Firmware bundle 3.3beta2 released
@dc42 FIRMWARE_NAME: RepRapFirmware for Duet 3 MB6HC FIRMWARE_VERSION: 3.3beta2 ELECTRONICS: Duet 3 MB6HC v1.01 or later FIRMWARE_DATE: 2021-03-10 13:39:39
Duet TOOL1LC firmware version 3.3beta2 (2021-03-10 10:06:22)
Duet Web Control 3.3.0-b2
PrusaSlicer 2.3.0 + win64
Layer Chart, layer count and Time estimates don't update.
Are you using SBC or stand alone mode? see https://github.com/Duet3D/DuetWebControl/releases/tag/v3.3-b2
Rewrote backend for layers chart in standalone mode
I don't think the SBC version has been updated yet, as there have been some changes in the firmware related to layer height since 3.2.2.
Layer chart and layer count work for me as job progresses, in stand alone. However, estimations based on layer time (which was always the most inaccurate estimate), and the parsing of the file to count how many layers there are before printing, have been removed, because it was requiring more and more effort and memory to keep up with the ever-changing notation in slicers.
@droftarts Yes, with PI 4, missed that. Update: time estimates are working on the current print. Layer count is the on the line above the layer chart, that shows the file progress.
In 3.3beta2 the layer count and current layer time are only available if the GCode file being printed includes layer number comments.
Duet 3 Mini, updated to 3.3beta3. No updating in Layer chart or file completion.
@dc42 My current file is printing without updating the layer chart. The file, from Simplify3D, has an entry such as ; layer 14, Z = 2.800 for every layer. Is there something else needed?
Something strange is happening. As I was typing my previous post I was seeing that the Layer Chart was not updating and the printer was on layer 7. I just checked back again and the layer chart has been filled from layer 2 with 0 time up to layer 10. Not sure what happened to layer 1.
Also noticed that the button option to show all layers or the lastnn is gone. Is this intentional?
@Stephen6309 @DaveA Can you check you have updated DWC to Duet Web Control 3.3.0-b2? I had this when I was running previous RRF 3.3betas with DWC 3.2.2, but should be fixed in standalone DWC (I think not DWC SBC version, though). I got nice graphs from both simulation and real print.
Same file, real print:
These on Duet 2 Maestro (delta kinematics), Duet Web Control 3.3.0-b2 and RepRapFirmware for Duet 2 Maestro 3.3beta2 (2021-03-10)
@droftarts Settings General reports: Duet Web Control 3.3.0-b2
I'm going to start another print in the morning and pay closer attention.
@DaveA, if DWC isn't displaying layers you can send M409 K"job" during the print to check whether RRF knows the current layer number.
tekkydave last edited by tekkydave
RRF 3.3beta2 & DWC 3.3beta2 installed on Duet2 Wifi
Edit from the near-future: see my next post for the solution
Note: I'm only testing this in simulation in case that makes a difference.
I'm not getting any layer counts or graph when slicing with PrusaSlicer 2.3. Works ok when tested with Cura (which I don't use anymore).
The PrusaSlicer gcode seems to be missing the
lines that Cura puts in.
and seems to have this at every layer change instead
;LAYER_CHANGE ;Z:0.3 ;HEIGHT:0.3
These are my firmware settings in PrusaSlicer
Have I missed something on the PrusaSlicer config side or does it not support the necessary comments (yet).
A simple workround for PrusaSlicer is to add a custom gcode to the Printer Settings:
at the first layer, and
etc at each layer change. If you use @tekkydave 's work around above for PrusaSlicer (and any other slicer that omits this) the layer count and chart should work correctly.
deckingman last edited by deckingman
Just to add that the "before layer change" G-code section for Slic3R and it's variants like the Prusa edition, is under "Printer Settings". So if you have multiple printer profiles as I have (15 in my case) then you need to add that layer change g-code to all of them.
Oh and of course, if you want layer times and stats to show up on any parts that you've already sliced, then you'll have to re-slice them. Just sayin'....
To complicate things further, some slicers (e.g. Cura, Ideamaker) count the first layer as 0, others (e.g. S3D) start from 1. Currently, if RRF sees
;LAYER nthen it will assume layers start from zero and add 1 to n before storing it in the OM). If RRF sees
;layer nthen it will assume that n starts from 1.
I don't know whether PrusaSlicer starts from 0 or 1.
deckingman last edited by deckingman
@dc42 that explains why I don't see a layer 0 in DWC. Confused me a bit
@tekkydave I will clarify it in the upgrade notes. We'll also hide the layer chart in the next version of DWC when layer data is not available.
Egris last edited by Egris
Tested fw 3.3 beta 2 on my rotary delta. Has there been a change to Segments per second for this kinematic? X/Y G1 moves look like there is a very low segments per second value usesd for straight lines.
With the older 3.3 version its working fine
pfn last edited by pfn
Is DWC 3.3.0-b2 not completely compatible with RRF 3.2.2? My layer chart has disappeared (no points graphed).
I have 2 instances of DWC running, one on my machine itself, and another on the remote proxy, the one on machine is 3.2.2 and shows layer statistics. 3.3.0-b2 proxy version only has a chart without data points.
@tekkydave Adding that works to get PrusaSlicer 2.3.0 to show layer counts and cahrt in DWC 3.3.0-b2.
oliof last edited by
Currently, if RRF sees ;LAYER n then it will assume layers start from zero and add 1 to n before storing it in the OM). If RRF sees ;layer n then it will assume that n starts from 1.
kiri:moto starts at Layer zero and it's layer comments look like this:
[...] ;; --- layer 0 (0.200 @ 0.2) --- [....] ;; --- layer 1 (0.200 @ 0.4) --- [...] ;; --- layer 124 (0.200 @ 25) --- [...]
It does not emit a
; LAYERS 124comment by default, but it's available via a token to add in the end gcode.
Would that be sufficient for the layer graph to show, or does the per-layer marker need to change? If the latter, I'll file an enhancement request with kiri:moto.
This print is still in progress. Sliced from S3D and run through ArcWelder. Notice the layer count. It also started the display on layer 2 and didn't show layer 1 until it reached 30 layers and I could hit the "Show all Layers' item.