Hello, I recently uploaded my project from a CompactLogix L36ERM and opened it in Studio 5000 (Version 29.00). Upon trying to go online, I noticed that the project differs from the one on the PLC, even though I just uploaded it. I believe this discrepancy may be due to a firmware version mismatch. Could you please provide some advice on this issue? The project title uploaded from the PLC is visible in the attached photo. Does the "29.11" in the title refer to the firmware version? Does this mean that the Studio 5000 version on my Laptop should also be "29.11"? I am hesitant to download the project to align the versions, as the system is currently functioning properly. In summary, the problem is that the controller project does not match the laptop project, despite being uploaded from the controller moments ago. The suspected issue is a mismatch in firmware versions.
It is essential for the major versions to align in both firmware and software revisions. Any alterations made in the studio, whether permanent or reversed, will prompt the need for an upload/download.
Cheeseface explained that it is crucial for the major versions to align between firmware and software revisions. Any alteration in the studio, even if reverted, will prompt the need for an upload/download. This confirms the relevance of the "29.11" in the project name to the firmware version. Thank you for the clarification.
If you are receiving this notification, it may be due to accessing the backup version of your project (identified by the BAK extension) instead of the most recent one. Autosave creates periodic backups that are consistently older than the current version and may not accurately reflect the data in the main file.
If you're seeing this message, it's likely because you're accessing an outdated backup file instead of the most recent version of your project. Autosave regularly saves files, but these backups will always be behind the current version. Make sure to always work with the latest copy to avoid discrepancies in the controller. Thank you for the valuable input, I will investigate further.
In a comment by Angus_Fergusson, they expressed their gratitude for the advice on adjusting the number of backup (BAK) files created and the timing of those backups. This can typically be done through the tools or options menu of a program. By setting up backups to occur every 10 minutes, the risk of losing important data is minimized. Uploading the current program, saving it as a new file, and then making modifications ensures that the original program can easily be restored in case of any issues. This method of creating backups ensures that operations can quickly return to normal if needed. It's important to stay aware of these features for maintaining data security.
Indeed, it sounds like you might be onto something with the firmware version discrepancy. The "29.11" in your project title could indeed be referring to the firmware version. Studio 5000 can be quite particular about matching firmware versions for optimal functionality, your software version should be the same as that of the PLC for smooth operation. But since your system is currently functioning well, it would be wise not to rush with downloading or adjusting anything. Instead, try to get a hold of Studio 5000 version "29.11" or contact Rockwell Automation support for further assistance before making any changes. It's always better to be safe and sure when working with functional systems.
Yes, you're on the right track. The "29.11" in your project title indeed refers to the firmware version of your PLC. And typically, it's best to have your development environment (Studio 5000 in your case) match the same firmware version. So ideally, your Studio 5000 should be version 29.11 to reduce discrepancies. However, before making any changes, ensure you have a good backup. You're smart to hesitate in downloading the project to your PLC, as this could potentially disrupt its operation. I suggest consulting with tech support before any major changes. Mismatches between the PLC and development environment are common, and they can usually advise the safest course of action.
✅ 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: Answer: To troubleshoot a firmware version mismatch, ensure that the Studio 5000 version on your laptop matches the firmware version of the CompactLogix controller. You may need to update Studio 5000 to the same firmware version as the controller or vice versa.
Answer: Answer: Yes, the version number in the project title, like "29.11," typically refers to the firmware version of the CompactLogix controller. It is essential to ensure that the firmware versions between the controller and Studio 5000 match to avoid compatibility issues.
Answer: Answer: If the controller project differs from the one in Studio 5000 after uploading, it could indicate a firmware version mismatch. Consider updating Studio 5000 or the controller to align the versions, ensuring that both match to maintain proper functionality.
Answer: Answer: While it may not be necessary to download the project immediately if the system is functioning correctly, it is essential to address the firmware version
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.