Hello Guest it is July 16, 2019, 12:59:24 PM

Author Topic: touch probe function question  (Read 420 times)

0 Members and 1 Guest are viewing this topic.

Re: touch probe function question
« Reply #30 on: July 14, 2019, 01:05:27 AM »
Hi,
I'm out of my depth, please ignore my previous post. As I have said there is no documentation AFIK to help you
interpret the log file.

Code: [Select]
2019-07-13 13:50:32.623 - API: mcCntlGcodeExecute() called. (G 91
F 5)
2019-07-13 13:50:32.823 - Attempt transition from "Idle" on event "MDI Start" Controller.cpp:1811
2019-07-13 13:50:32.823 - S_IDLE_on_exit
2019-07-13 13:50:32.823 - ACTION_start_mdi
2019-07-13 13:50:32.823 - S_MDI_RUNNING_on_entry
2019-07-13 13:50:32.823 - S_MDI_RUNNING2_on_entry
2019-07-13 13:50:32.824 - Signal id 1114, (Gcode Running), changed from LOW to HIGH.
2019-07-13 13:50:32.846 - API: mcCntlEStop() called.
2019-07-13 13:50:32.846 - API: mcCntlEnable(false) called.
2019-07-13 13:50:32.846 - API: mcCntlCycleStop() called.

Look at the first line:   mcCntlGcodeExecute() called. (G 91 F 5)

Look at the retract move: G91 F5.....so where is the axis command?. G91 sets relative mode, the G31 previously executed
sets the motion mode of G1. Thus your G91 F5 says linear interpolated move at feedrate of 5......but what axis? If I'm not
mistaken....'It is an error if no axis word is  commanded'.

Craig
My wife left with my best friend...
     and I miss him!
Re: touch probe function question
« Reply #31 on: July 14, 2019, 10:18:12 AM »
Thank you for looking at this.  What is truely frustrating is that I am convinced that the solution is going to be simple even if illusive.  At this point I can only hope that someone with some knowledge about this process can chime in and help me figure this out.

thanks again for your effort.
Charlie
Re: touch probe function question
« Reply #32 on: July 14, 2019, 11:02:01 AM »
Here are the parameters that I'm using in case someone sees something that be causing this issue.
Re: touch probe function question
« Reply #33 on: July 14, 2019, 01:35:40 PM »
Hi,
I think your prep distance is too much. It only needs to be clear of the surface, say 0.25 inch.
I Think also your retract distance is wrong. If I'm not mistaken the retract height is relative to the nominal
surface, again 0.25 inch should be enough.

Craig
My wife left with my best friend...
     and I miss him!
Re: touch probe function question
« Reply #34 on: July 14, 2019, 05:25:13 PM »
Hi Charlie,

Looking at the last error history (click the "history" button) is a good way to see what is happening when using mcTouchOff. The guys at Mach have been very helpful by sending messages there when things are happening in that script, such as a probing move, setting offsets, retract moves, etc.

The command that Craig mentioned, G91 F5 followed by mcCntlEstop, looks like it is from the CheckProbe() function in the script. Look for the "CheckProbe failed" comment. It's also sending a message to the error log so it will be telling you something in that last error history.
Re: touch probe function question
« Reply #35 on: July 15, 2019, 10:46:25 AM »
Hi,
I think your prep distance is too much. It only needs to be clear of the surface, say 0.25 inch.
I Think also your retract distance is wrong. If I'm not mistaken the retract height is relative to the nominal
surface, again 0.25 inch should be enough.

Craig

I’m not sure I follow.  Your suggesting 0.25 inch which is greater than 5 mm.  Of course that is assuming that mach4 would assume the units I am working.  I tried to add “mm” to the number but it wouldn’t allow anything but numbers.
Re: touch probe function question
« Reply #36 on: July 15, 2019, 10:50:51 AM »
Hi Charlie,

Looking at the last error history (click the "history" button) is a good way to see what is happening when using mcTouchOff. The guys at Mach have been very helpful by sending messages there when things are happening in that script, such as a probing move, setting offsets, retract moves, etc.

The command that Craig mentioned, G91 F5 followed by mcCntlEstop, looks like it is from the CheckProbe() function in the script. Look for the "CheckProbe failed" comment. It's also sending a message to the error log so it will be telling you something in that last error history.

I will look at this as soon as I Finnish my current task (which is sitting in the a/c recouping from working in the un-airconditioed shop on a very hot day in Florida)