scottmurphy
Member
- Join Date
- Oct 2004
- Posts
- 363
Hello,
I had an instance today where a L55 processor had faulted. I had to access this site remotely, and could ping the Ethernet Module, but could not see it with RSLinx.
I managed to instruct the op on site to cycle power to the PSU, and this allowed me to finally get online to the CPU. Once online, there was a major fault on the processor, indicating that there was a major un-recoverable fault, with no-program in the CPU.
I was able to clear the fault, download the last saved copy of the code, and everything returned to normal, so all good.
The issue is, what could of caused this fault? I thought that you could still get-online with a faulted CPU via Ethernet? The CPU and ENBT module are v16.20, with the ENBT module in slot 9, and the CPU in Slot 1.
Normally you can see what the faults are, are they all cleared on power cycling?
I had an instance today where a L55 processor had faulted. I had to access this site remotely, and could ping the Ethernet Module, but could not see it with RSLinx.
I managed to instruct the op on site to cycle power to the PSU, and this allowed me to finally get online to the CPU. Once online, there was a major fault on the processor, indicating that there was a major un-recoverable fault, with no-program in the CPU.
I was able to clear the fault, download the last saved copy of the code, and everything returned to normal, so all good.
The issue is, what could of caused this fault? I thought that you could still get-online with a faulted CPU via Ethernet? The CPU and ENBT module are v16.20, with the ENBT module in slot 9, and the CPU in Slot 1.
Normally you can see what the faults are, are they all cleared on power cycling?