April-28th-2020, 09:49 AM
Meanwhile I checked the source code of the RTUbuffered mode to see what it is doing: https://github.com/yaacov/node-modbus-se...redport.js
I see in there that whenever the serialport node (used by Modbus RTU node: https://github.com/serialport/node-serialport) raises the event 'data' on each Rx byte that then it is checkin if a complete Modbus RTU message has been received to the end. This is possible since with the previously sent Modus command you know exactly how long the response of the server will be.
Is your python code doing the same thing? I don't know.
I see in there that whenever the serialport node (used by Modbus RTU node: https://github.com/serialport/node-serialport) raises the event 'data' on each Rx byte that then it is checkin if a complete Modbus RTU message has been received to the end. This is possible since with the previously sent Modus command you know exactly how long the response of the server will be.
Is your python code doing the same thing? I don't know.
„You never fail until you stop trying.“, Albert Einstein (1879 - 1955)