You may have set the deceleration and acceleration ramps too steeply 

Hi,

I am having the same problem, with the same controller , only 4 axis . Same id, and same symptoms. I am running linuxCNC 2.9.8, I have tried to change the ID in the .rules file, but no luck.
Did anyone resolve this, any suggestions?

I have an XHC-WHB04B pendant set up and everything works pretty well, except that when I turn the wheel in continuous mode it moves in jerks/jumps, while in step mode it moves smoothly. Is there any way to avoid the jumps in continuous mode?

Witam mam linuxcnc 2.9.8 płyta Mesa7i92 z SSK-MB2 jest to frezarka trzy osie X Y Z programy ngc działają prawidłowo.
Uruchomiłem WHBO4B-4 na przewodzie i nie do końca działa prawidłowo czyli gdy kręcę kółkiem i gdy przestanę oś idzie dalej .
Proszę co mam nie tak ustawione.
Załączam moją konfigurację.
  
 
 
 

That's great news, glad you got it sorted out!

Update on my situation.

I was able to solve my jog pendant issues. 

There were two changes I made:

1. halui signals:

Probe Basic
# ---HALUI signals---

net axis-select-x halui.axis.x.select
# net jog-x-pos halui.axis.x.plus
# net jog-x-neg halui.axis.x.minus
# net jog-x-analog halui.axis.x.analog
net x-is-homed halui.joint.0.is-homed
net axis-select-y halui.axis.y.select
# net jog-y-pos halui.axis.y.plus
# net jog-y-neg halui.axis.y.minus
# net jog-y-analog halui.axis.y.analog
net y-is-homed halui.joint.1.is-homed
net axis-select-z halui.axis.z.select
# net jog-z-pos halui.axis.z.plus
# net jog-z-neg halui.axis.z.minus
# net jog-z-analog halui.axis.z.analog
net z-is-homed halui.joint.2.is-homed
# net jog-selected-pos halui.axis.selected.plus
# net jog-selected-neg halui.axis.selected.minus
net spindle-manual-cw halui.spindle.0.forward
net spindle-manual-ccw halui.spindle.0.reverse
net spindle-manual-stop halui.spindle.0.stop
net machine-is-on halui.machine.is-on
# net jog-speed halui.axis.jog-speed
net MDI-mode halui.mode.is-mdiAxis# ---HALUI signals---

#net axis-select-x halui.axis.x.select
net jog-x-pos halui.axis.x.plus
net jog-x-neg halui.axis.x.minus
net jog-x-analog halui.axis.x.analog
#net x-is-homed halui.joint.0.is-homed
#net axis-select-y halui.axis.y.select
net jog-y-pos halui.axis.y.plus
net jog-y-neg halui.axis.y.minus
net jog-y-analog halui.axis.y.analog
#net y-is-homed halui.joint.1.is-homed
#net axis-select-z halui.axis.z.select
net jog-z-pos halui.axis.z.plus
net jog-z-neg halui.axis.z.minus
net jog-z-analog halui.axis.z.analog
#net z-is-homed halui.joint.2.is-homed
net jog-selected-pos halui.axis.selected.plus
net jog-selected-neg halui.axis.selected.minus
#net spindle-manual-cw halui.spindle.0.forward
#net spindle-manual-ccw halui.spindle.0.reverse
#net spindle-manual-stop halui.spindle.0.stop
#net machine-is-on halui.machine.is-on
net jog-speed halui.axis.jog-speed
#net MDI-mode halui.mode.is-mdi

For some reason I had ended up with the exact opposite lines commented between the new probe basic and the old axis configs (probably had used a toggle comment command in vs code accidentally). I swapped the commenting in the probe basic hal file to match the old axis file.

2. pendant.hal and pin conflicts
I had some pin conflicts between pendant.hal and the postgui hal that probe basic uses. I had originally changed them in the pendant.hal file to preserve probe basic postgui hal file. Now, I am using the pendant.hal file that worked with the old axis config and I modified the conflicting pins in the post gui hal file from probe basic.

Between those two changes, the pendant is now functioning just how it was on the old axis configuration.
So now I have a functioning pendant and a functioning ATC using probe basic as the UI.

Next to get my ATC rack made and get my probe working.

You may have a timer issue, I know others had conflict with the timer and hbo4 pregnant, I would investigate that.

Aside from that I'm not sure what would cause that except maybe a setting for the pregnant specific that may require a change?

Hopefully someone else can come in with knowledge on it. My wired jog pendant uses velocity mode when the speed is to fast for motion and the pulses begin to stack up, this stupid a runaway axis condition.

spumco wrote:

I consider any of the Mesa SmartSerial boards to be 'direct I/O' as that method of connection is rock-solid and there's no human-perceptible lag or latency.  Which means a hand-held MPG with a 7i73 inside (for the digital display) will be be just as responsive as the panel-mounted stuff I built.

Well there are wireless pendants that wire into direct I/O (but they are not USB) that will give equivalent response
www.wixhctech.com/product/23.html
They use a lot of I/O but you can get versions that use digital inputs (which I have used) that save a few inputs
 

Thanks, but the USB stick was really broken and it blocks any PC it's plugged into. I'm using the handwheel to modify it with an ESP32.

Hello,
When I implement the XHC-WHB04B-4 handwheel in LinuxCNC, my milling motor no longer receives a speed command via gcode file or mdi command. 
I had to remove some commands from the *.hal file to prevent errors from occurring at startup. My files are attached.
 

Hi all, I'm working on moving from an older (Linuxcnc 2. Axis config to a Probe Basic config after getting a new spindle for my router.

I have successfully gotten the basics working and have even gotten the ATC functions mostly where I want them. (Huge thanks for the the starting point that is the Probe Basic screen set and all the macros)

I am running into trouble integrating my XHC-WHB04B-6 pendant. It works just how I want it to in the old Axis configuration, and in fact that configuration runs just fine under Linuxcnc 2.9 and the pendant works in that config.

However, in Probe Basic the pendant produces stuttery motion when jogging both in step mode and in continuous mode. It also will not register all pulses or clicks of the jog wheel when the wheel is spun quickly. If I slowly click the wheel in step mode (say 1 click per second) I get each step translated into machine motion, but if I quickly spin the jog wheel, I will only get a small fraction of the wheel clicks actually translating into machine motion.

General info:
-  What Linux OS being used including kernel type?
> Debian GNU/Linux 12 (bookworm)
> Kernel version: 6.1.0-44-rt-amd64

-  What version of Linuxcnc is installed?
> 2.9.8

-  What version of QtPyVCP and Probe Basic is installed?
> Probe Basic version: 0.6.6

-  How did you install Probe Basic? Quickstart guide? Dev Guide? 
> Probe Basic APT stable install following the guide here: kcjengr.github.io/probe_basic/index.html

-  Have you gone through your ini and hal files and compared to the sim config files to make any changes needed?
> Yes, Probe Basic is functioning, just the integration with the pendant is giving me headaches

-  Have you added all of the necessary files in your config folder that probe basic needs to run?
> Yes

I attached the hal files ini files and pendant hal files for the two configs. (note i renamed the pendant.hal file for the Odroid config so that there were not two of the same file name)

Please take a look and let me know if more info will make the problem easier to diagnose.

Thanks!
 

I imagine that you will be satisfied with the updated xhc-whb04b-6 component by hdiethelm, which allows the pendant to reconnect in case it disconnects (as well as several other improvements). But you need to compile it from source, same as building LinuxCNC from source (which is not all that difficult). He made a backport to LinuxCNC 2.9.8:
github.com/hdiethelm/linuxcnc-fork/tree/...x-v2_backport-v2.9.8
So basically git clone that repository, checkout xhc-whb04b-6-fix-v2_backport-v2.9.8 and then compile. I don't know about exact version compatibility, but I don't think you actually need to use v2.9.8 to run the component. You can just give the full path to the newly built compnonent binary in the loadrt command.

I made a custom firmware for the USB dongle that I use myself, but I can't really recommend that for others. There is a decent risk that it would irreversibly break your dongle in case the hardware is slightly different than what I have.

I don't know your proficiency with git and compiling LinuxCNC from source. Just ask if my somewhat terse instructions are not clear to you.

I have this pendant and would like to test out your firmware. Where do I find it/install it from? I'm tired of this device working and then just deciding to quit working in the middle of operations.