You probably didn't read the whole thread—this is what it's all about
I’ve had problems with my lathe after running ‘reference’ in Flex GUI.
When both axes are homed, I can jog the X-axis without any problems.
But the Z-axis doesn’t move. If I run ‘unhome’ on the X or Z, I can jog the Z-axis.
I switched to Probe Basic and it works as intended with the same INI file
no problems with jogging once the axes are homed.
I checked with HalShow, and the difference between Flex GUI and PB was that the telop
function worked on both axes in PB but only on the X-axis in Flex GUI.
In Flex GUI, the X-axis is 0 and the Z-axis is 1. When the axes are not at home, jogging works normally. Where should I look for the fault?
On a lathe, the Z-axis is No. 2, and on a mill, it’s No. 3. I think that’s where the problem comes from—previously, I had to have two Z- and two Z+ buttons; on one pair, I used jog_1_pb,
and on the other, I used jog_2_pb, which I used when the axes were homed, and it worked. When the axes weren’t homed, I had to use jog_pb_1 to move the axis.
So why does it work normally in Probe Basic but not in Flex GUI?
As I mentioned earlier, in FlexGui, the Z-axis = 2 on a milling machine, and on the lathe, Z = 1. If I change Z to Y in the ini file to the following:
KINEMATICS = trivkins coordinates=xy
COORDINATES = X Y
[AXIS_Y]
Then I can jog the Z-axis after homing, just as it’s supposed to work,
but of course the lathe won’t run because it requires XZ.
So now I hope you’ll make the necessary changes so it works correctly.
