Z probe height

The_Geak

Im using ramps 1.4 with repetier firmware and host program. No matter what value I change the z probe height to it dosnt help keep from my extuder being to close to the bed to print, cause jamming in my extruder. I have changed values both in the eeprom and the configure.h file with seemly little to no results. I have made the values both positive and negative to see if it would get closer or further from the bed. From what I can tell all of my auto bed level is really innaccurate and when it does work it seems its just by luck. 1 out of ever 5+ bed levels might get me one printable z axis distance that wont jam extruder. Most of the time the extruder is just mashed in to the bed. Is there another setting that im missing? is auto bed level just that terrible? I don't understand.

from what I can tell the z probeis working. I can manually deploy it with gcode commands, and undeploy it. it does click in when iut touches print bed. If I try to auto level 2x in a row with out powering off printer first it will cause the printer to act werid, all the axis will go seperate ways and the z probe led light will flash, not really sure whats the deal with that either.

The_Geak

Below is a current copy of my config.h files Z probe settings.

// #################### Z-Probing #####################

#define Z_PROBE_Z_OFFSET 0
#define Z_PROBE_Z_OFFSET_MODE 0
#define UI_BED_COATING 1
#define FEATURE_Z_PROBE 1
#define Z_PROBE_BED_DISTANCE 10
#define Z_PROBE_PIN ORIG_Z_MIN_PIN
#define Z_PROBE_PULLUP 0
#define Z_PROBE_ON_HIGH 1
#define Z_PROBE_X_OFFSET 0
#define Z_PROBE_Y_OFFSET 0
#define Z_PROBE_WAIT_BEFORE_TEST 0
#define Z_PROBE_SPEED 2
#define Z_PROBE_XY_SPEED 150
#define Z_PROBE_SWITCHING_DISTANCE 1
#define Z_PROBE_REPETITIONS 2
#define Z_PROBE_HEIGHT 1
#define Z_PROBE_START_SCRIPT "M340 P0 S700"
#define Z_PROBE_FINISHED_SCRIPT "M340 P0 S1500"
#define Z_PROBE_REQUIRES_HEATING 0
#define Z_PROBE_MIN_TEMPERATURE 150
#define FEATURE_AUTOLEVEL 1
#define Z_PROBE_X1 20
#define Z_PROBE_Y1 20
#define Z_PROBE_X2 120
#define Z_PROBE_Y2 20
#define Z_PROBE_X3 100
#define Z_PROBE_Y3 120
#define BED_LEVELING_METHOD 0
#define BED_CORRECTION_METHOD 0
#define BED_LEVELING_GRID_SIZE 5
#define BED_LEVELING_REPETITIONS 5
#define BED_MOTOR_1_X 0
#define BED_MOTOR_1_Y 0
#define BED_MOTOR_2_X 200
#define BED_MOTOR_2_Y 0
#define BED_MOTOR_3_X 100
#define BED_MOTOR_3_Y 200
#define BENDING_CORRECTION_A 0
#define BENDING_CORRECTION_B 0
#define BENDING_CORRECTION_C 0
#define FEATURE_AXISCOMP 0
#define AXISCOMP_TANXY 0
#define AXISCOMP_TANYZ 0
#define AXISCOMP_TANXZ 0

#ifndef SDSUPPORT // Some boards have sd support on board. These define the values already in pins.h
#define SDSUPPORT 0
#undef SDCARDDETECT
#define SDCARDDETECT -1
#define SDCARDDETECTINVERTED 0
#endif
#define SD_EXTENDED_DIR 1 /** Show extended directory including file length. Don't use this with Pronterface! /
#define SD_RUN_ON_STOP ""
#define SD_STOP_HEATER_AND_MOTORS_ON_STOP 1
#define ARC_SUPPORT 1
#define FEATURE_MEMORY_POSITION 1
#define FEATURE_CHECKSUM_FORCED 0
#define FEATURE_FAN_CONTROL 1
#define FEATURE_FAN2_CONTROL 0
#define FEATURE_CONTROLLER 0
#define ADC_KEYPAD_PIN -1
#define LANGUAGE_EN_ACTIVE 1
#define LANGUAGE_DE_ACTIVE 1
#define LANGUAGE_NL_ACTIVE 0
#define LANGUAGE_PT_ACTIVE 1
#define LANGUAGE_IT_ACTIVE 1
#define LANGUAGE_ES_ACTIVE 1
#define LANGUAGE_FI_ACTIVE 0
#define LANGUAGE_SE_ACTIVE 0
#define LANGUAGE_FR_ACTIVE 1
#define LANGUAGE_CZ_ACTIVE 0
#define LANGUAGE_PL_ACTIVE 1
#define LANGUAGE_TR_ACTIVE 1
#define UI_PRINTER_NAME "RepRap"
#define UI_PRINTER_COMPANY "Home made"
#define UI_PAGES_DURATION 4000
#define UI_ANIMATION 0
#define UI_SPEEDDEPENDENT_POSITIONING 0
#define UI_DISABLE_AUTO_PAGESWITCH 1
#define UI_AUTORETURN_TO_MENU_AFTER 30000
#define FEATURE_UI_KEYS 0
#define UI_ENCODER_SPEED 1
#define UI_REVERSE_ENCODER 0
#define UI_KEY_BOUNCETIME 10
#define UI_KEY_FIRST_REPEAT 500
#define UI_KEY_REDUCE_REPEAT 50
#define UI_KEY_MIN_REPEAT 50
#define FEATURE_BEEPER 0
#define CASE_LIGHTS_PIN -1
#define CASE_LIGHT_DEFAULT_ON 1
#define UI_START_SCREEN_DELAY 1000
#define UI_DYNAMIC_ENCODER_SPEED 1
/**
Beeper sound definitions for short beeps during key actions
and longer beeps for important actions.
Parameter is delay in microseconds and the secons is the number of repetitions.
Values must be in range 1..255
/
#define BEEPER_SHORT_SEQUENCE 2,2
#define BEEPER_LONG_SEQUENCE 8,8
#define UI_SET_PRESET_HEATED_BED_TEMP_PLA 60
#define UI_SET_PRESET_EXTRUDER_TEMP_PLA 190
#define UI_SET_PRESET_HEATED_BED_TEMP_ABS 110
#define UI_SET_PRESET_EXTRUDER_TEMP_ABS 240
#define UI_SET_MIN_HEATED_BED_TEMP 30
#define UI_SET_MAX_HEATED_BED_TEMP 120
#define UI_SET_MIN_EXTRUDER_TEMP 170
#define UI_SET_MAX_EXTRUDER_TEMP 260
#define UI_SET_EXTRUDER_FEEDRATE 2
#define UI_SET_EXTRUDER_RETRACT_DISTANCE 3

The_Geak

so nobody understands this firmware? I think maybe this firmware is not good with z probe?

The_Geak

people say to change Z probe height to change distance from nozzle to bed but I have found this setting to be useless since it dosnt acutally do any thing.

The_Geak

i see videos of when other people home their Z axis their probe deploys to i assume be used sort of like a z min endstop, my probe doesnt do this on Z home.

RAyWB

https://www.repetier.com/documentation/repetier-firmware/z-probing/<br/>

BryanByrne

I am having a problem with my bed leveling that I hope fits this thread. In the past week, when my Da Vinci 2.0a tries to auto bed level, the left-hand extruder hits the side of the bed sensor as it is moving across thus causing a G29 bed level error and disables printing. It has never done this until now and nothing has changed (ie firmware, software, etc). Thoughts? It's running Repetier 0.92.10M firmware and I'm using Repetier-Host 2.1.3. I've tried disabling auto level with M321 S1 but it stills tries to auto level every time it tries to print. I'm sending the code through Repetier-Host.

Repetier

M321 just makes it use latest autolevel result, but is not required if you have already enabled it and autoleveling using
G32 S2
enables it and stores it in eeprom, so no need to repeat. G29 is not autoleveling, it is just measuring z as average of 3 points - at least in repetier-firmware.

Make sure the 3 points span a region that is reachable with active z probe. If you hit parts that just means the 3 points are too far outside.

If every print autolevels you must have the code either in host start gcode or in slicer start gcode. I personally do not autolevel every time. Only if I think I have moved the bed.