Advanced Search

LinuxCNC 2.9.7 released 26 October 2025. LinuxCNC 2.9.7 has been released.
This is another bug-fix release to fix an unexpected interaction in a previous bugfix. (In this case the driver for the popular XHC pendants was incompatible with changes made to HALUI pin creation)
In addition changes to the CI (continuous integration) in Github mean that the install debs will be available from the LinuxCNC Github repository under the "releases tab"

This update is for all users, but especially users of the XHC pendants and Gmoccapy.

Packages for 2.9-uspace for amd64 (PC) and arm64 (Pi) for Debian Buster, Bullseye, Bookworm, Trixie and Sid have been added to the linuxcnc repository.
If you installed from one of our live images or Pi SD-card images then the update should be available immediately. The install script here: linuxcnc.org/docs/stable/html/getting-st...th_preempt_rt_kernel has been
augmented with a version for Trixie updated to include a new, longer key required by Debian versions from Trixie onwards.
(A combined script is undergoing testing, www.linuxcnc.org/linuxcnc-install-test.sh if you have a working Debian (Buster through to Trixie) install and want to install LinuxCNC on it)
At the moment the live-image installer and SD card images will install 2.9.4 but update should be trivial (and possibly automatic). Updated images are in-progress. RTAI is still supported, but in the short term building from source is likely to be the most expedient way to get 2.9.7 on that platform. Changelog

• [ci] publish releases with artifacts - GitHub now builds release deb
• Revert 7d9ee66 to address #3583 - halui functions stop working in 2.9.5/6
• Merge pull request #3512 from Sigma1912/patch-1
• Gmoccapy: Fix arrow key up/down bug in tooleditor

Acknowledgements As always, we couldn’t do this without the contributions from the community, so many thanks:
Konstantin Tcepliaev
Sigma1912

Just noticed that the handwheel is (probably) already available in the newest linuxcnc. I tried it via a 5 year old YT Video. It is probably much more easy for the basic functions.
I try to do it now...

Are you compiling from source because 2.9.6 doesn't work properly with the XHCWHB component?
If so then see this thread:

forum.linuxcnc.org/21-axis/57364-axis-co...-9-6?start=10#336658

if not, then you can get a list of the missing build dependencies

cd linuxcnc-dev
./debian configure no-docs
dpkg-checkbuilddeps

try
you might want to have a look at section 4.2.2 'Satisfying Build Dependencies':
www.linuxcnc.org/docs/devel/html/code/building-linuxcnc.html

Hello,
i just try to get my Handwheel to work. Therefore i use these YT Video

At the moment i need to compile i get these error message.

cnc@cnc:~/linuxcnc-dev/src$ ./configure --with-realtime=uspace
checking for c++... c++
checking whether the C++ compiler works... yes
checking for C++ compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether the compiler supports GNU C++... yes
checking whether c++ accepts -g... yes
checking for c++ option to enable C++11 features... none needed
checking for a BSD-compatible install... /usr/bin/install -c
checking whether c++ supports C++20 features by default... no
checking whether c++ supports C++20 features with -std=gnu++20... yes
checking build toplevel... /home/cnc/linuxcnc-dev
checking installation prefix... run in place
checking for grep... /usr/bin/grep
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for gcc... gcc
checking whether the compiler supports GNU C... yes
checking whether gcc accepts -g... yes
checking for gcc option to enable C11 features... none needed
checking for stdio.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for strings.h... yes
checking for sys/stat.h... yes
checking for sys/types.h... yes
checking for unistd.h... yes
checking for rpc/rpc.h... no
checking for get_myaddress in -ltirpc... yes
checking for rpc/rpc.h... yes
checking for rtai-config... none
checking for xeno-config... none
checking for realtime API(s) to use... uspace
checking whether to enable userspace PCI access... yes
checking for libudev... yes - version 252
checking for cc version... not specified
checking whether the compiler supports GNU C... (cached) yes
checking whether gcc accepts -g... (cached) yes
checking for gcc option to enable C11 features... (cached) none needed
checking how to run the C preprocessor... gcc -E
checking for usability of linux/hidraw.h... yes
checking for usability of rpc/rpc.h... yes
checking for libmodbus3... yes - version 3.1.6
checking for libusb-1.0... yes
checking for libgpiod < 2.0.0... no
configure: WARNING: Could not find libgpiod, not building hal_gpio
checking for module installation directory... configuring for run-in-place
/home/cnc/linuxcnc-dev/rtlib
checking for glib... yes - 2.74.6
checking for GTK 3.22.4 or above... yes - 3.24.38
checking whether make sets $(MAKE)... yes
checking for ranlib... ranlib
checking for ar... /usr/bin/ar
checking for install... /usr/bin/install -c
checking for sed... /usr/bin/sed
checking for ps... /usr/bin/ps
checking for kill... /usr/bin/kill
checking for whoami... /usr/bin/whoami
checking for awk... /usr/bin/awk
checking for pidof... /usr/bin/pidof
checking for ipcs... /usr/bin/ipcs
checking for fuser... /usr/bin/fuser
checking for yapps... no
checking for yapps2... no
configure: error: yapps/yapps2 and not found

Iḿ a 2 two weeks linux newbie... so not much experience and google doesn´t really help me. 

Hey Chris,
thanks for the report on github! It seems like it got some attention and the problem with the xhc-whb04b pendant is already figured out. Can you tell me what the supposed fix is to get the pendant working again? Or I just have to wait for a future LinuxCNC version?

Вроде разобрался

Hendrixx wrote:

it's almost like multiprocess welders, unless you drop some serious money, you're compromising. 
 

Off-topic but I am impressed with the multiprocess welder at my local Hackspace. It allows you to keep both MIG and TIG torches permanently connected and has separate gas input spigots for each process gas. 
You are not wrong about the "serious money" part, though. 

parweld.com/product/xtm211di/

(#notsponsored )

We have very similar goals. In the future, I also want an ATC and a fiber laser machine for metal cutting. I’ll be keeping an eye on BidSpotter as you mentioned, but I think I’ll end up buying the resonator and all the necessary parts for the fiber laser from some affordable Chinese supplier. Thank you so much for your support with the MPG, you’re a legend!

FOUND IT!

After 3 years since I bought the MPG, finally found the cause and solution of the issue of not being recognized on some (or all in my case) USB ports. It probably also solve if somebody got connection problems.

The main issue is that the XHC WHB04b receptor needs quite a lot of power (comparing to other USBs) to maintain a stable connection, and not all USB ports does provide such high current. So if the connection is not stable because the power issure, the kernel does not detect it. This can also happen on windows, but the windows specific drivers solve it on some cases. My computer is an industrial mini PC with external 12V PSU, so all USBs get their 5V from the main board. On desktop computers, front forts have usually lower power than rear ones, causing the issue.

There are a couple of really easy and cheap solutions:
-Use an USB HUB with external 5V power supply
-Use a Y cable (2 male, 1 female USB) either with both male USB connectors to the computer or the power only connector to a 5V PSU.

You're welcome, I'm glad you got it worked out. On the topic of separate machines, the logic is there and holds water; it's almost like multiprocess welders, unless you drop some serious money, you're compromising. And I, for one reason or another in the past, needed both couldn't afford both, or didnt have the space, I know I'm basically handicapping the machine, whichever gui is loaded but not ot the point, parts are out spec, or customers bringing stuff back. The plan is to build another machine for a 3 to 5k fiber laser, ditch the plasma altogether, and mount an ATC spindle and vacuum holding to this current one. I've been really good this year, hopefully a smoking deal comes through on BidSpotter for a laser source. This is the 5th iteration of a CNC gantry-style machine I've built. I went HAM on it just because I'm tired of being tired of not being satisfied with it.  The .5" flat bar on top has a reference shoulder machined in and a skimmed on both sides im gonna use jack screws every 12" or so in pairs to get this thing as coplanar, square and level as pyhics will allow, me to and then use a metalized epoxy to bed the bar to the frame and finaly a few stitch welds to lock it in.  ce la vie i gues. Your set up is pretty gangster 

 

First of all, thank you so much for your effort and for sharing your files—without them I never would have gotten mine working.
I learned the hard way that it’s not practical to have one machine serve as both a router and a plasma cutter, so I developed a very affordable “plasma router” that works perfectly, and now I keep the two machines separate.
I’m leaving a video so you can see it running in case it helps, and a link where you can download the 3D model and wiring diagrams. I’m sharing it as open-hardware to give back a little of the much that the community—and generous acts like yours—have given me.


3D model and wiring files here
opencnc.mx/wordpress/index.php/elementor-420/

I don't use the pendant anymore and rely on a touch screen and wireless keyboard because my machine is a dual-use plasma /router, and I couldn't get plasmac.comp to play nice with the pendant. But once I get the table put back together, I will revisit and see if the berry is worth the squeeze.

[SOLVED] XHC-WHB04B-6 on LinuxCNC 2.9.6 (QtDragonHD + 7i96S) — Beginner notes
(I am sharing the exact steps I followed, written simply. Many threads assume advanced users; I am a beginner.)My machine / system

• Gantry router XYYZ (dual Y motors), work area approx. 1300 x 1210 mm
• Controller: Mesa 7i96S (Ethernet, step/dir)
• Spindle: 2.2 kW, 24,000 RPM
• UI: QtVCP / QtDragon_HD
• OS: Raspberry Pi 5, Debian 12 (Bookworm)
• LinuxCNC 2.9.6

What actually fixed it (short version)

1. Load the pendant HAL file as a HALFILE (before the post-GUI), same as the donor machine.
2. Add MDI_COMMAND lines under [HALUI] so pins halui.mdi-command-XX exist.
3. Keep qtvcp_postgui.hal clean (only GUI signals, no pendant driver).
4. In my case, moving the WHB USB dongle to another port made the wheel/jog and DRO updates work.

STEP 1 — Copy the pendant HAL file
Place xhc-whb04b-6.hal in your config folder (the same folder that has your .ini and main .hal), e.g.:STEP 2 — Load the pendant before the post-GUI
Open your .ini and in the [HAL] section add this line and keep this exact order:Important: do not load the WHB driver inside qtvcp_postgui.hal.STEP 3 — Create MDI pins under [HALUI]
In the same .ini, find (or create) the [HALUI] section and paste this block right under it:This creates halui.mdi-command-00..07 (indexes follow the order above).
Add more MDI_COMMAND lines if your xhc-whb04b-6.hal uses higher indices.Notes so jogging actually works

• E-STOP released, Machine ON
• Manual mode
• Fully homed (for XYYZ: X, Y1, Y2, Z)
• On the pendant, use Continuous, or Step + Step size
• If the wheel does nothing or DRO does not update: try a different USB port/dongle (this was the final fix for me)

Thanks and request
Many thanks to the original thread’s author for sharing files and guidance.
If possible, could you post a short summary of the final button mapping (what each macro-N does, Continuous/Step, ABS/REL, etc.)? That would help beginners keep their configs consistent.If anyone needs it, I can share my final .ini, xhc-whb04b-6.hal, and a minimal qtvcp_postgui.hal exactly as they ended up.

So I don't have to worry about the pins not being created?

No. Hal connections are created on startup when the hal files are read. If a hal pin used in any of your hal files was missing the config would not start at all. So your problem is not because of 'signals not being connected correctly'.
One thing to do is start your config from the terminal and check the output in the terminal. Another is to check the XHC WHB04B hal component using the halshow tool to confirm button press events are actually reaching your hal connections.