Duet Web Control 2.0.0-RC3 is ready

dc42

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

Then something is broken in backlog implementation because the Nth+1 connection gets TCP RST instead of waiting. Here is how to find out N:

I've found a couple of reasons for these issues:

DuetWiFiServer is coded to reject TCP connections if there are no listeners available for them. There are 4 HTTP responders, so an attempt to open a 5th concurrent HTTP connection is refused. I think this is the right thing to do. With luck, the browser will respect it.
The main problem I have identified is that DuetWiFiServer is running out of buffer space when returning multiple files concurrently. This results in the connection being aborted. I plan to change the code to buffer outgoing messages in our own code instead of in lwip, so that I can be sure that sufficient memory is available before accepting a message from the Duet.

sigxcpu

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

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

Then something is broken in backlog implementation because the Nth+1 connection gets TCP RST instead of waiting. Here is how to find out N:

I've found a couple of reasons for these issues:

DuetWiFiServer is coded to reject TCP connections if there are no listeners available for them. There are 4 HTTP responders, so an attempt to open a 5th concurrent HTTP connection is refused. I think this is the right thing to do. With luck, the browser will respect it.

The main problem I have identified is that DuetWiFiServer is running out of buffer space when returning multiple files concurrently. This results in the connection being aborted. I plan to change the code to buffer outgoing messages in our own code instead of in lwip, so that I can be sure that sufficient memory is available before accepting a message from the Duet.

Maybe I don't get this right, but 4 HTTP responders and backlog = 8 means that we can have up to 12 simultaneous connections, 4 accepted, 8 pending. The reset/connection refused should happen on the 13th concurrent attempt.
Based on your description (thanks, btw) and my network knowledge, I am pretty sure that the actual backlog is 0 if the 5th connection is refused.

percar

I have now been using the DWC 2.0.0 R2 for a few days now. I love the format. I also understand that this is a new undertaking and bugs are expected. Please continue in this direction because I feel that the new DWC format will be awesome once the bugs are gone. I ran into very few issues with one being the download time for the Gcodes to be printed. Also there have been a few disconnects which I have not really investigated the reason behind the disconnects. I am sure as time progresses this will all be sorted out. Again Thanks

gtj0

I have to say... I'm not a fan. Sorry.

Non sales/marketing users interfaces need to be designed for people who are going to be sitting in front of it and using it for 8 hours a day. Here are some things I'd like to see...

Get rid of the spacing in the left menu, then you don't need the major items to collapse. Keep it compact so everything you need is in the smallest space that's still usable.

The temperature plots are nice but I'd rather see a grid of my macros in that spot. Maybe you could keep the plots if the spacing in the other widgets were reduced.

When you scroll, the menu and top widgets should be pinned. For instance, when you're looking at the macros or system files, the only thing that should scroll is the list of files themselves. Even the list column headers and upload buttons should be fixed.

For devices with 3 movement axes and 1 or more extruders, the movement buttons should be laid out in a cross pattern. Vertical row for Y, horizontal row for X, then to the side, a vertical row for Z and each extruder.

These may be in the works but...
The height map display doesn't show the statistical analysis so if you look at it later you don't know the magnitude of the colors.

There's no display of system information.

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.