Hi everyone
This error runtime received "SIGABRT - system may be in an inconsistent state "keeps popping up in CODESYS .Only recent ,for some reason .The PFC keeps running and no problems seem to appear in prg or HMI
Port Authetication has been disabled.I need to login in twice everytime this appears
Any ideas would be greatly appreciated
Regards
Matt
What is in the + of the second line ?
Look like the error come from a socket. do you use OPC-UA ?
I am not intentionally using OPC-UA. The Weintek HMI communicates using the CODESYS V3 symbolic driver, and I also use Modbus TCP. I will check whether the OPC-UA service is enabled on the PFC200. I will also expand the + on the second log line and send the details.
I have cleared it already so I will respond when it reoccurs next
just for information what Firmware are you using ?
The latest firmware 04.09.01(31).
contact wago tech support. i have the feeling something isn’t right in the program but i can’t put my hand on it
Edit: you don’t have a file system usage problem ?
If you have an SSH access (like using putty) check “df” command and see how much usage you have
Ok.Thanks very much appreciate you looking into it.Its bizzare as prg has been working fine .I will check df now
I checked the filesystem over SSH.
df -h shows /dev/root at 69% used with 78.9 MB available.
stat -f / shows 77,520 total inodes with 73,117 free, so inode usage is also very low.
It therefore does not appear to be a filesystem capacity or inode exhaustion issue.
I was getting repeated CODESYS runtime faults on the WAGO 750-8212, showing SysSocket – NonContinuable in CH_COMM_CYCLE, followed by SIGABRT and a warning that the controller may be in an inconsistent state.
To troubleshoot it I disabled OPC UA, but the fault still returned. I then found a very high number of Modbus exception errors. Packet capture showed that both Weintek HMIs were polling an invalid Modbus register every second. This was traced to an unused EasyBuilder Data Sampling entry reading 4x-12299. I deleted this entry from both HMIs, after which the WAGO Modbus exception counters remained at zero.
The SIGABRT fault later returned, so the Modbus errors were a separate problem rather than the sole cause. I checked the controller logs, Linux system logs and firmware. The controller is running firmware 04.09.01(31). I also disabled the unused Separated WebVisu ports 8080/8081 and rebooted the controller.
Since that reboot, the startup log has been much cleaner and the previous Channel timeout / Closing connection messages associated with the communication channel have not reappeared. The controller is now being left running to confirm whether the CH_COMM_CYCLE fault has been eliminated permanently.
So at this stage, the confirmed fixes are the removal of the invalid HMI Modbus polling and disabling the unused WebVisu ports, with the controller currently operating cleanly.
that’s interesting, maybe using the integrated network sniffing tool could be a good idea to see what could be a problem on the ethernet side.
Finally solved the communication/runtime errors on my WAGO 750-8212 PFC200 G2.
The problem turned out to be communications rather than the PLC program itself. I removed the old CODESYS V3 symbolic HMI connection on port 11740, disabled unused OPC UA/WebVisu services, and moved the remaining HMI communications over to standard Modbus TCP.
I then tracked down some incorrect/excessive Modbus polling from the HMI and corrected it. After that the Modbus exception errors dropped to zero and the controller has been running normally.
Firmware was also checked and confirmed current at 04.09.01(31).
So the main fix was cleaning up the communication methods and HMI polling rather than changing the PLC logic.
Many thanks for your generous time and support
Regards
Matt