Bed auto leveling works, but x/y axis are off with correct offset

[Roxy]

I really appreciate all of the help.
I noticed however in that version of Marlin, that there was no Marlin.pde file that I normally use to upload the firmware with the Arduino software. I ended up just copying my .pde file over to compile it.(I hope that was ok because I'm not really sure how else to remedy that issue)

The .ini and .pde files switched between Arduino v.022 and Arduino v1.05 If everything compiles clean, you are good to go. But I suggest you download and install the v1.05 because some compiler bugs have been fixed in that version and right now you don't need extra variables when things don't work.

I'm going to try your version Roxy, but I was wondering if I could get some more information about how I should modify the pin.h because I have zero experience with messing with that. I'm going to go ahead and download your 9-15-2014-work copy.rar and see if I can't get that going. I was really hoping that Dacb's version was going to fix my issues because I was assuming it was a problem in my configuration.h. I feel more confused to why this I am experiencing this issue now more than ever lol.

Just take the stock, generic Pins.h from just about any Marlin release and replace that file in my version. I have a few extra things defined in my Pins.h and some stuff moved around to be on different GPIO pins. You don't want my changes. They are for my hardware setup. That is the only reason I pointed out that Pins.h was different so nobody would assume the generic #define's were there.

I almost forgot, here is the version of Marlin that I was using with my configurations. I did notice a few differences with mine and Dacb's in the configuration.h file in regards to endstop pullups and a few other things, but they must not be the cause of my issue since Dacb's version and configuration is still creating the same offset issue for me.

This is valuable information!

Roxy, I've been working on my configuration.h file for your 9-15-2014-Work Copy.rar, but when I got to a certain area it was so different than any other configuration.h file that I have ever messed with, that it just completely when over my head.

the part that has me confused and/or confused is about I'll paste below
-----------------------------------------------------------------
//===========================CALIBRATION PARAMETERS==========================
//================================================== =========================
...
#define DEFAULT_AXIS_STEPS_PER_UNIT {((XY_MTR_STPS/MICROSTEPPING_RATIO)/(BELT_PITCH*GEAR_TEETH)), ((XY_MTR_STPS/MICROSTEPPING_RATIO)/(BELT_PITCH*GEAR_TEETH)), ((Z_MTR_STPS/MICROSTEPPING_RATIO)/Z_ROD_PITCH),((PACKING_DENSITY*EXTRUDER_MTR_STPS*E XTRUDER_GEAR_RATIO*(1/MICROSTEPPING_RATIO))/(PI*BOLT_DIAMETER))}

Don't be scared of that stuff... Just delete it. All of that stuff is so that last line

#define DEFAULT_AXIS_STEPS_PER_UNIT

has the right numbers in it. I have symbolic values that get used in the calculation instead of just having final hard coded values there. Just put what ever your Configuration.h file's #define DEFAULT_AXIS_STEPS_PER_UNIT line is into the file to replace the stuff that is there.

I'm completely a newb when it comes to motor stepping and motor specs/belt pithces and what not. Any idea what I could enter for these values or where I could teach myself in order to better understand how to configure this part?

Well... For now delete that stuff up above and replace it with your hard coded numbers. But if you print out that section, you can walk through the calculations and see how those numbers are generated. Probably, my final numbers are not too far off from what yours are. But the point is with my setup I can change any one component and the correct numbers will get generated. For example, I could change my belt pitch and put the new number in there and in theory, my printer will stay calibrated.