Thanks Erik, much appreciated. Seen your thread on the Linuxcnc forum today. I'm hurting my brain the last few days learning whatever I can about interfacing both Gamepad controllers using buttons only, and also MPG pendants (got the very same model on it's way from XHC). It's like you say, the setup task itself is not difficult once you piece together all the bits of info that (hopefully) eventually lead to things working. But wow, I'm finding you have to put the time in with Linuxcnc to learn stuff. I'm using Qtplasmac and there's a few differences in hal to using say Axis, but still your hal file should help me out heaps. I'll be studying every line. Take care.
I did have one issue going from the simulator to a real machine. When I added my xhb.hal file to my milling machine, I got a number of errors saying "that pin is already in use somewhere else." For the most part, I was able to comment out the offending commands. However, it seems that "whb.halui.machine.is.on" is required to be activated for the jog wheel to work. I first just added whb.halui.machine.is.on to the main .hal file. However, that pin does not exist until whb driver is loaded. What I did to make it work is to add the other pin to to the whb.hal file. The other pin in my case was a signal to my Mesa card to enable the servo's, I needed it. Putting that signal in the whb.hal file did the trick. I learned about enabling multiple pins in this post: forum.linuxcnc.org/38-general-linuxcnc-questions/35822-two-signals-connected-to-one-output-pin
Thanx Eric, i am a total linux cnc nono. i am wondering how to use the macro buttons eg macro 1 for the z-probe, can you help me with that? for the normal buttons i can see the mdi commands but not for the macros. regards, Patrick
I think they advertise them as Mach 3 pendants since the Mach 3 software has native support. They both work with LinuxCNC in my experience. Both have their plusses and minuses but either is a great addition to an CNC
How are all your jog functions? I had problems trying to get those to work properly before I gave up when I was still in the planning/testing phase of my conversion about a year and a half ago. I haven’t gotten around to getting the pendant working yet since getting my retrofit done because of that
Almost everyone will have signal conflicts when they try and implement. You will get an error if you have specified a HAL pin somewhere else in your configuration. Some of them you can comment out but others are required. In particular, you need "whb.halui.machine.is-on" needs to be tied to the "halui.machine.is-on" is critical to operation. I found this post on how to link two signals, recommend this: forum.linuxcnc.org/38-general-linuxcnc-questions/35822-two-signals-connected-to-one-output-pin
Thanks Erik, much appreciated. Seen your thread on the Linuxcnc forum today. I'm hurting my brain the last few days learning whatever I can about interfacing both Gamepad controllers using buttons only, and also MPG pendants (got the very same model on it's way from XHC).
It's like you say, the setup task itself is not difficult once you piece together all the bits of info that (hopefully) eventually lead to things working. But wow, I'm finding you have to put the time in with Linuxcnc to learn stuff. I'm using Qtplasmac and there's a few differences in hal to using say Axis, but still your hal file should help me out heaps. I'll be studying every line.
Take care.
Thanks, works like a charm in sim, a few little bugs here and there on linuxCNC 2.9, but this saved me a lot of time. Cheers!
I did have one issue going from the simulator to a real machine. When I added my xhb.hal file to my milling machine, I got a number of errors saying "that pin is already in use somewhere else." For the most part, I was able to comment out the offending commands. However, it seems that "whb.halui.machine.is.on" is required to be activated for the jog wheel to work.
I first just added whb.halui.machine.is.on to the main .hal file. However, that pin does not exist until whb driver is loaded. What I did to make it work is to add the other pin to to the whb.hal file. The other pin in my case was a signal to my Mesa card to enable the servo's, I needed it. Putting that signal in the whb.hal file did the trick.
I learned about enabling multiple pins in this post: forum.linuxcnc.org/38-general-linuxcnc-questions/35822-two-signals-connected-to-one-output-pin
I am buying this just because you figured it out :)
Thanx Eric, i am a total linux cnc nono.
i am wondering how to use the macro buttons eg macro 1 for the z-probe, can you help me with that?
for the normal buttons i can see the mdi commands but not for the macros.
regards, Patrick
Thanks for a nice video!
Excellent
When I go to buy a pendant, they refer to Mach 3 in advertising that is still the one to buy as long as it's a xhc-whb04b-4 pendant ? Good video.
I think they advertise them as Mach 3 pendants since the Mach 3 software has native support. They both work with LinuxCNC in my experience. Both have their plusses and minuses but either is a great addition to an CNC
How are all your jog functions? I had problems trying to get those to work properly before I gave up when I was still in the planning/testing phase of my conversion about a year and a half ago. I haven’t gotten around to getting the pendant working yet since getting my retrofit done because of that
I had the same problem exactly. The fix for me was I needed to net "whb.halui.machine.is-on" in the HAL file. See my comment below
Inget signal conflict when I try to use this with a pretty big standard axis config
Almost everyone will have signal conflicts when they try and implement. You will get an error if you have specified a HAL pin somewhere else in your configuration. Some of them you can comment out but others are required. In particular, you need "whb.halui.machine.is-on" needs to be tied to the "halui.machine.is-on" is critical to operation.
I found this post on how to link two signals, recommend this:
forum.linuxcnc.org/38-general-linuxcnc-questions/35822-two-signals-connected-to-one-output-pin
lsusb - command not found... hmmm
If lsusb isn't on your system, you will need to install "usbutils." Something like apt-get install usbutils.
If my wife starts to complain that i again spend money for "some stupid cnc" i'll tell her it's your fault!