Software bundle 3.4.0 stable released!

fractalengineer

@chrishamm those look neat, I can't seem to be able to install them though?

I get this error message:

InvalidOperationException in InstallPlugin: Cannot perform command because the plugin service is not started

Any tips?

Thanks!

zapta

@chrishamm, do the extra plug-ins work with stand alone duet? (Asking because they have DSF in their path)

jay_s_uk

@zapta only the motion one is SBC only

Mike3D

Thanks for this update.
I can see the thumbnails on the pc using webcontrol.
But i see no thumbnails on the PanelDue.
On the PanelDeu is the latest firmware 3.4.1-pre2.
The slicer i have is Prusaslicer and thumbnails are 160x160.

jjude

@mike3d note: PanelDue can only use QOI format. PrusaSlicer 2.4.1 not creating yet QOI.

dc42

@mike3d you can get Windows and Mac binaries of a fork of Prusa Slicer that supports QOI format from https://github.com/n8bot/PrusaSlicer/releases/tag/version_2.5.0-alpha0%2Bn8-release1. This version also has the option to retrieve the machine parameters from the Duet via http, if you have configured it for upload via http. Thanks to user @bot for implementing all of this.

chrishamm

@fractalengineer Have a look at the DSF upgrade notes for v3.3, it sounds like you missed them.

bberger

@dc42 said in Software bundle 3.4.0 stable released!:

@mike3d you can get Windows and Mac binaries of a fork of Prusa Slicer that supports QOI format from https://github.com/n8bot/PrusaSlicer/releases/tag/version_2.5.0-alpha0%2Bn8-release1. This version also has the option to retrieve the machine parameters from the Duet via http, if you have configured it for upload via http. Thanks to user @bot for implementing all of this.

This is big news. Especially on the Duet integration part.

zapta

Thanks @chrishamm, I was able to install the external input shaping plugin. Next will figure out how to use it.

BTW, if most of the external plugins are not DSF specific, maybe remove DSF from their path on github?

bot

@bberger I have submitted a Pull Request to PrusaSlicer to include those integrations: https://github.com/prusa3d/PrusaSlicer/pull/8087

n8bot opened this pull request in prusa3d/PrusaSlicer

open Fix RRF Time Estimates and Add "Get Machine Limits" button for Duet printer hosts #8087

ctilley79

Is there a roadmap for RRF 3.5 available? What will be its focus?

oliof

@ctilley79 Looking at the Github commit history, independent gcode streams seems to be the main feature being developed right now.

StevenL

Failed up to Upgrade from 3.2.2 to 3.4.0

Wifi card is stuck in Starting mode. no actual IP working.
Help!

Do I need to revert back to 3.2.2 or reset back to factory or what?
Please advise

Phaedrux

@stevenl said in Software bundle 3.4.0 stable released!:

Failed up to Upgrade from 3.2.2 to 3.4.0

Wifi card is stuck in Starting mode. no actual IP working.
Help!

Do I need to revert back to 3.2.2 or reset back to factory or what?
Please advise

You may need to reflash the wifi module. Try sending M997 S1 from the USB terminal.

ctilley79

@oliof I was hoping they would continue to work on input shaper implementation because I believe it still lags behind Klipper.

dc42

@ctilley79 said in Software bundle 3.4.0 stable released!:

@oliof I was hoping they would continue to work on input shaper implementation because I believe it still lags behind Klipper.

In what way? We are continuing work on the IS plugin to make it easier to use accelerometer data to tune IS.

Argo

@dc42

Differences I see compared to Klipper right now:

separate shaper frequency for each axis
automatic resonance testing (with a accelerometer): Klipper firmware generates vibrations from lower to higher frequencies and tests each shaper for it‘s effectiveness at each frequency. The results and recommendations are then displayed in a graph. It also recommends maximum acceleration values.
Example:

https://www.klipper3d.org/img/calibrate-y.png

dc42

@argo separate shaper per axis is not only unnecessary (because the supported shapers cover frequency ranges of up to 3:1), it is a bad idea because if you use different shape on different axes then the motion of the axes will no longer be synchronised during acceleration and deceleration. This will result in print artefacts, for example on corners that are not aligned with the axes.

I already said that we are continuing work on the input shaping plugin to make tuning IS easier.

zapta

@dc42 said in Software bundle 3.4.0 stable released!:

it is a bad idea because if you use different shape on different axes then the motion of the axes will no longer be synchronised

How about a single input shaping that is direction dependent? That is, some interpolation for angles between X only and Y only?

(I don't know how input shaping works, just thinking loud).

chrishamm

@zapta Applying two different input shapers on two axes has certain downsides so we decided it would be better to support only a single input shaper for two axes to damp both ringing frequencies.

We have a first beta of a new input shaping plugin ready but we need to discuss a few more details internally before we eventually release it. I expect we'll publish it sometime this week.