MODBUS TCP/IP device type

MODBUS TCP/IP device type
none 0.0 0

Yes, SCADA connected to LAN1 communicating Modbus TCP/IP reading COM1 Modbus RTU data. I will forward to you shortly. Thank you.

I appreciate all your previous help getting these devices communicating and to confirm I was able to connect my laptop to LAN1 using CAS Modbus Scanner and replicate SCADA reading Modbus data. Now the devices are in the field, the customer is having difficulty reading data through LAN1 using their Modbus scanning software connected directly to LAN1 for trouble shooting. They have also changed the LAN1 IP and added a Gateway IP and the same DNS address. The first three bytes of all previously mentioned are the same and the Gateway and DNS match. I am going onsite tomorrow just to plug into LAN1 and again simulate SCADA using CAS Modbus Scanner. I will update my computer IP, but do you have any other suggestions now that they have added a Gateway and DNS? All I need to do is prove that I can read data through LAN1 and my job is done. SCADA acts as a Modbus TCP client. Thanks again!

Hi @ProcessControl,

There is no need to worry about the gateway and dns addresses when used over a local connection. Just ensure that your PC is on the same IP subnet as the HMI, verify that you can ping the unit, and the connection using software like CAS should be successful.