Atrium IIoT Gateway
The central hub for managing, monitoring, and automating your NCD industrial IoT sensors. This guide walks through every section of the Atrium web interface.
Overview
The Atrium IIoT Gateway is a platform-level guide. It does not cover sensor-specific setup or configuration — for individual sensor guides, refer to the documentation for your specific product.
Audience: Engineers, maintenance professionals, and integrators deploying or operating NCD sensors through the Atrium Gateway.
Detect, configure, and monitor every NCD wireless sensor from a single interface.
Build monitor dashboards with gauges and line graphs for the metrics that matter most.
Set threshold triggers and automate email notifications or relay actions.
Schedule automated reports and export data as CSV for offline analysis.
Prerequisites
Before using this guide, ensure you have the following.
- An NCD Atrium IIoT Gateway, powered on and connected to your local network (Ethernet or Wi-Fi)
- At least one NCD wireless sensor powered on and within range of the gateway’s DigiMesh radio
- A computer or mobile device on the same network as the gateway
- A modern web browser (Chrome, Firefox, Edge, or Safari)
Accessing the Gateway
Open a web browser and navigate to your gateway’s local address:
Replace XXXX with the last four characters of the gateway’s MAC address (printed on the enclosure label). For example, if the MAC ends in D8FC, navigate to http://ncd-d8fc.local.
http://192.168.1.100). Check your router’s DHCP client list to find it.When prompted, log in with your credentials. The default username is ncdio. If you haven’t changed the default password, refer to the credentials card shipped with your gateway.
01 First-Time Setup
When you access a new Atrium Gateway for the first time, a Setup Wizard overlay appears. This guided walkthrough takes approximately two minutes.
Assign a recognizable name to this gateway (e.g., “Plant Floor Gateway” or “Building A”).
Select your local timezone. All timestamps on sensor readings, alerts, and reports will reflect this.
Choose Celsius or Fahrenheit for all temperature displays across the platform.
Set how many days of sensor data to keep on the gateway. The default is 100 days. Longer retention requires more storage.
Verify the gateway’s network connection and DigiMesh radio status. Once complete, the gateway begins listening for nearby sensors.
02 Sensors Page
The Sensors page is the home screen of the Atrium Gateway. It shows every sensor the gateway has detected, along with key status information at a glance.
Sensor List Columns
| Column | Description |
|---|---|
| Status | Health indicator — ● Healthy ● Warning ● Offline |
| Device ID | The sensor’s unique hardware address |
| Type | Sensor type number and description |
| Sensor Name | User-assigned friendly name |
| Location | User-assigned location label |
| Asset | User-assigned equipment label |
| Last Seen | Timestamp of most recent data transmission |
| Battery | Battery percentage (where applicable) |
| RSSI | Wireless signal strength |
| Alerts | Active alert indicator |
Filtering & Search
Use the filter controls at the top of the sensor list to narrow the view:
- Filter by Sensor Type — Show only sensors of a specific type
- Filter by Location — Show sensors assigned to a specific location
- Search — Enter a device ID, sensor name, location, or asset name
- Hide Inactive Sensors — Toggle to hide sensors that haven’t reported in 7+ days
New Sensor Detection
When the gateway detects a new sensor, it appears in a “New Sensors Detected” notification. New sensors are not automatically whitelisted — you must explicitly add them to begin logging their data.
03 Sensor Dashboard
Click on any sensor in the sensor list to open its dashboard — the primary view for inspecting a single sensor’s data over time.
Data View
The dashboard displays all metrics reported by the sensor as time-series charts. The specific metrics vary by sensor type.
Choose preset ranges (Last Hour to Last 30 Days) or specify a custom date/time range.
Download displayed data as CSV for offline analysis or import into other systems.
Create a threshold-based alert for any metric displayed on this sensor.
Vibration sensors with FFT support show frequency-domain analysis for predictive maintenance.
04 Sensor Configuration
From any Sensor Dashboard, click Configure to open the Sensor Configuration page. It’s organized into three tabs.
Tab 1: Sensor Meta
The Sensor Meta tab manages the sensor’s identity and basic operational settings.
| Setting | Description |
|---|---|
| Status | Toggle between Whitelisted (active) and Blacklisted (inactive — data is ignored) |
| Sensor Name | Human-readable name (e.g., “Compressor #3 Vibration”) |
| Asset | Associate with a specific piece of equipment |
| Location | Physical location label (e.g., “Shop Floor – Bay 1”) |
| Report Interval | Interval at which Atrium should expect to hear from sensor |
| Offline Alert | Receive email notification if the sensor stops reporting |
Tab 2: Metrics
Per-metric configuration for every data point the sensor reports. For each metric you can set a Custom Label, apply a Conversion Formula, set display Units, and control Visibility.
Tab 3: Sensor Configuration
Modify settings pushed directly to the sensor’s firmware on its next check-in. Available settings vary by sensor type but commonly include network settings, sampling parameters, alert thresholds, and filter settings.
05 Monitor Dashboard
A customizable, at-a-glance view of the metrics that matter most. Build a single dashboard with widgets pulling data from any sensor.
Widget Types
When you click + Add Widget, the Widget Type dropdown offers nine visualizations. Pick the one that best matches how you want to read the data at a glance.
Time-series chart showing how one or more metrics change over the selected time period. Best general-purpose trend view.
Line graph with the area below the curve shaded. Useful when magnitude — not just shape — matters.
Discrete bars for comparing values across time buckets or sensors. Good for counts, totals, and period-over-period comparisons.
Circular dial showing the current value against a configurable min/max range. Ideal for instantaneous readings with a clear safe/warn band.
Large numeric readout of a single metric’s current value, with optional label and units. Great for KPI-style at-a-glance displays.
Summary card showing min, max, and average for a metric across the selected time range.
Compact, minimal-chrome time-series line designed to fit into tight dashboard layouts alongside many other widgets.
Tabular listing of raw metric values with timestamps. Best for data inspection, audits, and spot-checking readings.
Vertical fill indicator designed for tank, silo, reservoir, or container level visualization.
Managing Widgets
- Add Widget — Select sensor, metric, and widget type, then configure width, height, and optional title
- Edit — Modify an existing widget’s sensor, metric, type, or display settings
- Delete — Remove a widget from the dashboard
- Fullscreen — Expand the entire Monitor page to fill the browser, hiding the top navigation chrome
- Tidy Up — Automatically arrange widgets in an even grid layout
- Synthetics — Open the synthetic variable editor to define computed metrics derived from real sensor data
Synthetic Variables
Computed metrics derived from formulas applied to real sensor data. Useful for derived calculations such as heat index, energy consumption estimates, or multi-sensor unit conversions.
06 Gateway Health
The operational status of the gateway hardware itself — identity, connections, storage, CPU, and RAM.
| Metric | What It Shows |
|---|---|
| Gateway Identity | Name, firmware version, MAC address, network config |
| Cloudflare Tunnel | Remote access status — Connected or Disconnected |
| DigiMesh Radio | Whether the wireless mesh network module is connected |
| Storage Usage | Internal storage consumption progress bar |
| CPU Usage | Current utilization with time-series chart |
| RAM Usage | Current memory utilization with time-series chart |
https://<gateway-ip>:8443. The Gateway Health page shows application-level usage, which may show momentary spikes that don’t reflect sustained load.07 Alerts & Automations
Define conditions that trigger notifications and actions when sensor data crosses your thresholds.
Global Alert Templates
Apply a single alert rule across multiple sensors at once. Define a template and apply it to all sensors matching a specific type, location, or asset grouping.
Creating a Trigger
Go to the Alerts page and select the Triggers section.
Click Create Trigger, select the sensor, metric, condition (greater than, less than, equal to), and threshold value.
Save the trigger. It enters ARMED state, waiting for the condition to be met.
Automations
An Automation connects a Trigger to an Action. When the trigger fires, the automation executes the linked action.
Send notification emails to one or more recipients. Requires SMTP configured in Settings.
Send a command to an NCD Relay Controller — turn on a fan when temperature exceeds a threshold.
08 Output Devices
Manage NCD relay controllers and other output hardware connected to the gateway for physical responses to sensor conditions.
Each output device displays its device name, device type (e.g., “EndNode 4-Channel Relay Controller”), and channel status for each relay channel.
- Edit — Modify the device name or configuration
- Delete — Remove the output device from the gateway
- Test — Manually toggle a relay channel to verify the hardware connection during installation
To trigger a relay automatically, create a Trigger and Automation in Section 07: Alerts & Automations.
09 Settings
The gateway’s central configuration hub — gateway settings, email, MQTT, sensor management, user accounts, and the SQL console.
Gateway Settings
| Setting | Description |
|---|---|
| Gateway Name | Name displayed in header, reports, and alerts |
| Timezone | Local timezone for all timestamps |
| Temperature Unit | Celsius or Fahrenheit, applied globally |
| Data Retention | Days to keep sensor data (older data auto-purges) |
| Remote Access | Enable/disable access via Cloudflare Tunnel |
| Firmware Update | Check for and apply firmware updates |
MQTT Client
Publish sensor data to an external MQTT broker for integration with SCADA systems, cloud IoT platforms (AWS IoT, Azure IoT Hub), or custom solutions.
| Field | Description |
|---|---|
| Broker Host | Hostname or IP address of your MQTT broker |
| Broker Port | Typically 1883 (unencrypted) or 8883 (TLS) |
| Username / Password | Authentication credentials |
| TLS | Toggle for encrypted communication |
| Topic Patterns | MQTT topic structure with dynamic sensor variables |
SQL Query Console
At the bottom of Settings, click Open SQL Query Console for direct SQL queries against the gateway’s SQLite database. Intended for advanced users needing custom data extraction or investigation.
10 Reports
Scheduled email reports that are automatically generated and sent on a recurring basis.
Overview of all sensors — health status, battery levels, and recent activity.
Focused report on a specific group filtered by type, location, or asset.
Summary of all alert events that occurred during the reporting period.
Creating a Report
Go to the Reports page and click Create Report.
Select report type, choose which sensors to include, set the reporting period and recipients.
Set the schedule (daily, weekly) and delivery time, then save.
11 Apps
Specialized applications built on top of the Atrium platform for specific operational needs.
Productivity Monitor
Tracks machine runtime against shift-based production quotas. Provides visibility into whether equipment is running as expected and highlights downtime events.
Additional applications are under active development and will be available in future firmware updates.
Troubleshooting
Common issues and their solutions.
Sensor Not Appearing in the Sensor List
- Check power — Confirm the sensor is powered on and LED indicators show normal operation
- Check range — Move the sensor closer to rule out wireless range issues
- Check New Sensors list — New sensors must be manually whitelisted before appearing in the main list
- Check Inactive toggle — If “Hide Inactive Sensors” is enabled, sensors that haven’t reported in 7+ days are hidden
Sensor Showing as Offline
- Battery — Check last reported battery level; it may have died
- Report interval — Sensors with long intervals may appear offline between check-ins
- Wireless interference — Nearby equipment or metal enclosures can interfere with DigiMesh
- Sensor status — Verify the sensor is whitelisted (not blacklisted)
Email Alerts Not Sending
- SMTP configuration — Verify server, port, username, and password in Settings
- Firewall — Ensure the gateway can reach the SMTP server on ports 25, 465, or 587
- From address — Some SMTP servers reject messages if the “From” address isn’t authorized
Monitor Dashboard Widgets Showing No Data
- Time range — Ensure the selected range includes the period when data was collected
- Sensor status — Confirm the linked sensor is whitelisted and actively reporting
- Metric visibility — Check that the metric isn’t hidden on the Metrics configuration tab