Attached is the "test driver" I made, which repeatedly polls the pendant and displays the data received. It can also update the display if you uncomment the last line in usb_interrupt_callback(). Just unzip the file into a folder and running from the terminal you should get something like:
Code:
$ make && ./whb04b
gcc -Wall -Wextra -pedantic -c -o main.o main.c
gcc -o whb04b main.o -lusb-1.0 -lm
1771265676.388 info: usb->devh: 0x564516f1abe0
1771265676.491 info: IN data: 04 10 00 00 10 11 00 10
1771265676.509 info: IN data: 04 10 00 00 10 11 00 10
1771265676.951 info: IN data: 04 10 00 00 10 11 00 10
1771265677.395 info: IN data: 04 10 00 00 10 11 00 10
You need to have libusb-1.0-0-dev installed for this to compile it. But if you already compiled LinuxCNC from source, I think you should already have it.
And regarding repeated disconnects... It may be normal behavior in as far as that is what happens. But it is for sure not correct behavior.
I would also prefer a wired pendant over this wireless one. But when I bought it this seemed like the best option for me for a relatively low cost. And I do not think that the issues we see are caused by the RF link failing.
