XHC-WHB04B-6 LinuxCNC not working

Thanks for reply, i like to PR if you agree but i need to finish some works.

Is this have more sense ? "In Mpg mode the step speed is in percent of max-velocity"
(if yes the good pin it is halui.max-velocity.value for calc ?)

I have corrected the Lead mode for use spindle override to GUI.
Fix scale Button Feed+/- for speed override to GUI
Fix Rotary knob to change only pendant feedrate

alkabal wrote: Writing this allow to have something variable but i'm unsure about the real reaction needed for Mpg mode.
I have try to use without success :
halui.feed-override.count-enable (bit, in)
halui.feed-override.counts (s32, in) - counts * scale = FO
halui.feed-override.direct-value (bit, in)
halui.feed-override.scale (float, in)

If you can it is rather better to use the motion jogging pins rather than halui.

Halui is a user-space program. Motion (which creates the joint.... and axis.... HAL pins) runs in realtime so will react to inputs more dependably.

Though that probably doesn't matter as much when you are connecting via USB, which has its own issues.

Hi

Ok thanks for suggestion i will check for some motion.pin.
But only for stuff that can be used when program.is.running ? (like spindle override and feed override)

Except that a pendant is mostly a user component, or i'm wrong ?

Is this have more sense ? "In Mpg mode the step speed is in percent of max-velocity"
(if yes the good pin it is halui.max-velocity.value for calc ?)

i have do some test using halui.max-velocity.value * feed-button-position * 0.01 and i see the machine cant' move more than 16mm with one pulse but off course i think is better to use smaller value.
resulting value :
2% : 70 x 2 x 0.01 = 1.4 = move 1.4mm
5% : 70 x 5 x 0.01 = 3.5 =move 3.5mm
10% : 70 x 10 x 0.01 = 7 = move 7mm
30% : 70 x 30 x 0.01 = 21 = move 16mm
60% : 70 x 60 x 0.01 = 42 = move 16mm
100% : 70 x 100 x 0.01 = 70 = move 16mm

I see any nothing usefull in motion pin

alkabal wrote: Except that a pendant is mostly a user component, or i'm wrong ?

USB ones are, yes.

MPGs connected by ABZ wires to encoder counters in HAL and buttons connected to HAL can be realtime all the way.

Ok i understand, but in all way i can't see any motion override or jog related pin.

I have do a big cleaning for source code and use max-velocity for mpg

Two more stuff liked but no idea for do this for now
-swap spindle speed displayed on the pendant from Override % to Current-velocity regarding to used button (spindle+/+ or override+/-)
-Restore the MPG/CON/STEP usage for now the code force MPG at startup and does not allow to use the CON mode.