Work with probe

Cool, I think that tells me exactly what I need to know:

(a) yes, to use both probes, you need to set or2 in the hal file (my previous post has a sample of how to do that) and,
(b) consider using the tool table with pre-set tool heights if you can manage a tool bit holder,
(c) my own add... I plan on setting up the tool height probe semi-permanently, and having the or2 logic even though I'm also going to try and use the tool-table workflow: I'll use the tool height probe if I wear out a bit or otherwise have something appear to have drifted, because I'm working with ER16/ER11/ER8 collets, and I think those are not as repeatable as you grownups have with your heavy duty setups

For ease of use, I think the best place to start for someone hopping from this thread to go use tool or xyz probing over in the new gui, would be to go to the QTVCP > qtdragon probing issues thread.

Just my two cents, thanks to everyone.

Vector wrote:

For ease of use, I think the best place to start for someone hopping from this thread to go use tool or xyz probing over in the new gui, would be to go to the QTVCP > qtdragon probing issues thread.

Just my two cents, thanks to everyone.

FInally somebody has seen the light 

GOOD AFTERNOON! I use linuxCNC for milling through the AXIS 2.7.15 program. The programm has a PROBE function to set the height of the tool along the z-axis. The function worked fine. And suddenly it stopped. I tried to work out various control programs, including those that were already in operation. Each time axis gives an error: "EOF in file\path to NC file\seeking o-word: <zero_on_z> from line: 0". I'm not an advanced linux user at all. And English is not my native. If someone has something to say how to fix the problem, please use it in a simpler way, without abbreviations and slang specifics. I think this is a linux programm bug.I tried to change the ini and hal files according to the instructions on the Internet, but without result. And I don't know how to find and fix it. Additional information may be required to restore equipment to working order? Thanks in advance.

I've found a file in my directory for copies with this line: ... o<zero_on_z> sub ... Maybe that is what suits him? But where should I put in or write in this file?

problem's been solved, thanks for silence

What am I doing wrong?I keep getting this error 
 
 

Hi Ho,

so I write here since it is linked on GitHub. Disclaimer I am  total new to CNC stuff so have patience with me.

I have LInuxCNC 2.8.4, Gmoccapy and use Probe Screen for LinuxCNC 2.8. I use a touch Probe and a Touch Plate. I "or" connected the input signals in HAL and debounced one of them. Everything is working as I would suspect except:

After a manual tool change and the subsequent probing operation it finishes above my touch plate. Then the programmed gcode resumes and wants to move first in Z to the working piece. This would result in a crash into my touch plate. 

My fast fix was to add a move operation into gcode directly after M6. But that is not nice… 

So my question is how to tackle the problem?
1. Do I configure my FreeCAD post processeor to add a move after every manual tool change?
2. Do I add a Move at the end of /psng/macros/_probe_tool.ngc?
3. Did I overlook somewhere a configuration option? Which normally handles this problematic. 

Cheerio and Thanks in advance 
Isaak 

installed version V3. The machine goes to the shift place, gives information and that's it, no window for confirmation.
 
Enter does not help, Esk interrupts the task. Who managed to start this, share the knowledge that you need to click or how to call the window.
And why the tool number with six zeros?