-
-
Notifications
You must be signed in to change notification settings - Fork 112
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bug Sequential de-queuing #202
Comments
#195 is also interesting here to send only one msg to request all units |
I have same error with setup which worked for many monthes. Here is part of flow:
|
@mastrikGit try to work with the units in parallel on tcp in your case - how does it work for you in parallel? |
please test with the new v5.13.1 |
Updated, set setting as you suggest. Will write back tomorrow with results. Thank you for fast replies! |
@biancode Thanks for fast fix. Uptime is more than 24hrs after update and no errors appear |
Problem
Current behavior
Blocking serial messages on Timeout and sequential queue.
Expected behavior
It should not block the queue and every response should release with error if blocked.
Minimal reproduction of the problem with instructions
Your Environment
Please tell us about your environment:
Yes, modbus-serial is the name but it does all, TCP and Serial.
The node-modbus package is just for the Modbus Server node.
Device :
Description of the connecting Modbus system:
node-red-contrib-modbus version: v5.10.1
node --version
= v12.2.0The text was updated successfully, but these errors were encountered: