Signals & Alarms

Signals connect the visible twin to machine state. In a standalone model, simulated sensors, drives and logic provide the values. In Live mode, an industrial interface or realvirtual CONNECT discovers PLC signals and exchanges values with the running machine.

realvirtual presents signal values in the hierarchy, component information, CONNECT panel and signal search. A delivered HMI can also combine those values with configured status indicators, alarm messages, KPIs and documentation.

PLC signal convention

realvirtual uses Boolean, integer and floating-point signals with an explicit direction. The direction follows the PLC convention:

Signal	Meaning in realvirtual	Typical use
PLCInputBool / Int / Float	The viewer writes the value and the PLC reads it	Sensor state, axis feedback, an operator command sent to the controller
PLCOutputBool / Int / Float	The PLC writes the value and the viewer reads it	Motor or valve command, lamp, status or counter from the controller

The direction follows the PLC’s terminal strip. The field, represented here by the digital twin, supplies a PLC input. The PLC drives a PLC output, which the twin displays.

The displayed signal name comes from the model or the connected controller. A signal can also retain its full hierarchy path so the twin can resolve the correct component when names repeat.

Signal display and connection status

A signal chip can show its name, direction, type and current value, depending on the selected display level.
Hovering a chip can reveal the full signal details, source and component bindings.
For an active Boolean value, green identifies a PLCOutput and red identifies a PLCInput. These colors describe signal direction, not connection state.
An inactive or otherwise non-active value is grey. An amber force marker identifies a signal whose value is currently forced or overridden.
Connection and binding information is shown separately where the active workspace provides it. A lost connection can reconnect automatically when that option is enabled; confirm that Live mode is connected before acting on a displayed value.

Finding a signal

Open the Hierarchy and set its filter to Signals to list every signal in the model. The list shows names, directions and live values side by side, like a PLC tag list.

The hierarchy of the Laser Welding Assembly Station filtered to its 213 signals: TIA-style names such as BT4_AutoStart and FG_TS_Index01_B_Detect, each with a chip showing direction, type and value — PLC outputs in green, PLC inputs in red

The Laser Welding Assembly Station uses the same signal names as the real station’s TIA tag list. PLC programmers can find each tag by its familiar name during commissioning. Of its 213 signals, 193 are these TIA tags; the other 20, starting with SIM_, are helper signals of the virtual PLC.

Simulation or PLC

A model with a virtual PLC made of logic steps can run on its own logic or on a real controller. The Connection Mode component in the model stores the starting mode in StartMode.

While an interface is connected and the simulation runs, the Viewer and Commissioning workspaces show the current mode as a small button to the right of the simulation controls:

Shown	What runs the machine
SIM	The model’s virtual PLC writes the PLC outputs; the twin runs on its own
PLC	A real controller is expected to write the outputs; logic steps set to Active = Disconnected stay off, and ST programs stop writing only if they check `RV_SimulationMode`
PLC in green	A connected interface writes the model’s outputs and has taken over. The button is locked until it disconnects

Plant behaviour such as doors or an E-stop chain keeps running in every state.

Click the button to change between SIM and PLC; hover it for the full description. The document saves your choice.

Without a connected interface the button is hidden and the model runs in its saved mode. An AI assistant connected over the AI bridge can still switch it with the command sim.setConnectionMode (web_execute). The Operator Panel shows the mode in its first chip at all times.

Connecting alone changes nothing. An interface takes over when it writes its first model output. When the connection is lost or closed, the model returns to the saved mode, SIM or PLC. After reconnecting, the interface takes over again on its next output write. The same model can run as a laptop demo or as a commissioning twin connected to a real PLC, without editing it between uses.

Plant behaviour, such as doors or an E-stop chain, keeps running in both modes. PLC mode stops logic steps only when their Active setting is Disconnected; editor-created containers run Always. A Structured Text program stops writing only if it checks RV_SimulationMode; otherwise it runs until you stop it in the PLC editor.

Alarms and machine status

Alarm and status presentation is configured with the delivered twin. Supported HMI content includes alarm dashboards, messages, drive and sensor states, KPI overlays and production charts. A configured alarm can provide operator guidance or open the associated diagnosis and documentation workflow. Do not assume that every standalone GLB contains an alarm list or live data connection.

Quick Start

Open the twin in its HMI workspace and identify whether it is running in standalone or Live mode.
Select a component and inspect its signal chips or status indicators.
Hover a signal chip to review its name, direction, type, source and current value.
In Live mode, confirm that the connection and binding status indicate live data before acting on a value.
If the twin provides alarms or messages, open the relevant entry and follow the supplied component, document or diagnosis context.