How do you go back to your initial installation settings/configuration files, registry or whatever if you put in some settings that were incorrect?
I tried the deinstall–>reinstall route first but had low expectations of that working because applications don’t delete your configuration files any more. They’ll delete the program but when you reinstall, all of those setting just snapped back up.
Thats’s pretty typical of applications these days but the stuff that is left behind is what needs to be edited.
I want to run the initial setup over or get access to the file so that I can edit manually
The initial settings are the System presets. If you have saved any changes to those from within Studio you had to change the name, and then they became User Presets.
Unwanted User presets are deleted by clicking the “X” between the save and search icons.
System presets can be found in the configuration folder (Help>Show Configuration folder) and edited with a text editor, but that is pointless. They will be replaced with the next Studio upgrade. Make your changes to a User preset.
What I want to understand is why, when I have a P1S and initially set up the machine as a P1S why all the options in that dropdown below the Global/Objects toggle are all
something something @ BBL X1C
I read that as BamBu Lab @X-1Carbon, which I do not have.
yeah basically same settings from what i have found, it would be nice though to differentiate the machine with its individual name visually but not really necessary mechanically. I was confused at first as well
In my instance of Bambu Studio, if you go to the Prepare tab, top left it identifies my printer as “Wayne’s P1S Bambu” which how I named it earlier.
Unfortunately as the software that runs these Bambu printers is semi-proprietary, you can’t really look at how the software is written.
But the reason I ask the question isn’t just because I think the field should should say P1S and not A1C.
I’m asking because I took delivery of my P1S on July 22nd and submitted the support ticket on July 28th with what IMO is a software glitch or bug. It sat in the box some portion of that week before I put it together, and I did not write the ticket immediately because I did a little troubleshooting before I created the ticket. So, while I did print a couple of very small simple items that people on YouTube said I would need for the printer, it was for all intents, Dead on Arrival.
That bug manifests itself in a false error that tells me my front toolhead cover has fallen off. I bet I have seen that fault dozens of times and not once has the cover been even ajar. But, that fault always occurs at the same step and location in a print. It’s repeatable. That’s software.
There are differences between A Series and P Series printers else you me and everyone else would just buy the cheapest printer.
By not saying P1S in that dropdown it just muddies the water, IF it is just a typo. If it is actually A1C code in there, that’s a problem.
Support has been very helpful and have send me lots of parts to swap out but if it’s a software problem, board and cable replacement is not going to fix the problem because the problem is in some non-volatile memory chip that we have not yet replaced.
You are confusing the Printer selection with the Process selections.
Make the Printer selection from a System preset for your printer/nozzle type, or a User preset based on the matching System preset.
With the correct Printer selected, you will only see the Process selections that are appropriate for that Printer. As far as Process settings are concerned, the X1C, X1E and P1S are equivalent. The X1C came first so those are the System Process settings offered to X1E and P1S users. There are no process presets specifically for the X1E or P1S.
If you have selected a P1S printer, you will not see an A1 Process in the dropdown.
If you are seeing an A1 as the Printer selection, you’ve selected the wrong printer or have loaded a .3mf project file intended for a different printer. That’s up to you to verify and correct.
I’ve looked at the github already. Some of the files you can not read with VS Code. Tha’t the proprietary stuff.
While it may not be unusual to see X1C there doesn’t make it right. What it says is they are using the same configuration on both series of machine and that is a recipe for disaster.
The whole purpose of Github is to provide segregation of software so you don’t accidentally ship mismatched software.
Even if the software is the same, they should run two separate repositories one for the P-Series with text that reflects P-Series and another where A-Series is reflected. Or combine the two and use a naming scheme that reflects the commonality.
The printer selected is a P1S
If you are going to try and convince me that even though P1S is selected as the printer, but then all the system presets having @ BBL X1C hung off the end is , you won’t.
Unless you think you have unique software, it’s not the software. The toolhead cover error is repeatable on your printer, not the thousands of other printers using the same software. The slicer software did not ship with the printer.
It’s the software on MY printer.
Also, FWIW I think Bambu agrees with me rather than you, since I just got an email saying my printer was a DOA (their terminology) and they are going to swap me out for another printer.
It’s all software
I spent virtually my whole adult working life working with digital control systems from Allen Bradley and Emerson and I know a software problem when I see it.
Software vs Firmware is semantics
These are toys comparatively as far as complexity of the troubleshooting and determination of the problem but the support folks have to follow their process. I knew we were here 2 weeks ago .
We wasted most of this thread because you asked about installation, uninstallation, configuration files and registry entries, “@ BBL X1C” - all related to software on your computer, all related to Studio.
If we had known you wanted to reset the “software” on the printer, it would be a simple matter to direct you to your P1P screen to select Settings>General>Restore factory settings. But I would have expected Bambu support to have suggested that already, or to provided instructions to replace the “software”.
If Bambu did not think there was a hardware problem they would not be going to the expense of replacing the entire printer.
Let it go. You get a gold star for persistence.
I reset the printer back to default not once, not twice, but 3 times. The fault persisted across all those resets. Resetting it to factory didn’t do squat. And won’t do squat because they’ve burned the code onto an IC that requires some device to do a read/write. Perhaps it can be done via the SD card slot but I do not think so.
You should avail yourself of the opportunity to read your logger and recorder files.
You are thinking about a low level reset which Bambu’s factory reset is not. It just wipes user settings and you go through the binding and wifi setup and that is it. Low level is brick your printer country and that is the proprietary part.
The printer executes the print. That’s the proprietary part. All these various various Raspberry Pi OS setups like Marlin, Mainsail, Fluidd, on things like Ender printers are so you can tweak the hardware program on the fly, you can not do on a Bambu, that’s the proprietary part.
All studio does is slice the model and in my case append the Bambu created start finish routines to the model and the model executes the print. I have not defined any profiles/presets. It’s kind of challenging to do that when the printer fails right out of the box.
Tell me how to flash the software on the printer boards behind hose plastic covers.
You think perhaps after I uploaded copious log files to Bambu Lab they might have said “Oh hey. Resetting your printer will fix your issue.” Well, they didn’t. Through 3 different tech people.
When the printer goes through the auto calibration that has Zip to do with Studio, gives me a big thumbs up that I passed the auto-cal and then proceeds to carve a measurable gouge across the build plate, that’s the printer software.
When it executes the start sequence for a print and when it travels to the purge chute preparatory to doing a pre-print purge, and promptly faults at that exact location, every single time, that’s software.
A signature of software that is broken is it’s repeatability.
If you want to call it firmware, that’s on you. it is not germane. Only difference between firmware and software is where the code is written to and the language used.
It’s ALL code
When you get your new printer, it will use the same (current) code (software and firmware) used by everyone else who are not having toolhead cover errors.
Software is “soft” because it can be replaced without replacing a physical object. If it is burned into silicon it is no longer soft.
I predict that the new printer will work as designed because it will not have not faulty hardware.
Firmware IS software. It is a type of software that is non-volatile. That is to say, when you turn off your machine it doesn’t turn into an expensive hunk of scrap. I suppose you had a printer before you bought your Bambu and had to flash the firmware (software installed on low level non-volatile memory) and then there was an update and in some fashion you got a message saying we have updated the drivers for your BTT SKR Mini or some other board so the update is here so you can reflash with the updated firmware?
Perhaps Bambu looked at those logs and said Ooops, error in the firmware . We can reflash the firmware and sell this printer as an Open Box. None of that negates the fact that firmware is a sub-type of software. Every computer on Planet Claire has a re-writable BIOS that can be considered firmware. That BIOS (firmware) will likely be over-written numerous times over the life of the computer.
, you won’t.
