Interested in programming a Jog command in RSLogix 500 without affecting the encoder count? This allows for adjusting pieces without altering the current counter. One possible solution is to temporarily move the encoder count into a float before jogging, then transferring it back to the High-Speed Counter (HSC) once the jog is finished. This method ensures accurate adjustments without disrupting the running count.
To maintain accurate counts during operation, it is recommended to ensure the High-Speed Counter (HSC) is always in an unconditional state. If you wish to avoid losing counts while jogging, consider using an XIO or XIC instruction before the HSC to deactivate it during jog mode. The HSC's Accumulated (ACC) value is unable to be overwritten, so transferring a value back into it is not possible. Additionally, there is no need to convert the HSC to a float as the Pre-Set (PRE) and ACC values are both integer-based.
Thank you for the suggestion! I apologize for the confusion, the counts in the HSC are integers and not floats. Currently, I do not have a rung specifically enabling the HSC, as it is enabled in the function files. Would it be possible to move a bit to HSC:0.CE or FE to deactivate it while jogging? MikeyN suggested keeping the HSC on an unconditional rung to avoid losing counts during operation. If you want to prevent counting while jogging, consider adding an XIO or XIC before the HSC to disable it in jog mode. It is important to note that the ACC value of the HSC is read-only, so it cannot be moved back into it. Additionally, it is worth mentioning that the PRE and ACC values of the HSC are integers only.
If you are using a MicroLogix PLC and looking for guidance on using the HSC instruction, consider setting the .CE bit to 0 while jogging. For those with a TechConnect contract, there is a helpful article available under ID: QA1634 | Access Levels: TechConnect, featuring a detailed document that can assist in achieving your desired outcome.
That's a smart approach! In the applications I've worked on, we had similar scenarios and were able to accomplish something like this using additional rungs and timers. These help to pause and resume the count around the jogging. I like your method though—it seems more efficient, as it uses less additional resources. Plus moving the count into a float ensures no loss of any fractional counts in the HSC due to jogging. I'll definitely keep this in mind for future projects. Thank you for sharing.
✅ 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: 1. How can I program a Jog command in RSLogix 500 without interrupting the encoder count? - One solution is to temporarily move the encoder count into a float before jogging and then transfer it back to the High-Speed Counter (HSC) once the jog is complete. This method allows for adjusting pieces accurately without affecting the current counter.
Answer: - Avoiding disruption to the encoder count ensures that the counting remains accurate and continuous during adjustments, maintaining the integrity of the counting process.
Answer: - Transferring the encoder count to a float before jogging helps in preserving the accuracy of the count by temporarily storing it in a different data type while performing the adjustment.
Answer: - Using a float variable allows for temporary storage of the encoder count during the jog operation, preventing any interference with the continuous counting process in the High-Speed Counter (HSC).
Answer: - While transferring the encoder count to a float is one effective method, other approaches may involve utilizing temporary variables or implementing specific logic to isolate the jog operation from the ongoing counting process.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.