XHC WHB04b-6 - Disconnects / freezes?

More
08 May 2022 20:24 #242321 by GuiHue
Hi everyone,

wanting more buttons than my current hardwired pendant, I opted to go with the popular xhc whb04b-6. After some work with the documentation I have managed to get it to work in a satisfactory way, or so I thought.

Upon start-up of linxucnc, all major functions work. Note, that while I have connected all elements of halui-program connected, I have not connected halui.machine.on and halui.machine.off, as I don't want to use the pendant to turn the machine on or off. To the best of my knowledge, everything else is connected.
Jogging works, all buttons work. 

Things get strange after some time and the following occurs:
- whb.pendant.is-connected remains true
- No buttons react
- jogging doesn't work
- Display on the pendant is not responsive any more (does not update, I think the selected axis remains highlighted and changes)

When does it happen:
Difficult to say, sometimes after a macro has been executed (e.g. probe-z macro using the wireless probe), sometimes after a program has been excecuted. It feels like It is stuck in the wrong mode, but I don't know how to work that one out.

I am using linuxcnc 2.8.2 with the build in driver, Wifi is active, I also use a wireless probe that communicates at 2425/2450/2475/2480 MHz. Changing the frequency had no effect. It is my understanding that whb04b uses 433MHz. I would not expect problems here.
Pendant config here (github):
github.com/GuiHue/kondor/blob/main/hallib/pendant_whb.hal
Entire config here: github.com/GuiHue/kondor/

Do you guys have any ideas? Thanks...

Please Log in or Create an account to join the conversation.

More
09 May 2022 14:26 #242380 by dannym
I do know if the probe cycle fails or another prob occurs, the UI goes into the MDI tab, and whb04 won't work while the MDI tab is active. But I'd expect you'd notice that it's on the MDI tab

Please Log in or Create an account to join the conversation.

More
09 May 2022 14:33 #242381 by GuiHue
Hi,

I know of general tab related issues. If memory serves correctly, this largely affects jogging. Changing the tabs doesn't do anything.

Other buttons, such as reset, don't do anything either (in my case this button is mapped to trigger estop via a toggle).

Please Log in or Create an account to join the conversation.

More
10 May 2022 07:43 #242466 by GuiHue
Latest update:
I reinstalled deb10 and 2.8.2 from the buildbot. Currently, it seems to work... dunno why..

Please Log in or Create an account to join the conversation.

More
31 Mar 2024 16:40 #297293 by Halbear
Sorry to bump an old thread, but this has been plaguing me pretty badly. I did look at everything I could find on this forum and the one workaround (booting computer and homing before turning on pendant) seemed to briefly offer a little hope til it didn't again.

I checked lsusb in terminal and it shows that the pendant's USB connection might be being briefly dropped, and when it comes in again nothing on the pendant works until the gui is restarted. There seems to be a correlation with the endings of programs or the stop button the pendant being pressed, but I haven't tested for that specifically.

Has anyone figured this out the last couple of years? 

Thanks,

Hal

Please Log in or Create an account to join the conversation.

More
01 Apr 2024 16:32 #297384 by jefsaro
Hello i have the same problem, before i have old model and never problem, from new it s a big problem.
Regards
The following user(s) said Thank You: Halbear

Please Log in or Create an account to join the conversation.

More
22 Aug 2024 18:21 #308422 by spontarelliam
I have the same problem. I've noticed that Linux itself has actually lost connection with the device, which I can see by running $lsusb while the pendant is working and again when it's not. The odd thing is that restarting LinuxCNC seems to mount the usb device in Linux.

I don't know the solution, but I'll continue taking notes and report back if I figure it out.

Please Log in or Create an account to join the conversation.

More
23 Aug 2024 15:03 - 23 Aug 2024 15:05 #308468 by spontarelliam
When the problem does occur, there's a continual connect/disconnect cycle of the device every ~20sec:
$ sudo dmesg -T
[Fri Aug 23 10:50:47 2024] usb 1-3.4: new full-speed USB device number 61 using xhci_hcd
[Fri Aug 23 10:50:47 2024] usb 1-3.4: New USB device found, idVendor=10ce, idProduct=eb93, bcdDevice= 0.00
[Fri Aug 23 10:50:47 2024] usb 1-3.4: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[Fri Aug 23 10:50:47 2024] usb 1-3.4: language id specifier not provided by device, defaulting to English
[Fri Aug 23 10:50:47 2024] hid-generic 0003:10CE:EB93.0129: hiddev1,hidraw3: USB HID v1.00 Device [HID 10ce:eb93] on usb-0000:00:15.0-3.4/input0
[Fri Aug 23 10:50:57 2024] usb 1-3.4: USB disconnect, device number 61
[Fri Aug 23 10:51:07 2024] usb 1-3.4: new full-speed USB device number 62 using xhci_hcd
[Fri Aug 23 10:51:07 2024] usb 1-3.4: New USB device found, idVendor=10ce, idProduct=eb93, bcdDevice= 0.00
[Fri Aug 23 10:51:07 2024] usb 1-3.4: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[Fri Aug 23 10:51:07 2024] usb 1-3.4: language id specifier not provided by device, defaulting to English
[Fri Aug 23 10:51:07 2024] hid-generic 0003:10CE:EB93.012A: hiddev1,hidraw3: USB HID v1.00 Device [HID 10ce:eb93] on usb-0000:00:15.0-3.4/input0
[Fri Aug 23 10:51:17 2024] usb 1-3.4: USB disconnect, device number 62
[Fri Aug 23 10:51:27 2024] usb 1-3.4: new full-speed USB device number 63 using xhci_hcd
[Fri Aug 23 10:51:27 2024] usb 1-3.4: New USB device found, idVendor=10ce, idProduct=eb93, bcdDevice= 0.00
[Fri Aug 23 10:51:27 2024] usb 1-3.4: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[Fri Aug 23 10:51:27 2024] usb 1-3.4: language id specifier not provided by device, defaulting to English
[Fri Aug 23 10:51:27 2024] hid-generic 0003:10CE:EB93.012B: hiddev1,hidraw3: USB HID v1.00 Device [HID 10ce:eb93] on usb-0000:00:15.0-3.4/input0
[Fri Aug 23 10:51:40 2024] usb 1-3.4: USB disconnect, device number 63
[Fri Aug 23 10:51:50 2024] usb 1-3.4: new full-speed USB device number 64 using xhci_hcd
[Fri Aug 23 10:51:51 2024] usb 1-3.4: New USB device found, idVendor=10ce, idProduct=eb93, bcdDevice= 0.00
[Fri Aug 23 10:51:51 2024] usb 1-3.4: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[Fri Aug 23 10:51:51 2024] usb 1-3.4: language id specifier not provided by device, defaulting to English
[Fri Aug 23 10:51:51 2024] hid-generic 0003:10CE:EB93.012C: hiddev1,hidraw3: USB HID v1.00 Device [HID 10ce:eb93] on usb-0000:00:15.0-3.4/input0


After restarting linuxCNC, this reconnection cycle stops. I let the pendant stay on overnight and it was still connected to LinuxCNC the next morning, so I don't think it's a timeout issue. I've also tried carrying the pendant far enough away until it displays Lost RF, but then returning to the machine, turning the pendant off/on allows it to reconnect to LinuxCNC properly in a way that doesn't happen when this disconnect/freeze error occurs.
Last edit: 23 Aug 2024 15:05 by spontarelliam. Reason: formatting struggles

Please Log in or Create an account to join the conversation.

More
26 Aug 2024 19:58 #308734 by spontarelliam
Alright a few other related forum posts (forum.linuxcnc.org/gmoccapy/34296-xhc-hc04-lost-connection, forum.linuxcnc.org/38-general-linuxcnc-q...-hb04-pendant-issues) convinced me to upgrade LinuxCNC, which appears to have solved the issue.

I upgraded from 2.8 to 2.9.3.
The following user(s) said Thank You: Aciera

Please Log in or Create an account to join the conversation.

More
27 Aug 2024 08:07 - 27 Aug 2024 08:09 #308776 by Mecanix

Alright a few other related forum posts (forum.linuxcnc.org/gmoccapy/34296-xhc-hc04-lost-connection, forum.linuxcnc.org/38-general-linuxcnc-q...-hb04-pendant-issues) convinced me to upgrade LinuxCNC, which appears to have solved the issue.

I upgraded from 2.8 to 2.9.3.
 

I have the same MPG, which I only use for the macro buttons for when I'm far from the controller and doing manual fixture setup and other non-automation related tasks. Regardless of the Lcnc version that MPG is near if not close to being useless. Similar to the keyboard, it's quite dangerous ($$$) I would like to add. There is no CRC neither data integrity to that thing and so, don't complain if it decides to randomly wander either sides and crash your >5k worth spindle into something... you get the idea. 

A safe & honest MPG requires to be hard wired. Only hardware that is legally allowed to move my axis here (no keyboard, no wifi, nothing else). 
Last edit: 27 Aug 2024 08:09 by Mecanix.

Please Log in or Create an account to join the conversation.

Time to create page: 0.206 seconds
Powered by Kunena Forum