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
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?
The text was updated successfully, but these errors were encountered:
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.
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?
The text was updated successfully, but these errors were encountered: