The same for people reporting to have problems.
Machine: X1C
Firmware: 1.07.03.00
BBS: 1.9.0.70
Filament: Bambu ABS
All stock settings for the machine and filament. Iāve not enabled the experimental retraction yet as the purge has never really bothered me, and I keep forgetting to enable it.
Iām am running a test now using the following settings:-
11 discs 0.2mm thick on a base
Update
So no issues encountered with 11 color changes.
While watching I could hear the retract before cut, but on the last color when the job was done I didnāt hear the retract.
OK this is great info, seems to work on on Bambu ABS for you, via configuring the Filament override settings.
I am doing more indepth testing with other filaments including swapping back\forth with Bambu PLA Basic and still hitting those extruder issues. I have also tried modifing the retraction amoun, 12, 15, 16, 18 etc (Bambu PLA Basic default is 18).
I stll suspect it something to do with what the patch notes referred to as filament matching etc etc, certain brands etc but otherwise, I am running out of ideas. The original authors work, adding the machine g-code, āJUST WORKEDā irrespective of filaments, vendors etc on previous firmwares for me . with a massive, nearly 50% reduction in purge wastage.
Rolling back the firmware, restarted the exact same gcode and not a single issue, no clog reported.
Iām so sorry for this issue,and thank your feed back, for you devices logs,we find the issue,special machine maybe catch this issue ,itās reason is extruder distance param not perfect, we will optimize this issue in the next version.of course, many machines are not worry, it isnāt appear this issue.
every body , Iām so sorry for this issue,and thank your feed back, we find the issue,special machine maybe catch this issue ,itās reason is extruder distance param not perfect, we will optimize this issue in the next version, now new version is testing!
of course, many machines are not worry, it isnāt appear this issue.
Great - thanks for reply and confirming, I think your saying in certain cricumstances the extruder paramater doesnt work for certain machines and you may have fouind the issue - welcome the new version for more testing thank you!
Mine had a similar issue but it was actually binding up the filament across multiple spools in the AMS after the update but getting 01.07.03.03 right now. .03 seemed to fix the camera got terrible after a previous update so 03.04 might include something else that is meaningful.
This is not a general firmware issue. I updated and havenāt had any issues and have printed a few multicolor items. Maybe the people reporting the problem do actually have something wrong between the AMS and the printer where itās good enough that normally the printer can just push through it, but now the firmware is detecting the issue.
If that is the case, maybe it is good that the firmware is reporting it because not addressing the issue could cause damage or premature wear on parts of the printer or AMS.
Had this issue when moving to 1.07.03.00. Unfortunately I didnāt realize it was a fw issue until I had taken everything apart to look for a jam and even replaced the print head assembly. After finding this via good I downgraded the fw back to 1.07.02 and it was smooth printing again. I saw 1.08 was released so I once again decided to go forward and Iām having the same issue again. The AMS tries to load filament, gets stuck at the printhead extruder, and then retracts. After a bunch of tries it gives up. Iām able to load filament via directly no problem. I once again reverted to 1.07.02 and itās once again working.
Anyone else seeing this still with 1.08? Suggestions on getting past it so I can keep the fw updated without losing AMS function?
Iām still seeing it on 01.08.00.00. Itās not as frequent as it was on 01.07.03.00, but it still happens maybe 5% of the time when trying to use the AMS for multicolor/multimaterial prints. Rolling back to 01.07.02.00 keeps it reliable for me too.
Itās a shame, the filament purge decrease is nice in theory, but when prints are failing due to a firmware bug Iād rather purge more filament than have to waste time retrying prints over and over.