Help configuring a Pendant

Yes, it touches off X and Y to zero.

It has identical functionality to the X0Y0 button in the DRO frame.
 

I stole your example and integrated your "qtplasmac.ext_touchoff" into my pendant (and that works perfectly)

Could you please explain to me what the => or <= operations mean? I can't find any real descriptions for those (and others) I can assume, but I'd rather ask. (it may help others)

Is there a way to jog using the same controls in the GUI (so that the pendant follows the rules on screen) Right now, my pendant jogging is always continuous and is at speeds defined in my custom HAL file rather than what the GUI is set at. I would like a way to cycle through the options with one pendant button and jog according to the GUI rules, but I haven't figured that part out yet.

Thank you again for all you do for us. Merry Christmas and Happy Holidays!

re: Could you please explain to me what the => or <= operations mean? I can't find any real descriptions for those (and others) I can assume, but I'd rather ask. (it may help others)

They don't mean anything they are there just to show the the direction of the flow but are quite often wrong. linuxcnc does not take any notice of them so they can be ignored.

rodw, could you please elaborate? I'm still on the steep side of the learning curve with all this (bit of information overload by adding a new to me OS on top of the software). I'm not sure how the "or2" component works.

By using the example below, both the GUI input on screen as well as the button on the USB pendant will start the program.

"net pendant-run-pause <= qtplasmac.ext_run_pause <= input.0.btn-base4"

you don't happen to know the HAL pin names that correspond to the on-screen (GUI) jog controls do you?

You don't need an "or2" when you use the GUI s external pins.

There are no GUI jog pins, jogging can be controlled by halui joint and axis pins.

linuxcnc.org/docs/devel/html/man/man1/halui.1.html

Jflesburg wrote:

rodw, could you please elaborate? I'm still on the steep side of the learning curve with all this (bit of information overload by adding a new to me OS on top of the software). I'm not sure how the "or2" component works.

Sounds like Phil has made it easy for you but:
or2 has to inputs or2.n.in0 and or2.n.in1, and one output or2.n.out
So you connect two pins to in0 and in2
If one of them or the other goes true (or both), out will go true.
That way, 2 outputs attached to the in pins can control a single function.

The other alternative is to add additional logic to the screen handler which is the path Phil has taken.