Duet Web Control 2.0.0-RC3 is ready

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.

gnydick

Honestly, I feel the new version is worse in almost every way.

There are even less buttons that can be clicked by using the space bar
The buttons are much slower to respond, for example, clicking baby-step repeatedly is torture, you have to wait for the flash animation to finish before you can click it again
It's clunkier, even though it looks prettier; more clicks to do the same thing
The pop-up messages take you to the g-code console when you dismiss them

I'm being brutally honest here, this is the perfect example of form over function. I tried explaining what was needed in the RFC and warned about this kind of stuff.

The web interface should be fast, instant in response as possible given the web host, predictable, and impossible to click the wrong thing at the wrong time. It should have every single button clickable via the space bar as well as every clickable item tab-indexed.

I predicted this would be a passion project about learning a new front end library, and I was right.

Honestly, I suggest going back to square one.

Start by creating a control interfaces like this was a manufacturing machine. Oh, wait, it is!

Forget fancy menus. What do we do a lot of?

Well, when tuning and tweaking

I want to have a g-code console and the config editor side-by-side
give me a small mechanical control there as well
a drop down with macros is enough, they don't need to be listed out
- if you want to repeatedly run macros, then make a screen for that

What we don't need

Graphs are pretty, but really, there's no reason for them to take up so much space
The status pane is also way too big. It would work just as well as a single line along the bottom or top

I could go on and on, but I'm honestly so mad that I warned this would happen. Since updating to the latest firmware, I can't even revert to Web Control 1. Can I just re-upload it or will I have to clean up files on the SD Card?

In reality, my suggestion a long time ago was to make each of these panes a widget you can drag 'n drop and resize to make your own screens. THAT would please everyone.

wilriker

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

Since updating to the latest firmware, I can't even revert to Web Control 1. Can I just re-upload it or will I have to clean up files on the SD Card?

M30 "/www/index.html"

should get you back to DWC1. Of course with a reload after that.

dc42

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

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.

Do you have a M551 password set? If so, try removing it. I've found that RC2 still doesn't work on my Kossel unless I remove the password.

Btw you can temporarily revert to DWC 1 by entering <ip_address>/reprap.htm in your browser instead of just the IP address.

Dougal1957

Love the new layout however are you going to support drag and drop files again or am I doing something stupid?

Jacotheron

A possible bug I found while printing: The Layer Chart does not scale down.

I am still having issues where my first layers are not correctly picked up, so my 2nd layer typically shows as taking 10x longer than what it should have taken, will report in separate thread. Now after that first extremely long layer time, the chart is scaled up to fit that time, but long after it is no longer being displayed (for example after the 35th layer [this DWC shows 30 layer's time]), the Y still shows the scale for the longer time - this means my other layers basically produce a flat line at the bottom of the graph.

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:

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.

Do you have a M551 password set? If so, try removing it. I've found that RC2 still doesn't work on my Kossel unless I remove the password.

Btw you can temporarily revert to DWC 1 by entering <ip_address>/reprap.htm in your browser instead of just the IP address.

I do have M551 Preprap but that is ignored. Before you asking me I've never noticed it is set. Always logged in as "ftp" with no password.
I know about /reprap.htm and that's what I'm using. I still don't understand why downloading assets in DWC2 fails randomly but DWC1 loads.
And, again, downloading them with ab returns successfully each and every request. Tried with 2 threads, let's try with 6 just like the browser does.
...
ab testing works up to 3 connections. Everything higher than that breaks with connection refused. I think that is the problem with the UI download.
Testing it further, I see that it works reliably with 2 connections. 3 is hit and miss, >=4 always fails.

dc42

@sigxcpu, I have come to the same conclusion that there are problems triggered by the increased number of concurrent connections that DWC2 uses. The problems are worse when there is a password set, but I get them occasionally even with no password. I've asked chrishamm if he can reduce the number of concurrent connections used. When I next work on DuetWiFiServer, I'll review the way that multiple concurrent connections are handled.

wilriker

After using DWC2 a lot today, I have found some issues (some personal others breaking changes)

I looks nice but wastes a lot of space especially on smaller resultion screens, e.g. there now are only 3 axis jog buttons per direction whereas there were 4 before. Changing CSS in dev tools to unhide one extra column of buttons use the space much more efficient without being too dense
It misses some information, e.g. end times based on remaining time estimates, detailed versions currently installed, more details on sliced file being printed (not that important)
Sometimes when switching away form job status and returning, the layer time graph stays empty until page is reloaded in browser

And my personal deal breaker: I cannot access DWC from remote anymore. I always get CORS request failed.
My setup for remote access:

I have a small server in my network that can be accessed from anywhere via SSH.
This server runs a nginx that has a host duet.localhost as a proxy pass setup and only listens on loopback interface.
I then connect from my smartphone to my server via SSH and do a port forwarding -L8080:localhost:80.
I access http://duet.localhost:8080 on my smartphone's browser and get DWC - and actually the page loads but then quits with the above error and does not load any status

EDIT: I just checked and duet.localhost:8080/reprap.htm works as always.

EDIT2: what I really do like is that the Macros widget has directories listed first now.

Scachi

For a file Filament usage is shown as:
2731.8999999999996
when I hover the mouse over this value this information shows up (slides down):
$display(props.item[header.value],1,'mm');

gnydick

@dc42 browsers have a limit of the number of concurrent connections to the same domain (IP address in this case).

All the more reason to simplify.

gnydick

@wilriker didn't work

sigxcpu

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

@sigxcpu, I have come to the same conclusion that there are problems triggered by the increased number of concurrent connections that DWC2 uses. The problems are worse when there is a password set, but I get them occasionally even with no password. I've asked chrishamm if he can reduce the number of concurrent connections used. When I next work on DuetWiFiServer, I'll review the way that multiple concurrent connections are handled.

@gnydick said in [Duet Web Control 2.0.0-RC2 is ready]

@dc42 browsers have a limit of the number of concurrent connections to the same domain (IP address in this case).

All the more reason to simplify.

It is the other way around. Browsers have a too high limit of concurrent connections per domain.
Most of modern browsers have 6, which is too much compared to Duet's 4.

For example, I've recompiled the firmware with 6 HTTP acceptors instead of 4. It reloads DWC2 most of the times, with very few exceptions (i've had DWC1 open in another brower so that ate a connection).
Unfortunately, I am pretty sure that will kill the firmware during printing because increasing to 8 kills it in a boot loop.

The proper fix here should be to implement TCP connection backlogging, instead of refusing them. OK, we serve 4 simultaneout, but we can keep more intents in the backlog before accepting them. I don't know how much memory a backlogged connection eats.

I don't think users care too much about the UI load time, but we do care about it to load reliably.
Another fix is in DWC2 to compact all JS files in a single one and all CSS files in a single one.

Maybe there is a web tool to compact all these in a single "archive" whatever that is. I am a backend developer, therefore I'm not versed in all of these.

gnydick

@sigxcpu That's exactly my point. The web page code should be simplified. It shouldn't be all ajax-y for an embedded web host (with limited resources -- 4 concurrent connections) .

There definitely are minifying tools fro JS and CSS.

Ultimately, the interface is way too complex for the task. Read my rant up the thread.

Danal

This post is deleted!