Hello everyone, at my workplace, we recently acquired a CompactLogix L18ER-BB1B from eBay that required powering up and updating the PLC firmware. I have experience with updating CompactLogix PLCs over both Ethernet and USB connections, having done so successfully on numerous occasions. However, when attempting to update the firmware on this particular device, I encountered a communication error and flash failure. Despite following the usual procedures, such as configuring the IP address and leaving the system to update over Ethernet IP, I was unsuccessful. Now, the solid red OK light is on, and I am unable to establish a connection over either Ethernet or USB. Any assistance in resolving this issue would be greatly appreciated. Below are the Control Flash logs for reference: - [-------] User must install FactoryTalk AssetCentre Client 2.31 or above if attempting to log a message to FactoryTalk AssetCentre Server. - [SUCCESS] User [DESKTOP-63LPSI5\MALCO] logged in ControlFLASH successfully. - [FAILURE] Load Script: Error #1902: Invalid 'Identity3' item in the script file's [Device] section. - [SUCCESS] Load Driver: AB_ASA.DLL - [SUCCESS] Initialize Driver: AB_ASA.DLL - [SUCCESS] Device Identity: Controller ICE1 - [SUCCESS] Validate: Maj Rev=20, Min Rev=14 - [SUCCESS] The current logon user [DESKTOP-63LPSI5\MALCO] is authorized to update firmware. - [SUCCESS] Program: Catalog Number = 1769-L18ER/B LOGIX5318ER, Serial Number = 605FBEC9, Size = 8914216 byte(s). - [SUCCESS] Transfer: Start transfer of update. - [FAILURE] Transfer: Error #11003: Unconnected Send timed out waiting for a response. - [FAILURE] Load Script: Error #1902: Invalid 'Identity3' item in the script file's [Device] section. If you have any insights or solutions to this issue, please share them. Thank you.
I have a suspicion of encountering counterfeit goods, which I have experienced in the past with items purchased from eBay. It's worth noting that any counterfeit AB products I've come across have failed to start the firmware update process. A solid red light typically indicates a faulty processor. Have you considered the possibility of a faulty ethernet cable or connection causing the issue?
I recall a discussion on this online message board suggesting that RA software has the capability to render a controller inoperable if it recognizes a counterfeit product.
Currently, there are no counterfeit versions of the CompactLogix available in the market. However, there have been reports that 5069 series devices purchased from China may become inoperable. To resolve this issue, try loading the firmware onto an SD card using a different L18 device. This should help restore functionality to the device.
A user named geniusintraining mentioned that there are no counterfeit versions of CompactLogix available yet. They warned that if a 5069 series PLC was purchased from China, it may become unusable. They recommended loading the firmware onto an SD card and inserting it into another L18 PLC to resolve the issue. When inserting the SD card with the firmware into the "bricked" PLC, the system should boot automatically. Stay tuned for updates as I attempt this solution.
Update: I recently encountered an issue with an L18 PLC, which I attempted to solve by loading firmware onto the SD Card. Unfortunately, despite my efforts, the PLC continued to boot up with a solid red Ok Light. These specific L18 models do not feature a removable battery, so I also attempted to reset the device by opening it up and shorting the super capacitor to clear any remaining memory. Regrettably, this method did not resolve the issue, but I wanted to mention it in case others encounter a similar problem and wish to attempt it. Ultimately, I was unable to successfully restore the PLC's functionality and had to discard it, opting to secure a new one instead. I am eager to understand what may have caused this issue and how to address it effectively in the future. It strikes me as peculiar that a reputable brand like Allen Bradley could produce a PLC that is susceptible to becoming "bricked," but perhaps I simply lack the expertise to rectify such situations. Your insights and suggestions are greatly appreciated. Thank you.
Hi, from analyzing your Control Flash logs, it seems you might be experiencing issues due to an invalid 'Identity3' item in the script file's [Device] section which is causing the failure of script load operation. First and foremost, I recommend reconfirming all IP settings and ensuring compatibility between the device and the PC interfaces. Then, do a careful review of the script file you are using for the update. This persistent issue might be due to an incorrect or incompatible script. Additionally, the unconnected send time error could suggest network instability, or that something is blocking the update on your network. You can try to isolate this by connecting the computer directly to the PLC via Ethernet cable. I hope you find these helpful. Good luck!
✅ Work Order Management
✅ Asset Tracking
✅ Preventive Maintenance
✅ Inspection Report
We have received your information. We will share Schedule Demo details on your Mail Id.
Answer: Possible reasons for such issues could include incorrect configuration settings (such as IP address), script file errors, unresponsive device, or compatibility issues with the firmware update process.
Answer: Troubleshooting steps may involve checking the network settings, verifying the USB connection, ensuring the compatibility of the firmware version, examining the Control Flash logs for error details, and attempting a recovery procedure recommended by the manufacturer.
Answer: To address this error, you can try verifying the network connectivity, restarting the update process, ensuring the device is responsive, checking for any firewall or security settings that may be blocking the communication, and seeking guidance from technical support or the manufacturer.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.