Unable to upload files larger than approx 1.2MB

bdelia

I have not narrowed down the file size that triggers the failure, however I am consistently not able to upload files larger than about 1.2MB. A Network Connection error happens, or at least that is the error presented to me. I have wiped and reformatted the SD card, it is 8GB. I have tested the card to ensure it is not damaged or corrupt. I have installed the 3.5.4 version of all and still cannot upload large files. Anything under 1MB uploads just fine.

Any thoughts on what I should look at next?

Phaedrux

Which Duet board?
Ethernet or wifi?
What is the exact error message?

bdelia

@Phaedrux I have the Duet 2 Ethernet. Was working fine a last time I printed a couple of weeks ago. Any file less that about 1.2MB uploads fine, that includes when trying to do a software update to the firmware, anything over about 1.2MB and the upload fails with a simple 'Network Connection Error' in a pop up and in the Console.

It also seems like it is taking a little longer than usual to connect via my web browser. The Duet 2 is wired directly to my cable modem/ router and my laptop is in the same room wired directly to the cable modem / router.

The only thing I did was swap out CAT5 cables with CAT6 recently. The CAT6 cables are new and I have ensured the cables are working on another computer.

Also, here is output from the M122 command:

M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.5.4 (2024-11-24 10:43:42) running on Duet Ethernet 1.02 or later
Board ID: 08DJM-9178L-L2MSD-6JKDA-3SS6K-K8G2Q
Used output buffers: 1 of 26 (14 max)
=== RTOS ===
Static ram: 23488
Dynamic ram: 68120 of which 0 recycled
Never used RAM 21868, free system stack 186 words
Tasks: NETWORK(1,ready,70.4%,222) HEAT(3,nWait 5,0.1%,328) Move(4,nWait 5,0.0%,361) MAIN(1,running,27.1%,742) IDLE(0,ready,2.5%,29), total 100.0%
Owned mutexes:
=== Platform ===
Last reset 00:00:40 ago, cause: power up
Last software reset at 2024-12-23 13:42, reason: User, Gcodes spinning, available RAM 16980, slot 1
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
MCU temperature: min 29.2, current 30.7, max 31.0
Supply voltage: min 26.5, current 26.6, max 26.6, under voltage events: 0, over voltage events: 0, power good: yes
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
Driver 1: standstill, SG min n/a
Driver 2: standstill, SG min n/a
Driver 3: standstill, SG min n/a
Driver 4: standstill, SG min n/a
Driver 5: 
Driver 6: 
Driver 7: 
Driver 8: 
Driver 9: 
Driver 10: 
Driver 11: 
Date/time: 2025-03-07 14:26:23
Cache data hit count 1649434290
Slowest loop: 253.65ms; fastest: 0.19ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest read time 25.5ms, 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
=== Heat ===
Bed heaters 0 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
Heater 1 is on, I-accum = 0.0
=== GCodes ===
Movement locks 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
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0
Q0 segments left 0
Code queue 0 is empty
=== Network ===
Slowest loop: 6.98ms; fastest: 0.02ms
Responder states: HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
HTTP sessions: 1 of 8
Interface state active, link 100Mbps full duplex
Socket states: 5 2 2 2 2 2

Phaedrux

Do you have a fresh SD card to test with?

Just in case, are you able to test with the old cat5 cable?

bdelia

@Phaedrux , thanks for the suggestions. I will try that and report back.

bdelia

@Phaedrux I just tried another SD card, 8GB. I formatted it first and then copied the contents of the original card over. I still experience 'Network Errors' when uploading a file over about 1.5GB.

I tested another ethernet cable, the CAT5 that was connected and it made no difference.

Are there any logs that the board outputs other than the Console output in the web client?

bdelia

@bdelia I just enabled logging of events via M929 P"eventlog.txt" S1, but the resultant log on shows the following after trying to upload a file that failed and caused the network error.

2025-03-08 09:41:49 [info] Event logging started at level warn
2025-03-08 09:41:49 [info] Running: Duet Ethernet 1.02 or later: 3.5.4 (2024-11-24 10:43:42)

bdelia

@bdelia I am at my wits end and am thinking I may need to replace the board...but everything seems to work with the exception of uploading files bigger than about 1.4MB. The uploads consistently fail, it is not intermittent.

Phaedrux

Did this start happening after updating a firmware or any other change?
Have you tried uploading from a different computer?

bdelia

@Phaedrux I just tried uploading from another computer and it worked. I have cleared the cache on the original computer's browser (Chrome), but that did not seem to help. I'll try again and another browser.

dc42

@bdelia if this issue continues then it may be helpful if you install Wireshark on your PC and get a trace of a failed attempt to upload a larger file.

bdelia

@dc42 , thanks I will give that a try tonight or tomorrow.

bdelia

@dc42 , I have been learning wireshark and have done some testing. I am not sure yet how to detect errors associated with network connections, but I know how to isolate the capture between my laptop IP and Duet IP. I now see that any file under about 1.5MB never gets to the POST command. Any file under that threshold uploads fine and I see the POST command.

Any recommendations on what to look for in the capture that might indicate a network issue? I am familiar with HTTP response codes due to my day job, but I am not a network engineer.

dc42

@bdelia there should always be a POST command, that's how file uploads are done.

Usually when there are network issues we see network packets with error status. Wireshark usually highlights these in a dark colour.

You probably already know this, but to isolate the traffic to the Duet use filter ip.addr==192.169.1.150 (substitute the actual IP address of the Duet).

bdelia

@dc42 I have been able to isolate the isolate the traffic to the Duet. I can see lines of info colored Red and Black amongst the green.

I am just not able to interpret the lines for meaningful errors.