Run · tab 5
Run and monitor
Tab 5 is the gateway’s dashboard: whether the service runs, what it is sending, and the state of every machine it reads.
Start the service
The installer starts the service, and it waits until it has a token and a password. Once tabs 1 and 2 are filled in, it begins on its own. If it is stopped, click Start the service on tab 5. Run.
- The service starts with Windows and runs with nobody logged in.
- Closing the app stops nothing. Only Stop the service does, and it asks first: no machine data is sent until it starts again, or Windows restarts.
- Opened by someone who is not an administrator, the app shows only this tab, with an Open as administrator button. Anyone may watch the machines and send diagnostics.
The status line
| It says | Meaning |
|---|---|
| Running | All good: machine data is read and Nexa answers. |
| Running, waiting for the machine data server | An OPC UA server does not answer. With several down it says how many. See Machine data. |
| Running, Nexa unreachable: buffering | Machines are read, but Nexa cannot be reached. Data waits on the PC and is sent when the connection is back. |
| Service stopped | Nothing is read or sent. Click Start the service. |
| The Nexa Edge service is not installed. Reinstall Nexa Edge. | Run the installer again; your settings are kept. |
The figures
| Figure | What it counts |
|---|---|
| Machine data servers | OPC UA servers connected, of those configured. |
| Nexa | Whether Nexa answered the last call, or the last error if it did not. |
| Linked tags | Tags linked to machines in Nexa that this gateway reads. |
| Machines fully read | Machines whose every tag has a good value, of all the machines it reads. |
| Sent | Minutes and readings Nexa has accepted since the service started. |
| Waiting to send | Batches buffered on the PC. Rises while Nexa is unreachable, then falls back to zero. |
| Rejected by Nexa | Readings Nexa refused as invalid. Should stay at zero; if not, send diagnostics. |
| Sending rules | Every linked tag, or how many tags are sent and held back by the rules of tab 4, and whether it is outside the upload window. |
Each machine
Below the figures, every machine the gateway reads, problems first, with since when it has been in that state and when its data last changed.
| State | Meaning |
|---|---|
| Disconnected | Its OPC UA server is down, or none of its tags has a good value. Shows within seconds of the server going away. |
| Partly read | Some of its tags have no good value. Check those tags in the OPC UA server. |
| No data yet | Just linked, or the service just started. |
| Flowing | Every tag is read. |
What you see in Nexa
On each linked machine’s Live tab:
- The gateway’s state: online if it was heard from in the last two minutes, with its last contact.
- Live values, refreshed every 2 seconds while someone has the tab open, and the last 30 minutes as a chart.
- Machine alarms from the fault tag, for the last two hours. A major fault also opens an unplanned downtime on the machine, closed when the fault clears.
- Trend rules: Nexa can warn when a measurement is heading for a limit, and suggest work before it gets there.
The first values
Live values appear within seconds of opening the Live tab. Minute data arrives about five seconds after each minute ends, so the charts and counts fill in from the next minute on.
Without the app
The service is an ordinary Windows service, so IT can also manage it from Services (services.msc) or an elevated prompt:
Get-Service NexaEdge # is it running?
Restart-Service NexaEdge # restart it (as administrator)