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

Data over TCP socket #127

Open
nbubis opened this issue Dec 5, 2024 · 1 comment
Open

Data over TCP socket #127

nbubis opened this issue Dec 5, 2024 · 1 comment

Comments

@nbubis
Copy link

nbubis commented Dec 5, 2024

The document here, explains the data format received from the robot over port 30000. Three questions:

  • When is the timetamp field in reference to? It's clearly not microseconds since epoch
  • Is there any way to synchronize this clock to the clock of the host computer the robot is attached to?
  • The table does not include the gripper position. What port and what bytes represent the gripper? I'm using the xArm parallel gripper.
@penglongxiang
Copy link

penglongxiang commented Dec 6, 2024

Hi @nbubis,

  1. The timestamp value is the microseconds elapsed since the controller box boot-up.
  2. It would be the user program to do the value comparison and synchronization. However if the host computer uses network clock sync mechanism, discontinuous time jump may occur.
  3. The communication with gripper is less efficient (as an external peripheral) and not automatically done in real-time, so there is no gripper position info in the real-time report channel. You can periodically check the gripper status through our API: get_gripper_position().

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

2 participants