XHC-HB04 wireless MPG pendant HAL module
07 Apr 2015 17:50 #57604
by etnur
Replied by etnur on topic XHC-HB04 wireless MPG pendant HAL module
The error was in the config file .
Now everything is running properly.
A nice side effect is that I have now learned a lot about EMC² .
Again, a special thanks for your support, dgarrett.
Now everything is running properly.
A nice side effect is that I have now learned a lot about EMC² .
Again, a special thanks for your support, dgarrett.
Please Log in or Create an account to join the conversation.
22 Apr 2015 00:36 #57979
by Gasman
Replied by Gasman on topic XHC-HB04 wireless MPG pendant HAL module
I recently ordered what I believed to be an HB04 pendant from Ebay. The pictures didn't show the model number and the device has taken a while to arrive. The device that has been shipped is an HB03. Bit cross with the seller as the model number is clearly visible on the device but has been airbrushed out of the advert photos. 
Otherwise, visually it looks the same as the 18 button HB04.
I have read through this thread and cant really find any reference to the HB03.
Anyhow, can I recompile the XHC-HB04 module with a different deviceID (it is EB6E not EB70)? I presume I need to edit xhc-hb04.cc, make && make install. I am also aware that I will need to change the deviceID in etc/udev/rules.d/90-xhc.rules. I am also aware that I am likely to have to do a bit of button re-mapping.
Am I on the right track? Has anyone actually done this with an HB03? Anything else I need to look out for?
Is this likely to result in a functional solution or am I better off taking this back to the post office for a refund?
Otherwise, visually it looks the same as the 18 button HB04.I have read through this thread and cant really find any reference to the HB03.
Anyhow, can I recompile the XHC-HB04 module with a different deviceID (it is EB6E not EB70)? I presume I need to edit xhc-hb04.cc, make && make install. I am also aware that I will need to change the deviceID in etc/udev/rules.d/90-xhc.rules. I am also aware that I am likely to have to do a bit of button re-mapping.
Am I on the right track? Has anyone actually done this with an HB03? Anything else I need to look out for?
Is this likely to result in a functional solution or am I better off taking this back to the post office for a refund?
Please Log in or Create an account to join the conversation.
22 Apr 2015 19:14 #58005
by Gasman
Replied by Gasman on topic XHC-HB04 wireless MPG pendant HAL module
I have recompiled the xhc-hb04.cc with the deviceID EB6E as well as adding etc/udev/rules.d/90-xhc.rules with the altered deviceID. I have had to comment out quite a few lines in the HAL config file referring to extra axes. Linuxcnc now runs without error but the handset still does nothing. 
I have runfrom the command line and, after creating the pins, it fails with
Living life dangerously I then tried running as root...
A partial success!!! xhc-hb04 now working and streaming rows of data on each button press. Not sure if I need to do anything to stop
However, I have also found this on Planet CNC - which says that the #_wc_frac is 8bit for the HB03 and 16bit for the HB04 as the former only displays to three significant figures. This sounds worrying to me as I am not a programmer and have not the faintest idea where to look to check this. Even more confusing is that my model displays not 2 or 4 but 3 significant digits!
I have run
xhc-hbo4libusb error (libusb couldn't open USB device ...)Living life dangerously I then tried running as root...
A partial success!!! xhc-hb04 now working and streaming rows of data on each button press. Not sure if I need to do anything to stop
libusb:warning [handle_bulk_completion] unrecognised urb status -108john@john-desktop:~$ sudo xhc-hb04
[sudo] password for john:
Creating pin: xhc-hb04.x.pos-absolute
Creating pin: xhc-hb04.y.pos-absolute
Creating pin: xhc-hb04.z.pos-absolute
Creating pin: xhc-hb04.a.pos-absolute
Creating pin: xhc-hb04.x.pos-relative
Creating pin: xhc-hb04.y.pos-relative
Creating pin: xhc-hb04.z.pos-relative
Creating pin: xhc-hb04.a.pos-relative
Creating pin: xhc-hb04.feed-value
Creating pin: xhc-hb04.feed-override
Creating pin: xhc-hb04.spindle-rps
Creating pin: xhc-hb04.spindle-override
Creating pin: xhc-hb04.jog.enable-off
Creating pin: xhc-hb04.jog.enable-x
Creating pin: xhc-hb04.jog.enable-y
Creating pin: xhc-hb04.jog.enable-z
Creating pin: xhc-hb04.jog.enable-a
Creating pin: xhc-hb04.jog.enable-feed-override
Creating pin: xhc-hb04.jog.enable-spindle-override
Creating pin: xhc-hb04.jog.scale
Creating pin: xhc-hb04.jog.counts
Creating pin: xhc-hb04.jog.counts-neg
Creating pin: xhc-hb04.jog.velocity
Creating pin: xhc-hb04.jog.max-velocity
Creating pin: xhc-hb04.jog.increment
Creating pin: xhc-hb04.jog.plus-x
Creating pin: xhc-hb04.jog.minus-x
Creating pin: xhc-hb04.jog.plus-y
Creating pin: xhc-hb04.jog.minus-y
Creating pin: xhc-hb04.jog.plus-z
Creating pin: xhc-hb04.jog.minus-z
Creating pin: xhc-hb04.jog.plus-a
Creating pin: xhc-hb04.jog.minus-a
waiting for XHC-HB04 device
found XHC-HB04 device
libusb:warning [handle_bulk_completion] unrecognised urb status -108
04 17 00 00 00 1B
04 00 00 00 00 0C
04 16 00 00 00 1A
04 00 00 00 00 0C
04 01 00 00 00 0D
04 00 00 00 00 0C
04 02 00 00 00 0E
04 00 00 00 00 0C
04 03 00 00 00 0F
04 00 00 00 00 0C
04 04 00 00 00 08
04 00 00 00 00 0C
04 0C 00 00 00 00However, I have also found this on Planet CNC - which says that the #_wc_frac is 8bit for the HB03 and 16bit for the HB04 as the former only displays to three significant figures. This sounds worrying to me as I am not a programmer and have not the faintest idea where to look to check this. Even more confusing is that my model displays not 2 or 4 but 3 significant digits!
How can I sort out the presumed permissions problem(s), what do I need to do to manage the 8bit vs 16 it words and how far away from a working solution am I? If this needs much more work it is definitely on its way back to the seller!#_wc_frac - it is 8bit for WHB03 and 16bit for WHB04 ... it is simple whan you look two display max frac part for WHB03 it is .99 and for WHB04 it is .9999 ... this value also have a SIGN bit if value is negarive you must set most significant bit to 1... little example:
WHB03
our X position is: -117.33
we put 117 to x_wc_int
we also put 33 to x_wc_frac
we have negative value... we also need to set most significant bit of x_wc_frac to 1...
Code: Select allx_wc_frac = x_wc_frac | 0x80;
WGB04
our X position is: -220.3345
we put 220 to x_wc_int
we also put 3345 to x_wc_frac
we have negative value... we also need to set most significant bit of x_wc_frac to 1...
Code: Select allx_wc_frac = x_wc_frac | 0x8000;
Please Log in or Create an account to join the conversation.
Time to create page: 0.109 seconds