Skip to content
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

Closed
bombjackit opened this issue Jan 30, 2024 · 4 comments
Closed

Plc is not automatically reconnected #5

bombjackit opened this issue Jan 30, 2024 · 4 comments

Comments

@bombjackit
Copy link

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

  • node-red-contrib-cip-st-ethernet-ip 2.0.0-beta.3
  • Node red 2.2.2
  • Node.JS 14.21.1
  • Plc Rockwell 1756L81ES
  • Windows 10 professional 21H2
@bombjackit
Copy link
Author

Original post st-one-io#39

@bombjackit
Copy link
Author

I see commit SerafinTech/ST-node-ethernet-ip@cc9b241, maybe resolve my problem, I'll try soon

@SerafinTech
Copy link
Owner

Fixed

@bombjackit
Copy link
Author

bombjackit commented Mar 4, 2024

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
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants