browse
This article is about the requirements to connect a ModbusTCP/RS485 equipment to the Tower/Bridge.
| Modbus | IP | RTU |
|---|---|---|
| Slave address* of all equipment | If applicable | R |
| IP address of all equipment | R | N/A |
| Modbus register list* (so-called exchange table) of all equipment | R | R |
| Modbus UDP ports | R | N/A |
| Network communication configuration (Baud rate/Parity/Data bit/Stop bit) | N/A | R |
R = Required/O = Optional / N/A = Not Applicable
Here is the parameters that you'll need to fill in order to create your modbus Equipment :
Modbus IP :
In an IP network you'll have to be aware of your IP parameters :
Be sure that your choosen IP address is available and free on your IP network.
Be sure that the Box can access the targeted equipment (Both are in the same subnetwork or accessible using a gateway for example)
| If you have a VPN on this network be sure that the Tower/Bridge is whitelisted otherwise the VPN will block Tower/Bridge communication. |
Modbus RS485 :
In a serial network be sure that the chosen address (slaveID) is free and available on the network.
Be sure that you are using a twisted paired communication cable.
| Please find here the hardware information |
Modbus properties requirements :
In order to get your data correctly, you'll have to know the Modbus register table of the device.
In this document (provide usually by the manufacturer) you'll have the information to fill these following blanks.
-
Slave address in Modbus IP is not mandatory. There are some Modbus TCP/IP <==> Modbus RTU gateway that forward Modbus packet to a slave. That’s why the slave address needs to be known.
-
A list of the point to be read can be provided instead of the entire Modbus register list and the following points are required
- Name of the variable
- Register address
- Data format
- Access type
- Modbus function used
If you have any problem, please do not hesitate to contact us: Wattsense Support
Comments
0 comments
Please sign in to leave a comment.