Hello everyone, I operate a facility utilizing a 1756-L61 controller, and I am planning to upgrade to the L61S model with L61SP B, while retaining the same I/O modules. As this is my inaugural experience with this specific type of upgrade, I'm slightly anxious about potential challenges that may arise from the differences in implementation between standard PLCs and GuardLogix controllers. Currently, my strategy involves updating the programming so that the PLC in Rockwell Automation's Studio 5000 is set to L61S rather than L61. I intend to download the updated code onto the controller using a test rig in my office and then perform the swap during the next scheduled downtime. Here are some key considerations I’m aware of for this upgrade: - Configuring a Safety Network Number (SNN) when the L61S is installed in the final backplane. - Establishing a safety task signature. - Confirming that the GuardLogix is configured as the Control System Technology (CST) master. I would greatly appreciate any advice or insights from those who have experience with this type of upgrade. It would be invaluable for identifying any potential issues that I might encounter. Additionally, I've been searching for information regarding compatible firmware revisions for the L61S. However, RSLogix appears to restrict me to a maximum version of 20. Can anyone provide details on the latest firmware revision I can implement on this controller? Thank you in advance for your assistance! Best, Zac
Zacslade inquired: "Can anyone tell me what the most recent firmware update available for this controller is?" According to the Rockwell Automation website, the latest compatible version for the GuardLogix L61S controller is 20.018.
I don't anticipate you'll encounter significant issues. The Social Security Number (SSN) should resolve itself. There's no need for you to create a signature. It’s essential to configure the CST (Central Standard Time) master settings, ensuring you set a time—though it doesn't have to be precise, having a time is necessary. I recently faced a hiccup with this, as I don't remember having to do this before. If you're upgrading to version 20 from an earlier release, you might need to refresh some other modules within the system.
I have several questions to discuss, and while you may already be aware of this information, I noticed that certain key points were not addressed in your post, which piqued my curiosity. Specifically, I’m interested in the 1756-LSP, the addition of safety I/O, and the modification of the program to include safety tasks alongside the main task. Are you knowledgeable about these considerations as well?
To enhance your system with safety features, consider sourcing a 1756-LSP safety processor, which must be correctly positioned in the slot directly to the right of your existing processor. If there is already a module installed in that location, it will need to be removed and relocated. For I/O modules, it's generally a straightforward process of re-mapping your I/O assignments within the program, along with updating any corresponding drawings. However, if you encounter an Ethernet module, take heed: you may need to adjust configurations for other PLCs communicating with yours via MSG instructions or produced/consumed tags, as these will also require updates. In cases where you have a DeviceNet, ControlNet, or similar module, the situation may become significantly more complex. It's essential to ensure you have the appropriate version of Logix 5000 that accommodates safety processors, specifically the Professional edition or the safety add-on package. As mentioned by kekrahulik, generating a safety signature is not mandatory; your PLC will function normally even without one. However, incorporating any safety-related code necessitates thorough testing, documentation, validation, and securing it with a password along with a recorded safety signature—this is essential for compliance and accountability. Your primary objective appears to be upgrading to a new processor to maintain your system's current operation, with plans to incorporate safety I/O at a later stage. I won't delve deeper into those future considerations since you may already be prepared for them or will initiate a new discussion on that topic later. Additionally, I suggest contemplating the use of the 1756-L71S and 1756-L7SP models instead of the older 1756-L61S. The installation process will remain consistent; however, these represent the latest iterations of safety processors (the L81S is on the horizon but not yet available). Opting for these newer models allows for compatibility with advanced firmware versions. Furthermore, you'll benefit from the added advantage of storing comments directly on the PLC itself—an exclusive feature of the L71 series and later. Just be sure to have the correct software version, as the L71 requires firmware version 21 or higher. For any additional inquiries on this topic, feel free to explore the community at http://www.plctalk.net/qanda/member.php?u=55789.
To streamline your experience and save time in the future, it's important to remember that when you generate your safety signature and secure your safety program for future downloads, you'll need to unlock your safety settings first. Failing to do so may result in a download failure. This advice is particularly useful if you're working during a weekend shutdown and rely on a Monday-to-Friday tech support plan. Being proactive in managing your safety program can make all the difference.
✅ Work Order Management
✅ Asset Tracking
✅ Preventive Maintenance
✅ Inspection Report
We have received your information. We will share Schedule Demo details on your Mail Id.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.