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/
@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"
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?
Yes, that will work. The G32 command is needed only if you are using multiple independently-driven leadscrews for the Z axis and have used M671 to set up the coordinates; then G32 will probe the bed and adjust them to level it. If instead you have a single Z motor and a belt driving multiple leadscrews, then you don't need the G32.
If you have a very accurate and level build, you don't need G29 either.
The bed compensation figures in the M122 report have no meaning when mesh bed compensation is in use.