Manual robot-camera Calibration

Before controlling the robot to follow a detected object, it is required to know the position and orientation (pose) between the robot and the camera.

To not waste much time on this task, let's perform a manual calibration.

It is important to know that this manual calibration is far for being accurate, but for the demonstration purpose, a manual calibration is more than suitable.

Configuration & Installation:

  • robot: UR10e
  • camera: Intel RealSense D435 (RGB-D camera)
  • Install the External Control URCap on your UR10e controller. See this post to further instruction on how to do it.

  • Clone this repository and install every required dependency. Every step of this calibration will work on top of this repository. See the ReadMe of it, or see this post for further instructions.

Performing manual calibration:

  1. Using the Free Drive mode on the UR10e controller Teach Pendant, move the TCP (tool center point) to the RealSense camera mass center:

     
     
  2. Run roslaunch ur_robot_driver ur10e_bringup.launch robot_ip:=192.168.56.2

  3. Run the external control program on the teach pendant:

    Click on Program + URCaps + External Control + Press "play"

    tp5

    At this point, you should get the message "Robot connected to reverse interface. Ready to receive control commands." printed out on your terminal window.

  4. Run rosrun tf tf_echo /base_link /tool0_controller

    You will see the Translation and Rotation (in quaternions and rpy) Values:



  5. Copy the values of X Y Z (translation) and the values R P Y (radians) and paste them on catkin_ws/src/larcc_interface/ur_description/urdf/ur10e.xacro
     
    Create a <origin> section inside the <xacro: realsense2_camera> section, as follows:
     
    <origin xyz="X Y Z" rpy="R P+{pi} Y"/> 

    You should add pi (3.14159) to the second rotation value (P), otherwise it won't work!

    Here is an example:
     

     In this case, 3.30 = 0.188 + pi


    That is it! The UR10e is calibrated with the RealSense RGB-D camera. Now we can work on the object tracking and following.




     

Comments

Post a Comment

Popular posts from this blog

Real-time UR10e following a tracked object

Image
For a first trial, it was developed this demonstration of a real-time followed object that is being tracked using one RGB-D camera (Intel RealSense D435).   As seen in this previous post , ViSP is used to process the images acquired by the RealSense RGB-D camera and to continuously track the object . A TCP/IP Socket Connection is established (inside the same computer) between ViSP and ROS . This socket communication is responsible for bringing the geometric transformation between the camera and the object to the ROS environment. This previous post describes with more detailed information this connection. Besides the transformation between the camera and the object, it is also required to know the transformation between the robot and the camera . For the robot to understand the position and orientation of the object in reference to the robot himself, this transformation becomes crucial. For getting it, I performed a manual calibration , as described in this previous post . Finally,
Read more

RGB-D tracking + UR10e following & picking/placing

Image
Following the first use case described in this last post , the result of the experiment can be seen in this video: There are still several improvements to be made to this job1 task: The job should wait for the response of each controller before sending the next request The robot xacro should be extended to include every object that compose the real scenario  The procedure should have an interactive way of telling the robot that is time to pick up the object The use case should ensure that the object pick was successful (or not) This issues can be followed here .
Read more

RGB-D tracking (ViSP/ROS) - 2nd demo

Image
  Using the infrastructure described in my last post , where ViSP communicates with ROS via a TCP/IP socket connection, this is the result of the RGB-D tracking:     I believe that this result is good enough for now. On the ROS side, we simply have the robot state publisher (responsible for the camera links) and the client node (responsible for the woodblock link). These two agents are continuously publishing the transformations.     One issue that we can already notice is that, in ROS, now we have neither the RGB image topic nor the depth map topic, which restricts us to create the pointcloud where we could clearly see the woodblock. A possible way around this issue is to send the images through the socket communication channel as well. For now, let's consider this step halfway concluded. Now it's time to control the robot!  The challenge for the next few days is to remotely control the UR10e collaborative robot.  
Read more