Hello, I am pretty new to working with PLCs and am seeking to update a MicorLogix 1100 1763 series A from FRN 3.0 to something newer. I am hoping to get it to communicate with the Ignition network I am building. I read that my outdated firmware was likely why I could not get their driver to work with my 1100.
I might have messed up though. At the bottom of this post, I get the below error codes in the log.
In updating firmware, I understand that I need to connect through the serial connector rather than the Ethernet I have been using to program the device. So I was able to get the RS-232 driver configured in RSLinx. With that done, I proceeded to using ControlFlash 12 to update to FRN 15. It began going to work and seemed okay until it errored. The device now shows the power led with the three below flashing and the screen reads as shown in the attached photo. Since then, I have tried Control Flash 8.0, 10.0, and 12.0 with various different firmware versions in hopes that there is some compatibility issue with the Series A I can overcome.
But it seems that something else is wrong. Maybe really wrong. I now can no longer access the device in RSLogix. I think this may have been my fatal error. I did not go into RSLogix to update the system Comms to the Serial connection I established in RSLinx. The PLC still had the Ethernet driver loaded.
Somehow the firmware update got far enough to wipe out the old FRN version but not far enough to begin the update. So now it is stuck in this boot sequence.
I guess my one hope is that since RSLinx still sees the device and all seems oaky there, that there still may be a chance to talk to the PLC.
Please let me know if I can provide any additional useful information. I appreciate your advice on what options I might be looking at here. Thank you.
________________________________________________
08/18/20 19:34:29 [SUCCESS] Load Script: C:\Program Files (x86)\ControlFLASH\0001\000C\00B9\ML1100_R03R15_Os.nvs
08/18/20 19:34:29 [SUCCESS] Program: Catalog Number = -----------------------------------, Serial Number = 000F73***26A, Num Updates = 2, Size = 546452 byte(s).
08/18/20 19:34:33 [SUCCESS] Update: Instance = 1, Size = 485036 byte(s), Chunk Size = 242 byte(s).
08/18/20 19:34:33 [SUCCESS] Load Script: C:\Program Files (x86)\ControlFLASH\0001\000C\00B9\ML1100_R03R15_Os.bin
08/18/20 19:34:50 [FAILURE] Transfer: Illegal command format.
DTL_E_FAIL, I/O completed with errors
08/18/20 19:34:50 [FAILURE] Transfer: Error Code: 24 Extended Error Code: 272 Context: 4
08/18/20 19:36:55 [FAILURE] Transfer: Illegal command format.
DTL_E_FAIL, I/O completed with errors
08/18/20 19:36:55 [FAILURE] Transfer: Error Code: 24 Extended Error Code: 272 Context: 4
08/18/20 19:36:57 [FAILURE] Transfer: File = C:\Program Files (x86)\ControlFLASH\0001\000C\00B9\ML1100_R03R15_Os.bin, Block = 26.
I might have messed up though. At the bottom of this post, I get the below error codes in the log.
In updating firmware, I understand that I need to connect through the serial connector rather than the Ethernet I have been using to program the device. So I was able to get the RS-232 driver configured in RSLinx. With that done, I proceeded to using ControlFlash 12 to update to FRN 15. It began going to work and seemed okay until it errored. The device now shows the power led with the three below flashing and the screen reads as shown in the attached photo. Since then, I have tried Control Flash 8.0, 10.0, and 12.0 with various different firmware versions in hopes that there is some compatibility issue with the Series A I can overcome.
But it seems that something else is wrong. Maybe really wrong. I now can no longer access the device in RSLogix. I think this may have been my fatal error. I did not go into RSLogix to update the system Comms to the Serial connection I established in RSLinx. The PLC still had the Ethernet driver loaded.
Somehow the firmware update got far enough to wipe out the old FRN version but not far enough to begin the update. So now it is stuck in this boot sequence.
I guess my one hope is that since RSLinx still sees the device and all seems oaky there, that there still may be a chance to talk to the PLC.
Please let me know if I can provide any additional useful information. I appreciate your advice on what options I might be looking at here. Thank you.
________________________________________________
08/18/20 19:34:29 [SUCCESS] Load Script: C:\Program Files (x86)\ControlFLASH\0001\000C\00B9\ML1100_R03R15_Os.nvs
08/18/20 19:34:29 [SUCCESS] Program: Catalog Number = -----------------------------------, Serial Number = 000F73***26A, Num Updates = 2, Size = 546452 byte(s).
08/18/20 19:34:33 [SUCCESS] Update: Instance = 1, Size = 485036 byte(s), Chunk Size = 242 byte(s).
08/18/20 19:34:33 [SUCCESS] Load Script: C:\Program Files (x86)\ControlFLASH\0001\000C\00B9\ML1100_R03R15_Os.bin
08/18/20 19:34:50 [FAILURE] Transfer: Illegal command format.
DTL_E_FAIL, I/O completed with errors
08/18/20 19:34:50 [FAILURE] Transfer: Error Code: 24 Extended Error Code: 272 Context: 4
08/18/20 19:36:55 [FAILURE] Transfer: Illegal command format.
DTL_E_FAIL, I/O completed with errors
08/18/20 19:36:55 [FAILURE] Transfer: Error Code: 24 Extended Error Code: 272 Context: 4
08/18/20 19:36:57 [FAILURE] Transfer: File = C:\Program Files (x86)\ControlFLASH\0001\000C\00B9\ML1100_R03R15_Os.bin, Block = 26.
