Marlin v1 issues MANUAL_Z_HOME_POS

I'm installing Marlin v1 for the first time (I've been running Repetier for a couple of years). I have two main issues,
I believe I have set the ( #define MANUAL_Z_HOME_POS 286 ) correctly but when I start to print it always prints about an 35mm
above the bed. Then when I run the auto bed leveling everything works except the probe does not touch the bed no matter what I do,
it seems to be about a 10MM high ??

Need more info. Sounds like the pulley teeth or fishing line diameter is not set properly. Also what are your microstep settings set to? Do you use 1/16th? 1/8th? etc etc? Yours seems to be set for GT2 20T pulleys.

---

My Personal Blog. Build blog.
[engineerd3d.ddns.net]

Modicum V1 sold on e-bay user jaguarking11

Check you don't have an M206 Z offset in EEPROM. M501 will list what it is currently set at. I believe you also need a decimal value after the integer for Z height as well, even if it is zero.

Edited 1 time(s). Last edit at 08/11/2014 05:27PM by AndyCart.

@ jaguarking11
I'm running MLX 6mm belt width 18 teeth. I'm running 1/32nd steps. I'm not very familiar with Marlin and I see the configuration.h page has string setting, how do I change this to pulley.

@AndyCart
here is the M501 info..thanks


18:22:26.352 : N222 M501 *5
18:22:26.359 : echotored settings retrieved
18:22:26.359 : echoteps per unit:
18:22:26.363 : echo: M92 X174.00 Y174.00 Z174.00 E1500.00
18:22:26.363 : echo:Maximum feedrates (mm/s):
18:22:26.367 : echo: M203 X80.00 Y80.00 Z80.00 E200.00
18:22:26.367 : echo:Maximum Acceleration (mm/s2):
18:22:26.371 : echo: M201 X3000 Y3000 Z3000 E3000
18:22:26.371 : echo:Acceleration: S=acceleration, T=retract acceleration
18:22:26.375 : echo: M204 S1000.00 T1000.00
18:22:26.382 : echo:Advanced variables: S=Min feedrate (mm/s), T=Min travel feedrate (mm/s), B=minimum segment time (ms), X=maximum XY jerk (mm/s), Z=maximum Z jerk (mm/s), E=maximum E jerk (mm/s)
18:22:26.383 : echo: M205 S0.00 T0.00 B20000 X10.00 Z10.00 E20.00
18:22:26.383 : echo:Home offset (mm):
18:22:26.388 : echo: M206 X0.00 Y0.00 Z0.00
18:22:26.388 : echo:Endstop adjustment (mm):
18:22:26.388 : echo: M666 X0.00 Y0.00 Z0.00
18:22:26.388 : echoelta Geometry adjustment:
18:22:26.395 : echo: M666 A0.00 B0.00 C0.00 E0.00 F0.00 G0.00 R108.40 D217.50 H258.00 P0.00
18:22:26.395 : echoID settings:
18:22:26.396 : echo: M301 P15.34 I1.57 D37.45

You have it set to 20t pulley there. Change the firmware to reflect that. There is a formula in the wiki. I will check in the am. If needed I'll run the numbers for you.

---

My Personal Blog. Build blog.
[engineerd3d.ddns.net]

Modicum V1 sold on e-bay user jaguarking11

@ jaguarking11
I believe the numbers are correct because when I request a movement in Z, I measure it with my calipers and it is correct.

I did use this formula ( [calculator.josefprusa.cz] ) and it verifies I have the correct steps.

Quote
Dannydefe
@ jaguarking11
I believe the numbers are correct because when I request a movement in Z, I measure it with my calipers and it is correct.

I did use this formula ( [calculator.josefprusa.cz] ) and it verifies I have the correct steps.

Well I see this line.

#define DEFAULT_AXIS_STEPS_PER_UNIT {80, 80, 80, 439.5}

Change it to

#define DEFAULT_AXIS_STEPS_PER_UNIT {88.889, 88.889, 88.889, 439.5}

This is assuming your running a GT2 belt with 18 Teeth. This would account for about a 8% difference in height. This takes into assumption two things here. One: your using GT2 belts, and your motors are 1.8 degree motors with full on 1/16 microstepping.

The formula is simple [www.reprap.org]

steps_per_mm = (motor_steps_per_rev * driver_microstep) / (belt_pitch * pulley_number_of_teeth)

---

My Personal Blog. Build blog.
[engineerd3d.ddns.net]

Modicum V1 sold on e-bay user jaguarking11

I'm running MLX 6mm belt width 18 teeth. I'm running 1/32nd steps.

my mistake, although I did change it in the EEPROM I never changed it in the firmware .This is what it looks like now (#define DEFAULT_AXIS_STEPS_PER_UNIT {174.1, 174.1, 174.1, 439.5})
and I believe it's set correctly because the Z movement is the correct amount.

I solved the problem by typing in M 666 L this is the result you get

07:17:19.871 : N22 M666 L *89
07:17:19.876 : Current Delta geometry values:
07:17:19.876 : X (Endstop Adj): 0.00
07:17:19.876 : Y (Endstop Adj): 0.00
07:17:19.881 : Z (Endstop Adj): 0.00
07:17:19.881 : P (Z-Probe Offset): X0.00 Y10.00 Z-5.60
07:17:19.881 : A (Tower A Position Correction): 0.00
07:17:19.884 : B (Tower B Position Correction): 0.00
07:17:19.885 : C (Tower C Position Correction): 0.00
07:17:19.885 : I (Tower A Radius Correction): 0.00
07:17:19.889 : J (Tower B Radius Correction): 0.00
07:17:19.889 : K (Tower C Radius Correction): 0.00
07:17:19.892 : R (Delta Radius): 105.00
07:17:19.893 : D (Diagonal Rod Length): 217.50
07:17:19.893 : H (Z-Height): 285.50


and it's easy to change the Z heights by typing in M 666 H and then the value you want for the high ( M666 H 285.5 ). to save do M500 Everything works now.

Eprom is all fine and good, but its no replacement to modifying the firmware properly for your build. I turned eprom off on my printer, as well as auto leveling is off. Its the harder way to tune a printer, but also the most reliable. I am now sadisfied with the settings and will be turning on those two features to increase accuracy and repeatability. However I do not like the microswitch/servo solution. I want to use either force sensors or embed the microswitch to head. Its possible I may use a proximity sensor as well. They are quite cheap on e-bay costing around 7bux a pop.

---

My Personal Blog. Build blog.
[engineerd3d.ddns.net]

Modicum V1 sold on e-bay user jaguarking11