jog (step mode) not working on start up

If you have a question about the software please ask it here.

jog (step mode) not working on start up

Postby oraclian » Sun Aug 08, 2021 8:48 pm

when I first start up UCCNC the continuous jog works ok but the step jog moves the DRO (very slowly) but the axis doesn't move. Once I load and run a program step mode works fine...I wrote a simple program that just moves each axis a small amount and run this on startup and once it has run step jog works ok. but would like a permanent fix...any ideas.
oraclian
 
Posts: 4
Joined: Fri Jan 29, 2021 2:41 am

Re: jog (step mode) not working on start up

Postby cncdrive » Sun Aug 08, 2021 9:45 pm

This is not something to be fixed, it works like this for reason.
The step jog moves runs with the set feedrate (Fset).
When you loading and running a g-code program it probably sets the feedrate to a different value, so the step jog will become faster,
because on startup the Fset is set to a low value of 6.
What you can do is you can type in an F command in the MDI.
E.g. if you want the step jog to run at 1000 units/min then type in F1000 into the MDI.
cncdrive
Site Admin
 
Posts: 4887
Joined: Tue Aug 12, 2014 11:17 pm

Re: jog (step mode) not working on start up

Postby oraclian » Sun Aug 08, 2021 11:21 pm

Thank you (cncdrive) that solves my problem. That it works this way is somewhat odd. i understand why the continuous jog rate is set to a low value at start up and how to fix it if I want too, i don't bother and adjust it manually depending on what i am doing. However the speed of the step move is not particularly important with small moves like 1 unit so why is the start up default not set to ,say, F1000 automatically ?
oraclian
 
Posts: 4
Joined: Fri Jan 29, 2021 2:41 am

Re: jog (step mode) not working on start up

Postby cncdrive » Mon Aug 09, 2021 6:08 am

It is set to a low value, because the Fset is the feedrate not only for the step jog, but also for other motion commands, MDI and g-code file commanded movements.
So, if the Fset would be set high on startup and you typing in a motion command to the MDI or if your g-code file accidentally does not contain the F code to set the feedrate then your machine would run those commands fast.
This could be a safety issue.

But if you find the initial Fset to be too low for you then you could change it with some macro code in the M99998 constructor macro.
cncdrive
Site Admin
 
Posts: 4887
Joined: Tue Aug 12, 2014 11:17 pm


Return to Ask a question from support here

Who is online

Users browsing this forum: Bing [Bot] and 36 guests