@dc42 said in Duet Wifi unable to upload files:
If/when the problem comes back, a WireShark trace of a failed upload may help diagnose the reason.
Good idea, I'll have to try that next time. Appreciate the help and have been in love with my Duet for almost 2 years now! Thank you
@dc42 said in Duet Wifi unable to upload files:
Please update DuetWiFiServer to 1.22 or 1.23, then confirm using M122 that the update succeeded:
WiFi -
Network state is running
WiFi module is connected to access point
Failed messages: pending 0, notready 0, noresp 0
WiFi firmware version 1.21
WiFi MAC address 5c:cf:7f:ee:61:e8
WiFi Vcc 3.36, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 12896
WiFi IP address 192.168.1.85
WiFi signal strength -46dBm, reconnections 0, sleep mode modem
Socket states: 0 0 0 0 0 0 0 0There is a known issue in 1.21 that causes problems with a small number of routers.
Ok I have updated back to 1.23. The problem randomly stopped happening sometime last night as it normally does, maybe by some act of god it won't come back.
@bot said in Duet Wifi unable to upload files:
Are there any potential sources of radio interference during the times the uploading doesn't work? Do you live in an apartment building? Is their wifi congestion in the area? Microwaves or 2.4Ghz wireless phones being used? Are there many people in your own house using the same wifi network?
No interference, and the ESP8266 is basically within 2 meters of the router. I even tried using a WiFi extender to basically make a network entirely dedicated to the print which did nothing.
@dc42 said in Duet Wifi unable to upload files:
Please test writing to the SD card by sending M122 P104. You can optionally add an S parameter to specify the file size in Mb, default 10.
Also please update your WiFi firmware (DuetWiFiServer) to 1.22 or 1.23. Your M122 report shows that you are running 1.21.
I've tried every firmware you've mentioned here and none worked. I tried rolling back since the problem has only gotten worse over time. 1.22, 1.23, and 1.21 are all the same.
M122 Results: SD write speed for 10.0Mbyte file was 2.62Mbytes/sec
Steps to recreate my problem would be:
The strangest thing is that it seemingly randomly might let me upload a file every once in a while. Sometimes it even behaves for a while. Its been behaving pretty well after making this post, even though I changed nothing. I'm sure the problem will come back though.
Its formatted to 32gb, there's no way the Duet could possibly care. I believe the reasoning behind 32gb max is because anything past that won't allow you to do FAT32 which I have done here.
Also, I've tried that solution to no avail 
Been dealing with this problem for a long time, and trying to troubleshoot from other posts but I've given up and have no idea where else to go. I've done every single fix anyone has ever offhandedly mentioned.
I am completely unable to upload anything to my Duet anymore. This problem has gradually grown from being non-existent at first, to slow upload speeds, to intermittently causing issues, to being completely unable to upload anything anymore. I've tried every firmware combination imaginable, and every web control version.
Pretty sure my hardware is just broken, not sure what else I can possibly try.
Here's my M122:
M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 2.03beta3 running on Duet WiFi 1.02 or later
Board ID: 08DDM-9FAM2-LW4SD-6JKFA-3S46P-K3XHW
Used output buffers: 1 of 20 (8 max)
=== RTOS ===
Static ram: 25632
Dynamic ram: 93836 of which 396 recycled
Exception stack ram used: 268
Never used ram: 10940
Tasks: NETWORK(ready,524) HEAT(blocked,1236) MAIN(running,3816) IDLE(ready,196)
Owned mutexes:
=== Platform ===
Last reset 00:06:10 ago, cause: power up
Last software reset at 2019-03-28 14:41, reason: User, spinning module GCodes, available RAM 12752 bytes (slot 3)
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d
Error status: 0
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest block write time: 8.7ms, max retries 0
MCU temperature: min 39.5, current 39.7, max 43.0
Supply voltage: min 13.3, current 13.4, max 13.5, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: standstill, SG min/max not available
Driver 1: standstill, SG min/max not available
Driver 2: standstill, SG min/max not available
Driver 3: standstill, SG min/max not available
Driver 4: standstill, SG min/max not available
Date/time: 2019-03-29 11:50:07
Cache data hit count 1340612078
Slowest loop: 10.68ms; fastest: 0.07ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0
=== Move ===
Hiccups: 0, FreeDm: 169, MinFreeDm: 169, MaxWait: 0ms
Bed compensation in use: none
Bed probe heights: 0.000 0.000 0.000 0.000 0.000
=== MainDDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0
=== AuxDDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0
=== Heat ===
Bed heaters = -1 -1 -1 -1, chamberHeaters = -1 -1
=== GCodes ===
Segments left: 0, aux move: no
Stack records: 2 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 ===
Slowest loop: 42.06ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
HTTP sessions: 1 of 8
and my M39
SD card in slot 0: capacity 62.21Gb, free space 31.44Gb, speed 20.00MBytes/sec, cluster size 64kb
I'm using a high quality, high class SD card currently. I've tried using tons of different SD cards of various sizes and speeds and nothing fixes this problem.
While I don't use the sensor, I can't get on with the ultrabase. Tried to clean it with alcohol and it stained the surface. Tried printing PETG on it and it won't stick at all unless I go above 100 deg c, even then I still get lifting
Same experience as the previous poster, I had to actually go pretty far under on temps to get things to stick properly. Honestly, PEI is probably just better for most plastics (though the way PLA pops off is magical)
I actually have this exact setup and the IR sensor performs very poorly due to the surface treatment. The surface is some kind of black material with tiny hole patterns throughout, and the sensor seems to pick up on the surface holes giving massive differences in readings +-.2mm
Pretty frustrating because I bought the surface for the sole purpose of having it work with the IR sensor.