Hello everyone, I am experiencing an issue with an Allen Bradley PLC model 1769-L30ER. After modifying the IP address and uploading a new program, the PLC successfully saves the changes. However, upon powering off and then back on, the PLC fails to retain the modifications and reverts to the previous program and IP address. This problem persists regardless of the presence of an SD memory card, ruling out the possibility of the previous program being loaded from the SD upon restart. The firmware version in question is 28.0.11. Any insights or solutions would be greatly appreciated. Thank you.
Welcome to the forum, Diberoma! When you mention updating the IP settings of the PLC, are you utilizing RS Linx for this process? And are you interfacing through USB?
AlfredoQuintero explained: Welcome to the forum, Diberoma. It seems like you're changing the IP settings of the PLC using RS Linx. Are you utilizing a USB interface for this task? Yes, that's correct. I've successfully adjusted the PLC's IP via RS Linx with USB and also attempted changing it through the Ethernet port. However, despite successful changes, the PLC reverts to its previous configuration upon restart.
It is likely that the CPU has been set up to boot from a memory card. After making adjustments, remember to save them to the memory card. Please note that this action cannot be performed while in run mode.
Ken Moore suggested that the CPU may have been set up to boot from a memory card. After making any adjustments, be sure to save them back to the memory card. Keep in mind that these changes cannot be made while the system is in run mode. I appreciate the advice and will attempt to follow these steps to see if they are successful.
It sounds to me like it might be an issue with the battery backup, which is responsible for retaining changes on power-down. If the battery isn't functioning correctly or is depleted, your PLC won't save changes when powered off. However, before concluding that, I'd also check whether you are correctly following the data storing procedure after making changes. Re-flashing firmware might also resolve if it's a software issue. See if any of these suggestions help - I had a similar issue and a battery replacement did the trick for me.
Hey there, sounds like a bit of hassle you're dealing with! One thing you could try checking is the battery in the PLC - it helps retain memory when the power goes off. If the battery is weak or dead, the PLC might lose any changes made. Additionally, try reloading the firmware, as it could either be corrupt or not compatible with your PLC model. Lastly, ensure to check "Load Program on Startup" or similar setting is selected in the program settings. If the project file doesn't have this selected, the PLC will always load its previous retained program on startup. Hope this helps you out!
✅ 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: 1. Why is my Allen Bradley PLC 1769-L30ER not saving changes after power cycling? - The issue of changes not being saved after power cycling could be due to a firmware bug, improper configuration, or a hardware malfunction.
Answer: - You can troubleshoot this issue by checking the firmware version, verifying the configuration settings, inspecting the hardware components, and ensuring proper programming and saving procedures.
Answer: - It is recommended to double-check and confirm that changes are saved correctly before power cycling the PLC. Additionally, keeping backups of the program and configuration settings is advisable to prevent data loss.
Answer: - Some common solutions include updating the firmware to the latest version, resetting the PLC to factory defaults, verifying power supply stability, checking for any error messages during startup, and consulting with Allen Bradley technical support for further assistance.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.