Material Flow Setting

[Camel 0]

Changing the material flow setting on an extruder appears to impact both extruders, not just the one selected.

[SandervG 1,521]

Can you be a little bit more specific in your question/comment? Are you asking something, or informing us? What 3D printer are you talking about and/or what version of Cura are you using? Thanks! 

[Camel 0]

Ultimaker 3

Cura 3.1

 

Start a dual extruder print, select Tune, change Extruder 1's material flow.  Return.  Go into Extruder 2, notice the material flow is now changed.  If that's intentional, it doesn't seem like its a per-extruder setting.  Did I do something wrong?

[SandervG 1,521]

Sounds like a firmware thing, I'll move your thread to firmware and tag @Marco_TvM

[Marco_TvM 34]

This is by design, so not a bug.

I think @Daid might shed some light as to why.

 

If you want to use different speeds tho, you can use the settings in Cura to make it so.

Edited February 1, 2018 by Marco_TvM

[kmanstudios 1,120]

I would like to know why myself. I noticed way back in my early start a year ago when I was just pushing buttons. Got some bad results though when the main filament needed a bit of oomph and the PVA was doing fine until I upped the flow. I did take note of what worked and started to use Cura to make that change if needed. But on the fly it had some odd results.

[Bossler 8]

32 minutes ago, Marco_TvM said:

This is by design, so not a bug.

I think @Daid might shed some light as to why.

Would be great to understand the rationale behind this.

Since my initial thought would be it makes more sense to be able to adjust the flow individually per extruder,
not for both at the same time. 

 

32 minutes ago, Marco_TvM said:

If you want to use different speeds tho, you can use the settings in Cura to make it so.

Which would not help during a print already running, right?

[Marco_TvM 34]

Ok, some more info.

Not entirely by design, but because of Marlin...

Marlin only supports one speed for flow speed for all possible extruders. There is an issue on the backlog to fix this, but it's not a priority right now.

[Marco_TvM 34]

25 minutes ago, Bossler said:

Which would not help during a print already running, right?

 

No it would not. I do see your point, but fixing this is not yet on our board of things to do soon(tm).

[Camel 0]

Thanks, gents!  Knowing to leave those bits alone is enough for now.  'Preciate the speedy feedback.