MODBUS TCP/IP device type

MODBUS TCP/IP device type
none 0.0 0

EasyBuilder Pro V6.10.01.259
cmt-SVR-100

I previously used a cmt-SVR-100 for protocol conversion MODBUS RTU (Zero-based Addressing) to EtherNet/IP (CompactLogix). Now a customer would like MODBUS RTU to MODBUS TCP/IP (Aveva Intouch HMI-SCADA). The SCADA device will only be reading the MODBUS TCP/IP data. I assume I would select MODBUS TCP/IP (Zero based Addressing) in the new Local Device for device type for SCADA? Are there any other questions I should be asking the customer regarding their communication protocol? They did mention “no Gateway” will be used and they have yet to determine an IP address at this time. Thank you.

Would you have any sample programming links for the Macro regarding SetData (I will be using the same GetData Macros as before)?

Hi there,

They should ask if the SCADA system is going to function as a Modbus TCP server or a Modbus TCP client. If the SCADA system will function as a Modbus TCP server, they can use the “Modbus TCP/IP” driver. However, if the SCADA system is going to function as a Modbus TCP client, they should use the “Modbus server” driver within the HMI project.

Here is an example in which the hmi acts as a Modbus tcp server to make Modbus rtu data available to a client.

You will not need to use SetData/GetData. The cMTSVR lets you set up a simple table. Watch the video from DanielDahilig. Note that SCADA & HMI’s are almost always a Modbus TCP “client”. It is a special feature of the cMT series that lets it act as a “server” as well. Also note that in your SCADA you will of course need to set the IP address to that of the cMT but you will also need to set the Modbus address of the Modus device in the SCADA driver. It is sometimes called a station address, or a unit ID. You will usually find it set to a default value of 1 or 255.

1 Like