How-to
Displaying safety controller status on an HMI panel
Short answer
Read status out of the safety controller's communication interface — Modbus TCP or RTU is the common route — with a matching HMI driver, and map each exported signal by location, width, bit position and polarity after checking raw words against the controller's online diagnostics. Keep every object read-only: the safety function stays in the controller and the display stays diagnostic.
On this page
- How do I get safety controller status onto an HMI panel?
- Which HMI driver do I select for the safety controller?
- Where do I find what the controller exports and where each signal sits?
- Why doesn't the safety project's symbol name work as an HMI address?
- How do I verify the raw reads before labeling any indicator?
- Why does an indicator show the wrong state or follow the wrong guard?
- Can the HMI write to the safety controller?
- What should the finished diagnostic screen show the operator?
- Questions asked
You display safety controller status by reading the data its communication interface exports — Modbus TCP or Modbus RTU is the common route — and pointing HMI objects at those exported locations through a matching driver. There is no conversion of the safety program into panel code, and none is wanted: the safety logic stays in the controller, and the panel shows guard states, output commands and fault flags as read-only diagnostics. The real work is a mapping table — location, width, bit position, polarity — verified against the controller's online diagnostics before any indicator gets a label. IEC 61511, the process-industry standard for safety instrumented systems, drives exactly this visibility: read status out for the operator, keep the safety function independent of the display.
How do I get safety controller status onto an HMI panel? #
Through the communication interface the controller already carries: configure it to export status over a documented protocol — Modbus TCP or RTU in most plants — and read those exported locations with a matching HMI driver; no translation of the safety program into HMI code exists or is needed.
A SICK Flexi Soft system, for example, exposes status through a communication interface whose documentation covers the status data, the planning and the related mapping, and the major safety controller families work the same way: the external data path lives in the interface configuration, not in the safety program. The panel side — EasyBuilder Pro on a Weintek panel is one instance — supplies only the driver and the address syntax. Decide the interface first and the panel project second: if no communication interface is installed and configured to export status, no amount of HMI work will produce data, and the first item to resolve is the interface, not the screen.
Which HMI driver do I select for the safety controller? #
Select the driver whose protocol and address types match the installed communication interface exactly — Modbus TCP for an Ethernet interface, Modbus RTU for a serial one — and choose it only after reading the interface's configured settings, never by vendor-name similarity.
Record from the installed hardware: the interface module, its protocol, its IP address or Modbus unit ID, and for a serial link its baud rate, parity and stop bits. Driver lists run long, and a safety controller usually appears on them as whatever its interface speaks, so the generic Modbus entry is often the correct choice even when a more specific PLC entry exists. Confirm the driver can address single bits inside words, or plan word reads with bit selection in the objects. If the panel itself is still to be chosen, selecting a Modbus TCP HMI panel for an existing controller walks through that decision.
Where do I find what the controller exports and where each signal sits? #
In the safety engineering tool, in the communication or mapping configuration of the interface: every exported signal is placed at a documented location with a width, a bit position and a defined asserted state, and that table is the single source of truth for the HMI.
| Field to record | What it tells you | How you confirm it |
|---|---|---|
| Signal meaning | Input condition, evaluated result, or output command | Controller online indication matches the intended function |
| Exported location | Data area and register offset | Raw HMI read agrees with the exported data |
| Width and bit position | 16-bit word, which bit carries the signal | Only the expected bit moves during the test |
| State polarity | What the 1 state and the 0 state each mean | Open and closed guard both display correctly |
| Screen label | Operator-facing wording | Label names the tested guard or output without ambiguity |
Bulk tools help at scale — one documented configuration tool exports or imports up to 200 Modbus mapping associations per CSV file — but the table above is what you carry to the panel. Keep it with the machine documentation: a copied HMI object that still carries the first object's address looks perfectly convincing while showing the wrong guard.
Why doesn't the safety project's symbol name work as an HMI address? #
Because symbol and address live in different namespaces: a symbol names a signal inside the safety project, an HMI address names a location a driver reads, and only the interface's mapping configuration connects the two — matching names prove nothing about a data path.
The mapping configuration is the entire conversion you were looking for: symbol in, exported location out, then the driver's syntax for that location. Bits inside words are where syntax diverges most — some drivers want a word address plus a bit number, others a standalone bit address — and a wrong entry fails loudly; fixing invalid bit address errors when adding HMI tags covers that failure as its own subject.
How do I verify the raw reads before labeling any indicator? #
Put one raw numeric object on a test screen reading the whole 16-bit word, then exercise each guard through both of its states under the machine's authorized test procedure and confirm that only the expected bit changes.
- Record the interface's identity, protocol and connection settings from the installed hardware, not from memory or an old printout.
- Open the controller's online diagnostics where you can see both states of each signal.
- Add the device in the HMI project with the selected driver and the recorded connection settings.
- Place a raw unsigned-decimal numeric object on a test screen and read the exported word.
- Actuate one guard: confirm exactly one bit changes and it is the documented bit.
- Restore the guard: confirm the bit clears and no other bit moved.
- Log the raw values for both states of every signal before building any indicator.
- Settle representation errors — off-by-one addressing, byte order — in the driver's settings, never by hunting for an address that makes the screen look right.
Work one register end to end, with illustrative numbers rather than a documented layout: a signal exported at register offset 10 of a 40001-based holding-register area, bit 3 of a 16-bit word. With a driver that counts 4x registers from 40001, the object address is 40001 + 10 = 40111. Guard open, the word should read 2^3 = 8; guard closed, 0.
If the object instead reads 2048, divide: 2048 / 8 = 256 = 2^8. The value sits eight bit positions high, which is one swapped byte, so fix the word-order setting in the driver and re-read. Do not move the address to bit 11: every other signal packed in that word would then read wrong. If the driver counts from 0 instead, the same offset lands at 40001 + 10 - 1 = 40110, and an off-by-one shows up as a neighboring signal's bit toggling when you actuate the guard. Word order bites hardest on 32-bit values, as displaying a PLC real value over Modbus on an HMI shows in detail.
Why does an indicator show the wrong state or follow the wrong guard? #
Four causes cover nearly every wrong indication: reversed polarity, a wrong bit position, a swapped byte order, or a copied object still carrying the first object's address — and each leaves a distinct signature in the raw word.
| What you see | Signature in the raw word | Fix |
|---|---|---|
| Colors or text reversed | Documented bit sets on the state you labeled closed | Swap the object's state labels to the observed polarity |
| Indicator frozen, word alive | Word changes, selected bit does not | Wrong bit number: recheck the mapping row |
| Value far too high | Reads 2048 where 8 was expected | Driver word-order setting, then re-verify every signal in the word |
| Another guard drives it | A bit in a different word toggles | Copied object kept the old address: re-point it |
| Nothing updates, no valid read | Communication error rather than data | Work the connection and polling first |
The last row is not a mapping fault at all: when nothing updates and the read itself errors, why HMI indicators stay off over Modbus RTU polling works that branch from the driver outward.
Can the HMI write to the safety controller? #
No: every object on this screen stays read-only, the safety evaluation runs in the controller, and under IEC 61511 the safety functions execute in the safety system regardless of what the display does — a status screen must never become an input to safety logic.
One safety note, in the one place it belongs: writing any value into the safety controller, or feeding any panel state into a safety function, is a modification to the safety system and goes through a safety reassessment, not through a screen design. Writing to a standard PLC from an HMI is a normal technique — toggling PLC BOOLs from HMI screens across the display boundary covers it — but it has no place on a safety diagnostic screen. Before deploying, strip write actions: check copied objects, touch actions and any scripts for stray writes to the controller's addresses.
What should the finished diagnostic screen show the operator? #
Guard states labeled with the polarity you observed, output indications labeled as commands unless feedback is also exported, and a visible communication-offline banner — three habits that keep a diagnostic screen honest.
An exported output signal is the controller's command, not proof that a contactor dropped: if the operator needs actual equipment state, bring the feedback input channel in as well and label the two indications differently. Drive the offline banner from the driver's device or communication status so a frozen word is never mistaken for a closed guard. Keep the controller's own fault diagnostics authoritative: the screen summarizes status for operators, it does not replace the safety controller's diagnostics or the machine's validated safety functions.
Questions asked
Is there a converter that turns the safety program into HMI screens?
No, and none is needed. The safety logic stays in the controller; what you build on the panel are display objects that read the signals the communication interface exports. You record each signal's exported location, width, bit position and polarity in a mapping table, then point objects at those locations and verify both states. The job is mapping and verification, not translation.
What do the indicators do if the Modbus link drops?
They stop updating, and a panel can leave the last value on screen, which looks exactly like a closed guard. Drive a banner from the driver's device or communication status so an offline controller is obvious, and treat any frozen indication as unknown until the link returns. The controller's own diagnostics remain the authoritative fault record.
Can one panel display two safety controllers?
Yes, when the panel's documented driver and connection limits allow it. Add each controller as its own device with its own connection settings and its own mapping table, and keep those tables separate in the machine documentation. Give each controller its own offline indication so one dead link is not hidden by the other's healthy display.
Does adding this display change the safety validation?
Not while it stays read-only. A screen that reads exported status sits outside the safety function, so the validated functions in the controller are unchanged. The moment you write to the controller, feed panel values into safety logic, or let the display influence a safety output, you have modified the safety system and it needs reassessment.