Duet Web Control 2.0.0-RC5

DocTrucker

I think we need to move this out of the DWC thread? I realised it may have started due to a link the the DWC.

I'll download the latest dev and confirm that's still the way its done after ordering a few bits...

Edit: I'll start a new thread: - https://forum.duet3d.com/topic/9378/slicer-based-dynamic-acceleration-control

DocTrucker

The posative is that RC5 is much more stable than RC4.

The area to work on is the text entry bug. It keeps ocuring. I have to close my browser tab and reopen to clear it, F5 or ctrl F5 doesn't cut it.

appjaws

@doctrucker I can now add temperatures after a reload of DWC

appjaws

@appjaws still missing even after a reload of DWC

kraegar

RC5 is more stable than RC4 for me, but the files menu is now more annoying with the single click / double click mechanics. And I can't find any way to navigate back up in the directory tree, other than to refresh the page.

NicoLab28

Keyboard issues (arrows and others) in the editor
Print time wrong under S3d, tells me 1h 0s instead of 1h 35m
No print time, after printing, when you arrive late.
The time of the simultation not updated.

Bug on the selected tool, it appears in dark mode, but not in light. I still have not validated everything, but it seems that in dark mode, it always displays tool 0 even unsorted.

chrishamm

I just figured out why the inputs stop working, it's due to an update of the 3D library THREE that somehow blocks keyboard inputs once an instance of it is created. I will provide RC6 with a downgraded version of THREE later today.

@appjaws said in Duet Web Control 2.0.0-RC5:

The connect / disconnect button is missing

At the moment the Connect / Disconnect button is only available when running from localhost. I will add an option as soon as multi-machine support has been fully added (should be no big deal since the backend is already finished).

@wilriker said in Duet Web Control 2.0.0-RC5:

@chrishamm: one thing that I always do and that never works - but worked in DWC1 - is to use ESC to close the editor without saving.

Good point, I'll add this again in RC6.

@garyd9 said in Duet Web Control 2.0.0-RC5:

@chrishamm
Very minor issue with Duet Web Control 2.0.0-RC5:

The interface shouldn't give the option to "simulate file" or "start file" while it's already simulating a file. (It also should disable those options if a print is already running, but I didn't check that.)

or

If disabling the options isn't possible, it should pop up the resulting duet error message ("Error: M37: cannot simulate while a file is being printed")

Good point, these options will be hidden in RC6 if a file print is in progress.

@kraegar said in Duet Web Control 2.0.0-RC5:

RC5 is more stable than RC4 for me, but the files menu is now more annoying with the single click / double click mechanics. And I can't find any way to navigate back up in the directory tree, other than to refresh the page.

You can go up by clicking on the links that are displayed above the file list once you enter a sub-directory. I understand the concept of click/double-click needs to be changed for touch devices (which I will do in RC6) but what's the problem with activating items via double-click on a standard PC?

@nicolab28 said in Duet Web Control 2.0.0-RC5:

Keyboard issues (arrows and others) in the editor
Print time wrong under S3d, tells me 1h 0s instead of 1h 35m
No print time, after printing, when you arrive late.
The time of the simultation not updated.

Bug on the selected tool, it appears in dark mode, but not in light. I still have not validated everything, but it seems that in dark mode, it always displays tool 0 even unsorted.

Thanks for the bug report concerning the active tool highlighting, it will be fixed in RC6. Are the keyboard issues related to the height map problem I mentioned? The print stats will remain on the jobs page after a print finishes in RC6.

wilriker

@chrishamm said in Duet Web Control 2.0.0-RC5:

but what's the problem with activating items via double-click on a standard PC?

Mainly because we are all used to using single-clicks to open the editor/start the print.

NicoLab28

@chrishamm said in Duet Web Control 2.0.0-RC5:

Are the keyboard issues related to the height map problem I mentioned?

I was not in the heightmap, but in the macro editor. But I may be open at one point the heightmap.

I also noticed that I could not edit gcode anymore in the top bar. Neither do F5, I had to close the window for it to work again. So it's probably the same problem.
I must say that the DWC window is open 24/24, by the way, when I turn off the printer, and that I turn it on, the temperature curves are extremely long, it seemed to me that it resynchronized on the last minutes.
To check that library three.js do not have this problem too.

AlexLin

@wilriker yeah first couple of times I was annoyed but you get used to it. And it probably more common to select with one click and open/print with 2..

kraegar

@chrishamm Might be a personal thing. I find it unintuitive.

The "go up a directory" wasn't appearing for me previously, but is now. May have been due to a restart being needed or something odd.

garyd9

@chrishamm

More feedback on RC5 (used with Chrome 72.0.3626.119 on 64-bit windows):

Every now and then (and I can't seem to figure out steps to repeat) aspects of the UI stop working or disappear. Two areas I've seen so far:

The ability to move to a parent directory in the "G-Code Jobs" (the navigation breadcrumb disappears.)
The ability to manually type a heater temperature. (The drop down works to change temp, but clicking/highlighting the active temp and typing a new temp doesn't work - the page doesn't seem to see any keystrokes.)

Edit: Both of the above two issues can be resolved by reloading the page (F5 on Win10/64.)

Another issue which is disturbing is that the page doesn't update when it's not in the foreground. To be specific, with Chrome 72.0.3626.119 on 64-bit windows, if I have DWC2 in a tab, and another page in another tab - DWC only updates if the DWC tab is in front. This results in the title of the page (which shows the percent complete) NOT updating. Once the DWC tab is brought to the front, DWC plays "catchup" with any graphs and percentages. (It's actually amusing to watch.)

DWC1 would update even if not the foreground tab (which meant I could at least monitor the percent complete of a print job while doing things in other tabs.)

ctilley79

@deckingman said in Duet Web Control 2.0.0-RC5:

@pkos Unfortunately, Prusa version of Slic3R is becoming more and more biased towards it being used with Prusa firmware and every release sees this integration becoming tighter and tighter.

So should we expect RepRap firmware to be changed to support a specific slicer? To my mind, the slicer should be firmware agnostic but Prusa Slic3R has started doing things differently.

I disagree with this statement. For example, they added the option to upload directly to a Duet WiFi from within slic3r pe. Not sure how your statement is in the least bit accurate.

Phaedrux

@ctilley79 the upload to duet feature was a contribution from a forum user here. They didn't expend much energy to bring you that.

I think most of the difference is because Marlin is just so pervasive. Not only do their own printers run Marlin but so does the majority of other users printers.

garyd9

Some more minor RC5 issues:

When printing something that hasn't been simulated, "Current Job - Status" shows a time estimate based on simulation. (I'm guessing that it's actually showing the useless time WAG that my slicer generates? Is so, should the label be "based on slicer" instead of "based on simulation"?)

While simulating a print, "Current Job - Status" is showing an estimation "based on simulation." (Again, I'm guessing that this number is actually based on the slicer WAG if the file hasn't been simulated before.) Even if there was an accurate simulated time in the gcode file, this number should be BLANK while simulating (as it can't possibly make sense.)

samlogan87

@chrishamm I think I have found another issue. I don't remember if this did it in the v1 DWC but if a job finishes, the baby stepping doesn't clear. It seems that when you relevel your bed and do not clear the baby stepping, it sets the zero point at the particular baby stepping height and you need to baby step down again to suit the print.

DocTrucker

@samlogan87 Think that's a firmware rather than DWC issue. There's been some discussion about it recently.

I've still got to get my head around why baby stepping exists rather than just having a wrapper around say 'G10 P0 Z...' for the first tool.

deckingman

@ctilley79 said in Duet Web Control 2.0.0-RC5:

@deckingman said in Duet Web Control 2.0.0-RC5:

@pkos Unfortunately, Prusa version of Slic3R is becoming more and more biased towards it being used with Prusa firmware and every release sees this integration becoming tighter and tighter.

So should we expect RepRap firmware to be changed to support a specific slicer? To my mind, the slicer should be firmware agnostic but Prusa Slic3R has started doing things differently.

I disagree with this statement. For example, they added the option to upload directly to a Duet WiFi from within slic3r pe. Not sure how your statement is in the least bit accurate.

Fair enough. You are entitled to your opinion. Mine is based on certain facts so I'd be interested to know what yours is based on. Let's leave aside the upload to Duet feature because that's common to both versions of slic3r and as @Phaedrux pointed out, the request for that integration originated here on these forums, not from Prusa.

I use mixing hot ends. So I might have say a 5 colour Diamond hot end with 5 filaments fully loaded at all times, each filament being driven by a single extruder. A tool can use any number of these extruders so for example to produce say Orange, I can mix Red and Yellow. Or if I wanted say dark Green, I might use Blue, Yellow and Black. And so forth.

So having 10 or more tools defined is not unreasonable. Plain "vanilla" slicr3r" doesn't care about this. For multi coloured objects, I can assign any tool number to any part. Even tool number 9,999 if I wanted to. All the slicer has to do is insert the correct tool number at the appropriate point in the file, which "vanilla" slic3r does admirably well.

Prusa printers don't have mixing hot ends. For multi colour printing, they use their own MMU unit. So the concept of mixing hot ends is alien to Prusa and they have disabled some of the features of slic3r in their version. For example, Prusa slic3r won't allow me to assign any tool to an object part if that tool number is greater than the number of extruders defined in the printer profile. It assumes that every tool must have a single extruder - not only does it assume that - it forces me to set up my printer that way. So if I want to assign say tools 3, 7 and 9 to parts of an object, I'd first have to define a printer profile with 10 extruders even though only 5 physically exist. Then to make matters worse, the slicer can put filament specific commands into the gcode file. But for that to work, every tool has to have a single filament assigned to it and every fiaments has to have a "profile".

So if I define a tool as say tool 15, I don't need to do anything differently using "vanilla" slic3r. If I want to use that on PE Slic3R, I'd have to define a machine with 15 or more extruders, and the set up filament profiles for 15 different filaments, even though they may all be combinations of the same PLA.

So, in my opinion PE Slic3R is becoming too biased towards Prusa printers and I continue to hold that opinion.

fma

@deckingman said in Duet Web Control 2.0.0-RC5:

So, in my opinion PE Slic3R is becoming too biased towards Prusa printers and I continue to hold that opinion.

I agree. Another annoying example: if you choose Marlin as flavor, it always set speed/accel/jerk params defined in Slic3rPE...

But this does not mean that a slicer and a firmware teams should not work together: I think it is mandatory to introduce new robust features. And it is possible to do it without breaking compatibility with other firmwares; it is just a matter of options to turn on/off.

And once these features are there, other firmware teams may add them.

deckingman

@fma Yes. It'd be nice to see the Duet team, or someone closely allied to them, write a slicer. I wouldn't be at all averse to using a RRF specific slicer - one that is actually tailored specifically to our firmware and which would evolve as the firmware continues to do.