• Expressions / Script language
  • Users and Permissions
  • Backup, restore, reset to factory settings
  • Software release notes
  • Examples of Modbus RTU cabling

    For devices connected to the Modbus RTU line, different rules apply when connecting devices. The devices are connected using two A / B wires. It is not necessary to implement a GND connection from a 24V DC source. Namely, if the devices require this connection in the manufacturer's conditions, the requirement must be implemented. Because manufacturers universally set their peripherals to address 1, I assign each device a sequential 1-250 identification address when sequentially connected. Devices with the same address do not work on the system. It is recommended to terminate the bus with a 120R resistor. Some products already have this resistor installed automatically, in which case it no longer needs to be retrofitted to the connection terminals. The devices that communicate with the Modbus RTU protocol are mostly recuperation, air conditioning, energy counting devices, relay output and input modules.

    For proper communication with Modbus, all peripherals must have the same communication protocol set with speed, parity and stop bits. Otherwise, the devices will not function as a whole. Always check the manuals of the peripherals you connect for the correct settings and the possibility of changing the settings of the communication parameters.

    For classic RS485 and Modbus RTU distributions, a cable type meeting the EIA RS-485 requirements with an impedance of 120R is prescribed for industrial distributions. All you have to do is create a bus for our control blocks using Cat5E, Cat6, Cat6A and others. RS-485 certified cabling is not required. Shielded cabling as a whole or separately in individual pairs is also not strictly prescribed. In cables that are not individually shielded in pairs, it is not recommended to run two different buses such as RS-485 and LAN 100/1000MBit, or other bus distribution EZS, EPS, Modbus RTU, etc.