The Device Detail View is the command center for monitoring a single asset. Unlike static configuration pages, this view connects directly to the Edge Gateway to stream real-time telemetry, health metrics, and status updates. For configuration history, you can also check the Audit Logs.
Header Controls
At the top of the interface, you manage the device's operational state:
- Active Checkbox: Starts or stops data collection. Changes are deployed instantly to the Gateway.
- Auto Refresh: Toggles the UI update interval (Default: 5s). Pause this when inspecting specific data rows.
- Current Status: A live indicator of the connection health.
- 🟢 Connected: Normal operation.
- 🛌 Sleep Mode: Device is active but outside of scheduled operating hours.
- ⚠️ Error: Connection issues or timeout. See System Logs for technical details.
- 🌐 Gateway Offline: The parent Edge Gateway is unreachable.
Overriding Connection Parameters
While Device Profiles define default settings (like standard ports or timeouts), specific devices on the factory floor may require unique configurations (e.g., a PLC on a different IP or a specific Station ID).
To override these settings:
- Click the Override Connection Parameters button in the header.
- A popup will appear showing all available parameters for the selected protocol.
- Modify the necessary fields (e.g.,
Host,Port,Station). - Click Save.
Saving overrides will trigger an immediate restart of the protocol driver on the Edge Gateway to apply the new settings.
Data Metrics
The Data Metrics tab provides a health check of the physical connection. It aggregates counters from the protocol driver.
| Metric | Description |
|---|---|
| Data Freshness | Percentage of successful reads in the last window. Should be near 100%. |
| Response Time | Average round-trip time (RTT) to the PLC/Device. |
| Success/Failed Ops | Total count of read/write operations since the last reset. |
| Sleep Mode Transitions | How many times the device entered power-saving mode. |
Latest Values
This tab shows the most recent value for every tag defined in the Device Profile. It is a "snapshot" of the machine's current state, cached in the Central Server's memory.
Update Mechanism
Data updates follow a two-tier process:
- Edge to Central: The Edge Gateway transmits telemetry and metrics based on configured intervals. By default, metrics are sent every 10 seconds.
- UI Polling: The browser fetches these values from the Central Server based on the Auto Refresh setting (Default: 5s).
For sub-second changes, use the Device Data tab, which provides a granular stream of incoming packets rather than a polling-based snapshot.
Configuration Settings
The following settings in Proxus-config.toml control the behavior of this view:
| Setting | Default | Description |
|---|---|---|
DeviceDataTimeRange | 1h | The time window of historical data kept in the UI cache. |
MaxDeviceDataLoad | 1000 | Maximum number of data points loaded per request. |
DeviceMetricsTransmissionInterval | 10s | How often the Edge sends health and performance metrics. |
For a complete list of all system settings, see the Configuration Reference.
To ensure platform stability, internal UNS updates are throttled at 500ms per metric. This prevents UI lockups during massive high-frequency data bursts.
Device Data (History)
The Device Data tab displays the raw packet stream coming from the device. It is useful for debugging protocol issues or verifying that data is being ingested correctly.
- Incoming: The raw value received from the device.
- Timestamp: The exact time (UTC) the data was timestamped at the Edge.
Targets
Manage where the data flows. By default, every device writes to the System Internal DB (ClickHouse). You can add external Targets like AWS IoT, Kafka, or MQTT Brokers here.
Transport Strategy
Each target has a Transport Strategy that controls how data is forwarded:
- Pass Through: Sends every data point to the target (best for full fidelity storage).
- On Change: Sends only values that changed (reduces bandwidth for high-frequency tags).
Choose the strategy per target based on bandwidth and storage requirements.
ISA-95 Hierarchy
This tab defines where this device fits in your organizational model.
- Enterprise: The top-level organization.
- Site: Physical location (e.g., "New York Plant").
- Area: Production area (e.g., "Assembly Line A").
- Process Cell: Logical grouping (e.g., "Welding Station").
Setting these values allows for hierarchical filtering in Dashboards and UNS (Unified Namespace) Topic Generation.