My H2-DM1E went nuts

[LWgreys]

Was getting ready to do a program update. I first selected the project. Left the CPU in RUN Mode. I then wanted to set the plc to manual configuration. So in the Configuration Menu, I set the Read Base to Manual mode. Then I updated the CPU and it went nuts. DMD 2.1 kept repeating Com Timeout Error. So I hade to truck across the plant  to were I have the DM installed and opened the cabinet, and there it was going NUTS. Had to a power off to clear the NUTS the CPU was doing. It was just rebooting over and over and over... again and again and again...

So I went back to the office and restarted the previous project to check up on the current program. Everything was normal. Even the Errors were clear. So I put it back in run mode and called it quits for the day.
I'll have to go into the DM and check its last error codes if there are any.

The current DM is all up to date firmware and the latest DMD software.

[BobO]

Yuk. Sounds like it got something stuck somewhere that upset its tummy. If you have a project that can dupe it, we'd love to look at it.

[BobO]

So was this following either a firmware update or a DmD update (maybe both)? If so, I have a theory.

[LWgreys]

OK, I was doing a program update. The firmware is the latest and DMD the latest version which was updated when they became available.

I checked the last errors in the PLC's memory and all were 0 No Errors. Then I checked the PLC Logs through DMD and found something interesting.

The events starting at S96 Sat Jan 06 11:46:56 2018 is were it was going NUTS.
I may need to order a new CPU module because it occurred also on the 3rd of Jan also.
I up loaded the EVENTS LOG File for you review.

I also am going to have to lock the cabinet door to keep the the people out and from doing a power OFF and ON over and over and over... when I told them not to be doing that.

[BobO]

Have you cleared the PLC and reloaded, or at a minimum, have you cleared the image register?

[LWgreys]

Not yet. I'll have to wait till the weekend to do that because we are running it currently the machine at this time.
Maybe it would be best to get a new CPU module first and swap it out, then program it which will give me time to play with the old one. Just in case if the old CPU is screwed-up.

[BobO]

Whatever you are most comfortable with. This sounds more like a firmware crash, possibly due to a corruption in the retentive image register content, than a hardware failure. I'm hoping that clearing the retentive memory clears it up.