Probe panel for Axis GUI

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
 

ok M61 Q99 solves that problem all good for now
thanks again for the help guys

Hello Gentlemen,

I have encountered an issue with my installation of EasyProbe. After installation, I have taken care of all errors and was able to start LinuxCNC and when I go to calibrate the probe, I get the following error: Named Parameter #<_ini[probe]vel_fast> not defined

I know that vel_fast was a variable copied directly from the installation instructions and placed into the ini file.  Any help pointing me in the right direction would be greatly appreciated.

-Sean
LinuxCNC ver: 2.8.4

Hi.
Please show your .ini and your .hal files. There must be a wrong typing or something like that.

Julian

Here are my hal and ini files.

-Sean

Two things.

First of all delete everthing before the MDI command for G54. So delete(pr comment out):

MDI_COMMAND=...
MDI_COMMAND=...
MDI_COMMAND=...
MDI_COMMAND=...
MDI_COMMAND=...
MDI_COMMAND=...
MDI_COMMAND=G10 L20 P1 X0MDI_COMMAND=G10 L20 P1 Y0
MDI_COMMAND=G10 L20 P1 Z0
MDI_COMMAND=G0 X0
MDI_COMMAND=G0 Y0
MDI_COMMAND=G0 Z0

The mdi commands haveto be in the right order like in the hal.

Second. Delete the "[...]" after the parameters in your ini. Or use "#" for comments.

Julian

I deleting everything before the G54 command and edited the Probe_Postgui.hal file to reflect the changes. When I start LinuxCNC, I still get the error: Named Parameter #<_ini[probe]vel_fast> not defined

Is there something that I am missing for declaring the vel_fast variable in the .ini file other than what I copied and pasted from the instructions?


-Sean

He has it at the end of the .ini file.
The error sounds strange and I never had this one.

Other than copy paste the parts again I have no clue.

Julian