Duet WiFi - User Interface

jmshep

If I make changes in the user interface and click apply, the changes take place but if I close and then reopen the program all settings go back to default.
E.g. I am trying to configure a web cam, I can enter the settings but the next time I open the control panel they have disappeared. The same thing happens with other settings such as fan controls etc.
If I try to clear the cache I get a 'no entry sign' as well.
I have reloaded both the latest Duet firmware and the web interface firmware (both V2.1) and there is no change.
Can any one help please.

dc42

Chrishamm can answer this better than I can, however I know that DWC uses HTML5 local storage to store the settings. So make sure that it is enabled in your browser settings. Some browsers use the cookies on/off setting to enable/disable HTML5 local storage too.

jmshep

I normally us Chrome and have reset the settings to defaults and also tried using Edge and still get the same results as before.

Danal

The free chrome plug-in "Local Storage Manager" may help give you insight as to what is going on.

jmshep

I have downloaded the suggested extension and can see that the settings data is recorded but not retained when the Duet interface is closed down. I have also deleted the Chrome default profile and allowed it to build a new one but the problem still persists. (the option to clear data on close down in Chrome settings is not enabled).
Any other suggestions welcome.

dc42

Perhaps you have disabled cookies?

Phaedrux

Can you try creating a new user profile on your computer and testing from that account?

Danal

Try:

chrome://settings/content/cookies

In the omnibox. Even though it says "cookies" there are settings on that page that affect local data as well. They are fairly self explanatory.

MSquared

@dc42 Just curious is there a reason that the settings are not persisted to the SD card?

resam

@msquared The next DWC release will do exactly that:

DWC settings are uploaded to and downloaded from the Duet board by default

https://github.com/chrishamm/DuetWebControl/commit/a0b0a18733ae75b63e7c286e454b8d2713bec35e

0

chrishamm committed to chrishamm/DuetWebControl

Version 1.21.1-b1

Added new 'O' status character to indicate that the machine has been turned off
Added support for 9 total fans whose visibility is set via the new
'controllableFans' bitmap field of the advanced status response
Implemented more granular control of pop-up notifications and made them wider on small devices
If a JavaScript error occurs, the message is no longer closed when the connection is re-established
Spindle RPM of multiple tools can be set (requires RRF 1.21.1 or later)
JSON files are automatically opened via the text editor when double-clicked
Clicking on heater links activates them, then puts them into standby mode and eventually turns them off
DWC settings are uploaded to and downloaded from the Duet board by default
More OEM enhancements

dc42

There are advantages and disadvantages to both approaches. You might want to use different settings on a smartphone or tablet compared to a PC, and with the settings stored on the SD card, you won't be able to do that.

jmshep

OK I Have tried most of the suggestions and checked settings again. I toggled all relevant settings in Chrome on and off and deleted all the cookies and tried again. Now I can see the Duet cookie in Chrome settings and if I make changes to DWC, apply settings and then close Chrome and re open DWC, the settings are retained BUT just one time!

dc42

Are you sure you don't have "Keep local data only until you quit your browser" enabled in Chrome?