Auto_Bed_Leveling: Enhanced G29 command

[Roxy]

Hi I just tried again and its downloaded fine this time, weird. The new copy i've made seems to be working better as it compiles and uploads and now when I run a g29 it doesn't do the annoying servo retract every move

Yes, that is intentional. But you can get it to E-ngage and retract the probe for each measurement if you want with the 'E' option. G29 E will give you back the annoying behavior.

but at the end the nozzle stays above the bed and cant be moved down to touch it, it actually raises the nozzle a fraction and shows as being at 0. Im using the probe as a z endstop so do I need to change M206 offset?

I suspect the reason you can't lower the nozzle is you have:

#define min_software_endstops true

It is trying to protect you. The Z-Axis height is computed as a result of all the probing and some points are measured higher than others. Where ever the zero point gets calculated, that #define keeps you from going lower. I don't use the software end stops. But before you turn this off, you might want to consider and try changing this line:

#define Z_MIN_POSITION -5 // (or how much you dare to allow it to violate the 0.00 mark on the Z-Axis)

I don't know about or use the M206 stuff. I doubt you need to mess with it. Let me know if these two things don't fix things for you. It is easy enough to add a couple lines of code to push the nozzle down some amount.

The last code I tried using added the two together so if both had an offset it would double the distance.
The other thing is the n parameter doesn't seem to have any effect, it always does 3x3

The n parameter doesn't have any effect??? Try G 29 n 99 and see if you get an error message. If not, we have some serious problems. But if so, it means the code is recognizing you gave it a number for one axis of the grid. If that gives you an error message, then G29 n 4 should do a 4 x 4 grid. Or G29 n 2 should give you a 2 x 2 grid.

although it moves around in a different pattern.

The order of the points is dependent on whether it is going to print a Bed Height Topology graph. If you set the V-erbosness level high enough or specify a T option, you will trigger the alternate path. The alternate path takes slightly longer (1 or 2 seconds) to accomplish, but it reduces the code complexity and code size dramatically.

Ive copied the output from the bed level matrix and topology map for you if that is of any help? Might be best to just leave the old copy alone as its a bit of a mash-up of different code. Sorry if i've wasted any of your time.

22:07:11.001 : Bed Level Correction Matrix:
22:07:11.009 : 0.999997 0.000000 0.002244
22:07:11.009 : 0.000000 1.000000 0.001029
22:07:11.009 : -0.002244 -0.001029 0.999997
22:07:11.312 : echo:endstops hit: Z:-0.40
22:08:14.532 : N180 G28 X0 *114
22:08:15.940 : N182 G28 Y0 *113
22:08:20.974 : N184 G28 Z0 *116
22:08:34.858 : N190 G29T0 *94
22:09:58.962 : Eqn coefficients: a: 0.00 b: 0.00 d: -1.02
22:09:58.962 :
22:09:58.966 : Bed Height Topography:
22:09:58.966 : --0.08199 +0.11606 +0.31254
22:09:58.970 : --0.27027 --0.05777 +0.11606
22:09:58.970 : --0.14293 --0.02691 +0.03520
22:09:58.970 :
22:09:58.974 : planeNormal x: -0.00 y: -0.00 z: 1.00
22:09:58.974 :
22:09:58.974 : Bed Level Correction Matrix:
22:09:58.978 : 0.999997 0.000000 0.002283
22:09:58.978 : 0.000000 1.000000 0.001003
22:09:58.982 : -0.002283 -0.001003 0.999997
22:09:59.285 : echo:endstops hit: Z:-0.40
22:10:43.899 : N213 M81 *58

I don't now what all that extra Nxxx stuff is. My suggestion is to just work off of the one I posted. Without the same source code, it is difficult to guess what is going on. But you have .5mm of difference between your lower left and upper right corner. The Auto_Bed_Leveling will correct for that, but you really ought to get that leveled out better. That is hugely excessive!

p.s Is there anyway to have the nozzle lift before the servo retracts at the end of G28 and G29? A few other people wanted the same thing and i'd tried using some of their code which might have caused me these problems in the first place. Thank you again for all the help.

Yes, that is not too hard to do. And in fact RegPye wanted the same thing. Let's get the first part working right... And I'll get a couple lines of code added to handle this request.