The NETx BMS Platform Core Server provides a Modbus interface to integrate Modbus devices. All Modbus datatypes are supported: discrete inputs, coils, holding registers, and input registers.
Since there is no discovery protocol for Modbus the configuration has to be done manually.
Modbus device definition
To define a Modbus device, first select open the Core Studio and select the menu item in Modbus / Device definitions.
Here the device parameters are defined. Provide a name, an IP address and a port and select the device type in the last column.
More information about Modbus device definitions fields can be found here.
Modbus data point definition
In the Core Studio, select the menu item in Modbus / Datapoint definitions.
For each data point provide device name, data point type, address. Details on Modbus datapoint definition can be found here.
Modbus address mapping
To use an addressing scheme different to the standard Modbus memory addresses that start with address 0, an address mapping is possible. Select the Modbus / Modbus mapping definitions menu item and provide for each Modbus device and register type an offset that is added to the address configured in the data point definitions.
The structure of the Modbus address mapping definition can be found here.
Afterwards, save all changes in Modbus tabs, NETx BMS Core Server will display a reinitialization message. Restart the NETx BMS Core Server again Server and open an Item Tree. All Modbus devices and objects are found under the sub tree "NETx\XIO\Modbus". Each device has one entry within the Item Tree. Below this entry, you will find a GATEWAY item which shows the connection state to the Modbus device. In addition, all selected objects are listed. As defined by the Modbus standard each folder represents the Modbus Datapoint type.
Article applies to the following products:
- NETx BMS Platform
- NETx Multi Protocol Server
- NETx BMS Server 2.0