Auto Bed Leveling - ZProbe Offset

Hallo

Ich habe ein kleines Problem mit den Einstellungen für das s.g Auto Bed Leveling.
Mein Drucker ist ein Eigenbau CoreXy.

Das Problem ist das wenn ich das " z_probe_offset_from extruder " berechne gehe ich wie folgt vor.

G28
G92 Z10
in 0.1 Schritten den Abstand verringern bis Düse 0.1 mm Abstand hat.

Das Ergebnis ist immer ein Offset von 1.3 ( 10 - 8.3 )
Ich trage also folgendes in der Arduino Software am PC ein und übertrage das Programm.

z_probe_offset_from extruder -1.3

Wenn ich jetzt allerdings ein Druck starte ist die Düse immer mehr als nur 0.1 vom Druckbett entfernt !
Als Start-Gcode habe ich folgendes ergänzt

G28
G29

Ich habe die Berechnung jetzt schon x-mal durchgeführt ich komme immer auf ein Offset von 1.3
Kennt jemand von euch Profis das Problem oder mach eich vieleicht etwas grundlegend falsch ?

Liebe Grüße

Vincent


Ergänzung:

Ich habe folgende Seite gefunden !
[marlinfw.org]

Ich werde mal versuchen das DEBUG_LEVELING_FEATURE zu nutzen.
Mehr Information kann ja nicht schaden.

Was mich wundert ist das hier

Quote
Upload Marlin to the board and get ready for that first test. As always, do M502 followed by M500 to ensure that the configured “default” settings are stored in the EEPROM. Otherwise, older saved settings might be loaded and used.

Das höre ich jetzt das erste mal das ich das auch machen muss wenn ich die Änderung per PC Uploade.
Habe es eben getestet leider keine Verbesserung.

1-mal bearbeitet. Zuletzt am 21.03.17 05:20.

Berechnest Du mit warmen oder kaltem Bett ?

---

Wer freundlich zu mir ist zu dem bin auch ich freundlich. Wer Schreibfehler findet darf sie gerne behalten / Geeetech Prusa I3 ProX extended / Repetierhost / Mattercontroll / Slic3r

Hallo kleiner Drache

Mit warmen Bett ( 60 Grad ).
Die Z Achse scheint kein Problem zu haben da ich ja immer den gleichen Wert bekommen mit G28
Auch die Werte bei G29 unterscheiden sich nicht wirklich.
Kann es sein dass die Software das Bett falsch berechnet ?

Hey...

machst du nach dem Probing ein G28? Das verwirft deine Messergebnisse. Immer VOR dem Probing ein G28 machen, danach nicht mehr!!

Zeig doch mal dein Start-Script!

Gruß
Sven

Ich hab das bei mir so gelöst das ich in der Firmware einen viel zu hohen Z-Offset eingetragen habe (Marlin lässt ein tiefer fahren als Z-Offset nicht zu) und meine "echte" z=0 per Befehl im Startscript hinterlege. Das hat hier bei mir die Bewandtnis das ich je nach gedrucktem Material eine andere Auflage mit unterschiedlichen stärken auf dem Heizbett habe.

mein Startscript:

G28; Homing
G29; AutoLevel
G92 Z0.8; set 0-Point <== wäre die echte Z=0 Höhe
G1 X0 Y0 Z0 F2500; Fahre auf Position und Z=0 damit er nicht raumsaut

Damit muss ich die Firmware nicht immer neu flashen wenn ich am Bett was verändert habe.

---

Wer freundlich zu mir ist zu dem bin auch ich freundlich. Wer Schreibfehler findet darf sie gerne behalten / Geeetech Prusa I3 ProX extended / Repetierhost / Mattercontroll / Slic3r

Hallo

Erstmal Danke für eure Hilfe.
Ich zweifel langsam echt an mir selbst. Ich versteh einfach nicht was ich falsch mache.

Ich habe alles nochmal geprüft , den Sensor neu ausgerichtet und das Bett nochmal besser ausgerichtet

Hier das Ergebnis von G29

19:24:59.499 : Bed x: 10.00 y: 40.00 z: 2.85
19:25:09.419 : Bed x: 130.00 y: 40.00 z: 2.81
19:25:19.339 : Bed x: 130.00 y: 160.00 z: 2.71
19:25:29.229 : Bed x: 10.00 y: 160.00 z: 2.78
19:25:29.244 : Eqn coefficients: a: -0.00 b: -0.00 d: 2.89
19:25:29.244 : planeNormal x: 0.00 y: 0.00 z: 1.00
19:25:29.244 : echo:endstops hit:  X:-19.86 Z:2.78

Ich berechne wieder das Offset indem ich G28 eingebe , die Z-Achse mit G92 Z10 in der Software hochsetze und dann in 0.1 Schritten solange nach unten fahre bis ich 0.1 mm über dem Heizbett bin.
Das Ergebnis ist 2.7 mm Offset.

z_probe_offset_from extruder -2.7

Also trage ich diesen Wert in der Arduino Software ein und übertrage das Programm !

Wenn ich den Druck jetzt starte ist die Düse ca 0.3 mm über dem Bett und nicht 0.1
Kann es sein das das Auto Leveling versucht das Bett falsch auszugleichen ?
In gefühlt 100 Videos wird es genauso beschrieben ! Muss ich noch was anderes in der Software einstellen ?

Hier noch der StartCode

G28 
G29 ;probe bed
G90; set absolute coordinates
G92 E0; reset extruder distance

Was könnte ich noch testen bzw ausprobieren , wie kann ich effektiv nach dem Fehler suchen ?
Kann es sein das die Software verhindert das ich so tief unter dem TriggerPunkt des Sensors fahre ?

2-mal bearbeitet. Zuletzt am 21.03.17 16:29.

Ich hab ja schon geschrieben das Dein Z-Offset der Absolut minimalste wert ist den du fahren kannst aber dein AutoLeveling will auf:

19:25:29.244 : echo:endstops hit: X:-19.86 Z:2.78 also auf -2.78 was ja schon 0.08 tiefer liegt als Dein minimalster Wert und auch FAST deinem 0.1 mm zu hohem Startpunkt entspricht. Bitte berichtigt mich wenn ich da was falsch interpretiert habe.

---

Wer freundlich zu mir ist zu dem bin auch ich freundlich. Wer Schreibfehler findet darf sie gerne behalten / Geeetech Prusa I3 ProX extended / Repetierhost / Mattercontroll / Slic3r

Hallo

Ich denke ich habe verstanden was du meinst !.
Was ich nicht verstehe warum das so ist.

Wenn ich das Offset auf - 3.0 mm hochsetze verändert sich ja auch immer die Werte des G29.

09:05:25.890 : Bed x: 10.00 y: 40.00 z: 3.14
09:05:35.812 : Bed x: 130.00 y: 40.00 z: 3.10
09:05:45.734 : Bed x: 130.00 y: 160.00 z: 3.02
09:05:55.625 : Bed x: 10.00 y: 160.00 z: 3.07
09:05:55.625 : Eqn coefficients: a: -0.00 b: -0.00 d: 3.17
09:05:55.640 : planeNormal x: 0.00 y: 0.00 z: 1.00
09:05:55.640 : echo:endstops hit:  X:-19.86 Z:3.08

Was bedeutet das ganze Auto Bed Leveling macht keinen Sinn da er die Z-Höhe wie du schon gesagt hast nicht anfahren kann da es unterhalb des Offsets liegt.
Es ist also egal welches Offset ich eintrage er kann den gewünschten Abstand von 0.1 mm nicht anfahren !
In allen Videos die ich gesehen habe funktioniert es so wie ich es beschrieben habe.
Liegt es an mir , meinem Druckbett oder wo ist das Problem.

was mich wundert ist das du keine Corektion Matrix bekommst.Bei mir sieht das z.B. so aus :

08:50:29.211 : G29 Auto Bed Leveling
08:50:56.234 : Bilinear Leveling Grid:
08:50:56.234 : 0 1 2
08:50:56.234 : 0 -0.09 -0.06 -0.12
08:50:56.234 : 1 -0.08 -0.02 -0.12
08:50:56.234 : 2 -0.10 -0.08 -0.11
08:50:56.234 : X:116.00 Y:190.00 Z:4.09 E:0.00 Count X: 9316 Y:15259 Z:1600
08:50:56.235 : X:116.00 Y:190.00 Z:0.85 E:0.00 Count X: 9316 Y:15259 Z:303
08:52:34.325 : X:0.00 Y:0.00 Z:0.00 E:0.00 Count X: 0 Y:0 Z:-34

Allerdings verwende ich Marlin und nicht Repetier (Repetier ist mir einfach zu Bugbelastet) aber auch bei Marlin ist das ABL nicht der Hit. Deswegen hab ich lieber wieder auf manuelles Leveling umgestellt (der von mir gepostet Startcode ist der den ich mit ABL genutzt hatte) und nutze den Sensor nurnoch als Z-Endstop.

---

Wer freundlich zu mir ist zu dem bin auch ich freundlich. Wer Schreibfehler findet darf sie gerne behalten / Geeetech Prusa I3 ProX extended / Repetierhost / Mattercontroll / Slic3r

Hallo Drache

Hm ich verwende auch Marlin !
Ich benutze Repetier-Host um den Drucker zu steuern aber auf dem Ramps läuft Marlin

FIRMWARE_NAME:Marlin V1; Sprinter/grbl mashup for gen6 FIRMWARE_URL:[github.com] PROTOCOL_VERSION:1.0

Sollte ich mal die neues Version ausprobieren ? Das mit der Matrix wundert mich auch.

Repetier Host verwende ich auch. Meine Marlin Version ist die Letzte RCBugFixed. Schau doch mal in die Notes ob da was am ABL verbessert wurde (meine mich zu erinnern das da was getan wurde)

---

Wer freundlich zu mir ist zu dem bin auch ich freundlich. Wer Schreibfehler findet darf sie gerne behalten / Geeetech Prusa I3 ProX extended / Repetierhost / Mattercontroll / Slic3r

Wo finde ich die neueste Version ?
[github.com]

Die Stable Version ?

Das ist die falsche Repo

HIER die offizielle. Musst nur noch den Branch umstellen auf "RCBugFix" letztes Update war vor 2 Tagen.

---

Wer freundlich zu mir ist zu dem bin auch ich freundlich. Wer Schreibfehler findet darf sie gerne behalten / Geeetech Prusa I3 ProX extended / Repetierhost / Mattercontroll / Slic3r

Hallo

Also ich habe jetzt Marlin neu aufgespielt.
Leider immer noch das gleiche Problem.

15:45:04.203 : Bed x: 10.00 y: 40.00 z: 1.23
15:45:13.968 : Bed x: 130.00 y: 40.00 z: 1.22
15:45:23.781 : Bed x: 130.00 y: 160.00 z: 1.18
15:45:33.531 : Bed x: 10.00 y: 160.00 z: 1.21
15:45:33.546 : Eqn coefficients: a: -0.00 b: -0.00 d: 1.25
15:45:33.546 : planeNormal x: 0.00 y: 0.00 z: 1.00
15:45:33.562 : echo:endstops hit:  Z:1.21

Die Düse ist 0.4 mm zu hoch über dem Bett.
Als Offset habe ich -1.1 eingetragen.
Nach dem G28 funktioniert der Befehl G1 Z0 F100 perfekt und die Düse ist 0.1 mm über dem Bett.
Ich habe mir unzählige Videos angeschaut alle machen genau das was ich auch gemacht habe.
Ich verstehe zwar das was Drache gesagt hat das die Software es nicht erlaubt unterhalb des Offset zu fahren aber es ergibt trotzdem keinen Sinn.

Hat jemand noch eine Idee an was es liegen könnte kann doch nciht sein das Gefühlt die halbe Welt ABL ohne Probleme installiert bekommt.
Hier mal meine Config

#ifndef CONFIGURATION_H
#define CONFIGURATION_H

#include "boards.h"

// This configuration file contains the basic settings.
// Advanced settings can be found in Configuration_adv.h
// BASIC SETTINGS: select your board type, temperature sensor type, axis scaling, and endstop configuration

//===========================================================================
//============================= DELTA Printer ===============================
//===========================================================================
// For a Delta printer replace the configuration files with the files in the
// example_configurations/delta directory.
//

//===========================================================================
//============================= SCARA Printer ===============================
//===========================================================================
// For a Delta printer replace the configuration files with the files in the
// example_configurations/SCARA directory.
//

// User-specified version info of this build to display in [Pronterface, etc] terminal window during
// startup. Implementation of an idea by Prof Braino to inform user that any changes made to this
// build by the user have been successfully uploaded into firmware.

//#define STRING_VERSION "1.0.2"

#define STRING_VERSION_CONFIG_H __DATE__ " " __TIME__ // build date and time
#define STRING_CONFIG_H_AUTHOR "(none, default config)" // Who made the changes.

// SERIAL_PORT selects which serial port should be used for communication with the host.
// This allows the connection of wireless adapters (for instance) to non-default port pins.
// Serial port 0 is still used by the Arduino bootloader regardless of this setting.
#define SERIAL_PORT 0

// This determines the communication speed of the printer
#define BAUDRATE 115200

// This enables the serial port associated to the Bluetooth interface
//#define BTENABLED              // Enable BT interface on AT90USB devices

// The following define selects which electronics board you have.
// Please choose the name from boards.h that matches your setup
#ifndef MOTHERBOARD
  #define MOTHERBOARD BOARD_RAMPS_13_EFB
#endif

// Define this to set a custom name for your generic Mendel,
// #define CUSTOM_MENDEL_NAME "Sompero"

// Define this to set a unique identifier for this printer, (Used by some programs to differentiate between machines)
// You can use an online service to generate a random UUID. (eg [www.uuidgenerator.net])
// #define MACHINE_UUID "00000000-0000-0000-0000-000000000000"

// This defines the number of extruders
#define EXTRUDERS 1

//// The following define selects which power supply you have. Please choose the one that matches your setup
// 1 = ATX
// 2 = X-Box 360 203Watts (the blue wire connected to PS_ON and the red wire to VCC)

#define POWER_SUPPLY 1

// Define this to have the electronics keep the power supply off on startup. If you don't know what this is leave it.
// #define PS_DEFAULT_OFF

//===========================================================================
//=============================Thermal Settings  ============================
//===========================================================================
//
//--NORMAL IS 4.7kohm PULLUP!-- 1kohm pullup can be used on hotend sensor, using correct resistor and table
//
//// Temperature sensor settings:
// -2 is thermocouple with MAX6675 (only for sensor 0)
// -1 is thermocouple with AD595
// 0 is not used
// 1 is 100k thermistor - best choice for EPCOS 100k (4.7k pullup)
// 2 is 200k thermistor - ATC Semitec 204GT-2 (4.7k pullup)
// 3 is Mendel-parts thermistor (4.7k pullup)
// 4 is 10k thermistor !! do not use it for a hotend. It gives bad resolution at high temp. !!
// 5 is 100K thermistor - ATC Semitec 104GT-2 (Used in ParCan & J-Head) (4.7k pullup)
// 6 is 100k EPCOS - Not as accurate as table 1 (created using a fluke thermocouple) (4.7k pullup)
// 7 is 100k Honeywell thermistor 135-104LAG-J01 (4.7k pullup)
// 71 is 100k Honeywell thermistor 135-104LAF-J01 (4.7k pullup)
// 8 is 100k 0603 SMD Vishay NTCS0603E3104FXT (4.7k pullup)
// 9 is 100k GE Sensing AL03006-58.2K-97-G1 (4.7k pullup)
// 10 is 100k RS thermistor 198-961 (4.7k pullup)
// 11 is 100k beta 3950 1% thermistor (4.7k pullup)
// 12 is 100k 0603 SMD Vishay NTCS0603E3104FXT (4.7k pullup) (calibrated for Makibox hot bed)
// 13 is 100k Hisens 3950  1% up to 300°C for hotend "Simple ONE " & "Hotend "All In ONE" 
// 20 is the PT100 circuit found in the Ultimainboard V2.x
// 60 is 100k Maker's Tool Works Kapton Bed Thermistor beta=3950
//
//    1k ohm pullup tables - This is not normal, you would have to have changed out your 4.7k for 1k
//                          (but gives greater accuracy and more stable PID)
// 51 is 100k thermistor - EPCOS (1k pullup)
// 52 is 200k thermistor - ATC Semitec 204GT-2 (1k pullup)
// 55 is 100k thermistor - ATC Semitec 104GT-2 (Used in ParCan & J-Head) (1k pullup)
//
// 1047 is Pt1000 with 4k7 pullup
// 1010 is Pt1000 with 1k pullup (non standard)
// 147 is Pt100 with 4k7 pullup
// 110 is Pt100 with 1k pullup (non standard)

#define TEMP_SENSOR_0 13
#define TEMP_SENSOR_1 -1
#define TEMP_SENSOR_2 0
#define TEMP_SENSOR_BED 1

// This makes temp sensor 1 a redundant sensor for sensor 0. If the temperatures difference between these sensors is to high the print will be aborted.
//#define TEMP_SENSOR_1_AS_REDUNDANT
#define MAX_REDUNDANT_TEMP_SENSOR_DIFF 10

// Actual temperature must be close to target for this long before M109 returns success
#define TEMP_RESIDENCY_TIME 10  // (seconds)
#define TEMP_HYSTERESIS 3       // (degC) range of +/- temperatures considered "close" to the target one
#define TEMP_WINDOW     1       // (degC) Window around target to start the residency timer x degC early.

// The minimal temperature defines the temperature below which the heater will not be enabled It is used
// to check that the wiring to the thermistor is not broken.
// Otherwise this would lead to the heater being powered on all the time.
#define HEATER_0_MINTEMP 5
#define HEATER_1_MINTEMP 5
#define HEATER_2_MINTEMP 5
#define BED_MINTEMP 5

// When temperature exceeds max temp, your heater will be switched off.
// This feature exists to protect your hotend from overheating accidentally, but *NOT* from thermistor short/failure!
// You should use MINTEMP for thermistor short/failure protection.
#define HEATER_0_MAXTEMP 275
#define HEATER_1_MAXTEMP 275
#define HEATER_2_MAXTEMP 275
#define BED_MAXTEMP 150

// If your bed has low resistance e.g. .6 ohm and throws the fuse you can duty cycle it to reduce the
// average current. The value should be an integer and the heat bed will be turned on for 1 interval of
// HEATER_BED_DUTY_CYCLE_DIVIDER intervals.
//#define HEATER_BED_DUTY_CYCLE_DIVIDER 4

// If you want the M105 heater power reported in watts, define the BED_WATTS, and (shared for all extruders) EXTRUDER_WATTS
//#define EXTRUDER_WATTS (12.0*12.0/6.7) //  P=I^2/R
//#define BED_WATTS (12.0*12.0/1.1)      // P=I^2/R

// PID settings:
// Comment the following line to disable PID and enable bang-bang.
#define PIDTEMP
#define BANG_MAX 255 // limits current to nozzle while in bang-bang mode; 255=full current
#define PID_MAX BANG_MAX // limits current to nozzle while PID is active (see PID_FUNCTIONAL_RANGE below); 255=full current
#ifdef PIDTEMP
  //#define PID_DEBUG // Sends debug data to the serial port.
  //#define PID_OPENLOOP 1 // Puts PID in open loop. M104/M140 sets the output power from 0 to PID_MAX
  //#define SLOW_PWM_HEATERS // PWM with very low frequency (roughly 0.125Hz=8s) and minimum state time of approximately 1s useful for heaters driven by a relay
  #define PID_FUNCTIONAL_RANGE 10 // If the temperature difference between the target temperature and the actual temperature
                                  // is more then PID_FUNCTIONAL_RANGE then the PID will be shut off and the heater will be set to min/max.
  #define PID_INTEGRAL_DRIVE_MAX PID_MAX  //limit for the integral term
  #define K1 0.95 //smoothing factor within the PID
  #define PID_dT ((OVERSAMPLENR * 10.0)/(F_CPU / 64.0 / 256.0)) //sampling period of the temperature routine

// If you are using a pre-configured hotend then you can use one of the value sets by uncommenting it
// Ultimaker
    #define  DEFAULT_Kp 22.2
    #define  DEFAULT_Ki 1.08
    #define  DEFAULT_Kd 114

// MakerGear
//    #define  DEFAULT_Kp 7.0
//    #define  DEFAULT_Ki 0.1
//    #define  DEFAULT_Kd 12

// Mendel Parts V9 on 12V
//    #define  DEFAULT_Kp 63.0
//    #define  DEFAULT_Ki 2.25
//    #define  DEFAULT_Kd 440
#endif // PIDTEMP

// Bed Temperature Control
// Select PID or bang-bang with PIDTEMPBED. If bang-bang, BED_LIMIT_SWITCHING will enable hysteresis
//
// Uncomment this to enable PID on the bed. It uses the same frequency PWM as the extruder.
// If your PID_dT above is the default, and correct for your hardware/configuration, that means 7.689Hz,
// which is fine for driving a square wave into a resistive load and does not significantly impact you FET heating.
// This also works fine on a Fotek SSR-10DA Solid State Relay into a 250W heater.
// If your configuration is significantly different than this and you don't understand the issues involved, you probably
// shouldn't use bed PID until someone else verifies your hardware works.
// If this is enabled, find your own PID constants below.
//#define PIDTEMPBED
//
//#define BED_LIMIT_SWITCHING

// This sets the max power delivered to the bed, and replaces the HEATER_BED_DUTY_CYCLE_DIVIDER option.
// all forms of bed control obey this (PID, bang-bang, bang-bang with hysteresis)
// setting this to anything other than 255 enables a form of PWM to the bed just like HEATER_BED_DUTY_CYCLE_DIVIDER did,
// so you shouldn't use it unless you are OK with PWM on your bed.  (see the comment on enabling PIDTEMPBED)
#define MAX_BED_POWER 255 // limits duty cycle to bed; 255=full current

#ifdef PIDTEMPBED
//120v 250W silicone heater into 4mm borosilicate (MendelMax 1.5+)
//from FOPDT model - kp=.39 Tp=405 Tdead=66, Tc set to 79.2, aggressive factor of .15 (vs .1, 1, 10)
    #define  DEFAULT_bedKp 10.00
    #define  DEFAULT_bedKi .023
    #define  DEFAULT_bedKd 305.4

//120v 250W silicone heater into 4mm borosilicate (MendelMax 1.5+)
//from pidautotune
//    #define  DEFAULT_bedKp 97.1
//    #define  DEFAULT_bedKi 1.41
//    #define  DEFAULT_bedKd 1675.16

// FIND YOUR OWN: "M303 E-1 C8 S90" to run autotune on the bed at 90 degreesC for 8 cycles.
#endif // PIDTEMPBED



//this prevents dangerous Extruder moves, i.e. if the temperature is under the limit
//can be software-disabled for whatever purposes by
#define PREVENT_DANGEROUS_EXTRUDE
//if PREVENT_DANGEROUS_EXTRUDE is on, you can still disable (uncomment) very long bits of extrusion separately.
#define PREVENT_LENGTHY_EXTRUDE

#define EXTRUDE_MINTEMP 170
#define EXTRUDE_MAXLENGTH (X_MAX_LENGTH+Y_MAX_LENGTH) //prevent extrusion of very large distances.

/*================== Thermal Runaway Protection ==============================
This is a feature to protect your printer from burn up in flames if it has
a thermistor coming off place (this happened to a friend of mine recently and
motivated me writing this feature).

The issue: If a thermistor come off, it will read a lower temperature than actual.
The system will turn the heater on forever, burning up the filament and anything
else around.

After the temperature reaches the target for the first time, this feature will 
start measuring for how long the current temperature stays below the target 
minus _HYSTERESIS (set_temperature - THERMAL_RUNAWAY_PROTECTION_HYSTERESIS).

If it stays longer than _PERIOD, it means the thermistor temperature
cannot catch up with the target, so something *may be* wrong. Then, to be on the
safe side, the system will he halt.

Bear in mind the count down will just start AFTER the first time the 
thermistor temperature is over the target, so you will have no problem if
your extruder heater takes 2 minutes to hit the target on heating.

*/
// If you want to enable this feature for all your extruder heaters,
// uncomment the 2 defines below:

// Parameters for all extruder heaters
//#define THERMAL_RUNAWAY_PROTECTION_PERIOD 40 //in seconds
//#define THERMAL_RUNAWAY_PROTECTION_HYSTERESIS 4 // in degree Celsius

// If you want to enable this feature for your bed heater,
// uncomment the 2 defines below:

// Parameters for the bed heater
//#define THERMAL_RUNAWAY_PROTECTION_BED_PERIOD 20 //in seconds
//#define THERMAL_RUNAWAY_PROTECTION_BED_HYSTERESIS 2 // in degree Celsius
//===========================================================================


//===========================================================================
//=============================Mechanical Settings===========================
//===========================================================================

// Uncomment the following line to enable CoreXY kinematics
#define COREXY

// coarse Endstop Settings
#define ENDSTOPPULLUPS // Comment this out (using // at the start of the line) to disable the endstop pullup resistors

#ifndef ENDSTOPPULLUPS
  // fine endstop settings: Individual pullups. will be ignored if ENDSTOPPULLUPS is defined
  // #define ENDSTOPPULLUP_XMAX
  // #define ENDSTOPPULLUP_YMAX
  // #define ENDSTOPPULLUP_ZMAX
  // #define ENDSTOPPULLUP_XMIN
  // #define ENDSTOPPULLUP_YMIN
  // #define ENDSTOPPULLUP_ZMIN
#endif

#ifdef ENDSTOPPULLUPS
  #define ENDSTOPPULLUP_XMAX
  #define ENDSTOPPULLUP_YMAX
  #define ENDSTOPPULLUP_ZMAX
  #define ENDSTOPPULLUP_XMIN
  #define ENDSTOPPULLUP_YMIN
  #define ENDSTOPPULLUP_ZMIN
#endif

// The pullups are needed if you directly connect a mechanical endswitch between the signal and ground pins.
const bool X_MIN_ENDSTOP_INVERTING = true; // set to true to invert the logic of the endstop.
const bool Y_MIN_ENDSTOP_INVERTING = true; // set to true to invert the logic of the endstop.
const bool Z_MIN_ENDSTOP_INVERTING = true; // set to true to invert the logic of the endstop.
const bool X_MAX_ENDSTOP_INVERTING = true; // set to true to invert the logic of the endstop.
const bool Y_MAX_ENDSTOP_INVERTING = true; // set to true to invert the logic of the endstop.
const bool Z_MAX_ENDSTOP_INVERTING = true; // set to true to invert the logic of the endstop.
//#define DISABLE_MAX_ENDSTOPS
//#define DISABLE_MIN_ENDSTOPS

// Disable max endstops for compatibility with endstop checking routine
#if defined(COREXY) && !defined(DISABLE_MAX_ENDSTOPS)
  #define DISABLE_MAX_ENDSTOPS
#endif

// For Inverting Stepper Enable Pins (Active Low) use 0, Non Inverting (Active High) use 1
#define X_ENABLE_ON 0
#define Y_ENABLE_ON 0
#define Z_ENABLE_ON 0
#define E_ENABLE_ON 0 // For all extruders

// Disables axis when it's not being used.
#define DISABLE_X false
#define DISABLE_Y false
#define DISABLE_Z false
#define DISABLE_E false // For all extruders
#define DISABLE_INACTIVE_EXTRUDER true //disable only inactive extruders and keep active extruder enabled

#define INVERT_X_DIR true    // for Mendel set to false, for Orca set to true
#define INVERT_Y_DIR true    // for Mendel set to true, for Orca set to false
#define INVERT_Z_DIR false    // for Mendel set to false, for Orca set to true
#define INVERT_E0_DIR true   // for direct drive extruder v9 set to true, for geared extruder set to false
#define INVERT_E1_DIR false    // for direct drive extruder v9 set to true, for geared extruder set to false
#define INVERT_E2_DIR false   // for direct drive extruder v9 set to true, for geared extruder set to false

// ENDSTOP SETTINGS:
// Sets direction of endstops when homing; 1=MAX, -1=MIN
#define X_HOME_DIR -1
#define Y_HOME_DIR -1
#define Z_HOME_DIR -1

#define min_software_endstops true // If true, axis won't move to coordinates less than HOME_POS.
#define max_software_endstops true  // If true, axis won't move to coordinates greater than the defined lengths below.

// Travel limits after homing
#define X_MAX_POS 190
#define X_MIN_POS 0
#define Y_MAX_POS 180
#define Y_MIN_POS 0
#define Z_MAX_POS 160
#define Z_MIN_POS 0

#define X_MAX_LENGTH (X_MAX_POS - X_MIN_POS)
#define Y_MAX_LENGTH (Y_MAX_POS - Y_MIN_POS)
#define Z_MAX_LENGTH (Z_MAX_POS - Z_MIN_POS)
//============================= Bed Auto Leveling ===========================

#define ENABLE_AUTO_BED_LEVELING // Delete the comment to enable (remove // at the start of the line)
#define Z_PROBE_REPEATABILITY_TEST  // If not commented out, Z-Probe Repeatability test will be included if Auto Bed Leveling is Enabled.

#ifdef ENABLE_AUTO_BED_LEVELING

// There are 2 different ways to pick the X and Y locations to probe:

//  - "grid" mode
//    Probe every point in a rectangular grid
//    You must specify the rectangle, and the density of sample points
//    This mode is preferred because there are more measurements.
//    It used to be called ACCURATE_BED_LEVELING but "grid" is more descriptive

//  - "3-point" mode
//    Probe 3 arbitrary points on the bed (that aren't colinear)
//    You must specify the X & Y coordinates of all 3 points

  #define AUTO_BED_LEVELING_GRID
  // with AUTO_BED_LEVELING_GRID, the bed is sampled in a
  // AUTO_BED_LEVELING_GRID_POINTSxAUTO_BED_LEVELING_GRID_POINTS grid
  // and least squares solution is calculated
  // Note: this feature occupies 10'206 byte
  #ifdef AUTO_BED_LEVELING_GRID

    // set the rectangle in which to probe
    #define LEFT_PROBE_BED_POSITION 10
    #define RIGHT_PROBE_BED_POSITION 130
    #define BACK_PROBE_BED_POSITION 160
    #define FRONT_PROBE_BED_POSITION 40

     // set the number of grid points per dimension
     // I wouldn't see a reason to go above 3 (=9 probing points on the bed)
    #define AUTO_BED_LEVELING_GRID_POINTS 2


  #else  // not AUTO_BED_LEVELING_GRID
    // with no grid, just probe 3 arbitrary points.  A simple cross-product
    // is used to esimate the plane of the print bed

      #define ABL_PROBE_PT_1_X 15
      #define ABL_PROBE_PT_1_Y 180
      #define ABL_PROBE_PT_2_X 15
      #define ABL_PROBE_PT_2_Y 20
      #define ABL_PROBE_PT_3_X 170
      #define ABL_PROBE_PT_3_Y 20

  #endif // AUTO_BED_LEVELING_GRID


  // these are the offsets to the probe relative to the extruder tip (Hotend - Probe)
  // X and Y offsets must be integers
  #define X_PROBE_OFFSET_FROM_EXTRUDER 0
  #define Y_PROBE_OFFSET_FROM_EXTRUDER 0
  #define Z_PROBE_OFFSET_FROM_EXTRUDER -1.1

  #define Z_RAISE_BEFORE_HOMING 4       // (in mm) Raise Z before homing (G28) for Probe Clearance.
                                        // Be sure you have this distance over your Z_MAX_POS in case

  #define XY_TRAVEL_SPEED 1500         // X and Y axis travel speed between probes, in mm/min

  #define Z_RAISE_BEFORE_PROBING 15    //How much the extruder will be raised before traveling to the first probing point.
  #define Z_RAISE_BETWEEN_PROBINGS 5  //How much the extruder will be raised when traveling from between next probing points

  //#define Z_PROBE_SLED // turn on if you have a z-probe mounted on a sled like those designed by Charles Bell
  //#define SLED_DOCKING_OFFSET 5 // the extra distance the X axis must travel to pickup the sled. 0 should be fine but you can push it further if you'd like.

  //If defined, the Probe servo will be turned on only during movement and then turned off to avoid jerk
  //The value is the delay to turn the servo off after powered on - depends on the servo speed; 300ms is good value, but you can try lower it.
  // You MUST HAVE the SERVO_ENDSTOPS defined to use here a value higher than zero otherwise your code will not compile.

//  #define PROBE_SERVO_DEACTIVATION_DELAY 300


//If you have enabled the Bed Auto Leveling and are using the same Z Probe for Z Homing,
//it is highly recommended you let this Z_SAFE_HOMING enabled!!!

  #define Z_SAFE_HOMING   // This feature is meant to avoid Z homing with probe outside the bed area.
                          // When defined, it will:
                          // - Allow Z homing only after X and Y homing AND stepper drivers still enabled
                          // - If stepper drivers timeout, it will need X and Y homing again before Z homing
                          // - Position the probe in a defined XY point before Z Homing when homing all axis (G28)
                          // - Block Z homing only when the probe is outside bed area.

  #ifdef Z_SAFE_HOMING

    #define Z_SAFE_HOMING_X_POINT (X_MAX_LENGTH/2)    // X point for Z homing when homing all axis (G28)
    #define Z_SAFE_HOMING_Y_POINT (Y_MAX_LENGTH/2)    // Y point for Z homing when homing all axis (G28)

  #endif

  #ifdef AUTO_BED_LEVELING_GRID	// Check if Probe_Offset * Grid Points is greater than Probing Range
    #if X_PROBE_OFFSET_FROM_EXTRUDER < 0
      #if (-(X_PROBE_OFFSET_FROM_EXTRUDER * AUTO_BED_LEVELING_GRID_POINTS) >= (RIGHT_PROBE_BED_POSITION - LEFT_PROBE_BED_POSITION))
	     #error "The X axis probing range is not enough to fit all the points defined in AUTO_BED_LEVELING_GRID_POINTS"
	  #endif
	#else
      #if ((X_PROBE_OFFSET_FROM_EXTRUDER * AUTO_BED_LEVELING_GRID_POINTS) >= (RIGHT_PROBE_BED_POSITION - LEFT_PROBE_BED_POSITION))
	     #error "The X axis probing range is not enough to fit all the points defined in AUTO_BED_LEVELING_GRID_POINTS"
	  #endif
	#endif
    #if Y_PROBE_OFFSET_FROM_EXTRUDER < 0
      #if (-(Y_PROBE_OFFSET_FROM_EXTRUDER * AUTO_BED_LEVELING_GRID_POINTS) >= (BACK_PROBE_BED_POSITION - FRONT_PROBE_BED_POSITION))
	     #error "The Y axis probing range is not enough to fit all the points defined in AUTO_BED_LEVELING_GRID_POINTS"
	  #endif
	#else
      #if ((Y_PROBE_OFFSET_FROM_EXTRUDER * AUTO_BED_LEVELING_GRID_POINTS) >= (BACK_PROBE_BED_POSITION - FRONT_PROBE_BED_POSITION))
	     #error "The Y axis probing range is not enough to fit all the points defined in AUTO_BED_LEVELING_GRID_POINTS"
	  #endif
	#endif

	
  #endif
  
#endif // ENABLE_AUTO_BED_LEVELING


// The position of the homing switches
#define MANUAL_HOME_POSITIONS  // If defined, MANUAL_*_HOME_POS below will be used
//#define BED_CENTER_AT_0_0  // If defined, the center of the bed is at (X=0, Y=0)

//Manual homing switch locations:
// For deltabots this means top and center of the Cartesian print volume.
#define MANUAL_X_HOME_POS 0
#define MANUAL_Y_HOME_POS -40
#define MANUAL_Z_HOME_POS 0
//#define MANUAL_Z_HOME_POS 402 // For delta: Distance between nozzle and print surface after homing.

//// MOVEMENT SETTINGS
#define NUM_AXIS 4 // The axis order in all axis related arrays is X, Y, Z, E
#define HOMING_FEEDRATE {50*60, 50*60, 4*60, 0}  // set the homing speeds (mm/min)

// default settings

#define DEFAULT_AXIS_STEPS_PER_UNIT   {160,160,800,298}  // default steps per unit for Ultimaker
#define DEFAULT_MAX_FEEDRATE          {300, 300, 70, 5}    // (mm/sec)
#define DEFAULT_MAX_ACCELERATION      {1000,1000,100,10000}    // X, Y, Z, E maximum start speed for accelerated moves. E default values are good for Skeinforge 40+, for older versions raise them a lot.

#define DEFAULT_ACCELERATION          1000    // X, Y, Z and E max acceleration in mm/s^2 for printing moves
#define DEFAULT_RETRACT_ACCELERATION  3000   // X, Y, Z and E max acceleration in mm/s^2 for retracts

// Offset of the extruders (uncomment if using more than one and relying on firmware to position when changing).
// The offset has to be X=0, Y=0 for the extruder 0 hotend (default extruder).
// For the other hotends it is their distance from the extruder 0 hotend.
// #define EXTRUDER_OFFSET_X {0.0, 20.00} // (in mm) for each extruder, offset of the hotend on the X axis
// #define EXTRUDER_OFFSET_Y {0.0, 5.00}  // (in mm) for each extruder, offset of the hotend on the Y axis

// The speed change that does not require acceleration (i.e. the software might assume it can be done instantaneously)
#define DEFAULT_XYJERK                20.0    // (mm/sec)
#define DEFAULT_ZJERK                 0.4     // (mm/sec)
#define DEFAULT_EJERK                 5.0    // (mm/sec)

//===========================================================================
//=============================Additional Features===========================
//===========================================================================

// Custom M code points
#define CUSTOM_M_CODES
#ifdef CUSTOM_M_CODES
  #define CUSTOM_M_CODE_SET_Z_PROBE_OFFSET 851
  #define Z_PROBE_OFFSET_RANGE_MIN -15
  #define Z_PROBE_OFFSET_RANGE_MAX 0
#endif


// EEPROM
// The microcontroller can store settings in the EEPROM, e.g. max velocity...
// M500 - stores parameters in EEPROM
// M501 - reads parameters from EEPROM (if you need reset them after you changed them temporarily).
// M502 - reverts to the default "factory settings".  You still need to store them in EEPROM afterwards if you want to.
//define this to enable EEPROM support
#define EEPROM_SETTINGS
//to disable EEPROM Serial responses and decrease program space by ~1700 byte: comment this out:
// please keep turned on if you can.
//#define EEPROM_CHITCHAT

// Preheat Constants
#define PLA_PREHEAT_HOTEND_TEMP 180
#define PLA_PREHEAT_HPB_TEMP 70
#define PLA_PREHEAT_FAN_SPEED 255   // Insert Value between 0 and 255

#define ABS_PREHEAT_HOTEND_TEMP 240
#define ABS_PREHEAT_HPB_TEMP 100
#define ABS_PREHEAT_FAN_SPEED 255   // Insert Value between 0 and 255

//LCD and SD support
//#define ULTRA_LCD  //general LCD support, also 16x2
//#define DOGLCD  // Support for SPI LCD 128x64 (Controller ST7565R graphic Display Family)
//#define SDSUPPORT // Enable SD Card Support in Hardware Console
//#define SDSLOW // Use slower SD transfer mode (not normally needed - uncomment if you're getting volume init error)
//#define SD_CHECK_AND_RETRY // Use CRC checks and retries on the SD communication
//#define ENCODER_PULSES_PER_STEP 1 // Increase if you have a high resolution encoder
//#define ENCODER_STEPS_PER_MENU_ITEM 5 // Set according to ENCODER_PULSES_PER_STEP or your liking
//#define ULTIMAKERCONTROLLER //as available from the Ultimaker online store.
//#define ULTIPANEL  //the UltiPanel as on Thingiverse
//#define LCD_FEEDBACK_FREQUENCY_HZ 1000	// this is the tone frequency the buzzer plays when on UI feedback. ie Screen Click
//#define LCD_FEEDBACK_FREQUENCY_DURATION_MS 100 // the duration the buzzer plays the UI feedback sound. ie Screen Click

// The MaKr3d Makr-Panel with graphic controller and SD support
// [reprap.org]
//#define MAKRPANEL

// The RepRapDiscount Smart Controller (white PC
// [reprap.org]
#define REPRAP_DISCOUNT_SMART_CONTROLLER

// The GADGETS3D G3D LCD/SD Controller (blue PC
// [reprap.org]
//#define G3D_PANEL

// The RepRapDiscount FULL GRAPHIC Smart Controller (quadratic white PC
// [reprap.org]
//
// ==> REMEMBER TO INSTALL U8glib to your ARDUINO library folder: [code.google.com]
//#define REPRAP_DISCOUNT_FULL_GRAPHIC_SMART_CONTROLLER

// The RepRapWorld REPRAPWORLD_KEYPAD v1.1
// [reprapworld.com]
//#define REPRAPWORLD_KEYPAD
//#define REPRAPWORLD_KEYPAD_MOVE_STEP 10.0 // how much should be moved when a key is pressed, eg 10.0 means 10mm per click

// The Elefu RA Board Control Panel
// [www.elefu.com]
// REMEMBER TO INSTALL LiquidCrystal_I2C.h in your ARDUINO library folder: [github.com]
//#define RA_CONTROL_PANEL

//automatic expansion
#if defined (MAKRPANEL)
 #define DOGLCD
 #define SDSUPPORT
 #define ULTIPANEL
 #define NEWPANEL
 #define DEFAULT_LCD_CONTRAST 17
#endif

#if defined (REPRAP_DISCOUNT_FULL_GRAPHIC_SMART_CONTROLLER)
 #define DOGLCD
 #define U8GLIB_ST7920
 #define REPRAP_DISCOUNT_SMART_CONTROLLER
#endif

#if defined(ULTIMAKERCONTROLLER) || defined(REPRAP_DISCOUNT_SMART_CONTROLLER) || defined(G3D_PANEL)
 #define ULTIPANEL
 #define NEWPANEL
#endif

#if defined(REPRAPWORLD_KEYPAD)
  #define NEWPANEL
  #define ULTIPANEL
#endif
#if defined(RA_CONTROL_PANEL)
 #define ULTIPANEL
 #define NEWPANEL
 #define LCD_I2C_TYPE_PCA8574
 #define LCD_I2C_ADDRESS 0x27   // I2C Address of the port expander
#endif

//I2C PANELS

//#define LCD_I2C_SAINSMART_YWROBOT
#ifdef LCD_I2C_SAINSMART_YWROBOT
  // This uses the LiquidCrystal_I2C library ( [bitbucket.org] )
  // Make sure it is placed in the Arduino libraries directory.
  #define LCD_I2C_TYPE_PCF8575
  #define LCD_I2C_ADDRESS 0x27   // I2C Address of the port expander
  #define NEWPANEL
  #define ULTIPANEL
#endif

// PANELOLU2 LCD with status LEDs, separate encoder and click inputs
//#define LCD_I2C_PANELOLU2
#ifdef LCD_I2C_PANELOLU2
  // This uses the LiquidTWI2 library v1.2.3 or later ( [github.com] )
  // Make sure the LiquidTWI2 directory is placed in the Arduino or Sketchbook libraries subdirectory.
  // (v1.2.3 no longer requires you to define PANELOLU in the LiquidTWI2.h library header file)
  // Note: The PANELOLU2 encoder click input can either be directly connected to a pin
  //       (if BTN_ENC defined to != -1) or read through I2C (when BTN_ENC == -1).
  #define LCD_I2C_TYPE_MCP23017
  #define LCD_I2C_ADDRESS 0x20 // I2C Address of the port expander
  #define LCD_USE_I2C_BUZZER //comment out to disable buzzer on LCD
  #define NEWPANEL
  #define ULTIPANEL

  #ifndef ENCODER_PULSES_PER_STEP
	#define ENCODER_PULSES_PER_STEP 4
  #endif

  #ifndef ENCODER_STEPS_PER_MENU_ITEM
	#define ENCODER_STEPS_PER_MENU_ITEM 1
  #endif


  #ifdef LCD_USE_I2C_BUZZER
	#define LCD_FEEDBACK_FREQUENCY_HZ 1000
	#define LCD_FEEDBACK_FREQUENCY_DURATION_MS 100
  #endif

#endif

// Panucatt VIKI LCD with status LEDs, integrated click & L/R/U/P buttons, separate encoder inputs
//#define LCD_I2C_VIKI
#ifdef LCD_I2C_VIKI
  // This uses the LiquidTWI2 library v1.2.3 or later ( [github.com] )
  // Make sure the LiquidTWI2 directory is placed in the Arduino or Sketchbook libraries subdirectory.
  // Note: The pause/stop/resume LCD button pin should be connected to the Arduino
  //       BTN_ENC pin (or set BTN_ENC to -1 if not used)
  #define LCD_I2C_TYPE_MCP23017
  #define LCD_I2C_ADDRESS 0x20 // I2C Address of the port expander
  #define LCD_USE_I2C_BUZZER //comment out to disable buzzer on LCD (requires LiquidTWI2 v1.2.3 or later)
  #define NEWPANEL
  #define ULTIPANEL
#endif

// Shift register panels
// ---------------------
// 2 wire Non-latching LCD SR from:
// [bitbucket.org] 

//#define SAV_3DLCD
#ifdef SAV_3DLCD
   #define SR_LCD_2W_NL    // Non latching 2 wire shiftregister
   #define NEWPANEL
   #define ULTIPANEL
#endif


#ifdef ULTIPANEL
//  #define NEWPANEL  //enable this if you have a click-encoder panel
  #define SDSUPPORT
  #define ULTRA_LCD
  #ifdef DOGLCD // Change number of lines to match the DOG graphic display
    #define LCD_WIDTH 20
    #define LCD_HEIGHT 5
  #else
    #define LCD_WIDTH 20
    #define LCD_HEIGHT 4
  #endif
#else //no panel but just LCD
  #ifdef ULTRA_LCD
  #ifdef DOGLCD // Change number of lines to match the 128x64 graphics display
    #define LCD_WIDTH 20
    #define LCD_HEIGHT 5
  #else
    #define LCD_WIDTH 16
    #define LCD_HEIGHT 2
  #endif
  #endif
#endif

// default LCD contrast for dogm-like LCD displays
#ifdef DOGLCD
# ifndef DEFAULT_LCD_CONTRAST
#  define DEFAULT_LCD_CONTRAST 32
# endif
#endif

// Increase the FAN pwm frequency. Removes the PWM noise but increases heating in the FET/Arduino
//#define FAST_PWM_FAN

// Temperature status LEDs that display the hotend and bet temperature.
// If all hotends and bed temperature and temperature setpoint are < 54C then the BLUE led is on.
// Otherwise the RED led is on. There is 1C hysteresis.
//#define TEMP_STAT_LEDS

// Use software PWM to drive the fan, as for the heaters. This uses a very low frequency
// which is not ass annoying as with the hardware PWM. On the other hand, if this frequency
// is too low, you should also increment SOFT_PWM_SCALE.
//#define FAN_SOFT_PWM

// Incrementing this by 1 will double the software PWM frequency,
// affecting heaters, and the fan if FAN_SOFT_PWM is enabled.
// However, control resolution will be halved for each increment;
// at zero value, there are 128 effective control positions.
#define SOFT_PWM_SCALE 0

// M240  Triggers a camera by emulating a Canon RC-1 Remote
// Data from: [www.doc-diy.net]
// #define PHOTOGRAPH_PIN     23

// SF send wrong arc g-codes when using Arc Point as fillet procedure
//#define SF_ARC_FIX

// Support for the BariCUDA Paste Extruder.
//#define BARICUDA

//define BlinkM/CyzRgb Support
//#define BLINKM

/*********************************************************************\
* R/C SERVO support
* Sponsored by TrinityLabs, Reworked by codexmas
**********************************************************************/

// Number of servos
//
// If you select a configuration below, this will receive a default value and does not need to be set manually
// set it manually if you have more servos than extruders and wish to manually control some
// leaving it undefined or defining as 0 will disable the servo subsystem
// If unsure, leave commented / disabled
//
//#define NUM_SERVOS 3 // Servo index starts with 0 for M280 command

// Servo Endstops
//
// This allows for servo actuated endstops, primary usage is for the Z Axis to eliminate calibration or bed height changes.
// Use M206 command to correct for switch height offset to actual nozzle height. Store that setting with M500.
//
//#define SERVO_ENDSTOPS {-1, -1, 0} // Servo index for X, Y, Z. Disable with -1
//#define SERVO_ENDSTOP_ANGLES {0,0, 0,0, 70,0} // X,Y,Z Axis Extend and Retract angles

/**********************************************************************\
 * Support for a filament diameter sensor
 * Also allows adjustment of diameter at print time (vs  at slicing)
 * Single extruder only at this point (extruder 0)
 * 
 * Motherboards
 * 34 - RAMPS1.4 - uses Analog input 5 on the AUX2 connector 
 * 81 - Printrboard - Uses Analog input 2 on the Exp1 connector (version B,C,D,E)
 * 301 - Rambo  - uses Analog input 3
 * Note may require analog pins to be defined for different motherboards
 **********************************************************************/
// Uncomment below to enable
//#define FILAMENT_SENSOR

#define FILAMENT_SENSOR_EXTRUDER_NUM	0  //The number of the extruder that has the filament sensor (0,1,2)
#define MEASUREMENT_DELAY_CM			14  //measurement delay in cm.  This is the distance from filament sensor to middle of barrel

#define DEFAULT_NOMINAL_FILAMENT_DIA  3.0  //Enter the diameter (in mm) of the filament generally used (3.0 mm or 1.75 mm) - this is then used in the slicer software.  Used for sensor reading validation
#define MEASURED_UPPER_LIMIT          3.30  //upper limit factor used for sensor reading validation in mm
#define MEASURED_LOWER_LIMIT          1.90  //lower limit factor for sensor reading validation in mm
#define MAX_MEASUREMENT_DELAY			20  //delay buffer size in bytes (1 byte = 1cm)- limits maximum measurement delay allowable (must be larger than MEASUREMENT_DELAY_CM  and lower number saves RAM)

//defines used in the code
#define DEFAULT_MEASURED_FILAMENT_DIA  DEFAULT_NOMINAL_FILAMENT_DIA  //set measured to nominal initially 

//When using an LCD, uncomment the line below to display the Filament sensor data on the last line instead of status.  Status will appear for 5 sec.
//#define FILAMENT_LCD_DISPLAY






#include "Configuration_adv.h"
#include "thermistortables.h"

#endif //__CONFIGURATION_H

das ist aber immer noch deine alte config.h oder? Hast du nicht auf RCBugFix umgestellt ? Irgedwie fehlen hier Optionen für das ABL.

---

Wer freundlich zu mir ist zu dem bin auch ich freundlich. Wer Schreibfehler findet darf sie gerne behalten / Geeetech Prusa I3 ProX extended / Repetierhost / Mattercontroll / Slic3r

Hallo

Das ist die Version Marlin-1.0.2-1.
Das mit den BugFix Version habe ich nicht so ganz verstanden.
Im engl. Forum steht das man rc_final_z_correction ausprobieren soll kann das aber nirgendwo finden.

Soll ich mal diese Version ausprobieren Marlin 1.1.0-RCBugFix

[github.com]

Denke mal das wir ganz normal wie die Stable Version installiert oder ?

jup das ist die letzte 1.1.0 RC8 BugFixed musst halt aufpassen da hat sich einiges getan in der Config.h also NICHT einfach deine alte einfügen sondern die wichtigen werte in die neue übernehmen.

---

Wer freundlich zu mir ist zu dem bin auch ich freundlich. Wer Schreibfehler findet darf sie gerne behalten / Geeetech Prusa I3 ProX extended / Repetierhost / Mattercontroll / Slic3r

So habe alles installiert !

Ich habe zwar den selben Fehler allerdings bekomme ich jetzt genau die 0.4 angezeigt

17:51:46.343 : Bed Level Correction Matrix:
17:51:46.359 : +1.000000 +0.000000 +0.000125
17:51:46.359 : +0.000000 +1.000000 -0.000531
17:51:46.359 : -0.000125 +0.000531 +1.000000
17:51:46.359 : X:155.00 Y:59.99 Z:11.09 E:-24.74 Count A:34400 B:15200 Z:8880
17:51:46.375 : X:155.00 Y:59.99 Z:11.09 E:0.00 Count A:34400 B:15200 Z:8898
17:51:46.390 : X:155.00 Y:59.99 Z:11.09 E:0.00 Count A:34400 B:15200 Z:8898
17:51:46.390 : Drucke Layer 1 von 199
17:51:46.390 : X:155.00 Y:59.99 Z:0.40 E:0.00 Count A:34400 B:15200 Z:8894

Ich verstehe einfach nicht warum er das Bett so versucht zu kompensieren indem er Z auf 0.4 setzt ?


Hier G28 und G29 mit DebugModus

18:06:44.578 : *** Z HOMED WITH PROBE (Z_MIN_PROBE_USES_Z_MIN_ENDSTOP_PIN) ***
18:06:44.578 : > zprobe_zoffset = -1.10
18:06:44.578 : > home_offset[Z] = 0.00
18:06:44.578 : current_position=(100.00, 100.00, 1.10) :
18:06:44.578 : <<< set_axis_is_at_home(Z)
18:06:44.593 : current_position=(100.00, 100.00, 1.10) : sync_plan_position
18:06:44.593 : current_position=(100.00, 100.00, 1.10) : > AFTER set_axis_is_at_home
18:06:44.609 : current_position=(100.00, 100.00, 1.10) : set_probe_deployed
18:06:44.609 : deploy: 0
18:06:44.609 : do_probe_raise(10.00)
18:06:44.609 : >>> do_blocking_move_to(100.00, 100.00, 11.10)
18:06:44.984 : echo:busy: processing
18:06:46.984 : echo:busy: processing
18:06:47.156 : <<< do_blocking_move_to
18:06:47.156 : >>> do_blocking_move_to(100.00, 100.00, 11.10)
18:06:47.156 : <<< do_blocking_move_to
18:06:47.156 : <<< homeaxis(Z)
18:06:47.156 : <<< Z_SAFE_HOMING
18:06:47.171 : current_position=(100.00, 100.00, 11.10) : > (home_all_axis || homeZ) > final
18:06:47.171 : current_position=(100.00, 100.00, 11.10) : sync_plan_position
18:06:47.171 : current_position=(100.00, 100.00, 11.10) : clean_up_after_endstop_or_probe_move
18:06:47.187 : X:100.00 Y:100.00 Z:11.10 E:0.00 Count A:32000 B:0 Z:8880
18:06:47.187 : <<< gcode_G28
18:07:07.125 : current_position=(100.00, 100.00, 11.10) : >>> gcode_G29
18:07:07.125 : Machine Type: Core
18:07:07.125 : Probe: FIX_MOUNTED_PROBE
18:07:07.140 : Probe Offset X:0 Y:0 Z:-1.10 (Aligned With & Below Nozzle)
18:07:07.140 : Auto Bed Leveling: 3POINT
18:07:07.140 : current_position=(100.00, 100.00, 11.10) : sync_plan_position
18:07:07.156 : current_position=(100.00, 100.00, 11.10) : setup_for_endstop_or_probe_move
18:07:07.156 : current_position=(100.00, 100.00, 11.10) : set_probe_deployed
18:07:07.156 : deploy: 1
18:07:07.156 : do_probe_raise(10.00)
18:07:07.156 : >>> do_blocking_move_to(100.00, 100.00, 11.10)
18:07:07.156 : <<< do_blocking_move_to
18:07:07.171 : >>> do_blocking_move_to(100.00, 100.00, 11.10)
18:07:07.171 : <<< do_blocking_move_to
18:07:07.171 : > 3-point Leveling
18:07:07.171 : >>> probe_pt(15.00, 180.00, no stow)
18:07:07.171 : current_position=(100.00, 100.00, 11.10) :
18:07:07.187 : do_probe_raise(5.00)
18:07:07.187 : >>> do_blocking_move_to(15.00, 180.00, 11.10)
18:07:09.125 : echo:busy: processing
18:07:11.125 : echo:busy: processing
18:07:11.875 : <<< do_blocking_move_to
18:07:11.890 : current_position=(15.00, 180.00, 11.10) : set_probe_deployed
18:07:11.890 : deploy: 1
18:07:11.890 : current_position=(15.00, 180.00, 11.10) : >>> run_z_probe
18:07:11.890 : >>> do_blocking_move_to(15.00, 180.00, 6.10)
18:07:13.125 : echo:busy: processing
18:07:13.171 : <<< do_blocking_move_to
18:07:13.187 : current_position=(15.00, 180.00, 6.10) : >>> do_probe_move
18:07:13.187 : >>> do_blocking_move_to(15.00, 180.00, -210.00)
18:07:15.125 : echo:busy: processing
18:07:15.750 : <<< do_blocking_move_to
18:07:15.750 : current_position=(15.00, 180.00, 1.03) : sync_plan_position
18:07:15.750 : current_position=(15.00, 180.00, 1.03) : <<< do_probe_move
18:07:15.750 : current_position=(15.00, 180.00, 1.03) : <<< run_z_probe
18:07:15.750 : do_probe_raise(5.00)
18:07:15.750 : >>> do_blocking_move_to(15.00, 180.00, 6.10)
18:07:17.046 : <<< do_blocking_move_to
18:07:17.062 : <<< probe_pt
18:07:17.062 : >>> probe_pt(15.00, 60.00, no stow)
18:07:17.062 : current_position=(15.00, 180.00, 6.10) :
18:07:17.062 : do_probe_raise(5.00)
18:07:17.062 : >>> do_blocking_move_to(15.00, 60.00, 6.10)
18:07:17.125 : echo:busy: processing
18:07:19.140 : echo:busy: processing
18:07:21.140 : echo:busy: processing
18:07:21.890 : <<< do_blocking_move_to
18:07:21.906 : current_position=(15.00, 60.00, 6.10) : set_probe_deployed
18:07:21.906 : deploy: 1
18:07:21.906 : current_position=(15.00, 60.00, 6.10) : >>> run_z_probe
18:07:21.906 : current_position=(15.00, 60.00, 6.10) : >>> do_probe_move
18:07:21.906 : >>> do_blocking_move_to(15.00, 60.00, -210.00)
18:07:23.140 : echo:busy: processing
18:07:24.437 : <<< do_blocking_move_to
18:07:24.437 : current_position=(15.00, 60.00, 1.08) : sync_plan_position
18:07:24.453 : current_position=(15.00, 60.00, 1.08) : <<< do_probe_move
18:07:24.453 : current_position=(15.00, 60.00, 1.08) : <<< run_z_probe
18:07:24.453 : do_probe_raise(5.00)
18:07:24.453 : >>> do_blocking_move_to(15.00, 60.00, 6.10)
18:07:25.140 : echo:busy: processing
18:07:25.750 : <<< do_blocking_move_to
18:07:25.750 : <<< probe_pt
18:07:25.750 : >>> probe_pt(155.00, 60.00, no stow)
18:07:25.750 : current_position=(15.00, 60.00, 6.10) :
18:07:25.750 : do_probe_raise(5.00)
18:07:25.765 : >>> do_blocking_move_to(155.00, 60.00, 6.10)
18:07:27.140 : echo:busy: processing
18:07:29.140 : echo:busy: processing
18:07:31.140 : echo:busy: processing
18:07:31.390 : <<< do_blocking_move_to
18:07:31.390 : current_position=(155.00, 60.00, 6.10) : set_probe_deployed
18:07:31.390 : deploy: 1
18:07:31.390 : current_position=(155.00, 60.00, 6.10) : >>> run_z_probe
18:07:31.406 : current_position=(155.00, 60.00, 6.10) : >>> do_probe_move
18:07:31.406 : >>> do_blocking_move_to(155.00, 60.00, -210.00)
18:07:33.140 : echo:busy: processing
18:07:33.906 : <<< do_blocking_move_to
18:07:33.906 : current_position=(155.00, 60.00, 1.13) : sync_plan_position
18:07:33.906 : current_position=(155.00, 60.00, 1.13) : <<< do_probe_move
18:07:33.921 : current_position=(155.00, 60.00, 1.13) : <<< run_z_probe
18:07:33.921 : do_probe_raise(5.00)
18:07:33.921 : >>> do_blocking_move_to(155.00, 60.00, 6.10)
18:07:35.140 : echo:busy: processing
18:07:35.203 : <<< do_blocking_move_to
18:07:35.203 : <<< probe_pt
18:07:35.203 : current_position=(155.00, 60.00, 6.10) : set_probe_deployed
18:07:35.203 : deploy: 0
18:07:35.203 : do_probe_raise(10.00)
18:07:35.218 : >>> do_blocking_move_to(155.00, 60.00, 11.10)
18:07:36.500 : <<< do_blocking_move_to
18:07:36.500 : >>> do_blocking_move_to(155.00, 60.00, 11.10)
18:07:36.500 : <<< do_blocking_move_to
18:07:36.515 : current_position=(155.00, 60.00, 11.10) : clean_up_after_endstop_or_probe_move
18:07:36.515 : current_position=(155.00, 60.00, 11.10) : > probing complete
18:07:36.515 : Bed Level Correction Matrix:
18:07:36.515 : +1.000000 +0.000000 +0.000366
18:07:36.531 : +0.000000 +1.000000 -0.000406
18:07:36.531 : -0.000366 +0.000406 +1.000000
18:07:36.531 : current_position=(155.00, 60.00, 11.10) : G29 uncorrected XYZ
18:07:36.531 : Z from Probe:11.07  Matrix:11.06  Discrepancy:0.01
18:07:36.546 : current_position=(155.00, 60.00, 11.07) : G29 corrected XYZ
18:07:36.546 : <<< gcode_G29
18:07:36.546 : X:155.00 Y:60.00 Z:11.07 E:0.00 Count A:34400 B:15200 Z:8880
18:07:36.546 : current_position=(155.00, 60.00, 11.07) : sync_plan_position

1-mal bearbeitet. Zuletzt am 22.03.17 13:07.

wenn ich das hier richtig interpretiere funktioniert dein ABL korrekt:

18:07:36.531 : current_position=(X:155.00, Y.60.00, Z:11.10) : G29 uncorrected XYZ
18:07:36.531 : Z from Probe:11.07 Matrix:11.06 Discrepancy:0.01
18:07:36.546 : current_position=(X:155.00, Y:60.00, Z:11.07) : G29 corrected XYZ

(die X,Y,Z sind von mir)

heisst er hat durch das "do_probe_raise(10.00)" plus 10mm gefahren und dein Offset von -1,1 auf -1,07 korrigiert also stimmt dein Abstand nicht. Änder doch einfach den Offset wert um das was er zu hoch ist, also wenn er jetzt 0,4 hat aber nur 0,2 haben soll z.B. Dein Offset von -1,1 auf -1,3 ändern. dann neu G29 und halt aufpassen wenn du dann startest die Hand am Reset lassen.

1-mal bearbeitet. Zuletzt am 22.03.17 13:25.

---

Wer freundlich zu mir ist zu dem bin auch ich freundlich. Wer Schreibfehler findet darf sie gerne behalten / Geeetech Prusa I3 ProX extended / Repetierhost / Mattercontroll / Slic3r

Hallo

Die Änderung von 1.1 auf 1.07 ist ja nicht wirklich viel !
Ich werde es mal ausprobieren das Offset anzupassen.
Ich möchte aber echt gerne wissen woher den die 0.4 mm kommen bzw warum er nicht auf Z 0 fährt sondern auf Z 0.4
Ich kann mir das nur so erklären das er versucht ein unebenes Bett auszugleichen , ohne die Möglichkeit das Z-Offset anzupassen wäre das ABL ja nicht in der Lage Unebenheiten auszugleichen.
Das Problem ist nur das es nicht ersichtlich ist warum er um den Faktor 0.4 korrigieren will. Könnte es sein das er in die falsche Richtung versucht zu kompensieren ?

Bed Level Correction Matrix:
+1.000000 +0.000000 +0.000125
+0.000000 +1.000000 -0.000531
-0.000125 +0.000531 +1.000000

Könnte vielleicht Slicer was damit zu tun haben ?
Was auffällig ist meine Layerhöhe ist 0.2 mm und die erste Schicht drucke ich mit 200% was ja genau 0.4 mm sind .
Das sollte aber die Düsenhöhe doch nicht beeinflussen ?!

mal ne frage so am rande *kopfkratz* hast du EEprom Aktiv ? Wenn ja musst du nach jedem neu flashen einmal die Werkseinstellungen Laden sonst wird ein geänderter Z-Oset nicht übernommen. Sieht man nach dem manuellen Homen da sollte dann nämlich dein Z-Wert auf dem eingestellten Offset stehen (achtung der wird als PLUS angezeigt, weil ja dann Triggerpunkt Sensor/Offset - PLUS Wert 0 ergibt)

---

Wer freundlich zu mir ist zu dem bin auch ich freundlich. Wer Schreibfehler findet darf sie gerne behalten / Geeetech Prusa I3 ProX extended / Repetierhost / Mattercontroll / Slic3r

Ja hab ich , war einer meiner ersten Gedanken :-)

naja was mir sonst noch einfällt ist das mit dem

#define Z_RAISE_BEFORE_PROBING 15
#define Z_RAISE_BETWEEN_PROBINGS 5

das hat bei mir am Anfang immer Probleme gemacht allerdings nicht im 10tel bereich wie bei Dir sondern immer um einen der beiden Werte, ich weis bloß nicht mehr welcher es war, hab mittlerweile beide auf 0.

---

Wer freundlich zu mir ist zu dem bin auch ich freundlich. Wer Schreibfehler findet darf sie gerne behalten / Geeetech Prusa I3 ProX extended / Repetierhost / Mattercontroll / Slic3r

Versuch mal M851 zu nutzen für den Offset

---

Gruß
Siggi

Geeetech I3 Pro B 8mm Acryl - Mega 2560 - Ramps 1.4 - TMC2100 - MK42 - E3DV6-Clone 0,4 - SSR 522-1dd60-40 (A-Senco) - Marlin RC8Bugfix 26.12.2016 - Repetier Host - Windows 7 64 Bit
Vulcanus mit Linearschienen
Anycubic i3 Mega

Ich weiß, ist schon etwas älter. Aber hat mal jemand daran gedacht, dass der Druck immer ca. bei 0.3 mm startet (durch Slicer bestimmt)? Das ist die Höhe für die erste Schicht.