Probe panel for Axis GUI

thankyou aciera, i think i understand what you did there and it sorted that part out, so i can call multiple post_gui.hal files that way, very cool. now im back to this error

PARAMETER_FILE=linuxcnc.var
TASK=milltask
HALUI=
DISPLAY=axis
COORDINATES=X Y Z
KINEMATICS=trivkins coordinates=XYYZ kinstype=BOTH
Starting LinuxCNC...
Starting LinuxCNC server program: linuxcncsvr
Loading Real Time OS, RTAPI, and HAL_LIB modules
Starting LinuxCNC IO program: io
Found file(REL): ./PRINTNC.hal
Found file(REL): ./Probe_preload.hal
Found file(REL): ./custom.hal
Starting TASK program: milltask
Starting DISPLAY program: axis
Shutting down and cleaning up LinuxCNC...
task: 214 cycles, min=0.000032, max=0.014714, avg=0.009666, 0 latency excursions (> 10x expected cycle time of 0.010000s)
INFO CLASSICLADDER---I/O modbus master closed!
Failed to open serial port /dev/ttyUSB0...
INFO CLASSICLADDER---I/O modbus master Data bits 8 Stop bits 1 Parity 0
ERROR CLASSICLADDER- MODBUS NO RESPONSE (Errs=1/1) !?
ERROR CLASSICLADDER- MODBUS-LOW LEVEL ERROR IN RESPONSE!!!
ERROR CLASSICLADDER- MODBUS NO RESPONSE (Errs=2/2) !?
ERROR CLASSICLADDER- MODBUS-LOW LEVEL ERROR IN RESPONSE!!!
ERROR CLASSICLADDER- MODBUS NO RESPONSE (Errs=3/3) !?
ERROR CLASSICLADDER- MODBUS-LOW LEVEL ERROR IN RESPONSE!!!
ERROR CLASSICLADDER- MODBUS NO RESPONSE (Errs=4/4) !?
ERROR CLASSICLADDER- MODBUS-LOW LEVEL ERROR IN RESPONSE!!!
ERROR CLASSICLADDER- MODBUS NO RESPONSE (Errs=5/5) !?
ERROR CLASSICLADDER- MODBUS-LOW LEVEL ERROR IN RESPONSE!!!
ERROR CLASSICLADDER- MODBUS NO RESPONSE (Errs=6/6) !?
ERROR CLASSICLADDER- MODBUS-LOW LEVEL ERROR IN RESPONSE!!!
ERROR CLASSICLADDER- MODBUS NO RESPONSE (Errs=7/7) !?
ERROR CLASSICLADDER- MODBUS-LOW LEVEL ERROR IN RESPONSE!!!
ERROR CLASSICLADDER- MODBUS NO RESPONSE (Errs=8/ !?
ERROR CLASSICLADDER- MODBUS-LOW LEVEL ERROR IN RESPONSE!!!
ERROR CLASSICLADDER- MODBUS NO RESPONSE (Errs=9/9) !?
ERROR CLASSICLADDER- MODBUS-LOW LEVEL ERROR IN RESPONSE!!!
ERROR CLASSICLADDER- MODBUS NO RESPONSE (Errs=10/10) !?
ERROR CLASSICLADDER- MODBUS-LOW LEVEL ERROR IN RESPONSE!!!
ERROR CLASSICLADDER- MODBUS NO RESPONSE (Errs=11/11) !?
ERROR CLASSICLADDER- MODBUS-LOW LEVEL ERROR IN RESPONSE!!!
ERROR CLASSICLADDER- MODBUS NO RESPONSE (Errs=12/12) !?
ERROR CLASSICLADDER- MODBUS-LOW LEVEL ERROR IN RESPONSE!!!
ERROR CLASSICLADDER- MODBUS NO RESPONSE (Errs=13/13) !?
ERROR CLASSICLADDER- MODBUS-LOW LEVEL ERROR IN RESPONSE!!!
ERROR CLASSICLADDER- MODBUS NO RESPONSE (Errs=14/14) !?
ERROR CLASSICLADDER- MODBUS-LOW LEVEL ERROR IN RESPONSE!!!
ERROR CLASSICLADDER- Error initializing classicladder user module.
config string '0 out'
creating ladder-state
Removing HAL_LIB, RTAPI, and Real Time OS modules
Removing NML shared memory segments

Debug file information:
Note: Using POSIX realtime
Unexpected realtime delay on task 0 with period 35000
This Message will only display once per session.
Run the Latency Test and resolve before continuing.

(classicladder:1113): Gtk-CRITICAL **: 22:35:07.063: IA__gtk_widget_get_parent: assertion 'GTK_IS_WIDGET (widget)' failed
note: MAXV max: 146.670 units/sec 8800.200 units/min
note: LJOG max: 146.670 units/sec 8800.200 units/min
note: LJOG default: 30.000 units/sec 1800.000 units/min
note: jog_order='XYZ'
note: jog_invert=set([])
custom_postgui.hal:23: Pin 'parport.0.pin-15-in' was already linked to signal 'probe-input'
1092
1134
Stopping realtime threads
Unloading hal components
Note: Using POSIX realtime

so i uncomment the
net probe-input motion.probe-input <= parport.0.pin-15-in
line in my hal file and i get
custom_postgui.hal:31: Pin 'halui.mdi-command-00' does not exist
i need to understand why im getting the probe pin error and then why im getting the second error for the hal ui command

ok making small steps in progress, i asked chatgpt to help and by adding
[HAL]
HALFILE = PRINTNC.hal
HALFILE = Probe_preload.hal
HALFILE = custom.hal
POSTGUI_HALFILE = postgui_call_list.hal
HALUI = halui <---- this line

to the hal section the "custom_postgui.hal:31: Pin 'halui.mdi-command-00' does not exist" is now gone and im just getting the custom_postgui.hal:23: Pin 'parport.0.pin-15-in' was already linked to signal 'probe-input' and the only other place that pin is mentioned is in my macros folder tool-change.ngc file, and i dont know how to make both work, i.e the toolsetter is already configured, and have the touch probe working too, both on the same input pin.15 parport 0

I presume it's this line that causes the error:
So if you have 'parport.0.pin-15-in' already linked to a signal named 'probe-input' then change the line above to this:

 

thanks aciera,
this is my line in my hal file

net probe-input motion.probe-input <= parport.0.pin-15-in

is there something wrong with this line?
from what i read lcnc only has one probe signal called "probe-input motion.probe-input" that deals with all probe signals, if i had them on seperate pins on my breakout board i would have to link them to a digital signal in software with an OR component i believe, so instead i did it with a relay that makes both probes NC as the touch probe was NO and the toolsetter is NC and i can realisticly only use one at a time,to save myself the trouble of figuring out the OR component and using a different input pin on my breakout board, and as you can tell without help from people like you, id just be lost.
if i comment it out i have no signal from the probe sent to linuxcnc,
if i leave it in and edit the line you suggested in my custom_postgui.hal file
i now get this error

custom_postgui.hal:23: Pin 'motion.probe-input was already linked to probe-input

i really appreciate your help, i considered myself to be intelligent to a certain degree but linuxcnc makes me feel dumb, because no matter how much i read or how many videos i watch it just doesnt seem to click

Think of hal file as a distribution box full of wires, the "net" command is literally "connect this pin to that pin"
Usually the firts name after net is whatever you want to call a signal (think of it as a buss bar) and other pins can be wired to it and can be used over and over throughout the hal file as needed.
Other names must be existing LinuxCNC pins.

thankyou tommy, that makes sense now, so my "net probe-input motion.probe-input <= parport.0.pin-15-in" is getting a signal from pin 15 on my paralell breakout board, so those signal names are connected to components in my HAL.files, if i get it right? when i was putting that line into my machine.hal and setting up easyprobe, i kept getting errors, with help from aceira and you just explaining that, i shortened that line to "net motion.probe-input <= parport.0.pin-15-in" and pow, it works, the only reason i was using that line was because i read a forum post, that said that that pin in software controls all probing routines, it worked fine with my toolsetter but when trying this out easyprobe 2 it came up with errors that flagged that comment, without your help id have not been able to get it running, thankyou guys so much, tommy, aciera, talla, tillman, and julian, great work on the add on, and thanks for taking the time to help me guys i really appreciate it, i just have one problem left to solve, as my toolsetter uses an m6 remap which causes the spindle to do a manual toolchange subroutine, insert tool, move to toolsetter coordinates, and probe Z tool height, how would i stop this happening when i want to use the touch probe? the subroutines are in my macros folder and any m6 command causes the toolchange routine as i explained, is there a way to do this? i thought of making seperate macros folders for the toolchange macros and the probing macros, but the m6 would still cause a toolchange subroutine, and the toolsetter is quite tall so i cant just let the routine run without the toolsetter in place as it would break my touch probe,and if i let it run and move the toolsetter it would fail to touch the wasteboard before reaching the max Z travel i specified in the m6 subroutine if the probe isnt triggered, any ideas? ps when i get the last part sorted out i will write a tutorial and or make a video on how to get this set up if you already have a postgui.hal file, as already having certain files made the whole install tricky but again with every mountain to climb ive learned some very useful stuff, which i could probably pass on or help another newbie to linuxcnc to get this up and running