On detail. It is important to set you TCP at the glue dispensing point.
The Z axis of the dispensing tool should be vertical during dispensing with the axis point down.
There are 2 set nodes where you need to set your TCP.

Here below are the settings I use for this concept.

All relative moves are using "active TCP".

If my TCP is changing each time the code is run (I use a TCP detect method for the syringe), is there any additional code I need to add to this? Your method worked for me until I added a set tcp command within the code.

@aduban
Un your case, you have to save the TCP you calculated in a variable. Keep this variable as a reference.
Let say that you name this variable: myTCP

Replace the Set command by the following script command:

set_tcp(myTCP)

Thank you. What about rTrajectoryRef feature point? I am using your easy to edit relative programming article (https://dof.robotiq.com/discussion/2296/camera-easy-to-edit-relative-trajectory-with-robotiq-wrist-camera#latest)

and when I initially set rTrajectoryRef under the master setup folder, I am setting it with a certain TCP, but if my TCP is changing, don't I also need to change this reference point feature to reflect the changing TCP?

Thanks!

@aduban
What is important is that you use the same TCP when you initially set rTrajectoryRef under the master setup folder and when you set relative waypoints.
After that if the TCP change that should not be an issue.

Why to you need to change your TCP on each program execution ?

I found that there is a necessary modification to do in my program in the position where is applied the Z offset correction of the TCP to keep same orientation.

In my first program I directly edit the Z rotation of the TCP but this works only if the Z axis of the TCP is same as the flange Z axis. I heard about cases where the dispensing tool Z axis is not identical to flange Z axis.



Something could also be improved with the toolORef waypoint which is use as a tool orientation reference. This point is place in a moveJ in the before start program but there is not need to move the robot at this point in the before start. It make more sense to use a feature point instead.





I attach the updated version of the program to this post.

I found that there is a necessary modification to do in my program in the position where is applied the Z offset correction of the TCP to keep same orientation.

In my first program I directly edit the Z rotation of the TCP but this works only if the Z axis of the TCP is same as the flange Z axis. I heard about cases where the dispensing tool Z axis is not identical to flange Z axis.



Something could also be improved with the toolORef waypoint which is use as a tool orientation reference. This point is place in a moveJ in the before start program but there is not need to move the robot at this point in the before start. It make more sense to use a feature point instead.

Hi @bcastets!

I'm trying something similar as your project. I'm using a UR10e and a Wrist camera to first detect the object, extract object_location and apply x,y,z data to a Point Feature. After the camera detects the object, the Point Feature coordinates do not get updated. I made sure the specified feature inside MoveL is the right one, and that if the object is detected, the object_location data is assigned to the Point Feature variable.
However, if I move the object that I'm detecting for a few milimeters in either direction, the robot TCP does not move to the updated one, but still to the previously defined one inside the Installation-Features-Point Feature (Teach this Point). I've looked through your attached code but coulnd't find any conceptual differences.