Everything was working fine and no changes to the firmware or program or any ignition settings, no updates to Ignition either.
I would appreciate your help.
Sounds like the only remaining culprits are the network components and the operating systems between Ignition and that device. You should use wireshark on the gateway to see what traffic, if any, is getting through.
We lost the program in the PLC. I was surprised to see that. It happen second time this month. My mind did not go there because couple of weeks ago we downloaded latest program. But anyways it is fixed now, we will keep an eye. Thank you.
1 Like
That is a rather old processor. Have you checked its lithium battery? (They only last for ~10 years.)
yes battery was replaced Jan-2020, atleast that is what the sticker on the PLC says. I will look into it, for now I added an alarm notification to monitor and this silent death until someone from the floor reaches out about the accuracy of the data. The goal is to get rid of this all together and move to L83-EP family controllers. Too many moving parts to do a clean cutover.
Ewwww! Selecting the "P" suffix is a really bad idea:
(Read the whole thing. Read all the inner links when you have the time.)
Thank you for sharing, I think we are stuck with it now. We got L83-EPs before we embarked on ignition. We had GEMS and Rockwell discontinued it so are best path was to move towards Plant-PAx.
so I guess we will have to learn the hard way now.
As noted, it isn't the processor, but the PlantPax that is the problem.