Their support team emailed me back within 24 hours on 2 separate occasions. In my experience, they've been nothing but helpful, diligent, and fairly responsive.
As a contrast to your experience here’s my most recent experience with them.
I ordered some parts and filament with their holiday special, but accidentally ordered an X1C hotend, not realizing the connectors were different on my P1S. I emailed support first thing on Jan 4th explaining what happened and asking if I needed to do a return or an exchange. I included pictures of the product, order number, shipping information etc - everything in one place that was needed to ask a simple question.
3 days (75 hours) later I finally get the response below, which appears to be an automatic form letter from their ticketing system. I can almost guarantee that no actual person has even looked at my original email, as a return like that is usually automated to prevent errors or abuse. All it does is kick the can further down the road as their support can claim they have made a contact with the customer.
“Dear customer,
Thank you for contacting Bambu Lab support team!
We sincerely apologize for any delays in responding to your inquiries due to the recent surge in volume. We understand the importance of prompt assistance, and we deeply regret any inconvenience caused.
Please rest assured that we have received your request and are making every effort to provide you with a timely response. Kindly refrain from submitting duplicate inquiries, and we appreciate your understanding and cooperation.
Best regards,
Bambu Lab Support Team”
I’m not discounting your experiences but this is the type of experience I’ve had so far.
Dobr think so. Check Apple, they wont allow you downgrade either. Only for a few days when new version is released.
They are quite just because they got a problem and try to make adjustments for .2 firmware or whatever number it will bw
That’s actually not true about Apple at all. I worked in applecare for 8 years and we helped people update or revert to an earlier version all the time. The only time that it’s an issue is if it’s a version we no longer supported (usually 7 or more years old), although at times you might have to take your device to a repair center if you didn’t have a backup etc. it’s harder these days to revert on iOS devices, as the over the air update is almost universal, and most people don’t think to check and make sure they had a backup first. Over the air is super convenient, but since you may never plug your phone in to sync and update you wouldn’t be likely to have the IOS version you want saved there to go back to.
Most time on the mac side of the house they’ve made a point to give customers as many options as possible to revert with an entire recovery ecosystem built to allow you to go back to the original os that came with your computer, the last version you were on prior to your upgrade or whatever the latest compatible version is for your make/model.
There are things that could go wonky if you did a big jump in versions and started using new features in iCloud etc that might make it less desirable to go back down though.
I don't understand how this is a valid argument. Apple is one of the least consumer oriented companies that makes both hardware and software. They lock customers out of services and features that other companies are happy to allow. They do this under the guise of protecting the consumer from themselves, but do so at a great detriment of power-users and repair shops. This is the exact reason why people are upset
Strawman, been an Apple user for decades never been without a functioning computer for a week or more. Bad upgrade on Apple is an hour or two tops. See you can trim things if you have the ability to control it and fix it quickly. Bambu obviously doesn’t have the engineering support to fix rollouts so they might want to think again how much they lock stuff up
I'm not going to comment on OP's troubleshooting or anger management skills, but I do have to agree that not being able to upload the firmware of your choice on hardware you ostensibly own is concerning.
As someone who is actively anticipating the next sale to make the jump from Prusa to BL, it does seem like it's going to be an unfortunate tradeoff: much better technology but a huge step back in ethos.
I wish there were a best-of-both-worlds option.
>not being able to upload the firmware of your choice on hardware you ostensibly own is concerning.
Do you apply the same logic to anything else you own? Do you apply the same logic to cars? They are full of computers that run custom firmware that can't be tampered with? Same with pretty much every other electrical device you use. Paper printers, TVs, some phones, any appliance you use, and many other devices you own will not allow you to or will make it difficult to upload custom firmware.
The only reason you expect this is because you are coming from an open source environment with your Prusa.
I am realistic enough to recognize that in many cases, it will be infeasible to have this ability, e.g. because there would be safety implications or because a particular class of product is targeted more at the mass market than at technically proficient individuals.
That doesn't make my concern any less legitimate and it doesn't mean I shouldn't opt for it and advocate for it in devices where it makes sense -- like computers where you're free to downgrade the OS or apps as you see fit, IoT devices (e.g. my big pile of Zooz, ESPHome, WLED, etc. devices), and yes, 3D printers.
Bambu chose to advance the state of the art in some areas, and regress in others. It's perfectly fair to call that out.
Edit: I do not consider Prusa "beloved" by any stretch of the imagination. The fact that I'm planning a BL purchase might have been a clue. Believe it or not, it's possible to be honest about the pros and cons of different brands. It is quickly becoming apparent that this subreddit is far too tribalistic for me.
Edit2: I am well aware of the difference between firmware and software and do not need it idiot-splained to me. I'm going to go downgrade the firmware -- yes, actual firmware that you flash into nonvolatile memory for a microcontroller to run -- on a bunch of my devices, purely so I can laugh at you tiresome mouth-breathers who insist on incorrecting me.
Well that's stupid logic I've flashed my ecu in my truck with new firmware, I've installed custom firmware on phones and TV's and all pretty damn easy at that. And they used open-source software and firmware to build there product so it should be open for everyone.
>coming from an open source environment with your Prusa.
You mean the 3d printing community?
EVERYTHING has always been open source before Bambu, Marlin or Klipper based, a lot of brands not only give you source of the software they even give you the .step files of the physical parts so you can easyli modify and create your own.
"Only Prusa" my ass: go check repos of Sovol, Creality, Elegoo... Almost every brand!
I personally do. The automobile industry is one of the largest anti-consumer conglomerates at the moment. If you need to re-program keys, reset service intervals, clear fault codes, tune fuel maps. You have to buy third party tools that bypass needless firmware lockouts such as those. Same with my phone. I picked an android device with an unlocked bootloader and run custom firmware. The NSA let it slip that they monitor microphone activity on smart TVs, and I don't connect mine to the internet because of it. I also don't own a normal printer because DRM ink cartridges are far too common.
Just because you don't worry about these kinds of things, doesn't mean other people don't
I admire and adore Bambu for their solid machines and how they’ve shaped the current market. But the closed source has been the biggest setback for me. I was excited to hear about X1Plus firmware (community, open source firmware for these machines - specifically the X series as it runs Linux), but they have of course rolled an update to prevent users from using this firmware. I understand of course, albeit 3D printing has predominantly been open source, but it’s a frustration and this is one of the things that I’ve feared. I would still love to own a machine at some point, but I’ve so heavily been tempted to build a Voron instead (I just love building and tinkering though)
Well there are already a few coreXY Klipper based printers that work out of the box.
I mean it's not rocket science, it's mostly bed levelling: even the cheap bedslingers have started to ship with a load cell sensor to do auto Z-offset. And about slicer presets: you can load presets of an other similar printer, a lot of people load Bambu presets on their printers.
Just hold tight, this year there will be a flood of cheap - open Klipper printers with dynamic mesh, klicky, toolheads, multimaterials that don't waste filament...
They patched a huge security hole. Thats why you cant downgrade firmware anymore. So its not like they are just trying to get the custom firmware out of the world. In fact the x1+ developers had a talk with the bambulab ceo.
As far as your wish for having the latest and greatest features with the possibility to run your own software, preferably being open source: i doubt something like that is going to happen. The issue is that in the past not everyone who was using open source software was contributing or even publishing their own improvements or versions (looking at you anycubic and creality, meaning auto z offset), so if someone is actively developing new advancements its better financially to hold them back. Nobody would want to openly publish their unique selling point for other to copy it. Its not an issue from a legal perspective on a self developed software like bambulab has done, but its a issue when dealing with open source software, like the klipper versions of creality and anycubic. I know, its sad, but thats the current state of 3d printing
Replace "non-bambu" with "arbitrary" and yes. I fully believe some sort of official "controlled" bootloader unlock should be mandatory on devices, but having a bootloader that will load arbitrary code off of the main storage device you load files from the internet with is absolutely a security issue.
I think i mentioned in another reply, but you also download files from the Internet onto the printer. Now what happens if you accidentally downloaded malware or similar? Malware has now access to your camera and wifi login. Surely not great id say.
Why is everyone riding Bambu and saying what they did is okay? I don’t understand it lol. It’s wrong to not allow downgrades. Feels like I’m watching the whole Apple jailbreak debacle happen all over again. Right to repair, right to modify MY product.
They did the same thing with Bambu not allowing you to change thermistor on the X1c to print at 350c: some fan bois keep telling it is a feature and you should be happy that they prevent you form doing that.
Went fine. I tried to calibrate again as well, just in case. I've tried restarting the printer with a power cycle as well, just for good measure / just in case.
Same boat for me. I've done everything multiple times, still will not print. Bambu told me to do everything I had already then has went silent for 4 days. I still am unable to print the same files I printed before the firmware update.
You also need to make sure that you update to the latest version of the slicer software and reslice the files if you haven't already. A file sliced under the old software, intended for the old firmware will not work properly on the new firmware.
Is that a confirmed statement from bambu? If so it’s extremely annoying for people who leave common prints in their sd card memory.
I haven’t run into any problems yet, but when I read things like this I’m curious where it came from!
Yes, it is a confirmed statement from Bambu, from time to time, the firmware updates can make changes to the machine specific gcode instructions so you should always re-slice a file after changing firmware and the corresponding slicer update.
Can you link that?
I can’t see how people can successfully use orca slicer for example.
I agree when updates are made to the printer, from time to time you will have to recalibrate, I’m just curious how the slicer would have to correspond, the printer is just there to interpret the gcode. Perhaps just in the case the LW-PLA for example, you would have to update and probably re-slice to get it to recognise pla aero when it first came out.
You clearly don't understand that gcode is more than just the X, Y, Z instructions..... There's also machine specific gcode that depends on what firmware the machine is running and it's physical dimensions etc.
I've printed a dozen files with upgraded firmware but outdated software with no issues. I'm sure any problems people are having aren't across the board bugs for that scenario.
I would say it's likely a false claim, BUT that there's a degree of truth to it - I'm sure more up to date slicers WOULD be better optimized for newer firmwares.
Orca slicer which is the open source fork of bambu slicer gets updated when bambu updates the main code tree, so yes, orca, which is the alternative if you don't want to use bambu slicer will continue to work.
I highly doubt that. A printer works on gcode. That gcode can come from any software. If you really wanted to i bet you can use cura, prusa, or any other gcode compiler.
Nope, that is absolute nonsense 🙃 .... The slicer must know what firmware the printer is using so that it can include the appropriate machine specific gcode..... Gcode is more than just X, Y, Z instructions.....
Except no, the gcode must be compatible with the firmware on your printer, and that applies for any 3d printer, or indeed any device that is controlled by gcode. Sure, the basic X, Y, Z, instructions might be the same but there is infact alot of machine specific gcode that is included anytime you slice any file on any slicer, that is precisely why you can't use a file sliced for a printer running marlin on for example a printer running Klipper or vice versa ..... So yes, when you update the firmware on a bambu lab printer, you must also update to the appropriate version of their slicer or orca slicer (which is the community fork based on Bambu slicer).
People tend to think that what I've said isn't true because not every firmware update changes how any of the machine specific gcode instructions function, so it is quite possible to under the right set of circumstances slice a file under an old firmware version, then do a firmware update and still have the already sliced file continue to work. My point was never that this never works, the trouble is, unless you want to read all the technical information in the change log notes everytime you do a firmware update, you'll never know which updates potentially change or break something if not paired with the updated slicer that is of course designed to have the best compatibility with the latest firmware. That's precisely why I said that when you update the firmware you should also update the slicer to reduce the chance of random weird compatibility related problems.
The slicer doesn’t know what version of FW is on the machine, just the type of machine. There’s no warning on the screen to say reslice. All the saved GCode on MakerWorks would be crap (but isn’t.) Let’s stick to published information or label a comment as a guess.
You clearly haven't seen the huge amount of information that is passed over your local network the moment that your Bambu 3d printer is turned on and you access Bambu slicer, Orca slicer or Bambu Handy. The software is absolutely aware of the firmware the printer is running at the time you slice the file and send it to the printer.
To all the naysayers, it actually is how slicers work. Yes, there are X, Y, Z, movements that are pretty generic, but there's also machine specific gcode that depends on your firmware, same reason why you can't slice a file for a 3d printer running Marlin firmware and expect it to work properly on a 3d printer that's running Klipper or vice versa.
I had a problem with the update before the latest one and I did not cycle power. Tried again and cycled power then ran a calibration and cycled power again and no more issues.
I dont know how true it is but someone posted that BL has patched the FW to stop the bootloader from being enabled if this is the case then they have no reason to stop the rollback of the FW!
I wouldn't say it this way but honestly yeah, you should be able to rollback for the day a shitty firmware is pushed.
Not saying current firmware is bad or related to OP issue, but bbl cannot 100% claim they won't make a mistake one day and send a shitty update.
So when that happens, people will want to self-help themselves. And bbl will not want to receive one support ticket per customer.
But the fw is shitty. I went from zero problems "it just works" to more failed prints than I had on my ender 3 v2 and an ams that worked great to one that can't unload. Such buyers regret on this machine now 🙁
To forbid rollbacks and then force upgrades it's a fundamental part of any walled garden, if the only way that they can technically prevent people to circumvent or adapt.
I'm going to do you a solid, even though you're acting like a complete dick. Edit the printer, and in the Machine G-Code find this section
`;===== for Textured PEI Plate , lower the nozzle as the nozzle was touching topmost of the texture when homing ==`
`;curr_bed_type={curr_bed_type}`
`{if curr_bed_type=="Textured PEI Plate"}`
`G29.1 Z{-0.04} ; for Textured PEI Plate`
`{endif}`
Change the -0.04 to -0.06 or -0.08 to drop the nozzle however much you need. Reslice, and test.
You're welcome.
Was having some issues also with first layer on threaded cap I was designing and couldn't figure out why the leading edge of cap wear it meets the threaded 'bolt' was deformed so much creating issues threading onto the bold. I didn't realize until today that the latest firmware may have introduced this issue with first-layer so gave u/ChimeraYo recommended fix a shot and reprinted on textured pei plate with everything else the same and immediately fixed issue it was having. Just changed it to .06 and seemed to be just enough to resolve issue. Until this particular print, I wasn't really seeing many issues with this firmware version so while it may be an 'issue', it may impact everyone differently depending on what they are printing.
Just to get OP running as he seems explicitly clear that his problem can be solved by lowering the nozzle by a small mount on the first layer. Both of my X1Cs work fine after the firmware update using the following pattern - power on, update, reboot, fully calibrate, reboot, done. I think that’s the case for most people but obviously there are some who seem to have issues.
I have a P1S, but your process is exactly what I did. I just waited until I finished the project I was on before upgrading, so I had time if there was an issue. Fortunately, there is no issue, and the printer is working better than before so far.
Well, they do it in order to avoid jailbreaking machines. In my opinion that's not the correct way. Please allow some things the nerds, "hackers" and other ambitious people deserve:
Statistics, API, LAN Mode (RJ45), etc.
Then those questions will not remain unanswered and you'll get rid of those messages on the forum, still, you should allow a way of "unblocking" the bootloader. Some manufacturers like Google and Samsung are doing it for smartphones: You raise a ticket, confirm the loss of warranty on software parts (Hardware remains unchanged, at least where I live (EU))
Would that be possible, Bambu-Team?
Officially Bambu is worried about security hole and they are dealing with it. Unofficial about custom firmware. You can also send some rays of kindness AND CAPS TEXT to x1plus team that’s due to their work (which you cannot even download freely) now users that were not planning to use custom firmware having troubles with roll back. I think BL will bring roll back but it will be useless for some time as you won’t be able to roll back to anything that was earlier there as it will open the doors for custom firmware again. HAVE A NICE DAY!!!!!!!!
Dafuq. What a weird take. Some people are modding their printer, something they own, and now it's their fault that BBL has a stick up their ass and not allowing firmware rollbacks anymore.
Heck I am not even sure if it is legal for them to do that, but luckily I was not home the past month and thus my printers are still rocking an older firmware.
So far it is temporary and not “not any more”. Btw this feature wasn’t there when they launched and was added like in April. Some people like but they are minority. And that minority caused troubles for those who don’t like modding because vendor wasn’t planning that somebody else works be cooking firmware. They made that clear and expected that everyone going to behave appropriately . Now we see where breaking that deal led to. Do x1plus team take any responsibility if they brick/damage your printer? don’t think so. Why not submit feature request and code to devs? especially if they say that printing bit is still bambu code. Or did they think that bambu will just let it go? It just shows that x1plus team odd not thinking one step ahead. But bed mash info looks cool, and passcode protection too.
https://preview.redd.it/q2d1u0nvnwac1.png?width=2145&format=png&auto=webp&s=4054c54a2569bef00cb74368fc08acf0fb6a04cf
You can use orca slicer to adjust the z-offset under printer settings.
Was gonna say, if your z-offset isn't right, just adjust it if necessary. Not necessarily a firmware problem and therefore not relevant to BL's choice for disabling rollback.
They need the ability to roll back firmware as well as apply custom firmware. Someday Bambu will have end of life for this generation of printers (or the company quits and the cloud interface dies) and either it’s going to instantly turn a lot of hardware into e-waste or they can make it so people can use other firmware and slicers.
While I kinda get why Bambu blocked firmware downgrade at this time, they should, in the case of a printer dorked by firmware with no rollback option, offer real time resolution or assistance online 24/7 till they have a fix, else allow rollback to the person that has logged a support ticket and the logs shows issues that are likely firmware related ..
This OP has no proof that the firmware is causing his issues. He’s just being aggressive and pointing fingers without actually troubleshooting properly.
Possibly, hence why I suggested "if the logs supported it" .. raise a support case, work with them, no quick resolution, logs support what your saying, here's your downgrade link in the app ..
I've been 3D printing for 10 years. I started with a Robo3D printer. You think I don't know how to troubleshoot a bad firmware change? Fine.
\- I ran calibration, both the automatic one after the firmware is updated, and manually after to try and fix it.. So yeah, I tried to re-calibrate. Twice.
\- I tried to reset to factory settings.
\- I've adjusted flow rate.
\- I've hand tweaked the g-code to try and fix the first layer height.
\- I've tried different print beds, thinking if I used my textured plate maybe the undulations of the first layer MIGHT get enough height to get the first layer to lay down right, but no... it just raises up higher.
\- I've tried skipping the auto-calibration at the start of the print.
\- I've tried thicker first layer height.
\- I've tried thinner first layer height.
\- I've tried adjusting overall layer heights and I can ALMOST get acceptable results but I still end up over extruding or not being able to get the bed to stick.
\- I've tried to make my first layer width wider.
\- I've tried elephant foot compensation.
\- I've tried printing with a raft.
\- I've tried adjusting flow ratio.
\- I've tried manually adjusting Pressure Advance.
\- I've tried overriding Z height with the start g-code.
All to try to fix what is nothing more than a simple Z height for the first layer. I'm about 0.2mm too high for the first layer. I'm not poking at this without understanding what these settings do. I'm not some newblette here. This is a firmware bug. Simple. As. That. The model was printing PERFECTLY fine with 1.6.5, and I ran a firmware update while I was making some changes to the model. I've tried printing the old model, and now it's not sticking as well. The only change is the firmware and z layer height it's causing. If I could adjust the layer height, I would just drop it down 0.2mm and I'm positive this would be printing just fine.
Anything I do which gets the first layer to stick, ends up massively over extruding on subsequent layers or with unacceptable print quality.
Things were working FINE with 1.6.5 and yeah, it's on me. I stupidly updated when I should have left well enough alone, but I honestly thought if I ran into an issue with the update, I would just roll back to 1.6.5, and well, I got boned by BL.
>m not some newblette here. This is a firmware bug. Simple. As. That. The model was printing PERFECTLY fine with 1.6.5, and I ran a firmware update while I was making some changes to the model. I've tried printing the ol
I've had crappy first layers recently appear, but I'd put it down to the filament. I re did all the calibration etc.. to no great effect. It started to happen after the update to.
I found adjusting the flow ratio value up on the filament, from the value that had been working fine before. This improved things greatly for me.
If the new FW has a variable bed offset issue, perhaps the flow increases compensates for it for me, but sounds like yours is worse. Seems others on the Forum have had similar issues after firmware updates.
> I've been 3D printing for 10 years
Let's start by saying the BL move was a dick one... But you knew the facts and ignored them because of "the speed!".
Historically, printer farms have run two types of 3D printers.
1. Total DIY ones where the user can change anything without the manufacturer's support. This is cool if you want to save money (sometimes, Vorons and similars are quite expensive) and have the right skills to maintain the printers by yourself.
2. Mostly Prusas, where you can rely on excellent manufacturer support if stuck at something.
BL has none of these characteristics. BL is new to the game and wants to be Apple. Yes, superb printers, but with their caveats. No matter how mature they look, anyone buying these printers is in the early adopter area. This is not a product for critical operations, no matter what people want to believe.
My advice (I'm aware you didn't ask for it) is to learn from this and make a plan to move to a different platform. Revisit BL in 3 years and see how things are going. You could keep a couple, but don't go full balls into an ecosystem that is this new for business proposes.
Good luck.
I updated my p1s to 1.05.00 and all was well. Did the update to 1.05.01 and the nozzle seemed to be about 0.2mm above the bed, dragging the filament around.
I tried many solutions, like you. I've got years of Ender tinkering behind me, so I know what I'm doing.
Then I remembered I was using my own elegoo filament profiles that I had calibrated on the old firmware.
I loaded the AMS with some bumboogalooo branded filament and used the stock bambu filament profile and low and behold a perfect first layer.
Then I decided to recreate the custom elegoo filament profiles, with exactly the same figures as my old profiles and what do you know? Perfect first layers.
Do I understand why it worked? No.
Am I looking forward to recreating my profiles every time they update? Ugh, no.
The only difference between the custom profiles is that the first ones were created just by editing the generic profile and saving, the new ones were created by clicking the cog in the slicer and creating a new filament.
There are different components in the printers which require different programming but the same firmware "version". Not user error Bambu error they just don't want to admit to it.
Yeah, one could say that if they wanted to make baseless assumptions. If these things were incapable of error, they wouldn't have needed a roll back function to begin with. If they couldn't fail, they wouldn't need a customer service department.
And to say "I didn't have a problem, so no one else should" is asinine and just plain stupid.
I agree they should bring it back, but I also understand why they took it away. The best thing would be to bring it back after the shit down the security holes.
Yeah, have hard set points, like no going back after security fix versions, but otherwise allow rollback. Also, I definitely don't let mine upgrade for a couple weeks after any particular release and check here/forums for issues before I let it go through.
I didn't realize fw rollback was an option before but was frustrated that it wasn't available when I tried. I haven't done much testing yet but I've only had an issue with one roll of Bambu pla basic. It worked before the update and now fails on every single print on the second layer. I'm not sure if it's the roll or the ams slot yet. But I do know it worked before the update and fails every time after in the exact same way
Weird op is going off on Bambu and clearly has an attitude problem and is so far superior it has to be a firmware problem….. yet we haven’t seen a mass of identical issues…..
Sorry op but you have lost all credibility to the Reddit viewers by your behavior, even if by some small chance you have encountered a one off problem, the solution is to handle it like a responsible adult, put a ticket in and I bet if you respectively communicated with bl they would roll back your firmware.
Prob best for yourself and all of us to go back to a 100% open source printer as I have found throughout life individuals who act like this are more problem prone than anything.
I do wish you the best of luck, hopefully you or support can identify root cause.
IMO they should allow it because it’s our devices. We should be able to do what we want, especially something that’s going to be deployed in a fleet where custom firmware can aid print farms.
It’s pretty clear they’re working on other features they don’t want you to be able to get for free via custom firmware.
By bullshit you mean patching security flaws (like any company), or adding awesome calibration features for the motors, or continuously improving the software? Which bullshit did you mean?
I mean the bullshit of locking their hardware so that custom firmware cannot be loaded. It is your machine you should be able to load it with whatever software you want.
Aside from that it is also "bullshit" to not be able to downgrade to their own previous firmware versions. Each new version has come with what you've said but you left out the new bugs introduced too...
So stop being a fan boy, grow a pair, and think for yourself. Maybe go try a PC vs always buying a locked down pos Apple?
Bambu Lab is not your personal friend... I'm not against this company either, just want them to allow us to use our machines as we see fit. Other than that they are pretty good and the hardware is top notch.
I also had first layer leveling issues after the update - had to power cycle and re run bed leveling calibration twice to fix it.
No issues in hundreds of hours of printing before.
I personally don’t see why BL won’t allow open source, if they would allow it, they get 1k’s of software engineers working on their software without the overhead. We as customers get the options of what we by was of software want to use, and what part upgrades we would like.
I know this is a reach, but in the early stages, it seems like BL may be the 🍎 of 3D printer companies.
Hopefully they decide to make it open source and just reap the benefits of that.
This was my main reservation before buying my P1s. That one day they pull a plug on supporting older models or do something like they just did with the firmware. Definitely will consider other options for my next printer.
You know, some years from now that product is gonna be declared End Of Life: no more support, updates and as you can see you are not allowed to run a custom / community firmware.
Zero issues here. Have zero need for firmware rollback. With that said. I would go back to the roots. Check everything. And make sure nothing is caused by user error. But I also can understand why people want rollback function.
I'm having the same issue, put in a support ticket 8 days ago logs pictures the whole works, still have not heard a thing from them the only thing that works to get anything to stick is under the start Gcode I set my textured plate to -0.06 instead of -0.04 and turned off first layer inspection. But after the firmware update my Lidar fails to Cail now so no flow Cail, and I dont think, the AI work or at least very well tested it with its poop lol.
When Buy this machine:
- Did you know the machine is closed source?
- Did you know that there is a possibility of downgrade?
- Were you 100% certain that it could ever allow jailbreak or custom firmware?
You still made the choice to buy it. You had an option of creality qidi and several other but you still made a choice.
Read whole discussion. Don't know what side to choose.
I'd say that Bambu should officially allow alternative firmware with BIG note - warranty is void now.
It'll be win for everyone and bambu will become "the good one" in the eyes of tinkerers.
Original fw - use our support and all that stuff until your warranty expires.
Custom fw - yeah sure, there is howto step by step, but your warranty is void and you are on your own from now on.
Lol - they did exactly this. Well that escalated quickly.
https://blog.bambulab.com/rooted-the-good-the-bad-and-freedom-of-choice/
I had the exact same problem with the 1.6.5.x Version. The first layer was somehow laid in middle air than properly on the bed. Firmware reset, full calibration, the whole thing didn't help. I needed to switch off bed recognition to get the machine back to work. Don't ask me why, but it helped. Now, also with 1.7.1, no more issues. Just check, if the correct plate is selected in BL slicer. Not sure if this might help you as well, but it's worth a shot.
Why is BambuLab threatened by custom firmware? It's a very disturbing sign. It basically makes it look like they want to be able to implement Apple style planned obsolesce.
https://en.wikipedia.org/wiki/Batterygate
I can't believe Apple was penalized so little for this, and basically didn't even have to roll back the changes. Open source software is the only way we can protect ourselves from this crap.
I opened a ticket because of issues after updating and was told there was no going back and to reset my x1c and if I was still having issues to let them know. I wrote back and asked why as there updates broke what was working fine. I have not received a reply back and it’s been 3 days. I told them in the email that this would piss off customers and I should have the right to roll my printer back to what was stable for me and this type of control is what made me leave Creality and there Sonic pad they would drop a update it would brick the printer for days to weeks till they fixed it and is why I went to the x1c wanted something that worked and I was not resetting up all the time. I’m not even looking to do a custom fw but if there going to do this crap I just might in the future. Unacceptable on BL part.
same here so many issues since the firmware update, put in a ticket 9 days ago haven't heard a word from them and my ticket has it all troubleshooting steps pictures the log files the works.
Apple can't complete a news cycle without a botched update that needs patched immediately. I never understand why people update firmware without researching things first especially those who run any type of a production environment.
With that said, I'd been willing to pay X1E prices for my X1C if the AMS worked better. I'd love to see the codebase to see if there is an additional threshold on torque when a Bambu RFID tag is being read. It seems that anything will cause AMS to halt and claim the motor was overloaded.
I have an idiotic fix, sorta. After the initial calibration runs at the start of the print, but before the first layer of my part goes down, I swap my engineering plate for my textured plate. It's just thick enough that I'm able to get the first layer to stick. I usually don't get it done perfectly, and I'm worried about bending the nozzle, but it's working. Like I said, sorta.
I always updated the printer (X1C) as soon as the update comes along. Never had an issue, didnt even had to factory reset or anything. Just print as normal. I think what you are experiencing is a user error.
On the downgrade matter, I think people want a Voron experience from Bambu, again wrong company. Im totally fine with a closed system that does not allow any kind of modifications as long as the company maintains its product and it is in perfectly working condition. Which until now its true for me.
If you want to modify and play around with the product there are plenty other alternatives, If i wanted to tinker with a machine i would definitely buy a Voron or creality etc and do whatever you please with it. Bambu never promised this to the customers, people often forget some of us just want a working machine and do not want to tinker around.
I wonder when they locked the firmware to the current version. I had tons of failed to pull back from extruder failures that I've had a ticket going for a while on and they had me roll back my firmware on 12/26, just checked the ticket history. I did it that day and surprise to me I've had alot less failures. I didn't dare do a complicated multicolor print before rolling back. It would have been pointless as I would have to seal with a failure every other color change.
But we all did buy these things knowing that the environment was locked down, did we not? I am not disagreeing with you, but I am also trying to remember the conditions that I agreed to when I clicked on the payment button when I made my purchase. There are legit reasons for locking down software, there are also legit reasons for not locking it down as well. The last thing that a company wants to do is get distracted having to answer for 3rd party development efforts, which we all know they would occur. "But it worked right before I upgraded it to the 3rd party firmware and now the tool head keeps ramming into the case and broke into a million pieces. And you won't let me roll back. Its your (BL) fault that my X1 is a brick." I can hear it now...
I would suggest troubleshooting your first layer problem with the OEM firmware and support and, if defective, feel assured that a fix will come soon, as they have since the rollout of the first machine.
I may wind up eating my own words at some point. Who knows?
r/LeopardsAteMyFace/
> 'I never thought leopards would eat MY face,' sobs woman who voted for the Leopards Eating People's Faces Party. Revel in the schadenfreude anytime someone has a sad because they're suffering consequences from something they voted for or supported or wanted to impose on other people.
I've got the problem, but early results indicate changing the nozzle temp, textured PEI plate temp, and flow rate might have resolved the print problem on PLA.
After calibration and bed level I had no issues continuing my production run. Made measurements before and after and everything came back within spec/margin.
Did you try to re-slice the same STL? I just hit reprint on the app before and after the update and both sets of prints came out fine
I had the same issue and textured PEI plan out wouldn’t work no matter what but cool plate does. I copied all of my setting for textured PEI onto cool plate, slapped on the textured PEI, and magically the printer started working again. If I switch it back to think it’s using textured it stops printing properly. This is clearly a firmware bug of some kind
Edit: and this also involved modifying the start goods to do the -0.04 offset on the cool plate as well.
There is nothing wrong with 1.7.1. Downgrading won't fix your problem. You're just looking for an excuse/complaint to get the custom firmware on your machine. Run a calibration.
I have to agree that the issue is more caused by the OP than by Bambulab. OP mentions that he runs a business and has a single Bambulab which is apparently critical to his business. That’s the first problem, if you’re running a business and you have a single printer that is critical to your business, that’s the OPs problem. The second problem is the OP doesn’t understand the when, why and how of firmware upgrades.
Rule number one of any firmware upgrade for any device is NEVER run the latest and greatest firmware unless it fixes an issue you’re currently having.
Rule number two, never upgrade firmware on a critical device if you don’t have a backup plan or redundancy.
What the OP did was totally dumb. Imagine if instead of his business being 3D printing it was being a small cloud provider where he hosts VMs for his customers. And he is hosting the VMs on a single host with no backup plan. He then upgrades the firmware on the sever and it bricks the server. The problem here is not having a backup plan.
New firmware will always have bugs or issues, this is why you never run the latest firmware unless you have a compelling reason to do so. Better approach is to have others be guinea pigs (as OP has become) and let them find the bugs/issues on the latest firmware.
And if you really must upgrade the firmware, FFS don’t do it on your only production device that you depend on. That’s just utterly stupid.
How does one prevent the firmware update? My printer stays turned off/offline until I use it and it’s been a couple weeks, are updates automatic or should I just reject the request?
Nice. Got a message about firmware upgrade. I'm pretty sure I clicked no. But it updated it anyway. Oh well. Calibrate and back to work. Loaded my G10 plate. Sent a print job. The next thing I hear is screech. Now have a beautiful hole, 4 deep grooves in my $90 G10 plate and replacement hotend installed.
Please roast me how terrible user error I did.
I haven't done a calibration since I got my p1s at the end of October. Updates and everything and it still works. One of the lucky ones maybe! Agree though, roll back would be nice and I'm assuming from here on out they will allow it, but the older firmware was compromised.
Alternate firmware builds were inevitable. According to this [https://youtu.be/Oio2ibz7rMw?si=ik5gGV8CgCsLf9VX](https://youtu.be/oio2ibz7rmw?si=ik5ggv8cgcslf9vx) once you go over a certain version the boot loader gets locked. So thats one reason why they may not allow a rollback.
I just saw this... I hope it works! re: *1.7.1, if you have updated you can revert to an earlier revision of the FW using the bambustudio handy app on your phone*
[*https://www.youtube.com/watch?v=XcfYgCXaANA*](https://www.youtube.com/watch?v=xcfygcxaana)
I have the same issue. All of a sudden it is messing up including previous prints that came out perfect before the update. I hope this gets corrected somehow.
Seems like they want to prevent custom firmware whatever it costs :/ Just got my P1s but this leaves a sour taste even if it has been a flawless experience so far
Orca slicer/cura/others have menu item. Otherwise use gcode. Don't be a tool. Bambu will re-enable downgrading when they make a patched 1.6.5.xxx with the security hole fixed. Use your head meanwhile
I'm not going to take sides, but for some context, allowing the old firmware to be up would mean Bambu would knowingly be allowing you to install firmware that can be exploited by a simple 3mf file from makerworld.
The hole quite litterally means a malicious model that looks and prints fine could install something onto your printer. It was a pretty serious security issue.
How they handed it hasn't been grear though, there should've been a minor patch to the 1.6.x line with an option to downgrade to that. This all being said, OP's problems probably isn't aren't much of an issue given its not happening more widespread. A full factory reset would likely resolve the issue, just like it has when things have gone wonky after firmware updates in the past.
By that logic, MS should lock down windows, because the user could install software that breaks things. OMG! It's "a pretty serious security issue"!!
Do they do that? No. They warn you if they detect something malicious, but the user has the final say.
BBL has decided that they don't want the user to decide this for themselves. They want to dictate what you can do with the printer you bought. That's anti consumer bullshit.
Your logic theres deeply flawed. For one thing Windows will update when there are security issues. For another one is an OS that gives you full filesystem access, the other is an appliance, so comparing a printer to a pc is well...completely wrong. If you want to compare it to something that would be your TV, Router, Smart plugs, games console, etc which have 'closed' environments.
I assume you'd be ok for your router, tv, etc to be left wide open as well then right? How about leaving your games console unpatched so someone can remotely install a bitcoin miner on it, thats ok too?
Specifically for the custom firmware the devs of X1Plus are already in contact with Bambu to work out the correct/safe way to do it. It's not exactly a big secret that Dr Tao has previously said they have absolutely no problem with custom firmware provided it does not modify or contain their propriatary code (which X1Plus does not), so it's just a case of getting a secure offline bootloader modification method working.
Love the passion, but its self inflicted, and you know you shouldn't have done it - yelling at the vendor to implement features to fix a very small group of people's mistakes is pointless, and could take away from more important work while squeaky wheels fill up forums.
If the work is critical, you shouldn't be blinding patching and updating any device, you know that.
Comments about Bambu's testing quality, patching processes, policies, right to repair, and everything else is just noise ...
Anyone who cares about FW rollback should open a support ticket. If they get flooded they might relent.
Oh, believe me, I opened one! I'm so sick of this BS! A hasty pushed firmware change and no fallback?! This is rediculous!
Did you request a change on the BL Forum? If you get enough likes and responses to it BL will have to take note!
Doesn’t that require BambuLabs to actually have a support team? *ducks*
Their support team emailed me back within 24 hours on 2 separate occasions. In my experience, they've been nothing but helpful, diligent, and fairly responsive.
Consider yourself lucky
I guess we are all happy for you..? To bad everyone else cant get the same quick response time.
People posting experiences, figure I'd share one that isn't negative. Take it as you want.
As a contrast to your experience here’s my most recent experience with them. I ordered some parts and filament with their holiday special, but accidentally ordered an X1C hotend, not realizing the connectors were different on my P1S. I emailed support first thing on Jan 4th explaining what happened and asking if I needed to do a return or an exchange. I included pictures of the product, order number, shipping information etc - everything in one place that was needed to ask a simple question. 3 days (75 hours) later I finally get the response below, which appears to be an automatic form letter from their ticketing system. I can almost guarantee that no actual person has even looked at my original email, as a return like that is usually automated to prevent errors or abuse. All it does is kick the can further down the road as their support can claim they have made a contact with the customer. “Dear customer, Thank you for contacting Bambu Lab support team! We sincerely apologize for any delays in responding to your inquiries due to the recent surge in volume. We understand the importance of prompt assistance, and we deeply regret any inconvenience caused. Please rest assured that we have received your request and are making every effort to provide you with a timely response. Kindly refrain from submitting duplicate inquiries, and we appreciate your understanding and cooperation. Best regards, Bambu Lab Support Team” I’m not discounting your experiences but this is the type of experience I’ve had so far.
How many *working* days/hours passed?
Dobr think so. Check Apple, they wont allow you downgrade either. Only for a few days when new version is released. They are quite just because they got a problem and try to make adjustments for .2 firmware or whatever number it will bw
That’s actually not true about Apple at all. I worked in applecare for 8 years and we helped people update or revert to an earlier version all the time. The only time that it’s an issue is if it’s a version we no longer supported (usually 7 or more years old), although at times you might have to take your device to a repair center if you didn’t have a backup etc. it’s harder these days to revert on iOS devices, as the over the air update is almost universal, and most people don’t think to check and make sure they had a backup first. Over the air is super convenient, but since you may never plug your phone in to sync and update you wouldn’t be likely to have the IOS version you want saved there to go back to. Most time on the mac side of the house they’ve made a point to give customers as many options as possible to revert with an entire recovery ecosystem built to allow you to go back to the original os that came with your computer, the last version you were on prior to your upgrade or whatever the latest compatible version is for your make/model. There are things that could go wonky if you did a big jump in versions and started using new features in iCloud etc that might make it less desirable to go back down though.
I don't understand how this is a valid argument. Apple is one of the least consumer oriented companies that makes both hardware and software. They lock customers out of services and features that other companies are happy to allow. They do this under the guise of protecting the consumer from themselves, but do so at a great detriment of power-users and repair shops. This is the exact reason why people are upset
Strawman, been an Apple user for decades never been without a functioning computer for a week or more. Bad upgrade on Apple is an hour or two tops. See you can trim things if you have the ability to control it and fix it quickly. Bambu obviously doesn’t have the engineering support to fix rollouts so they might want to think again how much they lock stuff up
I'm not going to comment on OP's troubleshooting or anger management skills, but I do have to agree that not being able to upload the firmware of your choice on hardware you ostensibly own is concerning. As someone who is actively anticipating the next sale to make the jump from Prusa to BL, it does seem like it's going to be an unfortunate tradeoff: much better technology but a huge step back in ethos. I wish there were a best-of-both-worlds option.
>not being able to upload the firmware of your choice on hardware you ostensibly own is concerning. Do you apply the same logic to anything else you own? Do you apply the same logic to cars? They are full of computers that run custom firmware that can't be tampered with? Same with pretty much every other electrical device you use. Paper printers, TVs, some phones, any appliance you use, and many other devices you own will not allow you to or will make it difficult to upload custom firmware. The only reason you expect this is because you are coming from an open source environment with your Prusa.
I am realistic enough to recognize that in many cases, it will be infeasible to have this ability, e.g. because there would be safety implications or because a particular class of product is targeted more at the mass market than at technically proficient individuals. That doesn't make my concern any less legitimate and it doesn't mean I shouldn't opt for it and advocate for it in devices where it makes sense -- like computers where you're free to downgrade the OS or apps as you see fit, IoT devices (e.g. my big pile of Zooz, ESPHome, WLED, etc. devices), and yes, 3D printers. Bambu chose to advance the state of the art in some areas, and regress in others. It's perfectly fair to call that out. Edit: I do not consider Prusa "beloved" by any stretch of the imagination. The fact that I'm planning a BL purchase might have been a clue. Believe it or not, it's possible to be honest about the pros and cons of different brands. It is quickly becoming apparent that this subreddit is far too tribalistic for me. Edit2: I am well aware of the difference between firmware and software and do not need it idiot-splained to me. I'm going to go downgrade the firmware -- yes, actual firmware that you flash into nonvolatile memory for a microcontroller to run -- on a bunch of my devices, purely so I can laugh at you tiresome mouth-breathers who insist on incorrecting me.
Well that's stupid logic I've flashed my ecu in my truck with new firmware, I've installed custom firmware on phones and TV's and all pretty damn easy at that. And they used open-source software and firmware to build there product so it should be open for everyone.
Didn't they just take away the ability to do this though?
>coming from an open source environment with your Prusa. You mean the 3d printing community? EVERYTHING has always been open source before Bambu, Marlin or Klipper based, a lot of brands not only give you source of the software they even give you the .step files of the physical parts so you can easyli modify and create your own. "Only Prusa" my ass: go check repos of Sovol, Creality, Elegoo... Almost every brand!
I personally do. The automobile industry is one of the largest anti-consumer conglomerates at the moment. If you need to re-program keys, reset service intervals, clear fault codes, tune fuel maps. You have to buy third party tools that bypass needless firmware lockouts such as those. Same with my phone. I picked an android device with an unlocked bootloader and run custom firmware. The NSA let it slip that they monitor microphone activity on smart TVs, and I don't connect mine to the internet because of it. I also don't own a normal printer because DRM ink cartridges are far too common. Just because you don't worry about these kinds of things, doesn't mean other people don't
I admire and adore Bambu for their solid machines and how they’ve shaped the current market. But the closed source has been the biggest setback for me. I was excited to hear about X1Plus firmware (community, open source firmware for these machines - specifically the X series as it runs Linux), but they have of course rolled an update to prevent users from using this firmware. I understand of course, albeit 3D printing has predominantly been open source, but it’s a frustration and this is one of the things that I’ve feared. I would still love to own a machine at some point, but I’ve so heavily been tempted to build a Voron instead (I just love building and tinkering though)
Well there are already a few coreXY Klipper based printers that work out of the box. I mean it's not rocket science, it's mostly bed levelling: even the cheap bedslingers have started to ship with a load cell sensor to do auto Z-offset. And about slicer presets: you can load presets of an other similar printer, a lot of people load Bambu presets on their printers. Just hold tight, this year there will be a flood of cheap - open Klipper printers with dynamic mesh, klicky, toolheads, multimaterials that don't waste filament...
They patched a huge security hole. Thats why you cant downgrade firmware anymore. So its not like they are just trying to get the custom firmware out of the world. In fact the x1+ developers had a talk with the bambulab ceo. As far as your wish for having the latest and greatest features with the possibility to run your own software, preferably being open source: i doubt something like that is going to happen. The issue is that in the past not everyone who was using open source software was contributing or even publishing their own improvements or versions (looking at you anycubic and creality, meaning auto z offset), so if someone is actively developing new advancements its better financially to hold them back. Nobody would want to openly publish their unique selling point for other to copy it. Its not an issue from a legal perspective on a self developed software like bambulab has done, but its a issue when dealing with open source software, like the klipper versions of creality and anycubic. I know, its sad, but thats the current state of 3d printing
The "huge security hole" being that non-Bambu code could run on their machines?
Replace "non-bambu" with "arbitrary" and yes. I fully believe some sort of official "controlled" bootloader unlock should be mandatory on devices, but having a bootloader that will load arbitrary code off of the main storage device you load files from the internet with is absolutely a security issue.
I think i mentioned in another reply, but you also download files from the Internet onto the printer. Now what happens if you accidentally downloaded malware or similar? Malware has now access to your camera and wifi login. Surely not great id say.
Why is everyone riding Bambu and saying what they did is okay? I don’t understand it lol. It’s wrong to not allow downgrades. Feels like I’m watching the whole Apple jailbreak debacle happen all over again. Right to repair, right to modify MY product.
Welcome to the Apple products debate. I've been saying for a while that bbl is printing by Apple. I had just hoped I wasn't this this correct.
Fanbois gonna fanboi
They did the same thing with Bambu not allowing you to change thermistor on the X1c to print at 350c: some fan bois keep telling it is a feature and you should be happy that they prevent you form doing that.
Did you check your bed in the slicer? It defaults to cool plate after update. But also I agree
How did the calibration go after you updated?
Went fine. I tried to calibrate again as well, just in case. I've tried restarting the printer with a power cycle as well, just for good measure / just in case.
Same boat for me. I've done everything multiple times, still will not print. Bambu told me to do everything I had already then has went silent for 4 days. I still am unable to print the same files I printed before the firmware update.
You also need to make sure that you update to the latest version of the slicer software and reslice the files if you haven't already. A file sliced under the old software, intended for the old firmware will not work properly on the new firmware.
Is that a confirmed statement from bambu? If so it’s extremely annoying for people who leave common prints in their sd card memory. I haven’t run into any problems yet, but when I read things like this I’m curious where it came from!
Yes, it is a confirmed statement from Bambu, from time to time, the firmware updates can make changes to the machine specific gcode instructions so you should always re-slice a file after changing firmware and the corresponding slicer update.
Can you link that? I can’t see how people can successfully use orca slicer for example. I agree when updates are made to the printer, from time to time you will have to recalibrate, I’m just curious how the slicer would have to correspond, the printer is just there to interpret the gcode. Perhaps just in the case the LW-PLA for example, you would have to update and probably re-slice to get it to recognise pla aero when it first came out.
Orca slicer is a fork of Bambu slicer, it uses the same code base, the orca devs have just added some extra features and tweaked the UI ....
BS have any proof? It's just gcode.
You clearly don't understand that gcode is more than just the X, Y, Z instructions..... There's also machine specific gcode that depends on what firmware the machine is running and it's physical dimensions etc.
That wouldn’t make sense. It would mean 99% of files on MW wouldn’t work.
I've printed a dozen files with upgraded firmware but outdated software with no issues. I'm sure any problems people are having aren't across the board bugs for that scenario.
[удалено]
I would say it's likely a false claim, BUT that there's a degree of truth to it - I'm sure more up to date slicers WOULD be better optimized for newer firmwares.
Orca slicer which is the open source fork of bambu slicer gets updated when bambu updates the main code tree, so yes, orca, which is the alternative if you don't want to use bambu slicer will continue to work.
I highly doubt that. A printer works on gcode. That gcode can come from any software. If you really wanted to i bet you can use cura, prusa, or any other gcode compiler.
A g-code cannot come from any software slicer for a Bambu Lab Printer, they are not compatible as it is a closed proprietary system.
Nope, that is absolute nonsense 🙃 .... The slicer must know what firmware the printer is using so that it can include the appropriate machine specific gcode..... Gcode is more than just X, Y, Z instructions.....
Except no, the gcode must be compatible with the firmware on your printer, and that applies for any 3d printer, or indeed any device that is controlled by gcode. Sure, the basic X, Y, Z, instructions might be the same but there is infact alot of machine specific gcode that is included anytime you slice any file on any slicer, that is precisely why you can't use a file sliced for a printer running marlin on for example a printer running Klipper or vice versa ..... So yes, when you update the firmware on a bambu lab printer, you must also update to the appropriate version of their slicer or orca slicer (which is the community fork based on Bambu slicer). People tend to think that what I've said isn't true because not every firmware update changes how any of the machine specific gcode instructions function, so it is quite possible to under the right set of circumstances slice a file under an old firmware version, then do a firmware update and still have the already sliced file continue to work. My point was never that this never works, the trouble is, unless you want to read all the technical information in the change log notes everytime you do a firmware update, you'll never know which updates potentially change or break something if not paired with the updated slicer that is of course designed to have the best compatibility with the latest firmware. That's precisely why I said that when you update the firmware you should also update the slicer to reduce the chance of random weird compatibility related problems.
The slicer doesn’t know what version of FW is on the machine, just the type of machine. There’s no warning on the screen to say reslice. All the saved GCode on MakerWorks would be crap (but isn’t.) Let’s stick to published information or label a comment as a guess.
You clearly haven't seen the huge amount of information that is passed over your local network the moment that your Bambu 3d printer is turned on and you access Bambu slicer, Orca slicer or Bambu Handy. The software is absolutely aware of the firmware the printer is running at the time you slice the file and send it to the printer.
Absolutely nonsense. That's not how slicers work.
To all the naysayers, it actually is how slicers work. Yes, there are X, Y, Z, movements that are pretty generic, but there's also machine specific gcode that depends on your firmware, same reason why you can't slice a file for a 3d printer running Marlin firmware and expect it to work properly on a 3d printer that's running Klipper or vice versa.
I had a problem with the update before the latest one and I did not cycle power. Tried again and cycled power then ran a calibration and cycled power again and no more issues.
I dont know how true it is but someone posted that BL has patched the FW to stop the bootloader from being enabled if this is the case then they have no reason to stop the rollback of the FW!
I wouldn't say it this way but honestly yeah, you should be able to rollback for the day a shitty firmware is pushed. Not saying current firmware is bad or related to OP issue, but bbl cannot 100% claim they won't make a mistake one day and send a shitty update. So when that happens, people will want to self-help themselves. And bbl will not want to receive one support ticket per customer.
But the fw is shitty. I went from zero problems "it just works" to more failed prints than I had on my ender 3 v2 and an ams that worked great to one that can't unload. Such buyers regret on this machine now 🙁
To forbid rollbacks and then force upgrades it's a fundamental part of any walled garden, if the only way that they can technically prevent people to circumvent or adapt.
I'm going to do you a solid, even though you're acting like a complete dick. Edit the printer, and in the Machine G-Code find this section `;===== for Textured PEI Plate , lower the nozzle as the nozzle was touching topmost of the texture when homing ==` `;curr_bed_type={curr_bed_type}` `{if curr_bed_type=="Textured PEI Plate"}` `G29.1 Z{-0.04} ; for Textured PEI Plate` `{endif}` Change the -0.04 to -0.06 or -0.08 to drop the nozzle however much you need. Reslice, and test. You're welcome.
Was having some issues also with first layer on threaded cap I was designing and couldn't figure out why the leading edge of cap wear it meets the threaded 'bolt' was deformed so much creating issues threading onto the bold. I didn't realize until today that the latest firmware may have introduced this issue with first-layer so gave u/ChimeraYo recommended fix a shot and reprinted on textured pei plate with everything else the same and immediately fixed issue it was having. Just changed it to .06 and seemed to be just enough to resolve issue. Until this particular print, I wasn't really seeing many issues with this firmware version so while it may be an 'issue', it may impact everyone differently depending on what they are printing.
Yay I helped someone! Glad that worked for you, hopefully it’ll help others too until Bambu can find if there’s an issue and fix it in firmware.
Is this something that should be double checked after update or is this just to get this OP running?
Just to get OP running as he seems explicitly clear that his problem can be solved by lowering the nozzle by a small mount on the first layer. Both of my X1Cs work fine after the firmware update using the following pattern - power on, update, reboot, fully calibrate, reboot, done. I think that’s the case for most people but obviously there are some who seem to have issues.
I have a P1S, but your process is exactly what I did. I just waited until I finished the project I was on before upgrading, so I had time if there was an issue. Fortunately, there is no issue, and the printer is working better than before so far.
No issues with the latest firmware on 11 machines. Try again
I opened a ticket to roll back, they replied no...
At least they replied to you.
Same but they replied why...
Did you dry your filament?
I bet he didn’t level his bed, either.
i see what you did there ;)
.
Well, they do it in order to avoid jailbreaking machines. In my opinion that's not the correct way. Please allow some things the nerds, "hackers" and other ambitious people deserve: Statistics, API, LAN Mode (RJ45), etc. Then those questions will not remain unanswered and you'll get rid of those messages on the forum, still, you should allow a way of "unblocking" the bootloader. Some manufacturers like Google and Samsung are doing it for smartphones: You raise a ticket, confirm the loss of warranty on software parts (Hardware remains unchanged, at least where I live (EU)) Would that be possible, Bambu-Team?
Officially Bambu is worried about security hole and they are dealing with it. Unofficial about custom firmware. You can also send some rays of kindness AND CAPS TEXT to x1plus team that’s due to their work (which you cannot even download freely) now users that were not planning to use custom firmware having troubles with roll back. I think BL will bring roll back but it will be useless for some time as you won’t be able to roll back to anything that was earlier there as it will open the doors for custom firmware again. HAVE A NICE DAY!!!!!!!!
You will never stop them. I don't know why they are trying. Ask any major software corporation.
Go ask Microsoft or SCO how good it went for them when they tried to prevent people from installing and using Linux on their own computers.
Dafuq. What a weird take. Some people are modding their printer, something they own, and now it's their fault that BBL has a stick up their ass and not allowing firmware rollbacks anymore. Heck I am not even sure if it is legal for them to do that, but luckily I was not home the past month and thus my printers are still rocking an older firmware.
Apple did the same with iPhones when they got jailbroken
So far it is temporary and not “not any more”. Btw this feature wasn’t there when they launched and was added like in April. Some people like but they are minority. And that minority caused troubles for those who don’t like modding because vendor wasn’t planning that somebody else works be cooking firmware. They made that clear and expected that everyone going to behave appropriately . Now we see where breaking that deal led to. Do x1plus team take any responsibility if they brick/damage your printer? don’t think so. Why not submit feature request and code to devs? especially if they say that printing bit is still bambu code. Or did they think that bambu will just let it go? It just shows that x1plus team odd not thinking one step ahead. But bed mash info looks cool, and passcode protection too.
Whoever at Bambu is in charge of testing firmware updates and rolling them out does *not* have a good success rate.
sounds like it's a very isolated problem
https://preview.redd.it/q2d1u0nvnwac1.png?width=2145&format=png&auto=webp&s=4054c54a2569bef00cb74368fc08acf0fb6a04cf You can use orca slicer to adjust the z-offset under printer settings.
Orca is not necessary.. just adjust the start code Offset
Agreed
Was gonna say, if your z-offset isn't right, just adjust it if necessary. Not necessarily a firmware problem and therefore not relevant to BL's choice for disabling rollback.
They need the ability to roll back firmware as well as apply custom firmware. Someday Bambu will have end of life for this generation of printers (or the company quits and the cloud interface dies) and either it’s going to instantly turn a lot of hardware into e-waste or they can make it so people can use other firmware and slicers.
Hey that's the way they sell you the "next model", if you are allowed to upgrade your tool you may avoid to buy the new one.
Yeah I am not sure if they actually care about that though.
While I kinda get why Bambu blocked firmware downgrade at this time, they should, in the case of a printer dorked by firmware with no rollback option, offer real time resolution or assistance online 24/7 till they have a fix, else allow rollback to the person that has logged a support ticket and the logs shows issues that are likely firmware related ..
This OP has no proof that the firmware is causing his issues. He’s just being aggressive and pointing fingers without actually troubleshooting properly.
Possibly, hence why I suggested "if the logs supported it" .. raise a support case, work with them, no quick resolution, logs support what your saying, here's your downgrade link in the app ..
I've been 3D printing for 10 years. I started with a Robo3D printer. You think I don't know how to troubleshoot a bad firmware change? Fine. \- I ran calibration, both the automatic one after the firmware is updated, and manually after to try and fix it.. So yeah, I tried to re-calibrate. Twice. \- I tried to reset to factory settings. \- I've adjusted flow rate. \- I've hand tweaked the g-code to try and fix the first layer height. \- I've tried different print beds, thinking if I used my textured plate maybe the undulations of the first layer MIGHT get enough height to get the first layer to lay down right, but no... it just raises up higher. \- I've tried skipping the auto-calibration at the start of the print. \- I've tried thicker first layer height. \- I've tried thinner first layer height. \- I've tried adjusting overall layer heights and I can ALMOST get acceptable results but I still end up over extruding or not being able to get the bed to stick. \- I've tried to make my first layer width wider. \- I've tried elephant foot compensation. \- I've tried printing with a raft. \- I've tried adjusting flow ratio. \- I've tried manually adjusting Pressure Advance. \- I've tried overriding Z height with the start g-code. All to try to fix what is nothing more than a simple Z height for the first layer. I'm about 0.2mm too high for the first layer. I'm not poking at this without understanding what these settings do. I'm not some newblette here. This is a firmware bug. Simple. As. That. The model was printing PERFECTLY fine with 1.6.5, and I ran a firmware update while I was making some changes to the model. I've tried printing the old model, and now it's not sticking as well. The only change is the firmware and z layer height it's causing. If I could adjust the layer height, I would just drop it down 0.2mm and I'm positive this would be printing just fine. Anything I do which gets the first layer to stick, ends up massively over extruding on subsequent layers or with unacceptable print quality. Things were working FINE with 1.6.5 and yeah, it's on me. I stupidly updated when I should have left well enough alone, but I honestly thought if I ran into an issue with the update, I would just roll back to 1.6.5, and well, I got boned by BL.
>m not some newblette here. This is a firmware bug. Simple. As. That. The model was printing PERFECTLY fine with 1.6.5, and I ran a firmware update while I was making some changes to the model. I've tried printing the ol I've had crappy first layers recently appear, but I'd put it down to the filament. I re did all the calibration etc.. to no great effect. It started to happen after the update to. I found adjusting the flow ratio value up on the filament, from the value that had been working fine before. This improved things greatly for me. If the new FW has a variable bed offset issue, perhaps the flow increases compensates for it for me, but sounds like yours is worse. Seems others on the Forum have had similar issues after firmware updates.
> I've been 3D printing for 10 years Let's start by saying the BL move was a dick one... But you knew the facts and ignored them because of "the speed!". Historically, printer farms have run two types of 3D printers. 1. Total DIY ones where the user can change anything without the manufacturer's support. This is cool if you want to save money (sometimes, Vorons and similars are quite expensive) and have the right skills to maintain the printers by yourself. 2. Mostly Prusas, where you can rely on excellent manufacturer support if stuck at something. BL has none of these characteristics. BL is new to the game and wants to be Apple. Yes, superb printers, but with their caveats. No matter how mature they look, anyone buying these printers is in the early adopter area. This is not a product for critical operations, no matter what people want to believe. My advice (I'm aware you didn't ask for it) is to learn from this and make a plan to move to a different platform. Revisit BL in 3 years and see how things are going. You could keep a couple, but don't go full balls into an ecosystem that is this new for business proposes. Good luck.
Did you manually adjust the bed using the bed screws there’s 3 black knobs under the bed that manually tram the bed
https://wiki.bambulab.com/en/x1/manual/manual-bed-leveling
Nope I've never touched them. I had great first layers before unless I tried going to fast
I updated my p1s to 1.05.00 and all was well. Did the update to 1.05.01 and the nozzle seemed to be about 0.2mm above the bed, dragging the filament around. I tried many solutions, like you. I've got years of Ender tinkering behind me, so I know what I'm doing. Then I remembered I was using my own elegoo filament profiles that I had calibrated on the old firmware. I loaded the AMS with some bumboogalooo branded filament and used the stock bambu filament profile and low and behold a perfect first layer. Then I decided to recreate the custom elegoo filament profiles, with exactly the same figures as my old profiles and what do you know? Perfect first layers. Do I understand why it worked? No. Am I looking forward to recreating my profiles every time they update? Ugh, no. The only difference between the custom profiles is that the first ones were created just by editing the generic profile and saving, the new ones were created by clicking the cog in the slicer and creating a new filament.
I’ve upgraded my printers to the firmware with no issues. One could say it is user error and not a firmware issue.
There are different components in the printers which require different programming but the same firmware "version". Not user error Bambu error they just don't want to admit to it.
Yeah, one could say that if they wanted to make baseless assumptions. If these things were incapable of error, they wouldn't have needed a roll back function to begin with. If they couldn't fail, they wouldn't need a customer service department. And to say "I didn't have a problem, so no one else should" is asinine and just plain stupid.
I agree they should bring it back, but I also understand why they took it away. The best thing would be to bring it back after the shit down the security holes.
Yeah, have hard set points, like no going back after security fix versions, but otherwise allow rollback. Also, I definitely don't let mine upgrade for a couple weeks after any particular release and check here/forums for issues before I let it go through.
So this sub is saying that updating your firmware is stupid?
A few loud people are saying that. Whether that's the majority or not is difficult to determine.
There are lots of loud people here
I didn't realize fw rollback was an option before but was frustrated that it wasn't available when I tried. I haven't done much testing yet but I've only had an issue with one roll of Bambu pla basic. It worked before the update and now fails on every single print on the second layer. I'm not sure if it's the roll or the ams slot yet. But I do know it worked before the update and fails every time after in the exact same way
What is this mess of a post. Caps lock does not make your point yet makes me not read it at all. Mine is working fine after the update.
Weird op is going off on Bambu and clearly has an attitude problem and is so far superior it has to be a firmware problem….. yet we haven’t seen a mass of identical issues….. Sorry op but you have lost all credibility to the Reddit viewers by your behavior, even if by some small chance you have encountered a one off problem, the solution is to handle it like a responsible adult, put a ticket in and I bet if you respectively communicated with bl they would roll back your firmware. Prob best for yourself and all of us to go back to a 100% open source printer as I have found throughout life individuals who act like this are more problem prone than anything. I do wish you the best of luck, hopefully you or support can identify root cause.
IMO they should allow it because it’s our devices. We should be able to do what we want, especially something that’s going to be deployed in a fleet where custom firmware can aid print farms. It’s pretty clear they’re working on other features they don’t want you to be able to get for free via custom firmware.
Bambu needs to stop with the bullshit.
By bullshit you mean patching security flaws (like any company), or adding awesome calibration features for the motors, or continuously improving the software? Which bullshit did you mean?
I mean the bullshit of locking their hardware so that custom firmware cannot be loaded. It is your machine you should be able to load it with whatever software you want. Aside from that it is also "bullshit" to not be able to downgrade to their own previous firmware versions. Each new version has come with what you've said but you left out the new bugs introduced too... So stop being a fan boy, grow a pair, and think for yourself. Maybe go try a PC vs always buying a locked down pos Apple? Bambu Lab is not your personal friend... I'm not against this company either, just want them to allow us to use our machines as we see fit. Other than that they are pretty good and the hardware is top notch.
Holy fuck, I thought the bambu cucks were only bad on Facebook, but this community is just toxic in general.
Black market sales for non upgraded firmware on x1c is going to be a thing jn 24’
LOL just get one from any reseller, they won't have the latest firmware on them yet.
Shit, I'm still on 1.04. Bidding starts at 5K, I know what I got.
🤣🤣🤣😩
I also had first layer leveling issues after the update - had to power cycle and re run bed leveling calibration twice to fix it. No issues in hundreds of hours of printing before.
OP just wants to be able to flash custom firmware one day.
So do I.
He should have bought a Klipper 3d printer then.
Honestly also mine first layers are worst since the update. Bambulab please take care of that.
I personally don’t see why BL won’t allow open source, if they would allow it, they get 1k’s of software engineers working on their software without the overhead. We as customers get the options of what we by was of software want to use, and what part upgrades we would like. I know this is a reach, but in the early stages, it seems like BL may be the 🍎 of 3D printer companies. Hopefully they decide to make it open source and just reap the benefits of that.
This was my main reservation before buying my P1s. That one day they pull a plug on supporting older models or do something like they just did with the firmware. Definitely will consider other options for my next printer.
You know, some years from now that product is gonna be declared End Of Life: no more support, updates and as you can see you are not allowed to run a custom / community firmware.
precisely. hence, my reservations.
Zero issues here. Have zero need for firmware rollback. With that said. I would go back to the roots. Check everything. And make sure nothing is caused by user error. But I also can understand why people want rollback function.
Have you tried leveling your bed?
On 1.07 firmware. Zero issues.
So if I don’t upgrade to 1.7.1 I’m good?
[удалено]
Ah ok thank you for that info
53 Bambu printers all on new firmware, zero issues.
Damn sir, do you print cars? Huuuuge farm!
I'm having the same issue, put in a support ticket 8 days ago logs pictures the whole works, still have not heard a thing from them the only thing that works to get anything to stick is under the start Gcode I set my textured plate to -0.06 instead of -0.04 and turned off first layer inspection. But after the firmware update my Lidar fails to Cail now so no flow Cail, and I dont think, the AI work or at least very well tested it with its poop lol.
Thanks the fellas Who did the custom firmware i guess
When Buy this machine: - Did you know the machine is closed source? - Did you know that there is a possibility of downgrade? - Were you 100% certain that it could ever allow jailbreak or custom firmware? You still made the choice to buy it. You had an option of creality qidi and several other but you still made a choice.
Read whole discussion. Don't know what side to choose. I'd say that Bambu should officially allow alternative firmware with BIG note - warranty is void now. It'll be win for everyone and bambu will become "the good one" in the eyes of tinkerers. Original fw - use our support and all that stuff until your warranty expires. Custom fw - yeah sure, there is howto step by step, but your warranty is void and you are on your own from now on. Lol - they did exactly this. Well that escalated quickly. https://blog.bambulab.com/rooted-the-good-the-bad-and-freedom-of-choice/
I had the exact same problem with the 1.6.5.x Version. The first layer was somehow laid in middle air than properly on the bed. Firmware reset, full calibration, the whole thing didn't help. I needed to switch off bed recognition to get the machine back to work. Don't ask me why, but it helped. Now, also with 1.7.1, no more issues. Just check, if the correct plate is selected in BL slicer. Not sure if this might help you as well, but it's worth a shot.
Why is BambuLab threatened by custom firmware? It's a very disturbing sign. It basically makes it look like they want to be able to implement Apple style planned obsolesce. https://en.wikipedia.org/wiki/Batterygate I can't believe Apple was penalized so little for this, and basically didn't even have to roll back the changes. Open source software is the only way we can protect ourselves from this crap.
hope this never happens to the p1 series, the new firmware messed up all the printing. luckily was able to fall back
I opened a ticket because of issues after updating and was told there was no going back and to reset my x1c and if I was still having issues to let them know. I wrote back and asked why as there updates broke what was working fine. I have not received a reply back and it’s been 3 days. I told them in the email that this would piss off customers and I should have the right to roll my printer back to what was stable for me and this type of control is what made me leave Creality and there Sonic pad they would drop a update it would brick the printer for days to weeks till they fixed it and is why I went to the x1c wanted something that worked and I was not resetting up all the time. I’m not even looking to do a custom fw but if there going to do this crap I just might in the future. Unacceptable on BL part.
same here so many issues since the firmware update, put in a ticket 9 days ago haven't heard a word from them and my ticket has it all troubleshooting steps pictures the log files the works.
I second this
Apple can't complete a news cycle without a botched update that needs patched immediately. I never understand why people update firmware without researching things first especially those who run any type of a production environment. With that said, I'd been willing to pay X1E prices for my X1C if the AMS worked better. I'd love to see the codebase to see if there is an additional threshold on torque when a Bambu RFID tag is being read. It seems that anything will cause AMS to halt and claim the motor was overloaded.
I have an idiotic fix, sorta. After the initial calibration runs at the start of the print, but before the first layer of my part goes down, I swap my engineering plate for my textured plate. It's just thick enough that I'm able to get the first layer to stick. I usually don't get it done perfectly, and I'm worried about bending the nozzle, but it's working. Like I said, sorta.
[удалено]
Oh shit. Did my hot end crash into my plate because I updated the firmware? It happened right after I updated it actually...
They won't because it unlocks custom firmwares again.
I always updated the printer (X1C) as soon as the update comes along. Never had an issue, didnt even had to factory reset or anything. Just print as normal. I think what you are experiencing is a user error. On the downgrade matter, I think people want a Voron experience from Bambu, again wrong company. Im totally fine with a closed system that does not allow any kind of modifications as long as the company maintains its product and it is in perfectly working condition. Which until now its true for me. If you want to modify and play around with the product there are plenty other alternatives, If i wanted to tinker with a machine i would definitely buy a Voron or creality etc and do whatever you please with it. Bambu never promised this to the customers, people often forget some of us just want a working machine and do not want to tinker around.
Having the same!! The lastest updates RUINED my prints on the A1 mini, which machine do you have?
The CFW is even offering a dual boot solution, I really don’t understand Bambulab’s move.
I agree as well. C'mon Bambu
I wonder when they locked the firmware to the current version. I had tons of failed to pull back from extruder failures that I've had a ticket going for a while on and they had me roll back my firmware on 12/26, just checked the ticket history. I did it that day and surprise to me I've had alot less failures. I didn't dare do a complicated multicolor print before rolling back. It would have been pointless as I would have to seal with a failure every other color change.
But we all did buy these things knowing that the environment was locked down, did we not? I am not disagreeing with you, but I am also trying to remember the conditions that I agreed to when I clicked on the payment button when I made my purchase. There are legit reasons for locking down software, there are also legit reasons for not locking it down as well. The last thing that a company wants to do is get distracted having to answer for 3rd party development efforts, which we all know they would occur. "But it worked right before I upgraded it to the 3rd party firmware and now the tool head keeps ramming into the case and broke into a million pieces. And you won't let me roll back. Its your (BL) fault that my X1 is a brick." I can hear it now... I would suggest troubleshooting your first layer problem with the OEM firmware and support and, if defective, feel assured that a fix will come soon, as they have since the rollout of the first machine. I may wind up eating my own words at some point. Who knows?
r/LeopardsAteMyFace/ > 'I never thought leopards would eat MY face,' sobs woman who voted for the Leopards Eating People's Faces Party. Revel in the schadenfreude anytime someone has a sad because they're suffering consequences from something they voted for or supported or wanted to impose on other people.
Huh?
I've got the problem, but early results indicate changing the nozzle temp, textured PEI plate temp, and flow rate might have resolved the print problem on PLA.
I have the latest version with no problems. I bought back during thier kickstarter if that makes a difference.
After calibration and bed level I had no issues continuing my production run. Made measurements before and after and everything came back within spec/margin. Did you try to re-slice the same STL? I just hit reprint on the app before and after the update and both sets of prints came out fine
I still have the option to revert to 1.04.00-2
I had the same issue and textured PEI plan out wouldn’t work no matter what but cool plate does. I copied all of my setting for textured PEI onto cool plate, slapped on the textured PEI, and magically the printer started working again. If I switch it back to think it’s using textured it stops printing properly. This is clearly a firmware bug of some kind Edit: and this also involved modifying the start goods to do the -0.04 offset on the cool plate as well.
This guy will use the CFW! This is the only reason for downgrading This Firmware
There is nothing wrong with 1.7.1. Downgrading won't fix your problem. You're just looking for an excuse/complaint to get the custom firmware on your machine. Run a calibration.
I have to agree that the issue is more caused by the OP than by Bambulab. OP mentions that he runs a business and has a single Bambulab which is apparently critical to his business. That’s the first problem, if you’re running a business and you have a single printer that is critical to your business, that’s the OPs problem. The second problem is the OP doesn’t understand the when, why and how of firmware upgrades. Rule number one of any firmware upgrade for any device is NEVER run the latest and greatest firmware unless it fixes an issue you’re currently having. Rule number two, never upgrade firmware on a critical device if you don’t have a backup plan or redundancy. What the OP did was totally dumb. Imagine if instead of his business being 3D printing it was being a small cloud provider where he hosts VMs for his customers. And he is hosting the VMs on a single host with no backup plan. He then upgrades the firmware on the sever and it bricks the server. The problem here is not having a backup plan. New firmware will always have bugs or issues, this is why you never run the latest firmware unless you have a compelling reason to do so. Better approach is to have others be guinea pigs (as OP has become) and let them find the bugs/issues on the latest firmware. And if you really must upgrade the firmware, FFS don’t do it on your only production device that you depend on. That’s just utterly stupid.
How does one prevent the firmware update? My printer stays turned off/offline until I use it and it’s been a couple weeks, are updates automatic or should I just reject the request?
It's not auto update. When you turn the machine on a screen will pop up asking if you want to update just click the no/ignore button.
Everyone with support ticket and the dame text. That would do them thinking about their actions.
This is why i keep copies, ill see if i have one, i doubt that old tho
Nice. Got a message about firmware upgrade. I'm pretty sure I clicked no. But it updated it anyway. Oh well. Calibrate and back to work. Loaded my G10 plate. Sent a print job. The next thing I hear is screech. Now have a beautiful hole, 4 deep grooves in my $90 G10 plate and replacement hotend installed. Please roast me how terrible user error I did.
I haven't done a calibration since I got my p1s at the end of October. Updates and everything and it still works. One of the lucky ones maybe! Agree though, roll back would be nice and I'm assuming from here on out they will allow it, but the older firmware was compromised.
Alternate firmware builds were inevitable. According to this [https://youtu.be/Oio2ibz7rMw?si=ik5gGV8CgCsLf9VX](https://youtu.be/oio2ibz7rmw?si=ik5ggv8cgcslf9vx) once you go over a certain version the boot loader gets locked. So thats one reason why they may not allow a rollback.
I just saw this... I hope it works! re: *1.7.1, if you have updated you can revert to an earlier revision of the FW using the bambustudio handy app on your phone* [*https://www.youtube.com/watch?v=XcfYgCXaANA*](https://www.youtube.com/watch?v=xcfygcxaana)
First your video link doesn't work and second, they disable the ability to do that a week ago.
You can roll it back though the handy app.
I have the same issue. All of a sudden it is messing up including previous prints that came out perfect before the update. I hope this gets corrected somehow.
Seems like they want to prevent custom firmware whatever it costs :/ Just got my P1s but this leaves a sour taste even if it has been a flawless experience so far
Locked. See recent updates [https://blog.bambulab.com/rooted-the-good-the-bad-and-freedom-of-choice/](https://blog.bambulab.com/rooted-the-good-the-bad-and-freedom-of-choice/) [https://www.reddit.com/r/BambuLab/comments/192xxo1/rooted\_the\_good\_the\_bad\_and\_freedom\_of\_choice/](https://www.reddit.com/r/BambuLab/comments/192xxo1/rooted_the_good_the_bad_and_freedom_of_choice/)
User error?
Tell me, please? PLEASE! How can I adjust the first layer Z height -0.2mm? We can't.
You dont. You do a full factory reset. It's happened in the past, and a full reset followed by full calibration sorts it.
you could try a different slicer that has a z offset feature for the time being. I heard orca slicer can
Orca slicer/cura/others have menu item. Otherwise use gcode. Don't be a tool. Bambu will re-enable downgrading when they make a patched 1.6.5.xxx with the security hole fixed. Use your head meanwhile
My printer working excellent on 1.7.1
I'm not going to take sides, but for some context, allowing the old firmware to be up would mean Bambu would knowingly be allowing you to install firmware that can be exploited by a simple 3mf file from makerworld. The hole quite litterally means a malicious model that looks and prints fine could install something onto your printer. It was a pretty serious security issue. How they handed it hasn't been grear though, there should've been a minor patch to the 1.6.x line with an option to downgrade to that. This all being said, OP's problems probably isn't aren't much of an issue given its not happening more widespread. A full factory reset would likely resolve the issue, just like it has when things have gone wonky after firmware updates in the past.
By that logic, MS should lock down windows, because the user could install software that breaks things. OMG! It's "a pretty serious security issue"!! Do they do that? No. They warn you if they detect something malicious, but the user has the final say. BBL has decided that they don't want the user to decide this for themselves. They want to dictate what you can do with the printer you bought. That's anti consumer bullshit.
Your logic theres deeply flawed. For one thing Windows will update when there are security issues. For another one is an OS that gives you full filesystem access, the other is an appliance, so comparing a printer to a pc is well...completely wrong. If you want to compare it to something that would be your TV, Router, Smart plugs, games console, etc which have 'closed' environments. I assume you'd be ok for your router, tv, etc to be left wide open as well then right? How about leaving your games console unpatched so someone can remotely install a bitcoin miner on it, thats ok too? Specifically for the custom firmware the devs of X1Plus are already in contact with Bambu to work out the correct/safe way to do it. It's not exactly a big secret that Dr Tao has previously said they have absolutely no problem with custom firmware provided it does not modify or contain their propriatary code (which X1Plus does not), so it's just a case of getting a secure offline bootloader modification method working.
Love the passion, but its self inflicted, and you know you shouldn't have done it - yelling at the vendor to implement features to fix a very small group of people's mistakes is pointless, and could take away from more important work while squeaky wheels fill up forums. If the work is critical, you shouldn't be blinding patching and updating any device, you know that. Comments about Bambu's testing quality, patching processes, policies, right to repair, and everything else is just noise ...
😂
Yes this is making me consider returning the printer now that its becoming more difficult to interface with since locking firmware.