I'm trying to mill some PCB's and so I am using the Auto-Level feature.

I’m trying to mill some PCB’s and so I am using the Auto-Level feature. I notice as it goes along probing, after each touch it retracts upwards at least 25mm. Is there a way to change that distance to say 3mm or something like that? It’d make the probing go a whole lot faster as it would not have to travel down for so long at the slow probing speed. Sorry if this has been asked before.

There’s a clearance height value in the widget. It defaults to 1.5mm so not sure why you’re seeing 25mm.

Huh, strange. Today I started everything up fresh and it behaves normally and is using the proper clearance height.
Is there any reason it has a 2 second delay between positioning at the next probe location and beginning to move down at the probe feed rate? i.e. moves up, over, down, delay 2 sec, probe, repeat. Not a huge deal though, still a lot faster today than it was yesterday. Thanks.

I’m still having troubles with Auto-Level. Now I have the dreaded “Auto-Level stops after first probe” problem. I thought that was an issue only Grbl users were having, I am in the TinyG workspace. I have tried Chrome, FireFox, and Chrome on a brand new laptop with freshly installed drivers, SPJS, etc. My setup is TinyG v8 running firmware 440.20, FTDI Driver CDM v2.12.18 WHQL Certified, serial-port-json-server-1.92_windows_386, Chrome Version 52.0.2743.116 m. All my limit switches are NC, so the input pins are not just flapping in the breeze. I recall that when I first built mt CNC over a year ago, it was really stable at first with ChiliPeppr but at some point it became a little crazy. I almost always have a problem where when I start a job, it will abruptly stop moving a few operations into the job. TinyG does not respond to any commands. If I unplug the USB but leave TinyG powered on and do not reset it, kill SPJS, then reconnect TinyG USB and start SPJS and reconnect in ChiliPeppr, I can usually restart without loosing XYZ position. Also it tends to stay stable after that until next time I power everything off and on again. I can piste my $$ config from TinyG if that would be helpful. I’m running out of logical troubleshooting steps and its starting to look like a case of satanic possession. LOL

You should probably turn off the filter in the Serial Port Console and watch what is coming back from TinyG. I’ve seen errors come back on probing before and that could be why.

I turned off the serial port console filter.
I ran an Auto-Level and got it to stop at first touch. Then I messed around for a while and restarted things and got it to work normally.

When it stops on the first probe touch, it looks like this:

{“sr”:{“posz”:-0.418}}
{“sr”:{“posz”:-0.520}}
{“sr”:{“posz”:-0.622}}
{“sr”:{“posz”:-0.625,“vel”:2.49}}
{“r”:{“prb”:{“e”:1,“x”:-0.396,“y”:-0.336,“z”:-0.625,“a”:0.000,“b”:0.000,“c”:0.000}},“f”:[1,0,0,1585]}
{“sr”:{“vel”:0.00,“coor”:1,“stat”:3}}
{“qr”:32}
… Then nothing further happens in the log.

When it works normally, it looks like this:

{“sr”:{“posz”:-0.622,“mpoz”:-0.622}}
{“sr”:{“posz”:-0.722,“mpoz”:-0.724}}
{“sr”:{“posz”:-0.824,“mpoz”:-0.826}}
{“sr”:{“posz”:-0.902,“vel”:2.49,“mpoz”:-0.902}}
{“r”:{“prb”:{“e”:1,“x”:-0.396,“y”:-0.336,“z”:-0.902,“a”:0.000,“b”:0.000,“c”:0.000}},“f”:[1,0,0,8160]}
{“sr”:{“vel”:0.00,“stat”:3,“coor”:1,“momo”:4}}
{“qr”:32}
… then continues with next probe and so on.

I notice the failed one is missing “momo”:4 on the “sr”. I’m not sure if that is important or not, I just see a difference there so I am wondering if perhaps it stops because there’s missing status information that was expected?

Hmm. That debug output looks more or less the same. I figured you’d see a probe error but i’m not seeing that in your output.

I did some more troubleshooting. It seems to be something abut Eagle BRD Import and Auto-Level clashing. See my troubleshooting procedure below.

Start PC
Turn on CNC/TinyG
Start SPJS
Start Chrome
Go to http://chilipeppr.com/tinyg?forcerefresh=true#
Drag .brd file into Eagle BRD Import
Click Send Gcode to Workspace from Eagle BRD
Run Auto-Level
Auto-level stops as soon as first probe touches.

(Click go to G54 Zero)

Pressed reset button on TinyG and changed nothing else.
Run Auto-Level
Auto-level stops as soon as first probe touches.

(Click go to G54 Zero)

power-cycled entire CNC and TinyG board and changed nothing else.
Reconnected to TinyG by selecting check box
Run Auto-Level
Auto-level stops as soon as first probe touches.

(Click go to G54 Zero)

Closed and restarted SPJS and changed nothing else.
Reconnected to TinyG by selecting check box
Run Auto-Level
Auto-level stops as soon as first probe touches.

(Click go to G54 Zero)

Terminate all chrome processes in Task manager and changed nothing else.
Start Chrome
Go to http://chilipeppr.com/tinyg?forcerefresh=true#
Drag .brd file into Eagle BRD Import
Click Send Gcode to Workspace from Eagle BRD
Run Auto-Level
Auto-level stops as soon as first probe touches.

(Click go to G54 Zero)

Terminate all chrome processes in Task manager and changed nothing else.
Start Chrome
Go to http://chilipeppr.com/tinyg?forcerefresh=true#
Leave cached board alone, no touching Eagle BRG Import.
Run Auto-Level
Auto-level WORKS FINE!

(Reset new safe Zero since now Z0 is touching board.)

Terminate all chrome processes in Task manager and changed nothing else.
Start Chrome
Go to http://chilipeppr.com/tinyg?forcerefresh=true#
Drag .brd file into Eagle BRD Import
Click Send Gcode to Workspace from Eagle BRD
Run Auto-Level
Auto-level stops as soon as first probe touches.

(Click go to G54 Zero)

Close chrome normally
Start Chrome
Go to http://chilipeppr.com/tinyg?forcerefresh=true#
Leave cached board alone, no touching Eagle BRG Import.
Run Auto-Level
Auto-level WORKS FINE!