-
-
Notifications
You must be signed in to change notification settings - Fork 6
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
Node red event loop delaying due to socket can node #42
Comments
OK I have not noticed this behavior. Would expect that it originate from lower layers but will check. Thanks for reporting. |
I can't view the pictures. Do you get the warnings with the current version 1.2.14 also. There was a mismatch in version requests of modules in previous versions which is solved. |
Sorry for the delay here. I have been away from office. In the old version there are requirements for old versions of submodules, among other old version of node-red (used for debug) which is not needed. The dependencies section in package.json should have "bcrypt": ">=5.0.1", There are some other changes but none that should cause the behavior you see. |
In node-red-contrib-socketcan 1.2.9 version, whenever the data has been requested from socket can in node for every 250ms, when socket can out node is added to the flow, the other part of the code execution is getting slower.
My CAN baudrate is configured at 125kbps
The text was updated successfully, but these errors were encountered: