With the C-more panel and CLICK PLC described here, the HMI initiates the ordinary data exchange: it requests PLC values for display and writes operator-entered values to PLC addresses. These communications run alongside the PLC’s input-program-output scan; they are not a separate step inserted at a fixed point in every scan.
Check whether the operator control writes a PLC address
Read the control’s configured action and destination address in the HMI project. A touch by itself does not necessarily change PLC data: the configured object must issue a write, and the PLC logic must use the destination value if it is intended to affect the process.
- If the control is configured to write a bit or value, the HMI sends a write request to the PLC when the operator activates it.
- If it is configured only as a display object, pressing it will not produce the intended command. Correct the object configuration before troubleshooting scan timing.
- If the object writes but the process does not respond, monitor the destination address in the PLC and check whether program logic reads or overwrites it.
Do not treat an HMI button as a physical PLC input. A physical input is acquired through the PLC’s input circuitry; an HMI command arrives as communications data at a PLC address. The PLC can act on that data only as its program logic evaluates it.
Check the PLC value before changing scan timing
Monitor the address configured as the button’s write destination while activating the button. This separates a communications or object-configuration problem from a PLC logic problem.
- If the value changes, the HMI write reached the PLC. Trace the logic that consumes the address, including any conditions that inhibit the action or logic that resets or overwrites the value.
- If the value does not change, check the HMI object’s target address and data type, the active screen and control behavior, and the panel-to-PLC communication status. Compare the configured target with the address being monitored.
- If the value changes only briefly, look for PLC logic that clears the command, or an HMI action configured as momentary rather than maintained. Confirm the intended behavior in the project configuration.
The PLC processes communications data within its own execution and communications architecture. The exact point at which a newly written value becomes visible to a particular instruction depends on the PLC and communications implementation. Do not assume that an HMI write arrives at the start of a scan or that the PLC reads it as a discrete physical input.
Check whether the HMI is requesting the displayed value
For an on-screen PLC value, inspect the display object’s configured PLC address, then change or observe that PLC value while the relevant screen is open. In the common master-initiated HMI pattern described here, the panel sends read requests for data it needs to display and refreshes that data repeatedly.
- If the PLC address changes but the displayed value does not, confirm the object points to the intended address and data representation, and check whether the panel is communicating successfully.
- If the display updates but appears delayed, inspect the amount of data the panel must poll, including alarm-associated data as well as visible objects.
- If only some objects update, compare their addresses and whether they are on the active screen or included for alarm monitoring; then check communication diagnostics for failed or delayed requests.
In this request-response arrangement, the PLC generally does not push every display update to the panel. The HMI asks for PLC data, receives the response, and refreshes the display. A project or protocol can implement data exchange differently, so verify the configured communication method before applying this pattern to another system.
Check why screen refresh slows as requests increase
Count the data the HMI needs to refresh, not just the visible numeric objects. Alarm-associated tags can require polling even when their values are not displayed on the current screen. More requested data means more communications work and can lengthen the time between display updates.
| Observation | Likely cause to check | Next check |
|---|---|---|
| All values refresh slowly | Many screen and alarm data requests, or communication capacity and response constraints | Review the active screen’s tags and alarm-associated data; inspect panel and PLC communication diagnostics |
| Nearby addresses update together | The HMI may combine address reads into a range and discard unneeded intermediate values | Compare configured addresses and observe request behavior if the diagnostics expose it |
| Distant addresses behave differently | They may require separate requests, depending on protocol limitations | Review the communications protocol and its permitted request ranges |
| One value fails while others update | Incorrect address, data interpretation, or an individual request issue | Verify that object’s PLC address, representation, and communication status |
For example, if two displayed tags use V100 and V105, an HMI may request the range V100 through V105 in one read and discard the unused values between them. Two tags at V100 and V1000 may require separate requests. Whether the panel can combine addresses depends on the protocol’s request limits; do not infer an exact limit from the address spacing alone.
Check scan order without confusing it with HMI polling
Keep the PLC scan and HMI communications sequence conceptually separate. A PLC scan commonly samples its inputs, executes the program, and updates outputs. HMI reads and writes are communications transactions that occur as the panel requests data and sends operator changes; they are not synchronized to a particular rung or scan phase by the general sequence alone.
When a button writes a value, the HMI processes the write as quickly as it can. If the panel is waiting for a response to a read request, it can send the pending write after that response arrives. The PLC then makes the updated data available to its program according to its own communications and execution behavior. There is no universal fixed delay or scan number to assign without the actual PLC, protocol, configuration, and timing measurements.
When a display refreshes, the panel likewise requests the PLC data it needs and updates the object after receiving the response. Screen data and alarm-related requests compete for communications time, so display refresh and button response need not line up with the same PLC scan.
Restore operation, then verify the permanent correction
For a temporary restore, reduce avoidable HMI communications demand only through project changes that preserve required commands, displays, and alarm monitoring. For a permanent repair, correct the specific bad address, object configuration, PLC logic, or overloaded request set identified by the checks above. Do not remove alarms or suppress operator feedback just to make a screen appear faster.
- Record the HMI object’s configured PLC address and action. Monitor that address in the PLC while operating the control.
- Correct an address or action mismatch if the write fails to reach the intended location. If the value changes, repair the PLC logic or reset behavior that prevents the intended process response.
- For stale display data, compare the object address with the PLC value and check panel communication diagnostics. Review visible and alarm-associated tag demand, then remove or consolidate only requests that are unnecessary and permitted by the application design and protocol.
- Repeat the test with the control and display on the intended screen. Confirm the PLC destination changes as designed, the program responds correctly, and the displayed value follows the PLC value.
- Check alarm-associated data and other required screens after any polling optimization. Confirm no required indication or command was lost and that operation remains correct through repeated use.
Keep any temporary change documented and restore required monitoring before returning the system to normal service. If a write reaches the PLC but the process behavior remains unclear, stop changing communications settings and trace the PLC logic with a controls engineer.
FAQ
Does the PLC read an HMI button like a physical input?
No. The HMI writes a configured PLC address through communications; PLC logic uses that data. A physical input is acquired through the PLC’s input circuitry.
Does the PLC write display values to the C-more panel?
In the common arrangement described here, the panel requests PLC values and refreshes its display from the responses. Check the project’s configured communication method for the actual installation.
Can an HMI button write while the panel is reading PLC data?
The panel processes a write as quickly as possible; if it is waiting for a PLC read response, it can send the write after that response arrives. The precise delay depends on the communications and PLC implementation.
Does adding alarm tags slow HMI display updates?
It can. Alarm-associated data may be polled even when it is not visible, adding requests to those needed for the current screen.
Can the HMI combine reads for nearby PLC addresses?
It may combine tags such as V100 and V105 into one range read and discard unused values, while distant addresses may need separate requests. The protocol’s request limits determine what can be combined; stop before changing protocol or PLC settings you cannot verify, and contact official support for the panel or PLC if diagnostics remain unclear.