forked from st-one-io/node-red-contrib-cip-ethernet-ip
-
Notifications
You must be signed in to change notification settings - Fork 4
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
Plc is not automatically reconnected #5
Comments
Original post st-one-io#39 |
I see commit SerafinTech/ST-node-ethernet-ip@cc9b241, maybe resolve my problem, I'll try soon |
Fixed |
I tried automatic reconnect after download to plc (with node-red-contrib-cip-st-ethernet-ip 2.0.2) and all go well. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
When a plc, for a known reason (like maintenance, firmware upgrade or software upload), is disconnected from the lan, sometimes it does not automatically reconnect : I have to restart flow manually.
Expected behavior
I expect that the plc is reconnected, in all case, automatically
Logs
This is the log (after this plc is disconnected)
26 Jun 08:03:27 - [error] [eth-ip endpoint:Plc] Error communicating with the PLC: {"generalStatusCode":4,"extendedStatus":[0]}
Environment
The text was updated successfully, but these errors were encountered: