Hello everyone, I've been working with RSLogix 500 for approximately five years, and I'm now starting to explore RSLogix 5000 programming. One of my initial projects at my current job involved modifying a few buttons that send print jobs to a laser printer. The process is relatively straightforward: certain bits are activated by one button, then another button is pressed to signal the laser printer to read those bits. After a designated period, everything is reset to ensure the printer’s I/O systems stabilize. Unfortunately, I've encountered an issue where this mechanism isn't functioning as intended. I've included a screenshot for reference. I've thoroughly searched for the One-Shot (ONS) and Output Latch (OTL) commands in the program to confirm they aren't located elsewhere. Additionally, I previously had the OTL implemented as an Output Energize (OTE) command, but switched it just to test if it would yield better results—unfortunately, it did not. I've also tested the buttons in real-time and observed that the rung turns green, except for the output section. If anyone has insights or suggestions on troubleshooting this issue, I would greatly appreciate your input!
I have a quick question: Has that specific output been utilized anywhere else within the program? If that's the case, the associated rung might keep the output at 0. Consequently, while your designated rung may turn true, the output could still remain at 0 due to its dual usage. Just a thought to consider... Stef.
When faced with situations like this, the initial steps you should take involve checking for additional improper uses of the output tag (as you've already mentioned) and verifying that the rung is correctly placed within a subroutine that is being invoked.
You may already be aware of this, but have you checked for word access at that specific address? I've come across instances elsewhere where bits are cleared using a FILL instruction or through standard word or integer access methods. Could that be the issue here? Is there a possibility that the tag could be overwritten by another PLC?
Common Troubleshooting Questions for Your Program: 1. Is your program actively executing? 2. Does it incorporate any jump or label commands? 3. Try adding a counter alongside your OTE/OTL instructions to monitor if it will increment. Understanding these aspects can help ensure your program runs smoothly and identifies any potential issues.
To gain a definitive understanding, we require additional details about the program. As Stef pointed out, it may have several potential destructive applications. Additionally, there’s the possibility of a rapidly resetting timer that could be contributing to the issue. We could engage in endless speculation on this topic.
✅ 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.