fixed aruco detect remaps to relative topic names to suport namespaces

[JanezCim]

On a robot that has exported a ROS_NAMESPACE, aruco detect does not map topics correctly, because the remap takes in absolute topics and that can not be modified from terminal like other topics can be (eg. camera topic):

mon launch aruco_detect aruco_detect.launch camera:=raspicam_node

The changes that are made also work with the rest of the system when ROS_NAMESPACE is not set.

test that it works within magni gazebo with

roslaunch magni_gazebo fiducial_world.launch

[MoffKalast]

Yep, works as intended.

[JanezCim]

@AGregorc can you also test this when you can

[MoffKalast]

On second thought I may have missed something, the TF frame the transforms are getting published in relation to what looks like namespace/raspicam_sensor instead of raspicam_sensor. Not sure why namespaces would get added to damn TF frames but it seems to be happening.

[MoffKalast]

Ok yeah it seems that if I add the namespace/raspicam_sensor link to the urdf with 0,0,0 connection to the actual one, it starts to work properly. Not sure how to properly solve this one though. There must be a line in there that wrongly takes a topic name as a tf frame, but I haven't found it yet.

[MoffKalast]

AH I found it, it's the frameId = msg->header_frame_id;. Checking the camera info topic, the frame is being published wrong by gazebo, it's not an aruco error.

All good then.

[JanezCim]

And i think that this camera frame topic in gazebo will be solved with UbiquityRobotics/magni_robot#146 (comment)