Hello

We have a troubles with new CPU 1515-2PN (6ES7515-2AM02-0AB0).

He goes to STOP mode with STOP button by itself, no one touch any buttons. 

CPU works fine since September 2022. Program bloks has empty system OB's (program error, hw error, rack error, etc..). Cycle 100-150 ms, Memory 50%.

One day he stops with the event "pressing STOP button", but no one press the button and cpu don't want to start with start button. Staff in a critical moment decide just to power off and power on, and PLC runs!

He work 1 week and then again stops. This time he starts with just pressing a start button, but after 40 min stops again. One more time we press start and he starts fine. Event still the same, "pressing STOP button". No one touch any button, network without internet..

There is a suggestion that it could be a cpu with factory defect..

Does anybody know how to fix its issue or lock STOP button?

Diag buffer in attachments.

Thanks for every advice.

Have a nice day!

What's HW_ID 276, you know, the one generating all the errors?

rokise

Hello

We have a troubles with new CPU 1515-2PN (6ES7515-2AM02-0AB0).

He goes to STOP mode with STOP button by itself, no one touch any buttons. 

CPU works fine since September 2022. Program bloks has empty system OB's (program error, hw error, rack error, etc..). Cycle 100-150 ms, Memory 50%.

One day he stops with the event "pressing STOP button", but no one press the button and cpu don't want to start with start button. Staff in a critical moment decide just to power off and power on, and PLC runs!

He work 1 week and then again stops. This time he starts with just pressing a start button, but after 40 min stops again. One more time we press start and he starts fine. Event still the same, "pressing STOP button". No one touch any button, network without internet..

There is a suggestion that it could be a cpu with factory defect..

Does anybody know how to fix its issue or lock STOP button?

Diag buffer in attachments.

Thanks for every advice.

Have a nice day!

Thanks for reply!

That is error from AI module UR20-4AI-UI-16, connected as IO device (weidmuller) through PROFINET. On this one available spare inputs with active diagnostic.

Hello,

Perform a factory reset and reload the project or try updating the firmware.

Thanks you

Ahh, that device's spare inputs are providing things like wire break or short-circuit diagnostics, or over/under range?  If so, can you jumper spare analog voltage inputs and verify no jumpers are present for spare current inputs so that module stops filling your diag buffer with "noise"?

Once you get the diag buffer to only report real problems, it's much easier to find the root cause.

It could be the gsdml PN version used is not fully compatible with the firmware in the PLC.  For example, let's say the PLC is configured for PN 2.33 (or lower) and the IO devices are configured for PN 2.34, then you might get what windows calls "unhandled exceptions".

Perhaps there is an unhandled exception causing the PLC to go into stop mode because it misinterprets the current value of the RUN/STOP switch.

That's where firmware updates come into play.  The PLC firmware should be updated to the latest available.  Siemens may have already addressed the root cause, so give that a try as already suggested.

rokise

Thanks for reply!

That is error from AI module UR20-4AI-UI-16, connected as IO device (weidmuller) through PROFINET. On this one available spare inputs with active diagnostic.