Firmware bundle 3.3beta2 released

[chrishamm]

@littlehobbyshop The plugin(s) on that repository are plain demos for now. I think there will be a separate plugin repository but this is still TBA. And please keep in mind this is still a beta, so the format of the plugin manifest may change again before the final release. Likewise the list of SBC permissions is not 100% certain. It may be expanded and/or changed based on the upcoming feedback.

[Argo]

@Alucardi

That was me. With the version I tested it with, the P value for the mode has no effect at all which I didn’t know. I had different ringing frequencies on the frame which was hardware related (play in the bearings on Y) which I just fixed yesterday. So I was fooled the modes had an effect which can’t be.

[dc42]

I confirm that in 3.3beta2, only DAA is implemented. The other P values do nothing. For backwards compatibility, if you use M593 without a P parameter and the existing resonance compensation method is None, it is changed to DAA.

[Alucardi]

@dc42 just me getting excited. I know it is meant for 3.4 but seeing it made me want to try it out

[dc42]

@Alucardi said in Firmware bundle 3.3beta2 released:

@dc42 just me getting excited. I know it is meant for 3.4 but seeing it made me want to try it out

I am developing input shaping on a fork of the 3.3 firmware, which is why I implemented some of the framework for it in the 3.3beta release. However, I think we will likely move to 3.3RC1 soon, and save input shaping for 3.4.

[tekkydave]

Thanks for this beta release. Finally a solution to the analogue piezo probe slowdown issue. I have tested the z homing on my D-Bot and confirm it probes & lifts at the full 6mm/s and no longer slows to 2mm/s for the dive.
Thanks guys.

[Alucardi]

@dc42 Well i can't be more excited. I run klipper on one machine but love my duet cards and the magnetic filmaent sensor. I assume there will be use of some accelerometer. Is it same as klipper? would be nice to have it home when 3.4 beta comes.

[DaBit]

We have local variables now. Nice!

[Stephen6309]

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

[droftarts]

@Stephen6309 said in 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.

Ian

[Stephen6309]

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

[dc42]

In 3.3beta2 the layer count and current layer time are only available if the GCode file being printed includes layer number comments.

[Stephen6309]

Duet 3 Mini, updated to 3.3beta3. No updating in Layer chart or file completion.

[DaveA]

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

[DaveA]

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?

[droftarts]

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

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)

Ian

[DaveA]

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

[dc42]

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

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

;LAYER:0

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

[tekkydave]

A simple workround for PrusaSlicer is to add a custom gcode to the Printer Settings: