The NumberOk system supports executive control modules with the Modbus protocol. 

To connect make the next steps :

1. select from the drop-down list of the manufacturer (model): ICP DAS, Barix AG, Adam 6050 SE, Custom;

2. enter the IP address;

3. enter the device port;

4. enter ModBus identifier "Network ID" assigned to the device at its native settings;

5. click the "Add" button.

For some executive devices, you need to enter a login and password.

Required fields:

• IP address 

• Port

• Login 

• Password

 The main characteristics:

• Connection time   <30 s

• Reconnection time about 3-4 min (if connection was lost ) 

• Triggering time  <1 s

Tested on the  cameras 

• Uniview IPC2324EBR-DP

•  AXIS  - P1447,P1445,P1368

• Hanwha XNO-6020

How it works:

NumberOk connect to the IP camera by ONVIF protocol  to the IP camera, Camera  return available output  numbers, and NumberOk add them to the list of relays

Some tricks:

• Uniview cameras can forget about the inputs/outputs configuration after a power loss.

• Axis cameras have individual users for ONVIF:

To investigate any connectivity issues using ONVIF protocol. Please do the following steps:

• Close NumberOk 

• Open Ini file (C:\ProgramData\FF\NumberOk3)

• Set  - log level - 0x400 

• 

• Save and close ini file 

• Start NumberOk 

• Open log file ((C:\ProgramData\FF\NumberOk3)

13.05.2019 10:10:35.825: ONVIF: 10.0.3.167:80, Type 1, UTCDateTime 2019.05:13 07:05:49

13.05.2019 10:10:35.825: ONVIF: 10.0.3.167:80, Type 1, LocalDateTime 2019.05:13 10:05:49

13.05.2019 10:11:05.063: ONVIF: 10.0.3.168:80, Type 1, UTCDateTime 2019.05:13 08:06:56

13.05.2019 10:11:05.063: ONVIF: 10.0.3.168:80, Type 1, LocalDateTime 2019.05:13 11:06:56

13.05.2019 10:12:12.180: ONVIF: 10.0.3.84:80, Type 0, UTCDateTime 2019.05:13 07:17:54

13.05.2019 10:12:12.180: ONVIF: 10.0.3.84:80, Type 0, LocalDateTime 2019.05:13 07:17:54

13.05.2019 10:13:26.110: CBarbos2: 10.0.3.83:80: Switch coil 0 to ON: Ok.

13.05.2019 10:13:26.680: CBarbos2: 10.0.3.83:80: Switch coil 0 to OFF: Ok.

13.05.2019 10:13:27.279: CBarbos2: 10.0.3.83:80: Switch coil 0 to ON: Ok.

13.05.2019 10:13:28.691: CBarbos2: 10.0.3.83:80: Switch coil 0 to OFF: Ok.

13.05.2019 10:13:40.600: CBarbos2: 10.0.3.83:80: Switch coil 0 to ON: Ok.

13.05.2019 10:13:41.687: CBarbos2: 10.0.3.83:80: Switch coil 0 to OFF: Ok.

13.05.2019 10:13:41.781: CBarbos2: 10.0.3.83:80: Switch coil 0 to ON: Ok.

13.05.2019 10:13:42.683: CBarbos2: 10.0.3.83:80: Switch coil 0 to OFF: Ok.

13.05.2019 10:13:47.863: ONVIF: 10.0.3.83 switched relay 1 >=  ON, result 28

13.05.2019 10:13:47.863: ModBus 10.0.3.83 : 0, LOST

13.05.2019 10:14:08.864: ONVIF: GetSystemDateAndTime SOAP error 28

13.05.2019 10:14:29.866: ONVIF: GetSystemDateAndTime SOAP error 28

13.05.2019 10:14:50.869: ONVIF: GetSystemDateAndTime SOAP error 28

13.05.2019 10:14:59.875: ONVIF: GetSystemDateAndTime SOAP error 28

13.05.2019 10:15:00.887: ONVIF: GetSystemDateAndTime SOAP error 28

13.05.2019 10:15:01.894: ONVIF: GetSystemDateAndTime SOAP error 28

13.05.2019 10:15:02.900: ONVIF: GetSystemDateAndTime SOAP error 28

13.05.2019 10:15:02.900: ModBus 10.0.3.83 : 0, LOST

13.05.2019 10:18:02.246: ONVIF: 10.0.3.83:80, Type 0, UTCDateTime 2019.05:13 09:26:45

13.05.2019 10:18:02.246: ONVIF: 10.0.3.83:80, Type 0, LocalDateTime 2019.05:13 09:26:45

13.05.2019 10:18:02.660: ModBus 10.0.3.83 : 0, relays: 0

Custom field is intended for connection with Modbus protocol executive devices not listed in a drop-down.

The required data should  be entered in accordance with the device documentation. You will need to complete the following:

• IP address (IP field);

• Device port (Port field);

• ModBus identifier (Network ID field);

• Decimal code of the register that reports the number (count) of inputs (count of DI channels);

• Decimal code of the register that reports the number (count) of outputs (count of DO channels).

The above information is available from your device ModBUS register table.

The example of the table for one of ICP DAS devices:

Outlined are registers that report counts of inputs and outputs respectively. You would use code 30100 as a DI count register and 30110 as a DO count register.

NumberOk distribution offers a utility DumpModBus.exe to dump Modbus device registers. Only registers with non-ZERO values are dumped. The utility is located along with NumberOk executable file.

The utility runs from the command line and requires the following parameters: DumpModBus.exe IP NetID, where:

• IP - ModBUS device IP address;

• NetID - device ID in the ModBUS bus.

Default ModBUS tcp port is 502.

List of fully tested and supported I/O modules: https://goo.gl/mr6bLC