Gantry with 2 Synced Y Axis motors, X axis jogging not possible when not homed

Ok, I thought that this gantry_jog must have been depreciated since the manpage did not say anything about it.

How would G10 help me ? I don't understand.

I made another step ahead. I integrated 2 buttons for jogging Plus and Minus in the GUI. Connected them to the joint 1 and 2.

net gantryjogplus halui.joint.1.increment-plus halui.joint.2.increment-plus  pyvcp.Gantryjogplus
net gantryjogminus halui.joint.1.increment-minus halui.joint.2.increment-minus  pyvcp.Gantryjogminus
 

Now I set the Jog Speed and the Jog increment higher than 0 and by clicking on the buttons both gantry joints are moving the same distance and the same speed even when not homed! This is a win.

However, the move is somehow not fully synced. It seems like that one joint is follwing the other one delayed. Not sure why that is happening.

mBender wrote:

However, the move is somehow not fully synced. It seems like that one joint is follwing the other one delayed. Not sure why that is happening.

I see the same here, most probably because halui is userspace rather than realtime.
Attached is a PyVCP panel and postgui halfile with a simulated MPG that seems to work, it is not very pleasant to jog with though...

Would user space make sense if I make like a single step 5mm long and the movement is within the 5mm not synced?