TCP 5-axis kinematics

dgarrett wrote: @plopes9000

please keep me updated on the success of this code making it in?

commit to the master branch today:
github.com/LinuxCNC/linuxcnc/commit/5ea5...6e3759f85bb4037869f7

Would be good if you try the master branch and report

So sorry dgarret, had not seen your message ... I’m on vacation but will be back home this coming weekend and can then test and report.

plopes9000 wrote:

dgarrett wrote: @plopes9000

please keep me updated on the success of this code making it in?

So sorry dgarret, had not seen your message ... I’m on vacation but will be back home this coming weekend and can then test and report.

@dgarrett, I built and tested the commit to the master branch github.com/LinuxCNC/linuxcnc/commit/5ea5...6e3759f85bb4037869f7, and can now report it as successful - thank you !

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.

Good work, I think i need to update my linuxcnc as well.
TCP switching after pre-rotation seems to work well.


I have posted rotate macro in this thread earlier.
Look it as well.
Problem in my rotate macro is that it only translates active zeropoint to correct location.
If you have multiple zeropoints around part, other than active one will shifted wrongly.

jsskangas wrote: Good work, I think i need to update my linuxcnc as well.
TCP switching after pre-rotation seems to work well.


I have posted rotate macro in this thread earlier.
Look it as well.
Problem in my rotate macro is that it only translates active zeropoint to correct location.
If you have multiple zeropoints around part, other than active one will shifted wrongly.

Thank you jsskangas.

Yes I did miss the macro you posted, which page?

Hello

Page 4

file is rotate.ngc