Updating firmware from 2 to 3 worhwhile?

infamous_panda

It's been a while.

I have a Tevo little monster (fairly large Delta) upgraded with a Duet Maestro, and it's been reasonably well sorted as far as print quality and reliability for the past couple of years. I have Slic3r profiles and Macros setup that have made running this thing mostly painless.

I have looked but have not found any firmware features that would warrant the upgrade from Rerap 2.05 to the current version of 3. I understand there is quite a bit of work to make sure all the configurations carry over properly.

I'd be interested in features that would improve speed and quality.

Phaedrux

If you don't see anything that catches your eye in the RRF3 changelog and you're happy with the way it's running now, there is no requirement to upgrade.

https://github.com/Duet3D/RepRapFirmware/wiki/Changelog-RRF-3.x#reprapfirmware-33

For speed and quality improvements you may benefit from input shaping, but this is still a beta feature and requires an accelerometer.

fcwilt

@infamous_panda said in Updating firmware from 2 to 3 worhwhile?:

I'd be interested in features that would improve speed and quality.

For me the conditional code features alone were worth the update, I make use of them in many places.

For now I have settled on version 3.3. I will let others try 3.4 and when it appears to be stable I may move up to it.

Frederick

zapta

@infamous_panda upgrading from 2 to 3 is a pain but I think it worth it because otherwise you will stay behind with less attention to the version you are using.

Unless if you don't plan to keep that printer for a long time.

Phaedrux

If you do wish to try it, here is the best way to upgrade and still retain the option to revert.

If you still have access to DWC. Upload these 3 zip files, one at a time in the system tab. Don't extract them first. Reboot after each. Use M115 in the gcode console to verify the firmware has been applied.
https://github.com/Duet3D/RepRapFirmware/releases/download/2.05.1/Duet2Firmware-2.05.1.zip
https://github.com/Duet3D/RepRapFirmware/releases/download/3.0/Duet2and3Firmware-3.0.zip
https://github.com/Duet3D/RepRapFirmware/releases/download/3.3/Duet2and3Firmware-3.3.zip
That will get your firmware and DWC up to date.

You can see the change logs here:
https://github.com/Duet3D/RepRapFirmware/wiki/Changelog-RRF-3.x

For your config, might be a good idea to run through the configurator tool and generate a fresh set for RRF3.
https://configtool.reprapfirmware.org/Start

Backup your existing config files in the sys folder in case you want to switch back to RRF2. It’s easy to switch back and forth, just upload the zip file for the version you want and then upload your config files.

These documents will come in handy during the conversion.
https://duet3d.dozuki.com/Wiki/RepRapFirmware_3_overview
https://duet3d.dozuki.com/Wiki/Gcode

DonStauffer

@infamous_panda Yes. RRF 3.4 is solid and has some terrific new features in terms of metacommands.

infamous_panda

So conditional programing and meta commands. What would a common use case for this be?

I am interested in input shaping.

zapta

@infamous_panda said in Updating firmware from 2 to 3 worhwhile?:

I am interested in input shaping

If you don't want to hassle with an accelerometer, you can also tune it with an input shaping tower as we do with other parameters. The duet documentation has a link to an stl model that is good for this purpose.

fcwilt

@donstauffer said in Updating firmware from 2 to 3 worhwhile?:

@infamous_panda Yes. RRF 3.4 is solid and has some terrific new features in terms of metacommands.

Even though it is still in BETA you are finding it bug free?

Frederick

DonStauffer

@fcwilt Wow, I put 3.4 when I meant 3.3. I have no experience with 3.4. But 3.3 is great!

oliof

@fcwilt to answer your question, 3.4b6 fares well on my IDEX setup on a duet 3 mini 5+ with expansion board in standalone mode.

I've been holding off 3.4b7 because the new event system and changed behavior around heater faults, but mostly because I don't have the time to build my own macros to re-implement previous default behavior.