OLD Lathe conversion to a CNC

This looks very odd. It looks like a gmoccapy glitch, but can you try the same sequence in:
1) The gmoccapy lathe sim config
2) The axis lathe sim config
And see if you see the same behaviour?

I guess there is a problem with the hall configuration. Today I broke 2 carbide inserts. After 10 made parts the axis started to move with a larger feed. But not too much, maybe 20-30% more. I tried in simulation but I don't know how to load my configuration into the simulation. There is no problem with the sample configurations.

Not sure if it's related, but here is a similar issue, also using gmoccapy:

forum.linuxcnc.org/20-g-code/44739-g96-issue
 

It seems that the two problems are related. I just have to try another gui

Today I ran some more tests. I can now reproduce the issue described in the other thread with 100% consistency. I noticed that when the Z-axis is moving, G96  doesn't seem to be working. I recorded a video showing that the spindle speed doesn't change at all during the movement.



PS. I think there might be something wrong with the HAL configuration. I just noticed that when starting LinuxCNC, I need to go into the calibration settings and re-save the PID values for the spindle (I enter test). If I don’t do that, the PID control is soft– under higher spindle load, it triggers a hold  .Also, if I leave LinuxCNC running idle (without running a program) for about an hour, and then start program execution again, the axis movement speed during a G1 command is once again higher than what was set.

Today I started the program with the axis graphical interface. No change, the problem remains. Could someone check the HAW connections?

this problem also exists : " ... I just noticed that when starting LinuxCNC, I need to go into the calibration settings and re-save the PID values for the spindle (I enter test). If I don’t do that, the PID control is soft– under higher spindle load, it triggers a hold .Also, if I leave LinuxCNC running idle (without running a program) for about an hour, and then start program execution again, the axis movement speed during a G1 command is once again higher than what was set."