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
when the plc is lost connection to the node red, it won't automatically reconnect to the plc, it must be re deploy the flow or fully restart the node red.
is there any other way to fix this problem?
The text was updated successfully, but these errors were encountered:
As stated in the readme, UDP 4E is the most reliable (In my previous job, I had years of problems with the TCP connections on Mitsubishi PLCs)
Regarding auto reconnect, you can also watch the status of the node or the output of the node and determine if a reconnect is necessary & issue a disconnect/connect.
The built in help states...
INFO: To open / close the MC Protocol connection, send boolean true in msg.connect , msg.disconnect or msg.reinitialize. Alternatively, send string connect, disconnect or reinitialize in msg.topic to the any mc read / mc write node.
Note everyone's configuration will be unique so you will need to adapt it to suit.
I will also reiterate the point:, where possible , use UDP. This will provide the most stable connection (with 4E is even better)
when the plc is lost connection to the node red, it won't automatically reconnect to the plc, it must be re deploy the flow or fully restart the node red.
is there any other way to fix this problem?
The text was updated successfully, but these errors were encountered: