Auto_Bed_Leveling: Enhanced G29 command

[Roxy]

Is there a reason you have #define Z_SAFE_HOMING disabled? It shouldn't matter, but it is causing things to go down drastically different code paths than what is happening on my system. Can this be enabled for the debugging process?

[brainscan]

Is there a reason you have #define Z_SAFE_HOMING disabled? It shouldn't matter, but it is causing things to go down drastically different code paths than what is happening on my system. Can this be enabled for the debugging process?

I have this enabled currently, it was off in the first configuration.h I gave you.

[Roxy]

Can you attach your current Configuration.h and Marlin_main.cpp to your next post so we both have the same code to work off of?

[brainscan]

I really can't work out how i've messed things up so badly, i'm so sorry.

[Roxy]

What ever it is that is wrong... It isn't much... I'm going to edit in some more debug info....

Roxy Edit:

Can you add the Configuration_adv.h to the above post?

Thanks! I got the Configuration_adv.h file....


OK, please save your existing Marlin_main.cpp file. Probably, the easiest thing to do is rename it to Marlin_main.xxx because Arduino is going to try to use every .cpp file it finds. Attached is a Marlin_main.cpp file with very verbose debug information in the G28 command. If you can put this where your existing Marlin_main.cpp file was (is) and rebuild... Let's see what it says.

[brainscan]

Here goes, hope it makes sense to you. Ive been lost for a long time.

>>>G28
SENDING:G28
??? Going to zero Z-Axis with offset of: -7.400000
Debug-1: Z-Axis current location: 11.000000
Debug-2: Z-Axis current location: 0.000000
Debug-3: Z-Axis current location: 0.000000
Debug-4: Z-Axis current location: 0.000000
Debug-5: checking if we can delete Z specific homing code.
Debug-8: Z-Axis current location: 0.000000
Debug-9: Z-Axis current location: -0.780000
Debug-10: Z-Axis current location: -0.780000
>>>M114
SENDING:M114
X:84.00 Y:97.00 Z:-0.78 E:0.00 Count X: 84.00 Y:97.00 Z:-0.78

***The 11.00000 is because I raised the nozzle manually before G28, I did a G92 X0 Y0 Z0 then G28 heres what it gave, probably doesnt help you though.

>>>G28
SENDING:G28
??? Going to zero Z-Axis with offset of: -7.400000
Debug-1: Z-Axis current location: 0.000000
Debug-2: Z-Axis current location: 0.000000
Debug-3: Z-Axis current location: 0.000000
Debug-4: Z-Axis current location: 0.000000
Debug-5: checking if we can delete Z specific homing code.
Debug-8: Z-Axis current location: 0.000000
Debug-9: Z-Axis current location: -0.780000
Debug-10: Z-Axis current location: -0.780000
>>>M114
SENDING:M114
X:84.00 Y:97.00 Z:-0.78 E:0.00 Count X: 84.00 Y:97.00 Z:-0.78

[Roxy]

OK... I know what is going on. If you look at the above debug stuff... somewhere between Debug-8 and Debug-9 that stupid -0.78 offset comes into play. But there isn't much code in between these spots in our debug version of Marlin_main.cpp :

SERIAL_PROTOCOLPGM("Debug-8: Z-Axis current location: ");
SERIAL_PROTOCOL_F(current_position[Z_AXIS],6);
SERIAL_PROTOCOLPGM("\n");
if((home_all_axis) || (code_seen(axis_codes[Z_AXIS]))) {

current_position[Z_AXIS] += zprobe_zoffset; //Add Z_Probe offset (the distance is negative)

SERIAL_PROTOCOLPGM("Debug-9: Z-Axis current location: ");
SERIAL_PROTOCOL_F(current_position[Z_AXIS],6);
SERIAL_PROTOCOLPGM("\n");


zprobe_zoffset gets read out of EEPROM automatically when Marlin starts up. Somehow you got some bogus information stored in your EEPROM and it is messing up everything. You can clear it by doing an M502 command followed by a M500 to store the 'normal' values in EEPROM. I suspect after you do that, the numbers are going to change when you do a G28. If so... can you post the output from G28? And... If that is the case it might make sense to do a G29 and see what happens... And maybe add back in the correct values for:

#define Z_RAISE_BEFORE_HOMING ???
#define Z_RAISE_BEFORE_PROBING ???
#define Z_RAISE_BETWEEN_PROBINGS ???

And try another G28 followed by G29

If this seems to do reasonable things... The debug version of Marlin_main.cpp should go away and you can restore the one we saved. Although that has some extra debug stuff that will need to be deleted.

[brainscan]

You're an absolute genius!!!!!!!!!!!!!!!
>>>G28
SENDING:G28
??? Going to zero Z-Axis with offset of: -7.400000
Debug-1: Z-Axis current location: 20.000000
Debug-2: Z-Axis current location: 0.000000
Debug-3: Z-Axis current location: 0.000000
Debug-4: Z-Axis current location: 0.000000
Debug-5: checking if we can delete Z specific homing code.
Debug-8: Z-Axis current location: 0.000000
Debug-9: Z-Axis current location: 7.400000
Debug-10: Z-Axis current location: 7.400000
>>>M114
SENDING:M114
X:84.00 Y:97.00 Z:7.40 E:0.00 Count X: 84.00 Y:97.00 Z:7.40

In my excitement though I forgot to raise the head again before G29 and had to quickly hit the reset button. I think i'll add the z raise before back in and try again. I'll post the results but I think you've cracked it. Not sure when I last reset the EEPROM so I would never have thought to try that. Thank you thank you thank you, you're honestly a legend!!!

***Thank you so much, everything seems to be working. I just sent a G1 Z0.2 and it went down to what looks like 0.2, yes!!!! Gave it a few x and y moves and it tracks the bed exactly as it should.

>>>G28
SENDING:G28
??? Going to zero Z-Axis with offset of: -7.400000
Debug-1: Z-Axis current location: 0.000000
Debug-2: Z-Axis current location: 0.000000
Debug-3: Z-Axis current location: 0.000000
Debug-4: Z-Axis current location: 0.000000
Debug-5: checking if we can delete Z specific homing code.
Debug-8: Z-Axis current location: 0.000000
Debug-9: Z-Axis current location: 7.400000
Debug-10: Z-Axis current location: 7.400000
>>>G29 n5 T V4
SENDING:G29 n5 T V4
Roxy's Enhanced G29 Auto_Bed_Leveling Code V1.01:
Bed x: 15.00 y: 10.00 z: 7.48
Bed x: 56.00 y: 10.00 z: 7.51
Bed x: 97.00 y: 10.00 z: 7.51
Bed x: 138.00 y: 10.00 z: 7.49
Bed x: 179.00 y: 10.00 z: 7.45
Bed x: 15.00 y: 55.00 z: 7.38
Bed x: 56.00 y: 55.00 z: 7.42
Bed x: 97.00 y: 55.00 z: 7.44
Bed x: 138.00 y: 55.00 z: 7.46
Bed x: 179.00 y: 55.00 z: 7.45
Bed x: 15.00 y: 100.00 z: 7.35
Bed x: 56.00 y: 100.00 z: 7.39
Bed x: 97.00 y: 100.00 z: 7.42
Bed x: 138.00 y: 100.00 z: 7.44
Bed x: 179.00 y: 100.00 z: 7.44
Bed x: 15.00 y: 145.00 z: 7.35
Bed x: 56.00 y: 145.00 z: 7.38
Bed x: 97.00 y: 145.00 z: 7.40
Bed x: 138.00 y: 145.00 z: 7.42
Bed x: 179.00 y: 145.00 z: 7.40
Bed x: 15.00 y: 190.00 z: 7.43
Bed x: 56.00 y: 190.00 z: 7.45
Bed x: 97.00 y: 190.00 z: 7.44
Bed x: 138.00 y: 190.00 z: 7.40
Bed x: 179.00 y: 190.00 z: 7.30
Eqn coefficients: a: 0.00 b: -0.00 d: 7.46
Mean of sampled points: 7.423578


Bed Height Topography:
+0.00884 +0.02212 +0.01627 --0.02280 --0.11889
--0.07163 --0.04233 --0.02084 --0.00444 --0.02553
--0.07670 --0.03139 --0.00405 +0.01744 +0.01900
--0.04506 --0.00834 +0.01431 +0.03228 +0.02447
+0.05455 +0.08853 +0.08345 +0.06275 +0.02798


planeNormal x: -0.00 y: 0.00 z: 1.00


Bed Level Correction Matrix:
1.000000 0.000000 0.000083
0.000000 1.000000 -0.000447
-0.000083 0.000447 1.000000
echo:endstops hit: Z:7.31

[Roxy]

Good news! I think you are ready to go back to the saved version of Marlin_Main.cpp but you still have a couple lines of debug code at the start of the G28 command that need to be pulled. My guess is your Z_OFFSET of -7.4 is going to have to be tweaked one direction or the other. I usually take a look at how the first layer of a print is going down to decide which way to adjust it.

[brainscan]

Thank you so much, its 1:00am so its a bit late to start a print but I have the day off college tomorrow so I can test it and tweak it. I just made a small adjustment to reduce the travel of the probe so the offset is -7.6 now and at Z0 gives me just enough room to squeeze a sheet of paper through the gap. Hopefully it should be pretty close from the start (probably much more so than manual levelling). Next thing is to improve my probe, way too much play in it. I was pretty happy with the 0.000700 standard deviation I got earlier but think it can still be better with ball/lead screws and proper probe mount. I'll try not to ask you for anything for a while, I really need to learn how to help myself when it comes to code but I just don't know where to start really.