Closed ktiwari9 closed 4 years ago
I guess you are using Hydro, since "summit_xl_robot_control" was deprecated in Indigo. I also guess that you refer to the transform being published by /gazebo between /odom and /summit_xl/base_footprint. Is this right? Note that "summit_controller_node" does not exist in this simulation. It should only exist in the real robot of the smaller version of the SummitXL.
Hi, I cant make the summit_xl move in gazebo, by using rqt. I checked both the summit_xl_control.yaml file and also the urdf for the rubber wheels. the type of controller for each wheel is consitent with the hardware interface mentioned in the wheel urdf file.
type: velocity_controllers/JointVelocityController (controller.yaml)
I get the following error as soon as I launch the summit_xl_control to get a link between odom and base_link. [ INFO] [1441269232.456259714, 0.241000000]: Physics dynamic reconfigure ready.
[summit_xl/summit_xl_robot_control-10] process has died [pid 13889, exit code -11, cmd /home/toshiba/catkin_ws/devel/lib/summit_xl_robot_control/summit_xl_robot_control __name:=summit_xl_robot_control __log:=/home/toshiba/.ros/log/664a1aea-5216-11e5-b082-e06995342d97/summit_xl-summit_xl_robot_control-10.log]. log file: /home/toshiba/.ros/log/664a1aea-5216-11e5-b082-e06995342d97/summit_xl-summit_xl_robot_control-10*.log
My tf tree is shown below. I have 2 robots. one husky and one summit so I am using a namespace for summit as summit_xl. I dont understand why is there a tf from /gazebo from /map->/odom but not via the summit_controller_node.