April-28th-2020, 12:18 PM
Which driver do you mean exactly?
Seems so, that the same behavior occurs already using the following recommended package:
https://hub.docker.com/r/hilschernetpi/n...dockerfile
I installed the container on the recommended (original) netPI OS and the fault free communation were only possible, if I use 'rtu-buffered' in node-red.
That looks like, that there is exactly the same problem. I connected another Modbus-RTU device (electrical meter) with the same results.
It is not possible for us to use node-red for our coming project. Therefore we need another solution.
The easiest way is at the moment, that we use an external USB Adapter instead of the internal RS485 interface.
I will diskuss that in our next internal team meeting.
Seems so, that the same behavior occurs already using the following recommended package:
https://hub.docker.com/r/hilschernetpi/n...dockerfile
I installed the container on the recommended (original) netPI OS and the fault free communation were only possible, if I use 'rtu-buffered' in node-red.
That looks like, that there is exactly the same problem. I connected another Modbus-RTU device (electrical meter) with the same results.
It is not possible for us to use node-red for our coming project. Therefore we need another solution.
The easiest way is at the moment, that we use an external USB Adapter instead of the internal RS485 interface.
I will diskuss that in our next internal team meeting.
