6HC SD failure
-
I have a 6HC and x2 1XD with Openpnp as sender for my PnP machine. The machine has been working great for over a year. Today I powered the machine and was able to connect to the 6HC via Openpnp, but unable to get the machine to home. Looking at the Openpnp trace log, "[no homall file found]". I powered everything down and retrieved the SD card; SanDisck Ultra 16GB, and attempted to review the files on my main PC. Attempting to open the SD folder crashed my main PC; AMD Ryzen 5 3600 6-Core Processor 3.59 GHz Windows 10 Pro. After removing the SD and rebooting the PC I tired the SD again and after long pause Win spits out "Request cannot be performed because of an I/O device error".
Is there anything that can be done to try and recover my config files? I know I should have a backup, but alas do not.
help
-
Googling, I tried to dx the SD using DISKPART with no luck
I did M122 with and without the SD card inserted;
SD removed; M122> M122 === Diagnostics === RepRapFirmware for Duet 3 MB6HC version 3.4.0beta7 (2021-12-16 12:22:39) running on Duet 3 MB6HC v1.01 or later (SBC mode) Board ID: 08DJM-956BA-NA3TJ-6J9F8-3SD6S-1A9AS Used output buffers: 1 of 40 (14 max) === RTOS === Static ram: 150664 Dynamic ram: 62560 of which 0 recycled Never used RAM 137448, free system stack 190 words Tasks: SBC(notifyWait,0.0%,974) HEAT(notifyWait,0.0%,372) Move(notifyWait,0.0%,352) CanReceiv(notifyWait,0.0%,772) CanSender(notifyWait,0.0%,374) CanClock(delaying,0.0%,339) TMC(notifyWait,7.4%,92) MAIN(running,92.6%,1084) IDLE(ready,0.0%,30), total 100.0% Owned mutexes: USB(MAIN) === Platform === Last reset 05:40:49 ago, cause: power up Last software reset at 2022-03-07 18:29, reason: User, GCodes spinning, available RAM 103240, slot 2 Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0x00000000 SP 0x00000000 Task MAIN Freestk 0 n/a Error status: 0x00 Step timer max interval 127 MCU temperature: min 48.4, current 48.5, max 48.8 Supply voltage: min 24.1, current 24.1, max 24.2, under voltage events: 0, over voltage events: 0, power good: yes 12V rail voltage: min 12.1, current 12.2, max 12.2, under voltage events: 0 Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0 Events: 0 queued, 0 completed Driver 0: pos 0, standstill, SG min n/a, mspos 8, reads 6222, writes 0 timeouts 0 Driver 1: pos 0, standstill, SG min n/a, mspos 8, reads 6222, writes 0 timeouts 0 Driver 2: pos 0, standstill, SG min n/a, mspos 8, reads 6222, writes 0 timeouts 0 Driver 3: pos 0, standstill, SG min n/a, mspos 8, reads 6222, writes 0 timeouts 0 Driver 4: pos 0, standstill, SG min n/a, mspos 8, reads 6222, writes 0 timeouts 0 Driver 5: pos 0, standstill, SG min n/a, mspos 8, reads 6222, writes 0 timeouts 0 Date/time: 1970-01-01 00:00:00 Slowest loop: 0.12ms; fastest: 0.06ms === Storage === Free file entries: 10 SD card 0 not detected, interface speed: 37.5MBytes/sec SD card longest read time 0.0ms, write time 0.0ms, max retries 0 === Move === DMs created 125, segments created 0, maxWait 0ms, bed compensation in use: none, comp offset 0.000 === MainDDARing === Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1 === AuxDDARing === Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1 === Heat === Bed heaters -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0 === GCodes === Segments left: 0 Movement lock held by null HTTP is idle in state(s) 0 Telnet is idle in state(s) 0 File is idle in state(s) 0 USB is ready with "M122" 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 === CAN === Messages queued 471, received 1508, lost 0, boc 0 Longest wait 0ms for reply type 0, peak Tx sync delay 5, free buffers 49 (min 49), ts 471/471/0 Tx timeouts 0,0,0,0,0,0 === SBC interface === Transfer state: 0, failed transfers: 0, checksum errors: 0 RX/TX seq numbers: 0/1 SPI underruns 0, overruns 0 State: 0, disconnects: 0, timeouts: 0, IAP RAM available 0x2bf44 Buffer RX/TX: 0/0-0 okM122 SD re-inserted
> M122 === Diagnostics === RepRapFirmware for Duet 3 MB6HC version 3.4.0beta7 (2021-12-16 12:22:39) running on Duet 3 MB6HC v1.01 or later (SBC mode) Board ID: 08DJM-956BA-NA3TJ-6J9F8-3SD6S-1A9AS Used output buffers: 1 of 40 (14 max) === RTOS === Static ram: 150664 Dynamic ram: 62560 of which 0 recycled Never used RAM 137448, free system stack 178 words Tasks: SBC(notifyWait,0.0%,974) HEAT(notifyWait,0.0%,372) Move(notifyWait,0.0%,352) CanReceiv(notifyWait,0.0%,772) CanSender(notifyWait,0.0%,374) CanClock(delaying,0.0%,339) TMC(notifyWait,7.4%,92) MAIN(running,92.6%,1045) IDLE(ready,0.0%,30), total 100.0% Owned mutexes: USB(MAIN) === Platform === Last reset 06:09:02 ago, cause: power up Last software reset at 2022-03-07 18:29, reason: User, GCodes spinning, available RAM 103240, slot 2 Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0x00000000 SP 0x00000000 Task MAIN Freestk 0 n/a Error status: 0x00 Step timer max interval 127 MCU temperature: min 48.3, current 49.2, max 49.4 Supply voltage: min 24.1, current 24.1, max 24.2, under voltage events: 0, over voltage events: 0, power good: yes 12V rail voltage: min 12.1, current 12.2, max 12.2, under voltage events: 0 Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0 Events: 0 queued, 0 completed Driver 0: pos 0, standstill, SG min n/a, mspos 8, reads 28115, writes 0 timeouts 0 Driver 1: pos 0, standstill, SG min n/a, mspos 8, reads 28115, writes 0 timeouts 0 Driver 2: pos 0, standstill, SG min n/a, mspos 8, reads 28115, writes 0 timeouts 0 Driver 3: pos 0, standstill, SG min n/a, mspos 8, reads 28115, writes 0 timeouts 0 Driver 4: pos 0, standstill, SG min n/a, mspos 8, reads 28115, writes 0 timeouts 0 Driver 5: pos 0, standstill, SG min n/a, mspos 8, reads 28115, writes 0 timeouts 0 Date/time: 1970-01-01 00:00:00 Slowest loop: 0.19ms; fastest: 0.06ms === Storage === Free file entries: 10 SD card 0 detected, interface speed: 37.5MBytes/sec SD card longest read time 0.0ms, write time 0.0ms, max retries 0 === Move === DMs created 125, segments created 0, maxWait 0ms, bed compensation in use: none, comp offset 0.000 === MainDDARing === Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1 === AuxDDARing === Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1 === Heat === Bed heaters -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0 === GCodes === Segments left: 0 Movement lock held by null HTTP is idle in state(s) 0 Telnet is idle in state(s) 0 File is idle in state(s) 0 USB is ready with "M122" 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 === CAN === Messages queued 8466, received 27092, lost 0, boc 0 Longest wait 0ms for reply type 0, peak Tx sync delay 266, free buffers 49 (min 49), ts 8466/8466/0 Tx timeouts 0,0,0,0,0,0 === SBC interface === Transfer state: 0, failed transfers: 0, checksum errors: 0 RX/TX seq numbers: 0/1 SPI underruns 0, overruns 0 State: 0, disconnects: 0, timeouts: 0, IAP RAM available 0x2bf44 Buffer RX/TX: 0/0-0 okIs there any way to get any of the config off the MCU or is it all lost on the SD?
Thanks Wayne
-
@wayneosdias said in 6HC SD failure:
Is there any way to get any of the config off the MCU or is it all lost on the SD?
The config files are all stored on the SD card. Sd cards are a fickle medium. Backups are a must.
-
@Phaedrux
I think it may be more serious than just the SD card. Fortunately I found the full config from a openpnp/duet wiki I did. Unfortunatley I cant get the 6HC to read/boot from a new SD. Ill have to pull the 6HC see whats going on. -
@wayneosdias said in 6HC SD failure:
Duet 3 MB6HC v1.01 or later (SBC mode)
Your M122 report indicates you're running in SBC mode, is that the case? Is your SD card in the Duet itself or the Pi?
-
@Phaedrux
Yes it reports that without an SD and the old bad SD installed. I now have the machine up and running config wise, but dont have my homing sequences. I'm having issues connecting to dwc via ethernet to the controlling laptop. Otherwise ethernet is fine if connected directly connected to my home router. I have a wifi wifi ethernet bridge on order so I can use dwc with the 6HC in situ, otherwise I have to pull the board ot of the machine.Once I get the ethernet working in situ I rework my homing processes. For PnP there is an axis interlock sequence for the drag pin feeder to prevent crashes.
In the end my issue was an inexplicable SD card failure. The card is the original that came w the 6HC. Thanks for everyone's help.
-
undefined wayneosdias marked this topic as a question
-
undefined wayneosdias has marked this topic as solved
