Bambu Firmware Bug Reporting Thread

This is so odd, how could they start selling new nozzles overlooking that the printer doesn’t support them?!

They will it is a partnership, they just started limited shipping Jan 2 so might already be in the next FW but just in case calling it out since it is in the wild now.

And just to be clear the standard nozzles work just fine with the bambu settings its just the new special sized nozzles that are missing most users will not be using those sizes any ways. I do across my diffrent printers for very fine gears and tiny models but most dont. Its why i love revos all nozzles shared across all devices

Oh right, I thought they were shipping already. I have Kingroon hotends with CHT nozzles but haven’t even tried them out yet. I’ll buy at least one of the Revo partnership ones as well, probably one of each :see_no_evil: or at least all the new sizes.

Vase mode with 1.40 nozzle should be cool… BTW I wonder if you could slap on a higher power heater without overtaxing whatever is feeding the power. Or maybe it isn’t about power at all, only heat transfer?

So assuming the data for the stock nozzles is correct that i have read the stock is a 40W ceramic heater. The Panda Revo is a 60W so clearly no issue.

1 Like

Problem: New Nozzles Sizes Not available in FW
Firmware Version: 01.07.01.00 (20231222)
Printer: Bambu Lab X1-Crabon
Steps to reproduce:

  1. Navigate to the Maintanace section on printer
  2. Try to change the nozzle size to a custom nozzle there are now options that are needed with the new partnership.
  3. Notice that there is no option for custom or Revo this is now an issue since Revo nozzles have new sizes that are not Bambu Standards.

This is a blocker since it does state the sliced file does not match the nozzle.

Nozzle sizes needed for revo are

0.15, 0,25, 0.4, 0.6, 0.8, 1.0, 1.20, 1.40

No logs needed for this issue.

I can now fully validate that this is an issue my devices just showed up for my two bambu X1 Carbons and they do not have the ability to print with the smaller or larger nozzles.




2 Likes

Problem : Filament doesn’t retract cancelling a print
Firmware Version : 01.07.02.00
Printer : Bambu Lab X1-Carbon
Steps to reproduce : Start a print. Cancel the print. The print stops, and the filament doesn’t retract.

This is true.
Anyways - Why should it? If you cancel a print there is a good likelihood that you restart with same filament again. If not, it is changed on start of print.
To me this seems to be a feature, not a bug.

Well, that purely depends on the system design. Only Bambu knows which max Power the designed the Heater to have. But I hope they don’t “co-develop” a hotend which exceeds their design limits …

This is a change to behavior. Previously the filament would be retracted on cancellation.

It wasn’t changed recently. I got my printer in August and it never did that on cancelling a print.

Problem: Since upgrading to Bambu Studio 1.8.4.51 on the current MacOS, right click on Object still brings up menu, but Edit Text menu item is now always grayed out
Firmware Version: N/A
Printer: Bambu Lab X1C
Steps to reproduce: Select text on an object. Right Click to bring up options menu, and Edit Text is grayed out and cannot be selected. Also if you go under Process → Objects and select a text object, right click and again Edit Text option is unavailable… (You can still edit text using the Text Shape button.)

Problem: skip object was skipping wrong object selected
Firmware Version: 01.01.01.01
Printer: Bambu Lab X1-Crabon
Steps to reproduce:

Load 25-50 piece file. Run first layer and pause to provide time to skip object. Select a few objects and see what happens. See if the selected objects are skipped. I was printing a lot of pieces and don’t know if there is a sensor that “reads” the objects. I’m new to the Bambu printers.

Log file: none

Other information:
Filament loaded from the ams. Put down its first layer and the software detected first layer issues. So I pulled those items off the print bed, I did the skip object feature via the touch screen. However it continued to print in mid air. Side note, I saw it skipping an object that wasn’t marked at all. Look at the images attached and compare. In the back right, those two were skipping fine as it was asked. However the group nearest the front kept trying to print. If you look at my photos you can also see one that was being skipped but was not asked to skip. I marked those with a ? And x. This first image shows a total of 8 objects that are marked to skip. The group of 4 is where the machine was trying to print in mid air. Yes, I know there is nothing in the spots on my second image. Thats because I kept pulling the gunk out/off so I didn’t have to start the print job over again. See second image. The far left two were marked to skip, but were not skipping. Keep in mind that all of the skips were requested before the machine even continued to print the full job.


If you compare it to the next image. the far back 2 parts are skipping as requested / expected. In the second image, the ones marked with the ?x wasn’t being asked to skip if you compare it to the previous image. You can tell it’s being skipped as those pieces are not as tall as the others at the time of the photo. The far left two appear to still be printing. On the second image, the one with the x? is actually to the right of my requested two right there.

@ z28kid

You should create an issue ticket at the link below since the issue seems to be slicer related not firmware … Also no one is watching this anymore i have placed an issue here and you can tell no one is monitoring it since the badges are no longer being given out.

1 Like

Need Help with P1P Firmware Upgrade from v01.00.00.04

Post:

Hi everyone,

I’m running into an issue trying to upgrade the firmware on my Bambulab P1P from version 01.00.00.04 using the Bambu Handy app (Android version 2.6.1) and could use some advice.

What I expected:
After configuring the network settings and my account on the Bambulab P1P, I expected to link it to my Bambu Handy app smoothly.

What actually happened:
Instead, I received an error code -7 from the Bambu Handy app during the process of associating my account with the printer.

Additional context:

  • I’ve attempted the firmware upgrade multiple times, encountering the same error each time.
  • My network connection is stable, and I’ve verified this.
  • Restarting the P1P and my Android device hasn’t resolved the issue.
  • This is the only error message I’ve seen, with no other indicators of what might be wrong.

Looking for:

  • Any advice on resolving the error code -7 and successfully upgrading the firmware.
  • Suggestions for any additional troubleshooting steps that might help.

I really appreciate any guidance you can offer. Thanks in advance for your help!

Welcome to the forum.

The wifi on the P series can also be configured via the SD card.

3 Likes

Thanks @JonRaymond,

I successfully configured wifi via SD card however the device fails to update the firmware OTA without an associated account…

Were you able to scan the QR code as detailed in the wiki steps? The “+” sign in the top right corner of the Handy app will allow you to scan the QR code that is presented.

2 Likes

I was able to scan the QR code and discover the printer but during the binding process an error code (-7) was received without context (see photos)


And you can’t press the “Confirm to Bind” at the bottom?

Is your bluetooth on and have you allowed Handy to use it?

2 Likes

It displays the error on each press of the “Confirm to Bind” button (button goes into a loading state on click and then the application displays the error). Bluetooth is on and Handy is allowed to use it.

Also attempted to bind using Bambu Studio and received error code:

“(-1080: failed to parse login report reason/has error code): possible cause is connection issue with printer.”

Just tested this on iOS as well and received the same—(-7)—error code as Android…

It appears as if there’s been a backwards incompatible change between versions of the system that support binding with this firmware version? I’ve reproduced this issue on three different networks with three different WIFI routers as well.