03-19-2021, 11:04 AM
Hi there
As soon as you generate a robotprogramm with a postprocessor, there will be generated a temporary file in the %TEMP% folder of windows. In this file, all movements with the points are written down. I need to find out, how the point coordinates in the RoboDK-Simulation are translated to this tempfile.
This is a little snippet of my code:
The commented out coords are the coords, which I've set in the RoboDK, and which I am moving to within a python-program. And I can see that the second argument in the MoveFunction includes the joint-angles. But how converts RoboDK for example the first point #(330,190,340,-150,10,75) to p(330,190,340,-73.4728,26.362,-162.149)?
I already found out, that the frame of the roboter does not have any affect on this, an that the cartesian coords always stay the same. But the Euler change sometimes, and sometimes they don't. What is the algorithm behind all of this?
Thanks
Janis
As soon as you generate a robotprogramm with a postprocessor, there will be generated a temporary file in the %TEMP% folder of windows. In this file, all movements with the points are written down. I need to find out, how the point coordinates in the RoboDK-Simulation are translated to this tempfile.
This is a little snippet of my code:
Code:
#(330,190,340,-150,10,75)
r.MoveJ(p(330,190,340,-73.4728,26.362,-162.149),[20.7222,41.5156,72.9095,-147.945,-48.7626,80.5139],[0,0,1])
#(290,130,220,90,60,-90)
r.MoveL(p(290,130,220,-30,90,0),[27.7485,61.2473,96.4928,59.7165,-78.3375,-19.0939],[0,0,1])
#(290,-140,225,0,90,0)
r.MoveL(p(290,-140,225,0,90,0),[-39.4803,58.2526,103.261,-40.977,-75.8336,12.001],[0,0,1])
#(290,10,175,-180,50,180)
r.MoveJ(p(290,10,175,-180,50,180),[-5.98706,58.6418,109.634,-7.3982,-38.3544,1.95735],[0,0,1])
#(330,190,340,-155,5,70)
r.MoveJ(p(330,190,340,-68.4838,21.7227,-166.379),[21.0954,42.9283,69.5598,-154.125,-55.9113,79.7147],[0,0,1])
#(290,130,220,85,55,-95)
r.MoveL(p(290,130,220,-107.563,80.4639,-72.4373),[28.2842,62.5264,94.4328,64.0265,-82.5098,-29.727],[0,0,1])
#(290,-140,225,-5,85,-5)
r.MoveL(p(290,-140,225,-63.3913,78.8225,-63.3913),[-39.5291,59.692,102.475,-40.3418,-81.3049,1.45943],[0,0,1])
#(290,10,175,175,45,175)
r.MoveJ(p(290,10,175,-168.118,43.9587,-168.118),[-4.94745,57.8235,108.95,0.0450415,-31.9916,-12.0677],[0,0,1])
The commented out coords are the coords, which I've set in the RoboDK, and which I am moving to within a python-program. And I can see that the second argument in the MoveFunction includes the joint-angles. But how converts RoboDK for example the first point #(330,190,340,-150,10,75) to p(330,190,340,-73.4728,26.362,-162.149)?
I already found out, that the frame of the roboter does not have any affect on this, an that the cartesian coords always stay the same. But the Euler change sometimes, and sometimes they don't. What is the algorithm behind all of this?
Thanks
Janis