After starting up canopen_motor_node, roservice call /driver/init be executed, the message "Initializing failed: Transition timeout: Colud not enable motor" appeared and it was abnormal Exit.
Perhaps it should have sent "#602#2B,40,60,00,06,00,00,00,00", "#602#2B,40,60,00,07,00,00,00,00", "#602#2B,40,60,00,0F,00,00,00,00", but I think it's not being executed because of the configuration.
We have confirmed that the state will be in Enable Operation when "601#2B,40,60,00,0F,00,00,00,00" is sent by cansend according to the manual of the motor.
operating environment
Ubuntu : 18.04
ROS : Melodic
ros_canopen : version 0.8.2 (I understand that this is a stable version of melodic)
Motor Controller ZLTech's ZLAC8030
The configuration file and the entire log are attached. ( lexx_auto_launch is the name of the package. )
After starting up
canopen_motor_node
,roservice call /driver/init
be executed, the message "Initializing failed: Transition timeout: Colud not enable motor" appeared and it was abnormal Exit.Perhaps it should have sent "#602#2B,40,60,00,06,00,00,00,00", "#602#2B,40,60,00,07,00,00,00,00", "#602#2B,40,60,00,0F,00,00,00,00", but I think it's not being executed because of the configuration.
The following is the log of candump at that time.
We have confirmed that the state will be in Enable Operation when "601#2B,40,60,00,0F,00,00,00,00" is sent by cansend according to the manual of the motor.
operating environment Ubuntu : 18.04 ROS : Melodic ros_canopen : version 0.8.2 (I understand that this is a stable version of melodic) Motor Controller ZLTech's ZLAC8030
The configuration file and the entire log are attached. ( lexx_auto_launch is the name of the package. )