Quick Start-up of Modbus

In order to launch the Modbus communication properly, it is necessary to follow these steps:

Step 1: Having the device added correctly in the iC Tool, expand the Networks container, and go to the Modbus component.

Step 2: Go to the Interfaces component. The Ethernet components is added by default, the SerialPort component has to be added manually, if required.

(a) Go to the Ethernet component to configure the IP port for Modbus TCP/IP communication if necessary.

(b) Go to the SerialPort components to configure the RS485 port for Modbus RTU communication if necessary.

Note

Please remember that the device can communicate only one type of serial protocol on one port. If the Modbus RTU protocol is enabled on the serial port, the BACnet MS/TP protocol is disabled.

Note

Please remember that although the nano EDGE ENGINE system is designed to handle communication in BACnet IP, BACnet MS/TP, Modbus TCP/IP, and Modbus RTU protocol, the variants may differ between devices. Always make sure to check the device’s hardware manual to check the available communication protocols.

Step 3: The nano EDGE ENGINE is designed to handle controller’s communication as the Modbus RTU client or server device and Modbus TCP/IP client or server device.

(a): The LocalDevice component (automatically named after the device's model and serial number) for Modbus TCP/IP or RTU server device is also added by default. In order to configure the Modbus server device, go to that component.

Note

The LocalDevice component has a Modbus gateway extension, which allows Modbus RTU server devices (for example, RS485 I/O modules) to communicate with the Modbus TCP/IP network through a gateway device (for example, a RAC18-IP or VAV14-IP controller).

(b): In order configure the Modbus RTU or TCP/IP network, the Network and Device components need to be added, along with AnalogPoint, BinaryPoint, MultistatePoint, and StringPoint components, as necessary. Go to the Device Libraries and expand the Core library for the Network component and Modbus library for other components. Choose components to be added—components may be added one by one or grouped in one selection. Drag the selected component(s) and drop it(them) under the Modbus component in the Networks container.

Note

Please remember that the components' hierarchy needs to be preserved here: the Network component has to be located under the Modbus component, the Device component under the Network component, and the AnalogPoint/BinaryPoint/MultistatePoint/StringPoint components have to be placed under the Device component.

If the superior component is selected in the Workspace Tree window and its special view (Network Manager/Device Manager/Point Manager) is opened in the main screen, the Device Libraries shows only the components that can be added directly under it. For example, if the Modbus component is selected in the Workspace Tree window, the Device Libraries shows only the Network component in the Core library.

Step 5: Go to each added component, open its Property Sheet (or go the the Modbus component's Property Sheet and expand each component there), and set their parameters (enable, addresses, etc.). Make sure to save the changes.

More

In order to facilitate working with Modbus, special views have been developed:

Network Manager, available in the Modbus component;
Data Point Manager, available in the LocalDevice component;
Device Manager, available in the Network component;
Point Manager, available in the Device component.

Ready to Use: Configured components are ready for proper Modbus communication.