›

Auto bed levelling

giangntgiangnt
edited May 26 in Repetier-Firmware
I am using repetier firmware, i was enabled auto bed levelling, with 3D touch probe (same BL touch), i was be error "G33 failed" please help me
 
https://www.facebook.com/groups/349181957012003/posts/781028827160645

this is link videos describe error

This is config Z_probe

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

#define Z_PROBE_Z_OFFSET 0
#define Z_PROBE_Z_OFFSET_MODE 0
#define UI_BED_COATING 0
#define FEATURE_Z_PROBE 1
#define EXTRUDER_IS_Z_PROBE 0
#define Z_PROBE_DISABLE_HEATERS 0
#define Z_PROBE_BED_DISTANCE 15
#define Z_PROBE_PIN ORIG_Z_MIN_PIN
#define Z_PROBE_PULLUP 1
#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 5
#define Z_PROBE_XY_SPEED 100
#define Z_PROBE_SWITCHING_DISTANCE 1
#define Z_PROBE_REPETITIONS 2
#define Z_PROBE_USE_MEDIAN 0
#define Z_PROBE_HEIGHT 0.9
#define Z_PROBE_DELAY 0
#define Z_PROBE_START_SCRIPT ""
#define Z_PROBE_FINISHED_SCRIPT ""
#define Z_PROBE_RUN_AFTER_EVERY_PROBE ""
#define Z_PROBE_REQUIRES_HEATING 0
#define Z_PROBE_MIN_TEMPERATURE 0
#define FEATURE_AUTOLEVEL 1
#define FEATURE_SOFTWARE_LEVELING 0
#define Z_PROBE_X1 0
#define Z_PROBE_Y1 -60
#define Z_PROBE_X2 -30
#define Z_PROBE_Y2 -60
#define Z_PROBE_X3 30
#define Z_PROBE_Y3 -60
#define BED_LEVELING_METHOD 1
#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

Comments

  • giangntgiangnt
    https://www.facebook.com/groups/349181957012003/posts/781028827160645

    this is link videos describe error
  • RepetierRepetier
    Best is to also see the firmware output to console of host. There you see normally what goes wrong.
    From the video I guess your testing area is outside reachable positions.

    For G33 these settings are relevant
    /* DISTORTION_CORRECTION compensates the distortion caused by mechanical
    * imprecisions of nonlinear (i.e. DELTA) printers assumes that the floor is
    * plain (i.e. glass plate) and that it is perpendicular to the towers and that
    * the (0,0) is in center requires z-probe G33 measures the Z offset in matrix
    * NxN points (due to nature of the delta printer, the corners are extrapolated
    * instead of measured) and compensate the distortion more points means better
    * compensation, but consumes more memory and takes more time
    * DISTORTION_CORRECTION_R is the distance of last row or column from center
    */

    #define DISTORTION_CORRECTION 1
    #define DISTORTION_CORRECTION_POINTS 5
    /** Max. distortion value to enter. Used to prevent dangerous errors with big
    * values. */
    #define DISTORTION_LIMIT_TO 2
    /* For delta printers you simply define the measured radius around origin */
    #define DISTORTION_CORRECTION_R 80
    /* For all others you define the correction rectangle by setting the min/max
    * coordinates. Make sure the the probe can reach all points! */
    #define DISTORTION_XMIN 10
    #define DISTORTION_YMIN 10
    #define DISTORTION_XMAX 190
    #define DISTORTION_YMAX 190

    /** Uses EEPROM instead of ram. Allows bigger matrix (up to 22x22) without any
    ram cost. Especially on arm based systems with cached EEPROM it is good, on
    AVR it has a small performance penalty.
    */
    #define DISTORTION_PERMANENT 1
    /** Correction computation is not a cheap operation and changes are only small.
    So it is not necessary to update it for every sub-line computed. For example
    lets take DELTA_SEGMENTS_PER_SECOND_PRINT = 150 and fastest print speed 100
    mm/s. So we have a maximum segment length of 100/150 = 0.66 mm. Now lats say our
    point field is 200 x 200 mm with 9 x 9 points. So between 2 points we have 200 /
    (9-1) = 25 mm. So we need at least 25 / 0.66 = 37 lines to move to the next
    measuring point. So updating correction every 15 calls gives us at least 2
    updates between the measured points. NOTE: Explicit z changes will always
    trigger an update!
    */
    #define DISTORTION_UPDATE_FREQUENCY 15
    /** z distortion degrades to 0 from this height on. You should start after the
    first layer to get best bonding with surface. */
    #define DISTORTION_START_DEGRADE 0.5
    /** z distortion correction gets down to 0 at this height. */
    #define DISTORTION_END_HEIGHT 1.5
    /** If your corners measurement points are not measurable with given radius, you
    can
    set this to 1. It then omits the outer measurement points allowing a larger
    correction area.*/
    #define DISTORTION_EXTRAPOLATE_CORNERS 0

    Consider DISTORTION_EXTRAPOLATE_CORNERS 1 as this removes to edge point lying outside anyway allowing a bigger area to be reached.


  • giangntgiangnt
    edited May 29
    https://drive.google.com/file/d/1iAod8OTC6gr66C9qteg0zKKjABnUSg3w/view?usp=sharing

    i am trying fix, but it still error, please help me!
    my config is in link, hope you check it, and please tell me where it is error, 
    At the moment. It still error autobed leveling, and distortion correction
  • RepetierRepetier
    Only config is needed, but what I really need is firmware output to serial connection when you get the error, That tells what the problem is. Only then it makes sense to look into config file at all. Also not that changes might not end in eeprom until you reset eeprom to config settings with
    M502
    M500

  • giangntgiangnt
    Link above, include config.h, i use Ardunio for compilation, all error, when i try autobed leveling and measures distortion correction like video shared, i still don't understand what is the firmware output you want
  • RepetierRepetier
    When you connect printer to pc with Repetier-Server or Repetier-Host and send G33 you can see in console/log the messages send from firmware which describe why it fails. This is exactly for such cases where you do not know what value is wrong. First you need to understand what is going on. Could be illegal position or probe did not untrigger because you meve not up enough or something else.
  • giangntgiangnt
    https://drive.google.com/drive/folders/1oYenQQ_HllhjUC9XAMAU3V3VjBNlQGnZ?usp=sharing

    in the link. i was uploaded two png, its show error when i use command G33 and G30, ......


  • RepetierRepetier
    Es reicht vollkommen den Text aus dem Log zu kopieren und einzufügen.

    Wie du siehst ist der Fehler das die Z Probe triggert bevor sie den Boden trifft. Ich hoffe es zumindest. Wenn du weiter oben bist sende mal 
    M119
    da sollte z-probe mit L stehen. Offenbar hast du das signal falsch konfiguriert und es ist ständig high oder er ist im Alarmstatus, dann ist der gleube ich auch high.
  • giangntgiangnt
    what do me need copy and paste?, and where it?, please tell me!
  • RepetierRepetier
    Sorry wrong language, her ein english:
    It is sufficient to copy and paste the text from the log.

    As you can see, the error is that the Z Probe triggers before it hits the ground. At least I hope so. When you are further up send 
    M119
    there should be z-probe with L. Obviously you have configured the signal incorrectly and it is constantly high or it is in alarm status, in which case I think it is also high.

    The copy remark was for future questions. All I needed from your screenshot was the output in log at the bottom and you can simply copy these messages.
Sign In or Register to comment.