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
I try to connect to a PLC that has a Duagon CIP Stack embedded.
When I use Schneider PLC, everything works.
Then I tried with Node-Red ethernet-ip and get a : "Error connecting to PLC: Error: TIMEOUT occurred while reading Controller Props."
Doing a bit of Wireshark on it, and below the extract of a working Schneider Communication :
Then the Node-Red one :
So the main difference between the two is that node-red request for a service Code 0x52 instead of 0x54 for the Schneider one.
Wireshark identifies this two services as :
Schneider : 0x54 : Service: Forward Open (Request)
Looks like Node-red is using a version of ethernet-ip that only has unconnected messaging. Schneider PLC looks like it is using connected messaging. You could try updating the ethernet-ip library to the latest commit on GitHub. That should support connected messaging.
I am having similar issue here with Omron PLC although in my case the message is saying malformed packet..? I am using the example code provided to get the tag list.
Hello,
I try to connect to a PLC that has a Duagon CIP Stack embedded.
When I use Schneider PLC, everything works.
Then I tried with Node-Red ethernet-ip and get a : "Error connecting to PLC: Error: TIMEOUT occurred while reading Controller Props."
Doing a bit of Wireshark on it, and below the extract of a working Schneider Communication :
Then the Node-Red one :
So the main difference between the two is that node-red request for a service Code 0x52 instead of 0x54 for the Schneider one.
Wireshark identifies this two services as :
Do you know why node-red is using this 0x52 instead of 0x54 ?
And is it possible to change it ?
Thanks for your help !
The text was updated successfully, but these errors were encountered: