Duet3D Logo

    Duet3D

    • Register
    • Login
    • Search
    • Categories
    • Tags
    • Documentation
    • Order

    Software reset whilst printing in SBC mode - Beta 3.2-1

    Hardware dev
    3
    6
    156
    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.
    • jay_s_uk
      jay_s_uk last edited by jay_s_uk

      Printing for the first time with the mini 5+ with an SBC attached. This is mainly due to the issue with the internal SD card.

      I suffered a reset. Below is the M122 output.

      === Diagnostics ===
      RepRapFirmware for Duet 3 Mini 5+ version 3.2-beta1 running on Duet 3 Mini5plus WiFi (SBC mode)
      Board ID: 8ULVP-1D6P9-F65J0-401FQ-2A03Z-RJW1V
      Used output buffers: 1 of 40 (10 max)
      === RTOS ===
      Static ram: 85692
      Dynamic ram: 105584 of which 44 recycled
      Exception stack ram used: 224
      Never used ram: 70600
      Tasks: HEAT(blocked,321) TMC(blocked,63) MAIN(running,557) IDLE(ready,20) AIN(blocked,267)
      Owned mutexes:
      === Platform ===
      Last reset 00:36:40 ago, cause: software
      Last software reset at 2020-10-02 20:19, reason: StuckInSpinLoop, GCodes spinning, available RAM 69708, slot 2
      Software reset code 0x4083 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0400f80f BFAR 0xe000ed38 SP 0x20007954 Task MAIN
      Stack: 00000940 0002e412 010f0000 3f800000 401c0000 3edb6db7 b6376c00 3e4c6bb0 b202d445 44fa76c6 44fa76c6 00000000 447a76c6 447a76c6 3e4c6bb1 3ca38959 3bb9135a 3f800000 3f800000 20000011 a5a5a5a5 2001a710 2001c448 91752604 a5a5a5a5 a5a5a5a5 a5a5a5a5
      Error status: 0x020
      Supply voltage: min 0.0, current 12.6, max 12.6, under voltage events: 0, over voltage events: 0, power good: yes
      Driver 0: position 0, standstill, read errors 0, write errors 1, ifcnt 17, reads 52032, writes 10, timeouts 0, DMA errors 0
      Driver 1: position 0, standstill, read errors 0, write errors 1, ifcnt 17, reads 51224, writes 10, timeouts 808, DMA errors 0, failedOp 0x06
      Driver 2: position 0, standstill, read errors 0, write errors 1, ifcnt 17, reads 52006, writes 10, timeouts 26, DMA errors 0, failedOp 0x6f
      Driver 3: position 0, standstill, read errors 0, write errors 1, ifcnt 17, reads 52031, writes 10, timeouts 0, DMA errors 0
      Driver 4: position 0, standstill, read errors 0, write errors 1, ifcnt 13, reads 52032, writes 10, timeouts 0, DMA errors 0
      Driver 5: position 0, assumed not present
      Driver 6: position 0, assumed not present
      Driver 7: position 0, assumed not present
      Date/time: 2020-10-02 20:56:57
      Slowest loop: 2.89ms; fastest: 0.08ms
      === Storage ===
      Free file entries: 10
      SD card 0 not detected, interface speed: 11.2MBytes/sec
      SD card longest read time 0.0ms, write time 0.0ms, max retries 0
      === Move ===
      Hiccups: 0(0), FreeDm: 169, MinFreeDm: 169, MaxWait: 0ms
      Bed compensation in use: none, comp offset 0.000
      === MainDDARing ===
      Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0  CDDA state: -1
      === AuxDDARing ===
      Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0  CDDA state: -1
      === Heat ===
      Bed heaters = 0 -1, chamberHeaters = -1 -1
      Heater 1 is on, I-accum = 0.0
      === GCodes ===
      Segments left: 0
      Movement lock held by null
      HTTP* is ready with "M122" 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
      SBC is idle in state(s) 0
      Daemon* is idle in state(s) 0
      Aux2 is idle in state(s) 0
      Autopause is idle in state(s) 0
      Code queue is empty.
      === Network ===
      Slowest loop: 0.00ms; fastest: 5726623.00ms
      Responder states:
      HTTP sessions: 0 of 8
      - WiFi -
      Network state is disabled
      WiFi module is disabled
      Failed messages: pending 2779096485, notready 2779096485, noresp 2779096485
      Socket states: 0 0 0 0 0 0 0 0
      === SBC interface ===
      State: 0, failed transfers: 0
      Last transfer: 11ms ago
      RX/TX seq numbers: 42795/4463
      SPI underruns 0, overruns 0
      Number of disconnects: 0
      Buffer RX/TX: 0/0-0
      === Duet Control Server ===
      Duet Control Server v3.2.0-beta1+1
      Code buffer space: 4096
      Configured SPI speed: 8000000 Hz
      Full transfers per second: 31.68
      

      Edit: I'm using the ribbon cable from my duet 3

      Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is

      1 Reply Last reply Reply Quote 0
      • jay_s_uk
        jay_s_uk last edited by

        I removed daemon.g and was able to get through a print.
        Here are the contents of it.

        if {state.status == "idle"}
        	M42 P0 S0
        else 
        	M42 P0 S1
        

        Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is

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

          I've put a new build with improved (I hope) SD card error recovery at https://www.dropbox.com/s/4mtjx1oo73nwv69/Duet3Firmware_Mini5plus_v02.uf2?dl=0. Please try it carefully. Currently I work with the version 0.4 prototype, and I test the build for the version 0.2 prototype only occasionally.

          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 1
          • jay_s_uk
            jay_s_uk last edited by

            I've installed this build and it no longer connect in SBC mode.
            I'll move the sd card and try it in standalone

            Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is

            chrishamm 1 Reply Last reply Reply Quote 0
            • chrishamm
              chrishamm administrators @jay_s_uk last edited by

              @jay_s_uk The latest RRF version requires DSF 3.2-b2 because the SPI protocol has slightly changed. I hope we can release that on Monday.

              Duet software engineer

              jay_s_uk 1 Reply Last reply Reply Quote 0
              • jay_s_uk
                jay_s_uk @chrishamm last edited by

                @chrishamm thanks for letting me know. I'll move to standalone and then test again when the next beta is released

                Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is

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