Mesh grid compensation - Setup on Initial Gcode

Phaedrux

@FelixH that's good. That's as it should be. Does that include g30 with the probe or manual?

FelixH

with the probe. If I do it outside of a print, it's not a problem. If I do it within the initial code of the print, then I get the warnings, i.e. that the probe was already triggered at the beginning of the probing. Yesterday I recimped the terminals of the probe. Everything is sound

infiniteloop

@FelixH said in Mesh grid compensation - Setup on Initial Gcode:

If I do it within the initial code of the print, then I get the warnings…

Looks to me as if the slicer commands the head to Z=0 before your G30 is executed in the initial section. As a test, you might insert a G0 Z4.0 (or whatever height is appropriate for your probe to keep free from the bed) just above the G30.

Phaedrux

@infiniteloop said in Mesh grid compensation - Setup on Initial Gcode:

@FelixH said in Mesh grid compensation - Setup on Initial Gcode:

If I do it within the initial code of the print, then I get the warnings…

Looks to me as if the slicer commands the head to Z=0 before your G30 is executed in the initial section. As a test, you might insert a G0 Z4.0 (or whatever height is appropriate for your probe to keep free from the bed) just above the G30.

It would appear he's got it at 15mm above the bed. and the probe offset is 12mm.

G1 Z15.  ; go close to to the surface
G30        ; Z=0 datum thing
G1 Z75    ; go up a bit

But maybe it should be higher still incase the homed height is off? 25mm maybe?

infiniteloop

@Phaedrux said in Mesh grid compensation - Setup on Initial Gcode:

It would appear he's got it at 15mm above the bed. and the probe offset is 12mm.

That’s absolutely fine, but: I had a similar problem with Cura when trying to set the extruder to relative movements - Cura tends to put some own lyrics in front of the user-defined intro, depending on settings and prefs. That’s why I propose a quick test - else, we should have a look at the first lines of Gcode from the slicer.

FelixH

@Phaedrux said in Mesh grid compensation - Setup on Initial Gcode:

It would appear he's got it at 15mm above the bed. and the probe offset is 12mm.
G1 Z15.  ; go close to to the surface
G30        ; Z=0 datum thing
G1 Z75    ; go up a bit
But maybe it should be higher still incase the homed height is off? 25mm maybe?

well, damn it!

ladies and gentlemen, we can close this thread as the error has been found.

The G1 Z15 command was implemented in order to control the speed while diving down. Apparently it didn't occur to me that the probe offset is 16.10mm. So the probe effectively was triggered before the G30 command was event queued. I just did a test run with a G1 Z25 instead and, voilà... it worked... I swear I never noticed the probe touching before the G30 command...

Thank you all for your brainstorming and patience!

Phaedrux

@infiniteloop

Glad you got it sorted out finally.

infiniteloop

@Phaedrux said in Mesh grid compensation - Setup on Initial Gcode:

Glad you got it sorted out finally.

Just jumped in when you had narrowed down the cause to a single question: if G30 works stand-alone, what is different when it resides in a .gcode file? So the honours belong to you, Sherlock

FelixH

@infiniteloop said in Mesh grid compensation - Setup on Initial Gcode:

@Phaedrux said in Mesh grid compensation - Setup on Initial Gcode:

Glad you got it sorted out finally.

Just jumped in when you had narrowed down the cause to a single question: if G30 works stand-alone, what is different when it resides in a .gcode file? So the honours belong to you, Sherlock

I coudn't agree more. It was not my doing at all...

infiniteloop

@FelixH said in Mesh grid compensation - Setup on Initial Gcode:

It was not my doing at all...

Sorry, but I disagree. Looking at those (rare) dudes who boldly claim to never ever having made anything wrong, thus always suspecting others to be the sole cause of their mishap, I have to appreciate that you instead tried to understand what’s going wrong, throughout the whole thread. Finally, it was you who put the loose ends together and spotted the gcode fragment in question. I think @Phaedrux won’t object if I state that it is fun to work with guys like you.

Phaedrux

Yes it's always a pleasure working together towards a common goal with a positive attitude.

FelixH

I hope this thread is useful to someone else...

Thanks again guys!