Is it expected that the AMS2 gears will squeeze filament so hard that it presses ridges into it? I’m getting this with my brand news AMS2 with every roll of PLA, PETG, PETG HS, etc so far.
Considering that I’ve had the thing installed for not even 1 week yet, and my unassisted print success rate is well under 10%, I’m really beginning to question why I spent so much money on this thing.
beyond the “failure to retract” issues I’m having in slots 4 and 3, I’m also getting “failure to load” issues now in all slots.
I’ve completely replaced the PTFE tubing lines already to no avail…
just trying to gather information while I open a support ticket.
In my experience (4 months) no. I occasionally get overload errors, but investigation shows cardboard spools can trap the filament and cause jams, or in one case the refill had a cross halfway through.
You mentioned you replaced the tubing lines - a member here suggested ordering one size up, I bought some to try loading TPU direct and haven’t tried it yet, but for $4.99 it may be worth trying.
Yep, that feeder gear goes very hard and very fast.
If you’re having ams2 problems where the filament is entering one of the 4 mouths but is not leaving the rear of the AMS2, there is a DIY repair on the internal hub that takes about 20 minutes, some tape, and an xacto knife. tldr shim it about 0.20 - 0.30mm and it begins to feed normal. Lots of large topics here and otherwhere
Thanks for the input so far all. I won’t worry about the ridges then.
I can confirm that the PTFE tubing I’m using as replacement is SOVOL 2.5mm ID tubing.
Additionally, the issue does not appear to be with the internal hub in the AMS proper, as there are no issues with that portion of the run.
Instead, I’m running into feeding issues primarily @ the external HUB that is mounted to the back of the P1s. I’ve attempted changing the input port, with no change, if there is an issue, the filament fails to make it past the input connector at the hub.
OR retraction, where the filament is successfully pulled 5-6 inches out of the tool head, but then seems to get “stuck”.
all filaments are thoroughly dried, and humidity within the AMS2 itself bounces between 15 and 20%.
I’ll look into the DIY fix when I can, but I’ve got a support ticket submitted now, so won’t be doing anything drastic until I work through the ticket with Bambu Support.
Only just noticed you say you have a P1S, AMS2 (is it just AMS2 or AMS2 Pro) Pro is normally promoted for P2S, etc. just a thought..
With my P2S and AMS2 Pro when using the external spool holder, the Loading & Unloading process is completely manual, this is because there is no drive to assist the print head gear.
So, is what it’s doing correct, once it’s pulled back a little, P2S will prompt you to remove the filament. What does Wiki say about P1S and your exact model of AMS? Are able to manually remove the filament?
The filament unloading/feeding issues are unrelated to any external filament, as all the issues I’ve been experiencing are with filaments that are loaded into one of the 4 positions of the AMS2 Pro (I shorthand to AMS2).
Some people have had success with using a deburring tool/other cutter to cut a light chamfer into the mouth of the ptfe section that is receiving the incoming filament. Gives it less wall to bind up on if that initial hole has a minor slope/funnel into it that guides filament in. No experience with it myself but Maybe that can help you.
Well, after multiple hours of babysitting, I’m quite confident that the issue is the angle on the inlet bowden tube connectors going into the AMS HUB.
While still not perfect, after considerable feats of engineering, I might have found a temporary fix. Since executing this fix, I’ve now reached more than 25 consecutive successful AMS driven filament changes… more than 10 times the prior record of 2 consecutive changes without a failure.
Got the new replacement hub in a few days ago, and haven’t been having any issues since. Does look like I may have gotten one where the alignment wasn’t quite right.
Marking as solved as replacement of the hub fixed the issue.
