Z probe doesn't work after z home max

edited September 2016 in Feature Requests
hi

i have a strange problem, if i dont home the z axis from my printer the z probing works pretty fine but after z max home the z probe wan't work, the printer ignired the z probe offset and just drive the z axis too z min but with out trigger so the nozzle hits the bed.

Comments

  • What printer type? Deltas even home z max but then go down to z probe bed distance to start probing. You should also go down before starting probing. Maybe that is also what is happening, but with z length set too high you will go below bed before starting probing. So try reducing z length of printer.
  • edited September 2016
    EDIT: Yes your right, that was the Problem :D
    Epic fail
    :((
  • edited September 2016
    now i have the next issue :/
    In the repetier host G33 is an unknown command(G32 still works), i think i've this issue cause z-probe support is not compiled.
    But my configuration string is very old and dont match with my used config.h so i cant upload my config into the online configurator to enable the support without losing my settings :(

  • edited September 2016
    I've made an new FW with the Config tool and ervery thing works fine, but my printer makes no z correction.
    If i send the command G32 the printer makes 3 test executions on 3 points, but with out correction.

    // #################### 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 5
    #define Z_PROBE_PIN 63
    #define Z_PROBE_PULLUP 0
    #define Z_PROBE_ON_HIGH 1
    #define Z_PROBE_X_OFFSET 0
    #define Z_PROBE_Y_OFFSET -56
    #define Z_PROBE_WAIT_BEFORE_TEST 0
    #define Z_PROBE_SPEED 5
    #define Z_PROBE_XY_SPEED 150
    #define Z_PROBE_SWITCHING_DISTANCE 1
    #define Z_PROBE_REPETITIONS 1
    #define Z_PROBE_HEIGHT 1
    #define Z_PROBE_START_SCRIPT ""
    #define Z_PROBE_FINISHED_SCRIPT ""
    #define Z_PROBE_REQUIRES_HEATING 0
    #define Z_PROBE_MIN_TEMPERATURE 150
    #define FEATURE_AUTOLEVEL 1
    #define Z_PROBE_X1 5
    #define Z_PROBE_Y1 5
    #define Z_PROBE_X2 180
    #define Z_PROBE_Y2 5
    #define Z_PROBE_X3 5
    #define Z_PROBE_Y3 130
    #define BED_LEVELING_METHOD 0
    #define BED_CORRECTION_METHOD 1
    #define BED_LEVELING_GRID_SIZE 5
    #define BED_LEVELING_REPETITIONS 5
    #define BED_MOTOR_1_X 266.5
    #define BED_MOTOR_1_Y 97
    #define BED_MOTOR_2_X -91.5
    #define BED_MOTOR_2_Y -18
    #define BED_MOTOR_3_X 288.5
    #define BED_MOTOR_3_Y -18
    #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
  • What does the log say? It will show if execution stops due to a error while probing. It also shows if autoleveling gets enabled.
  • edited September 2016
    If i send G32 the log says Autocorretion disabled than he probes all without any error massage, my next step was to write in the probe start script M323 S1, after this the log shows:  autocorrection dissabled; autocorrection enabled; (and the porbe points and that stuff)
  • edited September 2016
    image

    here you can see the log from the host app
Sign In or Register to comment.