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
Or we can add a frame_id and child_frame_id parameters for every sensor. But it interferes with the current config of users if they just update to the new version.
I added base_frame_id as a base for all distance sensor parent frame_id.
But imho better do not use send_tf: preconfigure TF in URDF and set orientation (to check consistence between FCU and URDF).
That way you will use static tf, that save a lot of bandwidth.
Problem:
The distance sensor frames are hardcoded. to
fcu
while we changed them all tobase_link
in PR #791mavros/mavros_extras/src/plugins/distance_sensor.cpp
Lines 255 to 256 in 0273f99
Solutions:
Adding a parameter
fcu_frame_id
to distance_sensor, yet, it interferes into the yaml parsing.Or we can add a
frame_id
andchild_frame_id
parameters for every sensor. But it interferes with the current config of users if they just update to the new version.Adding the hardcoded
base_link
is less versatile for custom setups.The text was updated successfully, but these errors were encountered: