Duet Web Control wishlist notes and priorities

wilriker

@chrishamm Thanks for fixing these issues and incorporating my idea about min/max MCU temp so fast. Also I like the approach of adding just more buttons to M291 dialog.

Regarding the Connect/Disconnect button: I can't believe that I will be the only one that will miss this feature. Also I do occasionally fork stuff to customize it to my needs but I prefer to stay with the original developers version as this relieves me from patching software again and again.

I found one more issue (that is probably due to adding MCU temp and requested/actual speed columns to Machine Status -> Sensors:

This is on my other monitor which is only 1280x1024.

chrishamm

@deckingman I am sorry for the confusion, the corresponding option has been removed from the move button code because I was explicitly asked to remove it. You can add M564
H0 in config.g to allow moves while the machine is unhomed, though.

Thanks @wilriker, I will have a look at this.

deckingman

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

@deckingman I am sorry for the confusion, the corresponding option has been removed from the move button code because I was explicitly asked to remove it. You can add M564
H0 in config.g to allow moves while the machine is unhomed, though.

So now I'm even more confused. To be clear, I do have M564 H0 in my config.g file. Using DWC 1.21.2-dc42 I was able to move axes without them being homed. On upgrading to your latest 1.22-b2 I am unable to move any axes unless they have been homed. Ticking the check box in DWC makes no difference.

whosrdaddy

@chrishamm : the error is in DWC...

wilriker

@chrishamm I just realized a misunderstanding regarding the saving of bandwidth. I don't want to save it by not downloading the webpage resources via the remote connection but by not having the permanent status updates in the background (when I don't need them) that can sum up to a considerable amount one wouldn't expect immediately.

That's what I used the disconnect button for. Keep the tab in the browser open but disable permanent Ajax calls. I know they slow down if the tab is not focused but they still happen - and otherwise you would no longer get the current print progress as favicon.

ShadowX

@phaedrux

Understood. But its a bit inconvenient. The majority of the code should already exist since he has a "Download as zip" file for the System Editor settings and G-code files already. If the Macros also has that function, it would make backing up the Macros much easier.

chrishamm

@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

@ShadowX It is already possible to download macro files as a ZIP bundle but the code behind does not support zipping up entire directories yet. I guess that is the reason why this option appears to be hidden for you.

Phaedrux

The List items functionality is still off. It lists every single gcode I've entered into the console and even if I delete them they just show up again on the next reload. Any new ones I purposely enter using the add gcode button don't remain after a reload either.

ShadowX

@chrishamm

Okay, that makes sense. I did have directories inside the folder to sort the different macro sets.

wilriker

@chrishamm Again thanks for coming up with fixes so quickly.

Now I only need my Connect/Disconnect button back.
Or - and that would also be OK for me - drastically reduce the AJAX calls when the tab is in the background and no print is ongoing. And by drastically I mean intervals of at least 1 minute. This could even be made a setting.
Just thinking: is the longer interval for background tabs an implemented feature or is that just what my browser (Vivaldi) does and you have no control over it?

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

Tab in foreground: selected update interval
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)
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.