Novus DIGIRAIL OEE User manual

NOVUS AUTOMATION 1/33
DIGIRAIL OEE
USER GUIDE V1.0x D

NOVUS AUTOMATION 2/33
1SAFETY ALERTS ..................................................................................................................................................................................................3
2PRESENTATION....................................................................................................................................................................................................4
3IDENTIFICATION ...................................................................................................................................................................................................5
3.1 DEVICE OVERVIEW .....................................................................................................................................................................................5
3.2 DEVICE IDENTIFICATION............................................................................................................................................................................5
3.3 DEVICE MODEL............................................................................................................................................................................................5
4INSTALLATION .....................................................................................................................................................................................................6
4.1 MECHANICAL INSTALLATION..................................................................................................................................................................... 6
4.1.1 DIMENSION.......................................................................................................................................................................................... 7
4.2 ELECTRICAL INSTALLATION ...................................................................................................................................................................... 8
4.2.1 POWER SUPPLY .................................................................................................................................................................................8
4.2.2 DIGITAL INPUT ....................................................................................................................................................................................9
4.2.3 ANALOG INPUT ...................................................................................................................................................................................9
4.2.4 DIGITAL OUTPUT .............................................................................................................................................................................. 10
4.3 LED INDICATORS.......................................................................................................................................................................................10
5COMMUNICATION INTERFACES ...................................................................................................................................................................... 11
5.1 USB INTERFACE ........................................................................................................................................................................................ 11
5.2 RS485 INTERFACE..................................................................................................................................................................................... 11
5.3 ETHERNET INTERFACE ............................................................................................................................................................................ 12
5.4 WI-FI INTERFACE....................................................................................................................................................................................... 12
6MQTT PROTOCOL ..............................................................................................................................................................................................13
6.1 PUBLICATION AND SUBSCRIPTION TOPICS.......................................................................................................................................... 13
6.2 TRANSMISSION MODEL FOR DATA AND EVENTS ................................................................................................................................ 13
6.2.1 DATA AND EVENTS........................................................................................................................................................................... 13
6.2.2 CHANNEL DATA ................................................................................................................................................................................ 13
6.2.3 EVENTS.............................................................................................................................................................................................. 14
6.3 CONFIGURATION.......................................................................................................................................................................................14
6.3.1 TRANSMITTION MODEL FOR CONFIGURATIONS AND COMMANDS.......................................................................................... 14
6.4 COMMANDS................................................................................................................................................................................................14
6.4.1 OUTPUT ............................................................................................................................................................................................. 15
6.4.2 RESET COUNTERS ........................................................................................................................................................................... 16
6.4.3 GET DIAGNOSTIC ............................................................................................................................................................................. 16
6.4.4 GATEWAY MQTT RS485................................................................................................................................................................... 17
7MODBUS-TCP PROTOCOL................................................................................................................................................................................18
7.1 COMMANDS................................................................................................................................................................................................18
7.2 REGISTERS TABLE.................................................................................................................................................................................... 18
8CONFIGURATION SOFTWARE..........................................................................................................................................................................22
8.1 CONFIGURING DIGIRAIL OEE WITH NXPERIENCE................................................................................................................................ 22
8.1.1 GENERAL INFORMATION................................................................................................................................................................. 22
8.1.2 COMMUNICATION ............................................................................................................................................................................. 23
8.1.3 CHANNELS.........................................................................................................................................................................................27
8.2 DIAGNOSTICS ............................................................................................................................................................................................ 28
8.2.1 INFORMATION ................................................................................................................................................................................... 28
8.2.2 INPUTS ............................................................................................................................................................................................... 29
8.2.3 OUTPUTS...........................................................................................................................................................................................29
8.2.4 CONNECTIVITY ................................................................................................................................................................................. 30
9TECHNICAL SPECIFICATION ............................................................................................................................................................................ 31
9.1 CERTIFICATION .........................................................................................................................................................................................32
10 WARRANTY ....................................................................................................................................................................................................33

NOVUS AUTOMATION 3/33
1SAFETY ALERTS
The symbols below are used in the device and throughout this manual to draw the user’s attention to important information related to device safety
and use.
CAUTION
Read the manual fully before installing, and
operating the device.
CAUTION OR HAZARD
Risk of electric shock.
ATTENTION
Material sensitive to static charge. Check
precautions before handling.
All safety recommendations appearing in this manual must be followed to ensure personal safety and prevent damage to the instrument or system.
If the instrument is used in a manner other than that specified in this manual, the device’s safety protections may not be effective.

NOVUS AUTOMATION 4/33
2PRESENTATION
The DigiRail OEE is the ideal tool to read the sensors that monitor the operation of machines, devices or processes. Among its many applications, this
multi input module allows you to count operation time and downtime and the amount of approved and rejected parts, signal the need for preventive or
corrective maintenance or monitor operating conditions in general.
The device has 6 digital inputs, 2 analog inputs and 2 digital outputs, RS485 interface, USB interface, Wi-Fi or Ethernet communication interface and is
compatible with the main clouds on the market. In addition, it can be integrated with MES, SCADA and ERP systems.
The figure below shows an example of topology for DigiRail OEE:
Topology

NOVUS AUTOMATION 5/33
3IDENTIFICATION
3.1 DEVICE OVERVIEW
Built in ABS+PC and with IP20 protection rating, the DigiRail OEE has high quality housing, three LEDs on its front and a protection cover with
detachable faces to pass the sensors, as shown in the figure below:
Device overview
3.2 DEVICE IDENTIFICATION
The identification of the device model is described on the label attached to the back of the housing. This label also provides information on the
power supply, MAC address and serial number, as shown in the figure below:
DigiRail OEE
3.3 DEVICE MODEL
The DigiRail OEE has two models: DigiRail OEE - WRL and DigiRail OEE - ETH, whose features are described in Table 01:
Digital Input Analog Input Digital
Output
USB
Interface
RS485
Communication
Interface
Ethernet
Communication
Interface
Wireless
Communication
Interface
WRL
6
2
2
1
1
×
1
ETH
6
2
2
1
1
1
×
Table 01 – DigiRail OEE Models

NOVUS AUTOMATION 6/33
4INSTALLATION
4.1 MECHANICAL INSTALLATION
As shown in the figure below, the DigiRail OEE can be installed on DIN 35 mm rail. You must fix it with its back clips:
DIN rail installation
In addition, the device also has two holes to fix it with screws, as shown in the figure below:
Installation with screws
The DigiRail OEE has a removable protection cover to protect its connection terminals. The protection cover has three detachable areas, one at
the bottom and one at each side, so you can easily handle the sensors:
Detachable areas of the protection cover
The protection cover has two pins, located on the sides of the housing, which help you fit it into the device. Once the cover has been installed, you
will need a screwdriver to remove it.

NOVUS AUTOMATION 7/33
4.1.1 DIMENSION
The DigiRail OEE has the following dimensions:
Device dimensions with the protection cover
Device dimensions without the protection cover
The DigiRail OEE protection cover has the following dimensions:
Dimensions of the protection cover

NOVUS AUTOMATION 8/33
4.2 ELECTRICAL INSTALLATION
The DigiRail OEE has three detachable connection terminals for the connection of the external power supply, RS485, digital inputs and outputs
and analog inputs, as shown in the figure below:
Electrical connections
To connect the sensors, you must previously remove the connection terminals from the device and observe the enumeration recorded in the
housing, as shown in the figure of electrical connections above.
The inputs, outputs and communication interfaces of this device are not isolated from the power
supply or from each
other.
INSTALLATION RECOMMENDATIONS:
•Electronic and analog signal drivers must run the plant separately from the output and power leads. If possible, in grounded conduits.
•The power supply for the electronic instruments must come from a proper power grid for instrumentation.
•It is recommended to use RC FILTERS (noise suppressors) in contactor coils, solenoids, etc.
•In control applications, it is essential to consider what can happen when any part of the system fails. The device's internal security features do
not guarantee full protection.
•The electrical connections must be made with the connection terminals marked on the device. Before connecting them, make sure that the
connections have been made correctly.
4.2.1 POWER SUPPLY
The connection for power supply is made at the terminals, according to the figure below. You must use a direct current power supply, with voltage
between 10 and 30 V. You can also use 12 and 24 Vdc power supplies.
Power supply

NOVUS AUTOMATION 9/33
4.2.2 DIGITAL INPUT
The DigiRail OEE has digital input channels that can be configured in “Counting” or “Event” modes. Regardless of the selected function, you must
configure the type of sensor connected to the input: PNP, NPN or Dry Contact. After that, select the edge of the digital signal to generate the count
or event: Rising edge, falling edge or both edges.
Correlation between Sensor Type, Sensor Status and Logical Level
Sensor Type
Sensor Status
Logical Level
PNP
Open
0
Closed
1
NPN Open 1
Closed 0
Dry Contact Open 1
Closed
0
Table 02 – Digital input
The connection to the digital inputs is made at the corresponding terminals, as shown in the figure below:
Digital inputs
4.2.3 ANALOG INPUT
The connection to the analog inputs is made at the corresponding terminals, as shown in the figure below:
Analog inputs

NOVUS AUTOMATION 10/33
4.2.4 DIGITAL OUTPUT
The connection to the digital outputs is made at the corresponding terminals, as shown in the figure below:
Digital outputs
4.3 LED INDICATORS
The DigiRail OEE has three LEDs, located on the front of the device, as shown in the figure below:
LED indicators
The operation and description of each LED are as follows:
NAME SYMBOL STATUS DESCRIPTION
STATUS
Off Device off.
On
Device on.
Flashing
Device in firmware update mode.
WI-FI / ETHERNET
CONNECTION
INDICATOR
On The connection has been established.
Flashing The data is being transmitted.
Off The connection has not been established.
MQTT BROKER
CONNECTION
INDICATOR
On The connection has been established.
Flashing The data is being transmitted.
Off The connection is disabled or failed when initializing.
Table 03 – LED indicators

NOVUS AUTOMATION 11/33
5COMMUNICATION INTERFACES
5.1 USB INTERFACE
The DigiRail OEE has a USB port, located on the side of the housing, to configure and perform the device diagnostic. You must use a USB cable
in the standard micro-USB (not supplied) to connect the device with a desktop or notebook.
During the installation of the NXperience configuration software, the USB port drivers will be automatically installed (see chapter
CONFIGURATION SOFTWARE).
USB cable connection
The USB interface is NOT ISOLATED.
It should be used temporarily to CONFIGURATE the device or to PERFORM THE DIAGNOSTIC of it.
5.2 RS485 INTERFACE
Operating only in Modbus-TCP Gateway mode for Modbus RTU, the RS485 connection interface is located on one of the DigiRail OEE detachable
terminals, as shown in the figure below:
RS485
The RS485 interface can be configured to operate at the following speeds (Baud Rates): 1200, 2400, 4800, 9600, 19200, 38400, 57600 and
115200. Besides, it can be configured to operate with 1 or 2 Stop Bits and in even, odd and none parities. You can configure all these parameters
through the NXperience software (see chapter CONFIGURATION SOFTWARE).
The RS485 interface works only when the DigiRail OEE is powered by an external source. It will not work
when the device is powered by the USB interface only.
The device has an internal 120 ohms terminating resistor for the RS485 interface.
Table 04 shows how to connect the connectors to the RS485 communication interface:
Inverted bidirectional data line. Terminal 11
Bidirectional data line. Terminal 12
Optional connection which improves the communication performance. Terminal 13
Table 04 – RS485 Connections
More details about implementing a network of devices via RS485 can be found in the document “Basic Concepts of RS485 and RS422”, available
at www.novus.com.br.

NOVUS AUTOMATION 12/33
5.3 ETHERNET INTERFACE
The DigiRail OEE - ETH has an Ethernet interface, located next to the device terminals, as shown in the figure below:
Ethernet interface
If the Ethernet interface is enabled and the device is connected to an Ethernet network, the LED , located on the front of the device, will
remain lit. While data is being sent through this interface, this LED will remain on and flashing.
5.4 WI-FI INTERFACE
The DigiRail OEE - WRL has an 802.11 Wi-Fi interface in b/g/n 2.4 GHz standards, operating through an internal antenna.
If the Wi-Fi interface is enabled and the device is connected to a Wi-Fi network, the LED , located on the front of the device, will remain lit.
While data is being sent through this interface, this LED will remain on and flashing.

NOVUS AUTOMATION 13/33
6MQTT PROTOCOL
The DigiRail OEE is compatible with Message Queue Telemetry Transport (MQTT) protocol, which allows publishing data in the cloud, and
supports the following MQTT Brokers: Google Cloud, Microsoft Azure, AWS, NOVUS Cloud and generic MQTT Brokers.
This chapter describes the structure of the data published in the cloud and introduces the structure to send settings to the device.
6.1 PUBLICATION AND SUBSCRIPTION TOPICS
As described below, DigiRail OEE uses five topics for operation:
•Topic to publish periodic data and events: Used to publish data generated on the device, i.e. the logs. There are two types: channel and
events.
•Topic to receive the configuration:Used to receive configuration data. The device subscribes to this topic to receive configuration data. For
each configuration received, a confirmation reply is published in the configuration confirmation topic.
•Topic to confirm the configuration: The device publishes the current configuration in this topic. Every time a configuration is received, the
device publishes a confirmation in this topic. After a configuration is applied to the device, the current configuration is also published in this
topic.
•Topic to receive commands: Used to receive commands. The device subscribes to this topic to receive commands and signals the execution
of a command by publishing in the command confirmation topic.
•Topic to confirm the command: The device publishes the result of commands executed in this topic.
Examples of topics for a generic Broker:
TOPIC
USE
Topic to publish periodic data and events NOVUS/device1/events
Topic to receive the configuration NOVUS/device1/config
Topic to confirm the configuration NOVUS/device1/ack/config
Topic to receive commands
NOVUS/device1/command
Topic to confirm commands
NOVUS/device1/ack/command
Table 05 – Topics for a generic Broker
6.2 TRANSMISSION MODEL FOR DATA AND EVENTS
The publication of events and data generated by the device follows the standard MQTT model and uses a topic defined during configuration.
6.2.1 DATA AND EVENTS
The data will be published in the topic defined for the publication of periodic data and events. The type of data is indicated in the JSON message.
For all data, the timestamps used are in Unix timestamp UTC format (GMT 0).
6.2.2 CHANNEL DATA
The channel data is published periodically, according to the device configuration. The data is in JSON format and has the following key/value sets:
{
"device_id":"device0",
"channels" :{
"timestamp":1585819219,
"chd1_value":0,
"chd2_value":0,
"chd3_value":0,
"chd4_value":0,
"chd5_value":0,
"chd6_value":0,
"ch1_user_range":2,
"ch2_user_range":-19991
}
}
Notes:
•device0 is configurable in the Device ID parameter of the MQTT configuration tab of the NXperience configurator software.
•The timestamp value is the timestamp in Unix UTC format at the time the device reads the channel.
•chdX_value corresponds to the information of the digital channels at the time of timestamp. If the channel is not enabled, it will not appear in
the JSON. If the channel is in “Register” mode, the value will correspond to the logical level of the digital channel at that moment. If the channel
is in “Counting” mode, the value will correspond to the counter value at that time.
•chX_user_range informs the value of the analog input in the range configured by the user and at the time of the timestamp. If the analog
channel is not enabled, it will not appear in the JSON.

NOVUS AUTOMATION 14/33
6.2.3 EVENTS
When the digital channel is configured in “Event” mode and an event occurs, an event type message will be generated, indicating the channel, the
timestamp and the edge where it occurred. The data are in JSON format and have the following key/value sets:
{
"device_id": "device0",
"events":{
"chd1":{
"timestamp":1585819219.685,
"edge":1,
}
}
}
Notes:
•The timestamp value is also in Unix timestamp format in UTC (GMT 0), but the milliseconds of the event have been added as fractional
part.
•Regarding the edge value: “1” means that the event occurred on a rising edge. “0” means that the event occurred on a falling edge.
6.3 CONFIGURATION
Some sets of device configuration can be changed or consulted via MQTT when publishing in the topic to receive device configuration. A
confirmation of this publication is received in the configuration confirmation topic.
The available configuration items for this device type are:
CONFIGURATIOM ITEM DESCRIPTION
rtc RTC (Real Time Clock - device internal clock) configuration.
device
General device configuration.
chdX
Digital channel 'X' configuration (Available:
chd1
,
chd2
,
chd3
,
chd4
,
chd5
and
chd6
).
Periodic counter reset
Configuration of the digital counters reset periodicity.
chX
Configuration of the analog channel 'X' (Available:
ch1
and
ch2
).
eth Configuration of the Ethernet interface (When available).
wifi
Configuration of the Wi-Fi interface (When available).
modbus tcp
Configuration of the Modbus-TCP protocol.
rs485 Configuration of the RS485 interface.
Table 06 – Configuration item
6.3.1 TRANSMITTION MODEL FOR CONFIGURATIONS AND COMMANDS
The basic operating model of the commands and configurations was developed to allow synchronization of the device settings and conditions with
the cloud.
In this model there are two basic concepts:
•Desired properties: These are the conditions and configurations that the backend application can change or query on the device with which it
interacts.
•Reported properties: These are the properties used as a response to receiving Desired properties, where the device reports its
current state or the result of a command.
This message exchange model needs two different topics to work. The first is the topic in which the device is subscribed to receive the Desired
properties. This step, initiated by the application, is called “request ”. The device uses the second topic to publish the Reported
properties after the command or configuration is executed. This step is called “response”.
For details on sending configurations via MQTT to DigiRail OEE, you should refer to the MQTT Protocol document available on the product page
on the NOVUS website.
6.4 COMMANDS
Following the same model of sending settings, the commands must be published in the Topic to receive commands. The type of data is indicated
in the JSON message. The return of the command execution is done through the Topic to confirm the command.
The available commands for DigiRail OEE are:
•Output: Used to obtain or modify the state of the digital outputs.
•Reset counters: Used to apply a reset to the digital counters.
•Get diagnostic: Used to obtain diagnostic data from the device.

NOVUS AUTOMATION 15/33
6.4.1 OUTPUT
This command modifies the status of the device outputs.
FORMAT OF THE OUTPUT COMMAND TO MODIFY THE OUTPUTS STATUS:
{
"timestamp":1585819219,
"desired":{
"output":{
"out1":1,
"out2":1
}
}
}
It is not necessary to publish the statuses that will not be modified.
FORMAT OF THE COMMAND OUTPUT RESPONSE:
{
"device_id": "device0",
"timestamp":1585819219,
"reported":{
"output":{
"error":0,
"out1":1,
"out2":1
}
}
}
Notes:
•The timestamp is the same as the command received (desired).
•The status described in the desired step will only be applied if the execution is done without errors.
•The value shown in the error field is an integer and reports the first error found in the execution of the command, as shown in the error
codes table below:
CODE
DESCRIPTION
Error 0
Success.
Error 1 The structure is correct, but the device has received an out of range parameter.
Error 2 The structure is correct, but the device has received an unknown parameter.
Table 07 – Error codes
There are, however, unanswered error cases from the device, as shown below:
oThe JSON structure was mounted wrong.
oThe structure was mounted right, but some element is missing (timestamp, desired, item).
In case of error, none of the parameters will be accepted and the device will not go into configuration mode
•If the command has failed, the statuses indicated in reported will be the current ones.
This command can also be used to consult the current status of the device outputs when sent with the format provided below.
FORMAT OF THE OUTPUT COMMAND TO OBTAIN THE CURRENT STATUS OF THE OUTPUTS:
{
"timestamp":1585819219,
"desired":{
"output":{}
}
}
THE FORMAT OF THE RESPONSE TO OBTAIN THE STATE OF THE OUTPUTS IS THE SAME FORMAT AS THE RESPONSE TO THE
COMMAND TO MODIFY THEM:
{
"device_id": "device0",
"timestamp":1585819219,
"reported":{
"output":{
"error":0,
"out1":1,
"out2":1

NOVUS AUTOMATION 16/33
}
}
}
6.4.2 RESET COUNTERS
The reset counters command is used so that the application can reset the digital channels counters. A digital channel needs to have MQTT
enabled for it to be restarted through this interface.
The structure used for this command follows the same model as for sending configurations, using the concepts of “desired” and “reported”.
The reset_chdX value can assume values of 0 or 1. The value of “1” indicates that a reset is to be applied to the counter of the corresponding
digital channel. The value “0” indicates that the counter should not be changed. In this case, it is also possible to simply omit the JSON channel.
REQUEST RESET COUNTERS:
{
"timestamp":1585819219,
"desired":{
"reset_counters" :{
"reset_chd2":1,
"reset_chd4":1
}
}
}
RESPONSE RESET COUNTERS:
{
"device_id": "device0",
"timestamp":1585819219,
"reported" :{
"reset_counters":{
"error":0,
"reset_chd1":0,
"reset_chd2":0,
"reset_chd3":0,
"reset_chd4":0,
"reset_chd5":0,
"reset_chd6":0
}
}
}
Notes:
•The timestamp is the same as the command received (desired).
•The status described in the desired step will only be applied if the execution is done without errors.
•The error value is an integer and reports the error found during the command execution.
•In this example, digital channels 1, 3, 5 and 6 do not appear in JSON desired, since you do not want to reset your counters.
6.4.3 GET DIAGNOSTIC
The get diagnostic command returns diagnostic data from the device.
REQUEST GET DIAGNOSTIC:
{
"timestamp":1585819219,
"desired" :{
"diag" :{}
}
}
RESPONSE GET DIAGNOSTIC:
{
"device_id": "device0",
"timestamp":1585819219,
"reported" :{
"diag":{
"title":"Pci v2",
"location":"home",
"curr_timestamp":1589326517,

NOVUS AUTOMATION 17/33
"cfg_timestamp":1589311676,
"fw_v":"01.23",
"mqtt_queue":1,
"sn":"00000001",
"rssi":"90",
"ipv4":[192,168,0,23 ]
}
}
}
Notes:
•The title and location fields are defined in the general configuration frame of the configurator software.
•The curr_timestamp field presents the current timestamp of the device, i.e., obtained from its internal clock and is in Unix timestamp UTC
format.
•The cfg_timestamp field presents the timestamp of the last configuration applied to the device and is also in Unix timestamp UTC format.
•The fw_v field presents the firmware version of the device.
•The mqtt_queue field presents the number of logs pending sending via MQTT.
•The sn field presents the serial number of the device.
•The rssi field informs the Wi-Fi signal quality. It is displayed in percent. Thus, the higher the value, the better the signal.
•The ipv4 field informs the IP of the device on the network.
6.4.4 GATEWAY MQTT RS485
Sending packets through the RS485 serial interface via MQTT allows you to read data from a local network (Modbus RTU, for example) and send
commands remotely via the MQTT protocol. In this case, DigiRail OEE operates as a Gateway, communicating with the slave devices through the
RS485 serial interface.
To send commands remotely, it is necessary to connect another MQTT client to the Broker to which the DigiRail OEE is connected and, in the
sequence, register in the topic configured for command confirmation. The command must then be published in the topic configured in DigiRail OEE
to receive commands.
Modbus RTU commands can be published in hexadecimal format with the following structure:
{
"timestamp":XXXXXX,
"desired":{
"gateway_485":{"mb_buffer":"bytes in hexadecimal to transmit through serial 485"}
}
}
Below is an example of a message to be published in the command sending topic:
{
"timestamp":15,
"desired":{
"gateway_485":{"mb_buffer":"02 03 00 00 00 0A C5 FE"}
}
}
In sequence, the response received through the RS485 serial interface will be published by DigiRail OEE in the topic assigned to the commands
confirmation, following the format:
{
"device_id":XX,
"timestamp":XXXX,
"reported":{
"gateway_485":{"error":0; "mb_buffer":"bytes received in response to the command sent"}
}
}
An example message that could be received in the command confirmation topic:
{
"device_id":"DeviceName",
"timestamp":15,
"reported":{
"gateway_485":{"error":0; "mb_buffer":"00 03 14 19 C7 00 00 06 4E 00 00 04 E0 00 00 03 D
0 00 00 03 D0 00 00 1B 13"}
}
}

NOVUS AUTOMATION 18/33
7MODBUS-TCP PROTOCOL
The DigiRail OEE is compatible with Modbus-TCP protocol, the data communication protocol used to connect the device to supervisory control and
data acquisition systems (SCADA). It supports up to 3 simultaneous connections, allowing up to 3 Modbus-TCP masters to monitor it at the same
time.
7.1 COMMANDS
READ HOLDING REGISTERS – 0x03:
This command can be used to read the value of one or up to a maximum of 125 consecutive registers, according to Table 08.
WRITE HOLDING REGISTERS – 0x06:
This command can be used to write in a register, according to Table 08.
WRITE MULTIPLE HOLDING REGISTERS – 0x16:
This command can be used to write in multiple registers, according to Table 08.
7.2 REGISTERS TABLE
Below is the table of registers supported by the device:
ADDRESS REGISTER DESCRIPTION
1 HR_PRODUCT_CODE
Product code.
2
HR_SERIAL_NUMBER_H
Serial number (32bits).
3 HR_SERIAL_NUMBER_L
4
HR_FIRMWARE_VERSION
Version firmware x 100.
Reserved.
6 HR_MAC_ADDR_0_1 MAC Address. Hexadecimal format with 2 digits per register.
0 : 1 : 2 : 3 : 4 : 5
7 HR_MAC_ADDR_2_3
8
HR_MAC_ADDR_4_5
Reserved.
10 HR_USB_STATUS USB interface status:
0 Disconnected;
1 Connected.
Reserved.
13 HR_NUMBER_OF_ACTIVE_CH Number of enabled analog channels.
14 HR_NUMBER_OF_ACTIVE_CHD Number of enabled digital channels.
15
HR_RESET_COUNTERS
Reset of digital channel counters.
Note: Write 1 resets all the digital counters that are configured to be reset
by Modbus-TCP and MQTT.
Reserved.
17 HR_STATUS_OF_RECORDS Number of registers pending sending via MQTT protocol.
Reserved.
20 HR_LAST_CONFIG_YEAR, Year of last configuration.
21 HR_LAST_CONFIG_MONTH, Month of last configuration.
22
HR_LAST_CONFIG_DAY,
Day of last configuration.
23 HR_LAST_CONFIG_HOUR, Hour of last configuration.
24
HR_LAST_CONFIG_MINUTE,
Minute of last configuration.
25 HR_LAST_CONFIG_SECOND Second of last configuration.
26 HR_CURRENT_YEAR Current year.
27 HR_CURRENT_MONTH Current month.
28
HR_CURRENT_DAY
Current day.
29 HR_CURRENT_HOUR Current hour.
30
HR_CURRENT_MINUTE
Current minute.
31 HR_CURRENT_SECOND Current second.
Reserved.

NOVUS AUTOMATION 19/33
ADDRESS
REGISTER
DESCRIPTION
34 HR_RESET_COUNTER_CHD1 Resets the digital channel counter 1.
Note: Write 1 resets the counter for this channel, if it is configured to allow
reset via Modbus-TCP and MQTT protocols.
35
HR_RESET_COUNTER_CHD2
Resets the digital channel counter 2.
Note: Write 1 resets the counter for this channel, if it is configured to allow
reset via Modbus-TCP and MQTT protocols.
36 HR_RESET_COUNTER_CHD3 Resets the digital channel counter 3.
Note: Write 1 resets the counter for this channel, if it is configured to allow
reset via Modbus-TCP and MQTT protocols.
37 HR_RESET_COUNTER_CHD4 Resets the digital channel counter 4.
Note: Write 1 resets the counter for this channel, if it is configured to allow
reset via Modbus-TCP and MQTT protocols.
38 HR_RESET_COUNTER_CHD5 Resets the digital channel counter 5.
Note: Write 1 resets the counter for this channel, if it is configured to allow
reset via Modbus-TCP and MQTT protocols.
39
HR_RESET_COUNTER_CHD6
Resets the digital channel counter 6.
Note: Write 1 resets the counter for this channel, if it is configured to allow
reset via Modbus-TCP and MQTT protocols.
Reserved.
41
HR_DIGITAL_OUT1_VALUE
Digital output status and control (on = 1/off = 0).
Allows the output reading and writing.
42 HR_DIGITAL_OUT2_VALUE Digital output status and control (on = 1/off = 0).
Allows the output reading and writing.
Reserved.
45 HR_CHD1_STATUS Digital channel status:
NOT_CONFIGURED 0;
OK 1;
CONFIG_ERROR 2.
46
HR_CHD1_VALUE_HIGH
Counting mode: Counter value in 32-bit.
Event mode: Logical input level.
47 HR_CHD1_VALUE_LOW
48 HR_CHD1_TIME_STAMP_LAST_HIGH Last event timestamp. 32-bit. Unix format.
49 HR_CHD1_TIME_STAMP_LAST_LOW
Reserved.
56 HR_CHD2_STATUS Digital channel status:
NOT_CONFIGURED 0;
OK 1;
CONFIG_ERROR 2.
57 HR_CHD2_VALUE_HIGH Counting mode: Counter value in 32-bit.
Event mode: Logical input level.
58
HR_CHD2_VALUE_LOW
59 HR_CHD2_TIME_STAMP_LAST_HIGH Last event timestamp. 32-bit. Unix format.
60
HR_CHD2_TIME_STAMP_LAST_LOW
Reserved.
67
HR_CHD3_STATUS
Digital channel status:
NOT_CONFIGURED 0;
OK 1;
CONFIG_ERROR 2.
68
HR_CHD3_VALUE_HIGH
Counting mode: Counter value in 32-bit.
Event mode: Logical input level.
69 HR_CHD3_VALUE_LOW
70 HR_CHD3_TIME_STAMP_LAST_HIGH Last event timestamp. 32-bit. Unix format.
71 HR_CHD3_TIME_STAMP_LAST_LOW

NOVUS AUTOMATION 20/33
ADDRESS
REGISTER
DESCRIPTION
Reserved.
78
HR_CHD4_STATUS
Digital channel status:
NOT_CONFIGURED 0;
OK 1;
CONFIG_ERROR 2.
79 HR_CHD4_VALUE_HIGH Counting mode: Counter value in 32-bit.
Event mode: Logical input level.
80
HR_CHD4_VALUE_LOW
81 HR_CHD4_TIME_STAMP_LAST_HIGH Last event timestamp. 32-bit. Unix format.
82
HR_CHD4_TIME_STAMP_LAST_LOW
Reserved.
89 HR_CHD5_STATUS Digital channel status:
NOT_CONFIGURED 0;
OK 1;
CONFIG_ERROR 2.
90
HR_CHD5_VALUE_HIGH
Counting mode: Counter value in 32-bit.
Event mode: Logical input level.
91 HR_CHD5_VALUE_LOW
92
HR_CHD5_TIME_STAMP_LAST_HIGH
Last event timestamp. 32-bit. Unix format.
93 HR_CHD5_TIME_STAMP_LAST_LOW
Reserved.
100 HR_CHD6_STATUS Digital channel status:
NOT_CONFIGURED 0;
OK 1;
CONFIG_ERROR 2.
101 HR_CHD6_VALUE_HIGH Counting mode: Counter value in 32-bit.
Event mode: Logical input level.
102 HR_CHD6_VALUE_LOW
103 HR_CHD6_TIME_STAMP_LAST_HIGH Last event timestamp. 32-bit. Unix format.
104 HR_CHD6_TIME_STAMP_LAST_LOW
Reserved.
109 HR_CH1_STATUS Analog channel 1 status:
NOT_CONFIGURED 0;
OK 1;
CONFIG_ERROR 2.
Reserved.
111
HR_CH1_MV_MA_VALUE_H
Value in the unit of measurement (mA or V). Float 32-bit format.
112 HR_CH1_MV_MA_VALUE_L
113
HR_CH1_SENSE_USER_RANGE_H
Value in user range. Float 32-bit format.
Note: This is the same value as the cloud publication.
114 HR_CH1_SENSE_USER_RANGE_L
120 HR_CH2_STATUS Analog channel 2 status:
NOT_CONFIGURED 0;
OK 1;
CONFIG_ERROR 2.
Reserved.
122
HR_CH2_MV_MA_VALUE_H
Value in the unit of measurement (mA or V). Float 32-bit format.
123 HR_CH2_MV_MA_VALUE_L
124
HR_CH2_SENSE_USER_RANGE_H
Value in user range. Float 32-bit format.
Note: This is the same value as the cloud publication.
125 HR_CH2_SENSE_USER_RANGE_L
Reserved.
130 HR_MQTT_LAST_UPDATE_YEAR Year of last sending to the MQTT Broker.
131
HR_MQTT_LAST_UPDATE_MONTH
Month of the last sending to the MQTT Broker.
132 HR_MQTT_LAST_UPDATE_DAY Day of the last sending to the MQTT Broker.