Duet Web Control wishlist notes and priorities

[DaveA]

Just installed 1.22.b3 and everything has moved. Machine status on left, temp graph on right., tool control in the middle. And I also don't have a connect button.
Is this intentional?

[chrishamm]

@phaedrux That is not surprising because you apparently did not save the settings after deleting those entries. I just checked and it does work.

@wilriker You can already do that. Just change the AJAX update interval to 60000 and it will send exactly one update request per minute.

@DaveA Yes, it is. I don't think there is any point in leaving the Connect/Disconnect button on the UI - if you want to disconnect, close the browser tab. Reconnecting will happen automatically anyway from now on.

[JoduWei]

make machine control modular! It would be nice, if i could remove, add widgets and edit widgets (every widget has its own file)

[wilriker]

@chrishamm said in Duet Web Control wishlist notes and priorities:

@wilriker You can already do that. Just change the AJAX update interval to 60000 and it will send exactly one update request per minute.

But that will reduce all AJAX updates to be 60s apart (and in background even 120s). What I would like is the following (in my case I already have AJAX update rate set to 1s interval):

1. Tab in foreground: selected update interval
2. Tab in background and print ongoing: 2x interval as selected (this is currently what I get whenever the tab is in background, i.e. 2s update interval for my settings)
3. Tab in background with no print: 60s update interval - or even paused but this may lead to not going to 2) above if a print is started another way/session

I usually keep my tabs open and in specific positions inside my tab bar (they form some kind of logical groups) and I only close tabs that I will not use for longer, so what you recommended to @DaveA would heavily disrupt my workflow.

I could also live with a configurable visibility of a Connect/Disconnect button that is invisible by default.

[dc42]

If a web client doesn't request an update for more than 8 seconds and isn't doing a file upload, it will be timed out after 8 seconds. So you shouldn't reduce the polling rate to below about once every 5 seconds, unless the automatic reconnect mechanism is working really well.

[wilriker]

@dc42 said in Duet Web Control wishlist notes and priorities:

If a web client doesn't request an update for more than 8 seconds and isn't doing a file upload, it will be timed out after 8 seconds. So you shouldn't reduce the polling rate to below about once every 5 seconds, unless the automatic reconnect mechanism is working really well.

OK, then this leaves me with my request to get the Connect/Disconnect button back as virtually the only option.

[chrishamm]

@dc42 and @wilriker I think you only need to worry about session timeouts if you have a password configured. If none is set, RRF does not deny rr_* request and thus the web interface should remain functional even with status update intervals greater than 8 seconds. And if DWC encounters multiple AJAX errors (e.g. because the session timed out), v1.22 attempts to reconnect automatically with the last entered password. I suggest you try it out and if it does not work in the way you expect, I'll consider adding back the Connect/Disconnect buttons.

[wilriker]

@chrishamm I don't have a non-default password set, so no problem on this end.
Still I would need a way to configure a separate (tab in) background update interval if no print is running. I do want my 1s-updates when tab is in foreground and I am ok with 2s-updates when tab is in background and printing. I just need this third case.

[deckingman]

@chrishamm said in Duet Web Control wishlist notes and priorities:

@deckingman Sorry for the confusion, my bad. It's fixed in 1.22-b3 which is now available here: https://github.com/chrishamm/DuetWebControl/blob/dev/DuetWebControl-1.22-b3.zip

Confirmed fixed. Thanks.

[wilriker]

@chrishamm I have to apologize. I am doing something here, that I, as a professional software developer, always complain about: I told you what I want you to implement. I'm sorry this is bad behavior.

Instead I am now going to tell you what I need in terms of functionality:
I need an (at least semi-)automatic way to considerably reduce non-printing background traffic (even down to zero).
It would be acceptable for me to push a button or to configure a setting or something similar.
It is not acceptable to me to have to change settings all the time.

I will be happy to accept whatever you implement as long as it fulfills my above description.

And just to be clear this is just a request not an order nor an expectation.

[Phaedrux]

@wilriker I'm curious how much bandwidth is actually being used. I suppose on a metered connection everything adds up.

[wilriker]

@phaedrux I'd have to calculate this again but AFAIR it did sum up to something between 1 and 2 GB per month just for the Ajax updates in my use-case. This does not include any further interaction with the Duet.
Currently I have a monthly included traffic of 10GB on the connection I need to use for this which is more than sufficient but this will drop to only 1GB in September.

[whosrdaddy]

@Phaedrux : well it consumes quite a bit, open F12 on IE or Chrome and see what I mean, on a local network this is no problem, but can be problematic on mobile...

[chrishamm]

So I've just released v1.22 of the web interface, see https://github.com/chrishamm/DuetWebControl/releases/tag/1.22 for the ZIP bundle and the full change log since the last stable version.

@wilriker This version brings back the Connct/Disconnect button too, although you need to enable it explicitly on the Settings page. I guess that is OK.

[zerspaner_gerd]

With German language setting, you can not create new system files

[gideon]

@zerspaner_gerd said in Duet Web Control wishlist notes and priorities:

With German language setting, you can not create new system files

thate is also at the dutch language settings you can not create new system files

[wilriker]

@chrishamm said in Duet Web Control wishlist notes and priorities:

@wilriker This version brings back the Connct/Disconnect button too, although you need to enable it explicitly on the Settings page. I guess that is OK.

Thank you that is totally acceptable for me!

Minor thing: in the changelog it is still listet that S2 would be added to G1 moves and that this is configurable even though this has been removed again. I know it but it might confuse users that did not follow the beta-development.

[DaveA]

Just a small nit or confusion on my part. In the G-Code Files display the file sizes are shown as KiB or MiB. I get Kilo or Mega and Byte but what's the lower case i signify?

[wilriker]

@davea said in Duet Web Control wishlist notes and priorities:

Just a small nit or confusion on my part. In the G-Code Files display the file sizes are shown as KiB or MiB. I get Kilo or Mega and Byte but what's the lower case i signify?

These are the binary prefixes, so actually this stands for Kibi Byte and Mebi Byte. This means it is based on powers of two instead of powers of ten for KB, MB, Kilo Byte, Mega Byte.

[resam]

@davea thats the difference between factor 1024 or 1000.
KiB, MiB, etc are with 1024 - which is technically the correct factor in computer science.