I have solved this. I had a similar issue. Trick is to upgrade to 2.10 by compiling your own version. I highly recommend using ChatGPT or Gemini to help with this process. This has a new feature for pipe cutting.

What you then do is to enable pipe-cut in the HAL-config OR enable it through Hal Show, this avoids the Z axis movement probe cycle prior to running the program. I can now run my XXY with a fixed Z and get the torch to run without needing to do the probe cycle.

I also created a button in the UI under settings to toggle the hal pin pipe cut to make this easier because the flag was reset each time i loaded a new program.

I've taken a look and haven't found such an option for this particular config. 5i25+7i76u+7i89. Would that need custom firmware? I see a firmware with index for 7i95t, so maybe I should've gone that route from the start.

I have a XXY plasma without Z axis. Similar issue. I compiled a new version of LinuxCNC 2.10 then I set the tube-cutting in HAL to true in my .HAL. This avoids doing the Z probing before starting the program.

I did notice that once once I load a new program, it resets the tube cutting to False to I created a button in the QTPlasmaCNC UI under settings which I named IGNORE Z-PROBE and then you can look at the config how to toggle a pin to set the tube-cutting to True.

This seems to work well in converting a non-Z plasma cutter into a working state but still use QTPlasmaC.

You might post a link to this thread on the MesaCT topic

You made my day. I had tried everything, including this, but that was in the broken config I was trying to produce from scratch by hand. (And no, I didn't ask ChatGPT. Maybe I should have. For now ChatGPT is fired as long as I don't know what I'm asking for.) I tried this on the new config I started with Pncconf and it just worked:

in my pullmax.ini I have under [DISPLAY]:
DISPLAY = halui

and under [APPLICATIONS]
#APP = halcmd loadusr -Wn pullmax gladevcp -c gladevcp -H ui.hal -x {XID} pullmax.ui
#APP = halcmd loadusr -Wn pullmax gladevcp -H ui.hal pullmax.ui

Wow! how did that work? I forgot to uncomment the second line. Tested it a bit, it also works fine if I change it to what I originally intended, and my ui does not come up if I delete the two commented lines. Each time, I am starting it from the terminal and am seeing the normal chatter, but no warnings or errors. My ini file now has:

[APPLICATIONS]
APP = halcmd loadusr -Wn pullmax gladevcp -H ui.hal pullmax.ui

Now I think I am prepared to wire up closed loop operation for each axis...
 

I suggested the G540 configuration because it includes  PWM generator that you can use
with pncconf for setting up the the spindle, the 7I76 configuration does not.

On the halcmd, yes you need the driver loaded, as I mentioned:

Note that you can list all pin and parameter names when LinuxCNC is running with:

ENCA+, ENCA-, ENCB+, ENCB-, IDX+, IDX- are all physical signal names and are not present in hal

encoder hal pins and parameters will all have names like:

hm2_7c81.0.encoder.00.position
hm2_7c81.0.encoder.00.index-enable
 etc etc

Where  the 00 in hm2_7c81.0.encoder.00.position is the encoder number

with 7C81 7i78X2d or 7I78x3d firmware, encoder 0 would be on P1

If you want to use encoder 0 on P1 for the spindle encoder, you select encoder 0
as spindle encoder  in pncconf. Similarly PWMgen 0 is on P1 with the 7I78 firmware
so pwmgen 0 would be selected for spindle speed control.





 

 Indeed, there was an error; I had given the threads "scale" names, and that's why it was giving that error. I'm resending the corrected file.

ADm1N didn't use CSV mode, it doesn't work well for a spindle as you see.
He used PV Profile Velocity mode which works well for spindle.
I made an adaptation to cia402 component for pv mode here incl an example
github.com/MetalMusings/cia402pv

The command you recommended wrote this:
halcmd show all hm2
Loaded HAL Components:
ID Type Name PID State

Component Pins:
Owner Type Dir Value Name

Pin Aliases:
Alias Original Name

Signals:
Type Value Name (linked to)

Parameters:
Owner Type Dir Value Name

Parameter Aliases:
Alias Original Name

Exported Functions:
Owner CodeAddr Arg FP Users Name

Realtime Threads:
Period FP Name ( Time, Max-Time )

This works:
halcmd -kf
halcmd: loadrt hostmot2
halcmd: loadrt hm2_rpspi
halcmd: show all hm2
 

A quick update here! I got my 7I92TM and 7I76U today, and after some swearing at Linux networking I got them flashed and confirmed working via halscope. Thanks all for getting me to this point, I need to request an RMA for the other card as well and get them in the mail.

Thanks again to everyone who's gotten me here. Now that I've got this sorted out and am confident I understand a bit more about Mesa / Hal / etc, I'm going to build out the wiring diagram, which I'll put in my other thread.  

Thanks!

 

Here is the update on my VFD braking.

No, I added my pins and linked them to jog_increments widget: [/code][/code][/code][/code][/code]

Thanks for the answer. There is one 7i78 -> P1 connected to 7c81, one optocoupler board on P7 and when I know how to do it, one 7i73. Why not pncconf for 7i76 but G540? It's more similar to 7i78. So with that encoder it means that it doesn't matter where and what encoder I choose, just change the name in .hal according to your example? Sorry for the question, will it be clear that it is a spindle encoder? Although it may be a stupid question, 7i78 has only one encoder and it is for the spindle... In the manual for 7c81 the encoder is marked as ENCA+, ENCA-, ENCB+, ENCB-, IDX+, IDX-. I don't know how it will look in .hal, because pncconf does not have the option to configure the 7c81 board. Well, with the list of parameters, it's clear, but as I already wrote, I'm completely lost and it's going slowly .