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

Duet 2 Wifi rebooting/crashing during print

Scheduled Pinned Locked Moved Solved
Beta Firmware
crash firmware hardware
7
41
2.2k
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
    bwnance
    last edited by 8 Jan 2021, 21:53

    @hackinistrator Moved the board over and repositioned the berdair to be nowhere near the board... we shall see.

    undefined 1 Reply Last reply 12 Jan 2021, 08:13 Reply Quote 0
    • undefined
      hackinistrator @bwnance
      last edited by 12 Jan 2021, 08:13

      @bwnance
      so?

      undefined 1 Reply Last reply 12 Jan 2021, 21:05 Reply Quote 0
      • undefined
        bwnance @hackinistrator
        last edited by 12 Jan 2021, 21:05

        @hackinistrator haven't had a bunch of time, but i've run 3 dry runs so far with no issue - a pretty good sign.

        1 Reply Last reply Reply Quote 0
        • undefined
          dc42 administrators
          last edited by dc42 1 Dec 2021, 21:12 12 Jan 2021, 21:11

          Is the Berdair driven directly from a Duet heater output? If so then I suggest twisted pair wires between the two. Hand twisted will do.

          Have you connected a fast recovery flyback diode in parallel with the Berdair? The best place for it is on the motor terminals. Make sure you connect it the right way round!

          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 1 Reply Last reply 13 Jan 2021, 19:46 Reply Quote 0
          • undefined
            bwnance @dc42
            last edited by 13 Jan 2021, 19:46

            @dc42 the Berdair is connected directly to FAN0 -- i was under the impression that a flyback diode had been included on all the fan headers in recent board revisions - i might have misunderstood?

            undefined 1 Reply Last reply 27 Jan 2021, 09:19 Reply Quote 0
            • undefined
              bwnance
              last edited by 27 Jan 2021, 04:30

              @dc42 just got another crash -- should i have the berdair wired differently than i do now?

              m122
              === Diagnostics ===
              RepRapFirmware for Duet 2 WiFi/Ethernet version 3.2 running on Duet WiFi 1.02 or later
              Board ID: 08DJM-9178L-L2MSD-6J1FA-3S46N-KSFYP
              Used output buffers: 3 of 24 (11 max)
              === RTOS ===
              Static ram: 23460
              Dynamic ram: 72744 of which 24 recycled
              Never used RAM 15852, free system stack 191 words
              Tasks: NETWORK(ready,188) HEAT(blocked,307) MAIN(running,452) IDLE(ready,19)
              Owned mutexes: WiFi(NETWORK)
              === Platform ===
              Last reset 00:01:26 ago, cause: software
              Last software reset at 2021-01-26 23:27, reason: HardFault invState, GCodes spinning, available RAM 15608, slot 1
              Software reset code 0x4063 HFSR 0x40000000 CFSR 0x00020000 ICSR 0x0041f003 BFAR 0xe000ed38 SP 0x2001ffc0 Task NETW Freestk 31192 ok
              Stack: 400a4000 2000222c 00000003 00000001 200000ac ffffffed 00000000 200f000e 00000000 00f00000 e000ef34 c0000000 20004690 004548f5 0045465c 61000000 ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff
              Error status: 0x00
              Aux0 errors 0,0,0
              MCU temperature: min 25.0, current 25.3, max 26.1
              Supply voltage: min 24.0, current 24.1, max 24.2, under voltage events: 0, over voltage events: 0, power good: yes
              Driver 0: position 62532, standstill, SG min/max not available
              Driver 1: position 62532, standstill, SG min/max not available
              Driver 2: position 62532, standstill, SG min/max not available
              Driver 3: position 0, standstill, SG min/max not available
              Driver 4: position 0, standstill, SG min/max not available
              Driver 5: position 0
              Driver 6: position 0
              Driver 7: position 0
              Driver 8: position 0
              Driver 9: position 0
              Driver 10: position 0
              Driver 11: position 0
              Date/time: 2021-01-26 23:28:54
              Cache data hit count 106076577
              Slowest loop: 6.33ms; fastest: 0.20ms
              I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
              === Storage ===
              Free file entries: 10
              SD card 0 detected, interface speed: 20.0MBytes/sec
              SD card longest read time 1.0ms, write time 0.0ms, max retries 0
              === Move ===
              DMs created 83, maxWait 0ms, bed compensation in use: none, comp offset 0.000
              === MainDDARing ===
              Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
              === AuxDDARing ===
              Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
              === Heat ===
              Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
              === GCodes ===
              Segments left: 0
              Movement lock held by null
              HTTP is idle in state(s) 0
              Telnet is idle in state(s) 0
              File is idle in state(s) 0
              USB is idle in state(s) 0
              Aux is idle in state(s) 0
              Trigger is idle in state(s) 0
              Queue is idle in state(s) 0
              LCD is idle in state(s) 0
              Daemon is idle in state(s) 0
              Autopause is idle in state(s) 0
              Code queue is empty.
              === Network ===
              Slowest loop: 15.65ms; fastest: 0.00ms
              Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
              HTTP sessions: 1 of 8
              - WiFi -
              Network state is active
              WiFi module is connected to access point 
              Failed messages: pending 0, notready 0, noresp 0
              WiFi firmware version 1.25
              WiFi MAC address dc:4f:22:6e:6c:ca
              WiFi Vcc 3.43, reset reason Turned on by main processor
              WiFi flash size 4194304, free heap 19328
              WiFi IP address 192.168.86.20
              WiFi signal strength -36dBm, mode 802.11n, reconnections 0, sleep mode modem
              Clock register 00002002
              Socket states: 0 0 0 0 0 0 0 0
              1 Reply Last reply Reply Quote 0
              • undefined
                dc42 administrators @bwnance
                last edited by 27 Jan 2021, 09:19

                @bwnance said in Duet 2 Wifi rebooting/crashing during print:

                @dc42 the Berdair is connected directly to FAN0 -- i was under the impression that a flyback diode had been included on all the fan headers in recent board revisions - i might have misunderstood?

                We don't advise connecting a Berdair directly to a fan port. The starting current of the motor will exceed the peak rated current of the fan mosfet, causing it to fail after a while.

                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 1 Reply Last reply 3 Feb 2021, 22:33 Reply Quote 0
                • undefined
                  bwnance @dc42
                  last edited by 3 Feb 2021, 22:33

                  @dc42 I connected the EZ-Switch that the berdair comes with to an unused heater block + a fan header -- This appears to have solved the crashing issues.

                  Using any high PWM frequency after this ended up resulting in "all or nothing" fan control -- i dropped the frequency down to 20hz and that seems to have solved the issue, though.

                  1 Reply Last reply Reply Quote 0
                  • undefined
                    dc42 administrators
                    last edited by dc42 2 Apr 2021, 13:51 4 Feb 2021, 13:50

                    Thanks for the update! I'm glad the problem is solved. I'll mark this as solved, but feel free to un-mark it if the problem recurs.

                    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 1 Reply Last reply 5 Feb 2021, 20:17 Reply Quote 0
                    • undefined
                      bwnance @dc42
                      last edited by 5 Feb 2021, 20:17

                      @dc42 thank you so much for the support! I really appreciate it 🙂

                      1 Reply Last reply Reply Quote 0
                      • undefined
                        Robthide37
                        last edited by 16 Feb 2021, 12:00

                        @dc42 and @Phaedrux and @bwnance please correct me if i am wrong i am going to be adding my ez out switch now to as i was under the impression the 1 amp plus 50 percent for start was still ok for the mosfet on fan0 but anyway i plan on swithing to a brushless pump anyway as i found a kvp8 pump that flows a large amount and can run series or parallel.
                        I run berd air as well and two things the pump is very noisy it actually can make my camera get artifacts from the emi. Also if you remove the flux ring you will increase rpm as we are not running a high pressure system. Last why are you using a heater block oyu should be connecting 24v constant to the ez pwm board then use the fan output. The only time you would do what you listed would maybe be with a brushless motor that has built in controller and you wanted to run 3wire or try and run a 4 wire with tach but in that situation i would think you would use and endstop output to pwm control the brushless pump so that it only gets 5v unless you want to run all fans at 5v. I say that cause most things do not like the 24v pwm control signal.

                        1 Reply Last reply Reply Quote 0
                        • undefined
                          dc42 administrators
                          last edited by dc42 16 Feb 2021, 15:16

                          Brushed DC motors usually take much more than 50% extra current when starting. More like 500%. Brushless motor have much lower starting currents.

                          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 1 Reply Last reply 18 Feb 2021, 14:07 Reply Quote 0
                          • undefined
                            Robthide37 @dc42
                            last edited by 18 Feb 2021, 14:07

                            @dc42 Ohhh thankyou i did not know that i was just using the info from my generator and my well pump starting load vs running load lol

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