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
For explicit messages sent using getAttributeSingle it would be useful to add an optional parameter with a buffer. This buffer is appended to the message. Some ethernet/IP devices require additional information beyond the class/instance/attribute. See this issue for a description for such a case for a SEW drive #62
Code/documentation change for PR is here: https://github.com/greg9504/ST-node-ethernet-ip/tree/ExplicitMsgWithData
The text was updated successfully, but these errors were encountered:
for connecting to a device for explicit messaging that is not a PLC I put Buffer.alloc(0) as the slot number. This will blank out the slot part of the path.
For explicit messages sent using getAttributeSingle it would be useful to add an optional parameter with a buffer. This buffer is appended to the message. Some ethernet/IP devices require additional information beyond the class/instance/attribute. See this issue for a description for such a case for a SEW drive #62
Code/documentation change for PR is here:
https://github.com/greg9504/ST-node-ethernet-ip/tree/ExplicitMsgWithData
The text was updated successfully, but these errors were encountered: