I will have filaments in my right nozzles AMS on my H2C. I will apply that filament to the model, in this instance it is DEEPLEE PETG and on the filament list on the left I have selected that material for the model.
I go to select convenience mode and it chucks the filament on the left nozzle (I do also have DEEPLEE PETG on the left nozzle) but I am selecting the right nozzle ams when applying that material to the part!
I’ve raised a ticket, does anyone else have this issue? Used to work a treat before with zero issues.
What do you mean here, how are assigning a filament specifically from the right-side AMS in the project settings?
AFAIK the project filaments are not specific to any nozzle or side or AMS. That’s why they can/need to be mapped during slicing. The green check mark next to filament selection just means that material is loaded somewhere. If you have the same material in both sides, I’m not sure how the slicer would know which to choose for your convenience.
FWIW, I haven’t noticed any changes in this regard with my H2C in any supported Studio version.
I just posted on a different thread about this. I’m seeing the same issue.
If I have the same filament type and color loaded in both nozzles on my H2D ( left is using external spool holder, right is AMS) it seems to get confused and tries to use the filament from my ext spool holder, even though I sliced it with the filament selected from my AMS. If I change the color to something else from the AMS config page and rsync, it works and uses the correct filament.
Hi, are you talking about the assignment when slicing (as in the OP’s screenshot), or when sending the print (the final nozzle/filament assignment dialog)? From your other post I took it to mean the latter, but perhaps not?
Yeah, not saying it couldn’t be improved somehow, but that’s kinda a difficult case… it likely boils down to how the filament profiles are defined (if they have unique IDs or not) and how all this is synced to the printer, or not. The names shown in Studio don’t necessarily make them unique… to the printer/AMS system it may basically all look like “gray PETG” (so when the printer reports loaded filaments, Studio doesn’t have a way to tell them apart). In the OPs case it’s literally the same filament (seems like).
So on that drop down on the left, when you have multiple AMS units connected to the printer, there is a subcategory within that dropdown showing which filaments are loaded into which AMS unit. When I select the filament that is in the right nozzle and apply it to the model (for example if this falls in slot 6, and I press the model and click 6 to apply it to the model), I would expect that to then appear on the right nozzle when slicing in convenience mode which is the opposite to my initial screenshot.
Which is AFAIR, is what used to happen as I haven’t encountered this problem before since updating. I hope I have explained myself properly!
I have noticed a few people mention this issue as of late.
Ah yes, sorry I overlooked/forgot that. Pretty much all the profiles I use are customized so I kinda skip over the “what’s in the AMS” parts… my bad. Given that, yes, I’d expect it to know which side would be more convenient. I’m not sure, need to check the code, but I think the AMS of the filament is only visual in the selector, not stored once you actually select it (eg. with a custom profile it doesn’t even seem to know which AMS it would be in). But if that relationship did exist in previous versions, I could see it being “fragile” and breaking after some change, indeed.
Do you see the same issue with BL filaments… if you have any? With the magic tags.
No problem at all mate. I’m not too familiar with the process of how it all works from that side of it and haven’t tried with BL filaments being honest!
But from a logical point of view, it doesn’t make sense why it would go to the left filament when I have chosen the filament in the right nozzle.
I’ve opened a ticket and sent some vids through showing the issue, I have been asked to go back down a level of software so will try that and see if it resolves it.
In the OPs case it’s literally the same filament (seems like).