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

Ros2 node publishes incorrect imu transform for Femto sensor #81

Open
john-maidbot opened this issue Dec 16, 2024 · 0 comments
Open

Ros2 node publishes incorrect imu transform for Femto sensor #81

john-maidbot opened this issue Dec 16, 2024 · 0 comments

Comments

@john-maidbot
Copy link

john-maidbot commented Dec 16, 2024

Issue Summary:
I am encountering a problem with the femto.launch.py .

  • Commit (main today): 98a1cafd9beec33d6433e82c8e9af5ea0307e9de

Expected Behavior:
The correct inu to depth_optical frame transform should be published over tf2 when running femto.launch.py.

Actual Behavior:
The imu to depth_optical transform is currently published as identity, which seems incorrect. I think this is supported by the documentation: [Orbbec Femto Coordinate Systems](https://www.orbbec.com/documentation/femto-bolt-coordinate-systems/#:~:text=The%20%5Bx%2Cy%5D%20coordinates,left%20pixel%20in%20the%20image).

Potential Causes:

  • Is this an SDK issue where extrinsics are read incorrectly?
  • Or is the wrapper misinterpreting the extrinsics from the SDK?

Additional Notes:

  • I attempted using the v2-main branch, but my sensor doesn't connect (the README suggests Femto isn't supported on v2-main, though I might be mistaken).

Thank you for your help!

@john-maidbot john-maidbot changed the title Ros2 node publishes incorrect transform for Femto sensor Ros2 node publishes incorrect imu transform for Femto sensor Dec 16, 2024
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