Duet Web Control 1.17 RC
-
As suggested by whosrdaddy I needed to restart Chrome and now DWC is reported as 1.17.
Thanks.
Frederick
-
How about . order by date on the sd card contet list . so the latest file is on top
-
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
-
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.
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.
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.
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.
-
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.
-
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? -
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?
-
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.
-
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, 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?
-
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
-
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.
-
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.
"Wobbly" - that's awful - I think - what's a "wobbly"?
I was getting ready to test a new install of a Diamond 3.
I created a filament for each color I was going to use naming each according to actual filament color: RED, YELLOW, BLUE.
Then I assigned each newly created filament to each tool.
During testing it was nice to be sure I was selecting the correct tool since the color of the filament was displayed.
Frederick
-
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?Yes, that's sort of new. It's more convenient to test changes when the web interface reloads automatically.
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?
Thanks for your report, I've just fixed this problem in v1.17+1 - see https://github.com/chrishamm/DuetWebControl/blob/master/DuetWebControl-1.17%2B1.zip.
The web interface had a problem with filament directories that did not have a valid "last modified" attribute, but it should be fixed now.Using the new Filaments feature you can automate your filament load+unload process and set the required temperatures, fan values etc. in the load+unload macros. They can be edited by right-clicking on the items of the Filaments page.
-
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?Yes, that's sort of new. It's more convenient to test changes when the web interface reloads automatically.
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?
Thanks for your report, I've just fixed this problem in v1.17+1 - see https://github.com/chrishamm/DuetWebControl/blob/master/DuetWebControl-1.17%2B1.zip.
The web interface had a problem with filament directories that did not have a valid "last modified" attribute, but it should be fixed now.Using the new Filaments feature you can automate your filament load+unload process and set the required temperatures, fan values etc. in the load+unload macros. They can be edited by right-clicking on the items of the Filaments page.
Nice, cant wait to finish building my wifes new craft studio so i can get back to the printer and try it out.
Any chance the upload button got fixed to filter out stl files?
-
Thanks for your report, I've just fixed this problem in v1.17+1 - see https://github.com/chrishamm/DuetWebControl/blob/master/DuetWebControl-1.17%2B1.zip.
The web interface had a problem with filament directories that did not have a valid "last modified" attribute, but it should be fixed now.Using the new Filaments feature you can automate your filament load+unload process and set the required temperatures, fan values etc. in the load+unload macros. They can be edited by right-clicking on the items of the Filaments page.
Hi Chris,
I'm pleased to report that it works fine now. I'd also like to say thank you for this feature which will be useful with my Diamond hot end.
This is probably too complicated but it would be kind of nice if I could assign multiple filaments to tools that use multiple extruders. e.g. if I had Tool defined which used two extruders, then it would be nice if I could show both the filaments (colours) that were assigned to it. As I understand it, I can only assign single filaments to single extruder tools. As I said, it would be nice to have but no bg deal if it's too complicated to do.
I have another little glitch to report to you I'm afraid. When I used the system editor to edit my config.g to create a virtual heater using M305 and give it a name, after saving config.g and rebooting Duet, DWC failed to connect and I got the following JavaScript Error…..........
Meesage: TypeError: lastStatusResponse.temps.extra "square bracket,i,square bracket" is undefined (had to type that long hand otherwise it looks like a single italic)
URL: http://192.168.1.119/js/dwc.js
Line: 1079:1
Error object:{}This only happens once. That is to say, after receiving the message I hit "Connect" and everything is fine again and the virtual heater shows up in the "Extra" tab as expected.
Ian
-
….............
"Wobbly" - that's awful - I think - what's a "wobbly"?
............................Frederick
Yes, sorry. You need to be a native English speaker to know what that means. It's usually applied to people. I don't know if you are married but if you are and you do something that really upsets your wife, she'd likely start shouting and waving her arms about - that's throwing a wobbly.
-
Thanks for your report, I've just fixed this problem in v1.17+1 - see https://github.com/chrishamm/DuetWebControl/blob/master/DuetWebControl-1.17%2B1.zip.
The web interface had a problem with filament directories that did not have a valid "last modified" attribute, but it should be fixed now.Using the new Filaments feature you can automate your filament load+unload process and set the required temperatures, fan values etc. in the load+unload macros. They can be edited by right-clicking on the items of the Filaments page.
Hi Chris,
I'm pleased to report that it works fine now. I'd also like to say thank you for this feature which will be useful with my Diamond hot end.
This is probably too complicated but it would be kind of nice if I could assign multiple filaments to tools that use multiple extruders. e.g. if I had Tool defined which used two extruders, then it would be nice if I could show both the filaments (colours) that were assigned to it. As I understand it, I can only assign single filaments to single extruder tools. As I said, it would be nice to have but no bg deal if it's too complicated to do.
I have another little glitch to report to you I'm afraid. When I used the system editor to edit my config.g to create a virtual heater using M305 and give it a name, after saving config.g and rebooting Duet, DWC failed to connect and I got the following JavaScript Error…..........
Meesage: TypeError: lastStatusResponse.temps.extra "square bracket,i,square bracket" is undefined (had to type that long hand otherwise it looks like a single italic)
URL: http://192.168.1.119/js/dwc.js
Line: 1079:1
Error object:{}This only happens once. That is to say, after receiving the message I hit "Connect" and everything is fine again and the virtual heater shows up in the "Extra" tab as expected.
Ian
Thanks, I found the bug and will fix it in my next release.
At the moment filaments are mapped per extruder drive, so you will be able to use filament counters etc. (of course as soon as that is implemented in the firmware) with your diamond hotend as well. However for the load+unload macros it really makes sense to run them in the context of a single extruder drive, so you will have to define individual tools per extruder drive to load+unload different materials.
-
Thanks, I found the bug and will fix it in my next release.
At the moment filaments are mapped per extruder drive, so you will be able to use filament counters etc. (of course as soon as that is implemented in the firmware) with your diamond hotend as well. However for the load+unload macros it really makes sense to run them in the context of a single extruder drive, so you will have to define individual tools per extruder drive to load+unload different materials.
Yes, that all makes perfect sense. Thanks again for what you've done so far - my interface is looking so much neater now that I don't have to use dummy tools to display the temperatures of various thermistors that I have stuck in various places around the printer.
-
Have we got an answer on whether the latest DWC can be installed via DWC or is it a case of remove memory card and install it manually?
