I agree completely and well stated.
All of the below is an assumption.
I think what’s happening here is that if the AMS is actively being used printing, it only has one output and thus cannot find the end of the filament either at the AMS or the buffer. I believe this also impedes its ability to use the RFIDs to read the filament type, but that can be manually put in as y’all know.
Perhaps what could happen is that in a future firmware if you are actively loading in more filament if the print does go through all spools available (assuming you have 2 or more of the same type already loaded before starting) that if you are manually loading in the data, it should just do the end finding after the last spool it knows of the same type is depleted. Or, if given no info from you, that it does the read-in procedure after the last known spool is depleted to see if the user was keeping up so that it can see if it has the type it needs.
This is all assuming that there isn’t some limit that is being introduced from the way the printer is loading in the gcode/print file at the initialization stage, but that of course could be modified in firmware as well.
That’s odd but good to know
We had a very similar issue to this today. 75% through a 27 hour print, AMS reports B4 on the left extruder had run out. I open the AMS, take out the spool, prepare and insert the new spool, offer the filament to the feeder, and it doesn’t pull it in. It does notice its there though as the slot flashes (2 short flashes per second) when the filament is in the top of the feeder. Clicking resume tries to resume but comes back with “filament run out” again like I havent fed it in. I tried resuming with no filament in the slot (no lights on the slot) and as expected “filament run out”.
I checked there wasn’t filament stuck in the AMS, or out the back of the AMS. The bowden tubes were all empty as I would expect. Tried a couple more times and even forced the filament in like 10-12cm, but slot continued to flash twice per second. I decided to power off the printer and try to perform a power-outage resume. When the printer powered up, it didn’t see either of the AMSs but was still prepared to resume. I waited five mins but still no detected AMS (either of them). I tried a power-off again. That time it did see both AMS, and was prepared to resume, but still continued to flash twice per second on the slot, and failed to resume.
I tried a third power off, waiting a good 1 min before powering back on and it then appeared to resume, but after homing the head and it was looking good. it did start again but seemed to ignore moving the Z axis, and started printing the prime tower in the air. After it did the sequence for the prime tower the print progress changed to 0% and then it seemed to start the print from 0% and complained there was something on the bed.
So that was that print ruined - oops…
First issue I’ve had with the H2D, and I’ve certainly had auto-refill work for me in the past, and at least once manual “run out / replace / resume” with no issues as well. Does look like a bug to me… I wouldn’t like to try and replicate it again though.
Here are my f/w versions:
H2D - 01.01.04.00
AMS 2 Pro (L) - 02.04.19.87
AMS 2 Pro (R) - 02.04.19.87
1 Like