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

Firmware 2.03beta2 available

Scheduled Pinned Locked Moved
Firmware installation
25
86
12.1k
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.
  • undefined
    adri84dj
    last edited by 24 Mar 2019, 09:35

    Hi. So far, I've been with firmware 2.02 RC3 in my Kossel.

    When I calibrated the bed with G32 with calibration factor 8, after two passes, I had some 0.05mm measurements, the difference between each measured point, and the first layer was very good

    I have updated to the latest version, 2.03 beta 2, and when doing the G32 calibration several times, I get disparate measurements between the measured points of up to 0.2mm. Now the first layers are uneven in different parts of the bed.

    Have I missed something? Has anything changed in this latest firmware?

    Thanks and best regards

    1 Reply Last reply Reply Quote 0
    • undefined
      dc42 administrators
      last edited by 24 Mar 2019, 10:27

      There has been no intentional change in this area. There might have been an unintentional change because the code that handles endstop corrections has changed. Can you revert to 2.02 and check whether the new firmware really is to blame?

      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

      undefined 2 Replies Last reply 24 Mar 2019, 11:28 Reply Quote 0
      • undefined
        adri84dj @dc42
        last edited by 24 Mar 2019, 11:28

        @dc42

        Okay. I go back to 2.02 and try it later.

        Thank you

        1 Reply Last reply Reply Quote 0
        • undefined
          adri84dj @dc42
          last edited by 24 Mar 2019, 11:55

          @dc42 said in Firmware 2.03beta2 available:

          There has been no intentional change in this area. There might have been an unintentional change because the code that handles endstop corrections has changed. Can you revert to 2.02 and check whether the new firmware really is to blame?

          Hello,

          With the 2.02 final it works correctly again, as in 2.02 RC3.

          At least in my case there is something weird about 2.03 Beta 2.

          1 Reply Last reply Reply Quote 0
          • undefined
            dc42 administrators
            last edited by 25 Mar 2019, 09:34

            I've found a bug which might explain the problem, if you don't home the printer between auto calibration and printing. So please try 2.03beta3 when i release it. Meanwhile, homing between auto calibration and printing should work around the bug, assuming that your homing switches have reproducible trigger heights.

            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

            undefined undefined 2 Replies Last reply 25 Mar 2019, 10:19 Reply Quote 0
            • undefined
              AlexLin @dc42
              last edited by 25 Mar 2019, 10:19

              @dc42 does only apply to G32 or also to G29 mesh calibration?

              undefined 1 Reply Last reply 25 Mar 2019, 10:33 Reply Quote 1
              • undefined
                dc42 administrators @AlexLin
                last edited by 25 Mar 2019, 10:33

                @alexlin said in Firmware 2.03beta2 available:

                @dc42 does only apply to G32 or also to G29 mesh calibration?

                Only to delta auto calibration.

                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

                1 Reply Last reply Reply Quote 0
                • undefined
                  adri84dj @dc42
                  last edited by 25 Mar 2019, 20:29

                  @dc42 said in Firmware 2.03beta2 available:

                  I've found a bug which might explain the problem, if you don't home the printer between auto calibration and printing. So please try 2.03beta3 when i release it. Meanwhile, homing between auto calibration and printing should work around the bug, assuming that your homing switches have reproducible trigger heights.

                  In agreement. When beta 3 is available, I try it. Thank you.

                  1 Reply Last reply Reply Quote 0
                  • undefined
                    dc42 administrators
                    last edited by 25 Mar 2019, 21:04

                    Beta 3 is available now.

                    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

                    undefined 2 Replies Last reply 26 Mar 2019, 22:19 Reply Quote 0
                    • undefined
                      adri84dj @dc42
                      last edited by 26 Mar 2019, 22:19

                      @dc42 said in Firmware 2.03beta2 available:

                      Beta 3 is available now.

                      In agreement. I'll try it this weekend.
                      Thank you

                      1 Reply Last reply Reply Quote 0
                      • undefined
                        adri84dj @dc42
                        last edited by 27 Mar 2019, 21:08

                        @dc42 said in Firmware 2.03beta2 available:

                        Beta 3 is available now.

                        Hello,

                        It is already tested and in beta 3 it works correctly again.

                        Thanks and best regards

                        1 Reply Last reply Reply Quote 0
                        • undefined
                          brunofporto
                          last edited by brunofporto 28 Mar 2019, 02:25

                          When running G29 now the printer is using the nozzle reference and my z probe is out of the bed area. But when showing the map it thinks it was the probe at the nozzle position.

                          undefined 1 Reply Last reply 28 Mar 2019, 08:59 Reply Quote 0
                          • undefined
                            dc42 administrators @brunofporto
                            last edited by 28 Mar 2019, 08:59

                            @brunofporto said in Firmware 2.03beta2 available:

                            When running G29 now the printer is using the nozzle reference and my z probe is out of the bed area. But when showing the map it thinks it was the probe at the nozzle position.

                            The only change should be that if you run G29 within a system macro file (for example, bed.g) then tool offsets will be applied., whereas in firmware 2.02 they are not. But Z probe offsets are always applied by G29. Are you using tool offsets?

                            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

                            undefined 2 Replies Last reply 28 Mar 2019, 13:46 Reply Quote 0
                            • undefined
                              brunofporto @dc42
                              last edited by 28 Mar 2019, 13:46

                              @dc42 Not using any tool offsets. The only offset is the z-probe defined at the z-probe configuration line.

                              Pretty sure it is putting the nozzle exactly where it should be the probe when I send a G29 - needed to change some parameters to make sure the probe is over the bed but the height map shows as the nozzle position is where the probe took the measurement.

                              1 Reply Last reply Reply Quote 0
                              • undefined
                                brunofporto @dc42
                                last edited by 28 Mar 2019, 13:47

                                @dc42 ps.: just realized that I post at the wrong thread! I am using the beta3! 😄

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