Advanced Search

I'm fighting with the setup of my HB04.
Simply copying over the files and adding the HAL and HALUI lines in the ini file didn't work.
Adding the loadusr line to the ini did help.
Then i ran into the error that pin "halui.spindle-override.counts" didn't exist (running 2.9.4) changed it to "halui.spindle.0-override.counts" but that gives me the same error.
#-ing out all the ofending lines till i got LinuxCNC to run worked, then in the terminal checked the pin's with "halcmd show pin" and fond that it has a different name. "halui.spindle.0.override.counts"

I now see the display matches, and updates to what the screen coordinates show. However, the jog wheel doesn't move the spindle/coordinates.
Any tips?

Ok, I didnt realize this, because the Probe Basic GUI and the VFD switched the ENA/FWD Output if I give some MDI S command. I can see that in the GUi, my relai clicks, the VFD switches to Run. But the Pin says the truth...

I don't fully understand why this Enable command should come only from the XHC-WHB-04 pendant (set pdnt....) and not from the PB Gui - I would like to enable the spindle over the pendant but more in an OR funktion not only with the pendant.
I have to say that all these spindle commands weren't made by myself but from someone else who wanted to help me out in the past. And I couldn't test it in real life, because my VFD wasn't connected until now.

How should I change the settings so that it works with GUI and pendant? can you give me some hints, please?
Thanks for your support!
Hanno

could you post the exact error message?

Bonjour a tous ,
je viens d 'installer linuxcnc 2.9.4,apres quelques heures de recherche sur le forum ,je ne trouve pas la solutions avec xhc-04, j 'ai toujours le probleme reading ini file.
 pouvez vous m 'aider .
 bonne journee
 jf
 

beauxnez wrote:

I deleted xhc-whb04b-6.hal still an error
I no longer have the problem of " MOTION: num_joints is 33, must be between 1 and 16" 
I post you the .ini and .hal files in 

 

File Attachment:

File Name: NVEM_2025-02-13.hal
File Size:4 KB

 

File Attachment:

File Name: NVEM_2025-02-13.ini
File Size:3 KB

LINUXCNC_EMCSH=/usr/bin/wish8.6
LINUXCNC - 2.9.0~pre1+git20230208.f1270d6ed7
Machine configuration directory is '/home/manu/linuxcnc/configs/NVEM'
Machine configuration file is 'NVEM.ini'
INIFILE=/home/manu/linuxcnc/configs/NVEM/NVEM.ini
VERSION=1.1
PARAMETER_FILE=linuxcnc.var
TPMOD=
HOMEMOD=
TASK=milltask
HALUI=halui
DISPLAY=qtvcp qtplasmac
COORDINATES=X Y Z
KINEMATICS=trivkins coordinates=XYZ
Starting LinuxCNC...
Starting LinuxCNC server program: linuxcncsvr
Loading Real Time OS, RTAPI, and HAL_LIB modules
Starting LinuxCNC IO program: io
Starting HAL User Interface program: halui
linuxcnc TPMOD=tpmod HOMEMOD=homemod EMCMOT=motmod
Found file(REL): ./NVEM.hal
Shutting down and cleaning up LinuxCNC...
Removing HAL_LIB, RTAPI, and Real Time OS modules
Removing NML shared memory segments

Debug file information:
Note: Using POSIX realtime
motmod: already exists
./NVEM.hal:6: waitpid failed /usr/bin/rtapi_app motmod
./NVEM.hal:6: /usr/bin/rtapi_app exited without becoming ready
./NVEM.hal:6: insmod for motmod failed, returned -1
8403
Stopping realtime threads
Unloading hal components
Note: Using POSIX realtime

 

The error gives a hint - motmod: already exists

Looks like you are loading it twice in your hal file. Try removing the 2nd line. From above EMCMOT=motmodloadrt [KINS]KINEMATICS
loadrt [EMCMOT]EMCMOT base_period_nsec=[EMCMOT]BASE_PERIOD servo_period_nsec=[EMCMOT]SERVO_PERIOD #num_joints=[KINS]JOINTS[TRAJ]SPINDLES
loadrt [EMCMOT]EMCMOT base_period_nsec=[EMCMOT]BASE_PERIOD servo_period_nsec=[EMCMOT]SERVO_PERIOD num_joints=[KINS]JOINTS num_spindles=[TRAJ]SPINDLES

I deleted xhc-whb04b-6.hal still an error
I no longer have the problem of " MOTION: num_joints is 33, must be between 1 and 16" 
I post you the .ini and .hal files in 

   

LINUXCNC_EMCSH=/usr/bin/wish8.6
LINUXCNC - 2.9.0~pre1+git20230208.f1270d6ed7
Machine configuration directory is '/home/manu/linuxcnc/configs/NVEM'
Machine configuration file is 'NVEM.ini'
INIFILE=/home/manu/linuxcnc/configs/NVEM/NVEM.ini
VERSION=1.1
PARAMETER_FILE=linuxcnc.var
TPMOD=
HOMEMOD=
TASK=milltask
HALUI=halui
DISPLAY=qtvcp qtplasmac
COORDINATES=X Y Z
KINEMATICS=trivkins coordinates=XYZ
Starting LinuxCNC...
Starting LinuxCNC server program: linuxcncsvr
Loading Real Time OS, RTAPI, and HAL_LIB modules
Starting LinuxCNC IO program: io
Starting HAL User Interface program: halui
linuxcnc TPMOD=tpmod HOMEMOD=homemod EMCMOT=motmod
Found file(REL): ./NVEM.hal
Shutting down and cleaning up LinuxCNC...
Removing HAL_LIB, RTAPI, and Real Time OS modules
Removing NML shared memory segments

Debug file information:
Note: Using POSIX realtime
motmod: already exists
./NVEM.hal:6: waitpid failed /usr/bin/rtapi_app motmod
./NVEM.hal:6: /usr/bin/rtapi_app exited without becoming ready
./NVEM.hal:6: insmod for motmod failed, returned -1
8403
Stopping realtime threads
Unloading hal components
Note: Using POSIX realtime
 

I think I misread that first error,
remove the xhc-whb04b-6.hal

I am attaching all the files of my 5-axis machine with the ability to work only with stepper motors, motors and an ecoder and in ClosedLoop mode. Spindle control via RS485 with a frequency converter. Additionally, the xhc-hb04 remote control is connected.
 

So jetzt geht alles bis auf Spindel AUS bei mir auch. 
Hab mir bei ner Flasche Bier jeden einzelnen Fehler entweder in der Machine.hal oder Handrad.hal auskommentiert, so lange bis alle wichtigen Funktionen funktionieren. 
Für das Spindel AUS brauch ich wahrscheinlich nochmal Bier Nachschub. 

Previously both, the MPG jogs and the keyboard jogs were limited by multiplexing lower acceleration values to ini.*.max_acceleration parameters during these jogs. Here is the commit message:

xhc-hb04.tcl use *.jog-accel-fraction pins
instead of mulitplexing reduced accels to ini.*.max_acceleration. Notes: 1) the prior multiplexing to ini.*.max_acceleration pins required a helper script (scripts/xhc-hb04-accels) since the ini pins are not available until task started. 2) the fractional accel settings apply only to wheel jogging (not other forms of jogging using nml commands)

The xhc-hb04-accels script is marked as obsolete and not used since 2.8~pre. The new suggested solution, to use *.jog-accel-fraction pins does not cover the keyboard jogs. Only MPG jogs.

Link to xhc-hb04-accels script from v2.7.15

USB receivers are tied to pendant, you can not replace it as I was informed . Only solution is to buy a new set.

If you have not damaged the board it should be repairable , maybe take it to some smartphone repair shop.

Hi.
Some time ago I took the photos of the PCB inside the wireless version of XHC WHB04B and then promptly forgot about them.
In hopes someone can make a good use of them in the future I'm gonna post them on the forum.
Unfortunately can't upload them all to the forum cause even at half the size they are to large, nor can I link them all in here so you'll have to follow the URL to view them on imgur. Sorry.

All the pictures at: imgur.com/a/xhc-whb04b-photos-of-pcbs-wNkBjyu

Cheers,
Bushman

Zuerstmal egal ob die Leitungs- oder die Funkvariante, die Verbindung über USB ist nicht sicher. Heißt, die Funktionen können, müssen aber nicht funktionieren.
Ich persönlich wollte aber die zusätzliche Unsicherheit mit der Funkverbindung nicht haben.

Vom Handrad gibt es jeweils eine 4- und 6-Achsvariante.

Ich denke nicht, dass da unterschiedliche Hersteller hinter stecken. Die werde alle aus der gleichen Fabrik kommen.

I have been using this pendant XHC HB04 wireless for some years and was satisfied with it.
Unfortunately I managed to damage the USB receiver of it last week when I moved the desktop PC.
The connections from the USB plug to the PCB inside broke. 
As a first attempt I tried to replace the USB part of it with a new USB plug plus cable and soldered the wires to the small PCB of the receiver.
But the first tests were not successfull. My existing LinuxCNC setup was not finding the XHC HB04 sofar. 
I am still testing and trying to fix it.

Does anyone know whether there exists an easy to find replacement for the USB receiver on the market? If so, which model/brand? Or is it a specific proprietary component. If so , is there a place to purchase only the USB receiver?

Thanks a lot,

Frans

unterscheiden sich die Handräder je nach Händler oder sind die mehr oder weniger gleichwertig? Die nächste Frage wäre ist Funk okay oder besser die Kabel Variante? 

Vielen Dank und einen schönen Feiertag
Erwin