Auto_Bed_Leveling: Z-Probe Repeatability code

[Roxy]

Will try it tomorow or so,

Will edit this post to tell you what happend!

I guess tomorrow means after mid-night to you!

Seems to work fine now

Like the update, It didnt gave the (3 of 10 z: 2.918500)
before

M48 Z-Probe Repeatability test. Version 1.60
M48 'e' option specified.
1 of 10 z: 2.907250
2 of 10 z: 2.903000
3 of 10 z: 2.918500
4 of 10 z: 2.918250
5 of 10 z: 2.911250
6 of 10 z: 2.918500
7 of 10 z: 2.918750
8 of 10 z: 2.907500
9 of 10 z: 2.926250
10 of 10 z: 2.907000
Mean: 2.913625
Standard Deviation: 0.007037
echo:endstops hit: Z:2.91

No... It did do that, but you had to turn the 'v' option up to a high enough level. You can specify 'v 4' to get even more detail and a running calculation of standard deviation.

OK... I'll take the "M48 'e' option specified." out of the code now... I just wanted to see if that was really being seen since it wasn't working. With a very small servo delay, the probe didn't have time to get all the way up before it got kicked down again. Now there is a 1 second delay anytime the probe is getting moved.

Seems nice. I guess i should do a first layer of 0.2 tho. To calibrate i did it to 0.1 for my first layer to fine tune it. But when i retry it on 0.1 it is sometime iffy, not at the sweet spot.

I have a something for you to keep in the back of your mind. When I get my stuff crossed over to the current release you will want my G29 code for two reasons. I am running with n=5 for the number of probe points. It slows things down and is a little bit annoying. With that said, you will want it because the Z-Probe isn't being engaged and retracted again and again. That is going to help your accuracy. But the other reason is it will print a topographical map of the bed. You are going to be amazed at how the glass is not flat. I think you are going to find you have high and low spots that consistently show up. I have one spot on my bed that I know to avoid on certain types of prints. Just crossing the changes over to the new code base shouldn't be too hard. But I'm thinking the G29 code should have run time options like how big 'n' is and how verbose to be. So it might take a little bit longer to get it all together.

/edit second try on another place,
SENDING:M48 n 10 x 124 y 100 e v 2
M48 Z-Probe Repeatability test. Version 1.60
M48 'e' option specified.
1 of 10 z: 2.789000
2 of 10 z: 2.769000
3 of 10 z: 2.760750
4 of 10 z: 2.786000
5 of 10 z: 2.760000
6 of 10 z: 2.781250
7 of 10 z: 2.759750
8 of 10 z: 2.767750
9 of 10 z: 2.772000
10 of 10 z: 2.774750
Mean: 2.772025
Standard Deviation: 0.010128
echo:endstops hit: Z:2.78

Those are good numbers! Was the first set of numbers with the 'e' option not included? In other words, was the first set of numbers with the probe staying down and that is why its standard deviation is a little bit better than the second set of numbers?

I am kinda suprised, i thought it wouldnt be this accurate!

Thanks for the script

Before I fold my changes into the new code base I'm thinking I want to check out how much 'slop' is in the X and Y axis. I know what I want to do and soon there will be an extra parameter you can give the M48 code to stress the mechanics a little bit harder. I'm thinking your machine is going to do better than mine.