Selection guide
Running an Ignition Vision Client as a Machine HMI Without Edge
Short answer
No Edge license is needed. A Vision client at the machine is one more client session of your existing on-site gateway, so the only check is whether that gateway's license counts clients. Edge is a separate device-level gateway for machines that must keep running with the site link down; your panel HMI stays as the OPC UA server either way.
On this page
- Why a Vision client needs no Edge license
- The one licensing check to make
- Client of the site gateway or Edge at the machine
- What stays in the panel
- Hardware at the machine
- Worked example: fitting four machine stations on a five-client license
- Commissioning the station
- Proving the path end to end
- Questions asked
No. A Vision client at the machine is a client of the gateway you already run, not a new server, so nothing about it calls for Ignition Edge. The licensing question reduces to a single check: whether your on-site gateway's license counts Vision client sessions. The default license is sold per server with unlimited clients, tags and projects, so a machine HMI added this way draws no additional license at all. Edge enters only when a machine must run its own gateway with the link to the site server down, and your panel HMI stays in the cabinet as the OPC UA server either way.
Why a Vision client needs no Edge license #
Ignition is licensed per server — one license per gateway — and by default that license is unlimited: unlimited clients, tags and projects, per the vendor's 8.1 licensing documentation. A Vision client is a session of the gateway it connects to, the same class of thing as the desktop clients you already open. Adding a machine station adds a session, not a server, so there is nothing for an Edge license to cover.
Edge answers a different question. It runs a local gateway on the machine itself, with a limited module set and no database connectivity, per the vendor's Edge overview, and it exists for machines that must keep visualizing while the site server is unreachable. A machine that sits on the plant network, a few hops from the gateway, is not that machine.
The arrangement you already have — one headless gateway feeding operator stations — is the split walked through in headless HMI server versus operator panel selection. The machine screens are simply more of the client side of it.
The one licensing check to make #
Open the gateway's web configuration and read the client allowance on its licensing page. On a default per-server license it reads unlimited. A number appears only when a limited client count was specified at licensing time, and the documented correction is to amend the license and reactivate the gateway, after which Vision runs under the full allowance.
Count what the allowance has to carry: every machine station that stays launched, every desktop client left open through the shift, and any designer session kept running. If the total sits at or under the allowance, add the stations now. If it passes the allowance, amend to unlimited first — the license, not the architecture, is the blocker.
Client of the site gateway or Edge at the machine #
| What you are deciding | Vision client of the site gateway | Edge gateway at the machine |
|---|---|---|
| License it draws on | the existing per-server license, unlimited clients by default | a separate gateway license for that machine |
| Where the project runs | on the site gateway; the station only renders it | on a local runtime at the machine |
| When the site link drops | the screen shows its disconnected state and recovers | the machine keeps visualizing locally |
| Database connectivity | through the site gateway | none, per the Edge overview |
| Module set | whatever the server license carries | a limited set |
| Best fit | machines on the site network | machines that must run through a link outage |
Pick the thin client whenever the machine is on the site network and an unreachable server means a blank screen, not a stopped process. Reserve Edge for machines that must keep their interface when the link is gone; that is the one condition it exists for.
What stays in the panel #
Keep the panel HMI that currently serves OPC UA between the PLCs and the gateway. A Vision client never opens the PLC link — it talks to the gateway, and the gateway holds the OPC UA connection and the tags. Nothing on the PLC side is rewired for this change.
Before building any window, confirm the layer the windows will inherit: the gateway's OPC UA connection to the panel server reports connected, and the machine tags show good quality and track the process. A tag that is bad at this layer displays as bad on every screen built on it, so fix it at the connection or the tag first.
Hardware at the machine #
Any computer that runs the Vision client launcher and can reach the gateway will do the job; the choice is reliability and maintenance.
| Station hardware | Use it for | Plan for |
|---|---|---|
| Industrial panel PC or thin client | production and critical machines | panel mounting and continuous duty |
| Single-board computer with a small touch display | trials, secondary screens, non-critical stations | a way to reboot it without a site visit |
| Existing desktop PC | commissioning and engineering | not a machine-mounted station |
Single-board computers are workable here: reported setups run the computer and its touch display as a machine HMI from a single PoE+ port, which supplies 30 W under 802.3at Type 2. Weigh the reliability reports as the deciding input — facilities running them in production report occasional freezes that need a reboot, and advise against them for critical duty. When a frozen screen would stop production or hide alarms, use industrial panel PCs at those machines and keep the single-board units where a blank screen costs nothing. Because the panel server holds the PLC link and the gateway holds the tags, a hung station loses you the display, not the data path.
The hardware shortlist is the one walked in selecting a touch panel that can run Ignition, which covers the sizing questions for a station hosting this software.
Worked example: fitting four machine stations on a five-client license #
Inputs:
- Licensed Vision client allowance on the gateway: 5 sessions. This is the limited-client case the licensing notes describe, where the count was set when the gateway was licensed; the default is unlimited.
- Desktop clients left open through the shift: 2, from your own session audit.
- Machine stations to add: 4.
- Designer session kept open during commissioning: 1.
The last three are illustrative counts; substitute your own audit for them.
Rule in words: a limited client allowance counts every simultaneous Vision session, and a machine station holds its slot for as long as it stays launched.
2 desktop clients + 4 machine stations + 1 designer = 7 simultaneous sessions
7 sessions − 5 allowed = 2 sessions over the allowance
The rollout does not fit the license as it stands. Amend the gateway license to unlimited clients and reactivate it: the per-server license already covers the sessions, and the stations need only the site link, not a local runtime. Any total above the allowance is a license blocker, not an architecture problem — on an unlimited license the same 7 sessions need nothing.
Commissioning the station #
- Install the Vision client launcher on the station, add the gateway project, and confirm the project opens manually before automating anything.
- Create a dedicated user for machine stations in the gateway's user source, with only the roles operators need, so a station cannot reach configuration screens.
- Point the project's startup window at each machine's own screen, with per-station parameters, so every station lands on its machine.
- Set the operating system to log in automatically and start the launcher at boot, full screen, relaunched on exit by the OS startup mechanism. The supported auto-login and kiosk-style launch options differ between releases, so take the exact settings from the documentation for the version you run.
- Power-cycle the station with no keyboard or mouse attached. It must reach its machine screen unattended, and the gateway's client list must show one session under the station user.
Proving the path end to end #
- Read a value at the PLC and see the same value on the machine screen.
- Write one setpoint you have confirmed is harmless to the running process — a value that moves an actuator is not a test point — watch it arrive at the PLC, then restore it.
- Unplug the station's network cable for a minute and reconnect: the client should show its disconnected state, then recover to the live screen without manual action, while the PLC and the panel server keep running.
- On single-board hardware, run a full shift before calling the station done; if it freezes, add a remotely switchable PoE port or a hardware watchdog, or move the station to an industrial PC.
Questions asked
How many Vision client stations can one gateway serve?
There is no licensed ceiling on the default per-server license, so the limit is the gateway's hardware, not the license. The vendor publishes a server sizing and architecture guide with gateway performance benchmarks for standard and Edge projects; size the host against your tag count and session count from that, and add stations until the host, not the license, is the constraint.
Can I add the first station before touching the license?
Yes, when the gateway's licensing page shows unlimited clients: install the launcher, point it at the project and run, with nothing to activate. If it shows a number instead, audit your always-on sessions first, because a limited allowance blocks the new station the moment the total passes it.
Does each machine need its own Edge license if I go that route later?
Yes. Edge is licensed per gateway, and a machine running its own runtime is its own gateway, so four machines means four Edge gateways alongside your site server. That is what you accept for local operation through a link outage; when machines sit on the site network, the thin-client route needs none of it.
Can the station power itself over the network cable?
Reported setups run the computer and its small touch display from one PoE+ port, which supplies 30 W under 802.3at Type 2. Check that the switch port is PoE+ and not the 15 W PoE type before you rely on it.
Does the plant-wide OPC server I want to trial change any of this?
No. Add it in the gateway as a separate OPC UA connection and leave the existing panel-server connection alone: tag paths carry the connection name, so moving tags between connections breaks the bindings already on them. The new stations read gateway tags and never see which connection feeds them.