Here’s an interesting bug I’ve found in the newest firmware.
- Have filament loaded in from the spool (I.e., not the AMS)
- Navigate to “Filament”, select the spool, then select Load. This is the first bug; if the filament is already loaded, it should not be possible to load it again.
- Then select “Unload”. This is the second bug. An Unload operation should not be possibler while the Load operation is in progress
- Eventually the “Retry/Done/Close” dialog for the load operation will pop up. Select “Close”. This is the third bug. Hitting “Close” will leave the printer in a state that looks like it’s still in the Load operation, the screen will show that a Unload operation is queued up, but nothing happens.
A 3-in-one!
I hope you opened a ticket on that one.
The forum seems like it’s the right place to report bugs that I don’t need immediate support on. After all, there is a “bug-report” tag.
@SirWill , @BambuLab , could you comment on this?
Speaking of which, I’ve found another bug that I think is just another manifestation of the bug above:
- Have a filament loaded from the spool.
- Start a print job from the slicer that uses the AMS.
- The printer will have you remove the existing filament.
- Then nothing happens forever. A power-cycle is required to get the printer functioning again.
There are a couple of BL employees that monitor this forum, but do not respond to all “Bug Report” tags. If you find something, open a ticket. Best way to solve it for everyone if it is indeed a firmware issue.
Sure the bed or hotend weren’t heating up? It doesn’t look like its doing anything while it waits for that.
1 Like
I’m quite sure about that.
Update: Turns out I hit “close” rather than “retry”.
- I think “retry” is a poor label. Perhaps “re-check” or “Done” would be better for that dialog.
- It’s still a bug that hitting “close” makes the printer useless.