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

Cant get my nozzle close to bed at all when trying to print

Scheduled Pinned Locked Moved
Tuning and tweaking
5
78
7.0k
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
    T3P3Tony administrators @Puppet172
    last edited by T3P3Tony 7 Apr 2018, 12:43 4 Jul 2018, 12:42

    @puppet172 said in Cant get my nozzle close to bed at all when trying to print:

    Its hard to tell though because the easiest way to tell it to see if i can connect to the DWC but since that then turns off the Wifi part i cant tell but its not doing the on off part as far as i can see because it stays connected to the printer

    The M587 only needs to be issued one - to add the SSID. the SSID (and password) is then stored on the Duet until you ask the Duet to forget it.

    Comment out M587 then try the SD card back in the Duet and see if it will boot without resetting.

    Normally M587 would not cause the Duet to reset but if that is the line that is causing the reset then thats the place to start.

    www.duet3d.com

    undefined 1 Reply Last reply 4 Jul 2018, 13:40 Reply Quote 0
    • undefined
      Puppet172 @T3P3Tony
      last edited by 4 Jul 2018, 13:40

      @t3p3tony @dc42 @Phaedrux
      even if i have that commented out it is still reseting and i changed the text setting to the ones above and i got this

      === Diagnostics ===
      RepRapFirmware for Duet 2 WiFi/Ethernet version 2.01beta1(RTOS) running on Duet WiFi 1.02 or later + DueX5
      Board ID: 08DDM-9FAM2-LW4S4-6J9D8-3SD6J-T3S7X
      Used output buffers: 1 of 20 (12 max)
      === RTOS ===
      Static ram: 28452
      Dynamic ram: 95912 of which 0 recycled
      Exception stack ram used: 256
      Never used ram: 6452
      Tasks: NETWORK(ready,1372) HEAT(blocked,1256) MAIN(running,3644)
      Mutexes: FilamentSensors(null) DHT(null) WiFi(null) TelnetGCodeReply(null) HttpGCodeReply(null) Telnet(null) HTTP(null) SD1(null) SD0(null) DirSearch(null) FileSystem(null) Aux(null) USB(null) MessageBox(null) ToolList(null) SPI(null) Malloc(null) NetworkGCodeInput(null) NetworkGCodeInput(null) FileInfoParser(null)
      === Platform ===
      Last reset 00:00:48 ago, cause: reset button or watchdog
      Last software reset details not available
      Error status: 0
      Free file entries: 10
      SD card 0 detected, interface speed: 20.0MBytes/sec
      SD card longest block write time: 0.0ms
      MCU temperature: min 136.1, current 136.8, max 138.1
      Supply voltage: min 0.2, current 0.2, max 0.3, under voltage events: 0, over voltage events: 0
      Driver 0: ok, SG min/max not available
      Driver 1: ok, SG min/max not available
      Driver 2: ok, SG min/max not available
      Driver 3: ok, SG min/max not available
      Driver 4: ok, SG min/max not available
      Driver 5: ok, SG min/max not available
      Driver 6: ok, SG min/max not available
      Driver 7: ok, SG min/max not available
      Driver 8: ok, SG min/max not available
      Driver 9: ok, SG min/max not available
      Expansion motor(s) stall indication: yes
      Date/time: 1970-01-01 00:00:00
      Slowest loop: 172.25ms; fastest: 0.07ms
      === Move ===
      Hiccups: 0, StepErrors: 0, LaErrors: 0, FreeDm: 240, MinFreeDm 240, MaxWait: 0ms, Underruns: 0, 0
      Scheduled moves: 0, completed moves: 0
      Bed compensation in use: mesh
      Bed probe heights: 0.000 0.000 0.000 0.000 0.000
      === Heat ===
      Bed heaters = -1 -1 -1 -1, chamberHeaters = -1 -1
      === GCodes ===
      Segments left: 0
      Stack records: 1 allocated, 0 in use
      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
      serial is ready with "M122" in state(s) 0
      aux is idle in state(s) 0
      daemon is idle in state(s) 0
      queue is idle in state(s) 0
      autopause is idle in state(s) 0
      Code queue is empty.
      === Network ===
      Slowest loop: 0.00ms; fastest: 4581298.50ms
      Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
      HTTP sessions: 0 of 8

      • WiFi -
        Network state is running
        WiFi module is connected to access point
        Failed messages: pending 0, notready 0, noresp 0
        WiFi firmware version 1.21
        WiFi MAC address 60:01:94:73:5a:d2
        WiFi Vcc 2.67, reset reason Turned on by main processor
        WiFi flash size 4194304, free heap 17184
        WiFi IP address 192.168.1.10
        WiFi signal strength -55dBm, reconnections 0, sleep mode modem
        Socket states: 0 0 0 0 0 0 0 0
        === Expansion ===
        DueX I2C errors 0
        ok
      undefined 1 Reply Last reply 4 Jul 2018, 14:59 Reply Quote 0
      • undefined
        Puppet172
        last edited by 4 Jul 2018, 13:41

        @T3P3Tony @dc42 @Phaedrux
        This is also with The M587 Commented out

        1 Reply Last reply Reply Quote 0
        • undefined
          dc42 administrators
          last edited by 4 Jul 2018, 13:59

          I think the problem is that you are supplying USB power only, and when the WiFi module tries to connect, your USB power source is cutting out because of the increased current demand.

          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 4 Jul 2018, 14:10 Reply Quote 0
          • undefined
            Puppet172 @dc42
            last edited by 4 Jul 2018, 14:10

            @dc42
            It happens when i have my 12v power on too i can send it with the power supply on.
            === Diagnostics ===
            RepRapFirmware for Duet 2 WiFi/Ethernet version 2.01beta1(RTOS) running on Duet WiFi 1.02 or later + DueX5
            Board ID: 08DDM-9FAM2-LW4S4-6J9D8-3SD6J-T3S7X
            Used output buffers: 1 of 20 (1 max)
            === RTOS ===
            Static ram: 28452
            Dynamic ram: 95912 of which 0 recycled
            Exception stack ram used: 300
            Never used ram: 6408
            Tasks: NETWORK(ready,1408) HEAT(blocked,1256) MAIN(running,3628)
            Mutexes: FilamentSensors(null) DHT(null) WiFi(null) TelnetGCodeReply(null) HttpGCodeReply(null) Telnet(null) HTTP(null) SD1(null) SD0(null) DirSearch(null) FileSystem(null) Aux(null) USB(null) MessageBox(null) ToolList(null) SPI(null) Malloc(null) NetworkGCodeInput(null) NetworkGCodeInput(null) FileInfoParser(null)
            === Platform ===
            Last reset 00:00:37 ago, cause: power up
            Last software reset details not available
            Error status: 0
            Free file entries: 10
            SD card 0 detected, interface speed: 20.0MBytes/sec
            SD card longest block write time: 0.0ms
            MCU temperature: min 44.6, current 67.1, max 67.1
            Supply voltage: min 12.3, current 12.4, max 12.5, under voltage events: 0, over voltage events: 0
            Driver 0: standstill, SG min/max not available
            Driver 1: standstill, SG min/max not available
            Driver 2: standstill, SG min/max not available
            Driver 3: standstill, SG min/max not available
            Driver 4: standstill, SG min/max not available
            Driver 5: standstill, SG min/max not available
            Driver 6: standstill, SG min/max not available
            Driver 7: standstill, SG min/max not available
            Driver 8: standstill, SG min/max not available
            Driver 9: standstill, SG min/max not available
            Expansion motor(s) stall indication: no
            Date/time: 1970-01-01 00:00:00
            Slowest loop: 1.09ms; fastest: 0.07ms
            === Move ===
            Hiccups: 0, StepErrors: 0, LaErrors: 0, FreeDm: 240, MinFreeDm 240, MaxWait: 0ms, Underruns: 0, 0
            Scheduled moves: 0, completed moves: 0
            Bed compensation in use: mesh
            Bed probe heights: 0.000 0.000 0.000 0.000 0.000
            === Heat ===
            Bed heaters = -1 -1 -1 -1, chamberHeaters = -1 -1
            === GCodes ===
            Segments left: 0
            Stack records: 1 allocated, 0 in use
            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
            serial is ready with "M122" in state(s) 0
            aux is idle in state(s) 0
            daemon is idle in state(s) 0
            queue is idle in state(s) 0
            autopause is idle in state(s) 0
            Code queue is empty.
            === Network ===
            Slowest loop: 14.21ms; fastest: 0.01ms
            Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
            HTTP sessions: 0 of 8

            • WiFi -
              Network state is running
              WiFi module is connected to access point
              Failed messages: pending 0, notready 0, noresp 0
              WiFi firmware version 1.21
              WiFi MAC address 60:01:94:73:5a:d2
              WiFi Vcc 3.17, reset reason Turned on by main processor
              WiFi flash size 4194304, free heap 17184
              WiFi IP address 192.168.1.10
              WiFi signal strength -62dBm, reconnections 0, sleep mode modem
              Socket states: 0 0 0 0 0 0 0 0
              === Expansion ===
              DueX I2C errors 0
            undefined 1 Reply Last reply 4 Jul 2018, 15:30 Reply Quote 0
            • undefined
              T3P3Tony administrators @Puppet172
              last edited by T3P3Tony 7 Apr 2018, 15:00 4 Jul 2018, 14:59

              @puppet172 said in Cant get my nozzle close to bed at all when trying to print:

              MCU temperature: min 136.1, current 136.8, max 138.1

              This is worrying. can you confirm you have nothing plugged into the Duet other than the USB/12V power. That temperature, if it continued to rise, would cause the MCU thermal protection to kick in.

              www.duet3d.com

              1 Reply Last reply Reply Quote 0
              • undefined
                dc42 administrators @Puppet172
                last edited by 4 Jul 2018, 15:30

                @puppet172, is the main processor chip really getting hot?

                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 4 Jul 2018, 15:40 Reply Quote 0
                • undefined
                  Puppet172 @dc42
                  last edited by 4 Jul 2018, 15:40

                  @dc42
                  The wifi chip is definitly hot. the main chip on the board is warm but its not hot like the Wifi Chip

                  1 Reply Last reply Reply Quote 0
                  • undefined
                    dc42 administrators
                    last edited by 4 Jul 2018, 15:47

                    Is the 3.3V regulator chip U2 also getting hot?

                    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 4 Jul 2018, 15:47 Reply Quote 0
                    • undefined
                      Puppet172 @dc42
                      last edited by 4 Jul 2018, 15:47

                      @dc42
                      Where is that located?

                      undefined 1 Reply Last reply 4 Jul 2018, 17:25 Reply Quote 0
                      • undefined
                        Puppet172
                        last edited by 4 Jul 2018, 15:57

                        @T3P3Tony
                        I have motors and ends stops and a hotend and just some regular 3d printing stuff but thats the only stuff plugged into the board.

                        1 Reply Last reply Reply Quote 0
                        • undefined
                          T3P3Tony administrators @Puppet172
                          last edited by T3P3Tony 7 Apr 2018, 17:25 4 Jul 2018, 17:25

                          @puppet172 said in Cant get my nozzle close to bed at all when trying to print:

                          @dc42
                          Where is that located?

                          alt text

                          Its this one:

                          0_1530725103973_67d53f99-0d45-4b26-bfec-2bd481c597a2-image.png

                          @puppet172 said in Cant get my nozzle close to bed at all when trying to print:

                          I have motors and ends stops and a hotend and just some regular 3d printing stuff but thats the only stuff plugged into the board.

                          Can you try with nothing plugged in other than USB.

                          www.duet3d.com

                          undefined 1 Reply Last reply 4 Jul 2018, 17:26 Reply Quote 0
                          • undefined
                            Puppet172 @T3P3Tony
                            last edited by 4 Jul 2018, 17:26

                            @t3p3tony
                            Yes just give me a couple min to unplug everything and im going to check if it gets hot one everything is unplugged

                            1 Reply Last reply Reply Quote 0
                            • undefined
                              Puppet172
                              last edited by 4 Jul 2018, 17:39

                              @T3P3Tony @dc42
                              When nothing is plugged into the board but the USB it does not get hot but when the 12v is applied it does get hot

                              1 Reply Last reply Reply Quote 0
                              • undefined
                                dc42 administrators
                                last edited by 4 Jul 2018, 17:52

                                If you comment out the M552 command in config.g so that the WiFi module stays disabled, does everything remain cool and does YAT remain connected? If so then perhaps just the WiFi module is faulty.

                                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 4 Jul 2018, 18:33 Reply Quote 0
                                • undefined
                                  Puppet172 @dc42
                                  last edited by 4 Jul 2018, 18:33

                                  @dc42
                                  the wifi module gets warm even when commented out but it still disconnects it seems when ever i send a command and then after a while of sittin there it will time out on its own and just disconnect

                                  undefined 1 Reply Last reply 4 Jul 2018, 19:01 Reply Quote 0
                                  • undefined
                                    T3P3Tony administrators @Puppet172
                                    last edited by 4 Jul 2018, 19:01

                                    @puppet172 thanks for the report. can you monitor the MCU temperature (repeated M122 calls over YAT). with just USB plugged in.

                                    www.duet3d.com

                                    undefined 1 Reply Last reply 4 Jul 2018, 19:20 Reply Quote 0
                                    • undefined
                                      Puppet172 @T3P3Tony
                                      last edited by Puppet172 7 Jun 2018, 00:17 4 Jul 2018, 19:20

                                      @t3p3tony @dc42

                                      Not Reliably because i get get the command output to pop up every once in a while but its kinda dependant on luck and perfect timing it seems because as i send the command it kinda disconnects then recconects
                                      @T3P3Tony

                                      1 Reply Last reply Reply Quote 0
                                      • undefined
                                        Puppet172
                                        last edited by 7 Jul 2018, 01:52

                                        @dc42 @T3P3Tony

                                        Hi, so as it looks now the board still does the same thing and i have been able to get and different outcomes
                                        So am i gonna need to get new boards?
                                        Since i bought it on the 21 of February this year would it be covered under warranty?
                                        Thanks

                                        undefined 1 Reply Last reply 8 Jul 2018, 10:49 Reply Quote 0
                                        • undefined
                                          T3P3Tony administrators @Puppet172
                                          last edited by 8 Jul 2018, 10:49

                                          @puppet172 yes, please contact who you bought the board from and reference this thread.

                                          www.duet3d.com

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