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

    Pause during bed heat wait Hard Fault

    Scheduled Pinned Locked Moved Unsolved
    STM
    4
    6
    327
    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.
    • guerty25undefined
      guerty25
      last edited by

      Duet Web Control 2.0.4
      Board: Duet WiFi 1.02 or later
      Firmware: RepRapFirmware for Duet 2 WiFi/Ethernet 2.05 (2019-12-13b1)
      Duet WiFi Server Version: 1.23

      I may have discovered a bug while attempting to install a filament sensor. I'm using a simple mechanical switch that didn't quite close its contacts after I had loaded some new filament. When I tried to start a job, my printer kept restarting. I checked the error code and it gave me a hard fault from spinning module GCodes. I commented out the filament sensor in config.g and tried again with no issues. I then tried to reproduce the fault without the sensor so I did a M190 S60, started a job, and then paused the print from the DWC. This too caused the same hard fault.

      M122:

      === Platform ===
      Last reset 00:00:11 ago, cause: software
      Last software reset at 2020-07-31 17:24, reason: Hard fault, spinning module GCodes, available RAM 11588 bytes (slot 1)
      Software reset code 0x4033 HFSR 0x40000000 CFSR 0x00008200 ICSR 0x0441f803 BFAR 0x487b72ca SP 0x200048cc Task 0x4e49414d
      Stack: 0041b6ab 00400576 61000000 20009ee8 20003258 20004af4 20008a10 00000010 00000073 200049bc 00000000 00000000 0044cd25 00000000 00000000 00000000 e000ed04 a5a5a5a5 ffffffed 00000055 65646f63 6f632f73 2000ba90
      Error status: 0

      Phaedruxundefined 1 Reply Last reply Reply Quote 0
      • Phaedruxundefined
        Phaedrux Moderator @guerty25
        last edited by

        @guerty25 said in Pause during bed heat wait Hard Fault:

        I commented out the filament sensor in config.g and tried again with no issues.

        How did you have it configured in config.g?

        Z-Bot CoreXY Build | Thingiverse Profile

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

          Please update the firmware to 2.05.1 and see whether it still happens.

          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

          guerty25undefined 1 Reply Last reply Reply Quote 0
          • guerty25undefined
            guerty25 @Phaedrux
            last edited by

            @Phaedrux

            M591 D0 P2 C3 S1 		      	   ; Filament Sensor (Extruder0)
            

            I still got the hard fault after commenting this out and manually performing the same steps through the console and UI.

            1 Reply Last reply Reply Quote 0
            • guerty25undefined
              guerty25 @dc42
              last edited by

              @dc42 Still occurs in 2.05.1

              Steps to reproduce:.

              1. Create .gcode with M190 SXX
              2. Start job
              3. Pause job

              Result:

              === Platform ===
              Last reset 00:01:18 ago, cause: software
              Last software reset at 2020-08-01 09:33, reason: Hard fault, spinning module GCodes, available RAM 11628 bytes (slot 1)
              Software reset code 0x4033 HFSR 0x40000000 CFSR 0x00008200 ICSR 0x0041f803 BFAR 0x487b76ca SP 0x200046dc Task 0x4e49414d
              Stack: 0041b6ab 00400576 61000000 00000000 00000000 00000000 00000000 40240000 00000001 00000000 004531f5 0044e1a3 0044e0eb 00000306 0044c3c5 0044c3c4 41000000 200134e8 00419b5f 00000001 00000000 2000a0ac 2000ba90

              1 Reply Last reply Reply Quote 0
              • A Former User?
                A Former User
                last edited by A Former User

                I think I experienced the same in 2.05.1 as well but chalked it up do noobishness in actually using the firmware to print. Maestro board, delta kinematics and ATX supply, no sensors at except mechanical endstops. (edit: it threw an error each time we canceled a job during pre-heating, which required us to first pause then stop the job, and issuing M562 to try again)

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