I solved it! I have to add I1 after the M558 in the config.g file. Thanks for the great documentation, I leave this thread here for helping people solve this. Bye!

@dc42 Thanks! Love my duet, you make a great job. Continue like this, I will continue supporting you buying your products. When will the DUET 3 be available?

@phaedrux said in Can't upload gcode files - Duet Web Control:

together

Ok, so you think it is for that reason? The printer is a bit far from the modem, yes. I will try relocating it, thanks for all. But it is normal that all works good but the files upload only? Thanks

Hi, thanks! I will read the troubleshooting guide. The M122 command gives me the following results:
M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 2.02(RTOS) running on Duet WiFi 1.02 or later
Board ID: 08DDM-9FAM2-LW4SD-6J9F4-3SJ6N-9LZRY
Used output buffers: 3 of 20 (9 max)
=== RTOS ===
Static ram: 25524
Dynamic ram: 98624 of which 0 recycled
Exception stack ram used: 280
Never used ram: 6644
Tasks: NETWORK(ready,544) HEAT(blocked,1232) MAIN(running,3788) IDLE(ready,200)
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:48:52 ago, cause: software
Last software reset at 2019-02-07 20:46, reason: User, spinning module GCodes, available RAM 6500 bytes (slot 1)
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: 10.4ms, max retries 0
MCU temperature: min 37.1, current 38.3, max 38.5
Supply voltage: min 12.0, current 12.1, max 12.2, 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-02-07 21:35:36
Cache data hit count 4294967295
Slowest loop: 20.37ms; fastest: 0.07ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0
=== Move ===
Hiccups: 0, StepErrors: 0, LaErrors: 0, FreeDm: 240, MinFreeDm: 240, MaxWait: 0ms, Underruns: 0, 0
Scheduled moves: 0, completed moves: 0
Bed compensation in use: none
Bed probe heights: 0.000 0.000 0.000 0.000 0.000
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1
=== GCodes ===
Segments left: 0
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: 39.10ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(1) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
HTTP sessions: 1 of 8

• WiFi -
  Network state is running
  WiFi module is connected to access point
  Failed messages: pending 0, notready 0, noresp 0
  WiFi firmware version 1.22
  WiFi MAC address 60:01:94:34:37:ff
  WiFi Vcc 3.37, reset reason Turned on by main processor
  WiFi flash size 4194304, free heap 26136
  WiFi IP address 192.168.0.104
  WiFi signal strength -70dBm, reconnections 0, sleep mode modem
  Socket states: 0 2 0 0 0 0 0 0

Hi, when I try to upload gcode files it gives me an error, the speed is reduced to about 7.4 KiB/s and it gives me an error message. I don't think it is the wifi connection nor the SD card. Any idea? It is the first time using this DUET wifi board, I am using 2.02 release with duet web control 1.22.6 and duet wifi server 1.22. I can't control the machine via the DWC but the only thing I can't do is upload gcode files. Any help? Thanks in advance.

I think it is all explained in my comments. The settings on the configurator are "switch" and trigger value 1000. And the two cables connected to the Z probe header, on Z PROBE IN and GND pins. And finally, you will have to add "I1" after the M558 command in the config.g file.

@dc42 trigger threshold is the same as trigger value? Or what is it?

I solved it! I have to add I1 after the M558 in the config.g file. Thanks for the great documentation, I leave this thread here for helping people solve this. Bye!

I forgot to say that I am using the "switch" option in the probe type of the configurator tool, and the trigger value in 1000.

Well, I changed the two cables from the E0 endstop to the Z probe header (Z PROBE IN and GND) and now the static test works, when I place my finger below the sensor it goes from 1000 to 0, but when I try to home all the axes the Z axis will not do it, and the DWC gives me a message saying the Z endstop is triggered. I try inverting the position of the two cables but the problem continues. Any idea? Thanks

If anyone needs me to measure some voltage please let me know and explain me how to do it because I am not so experienced with electronics. Here I leave an image of the board between the sensor and the Duet also.