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
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!
The text was updated successfully, but these errors were encountered:
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
Issue Summary:
I am encountering a problem with the
femto.launch.py
.98a1cafd9beec33d6433e82c8e9af5ea0307e9de
Expected Behavior:
The correct inu to depth_optical frame transform should be published over
tf2
when runningfemto.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:
Additional Notes:
v2-main
branch, but my sensor doesn't connect (the README suggests Femto isn't supported onv2-main
, though I might be mistaken).Thank you for your help!
The text was updated successfully, but these errors were encountered: