Closed towen closed 3 years ago
25 Mar 2021 17:13:29 conn[127.0.0.1]: request: [00][03][9c][40][00][64] 25 Mar 2021 17:13:29 conn[127.0.0.1]: broadcast request sent
Looks like your RTU slave is configured to use address 0 which is reserved for a broadcast address in Modbus protocol. In broadcast mode, the master sends a request to all slaves and no response is returned to broadcast requests sent by the master. Hence mbusd ignores this unexpected response message and logs the message about dropped bytes.
Could you configure your RTU device to use another address, like 1? It should fix the problem.
Aha of course! Thanks! :)
Hi,
When running on a Raspberry Pi connected to a Modbus RTU slave over RS232 (TTL) I get no response from mbusd. I am using the 'sunspec2' library. If I connect sunspec2 as an RTU client directly to the serial port (ttyUSB0) it works fine. But if I connect mbusd to the serial port and try to connect sunspec2 as a TCP client to mbusd, it times out. If I monitor the serial port, I can see the data returned, but mbusd never sees it. Setting loglevel 9, I can see that it says the tty dropped some bytes - I guess that's the problem