Duet Web Control 2.0.0-RC3 is ready

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).

3dmntbighker

If I have a limit switch for Z home, can I eliminate it from DWC? And why does the value change during a print when the switch remains untouched after the initial home?

Torro

Hi,

Just updated to the new DWC.
Webcam URL was missing, so i added that.

Now, there is a problem with the update interval. DWC doesn´t store a changed value. i change it to 1000ms and swap to the webcam. the image is updated every 5 seconds. so i jump back to "user interface" and the update interval is set to 5000ms.

any idea?

Thanks!!

chrishamm

Happy new year, RC3 is now available. See https://github.com/chrishamm/DuetWebControl/releases/tag/2.0.0-RC3 for the update package and for the full change list.

This version provides fixes for many bugs and greatly increases the performance - there was a bug in the model code that caused a lot of unnecessary VDOM updates which slowed the whole thing down. The new version should be way faster than RC1+RC2.

@wilriker The -mini version of DWC does not contain any source maps, so if you use it and get errors, no useful output would be printed in the JS console. Because DWC2 is still a pre-release I decided to always include them in the standard update bundle. RC2 did not take into account the port when connecting but it should be fixed in RC3.

@gnydick The main reason DWC2 was rewritten from scratch was to provide a solid base for future development and a better environment for OEM customisations. Here my notes on your points of criticism:

It's true that there was no tab navigation in RC1+2 but I added it back to most of the controls in RC3. Activating buttons and items can be done by pressing the Enter key and switches can be toggled via arrow keys. Dialogs are still missing keyboard navigation but I will add it in the future.
Good point about the babystepping+movement buttons. In RC3 they now longer wait for the code to be processed, so they should behave in the same way as in DWC1.
One of the requirements for DWC1 was to improve touch support, which needs wider spaces so that you don't activate two elements at once. The whole layout could be probably condensed a bit more, yet this is something we can still address.
I disagree with the idea that DWC2 would be a perfect example of form over function - it's just a fact that DWC has evolved into a big PWA and I do not want to drop functionality we had in DWC1 even if that makes the whole layout bigger/clumsier. If you say you don't need any fancy charts or as many sub-pages, you can still edit the layout/routing by changing the source files (src/App.vue and sub-files in the 'src/routes' directory in particular) - it's all open-source. In the long-term I will develop a UI designer but that is not a simple task and will involve more work. Originally I wanted to make use of a grid system to allow customisations right in DWC2 but I remove it again (for now) because it degraded the performance too much.
G-code pop-ups take you to the console only if you don't hit the 'X' button
You can return to DWC1 by deleting 'index.html.gz. from the /www directory.

@Dougal1957 Drag&Drop support for the upload buttons was broken in RC2 but it's fixed in RC3.

@Jacotheron I changed the layer chart to hide the 1st layer once the 2nd one is complete. Many people complained about the slider ranges in DWC1 so I decided to make them dynamic in DWC2. I agree the UI was rather slow in RC2 but should be way faster in RC3. If you have a good proposal about a potential new structure for DWC2, please feel free to share your thoughts. As I said in the original DWC2 RFC thread I know the layout is not perfect but I wanted to establish the same functionality from DWC1 before moving on to further changes.

@Scachi Thanks, it should be fixed in RC3.

@brandonh Sounds like a good idea to show 'loading' instead of 'No jobs' etc. I will consider it for RC4. Browser navigation is not supported in the file lists yet but I could add it in the future. What exactly do you mean by speed graphing?

@fotomas @whosrdaddy Thanks, these problems have been fixed in RC3.

@AS-3D-Druck There are some changes in the dark theme of RC3, perhaps you will like the new version better.

@Danal @kazolar Please try out DWC2-RC3. I reduced the number of CSS+JS files to 1 for both, so I think it will load more reliably.

@Edgars-Batna DWC2 uses a UI framework that follows material design and on Android the order of buttons is different from Windows. Did you have a tool selected when you tried to extrude? The prompt for restarting the board was added again in RC3. Thanks for the note about config.bak instead of config.g.bak, it's been fixed too.

@kraegar Drag&drop is supported in the Files category. If you want to move a file up, drag&drop it on one of the directory links at the top.

@percar Thanks, good to hear!

@patakopecek The general upload is on the System Files page. I will move that to a separate '(Auto-)Update' page when I find more time.

@kuhnikuehnast Support for i18n has been prepared but it is not finished yet. I will improve this aspect once the new layout is final.

In general CORS errors are equivalent to network errors. When running DWC2 on localhost and it tries to connect to another machine, the browsers do a CORS preflight check (by sending an OPTIONS request to the host to see if the other request would be actually permitted) and if that fails, DWC2 reports a CORS error. I may simplify this a bit more so that it shows 'Network error' instead of 'CORS error' when running on a Duet.