NetNathan
Lifetime Supporting Member
At the site I am at I am converting several 90-30 plcs to RX3i.
While I am here, the customer had me look at a problem with one of the 90-30 units.
They are using Proficy Machine Edition 8.5
Every time they turn it off an back on it goes into stop mode.
Okay...I ask..
1. Did you change the battery...yes it is a new remote battery supply and the BAT light on the power supply is not on.
It is odd because I cannot even ping the IP address on the 372CPU. They use a remote battery pack (because the 372CPU is a battery hog)
1. So I have to use the com port to connect to the plc and go online to clear the CPU faults:
A. LAN transceiver fault
b, Configuration mismatch error in slot 0.4. This is an ALG222 module (it is correct in rack configuration) and it works after starting the controller all Analog IO is working on ALG222? NO issues. I run Validate and no errors or faults.
I download the logic everything is running fine, all IO working.
Power down and up...same errors!
We replaced the power supply and the backplane...same problems.
They had a spare 364CPU (from an existing project I had converted) and we tried it.
Same problem...but the com port would not connect to plc??
I knew the old IP address (3.0.0.23) of the module and tried it.
I can connect that way??..even though the PLC is n stop mode.
The CPU still had the original rack configuration logic in it?
I cleared the faults relating to rack configuration errors.
I downloaded to the plc with the new IP (3.0.0.20), and rack configuration, and saved to flash also, but it is configured to use RAM on start up.
Everything is good...no faults and all IO working.
Power down and restart. Stop mode again (no run light).
This is where it gets odd. The CPU has reverted back to 3.0.0.23 and the old rack configuration of that CPU (which caused the stop mode) ?????? WHAT??
I even tried a different 364CPU with an original address of 3.0.0.24 and the same issues exist??
I tired this 3 times:
Reconnecting with 3.0.0.23, clearing IO faults relating to old rack layout and downloading with IP reset to 3.0.0.20 and correct rack configuration.
Same issues??
WHAT would cause these issue?
While I am here, the customer had me look at a problem with one of the 90-30 units.
They are using Proficy Machine Edition 8.5
Every time they turn it off an back on it goes into stop mode.
Okay...I ask..
1. Did you change the battery...yes it is a new remote battery supply and the BAT light on the power supply is not on.
It is odd because I cannot even ping the IP address on the 372CPU. They use a remote battery pack (because the 372CPU is a battery hog)
1. So I have to use the com port to connect to the plc and go online to clear the CPU faults:
A. LAN transceiver fault
b, Configuration mismatch error in slot 0.4. This is an ALG222 module (it is correct in rack configuration) and it works after starting the controller all Analog IO is working on ALG222? NO issues. I run Validate and no errors or faults.
I download the logic everything is running fine, all IO working.
Power down and up...same errors!
We replaced the power supply and the backplane...same problems.
They had a spare 364CPU (from an existing project I had converted) and we tried it.
Same problem...but the com port would not connect to plc??
I knew the old IP address (3.0.0.23) of the module and tried it.
I can connect that way??..even though the PLC is n stop mode.
The CPU still had the original rack configuration logic in it?
I cleared the faults relating to rack configuration errors.
I downloaded to the plc with the new IP (3.0.0.20), and rack configuration, and saved to flash also, but it is configured to use RAM on start up.
Everything is good...no faults and all IO working.
Power down and restart. Stop mode again (no run light).
This is where it gets odd. The CPU has reverted back to 3.0.0.23 and the old rack configuration of that CPU (which caused the stop mode) ?????? WHAT??
I even tried a different 364CPU with an original address of 3.0.0.24 and the same issues exist??
I tired this 3 times:
Reconnecting with 3.0.0.23, clearing IO faults relating to old rack layout and downloading with IP reset to 3.0.0.20 and correct rack configuration.
Same issues??
WHAT would cause these issue?