MadsKaizer

Hi All I was watching the Wago PFC300 webinar ( https://www.wago.com/global/lp-thank-you-onlineseminar-pfc-300 ), and the presenters comment about priority 1 being way above the Ethernet task priority, so that a priority 1 PLC program can actually loose SCADA connection, made me try to round up some hard evidence on Codesys Priorities. I find there is very little information on "correct" task priority configuration. There is a lot of different hardware manufacturers, using Codesys Runtime, that has...

We have similar issues, with crashing PLCs, but this ranges from 3.5.16.40 to 3.5.19.70. Which log made you confirm the exception crash? I am currently looking for evidence of what causes our PLCs to crash. Network stability could be an issue with latest security roll-outs like 802.1X and segregation.

Thank you, this came in handy a few years later :)

I got a Wago PFC200V2, running Codesys 3.5.16.40, 100ms scan cycle, consumes about 20ms. It will randomly crash the runtime every 10 minutes to a few hours. We suspect an overloaded ModbusTCP Slave Device, as this is work done by a 3rd party contractor, but we can not find anything in the help files or documentation, that mentions a hard limit on maximum number of clients connections. This PLC currently has 44 client connections to the Slave Device and 29 slaves configured for its own Master Device....

In V3.5.19.0 it seems that hide namespaces is forced, so our old 3.5.16.40 projects that show the namespace, are now loaded without namespace in 3.5.19.0. This sucks pretty hard, as it has to be turned off in EACH INDIVIDUAL program/method/act etc. Turning on namespaces in options does not help, it actually just makes it worse by some weird display error that shows some namespaces and some not. Another thing that really bothers me, why are all standard logic blocks like AND, OR etc, shifted 1 place...

All the log files there are only with data from after the latest reboot. There is a logrotate.status file that contains this: logrotate state -- version 2 "/var/log/sudo.log" 2021-12-21-14:0:0 "/var/log/runtime.log" 2021-12-21-14:0:0 "/home/log/wagolog.log" 2021-12-21-14:0:0 "/var/log/openvpn.log" 2021-12-21-14:0:0 "/var/log/syslog.log" 2022-1-2-18:1:0 "/var/log/lighttpd/error.log" 2021-12-21-14:0:0 "/var/log/kernel.log" 2021-12-21-14:19:0 "/var/log/lighttpd/access.log" 2021-12-21-14:0:0 "/var/log/earlymsg"...

I have a Wago PFC200 SL Runtime, that freezes up on me every 2-3 weeks. All it needs is a reboot and it runs again. But after the reboot, the log is "empty", I can only see the boot messages, not any messages from what made it halt. Is there a way to get a post-mortem log on freezing PLC? It looses network connection, so there is no OPC-UA connection, no webinterface, no shell access and cant even ping it.

Thank you for sharing these improvement speeds, its always nice to see some real numbers behind a patch note "Improved code execution" :)