Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Compatible to current robot hardware/firmware? #5

Open
fkraemer opened this issue Feb 11, 2020 · 0 comments
Open

Compatible to current robot hardware/firmware? #5

fkraemer opened this issue Feb 11, 2020 · 0 comments

Comments

@fkraemer
Copy link

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.

  1. The driver does not connect as described in the readme.md
  2. 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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant