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

    Leveling issue

    Scheduled Pinned Locked Moved
    Firmware installation
    5
    12
    350
    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.
    • Btjundefined
      Btj
      last edited by

      Do not make this machine level!
      M115
      FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi / Ethernet FIRMWARE_VERSION: 3.3 ELECTRONICS: Duet WiFi 1.02 or later FIRMWARE_DATE: 2021-06-15 21:45:03

      ; General preferences
      G90 ; send absolute coordinates...
      M83 ; ...but relative extruder moves
      M550 P"Ender 5 Plus" ; set printer name

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

      ; Drives
      M569 P0 S1 ; physical drive 0 goes forwards
      M569 P1 S1 ; physical drive 1 goes forwards
      M569 P2 S0 ; physical drive 2 goes backwards
      M569 P3 S0 ; physical drive 3 goes backwards
      M584 X0 Y1 Z2 E3 ; set drive mapping
      M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation
      M92 X80.00 Y80.00 Z800.00 E156.47 ; set steps per mm
      M566 X900.00 Y900.00 Z80.00 E120.00 ; set maximum instantaneous speed changes (mm/min)
      M203 X6000.00 Y6000.00 Z300.00 E1200.00 ; set maximum speeds (mm/min)
      M201 X500.00 Y500.00 Z30.00 E250.00 ; set accelerations (mm/s^2)
      M906 X800 Y800 Z800 E800 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 Z400 S0 ; set axis maxima

      ; Endstops
      M574 X1 S1 P"xstop" ; X min active high endstop switch
      M574 Y1 S1 P"ystop" ; Y min active high endstop switch

      Z-Probe

      M558 P9 C"^zprobe.in" H5 F100 T2000
      M950 S0 C"exp.heater3"
      G31 X-50 Y-11.02 Z 0 P25
      ; Heaters
      M308 S0 P"bedtemp" Y"thermistor" T100000 B4138 ; configure sensor 0 as thermistor on pin bedtemp
      M950 H0 C"bedheat" T0 ; create bed heater output on bedheat and map it to sensor 0

      M140 H0 ; map heated bed to heater 0
      M143 H0 S120 ; set temperature limit for heater 0 to 120C
      M308 S1 P"e0temp" Y"thermistor" T100000 B4138 ; configure sensor 1 as thermistor on pin e0temp
      M950 H1 C"e0heat" T1 ; create nozzle heater output on e0heat and map it to sensor 1
      M307 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit
      M143 H1 S280 ; set temperature limit for heater 1 to 280C

      ; Fans
      M950 F0 C"fan0" Q500 ; create fan 0 on pin fan0 and set its frequency
      M106 P0 S0 H-1 ; set fan 0 value. Thermostatic control is turned off
      M950 F1 C"fan1" Q500 ; create fan 1 on pin fan1 and set its frequency
      M106 P1 S1 H1 T45 ; set fan 1 value. Thermostatic control is turned on

      ; 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 are not defined

      ; Miscellaneous
      M575 P1 S1 B57600 ; enable support for PanelDue
      M911 S10 R11 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; set voltage thresholds and actions to run on power loss
      0
      homeall.g
      ; called to home all axes
      ;
      ; generated by RepRapFirmware Configuration Tool v3.3.0 on Wed Aug 04 2021 15:38:43 GMT+0200 (centraleuropeisk sommartid)
      G91 ; relative positioning
      G1 H2 Z5 F6000 ; lift Z relative to current position
      G1 H1 X-235 Y-215 F1800 ; move quickly to X and Y axis endstops and stop there (first pass)
      G1 H2 X5 Y5 F6000 ; go back a few mm
      G1 H1 X-235 Y-215 F360 ; move slowly to X and Y axis endstops once more (second pass)
      G90 ; absolute positioning
      G1 X150 Y150 F6000 ; go to first bed probe point and home Z
      G30 ; home Z by probing the bed

      ; Uncomment the following lines to lift Z after probing
      ;G91 ; relative positioning
      ;G1 Z5 F100 ; lift Z relative to current position
      ;G90 ; absolute positioning

      ;
      ; generated by RepRapFirmware Configuration Tool v3.3.0 on Wed Aug 04 2021 15:38:43 GMT+0200 (centraleuropeisk sommartid)
      G91 ; relative positioning
      G1 H2 Z5 F6000 ; lift Z relative to current position
      G90 ; absolute positioning
      G1 X150 Y150 F6000 ; go to first probe point
      G30 ; home Z by probing the bed

      ; Uncomment the following lines to lift Z after probing
      ;G91 ; relative positioning
      ;G1 Z5 F100 ; lift Z relative to current position
      ;G90 ; absolute positioning

      Please can you who understand take a look and see where I have a mistake ???

      DIY-O-Sphereundefined fcwiltundefined Phaedruxundefined 3 Replies Last reply Reply Quote 0
      • DIY-O-Sphereundefined
        DIY-O-Sphere @Btj
        last edited by

        @btj said in Leveling issue:

        ; Endstops
        M574 X1 S1 P"xstop" ; X min active high endstop switch
        M574 Y1 S1 P"ystop" ; Y min active high endstop switch

        Add

        M574 Z1 S2                         ; configure Z-probe endstop for low end on Z
        

        Does the probe deploy/retract by sending M401/M402?

        (UTC+1)

        fcwiltundefined 1 Reply Last reply Reply Quote 0
        • fcwiltundefined
          fcwilt @DIY-O-Sphere
          last edited by

          @diy-o-sphere said in Leveling issue:

          Add

          M574 Z1 S2                         ; configure Z-probe endstop for low end on Z
          

          From the M574 docs:

          Snnn 1 = switch-type (eg microswitch) endstop input, 2 = Z probe (when used to home an axis other than Z), 3 = single motor load detection, 4 = multiple motor load detection (see Notes).

          Frederick

          Printers: a small Utilmaker style, a small CoreXY and a E3D MS/TC setup. Various hotends. Using Duet 3 hardware running 3.4.6

          DIY-O-Sphereundefined 1 Reply Last reply Reply Quote 0
          • fcwiltundefined
            fcwilt @Btj
            last edited by

            @btj

            Do you mean actual bed leveling via G32 or mesh compensation via G29.

            They are two very different things.

            Frederick

            Printers: a small Utilmaker style, a small CoreXY and a E3D MS/TC setup. Various hotends. Using Duet 3 hardware running 3.4.6

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

              Please only create a single thread for your issue. Spamming multiple threads won't get you help any faster and in fact will only slow things down. Your other threads have been locked.

              https://forum.duet3d.com/topic/24469/duet-2-wifi-firmware-ender5-plus/1
              https://forum.duet3d.com/topic/24482/leveling/1

              @btj said in Leveling issue:

              Do not make this machine level!

              Please describe what you're trying to accomplish and how you are trying to accomplish it as best you can.

              Can you post your config.g, homeall.g, homez.g, and bed.g if it exists?
              Can you post a sliced gcode file or at least the first 50 or so lines of it?
              Can you send M122 and M98 P"config.g" in the Gcode console in DWC and post the results?

              That should give us a much better idea of what is happening in your setup.

              There are different kinds of bed correction. Which one are you trying to do?

              https://duet3d.dozuki.com/Wiki/Setting_up_automatic_probing_of_the_print_bed
              https://duet3d.dozuki.com/Wiki/Using_mesh_bed_compensation
              https://duet3d.dozuki.com/Wiki/Bed_levelling_using_multiple_independent_Z_motors

              Z-Bot CoreXY Build | Thingiverse Profile

              1 Reply Last reply Reply Quote 0
              • DIY-O-Sphereundefined
                DIY-O-Sphere @fcwilt
                last edited by

                @fcwilt said in Leveling issue:

                2 = Z probe

                Thanks for the hint. This is what comes out of the configurator. Probably a leftover from RRF2. But I could not find any difference if S1 or S2 is used.
                For the homing of Z with a BLtouch it doesn't even matter if the line is present at all.

                (UTC+1)

                fcwiltundefined engikeneerundefined 2 Replies Last reply Reply Quote 0
                • fcwiltundefined
                  fcwilt @DIY-O-Sphere
                  last edited by

                  @diy-o-sphere said in Leveling issue:

                  @fcwilt said in Leveling issue:

                  2 = Z probe

                  For the homing of Z with a BLtouch it doesn't even matter if the line is present at all.

                  Correct. Yet since the configuration tool puts it there many folks have duplicated the "error" over and over.

                  One reason I don't use or like the configuration tool.

                  Frederick

                  Printers: a small Utilmaker style, a small CoreXY and a E3D MS/TC setup. Various hotends. Using Duet 3 hardware running 3.4.6

                  1 Reply Last reply Reply Quote 0
                  • engikeneerundefined
                    engikeneer @DIY-O-Sphere
                    last edited by

                    @diy-o-sphere said in Leveling issue:

                    @fcwilt said in Leveling issue:

                    2 = Z probe

                    Thanks for the hint. This is what comes out of the configurator. Probably a leftover from RRF2. But I could not find any difference if S1 or S2 is used.
                    For the homing of Z with a BLtouch it doesn't even matter if the line is present at all.

                    @Phaedrux - could you guys take a look at this in the config tool? 🙂 seen a few posts with this recently and it might be causing some confusion

                    E3D TC with D3Mini and Toolboards.
                    Home-built CoreXY, Duet Wifi, Chimera direct drive, 2x BMG, 300x300x300 build volume
                    i3 clone with a bunch of mods

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

                      @engikeneer said in Leveling issue:

                      @diy-o-sphere said in Leveling issue:

                      @fcwilt said in Leveling issue:

                      2 = Z probe

                      Thanks for the hint. This is what comes out of the configurator. Probably a leftover from RRF2. But I could not find any difference if S1 or S2 is used.
                      For the homing of Z with a BLtouch it doesn't even matter if the line is present at all.

                      @Phaedrux - could you guys take a look at this in the config tool? 🙂 seen a few posts with this recently and it might be causing some confusion

                      Well it doesn't really cause a problem. Consider it a placeholder that explains that a Z endstop isn't used and the probe is used instead. Which is correct even if the gcode command itself is superfluous.

                      So since it doesn't actually cause a problem and actually explains what is happening it's been a low priority to change. Plus that command can be edited by the user to add a Z endstop min or max with a small change.

                      Z-Bot CoreXY Build | Thingiverse Profile

                      fcwiltundefined 1 Reply Last reply Reply Quote 0
                      • fcwiltundefined
                        fcwilt @Phaedrux
                        last edited by

                        @phaedrux said in Leveling issue:

                        So since it doesn't actually cause a problem and actually explains what is happening it's been a low priority to change. Plus that command can be edited by the user to add a Z endstop min or max with a small change.

                        But the command is wrong - the documentation makes it clear that S2 does not apply to the Z axis yet the command specifies Z.

                        IMO, putting in a meaningless, wrong command is just... wrong.

                        And it leads to folks thinking they need to put it there and it appears over and over - and no matter how many times it appears it is still... wrong.

                        If a placeholder is needed it should be M574 Z0 meaning no Z endstop which is not... wrong.

                        😉

                        Frederick

                        Printers: a small Utilmaker style, a small CoreXY and a E3D MS/TC setup. Various hotends. Using Duet 3 hardware running 3.4.6

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

                          @fcwilt Fair enough. Again, low priority. An overhaul of the config tool is coming at some point.

                          Z-Bot CoreXY Build | Thingiverse Profile

                          fcwiltundefined 1 Reply Last reply Reply Quote 0
                          • fcwiltundefined
                            fcwilt @Phaedrux
                            last edited by

                            @phaedrux said in Leveling issue:

                            @fcwilt Fair enough. Again, low priority. An overhaul of the config tool is coming at some point.

                            It certainly doesn't get much lower in priority than that.

                            😉

                            Frederick

                            Printers: a small Utilmaker style, a small CoreXY and a E3D MS/TC setup. Various hotends. Using Duet 3 hardware running 3.4.6

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