Duet Web Control wishlist notes and priorities

chrishamm

Thanks for your feedback! I'm glad you like the new dark theme better than the old one.

I'll have a look at the M291 issue. The wrapping of the babystepping captions is due to the fact that + is a bit wider than - but I'll check if I can work-around it.

Edit: Indeed the connect/disconnect button is gone now. But if you want to use it from a remote machine and try to save bandwidth, you could clone my DWC GitHub repository to your computer and open reprap.htm in your browser which lets you connect to your machine too. But if you feel like this solution is not sufficient for you, I may consider adding the connect button back to the UI.

kuhnikuehnast

I like the new designs! But on a big screen I think the old arrangement of the Tools / Machine status and Temperature Chart was better. (Also the Upload & Print / Send G-Code Button). Now you have to move the mouse over the whole screen to send a g-code / change the temperature or open the menu... You don't have to click anything on the machine-status panel but this is the one directly above the settings menu...

chrishamm

I've just pushed v1.22-b2 to my GitHub repo, see https://github.com/chrishamm/DuetWebControl/blob/dev/DuetWebControl-1.22-b2.zip

It provides fixes for the issues since 1.22-b1. Please let me know if you encounter any other problems.

@kuhnikuehnast One of the criticism points for DWC was that the machine coordinates were not displayed in the top left corner like on a typical CNC machine, so I decided to move the status panel to the left. Also, the new layout in the navbar makes it easier to add OEM banners if required.

deckingman

@chrishamm I just uploaded this and cannot move any axis unless they are homed. I've ticked the check box "Allow moves if axes are not homed" and applied that setting but to no avail. Mine is a CoreXYUV if that makes any difference. I do have M564 H0 at the end of my config.g. This was working fine on 1.21.2-dc42 but doesn't work on your 1.22-b2.

Cheers

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.