Weiler E30 Lathe retrofit?

Hi Andy,
By using halui.axis.Z.plus/minus, can I achieve feed per rev?
The machine would still be in manual mode, so mpg's would be active.
Also the sinumerik had taper turning, when you were toggling a button on the controller, and when taper turning was active, actuating the joystick would move both axes so that it would cut a taper.
I have achieved all that functionality with my implementation and it seems to work so far.
I think the nicest way of obtaining this would be with a custom component, but I don't have enough c/c++ skills for that.

I am now trying to figure out Constant surface speed mode.
When G96 D2500 S250 is active, should the spindle accelerate/decelerate when jogging the X axis with the MPG?

I know that a realtime component is needed for that, but I have done it is just some calculus that based on an angle, it determines a point in the machine bounds, then it issues a G1 command to that point, I do that in my software when the joystick is actuated, and when it returns to neutral, I set feed-hold=1, then switch to manual mode and when it switched to manual mode, I set feed-hold=0. The stopping logic is done in ladder.
I have found that for most of repair jobs, I am more efficient with a manual lathe so I want to keep those capabilities as close as the original controller had them.
So far it seems that my logic works, but I was thinking that a c++ realtime component for that would be the way to go, that way it could be reused by others that have servo-conventional lathes.

And for some reason, G96 does not seem to work for me, I have the spindle encoder linked, I have set the X0 of the tool at the center of the part..no idea why its not variating the speed...

I will have automatic cycles too, and for repetitive operations, I will use those.
The lathe macros will be a great source of inspiration, but I am kinda reinventing the wheel here.
My lathe UI is written in Kotlin & Compose for Desktop. I am using JNI to communicate with the linuxcnc, and I've already built most of the functionality that already exists in the linnuxcnc python library.
The reason I decided to go with Kotlin instead of python, is that at work, I am an Android developer, and the new Compose framework used to build UI for Android, is also available for multiplatform development.
I need to learn that new framework for job purposes, but don't wanna do it through useless hello world apps. So besides working in an object oriented environment, I am also achieving the learning part by doing something useful to me.

I have discovered why G96 does not work as I expected.
I start the spindle by linking the inputs from spindle lever switch to halui.spindle.0.reverse or halui.spindle.0.forward. The spindle starts fine in both rev of fwd, but g96 does not work correctly
Then if I type in MDI an M4 or M3, the CSS starts to work properly.
Is there a way avoid sending an M3 or M4 command in order to activate CSS and still rely on the physical lever switch?