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

    Cannot print anymore

    Scheduled Pinned Locked Moved
    General Discussion
    8
    35
    4.3k
    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.
    • Zesty_Lykleundefined
      Zesty_Lykle
      last edited by

      Something weird is happening.
      When I switch the printer on and upload a file to print, the system warms up as expected and the moment it needs to print, the extruder motor starts going back and forth all the time and the browser disconnects with the msg: Internal server error.

      I was printing normally, printing file after file, uploaded the next file and then this happened. So rebooting did not help.
      Any ideas? Any way to generate an error log or something?

      Lykle
      Design, make and enjoy life

      Co Creator of the Zesty Nimble

      1 Reply Last reply Reply Quote 0
      • InSanityundefined
        InSanity
        last edited by

        Almost sounds like a power drop out. Have you checked your power connections, do you have a meter to test voltages ? Run M122 and see what the min / max voltages are. Kind of odd that it's heating ok..hmm.

        Edit: Possibly short that's drawing excessive current when the motors are energized causing a drop out ?

        Jeff

        Duet WiFi Powered FFCP with E3D legends hotend system. BLTouch grid leveling.

        1 Reply Last reply Reply Quote 0
        • ShadowXundefined
          ShadowX
          last edited by

          Can you manually heat up the hot end to extrusion temperature and then extrude a fix amount of filament from the PanelDue controller? It could be a loose or bad connection to your extruder motor. If you can home your printer, it means the X,Y,Z motors work fine on your delta machine.

          1 Reply Last reply Reply Quote 0
          • InSanityundefined
            InSanity
            last edited by

            The fact the browser connection drops out kind of makes me think power drop out perhaps caused by a short or excessive current draw the PSU just can't handle. So hard to tell with stuff you can't put your hands on.

            Jeff

            Duet WiFi Powered FFCP with E3D legends hotend system. BLTouch grid leveling.

            1 Reply Last reply Reply Quote 0
            • T3P3Tonyundefined
              T3P3Tony administrators
              last edited by

              Lykke

              Use M122 to see why the last reboot happened (ie was is softeare, power whatever).

              Also could it be the gcode file, something new in you start gcode that does something really odd?

              www.duet3d.com

              1 Reply Last reply Reply Quote 0
              • Zesty_Lykleundefined
                Zesty_Lykle
                last edited by

                Well, had a look, already tried the extrusion.
                That worked. But then, after I switched it on again to test that, so did the printing.
                So there is an intermittent fault that remains after a reboot.

                Shit, it happened again. And another symptom. My Macro's are not visible on the home page. I have to go to the macros page, they are all there. When I come back, they are refreshed and on my home page.
                It seems to be getting worse, now it tried to do a head crash.

                Looked at the power: Supply voltage: min 12.3, current 12.4, max 12.5, under voltage events: 0, over voltage events: 0

                Lykle
                Design, make and enjoy life

                Co Creator of the Zesty Nimble

                1 Reply Last reply Reply Quote 0
                • Zesty_Lykleundefined
                  Zesty_Lykle
                  last edited by

                  It is not a reboot. It is a full lock up. Only way to get a responsive system is by switching it off and on again.
                  One more thing I noticed. It only happens when I start a print. I can do extrudes, retracts, calibrations, doesn't matter.
                  It does not matter if I have preheated the bed and hot end or not.

                  It feels random, a file loads and prints, same file again loads and the printer jams.

                  My start gcode:
                  G28 ; home all axes
                  M80 ; lights on
                  M106 ; fan on
                  G1 E2

                  Currently printing. Some results of M122 while printing:
                  MCU temperature: min 36.0, current 37.2, max 40.1
                  Supply voltage: min 12.1, current 12.2, max 12.5, under voltage events: 0, over voltage events: 0

                  Lykle
                  Design, make and enjoy life

                  Co Creator of the Zesty Nimble

                  1 Reply Last reply Reply Quote 0
                  • dc42undefined
                    dc42 administrators
                    last edited by

                    If the extruder goes back and forth when it is trying to print, this could mean that you have sliced in relative coordinate mode (as recommended for RRF) but the printer is in absolute mode. Add M83 to your slicer start gcode.

                    One reason you may see this is that in RRF 1.17 and 1.17a, each input source has its own relative/absolute extruder setting. An unforseen consequence was that an M83 command in config.g to set relative extrusion was forgotten once config.g had completed. This is fixed in 1.17b.

                    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
                    • Zesty_Lykleundefined
                      Zesty_Lykle
                      last edited by

                      How would that explain the fact that a file prints perfectly and the next time I load the same file, it doesn't?
                      Also, I am running 1.17b
                      But I certainly will add M83 to the startup code. Thanks

                      Lykle
                      Design, make and enjoy life

                      Co Creator of the Zesty Nimble

                      1 Reply Last reply Reply Quote 0
                      • dc42undefined
                        dc42 administrators
                        last edited by

                        @Zesty_Lykle:

                        How would that explain the fact that a file prints perfectly and the next time I load the same file, it doesn't?
                        Also, I am running 1.17b
                        But I certainly will add M83 to the startup code. Thanks

                        Is that the next time you print the same file without restarting the Duet, or the next time after restarting the Duet?

                        Some slicers put M83 in the starting gcode themselves when you specify relative extrusion.

                        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
                        • Zesty_Lykleundefined
                          Zesty_Lykle
                          last edited by

                          Ah, OK.
                          I will test it out tomorrow and let you know.
                          Thanks

                          Lykle
                          Design, make and enjoy life

                          Co Creator of the Zesty Nimble

                          1 Reply Last reply Reply Quote 0
                          • Zatsitundefined
                            Zatsit
                            last edited by

                            Funny: Exactly the same problem, today at about the same time!

                            I was using version 1.17 downloaded on January 2 on a fresh DuetWifi.
                            Many successfull prints since, before suddenly the extruder went crazy at the beginning of an print (endless retracted-unretracted-retracted), then the DuetWebControl said "Communication error" and then died completely. Can not make it alive since: the page does not respond.

                            No power problems, no abnormal temperature. The red light next to the SD card is always on. I do not remember if it's normal or not …

                            I tried to switch to 1.17b, changing the bin files in the / sys directory of the SD card. No luck for now.

                            P.S.
                            I also can not access DuetWifi via USB.

                            The Windows drivers for the USB port that I downloaded (duet.inf and duetinf.cat) no longer work normally. Their re-installation results in the installation on the COM7 port of a component named "Bossa Program Port", and not "Duet 3DPrinter ...".

                            Examination of the "Bossa Program Port" shows that this is some Arduino stuff. What is that doing there? In any case, nothing good ...

                            As a result, I can not send any code to DuetWifi.

                            Any idea?

                            Creator of Zatsit, the delta printer with none assembly

                            1 Reply Last reply Reply Quote 0
                            • InSanityundefined
                              InSanity
                              last edited by

                              @Zatsit:

                              I tried to switch to 1.17b, changing the bin files in the / sys directory of the SD card. No luck at the moment.

                              The firmware sits in the flash memory of the controller, changing it on the SD card without also telling it to Flash the controller does nothing. I don't have the bin file in my sys folder or SD card as it does nothing once flashed.

                              Jeff

                              Duet WiFi Powered FFCP with E3D legends hotend system. BLTouch grid leveling.

                              1 Reply Last reply Reply Quote 0
                              • Dougal1957undefined
                                Dougal1957
                                last edited by

                                @Zatsit:

                                Funny: Exactly the same problem, today at about the same time!

                                I was using version 1.17 downloaded on January 2 on a fresh DuetWifi.
                                Many successfull prints since, before suddenly the extruder went crazy at the beginning of an print (endless retracted-unretracted-retracted), then the DuetWebControl said "Communication error" and then died completely. Can not make it alive since: the page does not respond.

                                No power problems, no abnormal temperature. The red light next to the SD card is always on. I do not remember if it's normal or not …

                                I tried to switch to 1.17b, changing the bin files in the / sys directory of the SD card. No luck for now.

                                P.S.
                                I also can not access DuetWifi via USB.

                                The Windows drivers for the USB port that I downloaded (duet.inf and duetinf.cat) no longer work normally. Their re-installation results in the installation on the COM7 port of a component named "Bossa Program Port", and not "Duet 3DPrinter ...".

                                Examination of the "Bossa Program Port" shows that this is some Arduino stuff. What is that doing there? In any case, nothing good ...

                                As a result, I can not send any code to DuetWifi.

                                Any idea?

                                If you are now seeing a bossa programing port it means you have erased the firmware you need to visit the emergency recovery section of the Wiki to get the info to recover your board.

                                1 Reply Last reply Reply Quote 0
                                • Zatsitundefined
                                  Zatsit
                                  last edited by

                                  It is possible that I pressed the "Erase" button by believing to press "Reset", during the abnormal behavior of the extruder.

                                  According to the documentation, this could corrupt or erase the firmware. Does this make sense?

                                  In this case, I have to apply "Backup procedure #3" specified in the documentation, right?

                                  P.S. Thanks Dougal1957 ! I will do that.
                                  I find it strange that it is as easy to erase the firmware …

                                  Creator of Zatsit, the delta printer with none assembly

                                  1 Reply Last reply Reply Quote 0
                                  • Zesty_Lykleundefined
                                    Zesty_Lykle
                                    last edited by

                                    To me it feels like a software problem. It is not just the extruder stepper going crazy, the web server crashes as well.
                                    It would be nice to be able to have some sort of error logging, so we can trace what is happening.
                                    I would be more than willing to run a debugging version, if it would help to figure this out.

                                    Lykle
                                    Design, make and enjoy life

                                    Co Creator of the Zesty Nimble

                                    1 Reply Last reply Reply Quote 0
                                    • Zatsitundefined
                                      Zatsit
                                      last edited by

                                      In my case, the web server probably crashed as a consequence of the fact that I probably pressed the "Erase" button. We do not have proof that he would have crashed if not …

                                      Creator of Zatsit, the delta printer with none assembly

                                      1 Reply Last reply Reply Quote 0
                                      • Zatsitundefined
                                        Zatsit
                                        last edited by

                                        After applying Backup # 3, everything is now normal. I can print from Wifi and from USB.

                                        It remains to understand the abnormal behavior of the extruder motor, but the key is that everything works again.

                                        Thank you to all of you !

                                        Creator of Zatsit, the delta printer with none assembly

                                        1 Reply Last reply Reply Quote 0
                                        • dc42undefined
                                          dc42 administrators
                                          last edited by

                                          @Zatsit:

                                          After applying Backup # 3, everything is now normal. I can print from Wifi and from USB.

                                          It remains to understand the abnormal behavior of the extruder motor, but the key is that everything works again.

                                          Thank you to all of you !

                                          The reason for the extruder problem is probably as I explained a few posts back here https://www.duet3d.com/forum/thread.php?pid=7011#p7011.

                                          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
                                          • Zesty_Lykleundefined
                                            Zesty_Lykle
                                            last edited by

                                            Things are getting worse. Adding M83 to the startup code messed up my prints.
                                            Removing it made things even worse. Now I cannot print at all any more, even when the file is accepted.
                                            It prints a little while and then the extruder shoots back to its previous positions. Net result, no filament coming out.

                                            I am switching back to 1.15 for now, but keeping the micro sd card intact, so I can still test if and when needed.

                                            Lykle
                                            Design, make and enjoy life

                                            Co Creator of the Zesty Nimble

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