Skip to content

First Connection

To show live machine data, the browser needs a model, an interface to the controller, and matching signal names. CONNECT not installed yet? The video walkthrough shows the setup up to the free license.

The bundled realvirtual HMI served by CONNECT — machine, KPIs and live alarms in the browser

Right-click the tray icon and choose Open realvirtual WEB, or open http://localhost:5100.

The gateway serves the bundled viewer from the same origin, so no configuration, CORS setup or second web server is needed. It connects to the signal channel automatically and shows the connection state in the CONNECT panel.

A hosted realvirtual deployment on your own server, or the public demo, can connect to the gateway on the operator’s machine. See where the viewer comes from.

A model is a GLB file that carries geometry and realvirtual metadata together. You get one in two ways:

  • From Unity — export or publish with Tools > realvirtual > Export > WebViewer Tools. Publishing into the gateway’s models/ folder updates a running gateway without restarting it.
  • From CAD — import a STEP or JT assembly directly in the viewer. Files too large for a browser tab are converted by the gateway, see CAD conversion.

Models placed in the gateway’s data folder appear in the viewer’s model list.

The CONNECT panel before the first interface exists

In the viewer, open the CONNECT panel and add an interface:

  1. Choose the interface type — see supported protocols for the parameters each one needs.
  2. Enter the connection parameters (address, port, rack/slot, broker URL, credentials).
  3. Save. The gateway starts the interface immediately and shows its state on the interface card.

A connected interface reports Connected. A failing interface shows the reason and retries with increasing delays (1, 2, 4, 8, 15, 30 seconds) until it succeeds.

Signals carry the data. Depending on the protocol, you add them in one of three ways:

WayWhen
BrowseThe controller can be browsed — OPC UA, MQTT, ctrlX, TwinCAT, EtherNet/IP, Keba, Festo
ImportYou have a tag table, for example a Siemens tag export or an EtherNet/IP tag CSV
ManualEverything else — S7, Modbus, FANUC, Denso, ABB RobotStudio

Details and the direction convention: configuring interfaces.

The viewer connects signals in the model and gateway by matching their names. There is no separate mapping step.

From PLC tag to component slot A PLC tag is read by an interface signal in CONNECT, which carries the address. The interface signal meets the model signal of the same name. The model signal is bound to a slot of a component, for example the Forward command of a drive. PLC tag DB10.DBX0.0 in the controller Interface signal ConveyorStart name + address in CONNECT Model signal ConveyorStart PLC Output, bool in the model Component slot Drive · Forward command slot moves the model protocol same name binding
The name match connects gateway and model. The slot binding connects the model to what moves.

A signal that exists on one side only stays visible but unbound. This is useful while a machine is still being wired up. The viewer marks bound and unbound signals in the CONNECT panel, making name typos visible.

The signal tree of a connected MQTT interface — a link icon marks a bound signal, a green dot a live value

Each row shows the interface signal and its address. On the right is the chip for the model signal with the same name. A link icon marks a bound row; a green dot on the chip means a live value has arrived. The panel header counts admitted signals against the license limit: Signals 4 / 20 on the free tier.

Live signals in the CONNECT panel — grouped by topic, with the current value on each chip

In the CONNECT panel:

  • The interface card shows Connected and a signal count.
  • Values move when the machine moves.
  • Writing a command signal from the HMI reaches the controller only when Allow web to PLC is enabled on that interface. It is off by default. See configuring interfaces.