Hello, after a long time, I’ve printed in multiple colors again, and an error has occurred that I’ve never had before. As long as color changes are necessary, the purge tower is printed, and everything works, but as soon as no more color changes are needed, it stops printing the tower as usual. However, what’s new now is that the printer still unloads the filament only to reload it immediately, and in addition, every 4 layers, for no apparent reason, the AMS auxiliary motor error appears after unloading (see picture), which I have to close each time to resume the print.
Do you have AMS savers installed? They can help (not 100% but much better) with temporary filament catching/entangling. Spool jumping used to affect the AMS especially for nearly empty spools in the past. Weighing down spools by putting nuts in a centre spool dessiccant holder helped to counteractbthose issues.
And of course, the PTFE’s wear down, increasing the likelyhood of the error you are seeing.
Thank you for your response. However, it’s not a hardware issue; the AMS and the spools are working perfectly fine. The problem occurs, for example, with the model only at around 90%, when no more color changes are needed, but it still tries to change the color every 2 layers. This only leads to unloading and reloading the white filament before it continues printing. The print is now finished, but it was quite annoying because I had to clear the error message every 4 layers.
To explain it with an example: for instance, everything works fine up to layer 430. Starting from layer 431, the purge tower is no longer printed, as it’s no longer needed. Then from this point, the loop goes until the end: Layers 431, 432 are printed → Filament is unloaded → Filament is loaded → Layers 433, 434 are printed → Filament is unloaded → Error message/print is interrupted → Resume printing manually → Filament is loaded → Layers 435, 436 are printed → Filament is unloaded → Filament is loaded → Layers 437, 438 are printed → Filament is unloaded → Error message/print is interrupted … and so on.
I have never seen this behaviour due to software issues. I have however encountered this (including the repetitive nature of the error) when spools ran empty. That is why I assumed a hardware issue.
However, there are undoubtedly strange and unexpected things happening due to seemingly unrelated issues. Not my area of expertise though. I am frequently surprised at the number of items an SD card change for example can resolve…
I agree that a hardware or sensor problem sounds more likely - that is perhaps avoided by something to do with the colour change operations.
If it consistently happens at specific layers you could check the gcode in the print preview or by exporting it to make sure there is nothing in the layer change code that is asking the AMS to reload.
Or a rather inefficient work around/test could be the manufacture of an extra colour change at the top layer so that the prime tower keeps going even after it is no longer normally needed.
Edit: ok it looks like, that is not the Model, the AMS Slot 2 is the problem, sometimes it print->unload/load->print->unload the Filament and throw this error, without any reason …
And btw. … i hate makerworld … with his ■■■■ 3mf files, it allways overwrites my AMS + settings, why the hell there are no optional simple stl files (selecting “download stl file” is mostly a 3mf file too …) … or a option in Bambu Studio “load only Model without settings” ?
