@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

I found it. Researching the answers for @Phaedrux , I realized I was resetting M558 in my homeall.g file which was overriding my M558 from config.g.

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?