duet 085 sd card readings not consistent
Napalm1432 last edited by
I'm building a 3d printer using the duet 085 which i had still laying around, and am using the dwc too, i noticed though that it often happens that i get the error "can't read homex.g" for example, i then have to reset the machine for it to work correctly again.
Is this a hardware problem, or sd card problem or something else?
Also when using dwc it often has issues showing current states (for example having to refresh the page to see current temperatures) is there any cause/solution for this?
bearer last edited by
run M122 when it happens, and i'd pull the sd card and inspect the contacts
Napalm1432 last edited by Napalm1432
For some reason it took a while for it to happen again, but here is the log from M122
This is with a different SD card (a new one from SanDisk) and the same happens.
=== Diagnostics === Used output buffers: 2 of 32 (21 max) === Platform === RepRapFirmware for Duet version 1.21 running on Duet 0.85 Static ram used: 44844 Dynamic ram used: 40964 Recycled dynamic ram: 208 Stack ram used: 1192 current, 5380 maximum Never used ram: 6908 Last reset 00:02:13 ago, cause: power up Last software reset at 2020-07-28 13:35, reason: User, spinning module GCodes, available RAM 6956 bytes (slot 0) Software reset code 0x0003 HFSR 0x00000000, CFSR 0x00000000, ICSR 0x00438000, BFAR 0xe000ed38, SP 0xffffffff Error status: 0 Free file entries: 10 SD card 0 detected, interface speed: 21.0MBytes/sec SD card longest block write time: 0.0ms MCU temperature: min 40.9, current 42.6, max 42.7 Date/time: 2020-07-28 15:54:00 Slowest main loop (seconds): 0.050156; fastest: 0.000104 === Move === MaxReps: 0, StepErrors: 0, LaErrors: 0, FreeDm: 100, MinFreeDm 100, MaxWait: 0ms, Underruns: 0, 0 Scheduled moves: 10, completed moves: 10 Bed compensation in use: none Bed probe heights: 0.000 0.000 0.000 0.000 0.000 === Heat === Bed heaters = 0, chamberHeaters = -1 -1 Heater 1 is on, I-accum = 0.0 === GCodes === Segments left: 0 Stack records: 1 allocated, 0 in use 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 serial is idle in state(s) 0 aux is idle in state(s) 0 daemon is idle in state(s) 0 queue is idle in state(s) 0 autopause is idle in state(s) 0 Code queue is empty. === Network === Free connections: 15 of 16 Free transactions: 23 of 24 Locked: 1, state: 4, listening: 0x20071bf8, 0x0, 0x0
I suggest that you update the firmware. The last release available is 1.26.1 (which came with the 2.05.1 release)
There are likely some changes required to your config and homing files when going from 1.21 to 1.26 so take a look through the release notes.
At the very least updating will give us more detail in the M122 report.
Napalm1432 last edited by
Okay i have updated the firmware (just wondering is there another/newer version of dwc? running 1.22.6)
So far it seems like it keeps reading correctly, is there a way to keep checking if the sd card can be read every x seconds, without having to be constantly checking manually
is there a way to keep checking if the sd card can be read every x seconds, without having to be constantly checking manually
Not really. See here for testing SD card function: https://duet3d.dozuki.com/Wiki/SD_Card#Section_Troubleshooting_SD_Card_issues
is there another/newer version of dwc? running 1.22.6)
In that same link there are files for DWC 2.0.7 which may work on the older Duets, but I'm not certain about that.