After updating A1 to the latest firmware it won’t allow me to run print job sometimes, and even when i able to send it and start it, it gives random errors like AMS motor overloaded, or can’t push filament which were not present in previous A1 firmware, and there actually were no such issues until the update.
About firmware mismatch error, this is limitation of BMCU and it always been there and never affected print, and error itself is fine, but canceling your print without consent is absurd.
Oh and btw, the developer of BMCU firmware is the same guy who was threatened by bambu because of orca fork,
There’s a difference when BMCU doesn’t work and when new firmware introduces a specific way to stop you from printing when you don’t use official hardware which was not present in older firmwares.
The same thing as when paper printer blocks you from printing when you don’t use their overpriced official ink. Is it fault of third part ink manufacturer? I don’t think so.
I am not sure if I ever saw an improvement when updating the P1S firmware, I had no bugs since I bought the machine a year ago. My only problems are with the AMS itself (internal filament hub broke a few days ago). Looking seriously to setup a backup system with the BMCU and downgrade my printer firmware to 1.08.
I don’t use cloud anyway and work in LAN & developer mode since ever.
Thanks for the help, yes i know about this, when i created a reddit post so many blamed me for not reading docs properly, but these seller use old legacy firmware that stopped updating and it’s compatible with older firmwares, i use a new one, that in theory tested up up to last but one firmware version. And i already downgraded it, it seems to be working fine, my call was to bring attention to this issue, since it’s an artificial limitation.
yes my bad i didn’t see that, but still, why on previous firmware the same HMS message wasn’t issue, just an error, but in newer firmware, incompatible version suddenly became an issue that allow them to cancel the print?
Interesting thing i found out, the drama with Bambu lab and orca fork is actually started because developer tried to fix BMCU compatibility issue in the first place, not to just add cloud functionality to orca:
If i understand that correctly, Bambu did everything but not allow people to use BMCU with latest firmware, by blocking it with firmware updates and by treating legally developer to shut down fork and the only solution that was available.
The hilarious thing is that the consoles are much, much worse offenders at locking things down and prosecuting jailbreakers and modders - especially nintendo - yet everyone loves pikachu and forgets about the company that makes it. I actually think the whole current bambu “bad pr” thing is some kind of government plan to break depenence on imported printers. People really don’t care judging by console and iphone sales.
Don’t say that 3 times while looking in a mirror with a modded switch. They’ll GET YA!
Makes me think of their whole dock situation with the switch 2.
I’m sure there’s a certain level of lockin that is driven purely by money, but I think there’s a certain level of truth too that comes with the issues of third party stuff.
I think the real hucksters here are the ones selling the device, the BMCU. They openly know that it’s not supported by Bambu, and can break with firmware updates, but they’re still happy to take your money to sell you a potential brick.
I’ve seen this all play out a few different ways too. I mean, the amount of users that had AMS issues, talking about what crap it was, but then as you dig in, you realize it’s modded to the moon and back, and it’s like dude. You keep modding it to fix problems, but you’re only making the problems worse.
Or the consumer that falls into these advanced techy DIY projects, that aren’t ready for it, then mess their machine up, then go crying to Bambu, or whatever manufacture, about how it’s broken.
I guess it’s funny, because speaking of Nintendo. They pull this kind of BS too, but I have to admit, you know, I know what Nintendo is when I buy a Switch, I knew what I was getting into. I like the idea of a hand held console I can do all sorts of neat things with though, but then I’m looking at those cool emulation retro handheld console systems that ARE open like that.
It’s easy to be annoyed with Nintendo, Apple, Bambu, but I think there’s some level of that annoyance that is upon ourselves for choosing products from companies that we very well know how they act, what they’re about.
It is not the same, Bambu is adding stuff to make it intentionally difficult. In your slow leak example: would be then → your tractor needs to go back to John Deere to detect the wheel has been changed after the repair, oil changes, etc.
They have every right to modify their software and firmware to make it do whatever they want. It’s theirs. And yes, John Deere, Apple and dozens, if not thousands, more do the same thing. You agreed to it when you bought the machine and on every update. Change your diaper and quit crying about it. BL is not going to change it (firmware or diaper) for you.
It doesn’t work like that, the changes were made after i bought the printer, so they altering the TOS.
If you like to be treated like that, and defend company greed, well good news for you, you are perfect customer for them and don’t worry, they will treat you even worse and you will keep defending them.
Gladly we have EU and the same story was when paper printer companies were heavily penalized by blocking third party ink after people bought it.
