rvleugel

Hello Siemens colleges,

At our company we have a problem with falling of S7-1200's.
At one network we have around 20x S7-300/400 and 8 S7-1200's running.

This week i did a node scan (like searching for devices) and 5 of the 8 1200 plc's where in error (run to stop and not pingable.

I needed to do a power cycle to be able to connect from tia portal.

And open each s7-1200 plc with TIA portal to set from stop to run.

You have to know that some of this devices are communicating with other plc's etc.
Now i did some tests with a small network and a 1200 plc.

And yes, when i do a node scan (with some huge packet ping 256kb to the plc), the s7-1200 goes from run to stop and is not pingable.

Programs used:

TIA Portal V12 option device search.

S7-PCT - Port Configuration Tool.

test PLC:CPU 1212c DC/DC/Rly212-1HD30-0XB0Firmware V2.2

We tried webserver enabled and disabled, same results.

The other S7-1200's are not all the same type.

My the question is there a fix for this? ( i did not find anything at the internet)

Thank you.

huggy_d1

You may not like the answer you get from support request, but I am going to take a stab at it.

1. Ensure each PLC is not getting too much communications for the application. You can increase the communication % in each S7-1200 project up to around 50% to enable the plc to handle all the extra profinet traffic it is exposed to by being on such a large S7 network.

2. If the profinet traffic is also connected to the corporate LAN, you are going to have problems without some smart managed switches that filter out all non-essential traffic on the controls network. Siemens offers managed switches to help with that.

3. You can upgrade your S7-1200 PLCs to firmware 3.0 or 4.0 to improve their handling of all the LAN traffic.

CPU info: Serious firmware exception (not relevant for user, system code: 16#00644A4E 16#10000034 16#080D0000) |> CPU changes from RUN to DEFECTIVE mode |> HW_ID= 52 - Operating mode control

Description

Cyclic tests or exception handling have found a fatal malfunction in a CPU firmware function.

The CPU either remains in STOP mode (and sets a startup inhibit condition) or changes to the DEFECTIVE mode. All the CPU LEDs will flash to indicate this status. In this status, the program stops running and no further operator input is possible. Outputs are deactivated.

Note the additional information in the diagnostics buffer entry, particularly the reaction (mode transition actually initiated and newly set startup inhibit conditions).

Resolution

Normally, the CPU will be ready to resume operation once it has been turned off and on again or, in the case of more serious errors, once it has been turned off and on again without battery backup (in either case, the CPU must first be switched to STOP mode). Make a note of the HEX code marked as "Not user-relevant" in the detailed information for the diagnostics buffer entry and contact your manufacturer.

Make sure that it is not just a question of a straightforward mechanical problem by removing and reinserting the CPU.