Duet Web Control 2.0.0-RC6
-
@chrishamm
small bug:
I added a chamber heater with some fans on it.
This fan is created with that commands:M307 H3 A-1 C-1 D-1 M106 P3 S0 I0 F100 H-1 B0.5 C"Chamber" A3 L0.23; Heated chamber fan
And it doesn't show up when I select it in visibility
-
-
This is great! I was considering forking and doing a more modern UI.
Will test and write back with any issues
-
@chrishamm said in Duet Web Control 2.0.0-RC6:
@garyd9 You can hide the navigation menu by clicking on the button in the top left corner. That is supposed to happen automatically when the screen width becomes too low. Can you tell me what resolution you use on your MBP?
1440x900. (It's an older MBP.)
Take care
Gary -
Hello,
I commented on an earlier release of DWC, I believe RC4 or 5? Anyway, my issue was that the height map was storing correcting and applying software correction to my print, but the image of the height map would not display.
It turns out this was due to the browser I was using! Apparently Brave (a browser based on chromium that natively blocks ads/popups/trackers) does not allow for that image to refresh or display for some reason. When I pulled up DWC with Firefox it displayed perfectly fine.
-
A minor note - is the Fan RPM reading gone for good? There seems to be no way to either toggle or display it in DWC 2.
-
@mike I miss that as well. Jumped through all the hoops to read it out and no it's no longer displayed - I would very happily treat it for the Z probe value since I do not even have a Z probe.
-
Feature request / idea: temperature of heater in degrees or percent o taget temp in the title/heading.
So when a print is started I can se the progress of heating up, then when the printing starts it switches to print progress as of today.
Great new GUI, keep up the good work!
-
@chrishamm said in Duet Web Control 2.0.0-RC6:
mponents (also fixes a bug that caused all inputs to stop working once the heightmap was activated)
Changed click behaviour of file list items to be activated on a single click again
Added touch events to event+file lists to show the context menu on devices that do not support the native JS contextmenu event
Print information is no longer cleared when a print finishes
Simplified file list reset when the connection is interrupted
Print+Simulate options are hidden when a job file is being processed
Escape closes the text editor again
Height map is automatically reloaded once 'heightmap.csv' shows up in a G-code response
Minor other changes
Bug fix: Notification when editing a large file was not displayed during download
Bug fix: Macro list did not return to the root directory when the connection was interrupted
Bug fix: Warm-up time was not displayed
Bug fix: Selected tool was no longer highlighted when the light theme was selected
Bug fix: Drag&Drop was completely broken in Chrome and the drag animation stopped working anywhereFor me drag and drop in chrome is still not working. It always shows me the opended gcode
-
Agreed - in Chrome or Safari on my Mac, drag and drop to drag files from my desktop to the GCode files directory does not work.
@smoki3 said in Duet Web Control 2.0.0-RC6:
For me drag and drop in chrome is still not working. It always shows me the opended gcode
-
@johnocfii yes I am only on mac.
@chrishamm I also noticed that I can not move the cursor my the arrow keys in the editor
-
I looked everywhere but can't find Machine Properties to endstops ecc.
Also is it possible to make the webcam image fill the space?
In DWC2 the cam image takes much longer to loads than the old interface.Thanks
-
At the risk of asking a dumb question, What is the minimum Duet 2 Maestro firmware I should be running before installing the Duet Web Control 2.0.0-RC6 firmware? (I think I'm on RC5 of the Web Control, but I am not in front my printer right now. I suspect that my Duet 2 Maestro firmware is 2.02, but I would verify that before applying any Duet Web Control firmware upgrade.
-
@quarky42 2.02 and DWC 2RC6 will be fine together
-
i think "show mesh bed compensation" map is missing in "compensation & calibration"
-
moving speed slider to "1" generates error message - M220 S1 invalid speed factor
i think there should be a simple check - if speed is below 1, speed = 1 this should be done before sending speed to firmware.
-
suggestion to the time estimation section... too many words now and not easy to read
-
add words based on after "Estimations" --> "Estimations based on:"
-
remove these words afterwards
"Based onfilament usage" ---> "...filament usage" -
change color of list items OR color of data: "filament usage" can be white and time value can be light yellow or other non-white color
-
-
@c310 said in Duet Web Control 2.0.0-RC6:
i think "show mesh bed compensation" map is missing in "compensation & calibration"
height map has no use in main menu.
-
This is just gorgeous!!! Congratulations!
Thank you very much!
-
The Slicer or simulation time estimations showed during print starts counting during warm-up time.