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

    Auto Bed levelling Errors - printer continues print

    Scheduled Pinned Locked Moved
    Tuning and tweaking
    3
    6
    273
    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.
    • WillGIamundefined
      WillGIam
      last edited by WillGIam

      Hey everyone!

      I have now 4 printers running with duet, sensorless homing and auto bed compensation.

      But everytime he gets an error while probing (Z probe not triggered, Z probe already triggered, measurements not consistent, ...) he continues printing instead of stopping. Is there any way to configure this? So that he lifts Z and stops for example?

      Thats my config.g:

      ; Configuration file for Duet WiFi (firmware version 2.xx)
      ; executed by the firmware on start-up
      ;
      ; generated by RepRapFirmware Configuration Tool v2.0.4 on Wed Oct 02 2019 13:56:34 GMT+0200 (Mitteleuropäische Sommerzeit)

      ; General preferences
      G90 ; send absolute coordinates...
      M83 ; ...but relative extruder moves
      M550 P"Soldex SX" ; set printer name
      M667 S1

      ; Network
      M552 S1 ; enable network
      M586 P0 S1 ; enable HTTP
      M586 P1 S0 ; disable FTP
      M586 P2 S0 ; disable Telnet

      ; Drives
      M569 P0 S0 R-1 ; physical drive 0 deaktiviert
      M569 P1 S0 ; physical drive 1 goes backwards
      M569 P2 S1 ; physical drive 2 goes forwards
      M569 P3 S1 ; physical drive 3 goes forwards
      M569 P4 S0 ; physical drive 4 goes forwards
      M584 X4 Y1 Z2 E3 ; set drive mapping
      M350 X16 Y16 Z16 E16:16 I1 ; configure microstepping with interpolation
      M92 X80.00 Y80.00 Z400.00 E420.00 ; set steps per mm
      M566 X900.00 Y900.00 Z12.00 E600.00 ; set maximum instantaneous speed changes (mm/min)
      M203 X18000.00 Y18000.00 Z1000.00 E7200.00 ; set maximum speeds (mm/min)
      M201 X1500.00 Y1500.00 Z500.00 E1000.00 ; set accelerations (mm/s^2)
      M906 X1000 Y1000 Z1500 E800 I30 ; set motor currents (mA) and motor idle factor in per cent
      M84 S1 ; Set idle timeout

      ;Timing

      ; Axis Limits
      M208 X0 Y0 Z0 S1 ; set axis minima
      M208 X380 Y520 Z445 S0 ; set axis maxima

      ; Endstops
      M574 X1 Y1 S3 ; set endstops controlled by motor stall detection

      ; Z-Probe
      M574 Z1 S2 ; set endstops controlled by probe
      M307 H7 A-1 C-1 D-1 ; disable heater 7 on PWM channel for BLTouch
      M558 P5 H3.5 F400 T7000 S0.03 A6 X0 Y0 Z1 I1 ; Set Z probe type/mode 5. H=Dive Height. F=Speed the bed moves
      G31 P25 X36.4 Y16 Z1.42 ; Z probe trigger value, offset in relation to nozzle.
      ; And trigger height adjustment; Geringer = weiter weg vom Bett
      M557 X36.4:309 Y87:387 S54.52 ; define mesh grid

      ; Heaters
      M307 H0 B0 S1.00 ; disable bang-bang mode for the bed heater and set PWM limit
      M305 P0 T100000 B4138 R4700 ; set thermistor + ADC parameters for heater 0
      M143 H0 S120 ; set temperature limit for heater 0 to 120C
      M305 P1 T100000 B4138 R4700 ; set thermistor + ADC parameters for heater 1
      M143 H1 S280 ; set temperature limit for heater 1 to 280C

      ; Fans
      M106 P0 S1 I0 F500 H-1 ; set fan 0 value, PWM signal inversion and frequency. Thermostatic control is turned off
      M106 P1 S0 I0 F500 H-1 ; set fan 1 value, PWM signal inversion and frequency. Thermostatic control is turned off
      M106 P2 S0 I0 F500 H-1 ; set fan 2 value, PWM signal inversion and frequency. Thermostatic control is turned off

      ; Tools
      M563 P0 D0 H1 F0 ; 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

      ; Custom settings
      M501

      And my homing script:

      ; HOME X
      ; Custom settings
      M574 X2 Y1 Z0 S3
      M915 P0 S8 R0 ; Higher values reduce the sensitivity

      G91
      G92 X0
      G1 X5 ; use relative positioning
      G1 S1 X-500 F5000 ; move all carriages up 500mm, stopping at the endstop
      G92 X0 ; X reset
      G90 ; back to absolute positioning
      G91
      G92 X0
      G1 X5 ; use relative positioning
      G1 S1 X-500 F5000 ; move all carriages up 500mm, stopping at the endstop
      G92 X0 ; X reset
      G90 ; back to absolute positioning

      ; HOME Y
      M574 X2 Y1 Z0 S3 ; Higher values reduce the sensitivity
      M915 P1 S2 R0

      M913 X30
      G91
      G92 Y0
      G1 Y20 ; use relative positioning
      G1 S1 Y-500 F3500 ; move all carriages up 500mm, stopping at the endstop
      G92 Y0 ; X reset
      G90 ; back to absolute positioning
      M913 X100

      M913 X30
      G91
      G92 Y0
      G1 Y20 ; use relative positioning
      G1 S1 Y-500 F3500 ; move all carriages up 500mm, stopping at the endstop
      G92 Y0 ; X reset
      G90 ; back to absolute positioning
      M913 X100

      ; HOME Z
      M280 P7 S160 I1 ;
      G92 Z200
      G91
      G1 Z10
      G90
      M280 P7 S10 I1 ;
      M203 Z500
      G91 ; relative positioning
      G1 Z5 F1000 S2 ; lift Z relative to current position
      G90 ; absolute positioning
      G1 X30 Y30 F12000 ; go to first probe point
      G30 ; home Z by probing the bed
      M203 Z1800

      The homing script is a little workaround, because sometimes he recognizes the "endstop" while homing too early. Playing around with sensitivity and speed did not ended up in good results.

      Have a nice week.

      William

      dc42undefined Phaedruxundefined 2 Replies Last reply Reply Quote 0
      • dc42undefined
        dc42 administrators @WillGIam
        last edited by

        @WillGIam said in Auto Bed levelling Errors - printer continues print:

        But everytime he gets an error while probing (Z probe not triggered, Z probe already triggered, measurements not consistent, ...) he continues printing instead of stopping. Is there any way to configure this? So that he lifts Z and stops for example?

        Yes, use RepRapFirmware 3.01 and use conditional GCode to terminate the print if there was a probing error.

        Duet WiFi hardware designer and firmware engineer
        Please do not ask me for Duet support via PM or email, use the forum
        http://www.escher3d.com, https://miscsolutions.wordpress.com

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

          @WillGIam said in Auto Bed levelling Errors - printer continues print:

          M558 P5 H3.5 F400 T7000 S0.03 A6 X0 Y0 Z1 I1 ; Set Z probe type/mode 5. H=Dive Height. F=Speed the bed moves

          If you're using a BLTouch you can clean up this command a bit for potentially better results.

          M558 P9 H3.5 F100 T7000 R0.5 A6 S0.03

          Z-Bot CoreXY Build | Thingiverse Profile

          WillGIamundefined 1 Reply Last reply Reply Quote 0
          • WillGIamundefined
            WillGIam @Phaedrux
            last edited by

            @Phaedrux said in Auto Bed levelling Errors - printer continues print:

            @WillGIam said in Auto Bed levelling Errors - printer continues print:

            M558 P5 H3.5 F400 T7000 S0.03 A6 X0 Y0 Z1 I1 ; Set Z probe type/mode 5. H=Dive Height. F=Speed the bed moves

            If you're using a BLTouch you can clean up this command a bit for potentially better results.

            M558 P9 H3.5 F100 T7000 R0.5 A6 S0.03

            Thanks for your answer. I´m not using a BLTouch.

            I´ll try a newer firmware.

            Thanks!

            1 Reply Last reply Reply Quote 0
            • WillGIamundefined
              WillGIam @dc42
              last edited by

              @dc42 said in Auto Bed levelling Errors - printer continues print:

              conditional GCode

              Hey DC42!

              Thanks for your answer. So if I see this right, I have to add an if loop after G29 where I have to ask for error messages? Is there a boolean or something like this? I cannot find the right page in the documentation I think...

              Best regards

              1 Reply Last reply Reply Quote 0
              • WillGIamundefined
                WillGIam @dc42
                last edited by

                @dc42

                I can´t find a list with the "native" variables of the firmware. I could use the abort function after my G29 in an if loop for checking for error messages, but I don´t know how they named. I found some scripts online, but I don´t know where they got the information about the other variables....

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