Welcome to our new forum
All users of the legacy CODESYS Forums, please create a new account at account.codesys.com. But make sure to use the same E-Mail address as in the old Forum. Then your posts will be matched.
Close
I have a Wago PLC running runtime PFC200 V4.4 from Codesys. After a random amount of time 0 - 5 hours, the PLC goes into stop mode and I lose connection to the PLC from Codesys. I can still ping the PLC, but I can not reconnect to the PLC with Codesys. After power cycle the PLC goes back into run mode and then I can reconnect to it with Codesys.
Because I cant reconnect to the PLC when this happens, I can not see if it was an exception that caused this.
Is there a log file on the PLC I can check that might indicate why the PLC went into stop mode?
Regards
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Maybe the license is not activated? Then it will stop after 2 hours. I would suggest to check this first. You can check this in the log file (double click on the device and go to the log).
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
its not licensing, the license is activated. the log file does not show anything. i will take a screenshot of the log file if it happens again. Keep in mind I need to power cycle the PLC to get connection back. Not sure if the log file is cleared on power cycle.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi
I have had the same thing happen - It will be the Runtime shutting down for some reason. In my case it was due to reaching too high cpuload, which causes the runtime to stop. A lot of OPC UA traffic was taxing the CPU too much, so I eventually had to upgrade to a more powerful model.
You can take a look at /tmp/codesyscontrol.log (will not survive a reboot) which may give you some hints, or /var/log/
If the cause is the same, high cpuload, you can check this by typing 'plcload' in the PLC Shell, or watching 'top' in a shell.
Last edit: bjarne-pagaard 2022-08-19
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
thanks for the feedback. My CPU is running average at 90%, and the visu takes around 2-3 seconds to respond. If I load a tab/frame in the visu, the PLC hits 100%. It just baffles me that the logfiles does not survive a reboot, since that is the go to file for debugging things like this....
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Check the CODESYSControl.cfg.
Here you can specify where the log output is written to, so you can also let it write to file. Please regard the numbering, because it should be kept in order (0, 1, 2, etc).
Below a part which is copied from a .cfg file of the Control Win Runtime. This probably will look much the same on your controller.
[CmpLog]
Logger.0.Name=PlcLog
;Logger.0.Filter=0xFFFFFFFF
Logger.0.Enable=1
Logger.0.MaxEntries=100000
Logger.0.MaxFileSize=500000
Logger.0.MaxFiles=3
Logger.0.Backend.0.ClassId=0x0000010B ;sends logger messages to SysOut
Logger.0.Backend.1.ClassId=0x00000104 ;writes logger messages in a file
;Logger.0.Backend.2.ClassId=0x00000135 ;sends logger messages as UDP syslog
;Logger.0.Type=0x314 ;Set the timestamp to RTC
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks for the response Tim. Will the file that is being written to be cleared on PLC restart, or will the new entries on PLC startup just be written to a new line in the file?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have a Wago PLC running runtime PFC200 V4.4 from Codesys. After a random amount of time 0 - 5 hours, the PLC goes into stop mode and I lose connection to the PLC from Codesys. I can still ping the PLC, but I can not reconnect to the PLC with Codesys. After power cycle the PLC goes back into run mode and then I can reconnect to it with Codesys.
Because I cant reconnect to the PLC when this happens, I can not see if it was an exception that caused this.
Is there a log file on the PLC I can check that might indicate why the PLC went into stop mode?
Regards
Maybe the license is not activated? Then it will stop after 2 hours. I would suggest to check this first. You can check this in the log file (double click on the device and go to the log).
Hi
its not licensing, the license is activated. the log file does not show anything. i will take a screenshot of the log file if it happens again. Keep in mind I need to power cycle the PLC to get connection back. Not sure if the log file is cleared on power cycle.
Hi
I have had the same thing happen - It will be the Runtime shutting down for some reason. In my case it was due to reaching too high cpuload, which causes the runtime to stop. A lot of OPC UA traffic was taxing the CPU too much, so I eventually had to upgrade to a more powerful model.
You can take a look at /tmp/codesyscontrol.log (will not survive a reboot) which may give you some hints, or /var/log/
If the cause is the same, high cpuload, you can check this by typing 'plcload' in the PLC Shell, or watching 'top' in a shell.
Last edit: bjarne-pagaard 2022-08-19
Hi,
thanks for the feedback. My CPU is running average at 90%, and the visu takes around 2-3 seconds to respond. If I load a tab/frame in the visu, the PLC hits 100%. It just baffles me that the logfiles does not survive a reboot, since that is the go to file for debugging things like this....
Check the CODESYSControl.cfg.
Here you can specify where the log output is written to, so you can also let it write to file. Please regard the numbering, because it should be kept in order (0, 1, 2, etc).
Below a part which is copied from a .cfg file of the Control Win Runtime. This probably will look much the same on your controller.
[CmpLog]
Logger.0.Name=PlcLog
;Logger.0.Filter=0xFFFFFFFF
Logger.0.Enable=1
Logger.0.MaxEntries=100000
Logger.0.MaxFileSize=500000
Logger.0.MaxFiles=3
Logger.0.Backend.0.ClassId=0x0000010B ;sends logger messages to SysOut
Logger.0.Backend.1.ClassId=0x00000104 ;writes logger messages in a file
;Logger.0.Backend.2.ClassId=0x00000135 ;sends logger messages as UDP syslog
;Logger.0.Type=0x314 ;Set the timestamp to RTC
Thanks for the response Tim. Will the file that is being written to be cleared on PLC restart, or will the new entries on PLC startup just be written to a new line in the file?