I am currently utilizing a software program that allows me to modify tag values through a Human-Machine Interface (HMI). I can successfully observe the tag value transition from 0 to 1, but unfortunately, this change is not reflected in the ladder logic program, resulting in no output. I am operating with a 1769-L18ER controller and a C-More HMI. Despite seeing the tag value update in real-time, the state within the ladder logic remains unchanged while I am in run mode. Could anyone share some insights or theories on what might be causing this issue?
Are you managing your daily routine?
Is your routine being scanned effectively? Perform a cross-reference check on these tags; they may be unlatched or written to somewhere within your logic.
What is the Tag Data Type? Instruction Usage Insights. It's important to note that not all instructions turn green when they execute successfully; for instance, the Greater Than or Equal (GEQ) instruction may not display a green status even when it's true.
Hello, I’m reaching out to discuss a recurring issue I’ve encountered. I’ve cross-referenced the tag associated with this particular program, which is quite simple in nature. It utilizes a Boolean data type, and the input values fluctuate; however, the rung state remains unchanged, resulting in no output. This situation is intriguing to me, as I’ve never experienced this anomaly without an underlying cause. I've thoroughly checked everything within my knowledge base. Interestingly, while the value updates instantly from the HMI (Human-Machine Interface), there is no corresponding change in the rung state. This has sparked my curiosity further.
According to Iadapt: "[T]he value updates immediately on the Human-Machine Interface (HMI), but there is no corresponding state change at the rung level." Let’s break this down for clarity. Are you changing a bit (setting value to 1) on the HMI, which then displays '1', while the Programmable Logic Controller (PLC) continues to read '0'? If this is the case, it’s likely that there is an issue with the connection between the HMI tag database and the PLC. This misconnection can lead to updates in the HMI tag database while the PLC remains unaware of these changes. While I don't have specific insights into C-More, in general, such issues often stem from how the 'Access' name (sometimes referred to as 'Topic' or another term depending on the system) is configured in the link connection. Another potential cause to consider is that you might be writing to a PLC address which is being overwritten by other PLC logic—such as OTE, OTL, or MOV commands. To troubleshoot this, perform a cross-reference check in the PLC for the tag to identify any conflicting bits. It’s possible the HMI updates the value to '1', and even though the PLC receives this value, existing logic may revert it back to '0' before any significant action occurs. If my interpretation of your reference to "on the HMI" is incorrect, please elaborate with additional details about your observations. Remember, your comments are not limited by character count, so feel free to provide as much information as needed.
It sounds like a frustrating issue! One possible reason for this discrepancy could be the way the ladder logic is programmed to handle the tag value. Sometimes, the logic might require a specific condition to be met before it updates the output. Also, double-check that the tag mapping between your HMI and the PLC is correctly configured; any misalignment can lead to the kind of behavior you're experiencing. Additionally, ensure that your ladder logic is actually running correctly by monitoring other inputs/outputs to see if the logic is executing as expected. It could also help to review any potential scan time issues or memory constraints that might affect the real-time updates.
✅ 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: - Tag Configuration: Ensure that the tag is correctly configured in both the HMI and the PLC. Verify that the tag data type and addresses match. - Communication Issues: Check the communication settings between the HMI and the PLC to ensure there are no disruptions or misconfigurations. - Scan Class: Verify if the tag is being updated in the correct scan class. The ladder logic may not be set to scan the tag frequently enough, causing a delay in reflecting changes. - Program Logic: Check if there is any condition in the ladder logic that might be preventing the state change from executing correctly.
Answer: - Monitor Communication Status: Check for any errors or warnings in the communication status screens of both the HMI and PLC. - Ping Test: Use network tools to perform a ping test between the HMI and PLC to ensure network connectivity. - Diagnostic Tools: Utilize diagnostic tools or software offered by the HMI or
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.