ROBOTIS-GIT / DynamixelSDK

ROBOTIS Dynamixel SDK (Protocol1.0/2.0)
http://emanual.robotis.com/docs/en/software/dynamixel/dynamixel_sdk/overview/
Apache License 2.0
454 stars 405 forks source link

Turtlebot3: Open Manipulator Bringup Fails: DynamixelSDKWrapper: No status packet! Proces died: stack smashing detected. #592

Closed perrombouts2322 closed 1 year ago

perrombouts2322 commented 1 year ago

Turtlebot3: Open Manipulator: bringup fails: ERROR from Dynamixels SDKWrapper : No status packet found + proces dies: stack smashing detected.

-Ros 2 Humble -Waffle-Pi -Raspberry Pi 4 -Ubuntu 22.04 -OPEN CR 1.0 -Servo's: xm430-w350-t

Hello, me and my student group from UPV Valencia are following the ROBOTIS E-Manuel for the Turtlebot3: Open Manipualtor. We are following the steps issued for Foxy because Humble is not available. https://emanual.robotis.com/docs/en/platform/turtlebot3/manipulation/#turtlebot3-with-openmanipulator

We are currently stuck at step 7.5 (Bringup).

We took these premature steps:

SOFTWARE SETUP: (humble instead of foxy installed)

$ sudo apt install ros-humble-dynamixel-sdk ros-humble-ros2-control ros-humble-ros2-controllers ros-humble-gripper-controllers ros-humble-moveit $ cd ~/turtlebot3_ws/src/ $ git clone -b humble-devel https://github.com/ROBOTIS-GIT/turtlebot3_manipulation.git $ cd ~/turtlebot3_ws && colcon build --symlink-install

OPEN CR FIRMWARE SETUP

$ export OPENCR_PORT=/dev/ttyACM0 $ export OPENCR_MODEL=turtlebot3_manipulation $ rm -rf ./opencr_update.tar.bz2 $ wget https://github.com/ROBOTIS-GIT/OpenCR-Binaries/raw/master/turtlebot3/ROS2/latest/opencr_update.tar.bz2 $ tar -xvf opencr_update.tar.bz2 $ cd ./opencr_update $ ./update.sh $OPENCR_PORT $OPENCR_MODEL.opencr

Then when we try to launch the hardware bringup:

$ ros2 launch turtlebot3_manipulation_bringup hardware.launch.py

We get multiple errors stating:

[ros2-control-node-1] [ERROR] [DynamixelSDKWrapper] [TxRxResult] There is no status packet!

Later the proces dies stating:

stack smashing detected

I will upload screenshots taken stating the full output code:

Code1_Issue Code2_Issue

We as a group think it has to do with an incompatible firmware version on our OPEN CR board. Can anyone please help us resolve this issue or give an indication what the problem might be? Thanks!

perrombouts2322 commented 1 year ago

Any help would be appreciated @ROBOTIS-Will