Failed to upload, CRC is different

[that guy E]

Using a Duet3 MB6HC firmware version 3.3 in standalone mode. When trying to upload files over ethernet I'm getting upload errors, "Uploaded file CRC is different 9421be53 vs expected 557234ad". Seems to only be with larger files.

M122 immediately after error

=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.3 (2021-06-15 21:45:47) running on Duet 3 MB6HC v1.01 or later (standalone mode)
Board ID: 08DJM-956BA-NA3TN-6JTD0-3S46R-1BAGS
Used output buffers: 1 of 40 (17 max)
=== RTOS ===
Static ram: 150904
Dynamic ram: 90964 of which 92 recycled
Never used RAM 112232, free system stack 206 words
Tasks: NETWORK(ready,25.9%,206) ETHERNET(notifyWait,0.4%,117) HEAT(delaying,0.0%,405) Move(notifyWait,0.0%,352) CanReceiv(notifyWait,0.0%,944) CanSender(notifyWait,0.0%,374) CanClock(delaying,0.0%,333) TMC(notifyWait,7.7%,93) MAIN(running,65.3%,924) IDLE(ready,0.6%,29), total 100.0%
Owned mutexes:
=== Platform ===
Last reset 00:01:20 ago, cause: power up
Last software reset at 2021-12-17 15:06, reason: User, GCodes spinning, available RAM 111800, slot 1
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0044a000 BFAR 0x00000000 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
Step timer max interval 131
MCU temperature: min 28.3, current 33.4, max 34.0
Supply voltage: min 24.2, current 24.3, max 24.4, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 11.9, current 12.0, max 12.1, under voltage events: 0
Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
Driver 0: position 0, standstill, reads 52055, writes 14 timeouts 0, SG min/max 0/0
Driver 1: position 0, standstill, reads 52055, writes 14 timeouts 0, SG min/max 0/0
Driver 2: position 0, standstill, reads 52056, writes 14 timeouts 0, SG min/max 0/0
Driver 3: position 0, standstill, reads 52059, writes 11 timeouts 0, SG min/max 0/0
Driver 4: position 0, standstill, reads 52057, writes 13 timeouts 0, SG min/max 0/0
Driver 5: position 0, standstill, reads 52059, writes 11 timeouts 0, SG min/max 0/0
Date/time: 2021-12-17 15:08:06
Slowest loop: 87.83ms; fastest: 0.05ms
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 25.0MBytes/sec
SD card longest read time 3.0ms, write time 136.2ms, max retries 0
=== Move ===
DMs created 125, maxWait 0ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed moves 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, chamberHeaters = -1 -1 -1 -1
=== 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 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 402, received 0, lost 0, longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 49 (min 49), ts 402/0/0
Tx timeouts 0,0,401,0,0,0 last cancelled message type 30 dest 127

=== Network ===
Slowest loop: 293.52ms; fastest: 0.02ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions Telnet(0), 0 sessions
HTTP sessions: 1 of 8
- Ethernet -
State: active
Error counts: 0 0 0 0 0
Socket states: 5 2 2 2 2 0 0 0

@dc42 is there update on repurposing pins to use a second SD card?

[A Former User]

@that-guy-e
I have the same problem since a few months.
Hopefully this time somebody will help.
Because the problem is not solved by copying the file manually to the sd card.

RG

[that guy E]

@gruna-studio

I was able to remove the SD card and manually copy it over, but that isn't a viable long term solution.

Should also mention that with enough power cycles and reconnections of the browser I am randomly able to get the file to upload.

[dc42]

@that-guy-e I don't think that CRC error is anything to do with the SD card, because the CRC is calculated before the data is written to the SD card.

How large are the files you are trying to upload? If you can make one of them available on Dropbox or Google Drive etc. then I can try uploading them here to see of I get the same problem.

[that guy E]

@dc42

I only get the error when trying to upload a job or if I select upload and run. I haven't seen it any other time.

I'll send the file and details tomorrow. I've definitely upload larger files to a duet 2 before. I'll also retry uploading one of the smaller test files I was running the other day.

[Phaedrux]

Which slicer is doing the uploading?

[that guy E]

@dc42

I uploaded three example gcodes here:
Google Drive

The files range from 1.8mb to 85.7mb all failed to upload. The large file is a gcode that I've successfully uploaded to an alternate Duet2 over wifi without issue.

Anything else I can provide please let me know.

[that guy E]

@phaedrux

I've tried gcodes exported from numerous slicers and cam software. And have uploaded the same files to duet2 wifi without issue.

[dc42]

@that-guy-e said in Failed to upload, CRC is different:

@dc42

I uploaded three example gcodes here:
Google Drive

The files range from 1.8mb to 85.7mb all failed to upload. The large file is a gcode that I've successfully uploaded to an alternate Duet2 over wifi without issue.

Anything else I can provide please let me know.

Thanks, I'll try uploading those files to a couple of MB6HC boards.

There was a known issue in this area in early 3.0 firmware builds, but that was fixed many versions ago, well before version 3.3.

[that guy E]

@dc42

If its of any value, I'm currently running DWC 3.3.0

[dc42]

@that-guy-e I can get CRC errors sometimes using the large file in that collection. I will investigate this.

[that guy E]

@dc42

I've tried a few more different uploads today and I'm getting the error sometimes. seems to be "random" I can get them 2X in a row and then on the 3rd try it will work.

Has there any more investigation into adding the auxiliary SD card. this would be beneficial for scenarios like this or network errors in general.

[dc42]

@that-guy-e I have found and fixed the error with uploading files to the MB6HC. Please try the 3.4.0beta7+1 binary at https://www.dropbox.com/sh/5ubjszy9fmlvzwu/AAAeOMGP-Yi-Gn9LZwQoPfita?dl=0.

[cosmowave]

@dc42 said in Failed to upload, CRC is different:

I have found and fixed the error with uploading files to the MB6HC

Sometimes i have the same problem with a Duet2 Ethernet. Is that fixed too?
But this happens not very often...

[dc42]

@cosmowave I don't think the issue I found will affect Duet 2 Ethernet, although I think it will affect Duet 3 Mini Ethernet. However, I have put new Duet 2 builds there as well.

[that guy E]

@dc42

Seems to have solved the error. Tried 10 different file uploads without issue. I'll report back if I see any further errors but won't get to do much testing over the upcoming week.

[that guy E]

@dc42

I have not run into further upload error using the beta firmware you provided.