What firmware version are you using?

Frederik

zapta

I am on 3.1.1 (2020-05-19b2).

Does duet3d have any recommendation on what version we should use if want long term support without having to upgrade to each new release?

oliof

there is no LTS release. The recommendation so far always was to use the latest stable release (i.e. 3.2.2 right now). In practice, if you are on a release that works for you, there is no need to update. Unless there is (-:

martin7404

On a modified China corexy I run 2.05 and on new Muldex build yesterday 3.11, today 3.2 and at the moment rolling back as far 3.2 have major issues with tool change on my IDEX

Phaedrux

@zapta said in What firmware version are you using?:

I am on 3.1.1 (2020-05-19b2).

Does duet3d have any recommendation on what version we should use if want long term support without having to upgrade to each new release?

Ride the wave!

zapta

@Phaedrux said in What firmware version are you using?:

Ride the wave!

My printer is pretty stable and useful these days so my focus shifted from the printer itself to what I am creating with it.

Phaedrux

@zapta well understood. Keep an eye on the release notes to see if anything is relevant to you. Now that rrf3 is maturing more features and improvements are on the way.

o_lampe

@martin7404 said in What firmware version are you using?:

3.2 have major issues with tool change on my IDEX

Is there a separate thread about it?
I got pushed to upgrade from 2.05 to 3.2.
But now that I'm in the process of building my own tool changer, I am concerned reading this note from you...

martin7404

Most probably it is some mistake in panel due manual operation, that made me change from - to + tool offset. It seems it is ok now

oliverracing

Currently running 2.05 on both my machines, but plan on switching to whatever is latest at the time when changing the kinematics of the portable printer (currently polar swing-arm but it's a bit flexy, changing it to corexy).

Main printer is hooked up to looks of external stuff and using outputs for things that they probably shouldn't be so will have to rethink before upgrading as that's a big job and it's currently working!

GeneRisi

How well does the RRF3 firmware run on the Duet2? It has less compute power than the Duet3, so, while I know it is possible, does it handle conditional gcode well, or is it underpowered?

Phaedrux

@GeneRisi said in What firmware version are you using?:

How well does the RRF3 firmware run on the Duet2? It has less compute power than the Duet3, so, while I know it is possible, does it handle conditional gcode well, or is it underpowered?

It runs it perfectly fine. There are no limitations or draw backs running RRF3 on the Duet2 series boards. Even the Maestro.

Diamondback

Yep I can confirm that, been running RRF3 since it came out on my Duet 2 Wifi and there is nothing negative about it. Works perfectly fine and all the goodies are so worth the switch.

NeoDue

@generisi I can confirm that it runs perfectly fine and fast as well.

I had the "Operation 3 failed" Wifi problem (https://forum.duet3d.com/topic/21562/firmware-bundle-3-2-2-released/) when upgrading from 3.2.0 to 3.2.2 though.

RyanP

2.05 on all machines. Too much on my plate. But one day I will simply do all machines.

EducatingSavvas

@phaedrux I tried the latest beta version but found the addition of a P parameter to define a spindle tool in the M3 command problematic - so went back to 3.2. I got it working but suspect using/gearing up for multiple tools (tang knife, laser, plotting-pen and spindle) will be over complicated by this. Possibly having to to use separate post processors for each tool, instead of using the tool number in the tool database to determine the tool I am using.

dc42

@educatingsavvas said in What firmware version are you using?:

I tried the latest beta version but found the addition of a P parameter to define a spindle tool in the M3 command problematic

You only need the P parameter if you are in CNC mode and you want to control a spindle that is not the one used by the active tool.

EducatingSavvas

@dc42 Does that mean if R in M950 and P in M563 are the same number during CNC mode, I would not need to write P# when using an M3 command? Should any spindle defining commands be in the tfree#.g tpre#.g and tpost#.g? That is to say I load the spindle separately from config.g file?

I think the confusion with CNC is that you have the spindle and the bits, or tangential knife and blades are referred and all are referred to as tools. And that on a CNC mills the tool database in often part of a complicated control system, while for flat-bed panel CNC machine the tool database in part of the CAM software.

dc42

@educatingsavvas said in What firmware version are you using?:

Does that mean if R in M950 and P in M563 are the same number during CNC mode, I would not need to write P# when using an M3 command?

Yes.

Should any spindle defining commands be in the tfree#.g tpre#.g and tpost#.g? That is to say I load the spindle separately from config.g file?

There is no need to do that. In config.g, define all your spindles, then for each tool specify which spindle it uses in its M563 command.

EducatingSavvas

Not sure if this got noted @dc42 but I'm finding I still have to write the P# for the M3 command to work - I've start a separate post about this.