Duet Web Control 2.0.0-RC3 is ready

DocTrucker

@chrishamm said in Duet Web Control 2.0.0-RC1 is ready:

...
In order to use this new web interface version, you must upgrade to David's latest RepRapFirmware version 2.02 first.
...

Just to clarify, 2.02+ firmware only or will the just released bugfix for the first generation boards be ok?

Thanks & yuletide greetings to you.

gnydick

I uploaded it and nothing happened. Does the firmware have to be 2.0.2-rc7? or will 2.0.2-rc6 work?

Phaedrux

@gnydick 2.02 full release is available now: https://forum.duet3d.com/topic/8284/firmware-2-02-released

1ri

via google translator

Awesome !! I have tried the new DWC 2.0.0 RC1 and looks very well done and will allow a lot of evolution. Only one thing. I had to comment on the line that defines the machine's password (M551) in order to access the machine. With the password I was not allowed to enter on Safari (Mac and IOS), Explorer (Windows) Google Chrome (Mac, IOS and Windows).
Thanks for the good work and have a good Christmas

SupraGuy

Installed, and now I cannot access the Duet over network. Connection attempt yields a blank browser screen in Chrome and IE. (Title "Duet Web Control 2" -- blank page otherwise.)

edit:
@1ri said in Duet Web Control 2.0.0-RC1 is ready:

via google translator

Awesome !! I have tried the new DWC 2.0.0 RC1 and looks very well done and will allow a lot of evolution. Only one thing. I had to comment on the line that defines the machine's password (M551) in order to access the machine. With the password I was not allowed to enter on Safari (Mac and IOS), Explorer (Windows) Google Chrome (Mac, IOS and Windows).
Thanks for the good work and have a good Christmas

I do not h ave any M551 command in my config.g.

sigxcpu

Is there any special thing to do except uploading the .ZIP?
I have updated to Duet WiFi Firmware 2.0.2 yesterday and today to DWC2 RC1.

Both my printers behave the same: the page does not load.

The browser console shows two errors:
0_1545726285232_f5152fd8-7359-43ec-8bd6-ff626a6509e9-image.png

If I click reload maaaany times, I get a page without style applied sometimes. DWC 1.22.6 loads and works perfectly every time.

Strange thing, Firefox fails to load it the first time (missing files errors) then a refresh fixes it. Another refresh breaks it the same way then a another refresh fixes it and so on.
Other browsers (Safari, Chrome, Webkit based) all fail.

Later edit:
I think this is more for @dc42.
Interestingly, a failed request for /js/app*js shows this:

HTTP/1.1 200 OK
Content-Type: application/javascript
Content-Encoding: gzip
Content-Length: 70034
Connection: close

But the connection is forcibly reset by Duet with RST, ACK after ~26KB. ~~These 26KB are interesting because they match around the value of the uploaded file over FTP, which is another bug I encounter.~~ (not related, because there are 26KB uncompressed vs 26KB compressed sent by FTP). The FTP bug described below is still valid, but it may have nothing to do with the HTTP download bug.
If I try to upload file on /www over FTP they always reach the SD card truncated. This specific file has it's size between always the same 3 values: 26.XX KB, 27.XX KB and 28.XX KB. Never 70.XX KB.

Again, I don't think this is a Wifi network error because everything else works beautifully. Even more, doing an ab benchmark on these specific JS files, it never fails in 100 requests with concurrency 2.

Even later edit. Sorry for the long post.

It looks like downloading the "big" files like chunk-vendorsjs and appjs always fails. One of them is always failing randomly.

Enabled serial debugging and got this:

HTTP connection accepted
HTTP req, command words { GET / HTTP/1.1 }, parameters { }
Read 0 1 12022
Read 0 1 23286
Read 0 1 23287
Sending reply, file = yes
Read 0 1 119158
HTTP connection accepted
HTTP connection accepted
HTTP connection accepted
HTTP req, command words { GET /css/app.41ddf9b3.css HTTP/1.1 }, parameters { }
HTTP req, command words { GET /css/chunk-vendors.30c0b939.css HTTP/1.1 }, parameters { }
HTTP req, command words { GET /js/chunk-vendors.92cfeab5.js HTTP/1.1 }, parameters { }
HTTP connection accepted
HTTP req, command words { GET /js/app.9bf271d0.js HTTP/1.1 }, parameters { }
Read 0 1 12022
Read 0 1 23286
Read 0 1 115190
Read 0 1 115191
Sending reply, file = yes
Read 0 1 12022
Read 0 1 23286
Read 0 1 115190
Read 0 1 115191
Sending reply, file = yes
Read 0 1 12022
Read 0 1 23286
Read 0 1 116982
Sending reply, file = yes
Read 0 1 12022
Read 0 1 23286
Read 0 1 116982
Sending reply, file = yes
Read 0 2 118390
Read 0 1 118392
Read 0 4 119414
Read 0 4 119418
Read 0 4 120822
Read 0 4 120826
Read 0 4 120054
Read 0 4 120058
Read 0 4 119422
Read 0 4 120830
Can't send anymore
WiFi reported error: incomplete write

Looks somewhat solved. Errors appear from time to time, but it works. What I did on both printers is that I've forced a firmware rewrite for the WiFi server using serial console.
Both were 1.21 before, both are 1.21 now. Maybe there are multiple 1.21 versions out there?

dragonn

I got this:
0_1545734870732_bea578d9-6053-4e99-9e89-61a4e8b81f79-image.png
When I tried to print a file.

dragonn

And the "warning Revert to Duet Web Control 1" doesn't work for me

dragonn

I changed the name of the file to "GhostingTes MakerMuse.gcode", uploaded it and now it prints fine.

chrishamm

Thanks for your feedback so far! DWC2 may take a few seconds to load initially but once cached it's way faster. Again, RRF 2.02 is required for this web interface version.

If you cannot access your machine after upgrading to DWC2 but DWC1 worked, you can still access DWC1 via http://<your printer>/reprap.htm. This will effectively load the old UI.

I could reproduce the password input problem when DWC2 is running in remote mode (i.e. when it's downloaded from the board), so I will have a look at it and fix it in RC2.

@SupraGuy Are you on DuetWiFiServer 1.21 and does the problem persist on different devices? Can you press F12 while loading and check if you get any error messages in the Console? Maybe reflashing DuetWiFiServer resolves your problem.

@sigxcpu Thanks for investigating this. Did you power-cycle your board once after the initial DuetWiFiServer 1.21 update? Glad you could solve it though.

hurzhurz

I just noticed that the axis move buttons don't seem to switch to relative movement first?
Had a little nozzle crash while testing something...

chrishamm

@hurzhurz Oops, you're right - will provide RC2 later today which will fix this, the password problem and what else is reported in the meantime.

PlasticMetal

Is there a way to change the Z movement increments? With a 460mm delta, I'd really like a 100mm increment.

Otherwise, I like it. I have the same password & "revert" problems as noted above, but for the moment I pulled the card & commented out the M551. Running an Ethernet v1.03 with 2.02.

Phaedrux

@plasticmetal try right clicking on the button. At least that worked previously.

PlasticMetal

@phaedrux Sweet! I've tried right clicking on other items before, but for some reason never there. Thanks!

chrishamm

Alright, here you go: https://github.com/chrishamm/DuetWebControl/releases/tag/2.0.0-RC2

The password issue is now fixed as well as the movement buttons not sending relative/absolute position codes. Enjoy!

Mike

Amazing, don't know if that was intended, but I'm getting twice higher G-code upload speeds now.

wilriker

Very nice new DWC! I really like it. The one thing I like three most so far is finally listing print and simulation times for GCode files.

Also I like the timeline on the X axis of the temperature graph.

One question though: what is the -mini version on the release page? Is it just minified JS and CSS or is there something else mini?

sigxcpu

Well, I spoke too soon. The issue came back, randomly. Updated to RC2, no change in behavior.
DWC1 works, 2 fails to load assets. "ab" testing on a failing asset is successful so I think it is something related to sockets/memory/wifi firmware. There are lots of dups and retransmissions when it fails.

Jacotheron

Thank you very much for this newer version. It is responsive and amazing.

A few things I have picked up while running this:

The Webcam URL was forgotten and had to be added again. Also the Webcam is now on its own page, I would have liked at least an option of showing a smaller webcam on the Print Status page.
Fans do not use their assigned names. My Fans are named with the C-parameter of M106, and this does not show up on the new DWC - not a big issue.

It is amazing to have the statuses visible on all pages - temperatures, speeds etc.