Troubleshooting Latching Output Issues: Seeking Guidance and Solutions

Question:

I'm experiencing difficulties with my output not latching, and I'm unsure of the cause. I would greatly appreciate any assistance. The routine I’ve included is designed to monitor for sudden changes in tension—either a loss or gain—every second, based on the tolerance parameters established on the HMI. I have attached my logic for your reference. If you have any questions or need further clarification, feel free to ask!

Top Replies

You are currently comparing your stored values against the window limits. To enhance the accuracy of your comparison, please switch to the live values. For example, instead of using Tension_1_Control for your comparison, utilize Tension_1.

Upon reevaluating your setup, it appears that the comparators are arranged incorrectly. For the LEQ (Less Than or Equal) function to operate correctly, Source A should indeed be lower than Source B. I recommend reversing the GEQ (Greater Than or Equal) and LEQ commands on each latch rung, or alternatively, swapping the tags of Source A and Source B to ensure proper functionality.

User bernie_carlton commented: To enhance the accuracy of your comparisons, consider using real-time values instead of your saved values when assessing the window limits. For instance, instead of utilizing Tension_1_Control for your comparisons, switch to Tension_1. Click to expand... The rationale behind my approach is due to some fluctuations in my load cell input. By performing comparisons every second, I can minimize the risk of receiving a false reading that could trigger the emergency stop (E-Stop). In my machine, I am testing the tension on three distinct cables that are being tightened with a 50-ton screw jack and two 25-ton screw jacks. I even intentionally broke a cable to thoroughly evaluate this functionality, and I found that the mechanism did not engage as expected.

You are utilizing the stored values to calculate the window values based on the offset from the Human-Machine Interface (HMI). Next, you perform a comparison to check for any matching saved values. It’s important to note that the saved values will always fall within the window values they just established. Therefore, when making comparisons, it’s crucial to rely on the real-time or live values instead.

User jacoffey85 commented: Upon reviewing the setup again, I believe the comparators are switched. For the Less Than or Equal to (LEQ) condition to hold true, Source A must be less than Source B. I recommend either swapping the GEQ and LEQ commands on each latch rung or exchanging the tags for Source A and B. Click to expand... Initially, it was set up that way, but I altered it because I thought it was in reverse. I attempted both configurations, yet the latch still isn't functioning. Below is the previous logic for reference.

More Replies →

Streamline Your Asset Management
See How Oxmaint Works!!

✅   Work Order Management

✅   Asset Tracking

✅   Preventive Maintenance

✅   Inspection Report

We have received your information. We will share Schedule Demo details on your Mail Id.

You must be a registered user to add a comment. If you've already registered,
sign in. Otherwise, register and sign in.

Frequently Asked Questions (FAQ)

FAQ: A2: Common troubleshooting steps include:

Answer: - Verifying the logic design and ensuring it meets the intended function. - Checking the continuity of the control circuit to rule out wiring issues. - Ensuring the parameters set on the HMI are correct and within expected ranges. - Monitoring for any unexpected external signals that might reset the latch. - Reviewing any error logs or diagnostics available in the control system for clues.

Ready to Simplify Maintenance?

Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.

Request Demo  →