Problem regarding RS485 communication
Posted: 10 Apr 2025, 11:40
Hello everyone,
I'm creating this post because I'm currently working with the RevPi Connect 4, and I'm experiencing some issues with Modbus RTU.
I've followed the official tutorials on your website, watched videos on your YouTube channel, and reviewed several guides recommended in forum replies on this topic—but I still can't read the Modbus messages.
Context:
- Previously, I worked with the RevPi Connect+ and Connect S, connecting to a Modbus RTU slave. I tested the communication using modpoll, PICtory (piTest), and a custom service that interacts with the slave. Everything worked fine.
- Now, I'm using a new RevPi Connect 4 (4GB/32GB). I tested the communication using modpoll and PICtory, and it works as expected—I can interact with the slave.
However, once I activate my service, the connection stops until I stop the RTU bridge within the service and reboot the RevPi.
Has anyone encountered a similar issue or have any insights into what might be causing this conflict?
I'm creating this post because I'm currently working with the RevPi Connect 4, and I'm experiencing some issues with Modbus RTU.
I've followed the official tutorials on your website, watched videos on your YouTube channel, and reviewed several guides recommended in forum replies on this topic—but I still can't read the Modbus messages.
Context:
- Previously, I worked with the RevPi Connect+ and Connect S, connecting to a Modbus RTU slave. I tested the communication using modpoll, PICtory (piTest), and a custom service that interacts with the slave. Everything worked fine.
- Now, I'm using a new RevPi Connect 4 (4GB/32GB). I tested the communication using modpoll and PICtory, and it works as expected—I can interact with the slave.
However, once I activate my service, the connection stops until I stop the RTU bridge within the service and reboot the RevPi.
Has anyone encountered a similar issue or have any insights into what might be causing this conflict?