<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en" xmlns="http://www.w3.org/2005/Atom"><title>Recent posts to Trafo 6DOF</title><link href="https://forge.codesys.com/forge/talk/Motion/thread/16e1f0327f/" rel="alternate"/><link href="https://forge.codesys.com/forge/talk/Motion/thread/16e1f0327f/feed.atom" rel="self"/><id>https://forge.codesys.com/forge/talk/Motion/thread/16e1f0327f/</id><updated>2025-12-15T17:17:05.447000Z</updated><subtitle>Recent posts to Trafo 6DOF</subtitle><entry><title>Trafo 6DOF</title><link href="https://forge.codesys.com/forge/talk/Motion/thread/16e1f0327f/?limit=25#fe25" rel="alternate"/><published>2025-12-15T17:17:05.447000Z</published><updated>2025-12-15T17:17:05.447000Z</updated><author><name>rett84</name><uri>https://forge.codesys.com/u/rettore84/</uri></author><id>https://forge.codesys.comd928614c97a02d617407fef2b812d23cdcfbbb21</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;I didn't have a single reference. I used several sources through online reaserach.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Trafo 6DOF</title><link href="https://forge.codesys.com/forge/talk/Motion/thread/16e1f0327f/?limit=25#e769" rel="alternate"/><published>2023-03-13T14:09:20.596000Z</published><updated>2023-03-13T14:09:20.596000Z</updated><author><name>intvenkat</name><uri>https://forge.codesys.com/u/intvenkat/</uri></author><id>https://forge.codesys.comff9aadb7a2f6cc4c76a06380dfb0f3008721a2e2</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Hi&lt;br/&gt;
Actually I am also facing codesys Kinematic issues , and upon searching online I found your Post&lt;/p&gt;
&lt;p&gt;Thanks for sharing this here&lt;br/&gt;
I tested your code Fk is matching with RoboDk, in IK the values are sometimes matching with RoboDK &amp;amp; sometimes its not maybe due to elbow positions&lt;br/&gt;
I think euler angles are not matching correctly, Could you please provide the reference for the code you have developed, it would be great help&lt;/p&gt;
&lt;p&gt;Thanks &lt;br/&gt;
Venkat&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Trafo 6DOF</title><link href="https://forge.codesys.com/forge/talk/Motion/thread/16e1f0327f/?limit=25#b8b9" rel="alternate"/><published>2020-05-18T22:47:40.623000Z</published><updated>2020-05-18T22:47:40.623000Z</updated><author><name>rett84</name><uri>https://forge.codesys.com/u/rettore84/</uri></author><id>https://forge.codesys.com2018b65fa428c7e206f4782c2346f5d51099922e</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Due to the lack of response from 3S-Codesys, I decided to write my own FBs to perform this task. It took me some time to learn FK and IK, but it was worth it. I had to write some auxiliary Functions as well. Some are redundant with what is included in the Robotics library. The matrix operations are two dimensional arrays instead of a single array.&lt;/p&gt;
&lt;p&gt;The FBs are not optimized, do not cover all the elbow configurations, and probably contain some errors, but they are a good starting point. I was using RoboDk to compare my results, and they seem to be consistent.&lt;/p&gt;
&lt;p&gt;Because 3S Robotics library is not open source I can't change the parameters of the Homogeneous Transformation matrix and this was the problem(I think). I described in my previous post.&lt;/p&gt;
&lt;p&gt;Attached my project archive. Go ahead and test it. Constructive comments are welcome.&lt;/p&gt;
&lt;p&gt;Next will be velocity control.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Trafo 6DOF</title><link href="https://forge.codesys.com/forge/talk/Motion/thread/16e1f0327f/?limit=25#f76b" rel="alternate"/><published>2020-04-24T16:32:23.085000Z</published><updated>2020-04-24T16:32:23.085000Z</updated><author><name>rett84</name><uri>https://forge.codesys.com/u/rettore84/</uri></author><id>https://forge.codesys.com36e8480bca7ff53c2ffc3ac4f7b1e6be129999db</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;I have to do a correction, I was using the DH parameters of a different variation of the IRB 1200, now with the correct DH parameters the TCP values match(reading from MC_GroupJOG2.Currentposition.c). But still something is wrong with the inverse kinematics calculation. &lt;/p&gt;
&lt;p&gt;I changed my approach, instead of using MC_GroupJog2, I used MC_MoveLinearAbsolute.  I moved the robot, from home(all joints at 0 deg, except J5 at 90 deg) in the simulation software(Robodk) to an arbitrary position, in linear mode along the Y axis, then using the Linear Absolute FB in codesys I moved to the same position:&lt;/p&gt;
&lt;p&gt;X: 451mm&lt;br/&gt;
Y: 385mm&lt;br/&gt;
Z: 807mm&lt;br/&gt;
Rot:&lt;br/&gt;
Z: 0 deg&lt;br/&gt;
Y': 180 deg&lt;br/&gt;
Z'': 0 deg&lt;/p&gt;
&lt;p&gt;I attached the final joints position in angles, of both in Robodk and the Codesys values. A nice feature of RoboDK is that i gives you all possible configurations results as well. &lt;/p&gt;
&lt;p&gt;You will see that the results from Codesys do not match with any possible configuration variation, presented in RoboDK(compare last two images). &lt;/p&gt;
&lt;p&gt;The absolute values of J2 and J3 do match but its signals are inverted, and J6 angle value in Codesys would only match if J4 was at -180 and J5 at -93(you can see all of this in the images).&lt;/p&gt;
&lt;p&gt;Question to Codesys: Is it possible to access the source code of the 6DOF inverse kinematics FB?&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Trafo 6DOF</title><link href="https://forge.codesys.com/forge/talk/Motion/thread/16e1f0327f/?limit=25#dd3f" rel="alternate"/><published>2020-04-20T18:37:10.647000Z</published><updated>2020-04-20T18:37:10.647000Z</updated><author><name>rett84</name><uri>https://forge.codesys.com/u/rettore84/</uri></author><id>https://forge.codesys.comd87246ec74ce377e3ea7564ff72cd6b07c8ddbde</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;I'm trying to figure out how to get a 6DOF robot to work with Codesys using its kinematics FBs. I'm not sure if my implementation is wrong or an actual bug with the FBs. &lt;/p&gt;
&lt;p&gt;To start I used  ABB 1200 parameters, this way I can compare the results of Codesys with proven results of an Offline Robot programming software(RoboDK). I'm using virtual drives to map each Axis.&lt;/p&gt;
&lt;p&gt;The results don't match, and the TRAFO 6DOF FB outputs values don't make sense. For example,  SMC_Trafo_ArticulatedRobot_6DOF is always at error, which is strange because its config comes from the Axis group parameters. However, I can Jog the Axis group using MC_GroupJog2. I know these two FBS are not related, but I wanted to compare the results between them.&lt;/p&gt;
&lt;p&gt;Also, when I jog the axis group in any X, Y or Z plane, with MCS as Coordinate System, the output angles direction of Axis 2 and Axis 3 move in opposite directions as I would expect from the simulation, plus the TCP XYZ does not match with what I see on the simulation. Even with all Axis at 0 degree, the X,Y,Z TCP does not match.&lt;/p&gt;
&lt;p&gt;Also what is interesting is that the result of the SMC_TrafoF_ArticulatedRobot_6DOF, Z coordinate, does not match with the Z value that I get on MC-GroupJOG2.CurrentPosition.c, again, Config is the same.&lt;/p&gt;
&lt;p&gt;To sum up I have 3 different results: from RoboDK, which I know is the correct one, the results from MC-GroupJOG2 and the results from SMC_Trafo(TRafoF)Articulated_6DOF. The last two should at least be consistent, but they are not.&lt;/p&gt;
&lt;p&gt;I have attached some images and I hope it helps to understand what I am explaining.&lt;/p&gt;
&lt;p&gt;I would appreciate it if someone could shed some light on what I found.&lt;/p&gt;
&lt;p&gt;Thank you.&lt;/p&gt;&lt;/div&gt;</summary></entry></feed>