Advanced Search

Aha. Many thanks - commenting out that duplicated line did the trick, so I now have the machine moving in closed loop, homing correctly and e-stopping safely. That's a great step forward and it feels as if I'm getting close to getting this sorted out.

I now have to get the xhc-whb04b-6 MPG connected up (currently commented out) and the spindle vfd doesn't respond, so I'll need to check that out too.

Andy Pugh's macros don't show up in my GUI. I have the tab showing up but clicking on it does nothing - none of the graphics appear. There are several gmoccapy lathe sims that work but something's not right in my setup. Again, I'm not clear what files need to be where and what configs need to be set up. Is there any documentation for the lathe macros that I can refer to?

Many thanks

tommylight wrote:

@Rod,
We can not edit your youtube videos on your youtube studio!
-
how is the html code for grin?

That's quite an old video now. There are more reasons  in 2.10  to grin
In  2.10 there is a change to how Deb files are built by doing it the Debian way which installs all the dependencies for you. It is described in the building linuxcnc docs for 2.10. I do remember testing it prerelease and it was sooo simple,,, except for building the docs.

i made an support request (issue) on git...

"Support for additional device ID (0xeb91) for XHC-WHB04B-6 clone (EDING CNC rebrand)"

We have already added at least one extra ID. Should be easy to add more.

github.com/LinuxCNC/linuxcnc/pull/987

EdingCNC uses a Chinese clone of this wireless handwheel, probably with a customized Product ID. I’m not sure if this is a general issue, but it might be interesting for users who want to switch from EdingCNC to LinuxCNC without buying a new wireless handwheel controller.
The controller sold by EdingCNC — which is basically identical to the ones available on AliExpress — costs more than €300. It is needed in order to run with the EDING CNC Software.

@Gogonfa
It might be worth raising an issue on github & maybe request that the PID could included on the line that loads the driver.

Could be of immense help further down the track.

Hi @all,

the issue with the Product ID on my Eding CNC branded wirless Handwheel ist solved. By changing the PorductID in the usb.h file and a rebuild of LinuxCNC, everything works fine 

@Rod,
We can not edit your youtube videos on your youtube studio!
-
how is the html code for grin?

Thanks @rodw,
today I built LinuxCNC 2.10-pre directly from the git repository, using the 6.12.48+deb13-rt-amd64 real-time kernel together with the Probe Basic GUI.Getting Probe Basic up and running was a bit tricky — some of the Python libraries it relies on are deprecated and no longer available in Python 3.13, so I had to make a few adjustments. But it’s working now!I also changed the ID for the wireless handwheel (not yet tested), and EtherCAT is running as well.

Gogonfa wrote:

[b]From what I’ve read, the Product ID is defined in the driver source (like usb.h), and you’d need to rebuild it — which I can’t manage.[/b]

 

Anybody can build linuxcnc from source. I did a video guide. studio.youtube.com/video/Oe4Hfq3G2_A/edit
 

It's the IDs that are the issue which are hard coded into the driver. 2.9.7 won't help.

Linuxcnc 2.9.4 was released to fix some things with with XHC USB pendants. Perhaps an upgrade will fix things. Here is how to get it on Trixie
 

There may be more than the usb product code that differ between them.
Here is where to change github.com/LinuxCNC/linuxcnc/blob/fb1480...-whb04b-6/usb.h#L311
Then build linuxcnc and run-in-place.

lspci will only probe devices on the pci\pcie bus.
The OP is correct the USB device ids are defined in the header file.
Maybe if the OP raised an issue on the GitHub page he would have direct access to the Devs.
Unfortunately the only thing I can think of is to follow the instructions given in the docs and build Linuxcnc from source as a RIP and see how things go.

Wireless stuff will make the latency of your whole setup worse, though perhaps that's not an issue for you.

Perhaps it's mislabled; would not be the first time.

Is that lspci output?