You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Current behavior
read requests return crc errors or "Error: Data length error, expected y got x" with x < y. this problem does infrequently occur when requesting 1-2 registers, occurs about 50% of the time for 3-4 registers and almost always occurs when requesting more than 5 registers
as a brief follow-up: problem seems to be due to node-red-contrib-modbus. Using node-red-contrib-modbus-serial, I was able to retrieve the values as expected.
**I'm submitting a bug report:
Current behavior
read requests return crc errors or "Error: Data length error, expected y got x" with x < y. this problem does infrequently occur when requesting 1-2 registers, occurs about 50% of the time for 3-4 registers and almost always occurs when requesting more than 5 registers
`
Expected behavior
node should return the requested register. modpoll on command line (same system) works as expected:
`
Your Environment
Node-RED version: v0.17.5
Node.js version: v6.12.1
Linux 4.9.59+ arm LE
node-red-contrib-modbus: v2.5.0
upgrading also did not help:
Node-RED version: v0.18.7
Node.js version: v8.11.3
Linux 4.9.59+ arm LE
node-red-contrib-modbus: v3.6.1
AC-System from Kampman. connecting to it from the cmd-line as well as from a different windows system works as expected.
The text was updated successfully, but these errors were encountered: