Unable to start controller tilt_controller [closed]
I am trying to follow the Dynamixel motor tutorials.
I receive and error when trying to run the command roslaunch my_dynamixel_tutorial start_controller.launch.
The launch file starts to process the request but I get this error in return
core service [/rosout] found
process[dynamixel_manager-1]: started with pid [7825]
[INFO] [WallTime: 1375217005.105674] pan_tilt_port: Pinging motor IDs 1 through 25...
[INFO] [WallTime: 1375217007.372431] pan_tilt_port: Found 5 motors - 5 AX-12 [1, 3, 4, 12, 16], initialization complete.
[WARN] [WallTime: 1375217015.192204] The specified motor id is not connected and responding.
[WARN] [WallTime: 1375217015.193454] Available ids: [1, 3, 4, 12, 16]
[WARN] [WallTime: 1375217015.194311] Specified id: 6
^C[dynamixel_manager-1] killing on exit
shutting down processing monitor...
... shutting down processing monitor complete
done
I have the correct baud rate set for these motors as well as the correct motor IDs. I was able to launch roslaunch my_dynamixel_tutorial controller_manager.launch. But, I receive an odd Warning there as well. This warning states The specified id is not connected and responding. Specified id: 6.
This is odd since I don't have a motor marked id 6, nor is this listed in my 'start_tilt_controller.launch' file nor in my 'tilt.yaml' file. I did have a servo with this id number, but I removed it and it is no longer in use.
I have tested the functionality of these servos and they are position controllable in LabVIEW.
I am running ROS Fuerte on a Ubuntu 12.04 machine.
Thank you for the help.
I am also not able to directly move the servos from the command line... when using a command similar to this one:
rostopic pub -1 /tilt_controller_3/command std_msgs/Float64 -- 3.5
Ok. I think this may have to do with the fact that I'm trying to initialize multiple servos, at once, in a single tilt.yaml file. Is there any documentation on how you control more than one servo at once?
Please post you config files and launch files. It looks like one of your controllers is looking for motor with id 6 which is not present, that would be error in config files.
well, I added the motors to the "start" file and the "tilt.yaml" file... and that worked for a time. Now, randomly, one of the motors will fail to initialise. What's weird is that if I start the motors individually, they will start just fine...but not when listed all at once. I'll post my code
when I can (it's currently in a location I can't get at)... it may be awhile.