TCP 5-axis kinematics
25 Jul 2019 23:13 #140587
by andypugh
I thought that your video was very instructive about what TCP is, and the Linuxcnc home page needed a new Showcase.
So your video is now on the front page of LinuxCNC
Replied by andypugh on topic TCP 5-axis kinematics
Finally, see attached test gcode file and video.
I thought that your video was very instructive about what TCP is, and the Linuxcnc home page needed a new Showcase.
So your video is now on the front page of LinuxCNC
Please Log in or Create an account to join the conversation.
26 Jul 2019 16:15 #140660
by plopes9000
Replied by plopes9000 on topic TCP 5-axis kinematics
Thanks Andy
Please Log in or Create an account to join the conversation.
29 Aug 2019 17:26 - 30 Dec 2019 22:13 #143582
by plopes9000
Replied by plopes9000 on topic TCP 5-axis kinematics
Here's my update regarding the 5 axis.
Just before I went on vacation and since I arrived back, I have been working on a complete workflow for 5 axis.
With TCP but without an easy to use 3+2 setup its still a pain to rough out before the TCP operation.
Enter Dynamic Work Offsets - see Haas DWO G254 - link .
I came across a 4 axis macro ( link ) by "thesidetalker" and based on that design implemented a 5 axis version - see attached files (dwo_on/off) remapped as below:
By moving the 5 axis params from the hal file to the ini file, I only have to maintain these values in one location, serving both the xyzac-trt-kins module and the dwo_on/off gcode files.
Hence a fairly clean setup.
On a side note, I had to update the component axiszeropulserotposition to ignore small changes of direction in the count, i.e. more robust check using what I called a deadband property. I have updated my post on page 13.
I renew my offer to make all this (implemented this way or in better ways) part of the dev branch ... just need a dev sponsor
Totally forgot to talk about the Fusion360 post processor which had to see major redesign - see attachment.
Just before I went on vacation and since I arrived back, I have been working on a complete workflow for 5 axis.
With TCP but without an easy to use 3+2 setup its still a pain to rough out before the TCP operation.
Enter Dynamic Work Offsets - see Haas DWO G254 - link .
I came across a 4 axis macro ( link ) by "thesidetalker" and based on that design implemented a 5 axis version - see attached files (dwo_on/off) remapped as below:
<....>.ini
[RS274NGC]
...
REMAP=G55.4 modalgroup=1 ngc=dwo_on
REMAP=G55.5 modalgroup=1 ngc=dwo_offBy moving the 5 axis params from the hal file to the ini file, I only have to maintain these values in one location, serving both the xyzac-trt-kins module and the dwo_on/off gcode files.
<...>.ini
[XYZAC_KINS]
Y-OFFSET = -0.15
Z-OFFSET = -27.59
X-ROT-POINT = 407.565
Y-ROT-POINT = 154.229
Z-ROT-POINT = -225.9
<...>.hal
net :tool-offset motion.tooloffset.z xyzac-trt-kins.tool-offset
setp xyzac-trt-kins.y-offset [XYZAC_KINS]Y-OFFSET
setp xyzac-trt-kins.z-offset [XYZAC_KINS]Z-OFFSET
setp xyzac-trt-kins.x-rot-point [XYZAC_KINS]X-ROT-POINT
setp xyzac-trt-kins.y-rot-point [XYZAC_KINS]Y-ROT-POINT
setp xyzac-trt-kins.z-rot-point [XYZAC_KINS]Z-ROT-POINTHence a fairly clean setup.
On a side note, I had to update the component axiszeropulserotposition to ignore small changes of direction in the count, i.e. more robust check using what I called a deadband property. I have updated my post on page 13.
I renew my offer to make all this (implemented this way or in better ways) part of the dev branch ... just need a dev sponsor
Totally forgot to talk about the Fusion360 post processor which had to see major redesign - see attachment.
Please Log in or Create an account to join the conversation.
Time to create page: 0.126 seconds