Probe panel for Axis GUI

Hi,
Tilman and I worked the last weeks at Easyprobe 2.0. You can get the current version at his github:
github.com/hausen8/EasyProbe

A lot of bugs fixed and a lot of new functions. So have fun.

Best regards
Julian
 

thankyou for the reply, i will try this again as id given up trying to get this to work on my machine

I made a video about it. Maybe this will help someone.

english


german

talla you are a legend, ive watched several of your videos but they are usually in german, but this time you have it in english total kudos to you for doing that, i also saw a link to this on facebook so its doing the rounds, im going to try and get this installed on my machine but im in the process off setting up another pc with much lower latency for software stepping, and i already have a vfd.xml and post_gui.hal and it is throwing me off but im gonna try the 2.0 install and see how i get on, hopefully its the last thing i need to do before i start making chips and not worry about tuning and configurations, id also like to thank the devs for their time and effort they put into linuxcnc, its a major headache for a noob like me but the software has amazing potential and im going to stick with it

 ok sorry to be a pain but i tried installing this again, went through the tutorial and followed the steps in the video to install the ng file m130 and the easyicons.tff in the newly created fonts folder, i already have a pyvcp xml file that is used for the spindle rs485 control pyvcp panel called vfd.xml, so instead of adding the probe_panel.xml i edited my vfd.xml with the easy probe tab as per the manual, and in the (DISPLAY) section of my .ini file, i put vfd.xml instead of probe_panel.xml, i added the required entries under the (RS274NGC) and (HAL) sections

manuals instructed entries

[RS274NGC]
SUBROUTINE_PATH = macros
ON_ABORT_COMMAND = O <on_abort> call
FEATURES = 12
RETAIN_G43 = 0
INI_VARS = 1
HAL_PIN_VARS = 1

to my [RS274NGC] section

[RS274NGC]
PARAMETER_FILE = linuxcnc.var
SUBROUTINE_PATH = macros
REMAP=M6 modalgroup=6 ngc=tool-change
REMAP=M600 modalgroup=6 ngc=tool-job-begin
SUBROUTINE_PATH = macros
ON_ABORT_COMMAND = O <on_abort> call
FEATURES = 12
RETAIN_G43 = 0
INI_VARS = 1
HAL_PIN_VARS = 1

manuals instructed entries for HAL section

[HAL]
TWOPASS = on
HALFILE = Probe_preload.hal
POSTGUI_HALFILE = Probe_postgui.hal

to my (HAL) section

[HAL]
HALFILE = PRINTNC.hal
HALFILE = custom.hal
POSTGUI_HALFILE = vfd.hal
POSTGUI_HALFILE = custom_postgui.hal
POSTGUI_HALFILE = postgui_call_list.hal
TWOPASS = on
HALFILE = Probe_preload.hal
POSTGUI_HALFILE = custom_postgui.hal

and the (PROBE) section to my .ini file, in the manual,

the manual also says

*Note: When TWOPASS is activated, realtime components can not only be loaded in the main hal file but in any other hal file,
too. This allows us to offer a hal file with all required realtime components for [easy]probe so there is no need for you to
edit your machine hal file.*

also the manual says

*Note: LinuxCNC allows not more than one postgui hal file called from the ini file. If you already have a postgui hal file,
copy all content from the Probe_postgui.hal to your postgui.hal.*
so i dont use the Probe_postgui.hal file from the manual, i add the information to my custom_postgui.hal file.

now when i load linuxcnc it says classicladder couldnt load, and the only way to get it to run is commenting out the #TWOPASS = on ,in the hal section as i copy and pasted above , and when i do none of the buttons work on the probe tab, but classicladder loads, and my spindle panel works fine  , ive tried moving around the hal file entries in the hal section but had no luck, i have uploaded my machine config files, as i have an m6 remap for manual toolchanges and classicladder to control my spindle with an rs485 adapter, and tried with the 1.2 easy probe, and now struggling with this version

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/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

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