New Day, New issue SdCard reader not working
-
@Phaedrux I have the files on my computer, but I would like to view a picture of what they all should be, just to make sure I have them all. I'm at work and I have the board out of the printer. Will try once I get home, tonight.
-
@Theboz1419 said in New Day, New issue SdCard reader not working:
I would like to view a picture of what they all should be
You can find details here
https://docs.duet3d.com/en/User_manual/RepRapFirmware/SD_card
-
here is my M122 after adding all the files needed on the SD card
M122 === Diagnostics === RepRapFirmware for Duet 3 Mini 5+ version 3.5.2 (2024-06-11 17:14:16) running on Duet 3 Mini5plus WiFi (standalone mode) Board ID: KU1YQ-YN6KL-K65J0-409NW-4HW1Z-74M6V Used output buffers: 1 of 40 (1 max) Error in macro line 9 while starting up: in file macro line 9 column 11: M552: expected a string expression === RTOS === Static ram: 103368 Dynamic ram: 121916 of which 0 recycled Never used RAM 13276, free system stack 156 words Tasks: NETWORK(1,ready,6.4%,505) HEAT(3,nWait 1,0.0%,355) Move(4,nWait 6,0.0%,355) CanReceiv(6,nWait 1,0.0%,939) CanSender(5,nWait 7,0.0%,336) CanClock(7,delaying,0.0%,334) TMC(4,nWait 6,0.0%,121) MAIN(1,running,92.5%,651) IDLE(0,ready,0.2%,29) AIN(4,delaying,0.9%,264), total 100.0% Owned mutexes: USB(MAIN) === Platform === Last reset 00:01:02 ago, cause: power up Last software reset at 2024-07-30 00:02, reason: User, Gcodes spinning, available RAM 16244, slot 1 Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00487000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a Error status: 0x00 MCU revision 3, ADC conversions started 62975, completed 62975, timed out 0, errs 0 MCU temperature: min 26.4, current 30.2, max 30.5 Supply voltage: min 0.4, current 1.0, max 1.0, under voltage events: 0, over voltage events: 0, power good: no Heap OK, handles allocated/used 99/2, heap memory allocated/used/recyclable 2048/80/0, gc cycles 0 Events: 1 queued, 1 completed Driver 0: ok, SG min n/a, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0, CC errors 0 Driver 1: ok, SG min n/a, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0, CC errors 0 Driver 2: ok, SG min n/a, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0, CC errors 0 Driver 3: ok, SG min n/a, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0, CC errors 0 Driver 4: ok, SG min n/a, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0, CC errors 0 Driver 5: ok, SG min n/a, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0, CC errors 0 Driver 6: ok, SG min n/a, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0, CC errors 0 Date/time: 1970-01-01 00:00:00 Cache data hit count 132858382 Slowest loop: 4.16ms; fastest: 0.15ms === Storage === Free file entries: 20 SD card 0 detected, interface speed: 22.5MBytes/sec SD card longest read time 1.0ms, write time 0.0ms, max retries 0 === Move === DMs created 83, segments created 0, maxWait 0ms, bed compensation in use: none, height map offset 0.000, max steps late 0, min interval 0, bad calcs 0, ebfmin 0.00, ebfmax 0.00 no step interrupt scheduled Moves shaped first try 0, on retry 0, too short 0, wrong shape 0, maybepossible 0 === DDARing 0 === Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1 === DDARing 1 === Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1 === Heat === Bed heaters 0 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0 === GCodes === Movement locks held by null, 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 File2 is idle in state(s) 0 Queue2 is idle in state(s) 0 Q0 segments left 0, axes/extruders owned 0x0000803 Code queue 0 is empty Q1 segments left 0, axes/extruders owned 0x0000000 Code queue 1 is empty === CAN === Messages queued 563, received 0, lost 0, errs 303613, boc 2 Longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 26 (min 26), ts 315/0/0 Tx timeouts 0,0,313,0,0,247 last cancelled message type 30 dest 127 === Network === Slowest loop: 0.24ms; fastest: 0.00ms Responder states: MQTT(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) HTTP sessions: 0 of 8 === WiFi === Interface state: disabled Module is disabled Failed messages: pending 0, notrdy 0, noresp 0 Socket states: 0 0 0 0 0 0 0 0 okD card 0 detected, interface speed: 22.5MBytes/sec
SD card longest read time 1.0ms, write time 0.0ms, max retries 0 -
Ok, apparently it seems to be working, I think.
I had made a backup to the system files on my old laptop and when I put the backup files on the SD card, the Duet did connect to my home network as it should.
I need to reinstall the Duet back into the printer and will see if anything changes.
I did do a resolder of the SD card slot, so maybe that got things working again.
Regardless, I purchased another Duet board, so I can have a back up board.
-
@Theboz1419 said in New Day, New issue SdCard reader not working:
D card 0 detected, interface speed: 22.5MBytes/sec
SD card longest read time 1.0ms, write time 0.0ms, max retries 0Reply
That looks normal. SD card 0 detected means that first SD card slot on the Duet is detected, not that zero (none) card is detected. SD card 1 detected would be the SD card slot on the PanelDue.
@Theboz1419 said in New Day, New issue SdCard reader not working:
the Duet did connect to my home network as it should.
The wifi network information is saved to the wifi module itself. The only thing that may have been missing is the M552 S1 command in config.g to enable the module at startup.
-
@Phaedrux It still has an issue.
I installed it back into my printer and everything looked OK, for the most part. Wifi seemed a little odd, as it would timeout and I would need to press the button on the display, a few times, to get it to connect to my network.
After, I was doing a Mesh, and it looked good doing it. I wanted to get ready for a print and I started to upload a gcode file to the sd card in the Duet.
That made the Mesh stop and I started to get numerous errors for files missing on SD card.
Now, the drive is unmount again and I'm not able to get connected to the Duet, unless I turn off power.
After doing a reset(power) and finally getting it connected to my wifi. It fails to write anything to the SD card. I can't even open up my Config.g file.
I bought a new Duet 3 mini wifi board and try to figure out what's going on with it, until I get the new board. If I figure it out, or if it gets RMA'd, at this point, this board will be back up to the new board, once I get it.
-
Just tried another SD card and still not working correctly. I'm not able to read the sd card.
-
I'm able to put the SD card in my laptop and upload a gcode file for printing and put it into the printer and turn on printer, run a Mesh(I'm hoping as that will store a file on the SD card) and start the print. But, as soon as I try to change anything on the SD card via Duet, it unmounts the SD card and I'm not able to get it working again until I do a power cycle.
-
@Theboz1419 said in New Day, New issue SdCard reader not working:
That made the Mesh stop and I started to get numerous errors for files missing on SD card.
What errors exactly are you getting?
@Theboz1419 said in New Day, New issue SdCard reader not working:
I'm not able to read the sd card.
What exactly are you seeing for this?
When it's in a state where you're unable to read the SD card, can you gather an M122 report and share it here?
-
@Phaedrux I'm at work, but the one error I recieved was
"Error 2 accessing SD card"
All the other errors were not able to locate folders on the SD card or saying the card is full. Then you can't access the SD card until you power cycle.
I'm just about done trying to figure this out. It's had issues with Wifi, even after updating the wifi module, it still goes into idle mode and does not connect after everytime you need to reboot the Duet board, and I need to press the button on the display numerous times to finally get the wifi to start.
Now, it's the SD card I don't think it's reading the sd card correctly. I wanted to do a print today and every time I tried to save the Simplify3d gcode file of the project I wanted to print, would make the SD card reader stop working and it would not save. I took the sd card out and put in my laptop and saved the file to the correct file for gcode and restarted the printer and I was able to view and start the file, But....
Before printing, I set my z height(using a piece of paper) and then did a Mesh, no issues that I could see. After, I see the mesh, below the graph. This didn't happen prior to the SD card issue, and nothing was moved after.
When I try to print, the printer doesn't even print correctly, it does half the outline and then starts the infill. I rechecked my Simplify3d code and it looks just fine. Also, the nozzle keeps going to the wrong height. It's just one thing after another, and I'm done with it.
I bought another card, regardless if this card can be fixed. I'm done with it for the most part.
-
I see you've already sent an email for a warranty replacement. We arrange for a replacement there.
For your other printing issues, please start a new thread for those if they remain after your new card arrives.
