Industrial gateway integration
For industrial gateway integration, define the source signals, acquisition rate, record-retention requirement and destination system before selecting the communication and storage architecture.
NOVUS · Data Logging, Remote I/O & IIoT
DigiRail IoT
Industrial IoT gateway/I/O module that bridges field signals and Modbus data to MQTT-enabled local or cloud systems.
Roleindustrial IoT gateway
CategoryData Acquisition & Communication
IntegrationModel-specific
SupportPrimionics application engineering
Engineering position
Industrial IoT gateway for the industrial data layer
The product belongs to the acquisition and information layer: it records, converts, exchanges or publishes process and machine data. Deterministic machine or process control remains in the controller; logging, remote I/O and IIoT functions should be designed as a separate information path. Industrial IoT gateway/I/O module that bridges field signals and Modbus data to MQTT-enabled local or cloud systems.
Field-data integrationDefine field signals, channel count, acquisition purpose and the receiving PLC/SCADA/MES/cloud system.
Commissioning and diagnosticsProvide software access, network settings, firmware baseline and a repeatable commissioning procedure.
Documented protocol operationConfirm protocol role, addressing, network topology, security and data ownership for the selected model.
Current product position: Current DigiRail IoT positioning is an industrial IoT gateway with digital/analogue I/O, Modbus connectivity and MQTT integration to local or cloud systems.
System role
DigiRail IoT signal and system architecture
The architecture separates the field/process interface, the NOVUS function and the downstream control or information path. Exact electrical interfaces, protocol roles and accessories remain model-dependent.
01Sensors / Modbus devices
02DigiRail IoT
03I/O + protocol gateway
04MQTT / Modbus TCP
05Cloud / SCADA / analytics
Use the current NOVUS product page, manual and exact order code as the final authority for numeric ratings, approvals, firmware-dependent functions and supplied accessories.
Application scope
DigiRail IoT application environments
These application classes indicate the engineering context. Final selection still depends on the exact range, I/O, communication, installation and performance requirements.
SCADA and IIoT connection
For scada and iiot connection, define the source signals, acquisition rate, record-retention requirement and destination system before selecting the communication and storage architecture.
Remote process monitoring
For remote process monitoring, define the source signals, acquisition rate, record-retention requirement and destination system before selecting the communication and storage architecture.
Technical data
Technical data and model boundaries
The table is a selection summary, not a substitute for the current NOVUS manual or ordering information. Product families and optional versions can differ in input, output, communication, supply and approvals.
| Inputs | 6 digital and 2 analogue |
|---|---|
| Outputs | 2 digital |
| Interfaces | USB, RS485 and Wi-Fi or Ethernet by model |
| Protocols | MQTT, Modbus TCP and Modbus RTU |
| Cloud / IT integration | Supports connection to local or cloud systems through documented MQTT integrations |
| Configuration | NXperience |
| Supply | 10–30 Vdc |
Selection context
DigiRail IoT within the NOVUS portfolio
Use role, range, I/O, installation and communication requirements to distinguish nearby products. Similar naming does not imply interchangeable electrical or functional capability.
Current page
DigiRail IoT
Industrial IoT gateway/I/O module that bridges field signals and Modbus data to MQTT-enabled local or cloud systems.
Inputs: 6 digital and 2 analogueMachine-data I/O module for OEE and MESDigiRail OEE
Machine-data I/O module for capturing counts, states and analogue variables for OEE, MES and IoT analytics.
Inputs: 6 digital and 2 analogueEthernet and RS485 remote I/O moduleDigiRail Connect
Distributed mixed-signal remote I/O for extending PLC/SCADA systems over Modbus TCP or Modbus RTU.
Role: Distributed mixed-signal I/O extensionSelection basis: application duty, exact interface requirements and current orderable configuration.
Documentation & engineering inputs
Current NOVUS documentation and application data
Use the manufacturer page for the current orderable configuration, then provide the application information below so Primionics can review technical fit, accessories and commercial scope.
Signals & channelsAnalogue/digital signals, Modbus devices, pulse/event inputs and channel count.
AcquisitionSampling/recording interval, event triggers, buffering and record-retention requirement.
ConnectivityRS485, Ethernet, Wi-Fi, MQTT, Modbus TCP/RTU and receiving system.
IT/OT boundaryIP addressing, broker/cloud ownership, certificates, remote access and cybersecurity rules.
Software & validationNXperience, SCADA/MES/cloud integration, reports and validation requirements.
Commercial scopeQuantity, accessories, storage/media, software and commissioning support.