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

    duet3d 3.3 delta calibtating problems after fimware update

    Scheduled Pinned Locked Moved
    Using Duet Controllers
    5
    12
    306
    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.
    • ololenokundefined
      ololenok
      last edited by

      Greatings!
      I've recently updated my firmware from 1.2 to 3.3 (yeah, it was a challenge after 2 year of usage)
      After the update I have one unsolved problem:
      the printer calibrates nicely, builds mesh grid nicely, prints nicely. BUT after reboot it cant make a first layer.
      The nozzle touches the bed on one side and has a gap of a few mm on the other side. Never had such a problem before update.

      Looks like it ignores all the mesh grid and calibrations made. But the the mesh grid is definitely on: "DMs created 83, maxWait 0ms, bed compensation in use: mesh, comp offset 0.000"


      That's the result of m98:
      M98 P"config.g"
      HTTP is enabled on port 80
      FTP is disabled
      TELNET is disabled
      Warning: the height map was loaded when the current Z=0 datum was not determined probing. This may result in a height offset.
      Warning: Heater 0 appears to be over-powered. If left on at full power, its temperature is predicted to reach 298C
      Warning: Heater 1 appears to be over-powered. If left on at full power, its temperature is predicted to reach 681C


      That's my homedelta.g:
      G91 ; relative positioning
      G1 H1 X350 Y350 Z350 F1800 ; move all towers to the high end stopping at the endstops (first pass)
      G1 H2 X-5 Y-5 Z-5 F1800 ; go down a few mm
      G1 H1 X10 Y10 Z10 F360 ; move all towers up once more (second pass)
      G90 ; absolute positioning

      Config.g and current config-override.g and bed.g are attached.

      Any ideas? Maybe downgrade to some v2 will be ok?
      Thank you in advance!

      config-override.g config.g bed.g

      engikeneerundefined 1 Reply Last reply Reply Quote 0
      • ololenokundefined
        ololenok
        last edited by

        By the way, that's the video of first layer before reboot: https://www.youtube.com/watch?v=ZWKCwwZ0Bz8

        1 Reply Last reply Reply Quote 0
        • jay_s_ukundefined
          jay_s_uk
          last edited by

          @ololenok here are the files easier to read
          config.g

          ; Configuration file for Duet WiFi (firmware version 3.3)
          ; executed by the firmware on start-up
          ;
          ; generated by RepRapFirmware Configuration Tool v3.3.10 on Sat Jan 29 2022 23:54:53 GMT+0200 (Восточная Европа, стандартное время)
          
          ; General preferences
          M575 P1 S1 B57600                                  ; enable support for PanelDue
          G90                                                ; send absolute coordinates...
          M83                                                ; ...but relative extruder moves
          M550 P"Oloprint"                                   ; set printer name
          ;M665 L322.000:325.662:319.857 R130.135 H275.281 B130.0     ; Set delta radius, diagonal rod length, printable radius and homed height
          ;M666 X0 Y0 Z0                                      ; put your endstop adjustments here, or let auto calibration find them
          M665 L322.000:325.662:319.857 R130.132 H278.910 B130.0 X-1.006 Y-0.612 Z0.000
          M666 X0.644 Y-1.835 Z1.191 A0.00 B0.00
          
          ; 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 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 Z80.00 E420.00                   ; set steps per mm
          M566 X1200.00 Y1200.00 Z1200.00 E1200.00           ; set maximum instantaneous speed changes (mm/min)
          M203 X18000.00 Y18000.00 Z18000.00 E4800.00        ; set maximum speeds (mm/min)
          M201 X1000.00 Y1000.00 Z1000.00 E1000.00           ; set accelerations (mm/s^2)
          M906 X1400 Y1400 Z1400 E800 I30                    ; set motor currents (mA) and motor idle factor in per cent
          M84 S30                                            ; Set idle timeout
          
          ; Axis Limits
          M208 Z0 S1                                         ; set minimum Z
          
          ; Endstops
          M574 X1 S1 P"xstop"                                ; configure switch-type (e.g. microswitch) endstop for low end on X via pin xstop
          M574 Y1 S1 P"ystop"                                ; configure switch-type (e.g. microswitch) endstop for low end on Y via pin ystop
          M574 Z1 S1 P"zstop"                                ; configure switch-type (e.g. microswitch) endstop for low end on Z via pin zstop
          
          ; Z-Probe
          M558 P5 C"!^e0stop" H5 F120 T6000 I1               ; set Z probe type to switch and the dive height + speeds
          G31 P500 X0 Y0 Z0.182                              ; set Z probe trigger value, offset and trigger height
          M557 R85 S20                                       ; define mesh grid
          
          ; 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
          ;M307 H0 B1 S1.00                                   ; enable bang-bang mode for the bed heater and set PWM limit
          M307 H0 R0.805 C340.143:340.143 D4.58 S1.00 V24.3 B0 I0
          M140 H0                                            ; map heated bed to heater 0
          M143 H0 S130                                       ; set temperature limit for heater 0 to 130C
          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
          M307 H1 R2.371 C277.016:267.141 D5.28 S1.00 V24.2 B0 I0
          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
          ;M579 X0.9966 Y1.0176  		                      ; set scaling
          G29 S1    	                 					    ; Enable mesh compensation
          M911 S21 R23 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; set voltage thresholds and actions to run on power loss
          M501                                               ; load saved parameters from non-volatile memory
          T0
          

          config-override

          ; config-override.g file generated in response to M500 at 2022-01-31 23:12
          ; This is a system-generated file - do not edit
          ; Delta parameters
          M665 L322.000:325.662:319.857 R130.132 H278.910 B130.0 X-1.006 Y-0.612 Z0.000
          M666 X0.644 Y-1.835 Z1.191 A0.00 B0.00
          ; Heater model parameters
          M307 H0 R0.805 C340.143:340.143 D4.58 S1.00 V24.3 B0 I0
          M307 H1 R2.371 C277.016:267.141 D5.28 S1.00 V24.2 B0 I0
          ; Workplace coordinates
          G10 L2 P1 X0.00 Y0.00 Z0.00
          G10 L2 P2 X0.00 Y0.00 Z0.00
          G10 L2 P3 X0.00 Y0.00 Z0.00
          G10 L2 P4 X0.00 Y0.00 Z0.00
          G10 L2 P5 X0.00 Y0.00 Z0.00
          G10 L2 P6 X0.00 Y0.00 Z0.00
          G10 L2 P7 X0.00 Y0.00 Z0.00
          G10 L2 P8 X0.00 Y0.00 Z0.00
          G10 L2 P9 X0.00 Y0.00 Z0.00
          

          bed.g

          ; bed.g
          ; called to perform automatic delta calibration via G32
          ;
          ; generated by RepRapFirmware Configuration Tool v3.3.10 on Sat Jan 29 2022 23:54:53 GMT+0200 (Восточная Европа, стандартное время)
          M561 ; clear any bed transform
          ; Probe the bed at 3 peripheral and 3 halfway points, and perform 6-factor auto compensation
          ; Before running this, you should have set up your Z-probe trigger height to suit your build, in the G31 command in config.g.
          ;M913 X30 Y30 Z30 ; set X Y Z motors to 50% of their normal current DELETE IT!!!!
          G30 P0 X0 Y84.9 H0 Z-99999
          G30 P1 X73.53 Y-42.45 H0 Z-99999
          G30 P2 X-73.53 Y-42.45 H0 Z-99999
          G30 P3 X0 Y42.4 H0 Z-99999
          G30 P4 X36.72 Y-21.2 H0 Z-99999
          G30 P5 X-36.72 Y-21.2 H0 Z-99999
          G30 P6 X0 Y0 H0 Z-99999 S6
          ; Use S-1 for measurements only, without calculations. Use S4 for endstop heights and Z-height only. Use S6 for full 6 factors
          ; If your Z probe has significantly different trigger heights depending on XY position, adjust the H parameters in the G30 commands accordingly. The value of each H parameter should be (trigger height at that XY position) - (trigger height at centre of bed)
          

          Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is

          jay_s_ukundefined 1 Reply Last reply Reply Quote 0
          • jay_s_ukundefined
            jay_s_uk @jay_s_uk
            last edited by

            M665 L322.000:325.662:319.857

            @ololenok so the first question is do you really have arms/rods on your delta that are 3 different lengths?
            i suspect not, which makes this line very wrong.

            secondly, you shouldn't have G29 S1 in your config as you shouldn't be loading the heightmap until after the printer has been homed.

            your endstops are set at being at the lower end, they should be at the higher end. Change X1 to X2 in M574 and so on.

            Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is

            ololenokundefined 1 Reply Last reply Reply Quote 0
            • ololenokundefined
              ololenok @jay_s_uk
              last edited by

              @jay_s_uk
              Thank you so much for your reply!

              • The rod lengths are the same, but looks like the printer xyz tower distance is not the same (the build is not very accurate, my fault, firs project higher than 70cm). So I've made different rod length in config to compensate geometry while calibrating it with test prints.

              • where should I place G29 S1 to auto-load it each time the printer boots? Looks like it is the thing that's causing the problem...

              cosmowaveundefined jay_s_ukundefined 2 Replies Last reply Reply Quote 0
              • cosmowaveundefined
                cosmowave @ololenok
                last edited by

                @ololenok i think you can add your G29 at the end of your homing file (home delta) if you'd like to load the heightmap after every homing...

                Mankati FSXT+, DeltaTowerV2, E3D MS/TC

                ololenokundefined 1 Reply Last reply Reply Quote 0
                • ololenokundefined
                  ololenok @cosmowave
                  last edited by

                  @cosmowave
                  I'll check it today, thank you.
                  I just thought it would cause an error since the homing is not finished an that moment (the whole homing script is not finished still and mesh load command is in it)

                  1 Reply Last reply Reply Quote 0
                  • jay_s_ukundefined
                    jay_s_uk @ololenok
                    last edited by

                    @ololenok as @cosmowave says or use start.g or put it in your start gcode after homing the machine

                    Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is

                    1 Reply Last reply Reply Quote 0
                    • engikeneerundefined
                      engikeneer @ololenok
                      last edited by

                      @ololenok said in duet3d 3.3 delta calibtating problems after fimware update:

                      Warning: the height map was loaded when the current Z=0 datum was not determined probing. This may result in a height offset.

                      Likely this is part of your issue. You should do a single G30 at the center of your bed to set the z=0 datum before creating your heightmap (I think you missed this?), and before loading the heightmap to avoid an offset.

                      As the others said, you shouldn't load your heightmap until after the printer is homed etc. If you do a delta calibration with a heightmap loaded, it will mess up the calibration as they two things will fight each other

                      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

                      ololenokundefined 2 Replies Last reply Reply Quote 0
                      • ololenokundefined
                        ololenok @engikeneer
                        last edited by

                        @engikeneer , looks like the firmware behaviour has changed a lot since v1.21 (it worked fine on that version). Also the config generator gave some very raw results for v3.3, like strange homedelta.g with movements after homing that lead to additional problems.

                        I'll clean up that mess and test everything.

                        Thank you for reply.

                        Phaedruxundefined 1 Reply Last reply Reply Quote 0
                        • ololenokundefined
                          ololenok @engikeneer
                          last edited by

                          @engikeneer @cosmowave @jay_s_uk
                          Thank you guys for your time! Everything is working fine now.
                          (changed endstop types, moved G29 to start.g, making by hands G30 before mesh grid creation)

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

                            @ololenok said in duet3d 3.3 delta calibtating problems after fimware update:

                            Also the config generator gave some very raw results for v3.3, like strange homedelta.g with movements after homing that lead to additional problems.

                            That's likely a result of mistakenly having it set to low end endstops at the beginning.

                            Z-Bot CoreXY Build | Thingiverse Profile

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