CK_COMPOUND_RETURN_ERROR #173
Comments
|
sometimes this means that the brake test was not executed, could that be? By the way, you can already test the |
|
It seems like you didn't quite understand it accurately. Could you please explain a bit more in detail? |
|
did you execute the brake test? |
|
No, I haven't tested the brakes yet. I don't know exactly how to do it. |
|
okay no problem. Select: Applications -> BrakeTestMonitorS... Run the test as you run the LBRServer. Careful, when the test is finished, the robot will execute a sample motion. |
|
This is unrelated to your problem, but could you re-install the |
|
We are currently undergoing a brake test. Is it normal for the A1 joint to continuously move left and right? Do I have to quit it midway? Or do I have to wait until it ends? |
|
this test will move each joint left right, from A1 to A7. You have to press and hold play if you are in test mode when the test is over, the robot will start a left / right motion, so be a bit careful there. Let me know once you re-installed the
|
|
I reinstalled according to quick-start. Can I end the break test and try connecting to the robot again? |
|
yes so when the robot starts the motion, the brake test is finished. You can just stop it. Sorry for the confusion! |
|
LBRServer but same error occuired the first picture. |
|
when you go to Station -> Safety -> Status what can you see? |
|
State : Warning Safety Control |
|
what version of the FRI are you running and what did you install on the robot controller? I am just confused that it worked yesterday maybe try restart the system |
|
this is robot controller version?? yes, rotot was worked well yesterday :( |
|
looks good to me. I would suggest a restart see if the error persists |
|
Does restart mean to turn the robot off and on again? If so, I think I did it at least 5 times. |
|
hm okay |
|
maybe you are somehow using the wrong version of the FRI. Did you specify |
|
Probably so. I am using the code above with some modifications. |
|
but the driver doesn't even connect right? |
|
Yes, it doesn't seem to be able to connect in the first place. |
|
have you tried running the raw FRI? |
|
how to running raw FRI? |
|
suho@suho: above code is error code in terminal |
|
I mean you can essentially see here [ros2_control_node-1] [INFO] [1715621420.902732391] [lbr_ros2_control::SystemInterface]: Waiting for robot heartbeat [5/10]. Port ID: 30200.that no connection is established ever |
|
could you please share how you built this project? |
|
There is nothing called project. Using ROS is all about moving the robot using the path planning code mentioned above. This is a project that reads magnetic field sensor values into another laptop after movement. |
|
I am wondering how you compile this project |
|
I am conducting experiments to optimize the arrangement of eight electromagnets in an electromagnet system to maximize force and torque, and validating this through experiments. Is this information do you want information? |
|
no. What steps did you follow to build this project? |
|
Thank you for your kind reply. I came back today and tried to communicate and confirmed that the error was gone. |
|
awsome! Make sure you re-install the
source /opt/ros/humble/setup.bash
export FRI_CLIENT_VERSION=1.15
mkdir -p lbr-stack/src && cd lbr-stack
vcs import src --input https://raw.githubusercontent.com/lbr-stack/lbr_fri_ros2_stack/humble/lbr_fri_ros2_stack/repos-fri-${FRI_CLIENT_VERSION}.yaml
rosdep install --from-paths src -i -r -y
colcon build --symlink-install
source install/setup.bash
ros2 launch lbr_bringup bringup.launch.py model:=med14 sim:=false moveit:=true |
Hi mhubii,
Until yesterday, I was able to operate the robot well. (POSITION_CONTROL - POSITION & terminal: ros2 launch lbr_bringup bringup.launch.py model:=med14 sim:=false moveit:=true)
However, today when I try to communicate with the robot, I'm experiencing CK_COMPOUND_RETURN_ERROR as shown in the picture of the SMART PAD below.
Do you happen to know under what circumstances this ERROR occurs?
Thank you
The text was updated successfully, but these errors were encountered: