Auto bed level Z offset inconsistent

[DBFIU]

I really need to figure out why this is happening. I have literally replaced everything, my ramps, mega, stiffined up my ABL system 3 times. Redesigned brackets to position everything as close to the nozzle as possible for minimal error. Brought my bed as close to level as possible, although that doesnt make a difference to finding z home.

I just dont know why the z offset that I load up in there, works one time and then its a different z offset another time. And I have to switch back and forth between these two values, they are over 3 mm apart, it cant be servo and brackets... I am worried about it, I have 3 machines with this problem and I am getting 4 more machines and I cant afford to re-upload firmware everytime I need to print.

It has to be software related, just has to be...

Is it a version of marlin that is doing this? What about the EEPROM thingy you were talking about? I have no idea how to verify or what to do to confirm if it is that. I need some more detailed guidance, thank you!

[Roxy]

Hi Roxy,
The probe only goes up and down once. After it finishes the G28 it retracts, and then extends right before G29. This is unnecessary, how do I stop this from happening?

It is that way because the G28 and G29 should be self contained and do everything they each need. But if you want to change it, you can just call the routine to probe the point in the G28 and tell it not to retract the probe.

It has to be software related, just has to be...

Is it a version of marlin that is doing this? What about the EEPROM thingy you were talking about? I have no idea how to verify or what to do to confirm if it is that. I need some more detailed guidance, thank you!

You already said up above that the line:

//#define EEPROM_SETTINGS

is commented out. If that is what you are really building, the EEPROM isn't the source of your problem. But the problems you are having sure sound like the kind of thing you would experience if you had a bad value in the EEPROM that was getting used.

Arduino can be very confusing about what project it is loading and compiling. Are you sure you are building the code in the directory you think you are? It might not hurt to go edit a file there so it has a syntax error and then bring up Arduino and verify that the compiler says you have an error where you changed things.

[DBFIU]

It is that way because the G28 and G29 should be self contained and do everything they each need. But if you want to change it, you can just call the routine to probe the point in the G28 and tell it not to retract the probe.



You already said up above that the line:

//#define EEPROM_SETTINGS

is commented out. If that is what you are really building, the EEPROM isn't the source of your problem. But the problems you are having sure sound like the kind of thing you would experience if you had a bad value in the EEPROM that was getting used.

Arduino can be very confusing about what project it is loading and compiling. Are you sure you are building the code in the directory you think you are? It might not hurt to go edit a file there so it has a syntax error and then bring up Arduino and verify that the compiler says you have an error where you changed things.

I "think" it is loading and compiling the marlin.ino file from the directory I am working in. I don't see it loading any other way? How would I verify if it is compiling other code?

I am pretty sure it is compiling and uploading the code I am telling it. If I change my z offset in marlin.ino, and upload it, I immediately see the new Z offset on my LCD display once it is finished uploading. It all seems to work just fine until I go to print and then the z offset, although numerically the same, is physically off by a few millimeters.

Yes //#define EEPROM_SETTINGS is commented out. So I am not sure where the bad value is coming from, if it is that at all. Could this be something else? Have we looked at all possible ways for this to happen?

[DBFIU]

I uploaded the new firmware Roxy, with my config.h settings. I did the best I could to match up everything on the new firmware with my old values.

All axes are going in the correct direction, it homes fine and temps are fine. The problem is when it goes to start a print, right after it finds G28, instead of going into the G29 routine it just sits above the bed and tries to extrude for no reason. My LCD display shows weird characters for the Z axis, it looks like Z--*.,(

very strange why it will not just start the G29 and start to print? Whats in the new firmware that could be causing this?