Skip to content

Compatible to current robot hardware/firmware? #5

@fkraemer

Description

@fkraemer

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?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions