Developments on my Home built 5C CNC Lathe - new spindle and progress on the ATC

Understood, thanks for the clarification. And good luck with modifying the kinematics.

I guess on reflection that if one is going to spend quite a bit of time writing/developing/testing software, the time would be better spent modifying LCNC rather than a post processor that would not be CAM-agnostic.

At the very least, your live-tool lathe would be useful for C-axis indexing as-is.

We will see how we go with 'PolarKins".....

Can somewhere tell me how do I use  (in INI file under [EMCIO] ) TOOL_CHANGE_POSITION = XYZ on a lathe? - ( No Y..)
Or must I use G30?
EDIT - Sorted the above issue - Just entered 0,0,0 and the ATC went to home as I wanted...

I am having a hard time with tool table setup...
Regardless of choice of touch-off ; to workpiece or to fixture - selection , there appear two touch off options in AXIS Manual page - 
Touch Off
and 
Tool Touch Off
Neither one when selected allows selection of the tool-table update option in the coord update field.
IAW, I cannot select 'tool-table' in the coordinate system drop down box ( as should appear in the attached image)- it does not exist - only a bunch of G's ( G54....G92)
Am I in the incorrect coordinate system? How do I verify?
 

 

Look into G43 to load and read in the tools.

Quick search brought this up. Is in the docs too.

gnipsel.com/linuxcnc/g-code/gen05.html

Post Deleted - redone under main topic heading..Sorry..

Good Progress on the lathe and Polar kinetics...We kindly request some assistance and advice on a few things though please....

First the Polar Kinetics :
We are using custom kinematics based on userkins. The reason for requiring the custom kinematics is that we need to execute different kinematics depending on whether or not Polar Coordination Mode is enabled. (It is enabled using G12.1 and disabled using G13.1).
Linux CNC does not currently support Polar Coordination Mode.
The kinematics themselves are functioning.
However the problem is in knowing which kinematics should be active – something which could possibly be set in the iflags & fflags parameters passed to the forwardKinematics  and inverseKinematics functions.
We have remapped the G12.1 and G13.1 gCodes to .ngc files. These remappings are being executed as expected.
What we however need advice on is how to make the link between the .ngc file execution and the value of iflags / fflags sent to the kinematics. If this is not feasible, what alternative ways are there of achieving the same end result?

Second -  The G02/G03 Arc functions:

Nothing to do with the Kinetics question above...
I have joined the many many people traumatised by G02/G03.   My CAM package - Rhino-Cam from Mecsoft, generates the Gcode, to 5 decimal places, metric.
LCNC fails with the usual - Radius to end of arc differs from radius to start.....
with the other details after, and then the abs error value = 1.21
I am not ready to doubt the CAM software just yet...I set the [RS274NGC] CENTER_ARC_RADIUS_TOLERANCE_MM in ini to 2mm, but same error appears.
Cutting tool comp is off, tool tip radius is set to 0mm.
I can post details of the part, the Gcode, etc if needed. The part is simply a 20mm OD shaft, the end being machined into a hemisphere. The tool path follows the hemisphere arc in roughing, so the 1st arc is very small at the corner of the shaft. The last arc is the actaull face of the 'ball' and it parses correctly. 
Active G-codes include but not only -  G7 G18 G91.1 G43

Thank you for your valuable info! We had implemented the re-map along the the lines in your referred docs, and got it to work yesterday! But rather comforting to have what we did confirmed as the way to do it! Thank You.

So we can issue a G12.1 now - and that's where the complications arise...
We have joint following errors, etc all due to the kins being entered into poorly. We suspect(ed) this is due to parameters not set up in the transfer, etc, and your words 'switchable kinematics' are the key! We are digging in there now and will see how we go. Again - Thank You! This is deep in LCNC's heart we are playing and we have a lot to learn.
Just to be sure re your first sentence - We are using LinuxCNC 2.8.2 Debian 10 Buster PREEMPT-RT ISO download from the LinuxCNC website - is that what you mean by 'master' ?
Joe

Ok, so still a lot to learn here!
What is 'master' and what do I need to do to load 'master'?
And how will that effect what I have done already WRT my C axis ( component by Andy), the ATC component we did, etc?

Edit:
Do I need switchable Kinematics? or is there another way to pre-set the inputs so that there is no joint movement demand on entry.
Also, I suppose, what are the implications of sticking with 2.8 in terms of future updates, ie, when 2.9 becomes the general user download?
Seems I should really move to 2.9..