Duet Web Control 2.0.0-RC5

gtj0

@chrishamm Would it be possible to remove "json" from the list of webExtensions for upload purposes? Even though "json" is in the "accept" list for "/sys", when you upload a json file, either in a zip or individually, it's placed in /www. In 1.22.6, it defaults to /sys.

chrishamm

@dragonn See the other thread

@gtj0 Thanks for the note, I'll change that again

gtj0

@chrishamm said in Duet Web Control 2.0.0-RC4:

@dragonn See the other thread

@gtj0 Thanks for the note, I'll change that again

Thanks!

SupraGuy

@chrishamm Any change related to the issue where the Z jog buttons could only be used once with a manual probe while doing a G30 action? (For me, this is the only issue that I'd identified with RC3.)

chrishamm

@supraguy No it's still the same code. I tested the jog controls using a simple M291 message box before I released RC4 and it worked nicely there but I was not aware you were using a different kind of message box.
I'll remove the spinners from all the move buttons in RC5 just to be sure.

SupraGuy

@chrishamm Alas. Well, it didn't seem to pose a problem using the move axis buttons in the main control, only with the G30 probe, which has the unfortunate property of being where I might want to make several very small adjustments.

Well, I'll update to RC4 anyway.

wilriker

@chrishamm The issue did not appear when using a M291 directly but only if the jog button dialog appears as part of the Z sensor being configured as "none" and movement was required, i.e. for all bed compensation or Z height measuring methods.

garyd9

@chrishamm Thank you. Your hard work and careful attention to the needs (and whims) of users is sincerely appreciated.

samlogan87

@chrishamm I just installed the latest Web Control. I really like it. It has a nice layout.

One thing I noticed however is when you are running a Macro and it is showing the loading Icon, the size of it seems to be slightly larger than the box around the macro that is running. Not sure if that is meant to happen, but I personally don't think it looks quite right.

0_1551256752680_dbe32a39-3962-463d-8926-6e83a3861647-image.png

0_1551256561190_c551acf9-0182-435a-8824-c0e4569651fc-image.png

Other than that i haven't seen anything yet.

Kind Regards,
Sam

pkos

This is awesome. I absolutely love it. Thank you very much for your amazing work!

One question (tiny). Do you plan on maybe giving us either an option to easily change font colors?
I have a slight problems with colors it seems, because the dark theme makes a lot of text almost invisible to me - especially in gcode file selector and like here, for example with fans.

The blue fades too much into gray for me and I can't see what's written.

samlogan87

Sorry another thing, I have the print running at the moment. On my laptop which I sent the g code file through on, the active bed and nozzle temp are showing. When I access it via my phone, it says the active temp is zero not what it is actually running. It seems that it is not pulling that data through. It also says in a pop up that it cannot maintain a connection with the printer even though the position values are changing and you can see the temp moving ever so slightly as the pid control is working.

pkos

So yeah, I have to get back to this too sadly.

Every layer change, I get:
Failed to maintain connection to printer.local
Cannot set property 'firstLayerHeight' of undefined

My guess is this is attached to the problem with Slic3r PE 1.42.0 new way of storing metadata about the print that the newest Duet firmware doesn't always support yet.

I guess that because of this error also, I don't get any visibility into layer progression on the charts.
Going back to the old firmware immediately fixes that and while I still don't get information about which layer the printer is on - at least I can see progression on the chart.

deckingman

@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.

dc42

@deckingman said in Duet Web Control 2.0.0-RC4:

@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.

True; but:

Every layer change, I get:
Failed to maintain connection to printer.local
Cannot set property 'firstLayerHeight' of undefined

is a bug. RRF/DWC should not error out if the information wasn't found in the GCode file.

Martin1454

@deckingman said in Duet Web Control 2.0.0-RC4:

@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.

God dammit.... Changed from S3D to Slic3r PE due to S3D being to slow on devlopment, and now I might have to go to Cura? -.- Well, might be worth to try it with the new GUI.

pkos

I'm kinda looking forward to Pathio being the next big thing (way too feature starved at this point, but love the concept), or maybe, if S3D 5.0 is amazing - stick with that. I can't stand Cura
I chose Slic3r PE for my prints right now to get the strongest possible parts for a new HEVO, while not rattling the printer to bits with honeycomb. Gyroid is way easier on the printer.

chrishamm

Thanks for your feedback so far.

@samlogan87 Are you using any kind of scaling in your browser? It looks good to me on both Windows and Linux at 100%

@pkos I'll expand theming support in the future but for now it is limited to internal changes. Would it help to make the links in the file lists look like the other cells (e.g. black in the normal theme and white in the dark theme)? Perhaps I could change the font colors of the fan selectors to white in the dark theme too.

Thanks for reporting the disconnect problem, I'll release another RC shortly which is going to fix it.

@deckingman As long as Slic3r PE generates proper G-code I see no reason why it would become incompatible to RRF.

pkos

@chrishamm I like the idea of the blue to set it aside from regular text.
I am wondering if maybe making it a way lighter blue - so the contrast between the text and the background is bigger - would help blind people like your's truly

mudcruzr

I see the same error:

Failed to maintain connection to printer.local
Cannot set property 'firstLayerHeight' of undefined

And I'm using Cura (3.6.0)

deckingman

@martin1454 said in Duet Web Control 2.0.0-RC4:

God dammit.... Changed from S3D to Slic3r PE due to S3D being to slow on devlopment, and now I might have to go to Cura? -.- Well, might be worth to try it with the new GUI.

I use the latest dev build of Slic3R (non Prusa) https://dl.slic3r.org/dev/

It seems to be more actively developed than it used to be.

I've just downloaded the latest version although I haven't yet had time to play with it. My other version of 1.3.1 dev was dated June. This one is dated 10th Feb this year. New things I've noticed at first glance are:

"Use adaptive slicing" - automatically determine layer heights by the object topology instead of using a static value.
"Match horizontal surfaces"
"Minimum shell thickness" - Alternative method of configuring perimeters - additional perimeters and/or solid top bottom layers as necessary.
"Fill gaps"
A huge number of new options for generating support material.
Print server upload - can be set to Octoprint or Duet.

Also tick boxes for:
"Use set and Wait Gcode extruder" and "Use set and wait Gcode bed"

And it doesn't override configured acceleration settings and so forth, the way that PE does. And multi colour/material printing is still more "generic" rather than being biased towards using a Prusa style MMU.

For my particular usage case, non PE Slic3R is still by far the best slicer (but I do use mixing hot ends).