Skip to content

static_transform_publisher in launch is causing TF conflicts. Could you make it OPTIONAL? #68

@ahsanyusob

Description

@ahsanyusob

tf2_node = Node(package='tf2_ros',
node_executable='static_transform_publisher',
node_name='static_tf_pub_laser',
arguments=['0', '0', '0.02','0', '0', '0', '1','base_link','laser_frame'],
)

Hello developers,

I would like to request that this part of the launch file to be OPTIONAL.
It is good for testing the ydlidar out-of-the-box.
But, it is causing conflicts if e.g. we already have our own robot_descriptions that publishes our own
TF base_link->laser_frame.

Since a CHILD FRAME is not allowed to have multiple PARENT FRAME, the static tf publisher in current launch file is causing either one TF link to be removed or ignored.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions