Duet Web Control 2.0.0-RC3 is ready

3dmntbighker

How do I change the default fan from "Tool Fan" to "Fan 0"? I can't even hide Tool Fan, but I have to keep manually showing Fan 0, which is the tool fan.

kazolar

Maybe this was answered, but where is the diagnostics page in the new UI. I can't find drives/current/end stop status screen.

wilriker

@kazolar I don't think this is there, yet.

r123

Have not yet installed this. But would love to see a screenshot from someone who has so as to understand better what everyone's talking about!

kazolar

@wilriker ended up reverting the firmware to the previous RC build -- which removed the DWC upgrade, oh well...seems a bit raw as of now.

patakopecek

idk why but when I try to load code files my browser hangs, it just freezes

patakopecek

And I am unable to upload .bin files, which are essential for fw updating, until @dc42 starts packing his .zip with DWC2, and for some reason when I just removed the dwc1 files from the zip it would not let me update, it said that this package is not compatible with my electronics, I know it is because when I moved it to the sd card manually it worked like a charm

patakopecek

And I really miss a general purpose upload button for FW, DWC, Gcode etc.

Jacotheron

I have uploaded a few screenshots to my DropBox at https://www.dropbox.com/sh/s9jyzl8a9nmqbow/AAB5x4WU3fbKofEBBhQ3tatNa?dl=0

The naming is simple: if it starts with a 0, it is the light theme, and those that start with the 1 is the dark theme. I did not screenshot everything, it is easy enough to work from the light to imagine what the dark looks like.

Screenshots were taken in Firefox, on a full HD display.

Notes: 1) While I don't have the height map, enabled, I did screenshot it to show what details it can show. 2) "WanhaoD5S" is the name I gave the printer. 3) My printer is Cartesian, with a single extruder and heatbed. 4) While I have a webcam on it, I did not screenshot it, as it provides no real added value (it simply displays the images, or iframe in a big block). 5) I did not screenshot my config file in the file editor, since it may contain passwords and other info I would rather not have visible on the Internet. 6) Yes, I have a bunch of Macros. 7) MCU temperature, I like to be able to see it in the graph [during our recent heatwave it hovered around 50C].

For me this DWC simply works - there is small issues I found (mentioned above), but none that are a reason to revert to the previous version (at this time).

While I am here, I want to add a few things to the issues I have found:

Colors used in the Dark theme, quite a lot of the colors melts into the background. It seems that the Blue used is the same as in the light theme, maybe change it slightly.
The Extrusion Control in the Dashboard, those buttons (specifically the Feed Amount and Feedrate) looks "disabled" even though they are active and working

As to my opinion on the direction DWC is headed:

Change is needed from the version 1, using more modern and newer technologies. On this DWC2 is making good progress, but other sections needs to also be updated to prevent issues that many here have posted (not being able to connect, blank screens etc).
The Interface needs a big overhaul from version 1. While these visual changes are quite a lot, I think it may be too far from what we had for a single step. The animations should be a lot quicker, Yesterday when I did my M600 tests, the buttons in the Retract/Extrude section took too long before becoming "available" to click between clicks (I had 1m of bowden tube to retract/extrude) that I simply went to the PanelDue instead. The new interface works well on big screens with the current padding/white space used, but on smaller screens I keep scrolling to find the things I need (perhaps look at more Media Queries).
Browser caching needs to be used and optimized to use even less resources on the Duet.

Ultimately I think this is rather a Beta version, due to the amount of work still required.

That said, thank you for sharing it, it helps to gauge the community to help steer the development in the right direction.

Alas, it seems that my phone also had trouble connecting now - getting the white screen. Though a printer restart and it connects again (not always practical).

r123

Thanks a LOT for sharing screenshots.

Great to see time information on the X axis of the temperature graphs.

Often wondered if it would be interesting to add the parts FAN to that graph as well (0-100%) so that you can see what it's doing - and what it has been doing - at a glance?

3dmntbighker

@edgars-batna said in Duet Web Control 2.0.0-RC2 is ready:

I get CORS request failed seemingly sporadically. The error does not go away until I reload the page.

Same here.

nikker

I like it! I think some of the free space can be better utilized as mentioned above. One thing I miss is when you hover over a button, it would show you the G Code command that it would execute. I tried with a webcam and it seems like an actual stream is now supported? I use to use the jpeg every second but now i get a smooth video.

dc42

I have made a DuetWiFiServer 1.22 beta available, see https://forum.duet3d.com/topic/8355/duetwifiserver-1-22beta1-available. Specifically, this fixes (for me anyway) the issue of DWC 2.0.0RC2 not loading reliably from a Duet WiFi.

antlestxp

@dc42 is this only for the duet wifi? will it work for the maestro?

dc42

It's for the WiFi only. Are you having problems loading DWC2 from a Duet Maestro?

sigxcpu

@dc42 Interface loads reliably now. Many refreshes and no problem on sockets. Now I get the CORS error after a while, randomly. Cannot reproduce to see what triggers it.

kuhnikuehnast

Is there still a chance to change the language? Couldn't find it???

greetings kuhni

kuhnikuehnast

It is also impossible to upload .bin files by default. You have to check "upload all files" in the explorer before. (just found out as I wanted to update the DuetWifiServer.bin file.) Also the Version of this file isn't displayed any more?

antlestxp

@dc42 i am. the web control loads pretty slow compared to the original and i keep getting "CORS request failed" I have my duet plugged into a google mesh unit. it shows a connection speed of 600mb/s between nodes. i didn't have any connectivity issues before the updates.

Jacotheron

From my limited debugging related to the CORS errors, it seems that it may be used any time the request failed without something like error 404.

Where I got it, was trying to set it up for the reverse proxy, so I can visit it over HTTPS.

For the HTTPS, some resources are simply not loaded due to Mixed Content (the login call was sent without https and was denied by the browser) - this resulted in a CORS error being displayed.

Looking at the js, I found that in a few places, HTTP is hard-coded. For this I would recommend to determine the HTTPS status (whether it should be over https or http), and then use the correct one. This can be a global constant set at time of running (do a simple test and then set it), as it should not change during the browser session. This can also possibly shave off a few bytes in the file.

While debugging (in the reverse proxy scenario) I found Firefox report a lot of "[merge] Skipped merge of /autoConnect because it does not exist in the source" warnings (the autoConnect is only the first one, it seems like setting names).