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
Which node-red-contrib-modbus version are you using?
"node-red-contrib-modbus": "~5.42.0"
What happened?
using Flex Getter on com6 (USB /RS485 converter) to read from 2 devices (each with their own USB/RS485 converter) and slave nodes ( Using 2 separate functions to pre-load flex-getter with a different unitid. After deployment, whichever unit id is injected first (say unitid : 11) works as expected. The second does not work. Re-deploy and change the order (say unitid : 12) and this one now works.
Which node-red-contrib-modbus version are you using?
"node-red-contrib-modbus": "~5.42.0"
What happened?
using Flex Getter on com6 (USB /RS485 converter) to read from 2 devices (each with their own USB/RS485 converter) and slave nodes ( Using 2 separate functions to pre-load flex-getter with a different unitid. After deployment, whichever unit id is injected first (say unitid : 11) works as expected. The second does not work. Re-deploy and change the order (say unitid : 12) and this one now works.
Server
Other/External server
How can this be reproduced?
Flow.json
What did you expect to happen?
I expected that the Flex-Getter would be able to accept a new unitid programmatically
Other Information
Node-red version v4.0.2
Node.js version v20.16.0
The text was updated successfully, but these errors were encountered: