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
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