You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The same request works correctly from a Linux terminal and returns a value:
modpoll -m tcp -p 502 -a 1 -r 3 -t 4 -0 ...**
So the device and the Modbus TCP connection itself are working.
Could someone point out what might be wrong with the Modbus request?
console:
INFO: T#1828588613253415: Connection to Modbus server succeded
ERROR: T#1828589614819474: Error reading input status :: Slave device or server failure
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I am trying to read registers from a device using Modbus.
(Forte release)
The CLIENT_1 FB reports QO = TRUE and STATUS = OK, but no data appears on the output.
The request ID looks like this:
modbus[...**:502:1000:3::1:3]
protocol: tcp
ip: ***
port: 502
slaveId: 1
pollFrequency: 1000
readAddresses: 3 (h)
The same request works correctly from a Linux terminal and returns a value:
modpoll -m tcp -p 502 -a 1 -r 3 -t 4 -0 ...**
So the device and the Modbus TCP connection itself are working.
Could someone point out what might be wrong with the Modbus request?
console:
INFO: T#1828588613253415: Connection to Modbus server succeded
ERROR: T#1828589614819474: Error reading input status :: Slave device or server failure
Beta Was this translation helpful? Give feedback.
All reactions