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

New beta firmware 1.20beta8

Scheduled Pinned Locked Moved
Firmware installation
10
31
3.9k
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
    mchiriciuc
    last edited by 19 Nov 2017, 09:16

    @fma:

    David, I won't be able to test sensorless homing for CoreXY, as I need to replace my belt… If someone else can test it, and check than any of motors stall is detected, when moving along X or along Y (both motors turn in these directions)...

    I'm using sensorless homing on my CoreXY with 1.20beta7. Stalling is detected, but sometimes, instead of going to -x or -y, the move is executed in the opposite direction. After moving the head using the controls it gows in the right direction. I have not been able to replicate this behaviour. Other than this, stalling seems to be detected properly.

    This is my X home.g file content:

    ; Lift Z relative to current position
    G91
    G1 Z5 F6000
    G90

    M400 ; make sure everything has stopped before we make changes
    M913 X50 Y50 Z50 ; drop motor currents to 50%
    M574 X1 Y1 S3 ; set endstops to use motor stall
    M915 X Y S4 R0 F0 ; set X and Y to sensitivity 4, do nothing when stall, unfiltered
    G91 ; use relative positioning
    G1 S1 X-400 F4000 ; move left 400mm, stopping at the endstop
    G1 X5 ; move away from end
    G90 ; back to absolute positioning
    G92 X ; set new X home possition
    M400 ; make sure everything has stopped before we reset the motor currents
    M913 X100 Y100 Z100 ; motor currents back to 100%
    M574 X1 Y1 S0 ; Define active low and unused microswitches

    ; Lower Z again
    G91
    G1 Z-5 F6000
    G90

    I will test today 1.20beta8 in a few hours, I'll report if anything changes.

    Regarding the reset problem, I have been printing more then 24 hours without any reset or any other problems. I have a Duet Ethernet, not Wifi, so it might be wifi related?

    1 Reply Last reply Reply Quote 0
    • undefined
      zlowred
      last edited by 19 Nov 2017, 13:41

      I'm on Duet WiFi. Also, my printer is Delta, not CoreXY. The bug may be in Delta-specific code. Or something else specific to my configuration (sensors, heaters, motors…)

      1 Reply Last reply Reply Quote 0
      • undefined
        MrBlom
        last edited by 19 Nov 2017, 17:01

        i can comfirm the wrong direction on homing as mchiriciuc says (CoreXY )
        it happens sometimes but most of the times it works fine

        i have not yet upgrade to the latest FW will do that soon
        and do more test

        1 Reply Last reply Reply Quote 0
        • undefined
          fma
          last edited by 19 Nov 2017, 17:17

          I didn't notice that in beta7… But I was homing to max endstops.

          Frédéric

          1 Reply Last reply Reply Quote 0
          • undefined
            mchiriciuc
            last edited by 19 Nov 2017, 21:38

            I have printed all day with beta8. Works fine, except for this random homing direction inversion.
            No other issues detected so far by me.

            1 Reply Last reply Reply Quote 0
            • undefined
              dc42 administrators
              last edited by 19 Nov 2017, 22:26

              @mchiriciuc:

              @fma:

              David, I won't be able to test sensorless homing for CoreXY, as I need to replace my belt… If someone else can test it, and check than any of motors stall is detected, when moving along X or along Y (both motors turn in these directions)...

              I'm using sensorless homing on my CoreXY with 1.20beta7. Stalling is detected, but sometimes, instead of going to -x or -y, the move is executed in the opposite direction. After moving the head using the controls it gows in the right direction. I have not been able to replicate this behaviour. Other than this, stalling seems to be detected properly.

              This is my X home.g file content:

              ; Lift Z relative to current position
              G91
              G1 Z5 F6000
              G90

              M400 ; make sure everything has stopped before we make changes
              M913 X50 Y50 Z50 ; drop motor currents to 50%
              M574 X1 Y1 S3 ; set endstops to use motor stall
              M915 X Y S4 R0 F0 ; set X and Y to sensitivity 4, do nothing when stall, unfiltered
              G91 ; use relative positioning
              G1 S1 X-400 F4000 ; move left 400mm, stopping at the endstop
              G1 X5 ; move away from end
              G90 ; back to absolute positioning
              G92 X ; set new X home possition
              M400 ; make sure everything has stopped before we reset the motor currents
              M913 X100 Y100 Z100 ; motor currents back to 100%
              M574 X1 Y1 S0 ; Define active low and unused microswitches

              ; Lower Z again
              G91
              G1 Z-5 F6000
              G90

              I will test today 1.20beta8 in a few hours, I'll report if anything changes.

              Regarding the reset problem, I have been printing more then 24 hours without any reset or any other problems. I have a Duet Ethernet, not Wifi, so it might be wifi related?

              I suggest you remove this:

              G92 X ; set new X home possition

              and use parameter X-5 in your M208 S1 command to define the endstop position. I'm not sure it will fix the homing issue, but at least the printer won't think it is homed if the stall is not detected.

              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
                mchiriciuc
                last edited by 19 Nov 2017, 23:00

                The homing issue occurs an the G1 S1 X-400 F4000 command, so the G92 X should have nothing to do with it. I will go with your suggestion since is the better and safer way of doing this. Thank you.
                But, I think I have an ideea what is happening.
                Sometimes, a stall is detected when the motor accelerates and only the G1 X5 is executed (as far as movement is perceived by me).
                I will test this further, and report back.

                1 Reply Last reply Reply Quote 0
                • undefined
                  dc42 administrators
                  last edited by 19 Nov 2017, 23:55

                  Yes, that's entirely possible. You may need to increase the M915 S parameter, or reduce the acceleration.

                  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
                    DjDemonD
                    last edited by 19 Nov 2017, 23:57

                    Any thoughts on the probing issue DC? I only ask as the difference in results between firmware versions is so stark there has to be something going on? I've replicated that now on two different machines.

                    Simon. Precision Piezo Z-Probe Technology
                    www.precisionpiezo.co.uk
                    PT1000 cartridge sensors NOW IN, just attach to your Duet board directly!

                    1 Reply Last reply Reply Quote 0
                    • undefined
                      dc42 administrators
                      last edited by 20 Nov 2017, 00:09

                      @DjDemonD:

                      Any thoughts on the probing issue DC? I only ask as the difference in results between firmware versions is so stark there has to be something going on? I've replicated that now on two different machines.

                      Thanks for the reminder. I've made a note to look at it next week.

                      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
                        Forgvn77
                        last edited by 20 Nov 2017, 20:09

                        Just installed the 1.20beta8+1 and noticed right away that while printing my always on fan for my hot end is no longer always on. As the hot end moves, it revs up and down. The only change made to the printer was to update the firmware.

                        Velleman K8200, Geeetech G2S Pro (x2), Geeetech Rostock 301 retrofitted with Duet
                        Make A Difference!

                        1 Reply Last reply Reply Quote 0
                        • undefined
                          Forgvn77
                          last edited by 20 Nov 2017, 21:45

                          I worked the issue and determined it was a break in the fan connector or wiring somewhere that happened at the same time I updated the firmware. Checked further and found a broken ground wire at the board connector for the hot end fan.

                          Velleman K8200, Geeetech G2S Pro (x2), Geeetech Rostock 301 retrofitted with Duet
                          Make A Difference!

                          1 Reply Last reply Reply Quote 0
                          • undefined
                            okercho
                            last edited by 21 Nov 2017, 10:05

                            Question about the stall detection (I'm still in 1.19, so this is a theoretical question, not a bug report). I'm having issues since couple of prints ago with motors loosing steps, and of course, layer shifting. This is not happening always though. My suspect is that X carriage bushings has a problem, but I wasn't able to reproduce it, as it only happens from time to time.

                            Yesterday I was executing the mesh bed levelling, and I heard how the X carriage was stuck, and it checked twice the same point, assuming that it moved… Anyway, here my question, if the stall detection is enabled, and for any reason some steps are missed during the mesh bed levelling... what happens? is the procedure cancelled? it will home again and continue?

                            Regards

                            Okercho
                            Custom Prusa i3 Hephestos with Duet Wi-Fi
                            E3d V6 with Bondtech BMG DirectDrive and PrecisionPiezo Sensor
                            Rebuilding Hypercube Evolution

                            1 Reply Last reply Reply Quote 0
                            • undefined
                              dc42 administrators
                              last edited by 21 Nov 2017, 10:35

                              Currently, stall detection will only pause or rehome when you are printing from SD card.

                              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
                                okercho
                                last edited by 21 Nov 2017, 10:52

                                @dc42:

                                Currently, stall detection will only pause or rehome when you are printing from SD card.

                                Ok, thanks 🙂

                                Okercho
                                Custom Prusa i3 Hephestos with Duet Wi-Fi
                                E3d V6 with Bondtech BMG DirectDrive and PrecisionPiezo Sensor
                                Rebuilding Hypercube Evolution

                                1 Reply Last reply Reply Quote 0
                                • undefined
                                  dc42 administrators
                                  last edited by 22 Nov 2017, 21:20

                                  @DjDemonD:

                                  Any thoughts on the probing issue DC? I only ask as the difference in results between firmware versions is so stark there has to be something going on? I've replicated that now on two different machines.

                                  I just ran your file on my delta with the smart effector, and I added the results in a new column on your sheet. Looks OK to me. Probing speed is 1000mm/min, which is 16.7mm/sec or 16.7um/millisec. As the Z probe is only sampled once per millisecond, a range of commonly 15us and occasionally just over that is to be expected.

                                  I am running a later build than 1.20b8+1, so things may have changed.

                                  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
                                    DjDemonD
                                    last edited by 22 Nov 2017, 21:31

                                    Thanks for having a look David. And for appending the results. For now if I am using my corexy as a sensor test rig then I'll just flash 1.19 temporarily. I'll test with whatever the latest edge build is and see if the behaviour changes when they're released.

                                    Simon. Precision Piezo Z-Probe Technology
                                    www.precisionpiezo.co.uk
                                    PT1000 cartridge sensors NOW IN, just attach to your Duet board directly!

                                    1 Reply Last reply Reply Quote 0
                                    • undefined
                                      dc42 administrators
                                      last edited by 22 Nov 2017, 22:08

                                      btw in the next 1.20 beta there will be a new Z probe type 8, which is the same as type 5 without filtering, so faster response (no 1ms sampling). I've just tested it with your file again:

                                      x16 microstepping, F1000: 25 instances of -0.166mm, 5 instances of -0.171mm
                                      x32 microstepping, F1000: 1 instance of -0.158, 2 instances of -0.166, remainder -0.161 or -0.163.

                                      If you want to try this version, the Duet WiFi build is at https://www.dropbox.com/s/tr3be3v9o5iqxxa/DuetWiFiFirmware.bin?dl=0.

                                      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
                                        DjDemonD
                                        last edited by 22 Nov 2017, 23:08

                                        Thanks I will try it now, that sounds right up my street.

                                        Simon. Precision Piezo Z-Probe Technology
                                        www.precisionpiezo.co.uk
                                        PT1000 cartridge sensors NOW IN, just attach to your Duet board directly!

                                        1 Reply Last reply Reply Quote 0
                                        • undefined
                                          DjDemonD
                                          last edited by 22 Nov 2017, 23:37

                                          Probing is much more accurate now, thanks David this really helps, now that z-probes are a whole new league more accurate than before.

                                          Did have one heavy contact on kossel XL during autocal, just wanted to see if this more precise probing improves calibration, oddly it doesn't seem to make any difference (just goes to show we're getting more into the "physics" of these sensors, not the engineering, they're plenty accurate for 3D printing). Its quite reassuring from a sensor accuracy point of view that the calibration doesn't improve once you reach a certain level of accuracy, as the mechanics are not changing and the sensors are accurate enough.

                                          I'll try a few more (with lower motor current) and just see if it happens again. Interestingly my hotend temp shot up to 51 deg C when it crashed the bed, a wire had come loose.

                                          I'm finding my results at 1/32 less accurate than at 1/16th with interpolation.

                                          Simon. Precision Piezo Z-Probe Technology
                                          www.precisionpiezo.co.uk
                                          PT1000 cartridge sensors NOW IN, just attach to your Duet board directly!

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