I needed to do a manual cut using the console. I tested things out with a g1 x100 f2000 and it did what it was supposed to. The spindle moved right 100 mm (relative operation). I reversed that and got the spindle back to the starting point. I tried g1 z-3 f2000 expecting a relative movement but the spindle did an absolute movement and went down way past the 3 mm - it went to the absolute z=-3 position.
Why does one operation do a relative move and the other operation do an absolute operation?
I turned on the spindle (clicking on ‘spindle’ and clicking on ‘clockwise’) all fine.
I was going to adjust my spindle position but none of the normal jog functions worked. They were not greyed out, they just didn’t work. I turned off the spindle and tried again - no joy.
I went back into the console and tried some movement (G1) command and it worked just fine but still, jogging with the jog buttons did not work.
What am I missing here? Did I inadvertently lock the jogging function? How do I enable it again?
I decided that I needed to continue what I was doing and I reset the gControl. This gave me jogging functions again.
I turned on the spindle, jogged the head a bit down and jogged a long way while cutting the job - all good. I did that a couple of times and the damn thing locked out the jogging controls again. Direct command input worked fine but no joy on jogging x, y or z. Funny thing is, I hit the ‘go to z0’ key and it performed the action just fine. I tried jogging again - no dice.
It is my opinion that there is something hinky (technical talk) happening with the gSender jog controls.
Did you send G91 before starting the test commands. I don’t see how not setting it would cause all those problems but you didn’t mention setting G90 or G91 so I thought I’d ask.
No, neither G90 nor G91 was sent. I would have expected both axis to behave the same - either relative movement or absolute movement. Having one axis go relative and the other go absolute just doesn’t make sense unless each axis maintains their own register as to which mode to use. As far as I know that isn’t a thing.
@Jens when you go to jog and it’s not working, is there any messages appearing in the console indicating what might be going wrong? Also to your other situation it’s G90 and G91 are modal meaning that whichever was used last is what will automatically apply to all future movements until it’s changed again. This means it’s very possible that your first movement G91 happened to be active which gave you a relative movement, but then between that and your next move G90 became active which resulted in an absolute move. This is very common when g-code commands are being sent behind the scenes by the g-code sender which is why it’s always best to be explicit when you manually send commands
Since it’s been a few days and my brain sorta’ looks like swiss cheese, I don’t recall the exact details. I do understand that G90/91 are modal but it makes no sense to have one axis be relative and the other being absolute when there is no intervening action/command that would change the G90/91 flag.
I do not recall any console messages that showed when the jog function did not work.
Anyway, go ahead and close this thread. If it happens again I will post again.