G32 Error:´´ Z probe was not triggered during probing move´´

[dutti]

@fcwilt english is fine but especially person from the US or Australia uses expressions which I haven´t learned in school. I have to practice!

As to the heatmap.... I made a G32 but the Duet made a G29.
Before I made a nomral G30.
I know about G30.

Invoking G32 let the nozzle move to the first probe point of a G29 command. So the Duet makes a G29 instead of G32. How can so many things be wrong
Richard

[dutti]

@fcwilt
how can I make a G32 when my bed.g file isn´t there anymore?
I thought the software is calculating the high of each probing point in raleation to the leadscrews...

[fcwilt]

@barbarossa-cologne said in G32 Error:´´ Z probe was not triggered during probing move´´:

@fcwilt
how can I make a G32 when my bed.g file isn´t there anymore?
I thought the software is calculating the high of each probing point in raleation to the leadscrews...

Hi,

I want you to have a bed.g file but I only want it to contain the M291 command, for now, just as a test.

You invoke it with G32 which is access from the Duet Web Control (DWC) on the Dashboard, using the "Compensation and Calibration" drop down menu.

Once I am sure that nothing other than beg.g is running in response to G32 then we will insure the normal commands for auto bed leveling are back into bed.g and the M291 is gone.

That's why I said you can just comment everything else out and add the single M291 command. Commenting the other lines out will allow you to restore them just by removing the comment character.

Frederick

[dutti]

ok I understand!
so what can I do for the next steps?
richard

[fcwilt]

@barbarossa-cologne

Hi,

You mean after I'm sure that bed.g is running and nothing else unexpected happens?

Frederick

[dutti]

@fcwilt
to fix my multiple problems...

[fcwilt]

@barbarossa-cologne

Hi,

I am focusing on just two problems right now.

1. Making sure the probe is working.
2. Making sure bed.g is working.

Anything else you want to work on?

Frederick

[dutti]

@fcwilt
Probe is working.
I don´t know what I have to change in my bed.g file...
you told me you wanna make a test. So I did it.... and now?
I made a G32 and it´s doing a G29. Why?
I just wanna make a 4 point true auto level.... thats the last thing I have to do before printing. SOS

[fcwilt]

@barbarossa-cologne

Hi,

When you did the G32 did you see the popup message saying beg.g was running?

Frederick

[dutti]

@fcwilt
drives to the first probe point of mesh compension and --> g32 -->
Error: Z probe already triggered before probing move started

[dutti]

only this message came

[fcwilt]

@barbarossa-cologne said in G32 Error:´´ Z probe was not triggered during probing move´´:

@fcwilt
drives to the first probe point of mesh compension and --> g32 -->
Error: Z probe already triggered before probing move started

And this was with bed.g only having the M291 command?

Frederick

[dutti]

@fcwilt yes

[fcwilt]

@barbarossa-cologne said in G32 Error:´´ Z probe was not triggered during probing move´´:

@fcwilt yes

And you didn't see the popup message about bed.g running?

Frederick

[dutti]

@fcwilt no. just the message you see on the screenshot.

[fcwilt]

@barbarossa-cologne

Hi,

Do you know how to enter commands directly into Duet Web Control using the Console page?

Frederick

[dutti]

@fcwilt yes

[fcwilt]

@barbarossa-cologne

Good.

Enter M98 P"bed.g" and let me know what happens.

Frederick

[dutti]

@fcwilt said in G32 Error:´´ Z probe was not triggered during probing move´´:

M98 P"bed.g"

[dutti]

@fcwilt
and bed hasn´t reached the pin of the BL. I think it goes back to the same high then the bed was before the comand started.