Rockwell Automation 1757-SWKIT5000 ProcessLogix R500.1 Installation and Upgrade Guide - Manual (Page 190)

Publication 1757-IN500A-EN-P - September 2002
7-10 Firmware Maintenance Procedures
Special Considerations
Loading Boot Image
1. Click the desired CNB or ENET icon under the desktop tree and wait
for the graphic of the chassis to appear in the detail pane.
Table 7.B Special Considerations when Loading 1757-PLX52, TC-MUX021, or 1757-FIM
Boot and Personality Images
Special Considerations Description
Upgrading the 1757-PLX52 from
R300.0 to R500.1 When upgrading the firmware from R300.0 to the R500.1 firmware, the CPM will
not reset after the flash is completed. The module will display wait on the module
LED for an extended period of time.
Please follow these steps when upgrading a 1757-PLX52 from CPM300-xx.x to
PS500.1-01.1:
1. When you receive a new 1757-PLX52 and are ready to update its
firmware, check the firmware revision in NTools. If the boot code is not
CPM300.3-xx.x you will not be affected by this defect.
2. Flash the 1757-PLX52 with the new boot firmware. The 4-character LED
display should transition from:
ALIV to LOAD to wait
The wait text indicates that the CPM is writing the new boot image to flash. After
the image is written, the CPM will usually reboot. If the CPM doesn’t reboot and
continues to display wait for 10 minutes or more, then manually cycle power to
the module. Wait at least 10 minutes to ensure that the new boot image was
written successfully.
Redundant Chassis Firmware
Upgrade Precautions When updating 1757-PLX52 modules in a Redundant Chassis Pair (RCP), you must
turn OFF power to the Secondary Chassis in the RCP, so you can update the
firmware in the 1757-PLX52 in the powered controller chassis while it is in a
Primary with no partner state.
Once the 1757-PLX52 module is updated in the powered chassis, turn OFF power
to this chassis and turn ON power to the other controller chassis to repeat the
firmware update for the other 1757-PLX52 in the RCP. This avoids possible
confusion caused by the logical change in Network Addresses in response to a
controller switchover.
FIMs and Fieldbus Devices Reload
after Upgrade After updating firmware for all FIMs, all FF devices and all associated Control
Modules must be reloaded, even if the FF devices were allowed to continue
independent operation during the ProcessLogix upgrade. This is to permit the FIM
to view and save interface information that it may need for proper interface
operation.
TIP
The devices with non-compatible versions of firmware
display their firmware versions in red. Devices with the
correct version of firmware display their firmware version
in green. Unknown devices are displayed in yellow.