IMDTouchKnowledge BaseShop main store

Troubleshooting

Why extending HMI system event display time reveals comms faults

HMI and touchscreens Published 7 min read

Short answer

Set the system event display period to 20 seconds under Alarms > System events > Display period and put an alarm viewer on the screen the HMI opens at startup. Start the HMI before the PLC or PLCSIM so a connection rejection stays on screen long enough to read and photograph. The longer period is diagnostic visibility, not a fix: verify the HMI and CPU addresses and the connection configuration separately.

On this page
  1. What the display period controls and what it does not
  2. The startup sequence that catches the rejection
  3. Read the event text and choose the next check
  4. Catching the rejection on a TP700 Comfort with a 2 second display period
  5. Judge the project edits on their own evidence
  6. Decision for each case
  7. Questions asked

When a Comfort panel drops its connection to the PLC and the message that explains why disappears before anyone can read it, set the system event display period to 20 seconds, put an alarm viewer on the screen the HMI opens at startup, and start the HMI before the PLC or PLCSIM. The engineering software exposes this under Runtime settings at Alarms > System events > Display period. Treat the change as diagnostic visibility, not a repair: it keeps a connection rejection on screen long enough to read and photograph, while the fault itself — most often an address or connection configuration mismatch — is verified and fixed separately.

What the display period controls and what it does not #

The alarm documentation for Basic Panels, Comfort Panels and RT Advanced puts the setting in the project navigation under the HMI device: double-click Runtime settings, then enter a value at Alarms > System events > Display period, and that value is the time each system event stays visible on screen. On the TP700 Comfort project behind this article, edited in TIA Portal V18 and running against an ET200SP CPU, system events were displayed for 2 seconds. A rejection that fires while the engineer is still starting the simulation or switching screens is gone before it can be read; 20 seconds is the value that left the message on screen long enough to work with.

The setting changes screen time and nothing else. It does not write an IP address, repair a connection configuration or resynchronize a clock, so a recovery that follows the change is an observation to re-test, not proof that the setting repaired a network path.

One production note: on a machine that has to keep running, as this process-required HVAC unit did, load the last known-good project to restore operation first and run the diagnosis on a bench copy of the modified project.

The startup sequence that catches the rejection #

  1. Set Alarms > System events > Display period to 20 s under Runtime settings.
  2. Place an alarm viewer on the HMI screen the runtime opens first, so system messages are visible from the first second.
  3. Start the HMI runtime or the HMI simulation first and stay on that screen.
  4. Start the PLC or PLCSIM second, so the connection attempt happens while the viewer is watching.
  5. Read any communication event that appears and photograph it, keeping the exact wording and the order in which messages arrive.
  6. If no event appears, confirm the viewer was on screen for the whole startup and repeat the sequence; an empty viewer is not proof of a healthy connection.
  7. Correct one item the event text names, then repeat from step 3, so each run differs from the previous one by a single change.

Read the event text and choose the next check #

The wording of the captured event is the fork in the diagnosis.

  • A rejection that names an unreachable endpoint points at addresses. This case had changed both sides at once: the HMI address through runtime and the CPU address through a hardware configuration download. Those are two independent edits on two devices, so verify each against the network the devices actually sit on, after every download.
  • An event saying the connection was refused or is not configured points at the HMI connection settings; compare them against the PLC endpoint in both projects, the known-good backup and the modified one.
  • Wording about date or time points at the panel clock. A clock offset between panel and CPU is a commonly reported rejection source, and Setting HMI clock time from PC and PLC daily removes that variable on a schedule.
  • A connection that comes up and then drops is a different fault family; work it with Diagnosing intermittent HMI to PLC Ethernet comms hangs.
  • A timeout on a serial link points at cabling, ports or addressing; Fixing HMI PLC Communication Timeout Over Serial walks that fault.
  • A failure that appears in simulation but not in the field, or the reverse, means two communication paths are in play. The PC/PG interface selection and the simulation connection settings belong to the bench path only, and a simulation that communicates validates nothing about the addresses downloaded to the real devices; Testing HMI Simulation Against a Live PLC covers closing that gap.

Catching the rejection on a TP700 Comfort with a 2 second display period #

Inputs:

  • Display period before the change: 2 s, the value found in place on the reported TP700 Comfort project.
  • Target display period: 20 s, the value the reported case settled on.
  • Capture task: reading a two-line event and photographing it, taken here as 10 s for one engineer standing at the panel — an illustrative estimate, not a documented or measured figure.
  • Screen: alarm viewer on the runtime's opening screen.
  • Startup order: HMI first, PLCSIM second, as in the sequence above.

Rule in words: an event stays on screen for exactly the display period, counted from the moment it appears, and you capture it only if that period is at least the time the capture task takes.

Arithmetic: at the original 2 s period, 10 s needed − 2 s shown = 8 s short, so the text disappears 8 seconds before the photograph would be taken and the rejection is effectively invisible even with the viewer on screen. At 20 s, 20 s shown − 10 s needed = 10 s margin, so the same event is readable, photographable and still on screen 10 seconds after that.

Result: 2 s loses the message; 20 s captures it with margin to spare.

Decision: set the display period to at least the capture time you need — on this bench, 10 s — and use 20 s on panel projects of this kind, which is the value the reported case used and which clears that threshold with margin. Any period shorter than the capture time loses events no matter how carefully the startup is ordered.

Judge the project edits on their own evidence #

List every difference between the failing project and the known-good backup, then test the deltas one at a time:

  • Added data blocks, added to ease SCADA integration.
  • A duplicated library set as default and saved, done to clear the errors when PLCSIM started with the new blocks.
  • A new HMI IP address, entered through runtime.
  • A new CPU IP address, entered through a hardware configuration download.

The communication loss followed the added data blocks, but the address changes landed in the same work sessions, so the sequence of events does not single the blocks out. Reinstate one delta at a time on the bench — blocks with the original addresses, then the address changes, then the library fix — and rerun the startup capture after each. Library load errors at PLCSIM start and HMI communication loss sit in different layers; unless a captured event text ties them together, treat that link as undetermined and simply record whether the library errors return.

On the reported case, simulation came up after only the display-period change, with nothing else touched in that session. Read that as an observed recovery: run the startup sequence twice with the viewer in place, confirm both device addresses, then download to the real panel and repeat before calling the fault closed, because a simulation success validates the bench path only.

Decision for each case #

  • Simulation refuses communication and no event is readable: set the display period to 20 s, keep the alarm viewer on the opening screen, start the HMI before PLCSIM, and photograph the event. Decision: no further restart without the longer window in place.
  • Field machine that has to run: load the last known-good project immediately and move the diagnosis to a bench copy. Decision: production first, and the modified project never reaches the machine until a captured event names its fault.
  • Viewer stays empty on two clean runs: stop restarting blind. Decision: compare the HMI connection settings and both device addresses between backup and modified project, change exactly one item, and rerun the capture.
  • Fault found and fixed: keep the 20 s period while diagnosis continues on that panel and shorten it afterwards only if lingering system messages disturb operators. Decision: the period neither causes nor masks connection faults, so leaving it in place costs nothing.

Questions asked

How do I make the panel itself tell the operator that PLC communication is lost?

Open the alarm editor in the HMI project, select the System Alarms tab, scroll to the system alarm for the communication fault, and add events that call SetBit and ResetBit on a tag. The bit sets when the fault appears and resets when it clears, and an indicator object shows that tag on every screen, so operators see a communication-lost sign without reading the event text.

Is a date and time difference between the HMI and PLC actually able to break communication?

A clock mismatch is the most commonly reported cause of HMI communication trouble on these panels. Let the captured event text decide: if its wording mentions date or time, set both clocks from one source and rerun the startup test; if the wording says nothing about time, leave the clocks alone and keep working down the address and connection checks.

Why did the simulation start working after I only changed the display period?

The display period rides into the panel on a recompile and download, and a fresh runtime start on its own can clear a wedged connection state, so the timing change is not the only variable in that session. Its documented function is on-screen time only. Run the startup sequence twice with the viewer visible, check both device addresses, then repeat on the real panel before calling the fault closed.

Can the 20 second display period stay in the production project?

Yes. The setting only lengthens the on-screen time of each system event and has no effect on the connection itself. Keep it while diagnosis continues on that panel; shorten it afterwards if operators dislike messages that linger. If operators should notice communication events at a glance, leave both the period and the alarm viewer in place permanently.

Keep reading

  • How-to

    Setting HMI clock time from PC and PLC daily

    Connecting a PC or PLC to an HMI synchronizes nothing. Set the HMI clock once from the PC, then let a daily script triggered by a PLC bit copy the HMI clock into the FX clock registers D8013–D8019 through the PLC's time-write instruction, and verify each hop with an independent read-back; on an A series CPU only the register numbers change.

    HMI and touchscreens

  • How-to

    Connecting an XBTGT HMI to an M241 PLC over Modbus TCP

    Delete the Generic Modbus TCP slave from the M241 device tree and activate the Modbus server on the controller's Ethernet interface instead — that slave makes the M241 a client, so both devices poll and neither answers. Then map Vijeo Designer driver address 40001 to PLC word %MW0, keep TCP port 502 open between panel and controller, and shift the address map by one word if a test read lands one register off.

    HMI and touchscreens

  • How-to

    How to Disable a Remote HMI Display Through PLC Control

    Put the interlock in the PLC, not the panel. Read each panel's current screen through Remote Display Number, force display 21 through Replace Display Number while the disable bit is latched, and on release write the stored number back, hold one second, then write 0 so the panel never reports it is being controlled remotely.

    HMI and touchscreens

Send M221 PLC time to an HMI clock in Operator Terminal Expert