Duet Web Control 1.17 RC

chrishamm

I have just created a new 'dev' branch on my GitHub repository for Duet Web Control where I provide my latest development version, see https://github.com/chrishamm/DuetWebControl/tree/dev

If you own a Duet WiFi and want to give it a try, you have to update to either David's or my latest RRF 1.19 beta. if you are upgrading from 1.18.1 or older, please see https://duet3d.com/wiki/DuetWiFiFirmware_1.19beta for further information. Our latest DuetWiFiSocketServer versions should be fully compatible, so it won't matter if you install dc42's or mine as long as it is the latest version.

Quite a lot of things have changed since DWC 1.16 so I'd be happy to hear your feedback. The most notable change is the new file table design. You can now select multiple files, move, delete, and download them as a ZIP package by right-clicking on them and double-click entries to perform the associated primary action.

For those who are interested here the complete changelog since v1.16:

Added new Tools panel which will supersede the old Heaters panel in the next version
Refactored major parts of the Heaters panel
Added new Filaments page

Filaments can be created on the new page

Right-clicking entries allows load+unload macros to be modified

When clicking on tools that have only one extruder assigned, a popup is shown that lets users load, unload and exchange the current filament (requires RRF 1.19 or later)
Implemented support for custom extra temperature sensors:

Added new Extra panel to provide a list of the extra sensors

Extra temperatures can be optionally monitored on the chart

These temperatures on the chart are displayed as dashes
Greatly improved file tables:

Allow items to be sorted by clicking on the headers

Multiple items can be selected, moved via drag&drop and deleted or downloaded as ZIP

Added support for double-clicks

Implemented new logic for context menus (open via right-click)
Allow bed heater to be remapped to any other heater
Added support for M291+M292 (show+confirm/close message box, only RRF 1.19 or later)
Removed dependencies on the "axes" and "heads" fields of the HTTP status response
Added support for 3 more axes (ABC)
Grouped "Make new" buttons on the Macros page
When "config.g" is uploaded via the edit function, "config.g" is moved to "config.g.bak" first
Enhanced Tools tab on the Settings page and allow tools to be named
Improved status loop and chart performance
Updated JSZip library to the latest version
Added all missing German translations
Bug fix: Sometimes XY points in the 3D view weren't mapped correctly
Bug fix: G-Codes Files didn't display contents of second SD card after mounting
Bug fix: Main content was scrollable even though not enough space was available
Bug fix: Occasionally after reconnecting the macros weren't properly loaded

Please let me know how you like it and if you experience any problems with it. If no more problems show up, I will release the final version 1.17 by the end of this week.

Hergonoway

great news ! Already trying it.

Do you think that you'll add a plus/minus 1/2/5% or open field option for sliders (extrusion, fan speed, etc) in a near futur ? last time I wanted to add the extrusion to 102% on my smartphone, ended at 150% without being able to catch 100% again

Guyaros

Hi Chrishamm,

What's the best method to update to the new DWC version ?

As far as I know, I should copy the DuetWebControl-1.17-RC6.zip content to /WWW folder on the Duet microSD card.
(In case the /WWW folder is already exists it is recommended to delete if first)
and then power the board, and thats it, no M997 command is needed ?

In the previous DWC, I used to upload only the DuetWebControl-1.xx.bin and then accept to install.
simple and easy, without the need of removing the microSD card.
Is it possible to install the new DWC version without removing the microSD card from the Duet ?

My current software information:
Firmware Name: RepRapFirmware for Duet WiFi
Firmware Electronics: Duet WiFi 1.0
Firmware Version: 1.19beta9 (2017-07-10)
WiFi Server Version: 1.19beta9
Web Interface Version: 1.16

Thanks,

DjDemonD

Just installed it now. Very good. Like the dark theme especially, don't know if that's new but if it isn't I must have overlooked it before.

I'd second Hergonoway's suggestion to maybe add a text entry field for extrusion/fan etc.. if possible so we can type 102 rather than use a slider. It works fine on windows desktop, but on my 7 inch tablet I use as a touchpanel for one machine its a bit fiddly.

But great work. Thank you

DjDemonD

I notice the processor temp has disappeared from the main page. That was a useful thing to have displayed as it gave an indication at least of how hot the duetwifi card was generally. I know we can display it as a dummy tool instead. Is that the intention? to remove it as it can be added if required?

Edit - I see it has been moved to the tools panel under extras. And an option to add it to the temp. graph - nice!

fcwilt

Hi,

I'm baffled.

I am running the 1.19beta9 firmware on my DuetWifi.

I've tried everything I can think to update to DWC 1.17 but I am stuck on version 1.15a.

I removed the SD card, deleted the www folder, created a new www folder and extracted DuetWebControl-1.17 RC6.zip to that folder.

No change.

I copied DuetWebControl-1.17 RC6.zip to DWC.zip and was able to upload from the current DWC. It listed a number of different files being processed.

No change.

So what am I doing wrong?

Thanks.

Frederick

whosrdaddy

@fcwilt, did you restart your browser?
I had the same issue as you until I completely restarted my browser (Chrome).
It is most certainly a caching issue

fcwilt

@whosrdaddy:

@fcwilt, did you restart your browser?
I had the same issue as you until I completely restarted my browser (Chrome).
It is most certainly a caching issue

Hmm…

Didn't think of that - will have to give it a try.

Thanks.

Frederick

fcwilt

As suggested by whosrdaddy I needed to restart Chrome and now DWC is reported as 1.17.

Thanks.

Frederick

MrBlom

How about . order by date on the sd card contet list . so the latest file is on top

DADIY

Will this also be released for Duet 0.6?

Also, can the time bug be fixed when viewing the files on the SD card, I quite often see the minutes truncated in the generated by column, for example -

Slic3r 1.35.5-prusa3d-win64 on 2017-07-12 at 11:5

But the gcode file contains

; generated by Slic3r 1.35.5-prusa3d-win64 on 2017-07-12 at 11:57:44

chrishamm

@Hergonoway:

Do you think that you'll add a plus/minus 1/2/5% or open field option for sliders (extrusion, fan speed, etc) in a near futur ? last time I wanted to add the extrusion to 102% on my smartphone, ended at 150% without being able to catch 100% again

The slider works nicely on my smartphone and I can actually control it with +-1-2% accuracy, which is sufficient for my purposes. If more people request this, I can have a look at that though.

@Guyaros:

What's the best method to update to the new DWC version ?

Older DWC versions may complain about DuetWebControl*.zip being incompatible with the Duet WiFi. Hence I suggest to rename the ZIP archive to DWC.zip and to upload it once more. That should work.

@MrBlom:

How about . order by date on the sd card contet list . so the latest file is on top

I have an idea for that. What if we truncate the "Generated by" field and display it next to the filename? Then we would get enough space to display the "Last modified" field in the G-Code files list.

@DADIY:

Will this also be released for Duet 0.6?

Also, can the time bug be fixed when viewing the files on the SD card, I quite often see the minutes truncated in the generated by column, for example -

Slic3r 1.35.5-prusa3d-win64 on 2017-07-12 at 11:5

But the gcode file contains

; generated by Slic3r 1.35.5-prusa3d-win64 on 2017-07-12 at 11:57:44

It should be fully compatible with the Duet 0.6, but I haven't tested it on that board yet. If we go with the last proposal, this bug wouldn't matter any more. I'll ask T3P3 what they think about that.

chrishamm

Thanks everyone for your feedback! I have just released DWC 1.17 on my GitHub repository. The latest version includes initial support for HTML5 desktop notifications (aka push messages) too.

whosrdaddy

Small question:
I have uploaded 1.17 to the printer (upgrading from 1.17RC6) and now the printer asks to reload the page.
I can't remember seeing this dialog when I upgraded from 1.16, is this also new?

deckingman

Just updated to 1.17. Saw something labelled "Filaments". Didn't know what it did so I clicked on it and got a message to the effect that filament was empty or there were no filaments or some such. Saw a button labelled create new filament so I clicked on that and was asked to give it a name. Typed PLA in the box, hit return and got the following Java script error.

A JavaScript Error has occurred so the web interface has closed the connection to your board. It is recommended to reload the web interface now. If this happens again, please contact the author and share this message:

Message: Type Error: dateCreated is : undefined
URL@ http://192.168.1/119/js/dwc.js
Line: 2599:6
Error object:{}

Now it's completely bricked. I've cycled the power to the printer. Closed Firefox. Restarted everything but cannot connect to the printer. All I get is the JavaScript Error above.

What now?

deckingman

Update.

I managed to get back to the situation where I can at least connect again. To cut a long story short, I ended up deleting the folder "Filaments" which had appeared in the sd card. Deleting the file "PLA" that I tried to create didn't work - I had to delete the entire folder, even when it was empty. So now at least I can connect. If I click on the "Filaments" section, there is just a blank page "Failed to retrieve filaments but as I have no idea what this new "Filaments" feature is, or what it's supposed to do, I'll leave well alone.

Forgvn77

Deckingman, thanks for posting your fix. I ran into the same problem after I defined a couple filaments and then it started disconnecting all the time.

deckingman

@Forgvn77:

Deckingman, thanks for posting your fix. I ran into the same problem after I defined a couple filaments and then it started disconnecting all the time.

No worries. Do you know what defining filaments is actually supposed to do or be used for?

fcwilt

@deckingman:

@Forgvn77:

Deckingman, thanks for posting your fix. I ran into the same problem after I defined a couple filaments and then it started disconnecting all the time.

No worries. Do you know what defining filaments is actually supposed to do or be used for?

I tried it recently - too recently to know if it has issues.

But it does a couple of nice things. It allows you to associate a filament with a tool and, if desired, specify filament load/unload G-code.

On the web interface you can assign a filament to the tool and the name of the filament shows on the web page under the tool.

If there is defined G-code for loading that filament it executes.

And when the filament is unassigned from the tool if the is defined G-code for unloading that filament it executes.

Frederick

deckingman

Ah OK. That could be useful. How did you go about setting it up? I didn't get beyond pressing the "create new filament" button and giving it a name before it threw a wobbly.