Yesterday, 08:57 AM
Hi,
I am trying to get the N30 to work as a modbus device that I can read from via TCP on port 502. Could not get it to work on the IP address of the N30
Hooked up a Hi-Flying EW11 TCP to modbus converter to the RS485 port in modbus mode and that does work. Can see all the registers for chips on address 100/200/300
I was assuming that the setting
TCP Server: enable
Protocol: Modbus
local port: 502
modbus local addr 1
Would be sufficient to read the registers via the N30 IP address on port 502
Whatever I try I do get a time-out
Port 502 is open if I test with ModbusDoctor or Powershell I get connected but no readings at the expected adresses.
Also tried with setting Modbus-RTU-v2 and a virtual COM port without any responce. Please provide instructions if this should work and if so how?
Thanks,
GWS
I am trying to get the N30 to work as a modbus device that I can read from via TCP on port 502. Could not get it to work on the IP address of the N30
Hooked up a Hi-Flying EW11 TCP to modbus converter to the RS485 port in modbus mode and that does work. Can see all the registers for chips on address 100/200/300
I was assuming that the setting
TCP Server: enable
Protocol: Modbus
local port: 502
modbus local addr 1
Would be sufficient to read the registers via the N30 IP address on port 502
Whatever I try I do get a time-out
Port 502 is open if I test with ModbusDoctor or Powershell I get connected but no readings at the expected adresses.
Also tried with setting Modbus-RTU-v2 and a virtual COM port without any responce. Please provide instructions if this should work and if so how?
Thanks,
GWS

