husky urdf can't be customized
I am working on husky A200 and follow the instruction from this manual to get Husky run outdoor with GPS http://www.clearpathrobotics.com/asse... . There are several files that need to modified because I use different GPS, and laser. The laser im using is LIDAR 3D velodyne.I am at the step to customize URDF to bring the robot model correct to what I have compare to the one that they have in the manual. I customized urdf.xacro file like this
<robot name="husky" xmlns:xacro="http://ros.org/wiki/xacro">
<xacro:arg name="laser_enabled" default="$(optenv HUSKY_LMS1XX_ENABLED false)" />
<xacro:arg name="ur5_enabled" default="$(optenv HUSKY_UR5_ENABLED false)" />
<xacro:arg name="kinect_enabled" default="false" />
<xacro:include filename="$(find husky_description)/urdf/husky.urdf.xacro" />
<xacro:include filename="$(find husky_description)/urdf/decorations.urdf.xacro" />
<xacro:husky_robot />
<!-- Insert Customizations Below -->
<link name="mesh_link">
<visual>
<geometry>
<mesh filename="package://husky_custom_description/meshes/wisu01_husky_arch.dae" />
</geometry>
</visual>
</link>
<joint name="mesh_joint" type="fixed">
<parent link="top_plate_link" />
<child link="mesh_link" />
<origin xyz="-0.07 0.0 0.0" rpy="0 0 0" />
</joint>
<link name="velodyne"/>
<joint name="arch_to_velodyne" type="fixed">
<parent link="top_plate_link"/>
<child link="velodyne"/>
<origin xyz="0.0 0.0 0.68" rpy="0.0 0.0 0.0"/>
</joint>
</robot>
The wisu01_husky_arch.dae file was provided by clearpath together with my Husky, and when I launch the robot model without launching husky gps waypoint, it came up correctly. However, when I run in the waypoint_nav package, it appears the errors said:
Failed to find root link: Two root links found: [base_link] and [top_plate_link]
It seems to not be able to find base_link and top_plate_link in my husky_desktop, but I double check and they are there. This might because my knowledge about urdf still limit. Can anyone please point where I should go to check for this error? I have been google the familiar error and the answers are trivial.