Hello members, I hope you are having a great day. I have a question regarding renaming a file that is running in a controller, and I would like to provide an example for better clarity. Let's consider two machines, Machine A and Machine B. Machine A is running a program named 000_acd, while Machine B is running a program named 111_acd. Initially, both machines had their own programs, but at some point, a control engineer mistakenly downloaded the 111_acd program into Machine A's controller. Now, both machines are running the 111_acd program, which is different from the original 000_acd program in terms of constants and rungs. I would like to restore Machine A to its original program by renaming the program in the controller properties from 111_acd to 000_acd. However, when I try to do this online, the option appears grayed out. I am seeking advice on the best practices to make the program identical to its corresponding machine. How can I resolve this issue? I have attached an image for reference, which was taken when the controller was offline. Thank you for your assistance.
In this informative YouTube tutorial, you will learn how to easily rename a Logix controller program and PLC processor. Watch the step-by-step guide on how to change the name of your PLC processor in this video tutorial on YouTube. Click here to watch: youtu.be
Before anything else, it is important to note that the filename of the .ACD backup file may not necessarily match the Controller name. If you are looking to update the existing .ACD program backup file for Machine A to reflect recent program modifications on the Machine A PLC that were not saved in the old .ACD file for Machine A, you do not have to rename the Controller. To proceed, begin by creating a duplicate of the current .ACD file for Machine A and keep it in a safe place. Next, connect to the PLC with the Machine A program file. When you receive a notification indicating that the programs do not align, choose the option to upload from the PLC to synchronize them. Save the changes and the next time you go online, you should not encounter any program mismatch error messages.
When dealing with .ACD backup files, it's important to note that the file name may not always match the Controller name. If you're looking to update a .ACD program backup file for Machine A to reflect recent program changes made to the Machine A PLC, follow these steps: first, make a copy of the existing .ACD file for Machine A for backup. Then, connect to the PLC with the Machine A program file. When prompted about program mismatch, choose to upload from the PLC to align them. Save the changes to avoid future program mismatch errors.In summary, after opening the original Machine A file 000_acd and recognizing the Machine A running file as 111_acd, choose to upload the file when the mismatch warning appears. After uploading, Machine A should have the updated 000_acd file.
I find your naming convention to be confusing. In practical terms, there is an offline file (ACD) and an online program on the processor. When you establish a connection using the offline file, if the two do not match, you have two choices. Firstly, you can download: this involves transferring the offline file to the processor, overwriting the previous program in the controller. Alternatively, you can upload: this saves the program from the controller to the offline file, replacing the previous code in the offline file.
Robertmee stated that when you upload a program in the controller, it is saved into the offline file, replacing the previous code. However, it is important to note that the uploaded program is not immediately saved to your PC until you perform a Save. You can close the file without saving, and the previous offline file will remain intact. If you do choose to save it, the software will automatically rename the previous offline file and create a new file with the uploaded content. For example, if your original offline file was named Test.ACD, after uploading and saving the contents from your PLC, the file would be renamed to Test.My_Computer_Name.My_User_Name.BAK000.ACD. The software will keep the current version and the three previous versions before a file is permanently lost. This number of backups can be adjusted according to your needs.
Hey there! It seems like you're in a bit of a pickle there. The primary concern here is to ensure that Machine A gets its original program back and both your machines run their proper, customized settings. Typically, renaming a running program on a controller isn't a straightforward process due to operational safety and data integrity. What I'd suggest is downloading the original 000_acd program back into Machine A's controller from your database (I'm hoping you have a backup). It's a safer and cleaner approach than renaming the program online especially since different program files often involve different values and dependencies. This way, you also retain the original framework of the program specific to the machine. Always remember to back up your individual programs to prevent such instances in the future. Hope this helps!
Hi there! It seems that the grayed out renaming option could be due to the controller being run in remote mode. To perform certain actions like renaming a program, many PLCs need to be in program mode. However, please be aware that switching to program mode will most likely stop the process it's currently running. It would also be beneficial to check if you have the right access level. Also, rename operation in online mode may not be sufficient to revert to the correct program version. The rename function may only change the tag, while the program logic and attributes stay relevant to 111_acd. You might need to upload the original 000_acd program from your backups to truly revert Machine A. Remember: Always keep your PLC programs well-documented and backed up. It saves a lot of headache in situations like these. Good luck!
It sounds like a tricky situation! Since the option to rename the program is grayed out while you're online, it's likely because the controller needs to be in a specific state to allow changes to the program name. I’d recommend first downloading the original 000_acd program from a backup or the source you have, and then uploading it to Machine A when the controller is offline. Additionally, you may try shutting down the controller, making sure everything is saved, and then starting it back up again to see if that enables the renaming option. Always double-check your backups to make sure you won’t lose any important configurations. 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: - The option to rename a file in a running controller may be disabled online due to safety reasons and to prevent unintended disruptions. It is recommended to perform such actions offline.
Answer: - Renaming a running file in a controller without following proper procedures can lead to program errors, loss of data, and operational disruptions. It is crucial to carefully follow recommended steps to avoid such risks.
Answer: - Best practices for restoring a controller to its original program involve offline renaming of the program file, ensuring compatibility with the machine, verifying constants and rungs, and thorough testing before implementation to prevent any issues.
Answer: - Yes, it is possible to make the program in Machine A identical to its original program by following correct procedures for renaming and ensuring that the constants and rungs match the original program. Thorough testing should be conducted to confirm the restoration.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.