Duet3D Logo Duet3D
    • Tags
    • Documentation
    • Order
    • Register
    • Login

    The G29 Mesh does not load well

    Scheduled Pinned Locked Moved
    General Discussion
    2
    7
    381
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • juanmenaundefined
      juanmena
      last edited by

      Good afternoon,

      I have a core XY (Voron 2.1) with a bed of 350x350 mm, and when I print before, I make a G29, but it seems that it does not carry the mesh well, because the nozzle does not stick well throughout the bed. Photo command I am using an original BlTouch.

      The first thing I do is a Macro to start printing.

      I send the files, let's see if there is something wrong.

      The M566 (Which has nothing to do with the error, is it correct, for a good operation or E, should it be faster?)

      Thank you very much in advance.

      CONFIG.G

      ; Configuration file for Duet WiFi (firmware version 1.21)
      ; executed by the firmware on start-up
      ;
      ; generated by RepRapFirmware Configuration Tool v2 on Sun Mar 10 2019 17:30:42 GMT+0100 (hora estándar de Europa central)

      ; General preferences
      G90 ; Send absolute coordinates...
      M83 ; ...but relative extruder moves

      M667 S1 ; Select CoreXY mode
      M555 P2 ; Set firmware compatibility to look like Marlin

      ; Network
      M550 P"Margarita" ; Set machine name
      M552 S1 ; Enable network
      M587 S"i" P"mi***" ; Configure access point. You can delete this line once connected
      M586 P0 S1 ; Enable HTTP
      M586 P1 S0 ; Disable FTP
      M586 P2 S0 ; Disable Telnet

      ; Drives
      M584 X0 Y1 Z5:6:7:8 E3:4:2 ; motor bindings
      M671 X400:400:-50:-50 Y355:-85:-85:355 S5 ; Z drive positions

      M569 P0 S1 ; X motor direction
      M569 P1 S1 ; Y motor direction
      M569 P5 S0 ; Z-- motor direction
      M569 P6 S1 ; Z-+ motor direction
      M569 P7 S0 ; Z++ motor direction
      M569 P8 S1 ; Z+- motor direction
      M569 P3 S1 ; E0 motor direction
      ;M569 P4 S1 ; E1 motor direction
      ;M569 P2 S1 ; E2 motor direction

      M350 X256 Y256 Z256 I0 ; Configure microstepping without interpolation
      M350 E16 I0 ; Configure microstepping with interpolation
      M92 X1280.00 Y1280.00 Z6400.00 E549.00 ; Set steps per mm
      M566 X900.00 Y900.00 Z150.00 E120.00 ; Set maximum instantaneous speed changes (mm/min)
      M203 X24000.00 Y24000.00 Z1800.00 E6000.00 ; Set maximum speeds (mm/min)
      M201 X3600.00 Y3600.00 Z500.00 E3600.00 ; Set accelerations (mm/s^2)
      M906 X900.00 Y900.00 Z900.00 E900.00 I30 ; Set motor currents (mA) and motor idle factor in per cent
      M84 S30 ; Set idle timeout

      ; Axis Limits

      M208 X0 Y0 Z0 S1 ; Set axis minima
      M208 X350 Y350 Z350 S0 ; Set axis maxima

      ; Endstops
      ;M574 X1 Y1 Z1 S0 ; Set active low and disabled endstops
      M574 X1 Y1 S0
      ;M574 Z1 S0 ; Set active low and disabled endstops

      M98 P"/macros/Zprobe BlTouch"

      ; Heaters
      M305 P0 T100000 B3950 R4700 ; Set thermistor + ADC parameters for heater 0
      M143 H0 S150 ; Set temperature limit for heater 0 to 120C
      M305 P1 T100000 B4725 C7.060000e-8 R4700
      M143 H1 S280 ; Set temperature limit for heater 1 to 280C

      ; Fans
      M106 P2 C"CAPA" ; Set fan 2 value, PWM signal inversion and frequency. Thermostatic control is turned off
      M106 P1 T45 H1 C"HOTEND" ; Set fan 1 value, PWM signal inversion and frequency. Thermostatic control is turned on

      ; Tools
      M563 P0 D0 H1 F2 ; Define tool 0
      G10 P0 X0 Y0 Z0 ; Set tool 0 axis offsets
      G10 P0 R0 S0 ; Set initial tool 0 active and standby temperatures to 0C

      ; Automatic power saving
      M911 S22 R23 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; Set voltage thresholds and actions to run on power loss

      ;Registro de eventos
      M929 P"registro.txt" S1 ; iniciar el registro en el archivo eventlog.txt

      ; Calibracion de la Temperatura

      M912 P0 S-10

      M572 D0 S0.15

      ; Automatic saving after power loss is not enabled

      M501

      ; Custom settings are not configured

      MACRO BLTOUCH:

      ; Z-Probe con BLTouch
      M98 P"/macros/Activar EndStop"
      M574 Z1 S2 ; Set endstops controlled by probe
      M307 H7 A-1 C-1 D-1 ; Disable heater on PWM channel for BLTouch
      M558 P9 F400 H5 R0.2 T6000 A5 S0.03 ;B1 ; Set Z probe type to bltouch and the dive height + speeds
      G31 P25 X0 Y-26.30 Z1.40 ; Set Z probe trigger value, offset and trigger height
      M557 X50:300 Y50:300 S20 ; Define mesh grid

      MACRO INICIAR IMPRESION:

      ;M98 P"/macros/Iniciar Impresion" ; Cargar Parametros de la malla

      M561
      G29 S2
      M280 P7 S160; Liberación de alarma BLTouch
      G4 P100; retraso para BLTouch
      M98 P"/sys/homeall.g"
      G1 X175 Y175 F12000
      G30
      G32
      G1 X175 Y175 F12000
      G30
      G1 Z10 F36000
      G29

      photo_2019-09-17_19-32-14.jpg

      Thank you.

      Phaedruxundefined 2 Replies Last reply Reply Quote 0
      • Phaedruxundefined
        Phaedrux Moderator @juanmena
        last edited by

        @juanmena said in The G29 Mesh does not load well:

        M561
        G29 S2
        M280 P7 S160; Liberación de alarma BLTouch
        G4 P100; retraso para BLTouch
        M98 P"/sys/homeall.g"
        G1 X175 Y175 F12000
        G30
        G32
        G1 X175 Y175 F12000
        G30
        G1 Z10 F36000
        G29

        This is really confusing.

        You're loading a saved mesh, but then later you're doing another probe routine.
        You're doing a homeall and then a G32, and then another G30.
        What is in your homeall.g? What is in bed.g?

        Z-Bot CoreXY Build | Thingiverse Profile

        1 Reply Last reply Reply Quote 0
        • Phaedruxundefined
          Phaedrux Moderator @juanmena
          last edited by

          @juanmena said in The G29 Mesh does not load well:

          M558 P9 F400

          The dive speed of the probing is quite fast. The BLTouch works best with a slower probe speed for best repeatability. Try F120.

          Z-Bot CoreXY Build | Thingiverse Profile

          1 Reply Last reply Reply Quote 0
          • juanmenaundefined
            juanmena
            last edited by juanmena

            bed.g

            ; bed.g
            ; called to perform automatic bed compensation via G32
            ;
            ; generated by RepRapFirmware Configuration Tool v2 on Tue Apr 23 2019 16:30:59 GMT+0200 (hora de verano de Europa central)

            M561 ; clear any bed transform

            M401

            G30 P0 X25 Y35 H0 Z-99999
            G30 P1 X25 Y310 H0 Z-99999
            G30 P2 X325 Y310 H0 Z-99999
            G30 P3 X325 Y35 H0 Z-99999 S4

            G30 P0 X25 Y35 H0 Z-99999
            G30 P1 X25 Y310 H0 Z-99999
            G30 P2 X325 Y310 H0 Z-99999
            G30 P3 X325 Y35 H0 Z-99999 S4

            ; Homez.g

            M98 P"0:/macros/Zprobe BlTouch"

            G91
            G1 Z10 F6000 S2 ; lift Z relative to current position
            G90
            G1 X175 Y175 F12000 ;Posiciona en el centro
            M280 P7 S10
            G30 ; Do a single probe to home our Z axis
            G90 ; Make sure we are in absolute mode
            G1 Z10 F6000 ; Rapidly move the Z axis to Z=10.

            juanmenaundefined Phaedruxundefined 2 Replies Last reply Reply Quote 0
            • juanmenaundefined
              juanmena @juanmena
              last edited by

              This post is deleted!
              1 Reply Last reply Reply Quote 0
              • Phaedruxundefined
                Phaedrux Moderator @juanmena
                last edited by

                @juanmena said in The G29 Mesh does not load well:

                M280 P7 S10

                You don't need to manually control the BLTouch pin. It will deploy as needed. So you can remove those M280 commands from your files.

                The bed.g you have configured is using the old plane for of bed compensation. It is redundant since you are using G29 for mesh bed compensation already. So I think you can just remove the G32 or alter the bed.g to use the independent Z motor leveling.

                So before a print all you have to do is

                G28 ; home all axis
                G29 ; mesh compensation probe routine if you want to probe before every print

                Or G29 S1 ; load previously saved mesh map

                Z-Bot CoreXY Build | Thingiverse Profile

                1 Reply Last reply Reply Quote 0
                • juanmenaundefined
                  juanmena
                  last edited by

                  Thank you.

                  I will try it and tomorrow I comment the results.

                  Thank you

                  1 Reply Last reply Reply Quote 0
                  • First post
                    Last post
                  Unless otherwise noted, all forum content is licensed under CC-BY-SA