select jog axis

with slight modification of python script from  forum.linuxcnc.org/38-general-linuxcnc-q...lect?start=10#281577
it is working now at least jog selection

i don't know why but i thought that all UIs should use some hal signals for representation of data. So changing `halui.axis.x.select` should be used by UIs.

 

There is no need for a GUI to get involved with external hardware. Thats what halui is for.
When GUIs extend their scope, we get a mess with differing configs for no reason.

No, halui does not integrate well with axis selection or jogging rates in GUIs.
Halui is really a UI all on it's own, it was not made to integrate with other GUIs.
Just in most cases you can make it work.

I have not tried with qtdragon but halui jogging has worked for me with dedicated pendant hardware on axis, gmoccappy, and qtplasmac. I helps that the pendant has a deadman switch that allows selection of teleop mode before the pendant can be used.. This was most visible on Gmocappy as it selected the jogging tab when pressed. I don't expect qtdragon would be any different and teleop mode selection would make it pretty seamless.
Using pendant buttons for continuous high and low speed jogging is a bit more complex and while it can be done with hal, writing a custom component makes it simpler to implement as it flattens thehall commands a lot.

What I meant be not integrating well is if you try to say select jog speed in the GUI but jog with Halui or some other combination of Halui and GUI controls.

Possibly, but on a table rather than a mill, where you are walking around the machine with pendant in hand, you never touch the GUI jog buttons (they might be on the other side of the table). So its not an issue.

well i didn't thought about this but it makes sense. If you have physical buttons and switches you don't need them on screen.

interestingly enough feed override and rapid now shown in ui with proper values