The ibvunit program converts protocols implemented on physical devices into the ibprotocol communication protocol used by all components of the IB-System.

The device registers of all devices defined in the ibvunit.xml configuration file are available to all IB-System programs under the names:

rs.X.id.Y.VARNAME

where:

• X – denotes the identifier of the gateway to which the device is connected.
• Y – denotes the MODBUS address of the device.
• VARNAME – denotes the name of the register defined in the device configuration file.

Example variables for the h3f1v6 device with MODBUS address 1 connected to the gateway defined with identifier 0:

rs.0.id.1.dev.hardware
rs.0.id.1.dev.firmware
rs.0.id.1.dev.version
…
rs.0.id.1.input.t.0.value
rs.0.id.1.input.t.1.value
rs.0.id.1.input.t.2.value
rs.0.id.1.input.t.3.value
...
rs.0.id.1.input.t.0.err
rs.0.id.1.input.t.1.err
rs.0.id.1.input.t.2.err
rs.0.id.1.input.t.3.err
…
rs.0.id.1.output.do.1
rs.0.id.1.output.do.2
rs.0.id.1.output.do.3
rs.0.id.1.output.do.4

In addition to the variables associated with physical devices, the ibvunit program provides the variables:

• ibvunit.version - the version of the ibvunit program.
• ibvunit.mwt - the maximum total operating time of the program expressed in days, after which the program will be blocked. The value “-1” means that the time lock mechanism associated with the <MWT> section in the configuration file has not been activated.
• ibvunit.cwt - the total working time of all instances of the program expressed in days. The value “-1” means that the time lock mechanism associated with the <MWT> section in the configuration file has not been activated.
• ibvunit.ld - the operating time expressed in days, remaining until the program is blocked. The value “-1” means that the time lock mechanism associated with the <MWT> section in the configuration file has not been activated.

Additionally, ibvunit monitors each device defined in the configuration file and provides associated variables:

• ibvunir.DEVICE.tslc - the time that has passed since the last correct communication with the DEVICE device.

The DEVICE device identifier depends on the connected device. For example, a MODBUS device according to the documentation will have an identifier in the form of, for example, rs.0.id.1.