Firmware bundle 3.3beta2 released

chrishamm

The first demo plugin for DWC can be found here which only displays the Endstop states on Settings -> Machine -> Endstops. To install it, either upload it on the "Upload&Start" button or on the "System Files" page. If you do the latter, you must go to Settings -> Machine -> Third-Party Plugins and then start it there.

SBC users must do a few extra steps before DSF/DWC plugins will work:

Install the duetpluginservice package (sudo apt install duetpluginservice)
Enable the two new plugin services sudo systemctl enable duetpluginservice duetpluginservice-root)
Install AppArmor (sudo apt install apparmor)
Enable AppArmor in the Kernel command-line arguments (edit /boot/cmdline.txt and append lsm=apparmor). Users of other distros may disable AppArmor in /opt/dsf/conf/plugins.json but this is NOT recommended
Restart the SBC (sudo systemctl reboot)
Install plugin(s) just like in standalone mode

These extra steps will become obsolete once we publish the next DuetPi image after v3.3.

We've got another plugin ready for simplified DuetPi configuration via M-codes that can be installed using the duetpimanagementplugin package but I haven't had much time to document and test everything yet (except this). I'll take care of this ASAP but probably not before next week. In the meantime you can find some more documentation about plugins here.

Alucardi

Is there a easy way to rollback if needed?

oliof

People with SBC setups that manually installed 3.3beta1 need to manually move the update files to the new firmware directory. Here is how I did that after running apt-get dist-upgrade only updated DWC because the IAP files and firmware files were in the wrong spot:

$ sudo su -
# for i in `dpkg -L reprapfirmware| grep .bin$` ; do cp $i /opt/dsf/sd/firmware/; done

After that, sudo dpkg --reinstall install reprapfirmware triggers the install of the firmware the usual way.

jens55

Cool .... I can see a light at the end of the tunnel of the 'why should I have a SBC attached' debate.

Thanks !

Alucardi

Trying out input shaper, i use same Hz as with DAA which completely removes my ringing. Input shaper P1/2/3 have terrible ringing. Changing the damping factor make no difference.

You can clearly tell on the picture when DAA is active. No ringing.

littlehobbyshop

@chrishamm This seems a great step forward in bringing plugins together for visibility. Am I right in thinking developers will be encouraged to merge their plugins to this repo?

oliof

@Alucardi I believe the input shaping types other than DAA are still no-ops, so it's no wonder you don't see an effect.

Alucardi

I seem to remember seeing a post where it accruals did make a difference when the guy changed to the different modes. Also according to the gcode wiki it should work.

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.