Register reading with Modbus TCP

[rapidscadaaks]

Yes. This matches with the documentation.

[rapidscadaaks]

Hi
Awaiting guidance for resolution.
Thanks

[manjey73]

Judging by the images from the Modpoll configuration documentation, everything seems to be the same, but your device simply does not respond to one of the commands.
Perhaps the manufacturer changed something in the new version and did not update the documentation.
If this command was supported, but you got the wrong address, the device would give an error response. Try polling one register from 0 using Holding Registers

[rapidscadaaks]

Hi
I tried polling one register from 0 using Holding Registers and there was no response from the unit

I have created a support ticket with the manufacturer and await their response.

In the meantime, please suggest software for testing purposes for sending command to the unit and getting response.

[manjey73]

Well, use Modpoll as shown in the device documentation. If he answers, try to compare why he is not responding in scada.

Also try to read just one element with the command 02
Also check the InputRegisters reading.

• This reply was modified 3 weeks, 2 days ago by manjey73.
• This reply was modified 3 weeks, 2 days ago by manjey73.

[Mikhail]

Hi,

I have created a support ticket with the manufacturer and await their response.

I suppose, the manufacturer should somehow comment the situation. Please notify us about the result.

[rapidscadaaks]

Hi
Manufacturer (Waveshare) is not responding to the issue.
I have checked connecting the device directly to the PC using serial port and values are not received for the Input Channels. The issue therefore is not Rapidscada related.
I am therefore using alternate product and results are fine.
Thank you for the assistance

[Mikhail]

Hi,
Thank you for the update.

[Author]

Posts