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

    differences between manual and automatic leveling

    Scheduled Pinned Locked Moved
    IR Height Sensor
    10
    41
    2.5k
    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.
    • Gip_86undefined
      Gip_86 @Phaedrux
      last edited by Gip_86

      @fcwilt

      okay thank you for this information.
      I think i can update this weekend. but i'm not shure if it works, because i have tried it befor i have set up the machine abd i always got errors. If i update to 3.3, can i use the old config or should i do all new?
      (because i'm not so good writing these files)

      @phaedrux

      here is M122, (M98 will follow this day)

      m122
      === Diagnostics === 
      RepRapFirmware for Duet 2 WiFi/Ethernet version 2.03 running on Duet WiFi 1.02 or later 
      Board ID: 0JD0M-9P6M2-NWNS4-7J1FG-3S06R-9A0ZM 
      Used output buffers: 3 of 24 (16 max) 
      === RTOS === 
      Static ram: 25680 
      Dynamic ram: 93680 of which 380 recycled 
      Exception stack ram used: 604 
      Never used ram: 10728 
      Tasks: NETWORK(ready,524) HEAT(blocked,1236) MAIN(running,3780) IDLE(ready,160) 
      Owned mutexes:
      === Platform === 
      Last reset 09:34:28 ago, cause: software 
      Last software reset at 2021-09-15 21:44, reason: User, spinning module GCodes, available RAM 10792 bytes (slot 1) 
      Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d 
      Error status: 24 
      Free file entries: 9 
      SD card 0 detected, interface speed: 20.0MBytes/sec 
      SD card longest block write time: 511.5ms, max retries 0 
      MCU temperature: min 37.7, current 38.8, max 40.4 Supply voltage: min 23.8, current 24.2, max 24.5, under voltage events: 0, over voltage events: 0, power good: yes 
      Driver 0: ok, SG min/max 0/1023 
      Driver 1: ok, SG min/max 0/1023 
      Driver 2: standstill, SG min/max 0/1023 
      Driver 3: ok, SG min/max 0/1023 
      Driver 4: standstill, SG min/max not available 
      Date/time: 2021-09-16 07:19:21 
      Cache data hit count 4294967295 
      Slowest loop: 227.29ms; fastest: 0.07ms 
      I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
      === Move === 
      Hiccups: 0, FreeDm: 148, MinFreeDm: 124, MaxWait: 20085157ms Bed compensation in use: none, comp offset 0.000 
      === DDARing === 
      Scheduled moves: 21661, completed moves: 21621, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 
      === Heat === 
      Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1 
      Heater 0 is on, I-accum = 0.9 
      Heater 1 is on, I-accum = 0.4
      
      - WiFi – 
      Network state is running WiFi module is connected to access point Failed messages: pending 0, notready 0, noresp 0 
      WiFi firmware version 1.26 
      WiFi MAC address f4:cf:a2:ea:55:43 
      WiFi Vcc 3.36, reset reason Turned on by main processor 
      WiFi flash size 4194304, free heap 27016 
      WiFi IP address 192.168.0.84 
      WiFi signal strength -65dBm, reconnections 0, sleep mode unknown 
      Socket states: 0 0 0 0 0 0 0 0
      

      Yes i can confirm that my coordinate system is right handed. as you described.

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

        @gip_86

        Hi,

        There are changes that need to be made to use v3 firmware but they are not extensive.

        You could use the configuration utility to create a new set of configuration files.

        Or you can edit your existing files.

        I put off doing it for quite a while but I'm glad I finally did. Version 3 firmware has many good things.

        You cannot for from v2.x to v3.3. You have to go from 2.x to 3.0 and then from 3.0 to 3.3.

        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
        • zaptaundefined
          zapta
          last edited by

          When dealing with bed mesh, it useful to remember that what we measure is not just the characteristics of the bed but also all the errors between the bed and the sensor, including x,y,z mechanical system, head errors (e.g. does it sags and tilts) and error nozzle and the sensor (e.g. if the head tilts) and sensor errors (how accurate it is, is the bed surface compatible with it, etc).

          That's why we sometimes see measurement results that wouldn't make sense if we would measure the bed alone.

          Having some experience with HEVO, and it's motion mechanism tends to be soft (compared to more modern extrusion+rail based designs), especially the X rods, which are thinner (8mm?) and sag or cause head tilting. I would suggest to place the sensor to have zero y offest rather than zero x offset since this will cancel better the effect of head tilting.

          BTW, do you use two independent drivers for the Z motors? If you do, the Duet can do auto 'real' leveling between the two motor which is nice and reduces the compensation that the mesh need to do.

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

            Updating to 3.3 isn't that hard really, but it can be confusing if you're really used to the RRF2 way. I do recommend updating though, 2.03 is ~2 years old.

            If you still have access to DWC. Upload these 3 zip files, one at a time in the system tab. Don't extract them first. Reboot after each. Use M115 in the gcode console to verify the firmware has been applied.
            https://github.com/Duet3D/RepRapFirmware/releases/download/2.05.1/Duet2Firmware-2.05.1.zip
            https://github.com/Duet3D/RepRapFirmware/releases/download/3.0/Duet2and3Firmware-3.0.zip
            https://github.com/Duet3D/RepRapFirmware/releases/download/3.3/Duet2and3Firmware-3.3.zip
            That will get your firmware and DWC up to date.

            You can see the change logs here:
            https://github.com/Duet3D/RepRapFirmware/wiki/Changelog-RRF-3.x

            For your config, might be a good idea to run through the configurator tool and generate a fresh set for RRF3.
            https://configtool.reprapfirmware.org/Start

            Backup your existing config files in the sys folder in case you want to switch back to RRF2. It’s easy to switch back and forth, just upload the zip file for the version you want and then upload your config files.

            These documents will come in handy during the conversion.
            https://duet3d.dozuki.com/Wiki/RepRapFirmware_3_overview
            https://duet3d.dozuki.com/Wiki/Gcode

            Z-Bot CoreXY Build | Thingiverse Profile

            Gip_86undefined 1 Reply Last reply Reply Quote 1
            • Gip_86undefined
              Gip_86 @Phaedrux
              last edited by Gip_86

              @phaedrux

              ufff spent the 4 last hours to upgrade to 3.3. holy sh... nothing was working anymore. had to switchover to bossa.

              Now it works ok. but i get a heater fault. i will try to compare to my old config

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

                @gip_86 said in differences between manual and automatic leveling:

                @phaedrux

                ufff spent the 4 last hours to upgrade to 3.3. holy sh... nothing was working anymore. had to switchover to bossa.

                Now it works ok. but i get a heater fault. i will try to compare to my old config

                If you copy-and-paste your new config.g file here (using the </> tag) we can all pitch in and take a look.

                It's very likely just a syntax error.

                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

                Gip_86undefined 1 Reply Last reply Reply Quote 0
                • Gip_86undefined
                  Gip_86 @fcwilt
                  last edited by Gip_86

                  @fcwilt

                  so this is the new config. I hava adjusted all i see to fit with the old config

                  ; Configuration file for Duet WiFi (firmware version 3.3)
                  ; executed by the firmware on start-up
                  ;
                  ; generated by RepRapFirmware Configuration Tool v3.3.2 on Sat Sep 18 2021 02:15:19 GMT+0200 (Mitteleuropäische Sommerzeit)
                  
                  ; General preferences
                  G90                                            ; send absolute coordinates...
                  M83                                            ; ...but relative extruder moves
                  M550 P"HeVo"                                   ; set printer name
                  M669 K1                                        ; select CoreXY mode
                  
                  ; Network
                  M552 S1                                        ; enable network
                  M586 P0 S1                                     ; enable HTTP
                  M586 P1 S0                                     ; disable FTP
                  M586 P2 S0                                     ; disable Telnet
                  M575 P1 B57600 S1
                  
                  ; Drives
                  M569 P0 S1                                     ; physical drive 0 goes forwards
                  M569 P1 S1                                     ; physical drive 1 goes forwards
                  M569 P2 S1                                     ; physical drive 2 goes forwards
                  M569 P3 S1                                     ; physical drive 3 goes forwards
                  M584 X0 Y1 Z2 E3                               ; set drive mapping
                  M350 X16 Y16 Z16 E16 I1                        ; configure microstepping with interpolation
                  M92 X80.00 Y80.00 Z400.00 E396.00              ; set steps per mm
                  M566 X21000.00 Y21000.00 Z180.00 E54000.00     ; set maximum instantaneous speed changes (mm/min)
                  M203 X21000.00 Y21000.00 Z180.00 E300000.00    ; set maximum speeds (mm/min)
                  M201 X4000.00 Y4000.00 Z3000.00 E4000.00       ; set accelerations (mm/s^2)
                  M906 X1000 Y1000 Z1000 E800 I30                ; set motor currents (mA) and motor idle factor in per cent
                  M84 S30                                        ; Set idle timeout
                  
                  ; Axis Limits
                  M208 X0 Y0 Z-1 S1                               ; set axis minima
                  M208 X205 Y202 Z150 S0                         ; set axis maxima
                  
                  ; Endstops
                  M574 X2 S1 P"xstop"                            ; configure active-high endstop for high end on X via pin xstop
                  M574 Y2 S1 P"ystop"                            ; configure active-high endstop for high end on Y via pin ystop
                  M574 Z1 S2                                     ; configure Z-probe endstop for low end on Z
                  
                  ; Z-Probe
                  M558 P1 C"zprobe.in" H5 F120 T6000             ; set Z probe type to unmodulated and the dive height + speeds
                  G31 P500 X40 Y-35 Z2.04                          ; set Z probe trigger value, offset and trigger height
                  M557 X15:205 Y15:195 S20                       ; define mesh grid
                  
                  ; Heaters
                  M308 S0 P"bedtemp" Y"thermistor" T100000 B4400 ; 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
                  M307 H0 B0 S1.00                               ; disable bang-bang mode for the bed heater and set PWM limit
                  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 B4400  ; 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 F1 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 F0 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
                  
                  fcwiltundefined 1 Reply Last reply Reply Quote 0
                  • fcwiltundefined
                    fcwilt @Gip_86
                    last edited by

                    @gip_86

                    Hmm...

                    Everything seems correct.

                    When are you getting this fault?

                    What is the exact message your are seeing?

                    Thanks.

                    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

                    Gip_86undefined 1 Reply Last reply Reply Quote 0
                    • Gip_86undefined
                      Gip_86 @fcwilt
                      last edited by Gip_86

                      @fcwilt

                      hi Frederick

                      this is the message i got:

                      Error: Heater 0 fault: temperature rising much more slowly than the expected 1.3°C/sec
                      Resume state saved
                      Warning: Tool 0 was not driven because its heater temperatures were not high enough or it has a heater fault

                      Blacksheep99undefined 1 Reply Last reply Reply Quote 0
                      • Blacksheep99undefined
                        Blacksheep99 @Gip_86
                        last edited by

                        @gip_86 Have you run a PID tune of your extruder and bed?

                        Gip_86undefined 1 Reply Last reply Reply Quote 0
                        • Gip_86undefined
                          Gip_86 @Blacksheep99
                          last edited by Gip_86

                          @blacksheep99

                          yes i have one done for the heater and the bed.

                          Bed:
                          Warning: heater behaviour was not consistent during tuning
                          Auto tuning heater 0 completed after 4 idle and 25 tuning cycles in 5317 seconds. This heater needs the following M307 command:
                          M307 H0 B0 R0.957 C113.0 D6.66 S1.00 V24.2
                          Edit the M307 H0 command in config.g to match this. Omit the V parameter if the heater is not powered from VIN.

                          Heater:

                          M307 H1 B0 R2.746 C97.9:59.2 D5.41 S1.00 V24.2

                          one question:
                          after firmwareupdate now it takes very long to heat up the bed. is this normal?

                          Blacksheep99undefined 1 Reply Last reply Reply Quote 1
                          • Blacksheep99undefined
                            Blacksheep99 @Gip_86
                            last edited by

                            @gip_86 Have you got a config-override.g in your sys folder with the output of the tuning? You also need a M501 in your config.g if you do.

                            Gip_86undefined 1 Reply Last reply Reply Quote 1
                            • Gip_86undefined
                              Gip_86 @Blacksheep99
                              last edited by

                              @blacksheep99

                              no, i have put the M307 in config directly..

                              ; Heaters
                              M308 S0 P"bedtemp" Y"thermistor" T100000 B4400 ; 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
                              ;M307 H0 B0 S1.00                               
                              M307 H0 B0 R0.957 C113.0 D6.66 S1.00 V24.2	   ; disable bang-bang mode for the bed heater and set PWM limit
                              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 B4400  ; 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                               
                              M307 H1 B0 R2.746 C97.9:59.2 D5.41 S1.00 V24.2 ; disable bang-bang mode for heater  and set PWM limit
                              M143 H1 S280                                   ; set temperature limit for heater 1 to 280C
                              

                              if i put it in override, what have i to put in?
                              and in config should only M501?

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

                                @gip_86

                                It's perfectly fine to put everything in config.g

                                The config-override.g file is just to make it a bit easier as a M500 after certain operations makes the needed entries in config-override.g.

                                I have never used config-override.g - I move the contents to config.g and delete config-override.g

                                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

                                Gip_86undefined 1 Reply Last reply Reply Quote 0
                                • Gip_86undefined
                                  Gip_86 @fcwilt
                                  last edited by

                                  @fcwilt

                                  after pid tuning i have decided to add "R4700 behind the M308.

                                  Now bed has heated really fast. Is there something agains R4700? I had this thing in my old config.

                                  Now it looks like:

                                  M308 S0 P"bedtemp" Y"thermistor" T100000 B4400 R4700
                                  M308 S1 P"e0temp" Y"thermistor" T100000 B4400 R4700

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

                                    @gip_86 said in differences between manual and automatic leveling:

                                    @fcwilt

                                    after pid tuning i have decided to add "R4700 behind the M308.

                                    Now bed has heated really fast. Is there something agains R4700? I had this thing in my old config.

                                    Now it looks like:

                                    M308 S0 P"bedtemp" Y"thermistor" T100000 B4400 R4700
                                    M308 S1 P"e0temp" Y"thermistor" T100000 B4400 R4700

                                    Well the R setting is supposed to match the values of the resistors on your board.

                                    If you don't have a R setting it is supposed to default to the correct values for your board.

                                    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

                                    Gip_86undefined 1 Reply Last reply Reply Quote 0
                                    • Gip_86undefined
                                      Gip_86 @fcwilt
                                      last edited by Gip_86

                                      @fcwilt

                                      Ok, machine is now running as aspected (but without mesh compensation)

                                      I also have designed a new holder for the probe.

                                      93795E95-F1FE-4F2A-A746-918B541B058B.jpeg

                                      A1C16F5A-1137-4B9F-AAF5-47BAB2640695.jpeg

                                      0E0D7CD5-EF38-42D9-AF88-B5EA3406593A.jpeg

                                      So and what are the best steps for next?

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

                                        @gip_86 said in differences between manual and automatic leveling:

                                        So and what are the best steps for next?

                                        Have you made the configuration settings needed to use the Manual Bed Leveling Assistant?

                                        Manual Bed Leveling Assistant

                                        Once that is done and the bed is level you should then proceed to get Mesh Bed Compensation working.

                                        Mesh Bed Compensation

                                        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

                                        Gip_86undefined 1 Reply Last reply Reply Quote 0
                                        • Gip_86undefined
                                          Gip_86 @fcwilt
                                          last edited by Gip_86

                                          @fcwilt
                                          ok i had done the neeed config and have leveled it. after several leveling, best i could do was about 0,03mm to adjust.

                                          then i had done a G29 and heres the height map:

                                          3850a325-a4e5-4402-a4f2-e08e425a578f-image.png

                                          1d4c2091-f1ec-4bff-a350-f0747dadf08c-image.png

                                          Any idears?

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

                                            @gip_86

                                            I have four different printers all with cast aluminum tool plate for the bed and they all are different.

                                            I haven't taken the time to find out why as they all print ok.

                                            FT5 Height Map.jpg

                                            MF1 Height Map.jpg

                                            SAFPRO Height Map.jpg

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

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