TCP/IP connection: UR10e - External PC

To use any of the features that have been published on my recent posts (UR10e external control, gripper external control, etc), it is required to have the cobot connected to my external computer. 

For that an Ethernet cable is connected from the UR10e controller to my PC, using a TCP/IP communication protocol. 

For enabling that communication,

On UR10e Teach Pendant:

  1. Click on Menu (top right corner) + System + Network
  2. Configure:
    1. Network method : Static Address
    2. IP address: 192.168.56.2
    3. Subnet mask: 255.255.255.0
    4. Default gateway: 192.168.56.2
  3.  Click on Apply

    tp4


  4.  Disable EtherNet/IP fieldbus:

    Installation > Fieldbus > EtherNet/IP > Disable

    tp5

 

On External Computer: 

    After you connect the cable, you need to configure the IPv4 like this:

tp6

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