How to configure a XHC-WHB04B pendant ?

No this would still be broke because it switches to teleop mode which won't allow to drive outside the designated area (that was the initial reason why I had a closer look at it).
The current update is very comfortable with my setup and my mill which supports automatic homing (I'm now homing each axis independently using the knob to select x/y/z/a/c and directly with the pendant), also with the lathe which I'm homing manually.

it? the XHC-WHB04B driver. And yes even the keyboard cannot manually home anymore after using the pendant with the current driver.
it's connected via halui in the configuration to switch the mode, basically that can configuration can also go away I don't see that the driver has to mess around with that at all.

tinyurl.com/36nsd7cj

it's wildly doing that and not correctly either.

After removing that wild code, your configuration would start to work.

well the patch works well so far and already solves all the issues, the timed buttons should be refactored into classes.

after that discussion:
- the teleop code should be removed completely from the driver and from the configuration file (I'm already not using it and turning it to dead code)
- instead of creating new pins:
net x-jog driver.jog-counts-0 => axis.x.jog-counts joint.0.jog-counts

should be used.

Teleop mode needs to be set to jog by default. When I set up my hardwired pendant, I got sick of walking back to the console to select Gmocappy's teleop mode jog tab. SO I programmed a button on the pendent to select it. When I do Gmocappy switches to its jog tab.

So just be aware you are overriding default behaviour.

Can you explain your post a little bit more accurate?

Teleop is a mode, and not an option that can be set to jog.

JOG JOINT / JOG TELEOP in the sourcecode.

However there are some sub-configurations in the emc code:
EMCMOT_FREE
EMCMOT_COORD
EMCMOT_TELEOP

in any case it is absolutely wrong to set jogging to TELEOP by default with the XHC pendant. It won't allow the user to home manually anymore (neither with the keyboard nor with the pendant).

The next few updates regarding the XHC-WHB04B pendant in linuxcnc for sure will break the current behaviour and need a configuration file update.
Please elaborate what exactly you need / you're doing so I can also understand that and take care about it.

Plus are you using an XHC-WHB04B? Why should someone wire up a button to teleop mode if the XHC pendant permanently sets it to teleop already. As mentioned your post is very unclear.

linuxcnc.org/docs/devel/html/man/man1/halui.1.htmlhalui.mode.teleop bit in - pin for requesting coordinated jog mode

I have a industrial hardwired 433 Mhz wireless pendant from XHC. It has a yellow safety button that needs to be pressed and held to activate the MPG. I have the relay on this button wired to the pin above and I can jog at any time regardless of the mode.
Try running up a gmocappy sim and observe this pin halui.mode.is-teleopwhen you change tabs. I think you will find it will only activated when you are on the jog tab. Setting the first pin I mentioned will select that tab in the GUI... A mesa MPG will not jog the machine if you are not on tihs tab.

PS. I never move my machine before its homed becasue its a joint axis gantry machine. i don't have kinstype=both set in my ini file.

I think you are running a wrong configuration if you're using the XHC-WHB04B pendant.

1. once you have homed an axis you are in teleop mode automatically for that axis
2. the XHC pendant (if you are using the same driver) permanently switches to teleop mode (even when not homed).
3. unhome and you're in joint jog mode (non teleop mode)

I still don't see why teleop / non teleop mode should be anything the user should touch directly by himself.
If you want to enable / disable jogging you should look at another pin -- the teleop mode should be clear now?