Auto_Bed_Leveling: Z-Probe Repeatability code

[brainscan]

Hi Roxy sorry I havent got back to you for a couple of days but work has been crazy and I needed a rest. I'm just about to try a print with pronterface and your code and thought i'd just add the M48 code first. When I added in the code it wouldnt compile saying #endif without #if at the very end of your code, I tried just removing the #endif line and it compiled and seems to work but don't really know if i've done something stupid. Here are my first results just sending an M48 command
>>>M48
SENDING:M48
M48 Z-Probe Repeatability test. Version 1.85
Mean: -0.167070
Standard Deviation: 0.002544
echo:endstops hit: Z:-0.17

I will have a go at printing something now and see how it goes but when I ran G29 last time this was my result
Bed Level Correction Matrix:
0.999998 0.000000 0.002131
0.000000 0.999999 0.001302
-0.002131 -0.001302 0.999997
isnt the last line supposed to be positive numbers? Or have I got that confused? Thanks again in advance

*Just wanted to try it one more time just to make sure
>>>M48 n10 V4
SENDING:M48 n10 V4
M48 Z-Probe Repeatability test. Version 1.85
Positioning probe for the test.
1 of 10 z: -0.791797 mean: -0.791797 sigma: 0.000000
2 of 10 z: -0.793750 mean: -0.792773 sigma: 0.000977
3 of 10 z: -0.792187 mean: -0.792578 sigma: 0.000844
4 of 10 z: -0.794531 mean: -0.793066 sigma: 0.001118
5 of 10 z: -0.793359 mean: -0.793125 sigma: 0.001007
6 of 10 z: -0.798828 mean: -0.794075 sigma: 0.002316
7 of 10 z: -0.807422 mean: -0.795982 sigma: 0.005139
8 of 10 z: -0.805469 mean: -0.797168 sigma: 0.005740
9 of 10 z: -0.800781 mean: -0.797569 sigma: 0.005530
10 of 10 z: -0.800000 mean: -0.797812 sigma: 0.005296
Mean: -0.797812
Standard Deviation: 0.005296
echo:endstops hit: Z:-0.80

[Roxy]

Hi Roxy sorry I havent got back to you for a couple of days but work has been crazy and I needed a rest.

No Problem!!!

I'm just about to try a print with pronterface and your code and thought i'd just add the M48 code first. When I added in the code it wouldnt compile saying #endif without #if at the very end of your code, I tried just removing the #endif line and it compiled and seems to work but don't really know if i've done something stupid. Here are my first results just sending an M48 command

It looks from the printout later that everything is good... But if you attach your current Merlin_Main.cpp I'll do a quick DIFF and make sure that #endif was safe to take out.

>>>M48
SENDING:M48
M48 Z-Probe Repeatability test. Version 1.85
Mean: -0.167070
Standard Deviation: 0.002544
echo:endstops hit: Z:-0.17

I will have a go at printing something now and see how it goes but when I ran G29 last time this was my result
Bed Level Correction Matrix:
0.999998 0.000000 0.002131
0.000000 0.999999 0.001302
-0.002131 -0.001302 0.999997
isnt the last line supposed to be positive numbers? Or have I got that confused? Thanks again in advance

Adding a 't' or 'T' to the G29 is helpful because you can see how flat the bed is from the Bed Height Topology map. Ideally, you should have a '0' after each decimal point. Like +0.0xxx or -0.0xxx The last line isn't supposed to be positive. I bet you are thinking about previous discussions where people's Z-Axis was going the wrong direction. The DIAGONAL of the matrix should be POSITIVE!!!!

*Just wanted to try it one more time just to make sure
>>>M48 n10 V4
SENDING:M48 n10 V4
M48 Z-Probe Repeatability test. Version 1.85
Positioning probe for the test.
1 of 10 z: -0.791797 mean: -0.791797 sigma: 0.000000
2 of 10 z: -0.793750 mean: -0.792773 sigma: 0.000977
3 of 10 z: -0.792187 mean: -0.792578 sigma: 0.000844
4 of 10 z: -0.794531 mean: -0.793066 sigma: 0.001118
5 of 10 z: -0.793359 mean: -0.793125 sigma: 0.001007
6 of 10 z: -0.798828 mean: -0.794075 sigma: 0.002316
7 of 10 z: -0.807422 mean: -0.795982 sigma: 0.005139
8 of 10 z: -0.805469 mean: -0.797168 sigma: 0.005740
9 of 10 z: -0.800781 mean: -0.797569 sigma: 0.005530
10 of 10 z: -0.800000 mean: -0.797812 sigma: 0.005296
Mean: -0.797812
Standard Deviation: 0.005296
echo:endstops hit: Z:-0.80

Those are super good numbers!!! Trike is the only one with better numbers so far. You might want to use the 'L' parameter to stress the X & Y axis a little also and see if there is much additional extra slop there. Like M48 L 7 but my guess is your machine is very tight and crisp! I wish mine could do those numbers!

[brainscan]

No Problem!!!



It looks from the printout later that everything is good... But if you attach your current Merlin_Main.cpp I'll do a quick DIFF and make sure that #endif was safe to take out.



Adding a 't' or 'T' to the G29 is helpful because you can see how flat the bed is from the Bed Height Topology map. Ideally, you should have a '0' after each decimal point. Like +0.0xxx or -0.0xxx The last line isn't supposed to be positive. I bet you are thinking about previous discussions where people's Z-Axis was going the wrong direction. The DIAGONAL of the matrix should be POSITIVE!!!!!

Yes now you've said it you're right I am thinking about the delta being positive (my maths is bad anyway so I get confused easily), I will add in a T to the G29. I am still having problems with it though, tried a print and the nozzle still just air prints. The z axis move to show its using the bed level matrix but because its so far from the bed I cant tell if its following it properly. Sorry I know this is the wrong thread for this problem so I will make a new post there with any files you want? Thank you, feel so close now!!!

Those are super good numbers!!! Trike is the only one with better numbers so far. You might want to use the 'L' parameter to stress the X & Y axis a little also and see if there is much additional extra slop there. Like M48 L 7 but my guess is your machine is very tight and crisp! I wish mine could do those numbers!

Thanks I was surprised how good they were actually and I know there is play in the probe as its only a thrown together prototype(cant print my new one until I sort out the bed levelling)

[Arno_Millenaar]

Hi Roxy,

Thanks for writing this nice feature for testing the Auto_Level sensor. I noticed your post at the Marlin GitHub and hence found this forum. Next i patched the Marlin_Main.cpp and tested my setup.

The results are very interesting indeed. Without retraction the deviation is at what I consider at the theoretical limit of the Z-Probe design I have as I get an astonishing 0.000691 (yes that’s right, 3 leading zero’s) i.e. better than 1 Mill accuracy. (1/1000mm).

However when adding ‘Retract’ this drops to 0.004797. This indicates that the ‘shaft-rotation’ in my design still induces a small deviation or I need to make a more accurate ‘head’ for the sensor probe. However if you then think about the BED flexing up and down when being heated even when this is done under PID control, then I believe that any further improvements will be futile as Bed Bending caused by temperature fluctuation and moving cooling fan’s around while printing will most likely be a bigger factor.

FYI: I use a M5 Ultra-Mini Proximity Sensor in combination with a bronze probe with a small metal nut on top, retracted by a mini servo. However the Servo is not part of the measurement and only used to lift the probe. Still I noticed that due to the lifting the probe, it slightly rotates each time its gets lifted and retracted, hence the difference in results when adding ‘retract’ to the M48 test command.

This Z-probe design I made can be applied to many extruder setup’s so if anybody is interested you can find a description of the setup at the following link: http://creatrtips.freeforums.org/vie....php?f=8&t=160

Here is a link for the mini proximity sensor I use: http://jimou.en.alibaba.com/product/...ty_sensor.html Type 10-30V NPN N.O. with a switching distance of 0.8mm

I also noticed (especially when using mechanical switches) that slowing down the second and final probe movement increases the accuracy significantly. I therefor patched the ‘homing_feedrate[Z_AXIS] ‘ lines within marlin_main.cpp to be divided by 8 where the default is only 2. This makes a notable difference. Even for a non-mechanical sensor such as an induction proximity sensor.

Results from M48 testing:
Without Retract:
10:25:02.150 : M48 Z-Probe Repeatability test. Version 1.85
10:27:22.410 : Mean: 12.281874
10:27:22.410 : Standard Deviation: 0.000691
10:27:22.410 : echo:endstops hit: Z:12.28

With Retract:
10:33:23.254 : M48 Z-Probe Repeatability test. Version 1.85
10:36:09.816 : Mean: 12.280522
10:36:09.816 : Standard Deviation: 0.004797
10:36:09.816 : echo:endstops hit: Z:12.29

Thanks again for sharing this nice feature with the 3D community,

Rgds, Arno

[Roxy]

Here is a link for the mini proximity sensor I use: http://jimou.en.alibaba.com/product/...ty_sensor.html Type 10-30V NPN N.O. with a switching distance of 0.8mm

I also noticed (especially when using mechanical switches) that slowing down the second and final probe movement increases the accuracy significantly. I therefor patched the ‘homing_feedrate[Z_AXIS] ‘ lines within marlin_main.cpp to be divided by 8 where the default is only 2. This makes a notable difference. Even for a non-mechanical sensor such as an induction proximity sensor.

Thanks for the hint!!! I'm going to set my homing_feedrate[Z_AXIS] to divide by 8 also!!! And once its benefit is confirmed, I'll change the directions in the first post of this thread.

[DrLuigi]

Lately ive got the issue that the button sticks, wich causes the Z endstop being pressed all time,
I was already guessing this would happen due the hairspray,
Do you have any advice ?
I guess i will try and leave it like that unstucked, for 3 days and afterwards replace it if it didnt go away.

[Roxy]

Lately ive got the issue that the button sticks, wich causes the Z endstop being pressed all time,
I was already guessing this would happen due the hairspray,
Do you have any advice ?
I guess i will try and leave it like that unstucked, for 3 days and afterwards replace it if it didnt go away.

Wow! That is horrible! The only thing I can think of would be to soak the switch in acetone. But given how cheap those switches are, I don't think I would risk it. I suspect it would be safe to soak it in acetone but the problem is you can't see what is inside. I would be worried the opposite thing would happen. I would worry a thin film of plastic got deposited on the contacts and then everything would act flakey.

I kind of risk the same thing spraying hair spray on the bed with the probe measuring things. But the good news is I'm spraying down and the switch button is kind of shielded. But I'm going to be more careful going forward!

[DrLuigi]

Wow! That is horrible! The only thing I can think of would be to soak the switch in acetone. But given how cheap those switches are, I don't think I would risk it. I suspect it would be safe to soak it in acetone but the problem is you can't see what is inside. I would be worried the opposite thing would happen. I would worry a thin film of plastic got deposited on the contacts and then everything would act flakey.

I kind of risk the same thing spraying hair spray on the bed with the probe measuring things. But the good news is I'm spraying down and the switch button is kind of shielded. But I'm going to be more careful going forward!

Just as an update, It kinda resolved now,
After a few clicks i gave it every few hours, it kinda became better and better.

I did have a few crashes tho, that it pressed once, went up, went back down and didnt stop immeaditly lol.. Hopefuly that doesnt happen anymore :P

/edit
Just had it again, weird it just goes to the platform, totaly pressed and just doesnt stop lol..

/edit
Well i guess i have found the problem, and a solution, I guess my glass was just to dirty of hairspray that it seem to have probems with it,
I cleaned it and it does it again just fine.

[tobben]

Sticky due to constructiveness and usefulness

[Roxy]

Sticky due to constructiveness and usefulness

Updated code coming soon... School work got in the way, and then I tried to move to Arduino 1.05 and everything went Pear-Shaped. But I can build again and will have updated G29 code (that is compatible with the latest release of Marlin) to combine with the updated M48 Z-Probe repeatability code soon....

M48 Z-Probe Repeatability code has been updated to include an L parameter to add legs of movement prior to each measurement. The code is attached to the first post in this thread.