Getting HMS: 0500-0400-0001-0049 Error, right after each print.
Printer = P1P Enclosed / Firmware 01.09.00.00
AMS = AMS 2 Pro2 Firmware 02.00.19.68
AMS HUB = Firmware 00.00.00.43
Bambulab Studio = Version 2.2.1.60
Also 2 more AMS (Older version), which i have disconnected, to try to shrink the route course. Issue persists, with all of them connected or just a single one connected.
Issue has started after Firmware and Bambulab Studio upgrade to latest version:
Issue: Printer ends each print with the following HMS error code, HMS: 0500-0400-0001-0049.
AMS starts blinking double red.
In Bambulab studio, the AMS dissapears.
To get it all up running again, you have to, switch of the printer and Bambulab Studio.
Then you can go for another print.
The above HMS error code, isn´t mentioned anywhere by Bambulab.
AMS HUB vs. Filament Buffer.
Tried to change the AMS Hub to the Filament Buffer delivered with the P1P, which doesn´t solve the issue. Same HMS error code pops up when the print ends.
On Reddit: BBL Users are there begining to write about the same issue, with the same HMS error code.
Just did a Downgrade of both Printer Firmware and Bambulab Studio. Downgraded Firmware to 01.08.01.00 Downgraded Bambulab Studio to 2.2.1.58
AMS and hub firmware persist the same. Result = issue solved. No HMS error, AMS stays in Bambulab Studio, after a print.
If you restart the printer, it works again. I did some cable test, with new cables before downgrading, which didn´t do it.
But i did a downgrade, which solved the issue…
Think Bambulab was to quick to get out of beta version
Follow up 2 hours later, I rolled the firmware back to 01.08.01.00, works fine now. Don’t see any new features that I lose that I care about. Thanks for the help to the folks above.
Looks like a known firmware issue they are working on:
Dear Bambu Lab Customer,
Thank you for your contact and we have received your information.
We sincerely apologize for the inconvenience you’ve experienced, and we’re fully committed to resolving this matter for you.
This is a known issue in version 1.09. We would like to ask you to try performing a factory reset while using version 1.09, which usually resolves the problem.
If the issue cannot be resolved, we kindly ask you to downgrade to version 1.08 for the time being. Our R&D team is currently working on a solution and is expected to release a hotfix in the future to address this problem.
If you have any other question or need further assistance, feel free to contact us and we’ll give you further assistance.
HA! - I’ll probably just do what gets it going for a couple of days - turn it off and back on - vs going through a whole setup again on this thing or just leave it at 1.08 for now.
I just encountered this error after upgrading to version 01.09.01 on the P1S. Rebooting has resolved the issue for now. If the problem reoccurs, I will try performing a factory reset.
We’ve been dealing with this issue for months. We have been restarting the P1S between every print, and hoping a fix would be released. I tried multiple factory resets with 01.09.01, and it didn’t fix the issue. I finally just found this thread and reverted back to 1.08. That seems to have fixed it. I hope they can figure this out eventually. I don’t like being stuck in the past.
I posted in Sep 2005 the same error after updating to v1.09.00.00…
Today I’ve updated to the v1.09.01.00 and got the same error (again) HMS: 0500-0400-0001-0049
P1S: 01.09.01.00 AMS 2 Pro (1): 02.00.19.68 AMS 2 Pro (2): 02.00.19.68 AMS Hub: 00.00.00.43