Hi Andreas, I think the main reason is (as far as I understood it) that the slave id is particularly needed for modbus RTU over RS485 as here multiple devices are listening to the same connection. For this you identify the desired host with the slave id. In TCP it's always a one-to-one connection, so the slave id is pretty much ignored (As I said ... as far as I know)
Chris -----Ursprüngliche Nachricht----- Von: Andreas Vogler <[email protected]> Gesendet: Donnerstag, 12. August 2021 11:18 An: [email protected] Betreff: ModBus set slaveId... Hi again, I found a thread regarding how to set the slaveId here: [email protected] <mailto:[email protected]> But when I try to use it (modbus://localhost:502?slaveId=2 <modbus://localhost:502?slaveId=2>) it does not make any difference. It always uses slave 1… Best regards, Andreas
