I have an intermittent issue with an ABB eCo PM554-eth where it occasionally goes into fault and stops running.
I have an intermittent issue with an ABB eCo PM554-eth where it occasionally goes into fault and stops running. I have to cycle the power to get it to run again and when I go online I find that all of the Retain Persistent variables have been corrupted. After resetting these variables back to correct settings it goes back to running normally.
The first time this occurred (about 3 months ago) I was doing an online download (without stopping processor), the second time (occured today) I was setting up a PC to view this PLCs webserver (//*.*.*.*/webvisu.htm).
After the first fault I replaced the PLC with a spare unit of identical specs and F/W. So now I have two pieces of hardware that have developed same fault. I am wondering if it could be a programming issue or a f/ware issue??
I am using Automation Builder 2.1, PLC is a PM554-eth running F/W 2.4.4
Voted best answer
when you can recharge the program inside the CPU, have you tried to check the error log?
Is the CPU connected to some peripheral devices that may have false contacts or dirt on the connectors?
A lack of coherence between the I / O mapping and the compromised physical presence of the links can cause an error like the one described, but they are only hypotheses, for more info you should access the alarm log and do some checks starting from the type of error.
not only with "diagshow all" command from PLC browser.
I mean the error log that you can read from Automation Builder side, as in the image you see below.
Open Automation Builder and login without open Codesys session.
In my example I have TK 503 cable with the CPU, but the functioning is the same:
If you push the Read Errors button, the CPU return the log of the errors that he have stored.
After the analyze, you can Clear all Error and try to restart the CPU
Hope this help you