Bed temperature dropdown does not match setting
-
@Phaedrux Sorry I forgot to mention... 3.5.3 both
-
@phoenix it's probably an issue with dwcsettings.json in the system folder. Try deleting it and trying again
-
@jay_s_uk thanks - deleted the file but it came back the same way
-
@phoenix you can check what they're set to in the settings tab. I think it's the machine specific one
-
@jay_s_uk The first screenshot in my original post shows the Machine Settings Tab: on the bottom you see the presets (90 / 85 / 65 / 60). The dropdown (250 /235 / 220 /205 / 195 / 160 / 120 ) is what I get as choices when I go to set Bed temperature
-
undefined Phaedrux moved this topic from General Discussion
-
One for @chrishamm I think.
-
I see the same problem and only with bed temperature. Deleting cookies and the dwc settings file and trying different browsers sometimes removes the error but it has always come back...
-
@Simonjb @pheonix Can you try:
- Renaming sys/dwc-settings.json to something different (eg .old on the end)
- Reload/refresh the browser, then check settings, and see if new sys/dwc-settings.json has been created.
- Edit something, eg add another temperature in Settings > Machine-specific > Tool temperatures to create a new dwc-settings.json.
- Check if new sys/dwc-settings.json has been created, and if settings stick.
Otherwise, it may be something hung over from a previous DWC install in the www folder. Edit the www folder on a PC: rename or delete it, create a new one, and unzip the contents of the DuetWebControl-SD.zip from the matching firmware version into it, then test. Check the sys folder for any other .json files kicking around, rename/move/delete them too (except for configtool.json, which is for the RRF config tool). If you find anything odd, please post.
Ian
-
Hi, sorry for the late repost here, as you can see, it also affects SBC mode. It probably has to do with the client it's connecting to. As you can see, in PrusaSlicer (whatever they use for connecting to the printer) the issue shows without fail. However, on Firefox Desktop, it works just fine
However, on Firefox Android, the bug happens again
Just like Firefox on Android, chrome also does it too
-
@Ballador I've just tried this using a recent 3.6 (standalone) build. Works fine for me on Chrome on Windows 11, ChromeOS (Asus Chromebook) and Android (Pixel 7a). Not suggesting you should switch to 3.6, just providing another data point.
