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

    Config.g not read at startup, Printer does not start

    Scheduled Pinned Locked Moved
    Firmware installation
    2
    4
    182
    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.
    • Philippe71undefined
      Philippe71
      last edited by Philippe71

      After an RRF3 3.01 RC7 Update on Duet3 6HC + 3HC,
      The printer does not boot anymore.
      When powering on, the machine do nothing, no home, nothing
      It look like the config.g is not read. and DWC does not start

      Trying 3 differents SD CARD (Kingston, Integral and Sandisk)

      SD CARD are FAT32

      Note the same SDCARD works on a other 6HC board !

      It is the same problem than my post
      https://forum.duet3d.com/topic/14158/duet-3-6hc-does-not-ping

      I can connect by USB with a terminal and send the network command :
      M552 S1 P192.168.0.74/24
      M554 P192.168.0.1
      M586 P0 S1
      M586 P2 S1 R23

      Then the Printer ping

      A connection with the browser gives message
      "Your Duet rejected the HTTP request: page not found
      Check that the SD card is mounted and has the correct files in its /www folder
      "
      There is the lastest DWC in the /www folder (2.1.2)

      M39 gives
      Error: M39: No SD card mounted in slot 0

      M21 gives
      Error: M21: Cannot initialise SD card 0: Card is unusable

      M122 gives
      18:07:58.028 -> === Diagnostics ===
      18:07:58.028 -> RepRapFirmware for Duet 3 MB6HC version 3.01-RC7 running on Duet 3 MB6HC v0.6 or 1.0
      18:07:58.028 -> Board ID: 08DJM-956L2-G43S4-6JKD6-3SN6T-KU6YH
      18:07:58.028 -> Used output buffers: 1 of 40 (13 max)
      18:07:58.028 -> === RTOS ===
      18:07:58.028 -> Static ram: 154580
      18:07:58.028 -> Dynamic ram: 160560 of which 20 recycled
      18:07:58.028 -> Exception stack ram used: 376
      18:07:58.028 -> Never used ram: 77680
      18:07:58.028 -> Tasks: ETHERNET(blocked,444) NETWORK(ready,276) HEAT(blocked,1412) CanReceiv(suspended,3412) CanSender(suspended,1484) CanClock(blocked,1432) TMC(blocked,216) MAIN(running,4524) IDLE(ready,80)
      18:07:58.028 -> Owned mutexes:
      18:07:58.028 -> === Platform ===
      18:07:58.028 -> Last reset 00:16:43 ago, cause: power up
      18:07:58.028 -> Last software reset at 2020-04-14 15:15, reason: User, spinning module GCodes, available RAM 75968 bytes (slot 1)
      18:07:58.028 -> Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x04437000 BFAR 0x00000000 SP 0xffffffff Task 0x4e49414d
      18:07:58.028 -> Error status: 0
      18:07:58.028 -> Free file entries: 10
      18:07:58.028 -> SD card 0 detected, interface speed: 0.2MBytes/sec
      18:07:58.028 -> SD card longest block write time: 0.0ms, max retries 0
      18:07:58.028 -> MCU temperature: min 27.8, current 29.6, max 29.8
      18:07:58.028 -> Supply voltage: min 23.8, current 23.8, max 23.9, under voltage events: 0, over voltage events: 0, power good: yes
      18:07:58.028 -> 12V rail voltage: min 12.0, current 12.1, max 12.1, under voltage events: 0
      18:07:58.028 -> Driver 0: standstill, reads 37298, writes 0 timeouts 0, SG min/max not available
      18:07:58.028 -> Driver 1: standstill, reads 37298, writes 0 timeouts 0, SG min/max not available
      18:07:58.028 -> Driver 2: standstill, reads 37297, writes 0 timeouts 0, SG min/max not available
      18:07:58.028 -> Driver 3: standstill, reads 37298, writes 0 timeouts 0, SG min/max not available
      18:07:58.028 -> Driver 4: standstill, reads 37297, writes 0 timeouts 0, SG min/max not available
      18:07:58.028 -> Driver 5: standstill, reads 37298, writes 0 timeouts 0, SG min/max not available
      18:07:58.028 -> Date/time: 2020-04-14 18:08:01
      18:07:58.028 -> Slowest loop: 88.23ms; fastest: 0.14ms
      18:07:58.028 -> === Move ===
      18:07:58.028 -> Hiccups: 0(0), FreeDm: 375, MinFreeDm: 375, MaxWait: 0ms
      18:07:58.028 -> Bed compensation in use: none, comp offset 0.000
      18:07:58.028 -> === MainDDARing ===
      18:07:58.028 -> Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 CDDA state: -1
      18:07:58.028 -> === AuxDDARing ===
      18:07:58.028 -> Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 CDDA state: -1
      18:07:58.028 -> === Heat ===
      18:07:58.028 -> Bed heaters = -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
      18:07:58.028 -> === GCodes ===
      18:07:58.028 -> Segments left: 0
      18:07:58.028 -> Movement lock held by null
      18:07:58.028 -> HTTP is idle in state(s) 0
      18:07:58.028 -> Telnet is idle in state(s) 0
      18:07:58.028 -> File is idle in state(s) 0
      18:07:58.028 -> USB is ready with "m122" in state(s) 0
      18:07:58.028 -> Aux is idle in state(s) 0
      18:07:58.028 -> Trigger
      is idle in state(s) 0 0, running macro
      18:07:58.028 -> Queue is idle in state(s) 0
      18:07:58.028 -> LCD is idle in state(s) 0
      18:07:58.028 -> SBC is idle in state(s) 0
      18:07:58.028 -> Daemon
      is idle in state(s) 0 0, running macro
      18:07:58.028 -> Autopause is idle in state(s) 0
      18:07:58.028 -> Code queue is empty.
      18:07:58.028 -> === Network ===
      18:07:58.028 -> Slowest loop: 11.80ms; fastest: 0.03ms
      18:07:58.028 -> Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
      18:07:58.028 -> HTTP sessions: 1 of 8
      18:07:58.028 -> - Ethernet -
      18:07:58.028 -> State: active
      18:07:58.028 -> Error counts: 0 0 0 0 0
      18:07:58.028 -> Socket states: 2 2 2 2 2 0 0 2
      18:07:58.028 -> === CAN ===
      18:07:58.028 -> Messages sent 5, longest wait 77ms for type 6024
      18:07:58.028 -> === Linux interface ===
      18:07:58.028 -> State: 0, failed transfers: 0
      18:07:58.028 -> Last transfer: 1003824ms ago
      18:07:58.028 -> RX/TX seq numbers: 0/1
      18:07:58.028 -> SPI underruns 0, overruns 0
      18:07:58.028 -> Number of disconnects: 0
      18:07:58.028 -> Buffer RX/TX: 0/0-0
      18:07:58.028 -> ok

      M122 B1 give

      18:09:25.119 -> Diagnostics for board 1:
      18:09:25.119 -> Board EXP3HC firmware 3.01-RC5 (2020-03-29b1)
      18:09:25.119 -> Never used RAM 163.6Kb, max stack 312b
      18:09:25.119 -> HEAT 1280 CanAsync 1452 CanRecv 1404 TMC 164 AIN 532 MAIN 2164
      18:09:25.119 -> Last reset 00:18:10 ago, cause: power up
      18:09:25.119 -> Driver 0: standstill, reads 18225, writes 0 timeouts 0, SG min/max not available
      18:09:25.119 -> Driver 1: standstill, reads 18226, writes 0 timeouts 0, SG min/max not available
      18:09:25.119 -> Driver 2: standstill, reads 18224, writes 0 timeouts 0, SG min/max not available
      18:09:25.119 -> Moves scheduled 0, completed 0, hiccups 0
      18:09:25.119 -> VIN: 24.1V, V12: 12.3V
      18:09:25.119 -> MCU temperature: min 34.5C, current 34.8C, max 34.8C
      18:09:25.119 -> Ticks since heat task active 247, ADC conversions started 1090990, completed 1090990, timed out 0
      18:09:25.119 -> Last sensors broadcast 00000000 found 0 0 ticks ago
      18:09:25.119 -> Free CAN buffers: 36
      18:09:25.119 -> NVM user row de9a9239 aeecffb1 ffffffff ffffffff
      18:09:25.119 -> ok

      Any Idea ??

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

        Can you post a close up detailed photo of the solder points on the SD card slot?

        The fact that the board is working via USB, and that the SD card works in another Duet 3 would seem to indicate that the problem is with the slot itself.

        Z-Bot CoreXY Build | Thingiverse Profile

        1 Reply Last reply Reply Quote 0
        • Philippe71undefined
          Philippe71
          last edited by

          Looks OK...
          2996b286-ef0a-4484-a2bb-8e026a4ebf49-image.png

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

            Hello, it's a little hard to tell from that angle if the pads are properly bonded or not, but the fact that the card works in another Duet 3 is enough to convince us that the Duet 3 slot is likely the culprit and therefore warranty replacement is approved. Please contact your original vendor for a warranty replacement and direct them to this thread. Sorry for the inconvenience.

            Z-Bot CoreXY Build | Thingiverse Profile

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