As it turns out... BrainScan went through a similar hair pulling debug session starting about here:
http://3dprintboard.com/showthread.p...ll=1#post19007
I don't know if this is what is causing your problems, but the big problem is the M503 command fails to report everything that is happening after reset on the Arduino.
Do you have the EEPROM turn on? Because if you do, you could have a bad value for the Z-PROBE-OFFSET stored in the EEPROM and you won't know it. It won't matter what you change the Configuration.h setting to, it will use the value out of EEPROM. Probably, the simplest suggestion is turn off the EEPROM chit chat until you get everything else running. But if you need it, you can do a M502 and a M500 to restore default (Configuration.h) settings and store them. The problem with doing this, is now the Configuration.h settings will be ignored unless you do the M502 & M500 pair. With that said... That might be what you are fighting right now. If somehow a bad number for the Z-PROBE-OFFSET got stored, it doesn't matter what you set things to in the Configuration.h file. You will need to do a M502 & M500 to load the compiled default values and store them.
At post #58 in the thread we finally get confirmation that was what was keeping him from setting his Z-PROBE-OFFSET in Configuration.h (See the previous post for the analysis)
http://3dprintboard.com/showthread.p...ll=1#post19319
And that is why there is an EEPROM Invalidate command provided in Post # 75:
http://3dprintboard.com/showthread.p...ll=1#post20943
New to 3d printing looking for...
05-20-2024, 12:56 AM in Tips, Tricks and Tech Help