Why can't backup be enabled for multicolor prints?

[ninjamida]

If I understand correctly: The "Backup" feature is so that if one spool runs out, it will switch to another one of the same color and material.

What reason is there that this can't be done on multicolor prints? Obviously if I'm using four different colors, it can't work; but if I'm only doing a two- or three- color print, there's no reason why the spare slots couldn't have extra spools of the same color and material. Stock firmware can definitely do this, and I"m fairly sure zMod without Bambufy can too (but might be wrong on that one)?

[function3d]

But if I'm only doing a two- or three- color print

Too complex to implement for such an unlikely scenario, and it will produce color changes in the same color that the user would ultimately have wanted to avoid.

[ninjamida]

Too complex to implement

This is fair.

for such an unlikely scenario

I don't see how two-color or three-color prints are a particularly unlikely scenario? In fact, an especially likely scenario to encounter this could be a one-color main print while also using a dedicated support (or interface) filament of another material.

and it will produce color changes in the same color that the user would ultimately have wanted to avoid.

How would it do this?

Perhaps you're misunderstanding how I envision this.

Let's say I'm doing a print with three colors - red, green, and blue. I have a nearly-empty roll of red loaded in #1, a new roll of red loaded in #2, green loaded in #3, blue loaded in #4. When I start the print, I point C1 / C2 / C3 to P1, P3 and P4 respectively. When the roll of red on #1 runs out, it does a backup switch to roll #2, and any future material changes to C1 will now use P2 instead of P1.

However - you did mention on the other issue, that Bambufy has no awareness of what colors are loaded. (Although zMod itself has awareness of this; is it possible to just take the information from there?) That does explain why such a feature would be more complicated - as without knowledge of this, the user would have to manually tell it each time which are the "backup" reels.

On a side note - does this also mean that when doing a single color print with the Backup option enabled, that it will just use any available spool, and thus any spools of different color / material need to be physically removed from the printer first?

[function3d]

On a side note - does this also mean that when doing a single color print with the Backup option enabled, that it will just use any available spool, and thus any spools of different color / material need to be physically removed from the printer first?

Yes, any availability spool of the same material starting with 1. The color is the user's responsibility if they want it in different colors or not.

[function3d]

Although zMod itself has awareness of this; is it possible to just take the information from there?

Not exactly. As you know, you have to tell it the colors. This printer doesn't know what colors/materials you are using. This is what I am trying to avoid: the user having to physically set them (inevitable) and then having to set them virtually (redundant). The process of assigning ports already includes this step without needing it.

[TMTYD]

I just did a multi-color print as well. What I also noticed is that it doesn't automatically switch to the other spool when white filament runs out in IFS Port 1, nor does it automatically switch to IFS Port 2, which also contains white filament.

It would definitely be better if you could select which color is in which port from the start, so that it automatically continues printing when the first color runs out.

I agree with the previous commenter on this.

The standard firmware can definitely do this, and I believe Zmod can do it directly without the Bambufy plugin.

Furthermore, I noticed that when you load filament into the empty IFS port, the hotend fan doesn't continue running; it's immediately set to zero in Mainsail.

Watch the Video

[ninjamida]

Yeah… this is an impressive plugin, but I don’t think I’ve ever encountered a dev as arrogant as this one.

It’s fine to not want to implement a certain feature, but acting like everyone else’s workflow is wrong just because it doesn’t match his own is peak arrogance.

[function3d]

Calling me “arrogant” is a personal remark and not appropriate for a technical discussion.
Please keep the conversation focused on the technical aspects of the issue.

[function3d]

Furthermore, I noticed that when you load filament into the empty IFS port, the hotend fan doesn't continue running; it's immediately set to zero in Mainsail.

It seems that you are printing from the image you attached. Bambufy does nothing when you insert a filament into the IFS while printing. If it is not printing, autoinsert is executed and the current state of the layer fan is not affected at any time.

[function3d]

What I also noticed is that it doesn't automatically switch to the other spool when white filament runs out in IFS Port 1, nor does it automatically switch to IFS Port 2, which also contains white filament.

As long as Bambufy does not ask the user which colors are loaded in the IFS, this feature cannot be implemented.

[TMTYD]

What I also noticed is that it doesn't automatically switch to the other spool when white filament runs out in IFS Port 1, nor does it automatically switch to IFS Port 2, which also contains white filament.

As long as Bambufy does not ask the user which colors are loaded in the IFS, this feature cannot be implemented.

So it would make sense to implement this function to improve bambufy.

[TMTYD]

Furthermore, I noticed that when you load filament into the empty IFS port, the hotend fan doesn't continue running; it's immediately set to zero in Mainsail.

It seems that you are printing from the image you attached. Bambufy does nothing when you insert a filament into the IFS while printing. If it is not printing, autoinsert is executed and the current state of the layer fan is not affected at any time.

Explanation of the image:

The filament in IFS Port 1 ran out, and the printer automatically paused the print. Since bambufy doesn't automatically switch to the second IFS port (because it doesn't know that white filament is also loaded there), I manually loaded the filament into IFS Port 1 and resumed the print.

I then noticed that the hotend fan wasn't running and the FanM106 value in Mainsail was set to 0.

[function3d]

I then noticed that the hotend fan wasn't running and the FanM106 value in Mainsail was set to 0.

When printing is paused, the layer fan stops; this is expected behavior. Once printing resumes, the layer fan will return to the speed it had before the pause.