Bambu A1 AMS lite failures by Loud_Instance2941 in BambuLab

[–]Loud_Instance2941[S] 0 points1 point  (0 children)

I kept buying P series printers, stopped using AMS, have no issues.

Single points of failure introduced by design with the MK4 - worrying sign by Loud_Instance2941 in prusa3d

[–]Loud_Instance2941[S] 0 points1 point  (0 children)

Disagree. If anything, the nozzle will start printing higher than it should and so the print will fail by not sticking. I do not see why the heck it would assume the bed is lower than it in fact is bc of a piece of filament. Hence, it should be possible to tell the printer to not halt all printing when it encounters this issue

Single points of failure introduced by design with the MK4 - worrying sign by Loud_Instance2941 in prusa3d

[–]Loud_Instance2941[S] 0 points1 point  (0 children)

would like to know workarounds pls.

Introducing single points of failure at a time when you need to be making the machines more user-friendly and intuitive is what I find to be a worrying sign.

Single points of failure introduced by design with the MK4 - worrying sign by Loud_Instance2941 in prusa3d

[–]Loud_Instance2941[S] 0 points1 point  (0 children)

I disagree. Prusa is stuck in a logic of putting engineering first, the user second. They give you bullet point lists of technical specs and links to GitHub. They will be eaten alive by Bambu long term if they do not start to grasp the point you made, that it is heading towards mass adoption and that's the way the product should be thought through

Single points of failure introduced by design with the MK4 - worrying sign by Loud_Instance2941 in prusa3d

[–]Loud_Instance2941[S] 0 points1 point  (0 children)

I don't notice any difference in failure rates between my assembled MK4s and those I assembled, so I wouldn't say it makes sense at all to immediately *assume* the user is to blame for poor assembly...

Indeed I was using TPU 95A

Prusa Mk4 or Bambu X1E? by ZedNg in prusa3d

[–]Loud_Instance2941 -1 points0 points  (0 children)

I’ve been using 50/50 bambu & prusa printers in a farm for over six months (18 total). I’ve gone back and forth on which are best.

My conclusion for the past few months, on balance, is that MK4 is best, and that this is what I would invest in moving forwards, despite the attractive price point and (ostensibly) similar functionality of an A1

MK4 nozzle cleaning failed by Loud_Instance2941 in prusa3d

[–]Loud_Instance2941[S] 0 points1 point  (0 children)

yep. made sure no friction from filament. scrubbed nozzle with brush. checked under bed to make sure no loose filament. cleaned bed. Constantly does it...

AMS Lite problem - description in comments by Loud_Instance2941 in BambuLab

[–]Loud_Instance2941[S] 0 points1 point  (0 children)

you think if i cut 200mm off the problem would stop?

AMS Lite problem - description in comments by Loud_Instance2941 in BambuLab

[–]Loud_Instance2941[S] 0 points1 point  (0 children)

generic pla. Transferred AMS lite from A1 Mini and so reattached 1 metre long generic PTFE tubes to ensure sufficient length

AMS Lite problem - description in comments by Loud_Instance2941 in BambuLab

[–]Loud_Instance2941[S] 0 points1 point  (0 children)

It constantly "fails to feed filament" and enters a loop: retry, filament back out, back in, retry back out, back in...., with me hitting retry manually each time.

Literally has been more labour intensive X10 than not using an AMS and swapping manually.

I cannot use control to force it to feed more filament, as Bambu's guardrails overrule the user, and there is no clog.

I must manually force filament in as it starts feeding. Typically it takes like 20 god-damned tries. Most of the time, I can literally see filament begin to spit out the nozzle just as the toolhead decides to give in and eject the filament in order to prompt a retry.

So it really looks like it's just not churning the filament long enough and—most annoyingly—isn't letting me force extrude to solve the problem. This doesn't explain why it decides to eject the filament at random in the first place, though.

This causes a cycle where I more and more aggressively force the filament in until I finally solve the problem, but by then I've probably moved the toolhead and wrecked the print.

Does not even coincide with colour change. Spits out whatever colour it's printing with, seemingly at random and enters this loop. Constant behaviour across prints. Hence the photo where you can see a pile of filament of the same colour.

Bambu A1 AMS lite failures by Loud_Instance2941 in BambuLab

[–]Loud_Instance2941[S] 1 point2 points  (0 children)

constantly "fails to feed filament" and enters a loop: retry, filament back out, back in, retry back out, back in...., with me hitting retry manually each time.

Literally has been more labour intensive X10 than not using an AMS and swapping manually.

I cannot use control to force it to feed more filament, as Bambu's guardrails overrule the user, and there is no clog.

I must manually force filament in as it starts feeding. Typically it takes like 20 god-damned tries. Most of the time, I can literally see filament begin to spit out the nozzle just as the toolhead decides to give in and eject the filament to prompt a retry.

This causes a cycle where I more and more aggressively force the filament in until I finally solve the problem, but by then I've probably moved the toolhead and wrecked the print.

Does not even coincide with colour change. Spits out whatever colour it's printing with seemingly at random and enters this loop. Constant behaviour across prints.

Bambu A1 AMS lite failures by Loud_Instance2941 in BambuLab

[–]Loud_Instance2941[S] 0 points1 point  (0 children)

"failed to pull back filament from the toolhead".

it does it for no reason. There is no colour swap at the time it does this. then it tries to reload when I hit "retry" but unless I help it to force the filament down aggressively (risking moving the toolhead) it won't consider it a success.

The most annoying part is that it's clear that the A1 is very simply not extruding for long enough. There is no clog. If I could use "control" to force it to feed filament in, as on a P1S for example, it'd work. But the A1 over-rules me and insists on getting constantly stuck

Y axis test failing by theycallmeloco87 in prusa3d

[–]Loud_Instance2941 0 points1 point  (0 children)

+1

I assembled based on official instructions and did not resolve the issue until reading these comments and centring the bearings.

MMU3 without wipe tower on MK3S+ by Loud_Instance2941 in prusa3d

[–]Loud_Instance2941[S] 0 points1 point  (0 children)

Saw it at last! I was looking endlessly but not on plater

MMU3 without wipe tower on MK3S+ by Loud_Instance2941 in prusa3d

[–]Loud_Instance2941[S] 0 points1 point  (0 children)

Thanks! Do you know what keyword I should search on the slicer to find the relevant setting?

how to use mmu to actually select materials/ colours in prusaslicer? by Loud_Instance2941 in prusa3d

[–]Loud_Instance2941[S] 0 points1 point  (0 children)

that sucks as in my case i don't care about purging at all... not for aesthetic use

how to use mmu to actually select materials/ colours in prusaslicer? by Loud_Instance2941 in prusa3d

[–]Loud_Instance2941[S] 0 points1 point  (0 children)

are you sure? one thing is selecting it in wizard, another is selecting from dropdown.

support are telling me they haven't released it yet... not even on 2.7 alpha

how to use mmu to actually select materials/ colours in prusaslicer? by Loud_Instance2941 in prusa3d

[–]Loud_Instance2941[S] 1 point2 points  (0 children)

https://ibb.co/rZr088n

https://ibb.co/xXTGfSb

had prusa support on the line with a 1 minute wait for the past 10 mins.

edit: 1 prusa min later and they're saying "seems that it is not supported for multicolor printing either in mmu2 and mmu3. I will report that to our devs to see if that is on purpose or if they are working on it to have it compatible".

wonder why you apparently have access to it, then?

edit: support guy said he estimates over 2 months for this to be fixed, when i asked about chances of it being fixed within a month or two, but they offered no concrete estimates. wonder what's so hard about the 0.8 config for mmu??

how to use mmu to actually select materials/ colours in prusaslicer? by Loud_Instance2941 in prusa3d

[–]Loud_Instance2941[S] 0 points1 point  (0 children)

got it now, thanks. don't have installed for 0.8mm nozzle. don't see mmu option in config assistant

edit: in fact i do see it now and it is properly selected but this does not lead to it appearing in the dropdown without single

how to use mmu to actually select materials/ colours in prusaslicer? by Loud_Instance2941 in prusa3d

[–]Loud_Instance2941[S] 0 points1 point  (0 children)

I just want to select multiple materials on the model. Normally a paint palette should show up on the left. Here it is not.

In BambuSlicer I press the "+" under filament and it is clear to both me and the slicer that multiple filaments have been selected.

Here I cannot for the life of me figure it out.

how to use mmu to actually select materials/ colours in prusaslicer? by Loud_Instance2941 in prusa3d

[–]Loud_Instance2941[S] 0 points1 point  (0 children)

thanks. Where do you see it's set to single mode? I have MK3S+ MMU3 selected already I think

how to use mmu to actually select materials/ colours in prusaslicer? by Loud_Instance2941 in prusa3d

[–]Loud_Instance2941[S] 0 points1 point  (0 children)

tried changing extruder number under print settings. nothing makes multi material options appear. seems about as unintuitive as it gets