Duet Web Control 2.0.0-RC6



  • @thwe yeah, this is how my V1.12 looked like, before I loaded that file. Zip file has public folder etc. Again duet3D leave us to wonder what to do. Zero clear manuals for years...



  • 99% sure Vlad uploaded the source code zip file instead of the release zip file


  • administrators

    For anyone else new to DWC2 who is having issues with it, here is some guidance.

    1. DWC2 and DWC1 can coexist on the same SD card, because they use different files. The main page for DWC1 is reprap.htm. For DWC2 it is index.html. When you enter the Duet's IP address in the brower, firmware 2.02 and later will return index.html if it is present, otherwise reprap.html. So you can force DWC1 to load by appending /reprap.htm to the IP address in your browser tab, or by deleting or renaming index.html so that it is not found.

    2. DWC2 puts more stress on the network system when loading than DWC1 did, and this exposed a bug in DuetWiFiServer 1.21. So if using a Duet WiFi, you should upgrade DuetWiFiServer to version 1.23.



  • @frank26080115 : yep he did, and being a halfass towards others isn't going to help him...



  • Sorry I am a bit late to the party but here are some comments/issues:

    • The active temperature drop-down menu was truncating the values until I did a 'command -' to zoom out one step. This is fine but there was still lots of space around the elements, and more if I dragged the window wider.
    • I don't have an ATX power supply configured, can I make that control go away?

    This is on a 2012 MacBook Pro retina, running Firefox.

    Otherwise looks very nice. I thought the ability to edit the drop-down list of g-codes on the top bar had gone away, but I worked it out and prefer this newer implementation.
    Very happy to see the continued development.
    Rob.



  • @chrishamm I found another issue. I have a macro that works a bit like G32 with no probe, i.e. it goes to several points and then presents the jog dials for Z.

    In previous versions it was only possible to press reach jog button once but that has been fixed.

    Now I have a new issue where the dialog is only shown at the first point. If I click on OK there the head moves to the next point but no dialog is shown. Switching to DWC1 immediately presents the dialog and all following. I did not try to reload DWC2 to see what happens, though.


  • administrators

    @wilriker said in Duet Web Control 2.0.0-RC6:

    @chrishamm I found another issue. I have a macro that works a bit like G32 with no probe, i.e. it goes to several points and then presents the jog dials for Z.

    In previous versions it was only possible to press reach jog button once but that has been fixed.

    Now I have a new issue where the dialog is only shown at the first point. If I click on OK there the head moves to the next point but no dialog is shown. Switching to DWC1 immediately presents the dialog and all following. I did not try to reload DWC2 to see what happens, though.

    That bug was related to the message boxes in general and it has been fixed in RC7.



  • @chrishamm When will there be a RC7 package available for download? So far I can only find up to RC6 ZIP files.



  • @chrishamm
    Hi,
    looks good as far as I can tell! (took me a while to copy it to the sd-card - 🙂 )

    1 feature-request for people with moving-plate instead of moving-head, to make the symbol of the baby steps "ambidextrous" for both parties: dc42 already included it in the latest build for the panel due (https://forum.duet3d.com/topic/10061/paneldue-firmware-1-23-now-available/8) - it are two arrows either opposing each other for closer together - or two arrows pointing away from each other for spreading apart...

    All the best! Nice work!
    -> THANKS FOR THE TIMESTAMPS on the diagramm(s)



  • @chrishamm said in Duet Web Control 2.0.0-RC6:

    So hopefully this one is really the last RC before the actual release. You can get it here: https://github.com/chrishamm/DuetWebControl/releases/tag/2.0.0-RC6

    Here once again the changelog:

    Updated NodeJs components (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 anywhere

    Let me know if any other issues come up.

    I want to report an issue, after I uploaded the config files. It doesn't prompt up and ask for the restart the firmware. However it can on version 1.x...



  • @chrishamm
    Just another little bug report:

    1. the visibility of text when using dark mode is really poor, maybe its just cause im partly colorblind, but another shade of blue would be greatly appreciated
      text visibility

    2. I love being able to select which fans are shown but after selecting my LED (configured as Fan 2, Fan0 can be selected an deselected and it works fine)
      fan slider

    3. any reason there is no option in DWC2 to show the heightmap? found it quite usefull to get my bed as flat as possible

    Edit regarding 3.: nvm i found the heightmap tab, really like that implementation!



  • Hello.
    I think that on Dashboard/Extrusion Control
    "Feed amount in mm" and "Feedrate in mm/s: " default data will be 5 and 5.
    Now is 100 and 60 - in my opinion it is not safe and not good.
    Can I save other default value in RC6?



  • @totalos

    Now is 100 and 60 - in my opinion it is not safe

    I second that! It really should be 5 and 5 at default, better to extrude too little and too slow than too much and too fast.


 

Looks like your connection to Duet3D was lost, please wait while we try to reconnect.