-
Notifications
You must be signed in to change notification settings - Fork 9
Open
Description
My robot has hardware version 3.2 and software/system version 1.72.38. I am guessing the assumed communication protocol is outdated for this driver to work.
- The driver does not connect as described in the readme.md
- Neither the UI nor the manual suggest that this driver will work with the commands currently being sent (like movj0, ...) or expected to be received.
Instead the manual points for setting up a TCP IP connection to the "Listen" Node or TM Ethenet Slave mode.
Then it uses a communication protocol containing header, length, data, checksum chunks plus seperators. Does not look alot like this driver to me...
Can anyone confirm/correct this?
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels