Duet Wifi upgrade to 1.19 failed and I cannot access my printer.

[dc42]

You could send M122 then look for the WiFi firmware version in the response. It should be 1.22.

[Phaedrux]

@dougal1957 said in Duet Wifi upgrade to 1.19 failed and I cannot access my printer.:

Is it supposed to open a guy or does it just enable boss command line?

For me Bossa 1.8 in the applications folder opens a full GUI. Though there appears to be some compatibility issues. For me 1.9 behaves as you describe.

[Condensedcloud]

@dc42 Sending M122 from pronterface (w/o getting connected in terminal) :

M122
SENDING:M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 2.02(RTOS) running on Duet WiFi 1.0 or 1.01
Board ID: 08D6M-91AST-L23S4-7J1DG-3S86K-TPXFK
Used output buffers: 1 of 20 (1 max)
=== RTOS ===
Static ram: 25524
Dynamic ram: 98588 of which 0 recycled
Exception stack ram used: 304
Never used ram: 6656
Tasks: NETWORK(ready,1872) HEAT(blocked,1324) MAIN(running,3868) IDLE(ready,200)
Owned mutexes:
=== Platform ===
Last reset 00:00:24 ago, cause: power up
Last software reset details not available
Error status: 0
[ERROR] Error status: 0

Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest block write time: 0.0ms, max retries 0
MCU temperature: min 16.1, current 19.7, max 19.9
Supply voltage: min 0.0, current 0.6, max 0.6, under voltage events: 0, over voltage events: 0, power good: no
Driver 0: ok, SG min/max not available
Driver 1: ok, SG min/max not available
Driver 2: ok, SG min/max not available
Driver 3: ok, SG min/max not available
Driver 4: ok, SG min/max not available
Date/time: 1970-01-01 00:00:00
Cache data hit count 41978028
Slowest loop: 0.28ms; fastest: 0.06ms
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
Heater 1 is on, I-accum = 0.0
=== GCodes ===
Segments left: 0
Stack records: 1 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 ready with "M122" 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: 0.18ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
HTTP sessions: 0 of 8

• WiFi -
  Network state is disabled
  WiFi module is disabled
  Failed messages: pending 2779096485, notready 2779096485, noresp 2779096485
  Socket states: 0 0 0 0 0 0 0 0

[dc42]

Send M552 S0 to enable the WiFi module, then repeat the M122. Then send M552 S1 to try to connect to the AP, give it half a minute to connect, and run M552 again.

I think your browser may have cached the error message page and not be connecting to the Duet.

[Condensedcloud]

@dc42 Tried clearing cached data in browser (EDIT: also tried a different browser), same result, wall of text:

Connecting...
Printer is now online.

M552 S0
SENDING:M552 S0
WiFi module started
M122
SENDING:M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 2.02(RTOS) running on Duet WiFi 1.0 or 1.01
Board ID: 08D6M-91AST-L23S4-7J1DG-3S86K-TPXFK
Used output buffers: 1 of 20 (1 max)
=== RTOS ===
Static ram: 25524
Dynamic ram: 98588 of which 0 recycled
Exception stack ram used: 256
Never used ram: 6704
Tasks: NETWORK(ready,1492) HEAT(blocked,1296) MAIN(running,3868) IDLE(ready,200)
Owned mutexes:
=== Platform ===
Last reset 00:00:48 ago, cause: power up
Last software reset details not available
Error status: 0
[ERROR] Error status: 0

Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest block write time: 0.0ms, max retries 0
MCU temperature: min 16.0, current 21.2, max 21.4
Supply voltage: min 0.0, current 0.5, max 0.8, under voltage events: 0, over voltage events: 0, power good: no
Driver 0: ok, SG min/max not available
Driver 1: ok, SG min/max not available
Driver 2: ok, SG min/max not available
Driver 3: ok, SG min/max not available
Driver 4: ok, SG min/max not available
Date/time: 1970-01-01 00:00:00
Cache data hit count 86005194
Slowest loop: 99.20ms; fastest: 0.06ms
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
Heater 1 is on, I-accum = 0.0
=== GCodes ===
Segments left: 0
Stack records: 1 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 ready with "M122" 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: 1.28ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
HTTP sessions: 0 of 8

• WiFi -
  Network state is running
  WiFi module is idle
  Failed messages: pending 0, notready 0, noresp 0
  WiFi firmware version 1.22
  WiFi MAC address a0:20:a6:19:45:f5
  WiFi Vcc 3.38, reset reason Turned on by main processor
  WiFi flash size 4194304, free heap 33632
  Socket states: 0 0 0 0 0 0 0 0

M552 S1
SENDING:M552 S1
WiFi module is connected to access point interwebs, IP address 10.0.0.28
M552
SENDING:M552
WiFi module is connected to access point interwebs, IP address 10.0.0.28

[dc42]

Please confirm, you have a folder called www in the root of the SD card (not inside /sys), and in that folder is a file called reprap.htm or reprap.htm.gz ?

[Condensedcloud]

confirmed: https://imgur.com/a/30g8QEV

[dc42]

@condensedcloud, thanks for the image. I can now see the problem. Instead of copying the DuetWebControl-xxx.zip file into /www you need to extract the contents of it into /www.

[Condensedcloud]

@dc42 I dropped the .zip file into the /www folder I then double clicked it to extract it into the folder. I then followed the Getting Connected to Your Duet Steps into the Terminal. Same result (EDIT: left the .zip file in the /www folder)

[Dougal1957]

@condensedcloud you have 1 level of directories to many in the /www folder. You need to extract the file into /WWW from outside of it and not within it if that makes sense

You need to remove the DuetWebControl-1.22.6 folder

[dc42]

The image you posted doesn't show reprap.htm.gz or the js and css folders as being directly contained on /www. It only shows them as being contained in /www/DuetWebControl-1.22.6. I guess when you extracted the zip, it created a new folder.

Edit: Dougal beat me to it.

[Condensedcloud]

YASSSSS, Thank You. Thank You. Thank you Gentleman. I was losing hope and we are online. I thought I had a dead printer on my hand. I've heard you are the best in the business and your customer support has proven it to be so. (not to mention the quietest and smoothest delta I've ever worked with due to your handiwork) I plan on building a few more printers in the near future with some friends and I hope to not be such a pain in the arse for you guys soon. You get my standing ovation for your diligence standing behind your product.

[Condensedcloud]

Can I buy you guys a beer?(EDIT where/who do I donate/paypal) I do plan to support the project with future builds utilizing the chip but I do appreciate the above and beyond support you've provided.

[dc42]

@condensedcloud said in Duet Wifi upgrade to 1.19 failed and I cannot access my printer.:

Can I buy you guys a beer?(EDIT where/who do I donate/paypal) I do plan to support the project with future builds utilizing the chip but I do appreciate the above and beyond support you've provided.

If you bought a genuine Duet from Duet3d or one of our distributors, then no need to donate because support is part of what you paid for. But beers are always welcome, so if you are at MRRF or 3D meetup Sweden or 3d meetup UK or TCT this year, say hello to Duet3d staff there!