Hello all, modbus amateur here. This question has a duplicate in https://stackoverflow.com/questions/72959652/unkown-cause-of-pymodbustcp-timeout
I have an equipment connected via ethernet cable to the network and i am trying to check if i can get some information from it. Its manual says it accepts modbusTCP via its ethernet interface and modbus RTU via its serial interface. I know its I.P. and scanning it with nmap reveals that port 502 is open with mbap service. Therefore, following the equipment's registers map (i attach an image of the desired register) i tried implementing the python code:
from pyModbusTCP.client import ModbusClient
client = ModbusClient(host="device_IP", port = 502, auto_open=True,debug=True)
client.open()
client.read_holding_registers(4096,32)
To which i only get
Tx
[F4 2E 00 00 00 06 01] 03 10 00 00 02
timeout error
Am i doing something wrong? Since im only doing this to test if communication with device is ok, would anyone suggest other debug tool? Thanks in advance for any help.
I have an equipment connected via ethernet cable to the network and i am trying to check if i can get some information from it. Its manual says it accepts modbusTCP via its ethernet interface and modbus RTU via its serial interface. I know its I.P. and scanning it with nmap reveals that port 502 is open with mbap service. Therefore, following the equipment's registers map (i attach an image of the desired register) i tried implementing the python code:
from pyModbusTCP.client import ModbusClient
client = ModbusClient(host="device_IP", port = 502, auto_open=True,debug=True)
client.open()
client.read_holding_registers(4096,32)
To which i only get
Tx
[F4 2E 00 00 00 06 01] 03 10 00 00 02
timeout error
Am i doing something wrong? Since im only doing this to test if communication with device is ok, would anyone suggest other debug tool? Thanks in advance for any help.
Attachments
-
32 KB Views: 4