Comment on Major issues with klipper and bed levelling

DrakeRichards@lemmy.world ⁨9⁩ ⁨months⁩ ago

• Grippler@feddit.dk ⁨9⁩ ⁨months⁩ ago

  [gcode_macro PRINT_BEGIN] description: Begin printing with nozzle wipe gcode: M300 P500 {% set BED_TEMP = params.BED_TEMP|default(60)|float %} {% set EXTRUDER_TEMP = params.EXTRUDER_TEMP|default(210)|float %} BED_MESH_PROFILE LOAD=default M104 S{EXTRUDER_TEMP} M140 S{BED_TEMP} {% if printer.toolhead.homed_axes != “xyz” %} G28 {% endif %} #BED_TILT_CALIBRATE G1 X80 Y240 Z5.0 F3000 ; position nozzle right next to wipe pad M190 S{BED_TEMP} M109 S{EXTRUDER_TEMP} M300 P500 G4 P50 M300 P500 S1500 G1 Z-0.1 ; lower nozzle before wiping G1 X90 F500 ; wipe nozzle across pad in X direction G1 Y235 F500 ; wipe nozze in Y direction G1 Z3 ; lift nozzle to 3mm G1 X90 Y-3 F6000 ; move nozze to front-left center of bed for purging G1 Z0.28 ; lower nozzle to 0.28mm G1 X120 E25 F200 ; extrude 25mm of filament in a 40mm line G92 E0 ; reset extruder position G1 E-1 F2100 ; quickly retract filament 3mm G1 X135 F10000 ; quickly move away from purge
  G92 E0

  source

  • ShepherdPie@midwest.social ⁨9⁩ ⁨months⁩ ago

    Looks like you have it set to load the profile “default” instead of “bed60”

    Also worth asking, did you have your start gcode set in your slicer previously and if so, did you delete it out of there now that you’re using klipper macros?

    source

    • Grippler@feddit.dk ⁨9⁩ ⁨months⁩ ago

      Yeah forgot that I switched to default again to make sure it wasn’t something with the different profiles messing it up. I manually update the mesh before every print now.

      I did have my start gcode in the slicer before, but that’s been replaced with the macro.

      source

      • ShepherdPie@midwest.social ⁨9⁩ ⁨months⁩ ago

        I’ll try to check mine when I’m back home later. I just use the default profile since I don’t ever adjust anything with the bed unless it’s out of spec. Even printing at slightly different temps doesn’t seem to affect anything as far as bed leveling is concerned.

        source

        • -> View More Comments
  • DrakeRichards@lemmy.world ⁨9⁩ ⁨months⁩ ago

    Could you also post the [bed_mesh] section of printer.cfg?

    source

    • Grippler@feddit.dk ⁨9⁩ ⁨months⁩ ago

      Sure

      [bed_mesh] speed: 150 horizontal_move_z: 5 mesh_min: 25, 17 mesh_max: 220, 200 algorithm: bicubic bicubic_tension: 0.5 probe_count: 6, 6

      source

      • morbidcactus@lemmy.ca ⁨9⁩ ⁨months⁩ ago

        What type of probe and what’s the config on it?

        pin: PC14
        x_offset: 23
        y_offset: 5
        #z_offset: 0.10
        speed: 20.0
        samples: 5 
        samples_result: average
        sample_retract_dist: 1.0
        #samples_tolerance: 0.010
        #samples_tolerance_retries: 10 
          
        Is what I've got my pinda probe configured with, was playing around with sample tolerances like I have on my printer with a tap probe but I just found the inductive probe has a lot of variation, I added more samples to hopefully average out that error. 
        
        ```[bed_mesh]
        algorithm: bicubic
        fade_start: 0.6
        fade_end: 10.0
        bicubic_tension: 0.2
        faulty_region_1_max: 120.0, 74.0 
        faulty_region_1_min: 85.0, 45.0 # 103,69
        faulty_region_2_max: 125.0, 165
        faulty_region_2_min: 70, 110 # 103, 137
        horizontal_move_z: 2
        mesh_max: 228,210
        mesh_min: 24, 6
        mesh_pps: 2, 2
        probe_count: 5,5
        speed: 200
         
        Is my mesh setup, based on a [mk3s klipper config](https://github.com/dz0ny/klipper-prusa-mk3s). Meshes look a little odd but I ran some bed level prints fine and just ran a full plate of abs with pretty consistent 1st layer.
        

        source
• Grippler@feddit.dk ⁨9⁩ ⁨months⁩ ago

  [deleted]

  source

  • ShepherdPie@midwest.social ⁨9⁩ ⁨months⁩ ago

    I’m not at my computer now to be able to give specific examples but this most surely sounds like something wrong with the start gcode and klipper not loading your saved mesh before running the print. I’d double check the docs and make sure you have the correct gcode to load your saved mesh.

    source

    • Grippler@feddit.dk ⁨9⁩ ⁨months⁩ ago

      Made a different reply with the start macro I use, I checked and it is the one I use.

      source