Advanced Search

Sorry to keep updating this thread.  After a lot of reading this morning, I think I have a workable solution by adding two buttons to my gvcp, one for min jog rate and one for max jog rate.

Given this solution, is there a way to logically press these buttons via a mapped keyboard key?

Andy,
I found the document written by John B that describes key remapping.  The file that holds the mappings is /usr/bin/axis. From what I can decipher There isn't a function to set the jog rate to a specific value only the ability to change the jog rate to one of the predefined values in the ini file.

I also found functions in the green screen UI and the qtvcp UI that can change jog speed. Would either of these functions work in the axis UI?

Also, in section 13.4.4 Functions of the documentation is found these functions:

set_jograte (float) - LinuxCNC has no internal concept of jog rate -each GUI has its own. This is not always convenient. This function allows one to set a jog rate for all objects connected to the signal jograte-changed. It defaults to 15. GSTAT.set_jog_rate(10) would set the jog rate to 10 machine-units-per-minute and emit the jograte-chasignal.

get_jograte() (Nothing) - x = GSTAT.get_jograte() would return GSTAT’s current internal jograte (float).

set_jograte_angular (float) -

get_jograte_angular (None) -

set_jog_increment_angular (float, string) -

get_jog_increment_angular (None) - LinuxCNC V2.9.4, 25 Jan 2025 1268 / 1297

set_jog_increments (float, string) -

get_jog_increments (None) -

These sound promising, but have no documentation for their use. Has anyone documented these functions?

Kind Regards