Try this

G91 ; relative mode G1 H2 Z10 F200 ; raise head to avoid dragging nozzle over the bed G1 H1 X-350 F3000 ; move up to 240mm in the -X direction, stopping if the homing switch is triggered G1 X4 F600 ; move slowly 4mm in the +X direction G1 H1 X-10 ; move slowly 10mm in the -X direction, stopping at the homing switch G1 H1 Y300 F3000 ; move up to 240mm in the Y direction, stopping if the homing switch is triggered G1 Y-4 F600 ; move slowly 4mm in the -Y direction G1 H1 Y10 ; move slowly 10mm in the Y direction, stopping at the homing switch ;G1 Z-300 F3000 S1 ; move up to 240mm in the -Z direction, stopping if the homing switch is triggered ;G1 Z4 F600 ; move slowly 4mm in the +Z direction ;G1 Z-10 S1 ; move slowly 10mm in the -Z direction, stopping at the homing switch G90 ; back to absolute mode G1 X20 Y180 F3600 ; Move to position on glass. G4 P1000 ; Wait one second to let probe clear. ; G30 ; Home Z with probe ; G1 Z10 F3600 G1 X150 Y100 ; center M280 P3 S90 I1 ; reset probe G30 G90 ; absolute positioning G1 Z20 F4000 M280 P3 S90 I1 ; reset probe

@Coded-Games said in G29 does not deploy BL Touch (Duet Wifi 1.02):

M584 X1 Y0

YOu'll need to finish defining all of the drivers in M584, and the M584 command needs to be moved higher up in the file. Like right above the M350 command.

@Coded-Games said in G29 does not deploy BL Touch (Duet Wifi 1.02):

M574 X1 Y2 Z1 S1 ; set homing switch configuration

This command is no longer valid in RRF3.

See here: https://docs.duet3d.com/User_manual/Reference/Gcodes#m574-set-endstop-configuration

You may want to generate a new config file set using the online config tool to see what a modern config set looks like for comparison.

https://configtool.reprapfirmware.org/Start

@foesi said in BL-Touch M402 and M280 P0 S90 do not retract pin:

@Phaedrux I tried to position the screw in a position where the test at power on just gets the pin back up in retracted position.
I can´t get the screw in the position as mentioned in the antclabs documentation - because then the pin would not get back up.
And I also used magnets to get the pin magnetised.🤷

This makes it sound like there is something wrong with the BLtouch.

@droftarts
Many thank's for your suggestion I will try it.

That message is coming from a user macro and not the firmware. What did you push before you got that message?

Hardware seems functional. For further help you'll have to provide some config files. config.g, homeall.g, homex homey homez bed.g and results of M98 P"config.g".

@JDigglyWiggly I did it out of sympathy for a dad with 3 kids under 10.

@Marcelofs13 said in Duet 3 busy after homing all:

RepRapFirmware for Duet 3 MB6HC version 3.01-RC9

please update to 3.2.2

@Phaedrux
Thanks a lot for the help.
I actually went through that tutorial before.. but, now it just works.
Didn't have to change a line and was few hours on that already,
I have no clue what happened... but happy o/

I think the PETG available today is generally as easy to print as PLA. Hotter temps and less cooling are the big differences. Otherwise most print settings can remain the same.

@dc42 said in Probe Accuracy Test Macro [Issues]:

@CCS86 said in Probe Accuracy Test Macro [Issues]:

@dc42: Does it sound like a bug for the probe offset to be applied over and over on repeated G30 P3 X0 Y180 Z-99999 F2000 calls?

That doesn't sound right. Please post the complete macro file you are running, and your config.g file, and tell us which firmware version you are running.

I was originally on 3.0, and now on 3.01-RC4

Unfortunately, I did not save the macro before modifying it. That is my fault.

I did find one error in my code, in asking it to probe at X0, when my probe has a +12mm offset. I feel like the firmware should catch this more gracefully though. It appears that it ignores the endstop switch and the X0 minimum designation, and tries to aggressively get the probe to X0 anyway, which hard crashes into the machine limit and jumps the belts.

Also, it appears that I can't probe more than 32 points before I am "out of range"

f5cb5f29-c4cd-481d-8a66-404810d82659-image.png

@palmhoej Hi, was there any progress? I've the same problem, and I've made some test about that:
https://forum.duet3d.com/topic/11093/bltouch-m558-accuracy-test-strange-behaviour

@icy_snake said in BLTouch Not Probing Multiple Times:

I have different Alu beds and glass beds. but all of them look close. That can´t be.
Also if I rotate them the drop stays always at the same back corner. Thats not possible!

It is possible, if the beds are flat but the gantry height varies with XY position. I test bed probing by deliberately putting a thin item (e.g. a microscope slide, or thin piece of plastic) on part of the bed.

Certainly worth a try...

EDIT:

Thanks...

Sometimes its the simple things you don't see... >_>

You may also find these wiki pages useful:

https://duet3d.dozuki.com/Wiki/Connecting_a_Z_probe#Section_BLTouch
https://duet3d.dozuki.com/Wiki/Test_and_calibrate_the_Z_probe
https://duet3d.dozuki.com/Wiki/ConfiguringRepRapFirmwareCartesianPrinter#Section_Homing_Z_using_a_Z_probe

@fallenhorseman Glad I could help.

Note to all guys: Yeah 4k7Ohm Pullup to 5V is resolving that issues

Funnily, I dont need a pullup between 5V and the PWM of the FAN, but I need one between GND and Z-Probe (as you can barely see in my picture 😉 . I use the 'old' version of BLTouch which is not 3.3V 'tolerant'. Am I missing something or is that a typo on your side?