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.

1. Open the HMI
Section titled “1. Open the HMI”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.
2. Load a model
Section titled “2. Load a model”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.
3. Add an interface
Section titled “3. Add an interface”
In the viewer, open the CONNECT panel and add an interface:
- Choose the interface type — see supported protocols for the parameters each one needs.
- Enter the connection parameters (address, port, rack/slot, broker URL, credentials).
- 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.
4. Add signals
Section titled “4. Add signals”Signals carry the data. Depending on the protocol, you add them in one of three ways:
| Way | When |
|---|---|
| Browse | The controller can be browsed — OPC UA, MQTT, ctrlX, TwinCAT, EtherNet/IP, Keba, Festo |
| Import | You have a tag table, for example a Siemens tag export or an EtherNet/IP tag CSV |
| Manual | Everything else — S7, Modbus, FANUC, Denso, ABB RobotStudio |
Details and the direction convention: configuring interfaces.
5. Bind the model to the signals
Section titled “5. Bind the model to the signals”The viewer connects signals in the model and gateway by matching their names. There is no separate mapping step.
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.

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.
6. Check that data flows
Section titled “6. Check that data flows”
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 PLCis enabled on that interface. It is off by default. See configuring interfaces.
See also
Section titled “See also”- Connecting a PLC — the same set-up for virtual commissioning, with write access to the PLC
- Configuring interfaces — signals, directions, write access
- Supported protocols — connection parameters per protocol
- Troubleshooting — connected but no values, or values but no movement