Hello everyone, I'm currently facing a challenge and would appreciate some assistance. After updating my PLC program and transferring it to my controller, I encountered a problem when trying to run the program. Despite a successful download, the PLC remains in "STOP" mode and doesn't transition to "RUN" mode. I have a Allen-Bradley CompactLogix 1769-L24ER PLC and used Studio 5000 Logix Designer for the update. The changes I made include adding a new subroutine for additional sensor readings and some timer instructions. I have carefully reviewed the program for errors or typos and ensured all safety interlocks and necessary conditions are in place. Have you experienced a similar issue before? Could there be a hardware problem that I'm overlooking? Any insights or suggestions would be immensely helpful. Thank you in advance. Elena
To ensure proper functioning, verify that the keyswitch is positioned in the RUN or REMOTE mode under the memory card cover. Detailed instructions can be found on page 39 of the Rockwell Automation manual: https://literature.rockwellautomation.com/idc/groups/literature/documents/um/1769-um011_-en-p.pdf.
Attention Studio 5000 Logix Designer users! A product notice has been issued regarding a potential anomaly with versions V31 through V35 of the software. After downloading ladder diagram routines to certain controllers, such as ControlLogix 5580 and CompactLogix 5380, the routines may stop execution. The issue can be resolved by updating to software versions V33.02 and V34.02. For more detailed information and corrective measures, refer to Knowledgebase IDPN1620/1139086. Stay informed and keep your software up to date for optimal performance.
Aardwizz has announced a product notice regarding potential issues with Studio 5000 Logix Designer V31 through V35 Ladder Diagram Routines where execution may halt after downloading. It appears that the 1769 series is not affected by this notice. Click to learn more.
Can you clarify the concept of "stop" mode and whether it is indicated by a red fault signal?
In a forum discussion, jstolaruk noted that the 1769 series may not be covered in the product notice. Following their observation, another user suggested trying a possible fix based on personal experience with a similar issue. The suggestion involved switching the keyswitch to RUN mode from REM and power-cycling the PLC, as this workaround had worked on a different processor. It's worth a try for the original poster facing the problem, as sometimes the keyswitch commands may not always be followed accurately by the processor.
Hi Elena, I've had a similar experience with CompactLogix PLCs before. Since your download was successful, it's less likely to be a hardware issue but it's good to be thorough. I'd suggest checking whether your new subroutine is properly called in the main routine. Another angle to consider is the processor mode switch, make sure it's set to 'REMOTE RUN' or 'RUN'. If the issue persists, try going through the PLC fault table as it could provide some clues as to why the controller is not transitioning to 'RUN' mode. Hope this helps!
Hi Elena, a few things come to mind that you might want to check. One is to verify that the downloaded program has the same or newer firmware version as the PLC. Firmware incompatibility issues can sometimes cause complications. Also, ensure that your I/O configuration in the Studio 5000 matches the actual hardware configuration. Next, confirm that the PLC is in REM mode before you attempt to switch it to RUN. Furthermore, you might want to examine the PLC fault table in the Studio 5000 that might give you an indication if there's an issue with either your new function block or any I/O assignments. Finally, check the physical statuses. Make sure no critical hardware components are failing or reporting faults, including power supplies, modules, network cables or I/Os. I hope this helps and you can solve the problem soon.
Hi Elena, it sounds like you've thoroughly checked your program, which is a good step. I've experienced a similar issue once and it was due to my PLC being in "Remote Program" mode, not "Remote Run". Given you're using a CompactLogix, you might want to ensure your controller is in the correct mode. A simple oversight, but can cause quite a headache! Additionally, another area to investigate might be the status of the I/O modules, hence if your new subroutine involves an I/O module which isn't communicating properly with the controller, it could prevent a successful transition to "RUN" mode. 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: Answer: There could be several reasons for this issue, such as errors in the program logic, safety interlocks not being satisfied, hardware problems, or incorrect configuration settings.
Answer: Answer: You can start by checking the program logic for errors or typos, ensuring all safety interlocks and necessary conditions are met, verifying the configuration settings, and inspecting the hardware for any potential issues.
Answer: Answer: Double-check the newly added subroutine and timer instructions for correctness, review the interaction with existing program elements, and verify that the program as a whole is structured correctly and meets the required conditions for transitioning to RUN mode.
Answer: Answer: Yes, common strategies include thorough program inspection, debugging for errors, ensuring proper program organization, checking for conflicts with existing logic, validating hardware connections, and verifying that all necessary conditions for transitioning to RUN mode are satisfied.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.