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

    Gcode file corruption

    Scheduled Pinned Locked Moved
    General Discussion
    4
    8
    985
    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.
    • MortarArtundefined
      MortarArt
      last edited by

      I'm experiencing an issue with my Duet Wifi while repeatedly printing the same file. After a random amount of prints, the printer will stop communicating with Web Control, and stop printing. The LCD shows that the heaters are still operating, but control of the printer via the LCD panel does nothing.

      Turning the printer off, and then on again regains control.

      If I print the same file again, it fails in the same spot.

      If I upload the file again, from my PC, it prints successfully.

      1 Reply Last reply Reply Quote 0
      • elmoretundefined
        elmoret
        last edited by

        Sounds like a bad SD card. Have you tried a new one?

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

          As Tim says, it could be a bad SD card, or one that has been corrupted and has cross-linked clusters - although the types of SD card error I can think of shouldn't cause loss of control.

          If it happens again, try sending M122 from DWC, because it bypasses the gcode queue. Save the report if you get one. The Emergency Stop command also bypasses the gcode queue.

          After restarting, download the file back to the PC. Then compare the downloaded version with the original that you uploaded.

          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
          • MortarArtundefined
            MortarArt
            last edited by

            I've been uploading the file with each print as a work around, and so far I haven't had another failure, but I'll run the same file a few times until I have another one, to try and compare them.

            On the last failure, I noticed that in the console on the panel, it said that it could not read the file.

            Also will try another SD card…

            1 Reply Last reply Reply Quote 0
            • MortarArtundefined
              MortarArt
              last edited by

              Had a failure approximately 20% of the way into the print.

              Original file size was 999kb. Downloaded file after restart was 240kb.

              1 Reply Last reply Reply Quote 0
              • MortarArtundefined
                MortarArt
                last edited by

                Just had a failure on a larger file, in the first attempt at printing. 3.2mb, as uploaded. 0.8mb downloaded after the failure.

                1 Reply Last reply Reply Quote 0
                • MortarArtundefined
                  MortarArt
                  last edited by

                  Additional point of concern, which may be unrelated entirely to the Duet; I've had a different SD card fail repeatedly now with Octoprint. Not sure why I've got so many bad SD cards, but it might not be a coincidence.

                  1 Reply Last reply Reply Quote 0
                  • deckingmanundefined
                    deckingman
                    last edited by

                    I'm a bit confused by all the uploading/downloading comments. Are you uploading the file to the SD card, then printing from the SD card, or are you doing something different?

                    Ian
                    https://somei3deas.wordpress.com/
                    https://www.youtube.com/@deckingman

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