-
Notifications
You must be signed in to change notification settings - Fork 417
Closed
Description
Summary
Launching
roslaunch ur_robot_driver ur10_bringup.launch robot_ip:=10.31.1.70 \
kinematics_config:="${HOME}/left_ur_calibration.yaml" debug:=true
display
Thread 1 "ur_robot_driver" received signal SIGSEGV, Segmentation fault.
ur_driver::rtde_interface::RTDEClient::negotiateProtocolVersion (this=this@entry=0x55555585c9f0)
at /home/gaetan/ur_ws/src/Universal_Robots_ROS_Driver/ur_robot_driver/src/rtde/rtde_client.cpp:87
87 if (!tmp_version->accepted_)
and then quit due to missing required process.
Version
- ROS Driver version: commit 8d8e909
- Affected Robot Software Version(s): Polyscope 3.13
Impact
Cannot control robot
Issue details
Use Case and Setup
UR10 CB3.1 Series with default Polyscope version 3.2.21545 upgrading with a new USB key with version 3.13 on it
Actual Behavior
Segfault then quit due to missing required process
Moreover, launching
roslaunch ur_calibration calibration_correction.launch robot_ip:=10.31.1.70 \
target_filename:="${HOME}/left_ur_calibration.yaml"
works but says
[DEBUG]: Invalid robot package type recieved: 24
[DEBUG]: Invalid robot package type recieved: 23
[DEBUG]: Invalid robot package type recieved: 5
cannot say if this is linked or not
Metadata
Metadata
Assignees
Labels
No labels