Does anyone know if there is a way to change the jog rate for the x and y axis permanently? Every time I power down the jackpot controller or do a reset it defaults back to the original default.
After you make the changes you want, use the save Macro button I made on the WebUI home screen.
1 Like
You can also use the ‘hamburger’ (3 horizontal lines) in the upper right side of the WebUI, select ‘preferences’ scroll diwn and change it ther. Don’t forget to scroll to the bottom and click on ‘save’.
2 Likes
Risking sounding too NEWB for having a Lowrider now for several years, what do you mean by Jog rate? I am currently having issues with my X axis not keeping pace in the cut - ryan says to increase power as it might be a solution - but is this Jog rate? Or is it a speed it will travel between tool engagement areas?
I think jog is usually understood as positional movements you make between jobs, and the travel between cuts. Basically movements when no resistance from being in a cut.
So changing the jog speeds on the WebUI screen and then using the save macro button does not change anything. After a restart the speeds revert back to default. Matt K’s solution though does seem to work.
Thank you both for your help
1 Like
OK, so I’m circling back to say that apparently I had this wrong. The word for moving between cuts is rapids. Jogging can actually refer to movements that are made while cutting. At least, according to some googling and YouTube. My seemingly incorrect understanding on this was recently an underlying factor in a video that I posted and that Ryan commented on here asking why I used jog instead of rapid. 
I’ve seen the two terms used interchangeably in conversation. But the gcodes obviously have specific technical meanings.
I haven’t researched it w.r.t. fluidnc, but my understanding is that rapids or travel moves are non cutting moves created by the slicer. Jogging is done by a human and they have different technical requirements. For example, if you send a long jog command and immediately send a contradictory jog command, the controller should abort the first. I don’t have any confirmation this is actually happening in fluidnc. But IMO, that is one major difference.
I don’t seem to be able to interrupt a jog in process with a “contradictory” jog on my jackpot from the webui. Not really an issue but would be nice.
1 Like
There is a GRBL v1.1 jog command (starts with $J= instead of with G0) that, according to the docs, is supposed to be more cancelable. Your mention about “rapids … are non cutting moves created by the slicer” while “Jogging is done by a human” makes the most sense of anything I have read on it. The v1.1 jogging commands ( i.e. $J= ) are explained at Grbl v1.1 Jogging · gnea/grbl Wiki · GitHub …
I would have assumed the WebUI is using (issuing) jog commands with the $J= format. How interruptible they are probably depends on various factors. I think I had some success with overriding them with commands going the opposite way, on jog commands for a long distance jog, but hard to tell.
1 Like