WTF? This is NOT acceptable. No wonder I was having issues when using a 0.6mm nozzle. It acted like it was auto calibrating, but apparently it wasn’t. Why the heck didn’t it throw an error code? What kind of sloppy programming is this? I’ve probably lost countless hours of frustration as a result of this and–who knows?–maybe other similar things. It’s June 1, 2024. Why the heck hasn’t the work been completed by now so that it works on all on the nozzles ? Are they ever going to finish what they started? If BBL either can’t do the work, or is unwilling to, you can bet some other company or open source effort will, and that will be the company or software that gains customer loyalty and endures over the long-haul. It’s long past time for BBL to finish the work it promoted and sold us on. I’m pissed.
And the wiki itself is obviously dated too. It should be kept in sync with the latest releases. In general I like the way it’s written, but this is their core business. They should be delivering on the promises they’ve already made before venturing off onto tangents no one even asked for.
I’ve defaulted to doing my filaments manually, and currently starting again from scratch. It is a shame but hoping it really is a work in progress for them, I certainly would love the day when at minimum a semi-automated calibration cataloguing system is reliable. Put a Bambu Spool in and it’ll do the calibration via two steps and then saves the lot in the printer (localised in studio as well) with no human intervention other than cleaning the plate between calibration (or after if it could handle both sessions).
I find the current set up so clunky that I gave up on Bambu filament as the tags are not convenient, even when it does work smoothly. So its old-school calibrations and excel sheets for the meantime.
This has been part of my contention with Bambu. Consider the manpower expended on Makerworld that could have been reinvested in making other parts of their product whole or expanded. You’ve stumbled on one aspect but I can note others. As an example. Fixing their LAN-only mode or fixing the never-ending crashes of BambuSource.DLL. They should focus more on code stability in my view.
They would also be wise to invest in engineering upgrades for existing platforms. As an example, they could make a tidy little profit by designing Nozzle retrofit kits that allow for the use of the A1 interchangeable nozzles. Or making an upgrade kit to bring greater functionality to the P1 and X1 platforms such as providing a controller board kit from the X1E and offering Ethernet. There are so many holes and areas where they could better spend their resources.
What Bambu does not realize is that when all of their competitors catch up, the distinction between printer platforms will be minimal. One only has to look at tech products such as cell phones, desktop office printers, and even laptops. All of these technologies had their eras where there were huge opportunities for companies to distinguish themselves through innovation. However, every tech eventually reaches a plateau. At that point, long-term customers who have product loyalty will make the difference. Bambu is doing many things to alienate their established customer base and is telegraphing that they just don’t care about past customers. They want to know: Who is going to buy from us next? And it shows.
Presumably, they are looking to cash out at some point based on these tactics, and this is just a short-term play for bigger money through acquisition.
OTA version 01.06.00.00 (20230801) was only current for three days before it was replaced by 01.06.01.00.
I thought 01.06.00.00 might still have some use to boot into X1+ (which then loads 1.07 or newer) but even the necessary “R” firmware is going to be 01.06.06.55 to 01.06.99.99.
I may have gone off half-cocked without all the facts fully lined up regarding this. Apologies if that’s the case. That said, I still think 2 years is ample time to fully wrap things up.
