PHANTOM® Gateway
The PHANTOM® Gateway offers four integration interfaces, in addition to sending data to EI Analytic and EI Monitor.
Reading data
Section titled “Reading data”Three industrial protocols carry sensor telemetry. Use these when you are integrating with a SCADA, a historian or a PLC rather than writing application code against an HTTP API.
| Protocol | Port | Gateway acts as | Full waveforms? |
|---|---|---|---|
| Modbus TCP | 502 | Server | No |
| MQTT | your broker’s | Publisher / subscriber | Optional |
| OPC UA | 4334 | Server | No |
All three can run at the same time, and alongside EI Analytic and EI Monitor. Enabling one does not disable another.
Controlling the gateway
Section titled “Controlling the gateway”The fourth interface goes the other way. The Management API is the same API the Gateway Admin Console uses, so it can do anything the GUI can: change gateway and sensor settings, observe live state, and request measurements on demand.
It runs over WebSocket or MQTT and speaks the same JSON protocol on both.
| Page | Covers |
|---|---|
| Management API | Overview and the WebSocket interface |
| Management over MQTT | Driving it through your broker |
| The state object | What the gateway reports |
| Commands | Every action it accepts |
| Capturing commands | Finding undocumented messages |
Repeater networks
Section titled “Repeater networks”In a repeater network, only the Main gateway is configured for Modbus and OPC UA, and it is where the MQTT broker connection is configured. Subordinate gateways forward their data to the Main gateway, which serves it.
Where configuration happens
Section titled “Where configuration happens”These protocols are configured in the Gateway Admin Console, not through an API. Sensor-side settings can be changed either from the console, through the Management API, or through the PHANTOM® Manager app.