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

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.

fcwilt

@barbarossa-cologne

Well it seems the bed.g file you edited to enter the M291 command is not the bed.g file that G32 is executing.

Are you editing the bed.g file that is in the system directory - the directory where the config.g file is located?

Frederick

dutti

@fcwilt

for your question:

dutti

@fcwilt something to do with this code in config.g?



; Z-Probe
M558 P9 C"io4.in" H10 F200 T1800 ; set Z probe type to bltouch and the dive height + speeds
M950 S0 C"io4.out" ; create servo pin 0 for BLTouch
G31 P25 X-20 Y-20 Z2.5 ; set Z probe trigger value, offset and trigger height
M557 X15:650 Y15:650 S200 ; define mesh grid

fcwilt

Hi,

Now we are getting somewhere I think.

Notice on the left hand side you have MACROS selected.

Is that correct?

If so the files there are not the system files the firmware is using.

Those file are in the SYSTEM directory - the item below the MACROS item.

Select the SYSTEM item and take a look and see what is there.

Frederick

dutti

@fcwilt
ahhhh I know what you mean.... at the systems page my bed.g is:

; bed.g
; called to perform automatic bed compensation via G32
;
; generated by RepRapFirmware Configuration Tool v3.1.3 on Tue Jun 23 2020 22:36:44 GMT+0200 (Mitteleuropäische Sommerzeit)
M561 ; clear any bed transform
G29  ; probe the bed and enable compensation

fcwilt

Hi,

Well there is the G29 that G32 has been invoking.

I think you have a problem with files being in the MACROS directory rather than the SYSTEM directory.

You are going to have to determine if the some or all files in the MACROS directory need to be moved to the SYSTEMS directory.

If the files in the SYSTEMS directory are the ones you want to keep you should delete the files in the MACROS directory that have the same name.

For example - you should have homeall.g in your SYSTEMS directory. You should NOT have homeall.g in your MACROS directory.

Think you can get this sorted out?

Frederick

dutti

yes.. I know. It was stupid....
Now I took every code into the systems page.
Now, I have the message ´´failed to enable endstops´´when I make a single z probe.