Recently upgraded Firmware of MFP02 & NVRAM, completed off-line download, RESTORE blks not in module
I recently upgraded redundant MFP02 modules with newer firmware G5 and replaced NVRAM chips, completed off-line download, after a verification the RESTORE FC 140 blocks are not in the module. Has anyone else come across this?
Voted best answer
Very odd. Just to clarify, you compile and download the configuration to the controller, the controller works but the FC-140s that are in the CLDs are missing from the controller when you subsequently do a verify between the CLDs and the controller?
- If you do a verify between the CLDs and the CFG file are the FC-140s present?
- Revision G5 reportedly has some issues with saving and loading configurations that include Batch. Are you using Batch in this controller? If yes, did you download the controller from the NBS file or BDM? Try using BDM only.
- Did the controller firmware change by a major revision. I.E. F? to G5. If yes, it might pay to update the controller properties to reflect the new firmware revision and recompile.
- Are there any messages during the process of downloading and putting the controller to execute that are not normal?
- Does the module status report show any abnormal status bits being active or any messages?
- Did you do the special operations via SW4 to initialise the module? Maybe retry using Special Operation 2 (Initialise and format), 4 (Enable Infinet-Assuming you have an Infinet system) and 6 (Module timestamping-If needed for your site). After performing the Special Operations and the module is in execute, drop a fc89 (Last block, its an executive block already in the controller at block address 9999) onto a CLD and look at the block output. It's output should correlate to the the special operations carried out.
- When doing the offline download do you initialize the controller as part of the download dialog. An offline download would normally be yes to initialize the function code configuration memory space. Not initializing overlays the program over the existing memory contents. Not sure why this would cause the symptoms you observe.
- RIO02 firmware compatibility. The IMRIO02 firmware must be at E0 or greater.
- FC4 (PULPOS). Tuning a FC4 can cause a controller to redlight.
Source: E96-202 - Multi-Function Processor Module (IMMFP02)