Failed to upload sr.gcode
-
Can sobody help?
what i need to do?2023-06-26 11:17:44 m39
SD card in slot 0: capacity 29.00Gb, partition size 29.00Gb,free space 0.00Gb, speed MBytes/secm122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.4.0 (2022-03-15 18:57:24) running on Duet 3 MB6HC v1.01 or later (SBC mode)
Board ID: 08DJM-956BA-NA3TN-6JKD6-3SN6Q-TB8GU
Used output buffers: 1 of 40 (13 max)
=== RTOS ===
Static ram: 151000
Dynamic ram: 66692 of which 0 recycled
Never used RAM 132980, free system stack 192 words
Tasks: SBC(resourceWait:,0.6%,478) HEAT(notifyWait,0.0%,321) Move(notifyWait,0.0%,352) CanReceiv(notifyWait,0.0%,772) CanSender(notifyWait,0.0%,374) CanClock(delaying,0.0%,339) TMC(notifyWait,7.9%,92) MAIN(running,91.4%,923) IDLE(ready,0.0%,30), total 100.0%
Owned mutexes: HTTP(MAIN)
=== Platform ===
Last reset 00:36:39 ago, cause: software
Last software reset at 2023-06-26 10:33, reason: User, GCodes spinning, available RAM 133012, slot 0
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0x00000000 SP 0x00000000 Task SBC Freestk 0 n/a
Error status: 0x00
Step timer max interval 134
MCU temperature: min 38.8, current 38.9, max 39.1
Supply voltage: min 24.3, current 24.4, max 24.4, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 12.1, current 12.1, 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: standstill, SG min n/a, mspos 8, reads 264, writes 0 timeouts 0
Driver 1: standstill, SG min n/a, mspos 8, reads 264, writes 0 timeouts 0
Driver 2: standstill, SG min n/a, mspos 8, reads 264, writes 0 timeouts 0
Driver 3: standstill, SG min n/a, mspos 8, reads 264, writes 0 timeouts 0
Driver 4: standstill, SG min n/a, mspos 8, reads 264, writes 0 timeouts 0
Driver 5: standstill, SG min n/a, mspos 8, reads 264, writes 0 timeouts 0
Date/time: 2023-06-26 11:13:29
Slowest loop: 1.46ms; fastest: 0.05ms
=== 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 0 4 -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 doing "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
=== CAN ===
Messages queued 318, received 1418, lost 0, boc 0
Longest wait 0ms for reply type 0, peak Tx sync delay 5, free buffers 50 (min 50), ts 176/176/0
Tx timeouts 0,0,0,0,0,0
=== SBC interface ===
Transfer state: 4, failed transfers: 0, checksum errors: 0
RX/TX seq numbers: 19741/19741
SPI underruns 0, overruns 0
State: 5, disconnects: 0, timeouts: 0, IAP RAM available 0x2b858
Buffer RX/TX: 0/0-0, open files: 0
=== Duet Control Server ===
Duet Control Server v3.4.0
Code buffer space: 4096
Configured SPI speed: 8000000Hz, TfrRdy pin glitches: 0
Full transfers per second: 38.60, max time between full transfers: 53.2ms, max pin wait times: 38.2ms/13.4ms
Codes per second: 0.03
Maximum length of RX/TX data transfers: 6132/796 -
@DariusR4 said in Failed to upload sr.gcode:
SD card in slot 0: capacity 29.00Gb, partition size 29.00Gb,free space 0.00Gb, speed MBytes/sec
looks like your SD card is full
-
@DariusR4
i clean all files from SD card in slot 0 -
@DariusR4 thats the SD card partition on the SD card in the pi.
What may be the case is that you're running an older version of the pi image that had logging turned on.
It may be worth backing up your config etc and flashing a new version of the image
