I am trying to create a linear movement combined with a 540deg J6 rotation.
The TCP is (0,0,0,0,0,0), the linear movement is along Z_tool in tcp tool base and the rotation is along Rz_tool = J6.
I created a start_target and then created a end_target. The end end target has been defined manually using the displacement in the tool base.
I make then a moveL(end_target)… and impossible to get my full 540 deg rotation. The robot goes to the shortest way and make only 180 deg rotation displacement.
Is there a trick to create this kind of move ?
Thanks for your help
I would suggest trying breaking up the motion into smaller moves, rotating say 90o at a time. Hopefully this will prevent the robot from leaving out the extra 360o.
Movel is a point to point move and takes the shortest linear path between the two point with no consideration to the joint angles used when the point was taught.
As @sam.hilton said you will need to break up your points along the way to get it to go to all of them
Hi Florent. I just went through something similar wanting to rotate around a Z Axis in a specific direction until Wrist3 reached a position. My first attempts showed that Move commands appear to always be shortest-path (as mentioned above). --Leland (placing signature here since this post is a bit long)
The solution is to use a “direct drive” command. UR currently has two:
- speedl(), which directly drives linear motion and rotation
- speedj(), which directly drives joints.
The commands above are only accessible in a script instruction (line or file, but they don’t appear in the Polyscope “Function” list). A single-line script instruction works well for this in Polyscope.
I put a test program together that makes the motion you’re looking for, although the current study is in BaseFRAME. I’m working on a ToolfRAME solution but am posting my initial results here so you can follow the progression. The ToolFRAME solution might be a bit complex (like taking a snapshot of the TCP, converting that into a FeaturePOINT or FeaturePLANE, and then using that as the FRAME for the speedl() solution posted here; this is fine as long as it works but something simpler is better). I’ll report back in once I have some results using the ToolFRAME.
Lines in bold are the core speedn() logic. Note that I use a thread to continuously monitor the arm’s position in both joint and cartesian space. This allows the “Loop Until” condition to operate.
Indents in this forum platform are squirrelly and HTML strips out multiple spaces and multiple ellipses (…), so I had to create home-made indents.
InitRBT is a folder.
–Loop ActvCPOS > 0.350
This solution is based on a comprehensive answer to a slightly different question HERE: (Move (JOG) along Base or Tool axis).
Some usage notes plus the entry from the UScript manual:
- The [xyz, Rxyz] argument is a vector array/list. It MUST be enclosed in square brackets. If you get an error saying that speedl or speedj “only take 4 arguments”, then you’ve left out the square brackets.
- You have to nest the speedn() command in a loop.
- condition the loop on your stop condition, such as having traveled a certain distance in Z (you’ll need to add code to compare your start position and to your stop position).
- You MUST check “Check expression contunually” on the Loop instruction configuration page. The loop will execute up to the first speedn() instruction and the “Loop while” condition breaks execution out of the loop at that first speedn() instruction. Nothing in the loop after the first speedn() will execute.
- Much of the “non-core” code is for convenience in testing, making the robot reset itself automatically and return to the start point.
speedl(xd, a, t, aRot=’a’)
[Controls Tool speed]
DESCRIPTION: Accelerate linearly in Cartesian space and continue with constant tool speed. The time ‘t’ is optional; if provided the function will return after time ‘t’, regardless of the target speed has been reached. If the time ‘t’ is not provided, the function will return when the target speed is reached.
xd: tool speed [xyz (m/s), Rxyz (rad/sec)] (spatial vector)
a: tool position acceleration [m/s^2]
t: time [s] before function returns (optional)
aRot: tool acceleration [rad/s^2] (optional), if not defined
a, position acceleration, is used
EXAMPLE COMMAND: speedl([0.5,0.4,0,1.57,0,0], 0.5, 0.5)
– xd -> Tool speeds of: x=500 mm/s, y=400 mm/s, rx=90 deg/s, Ry and Rz=0 mm/s
– a = 0.5 rad/s^2 -> acceleration of the leading axis (shoulder is this case)
– t = 0.5 s -> time before the function returns
I tried both solutions :
I broke my trajectory in small step. It works fine but i did’nt find the way tho play the move continuously.I tried MoveL and MoveP. What is important in my proess is to get a conitnuous linear speed synchronised with the rotation.
The solution of “71b0c3d0191a551ba2ce” works fine ! I created my move along the Y axis.
If you have found a way to project the rotation vector in the tool frame, I am interested…
Thanks a lot for your time !