Bambu Labs A1 Octoprint issue

Get Help
1

What is the problem?

The Bambu Labs plugin from @jneilliii seems to work intermitently, so I'm hoping I'm doing the right thing by posting in a new thread instaed of hijacking another thread.

What did you already try to solve it?

I've tried disconnecting the printer, reconnecting it, turning the printer off, and back on again, I've uninstalled all non-essential plugins to OctoPrint so I'm left with the "base" ones.

Have you tried running in safe mode?

Nope, wasn't even sure what safe mode was going to achieve given I think it's a plugin problem

Systeminfo Bundle

Not sure how I can attach this here as a newbie, but lets give this a go....
octoprint-systeminfo-20250112140811.zip (63.2 KB)

Version information:

  • OctoPrint 1.10.3
  • Bambu Printer Plugin 0.1.7
  • Bambu Prrinter version: 01.04.00.00
  • Printer hardware: Bambu Labs A1 (not mini) with AMS Lite

Additional information about your setup

I'm using a Pi 3B with a logitech web cam plugged in as the internal A1 camera is really rubbish!

So with all the above out of the way, as I think I mentioned, I've sucessfuly installed OctoPrint and the plugin from Octoprint for Bambu Lab A1 support available? and confugured my printer using the plugin and I'm using a LogiTech Streamcam plugged into the RPi3B.

The plugin picks up the printer withtou a problem, shows what's on the SD Card, obtains print bed temerature, and at one point I had it hooked into OctoEverywhere and it was telling me when it throught a print had failed.

Recently however after not printing for a couple of days, the plugin refuses to detect that the printer is printing which also means that I've stopped getting alerts from OctoEverywhere as well. I've tried restarting OctoPrint, restarting the Pi, restarting the printer (after the print of course), but it's just refusing to detect that a print job has started, or is in progress. Which also means that the integration into OctoEverywhere isn't monitoring my print job and letting me know of print failures like spagetti or blob detection.

The firmware hasn't changed either and I'm using 01.04.00.00 which the Bambu handy app and the Bambu Slicer both tell me that it's the latest version (I'm not enrolled into the Beta Firmware program).

Have I misseed a setting? Should I be posting under the Plugins forum post? I wasn't sure of ettiqute.

Thanks in advance!

2

You mention Handy app, which means your printer is cloud connected. Is the plugin also cloud connected, because my understanding is that is required with the A1/P1 series. As soon as you connect printer to cloud it will not respond to local connections.

3

I couldn't actually work out how to get the plugin cloud connected. Wierdly, what I ended up doing was as follows:

  1. Install OctoPi
  2. Setup the Webcam
  3. Install the Bambu plugin using the zip file from the install plugins ( https://github.com/jneilliii/OctoPrint-BambuPrinter/archive/master.zip )
  4. Set plugin to the following:
  • Device Type A1
  • IP Address: IP Address of local printer
  • Serial Number: SN of the printer
  • Access Code: Access code from the front panel of the printer WITHOUT setting LAN only mode
  • Check "User Local Access, disable fro cloud connection" (mainly because I didn't know what to put in the boxes)

And then under "Default Print options" I have checked:

  • Enable Bed Leveling
  • Enable vibration calibration
  • Use AMS

Once I hit save, then under Serial Connections I could choose "BAMBU" as a serial port.

After saving the settings, under the "Connection" back on the main page, I choose "BAMBU" under serial port, baud ratge as 115200, and printer profile and then "Auto-Connect on server start up"

So now it connects, shows "Files" and detects the bed and the tool temp but just doesn't know that I'm in the middle of a print or that I've started one.

Like I said, a couple of days a go I was able to print a couple of fidgets and it showed I was printing and I was able to obtain a timelapse from OctoPrint (I just have to make sure it's a timeed time lapse as of course, it won't have the G-Code for a Z Change, so that makes sense).

But yes because I share my printer with my other half, my other half doesn't understand Bambu Slicer, so I've set him up with Bambu Handy. If remove the "User local Acess" checkbox, I can put my email and password in there, but when I click "Login" it doesn't work so I don't know how an auth token is generated and I don't know how necessary Region is.

4

If you are getting a file list then it's definitely connecting to the ftps side. On the printer's control panel, make sure you have cache files locally enabled (not sure where that is on the A1). There are lots of caveats discussed in a couple of issues on the plugin's repo, but the main one is related to filename not matching in the MQTT payloads. You can enable debug logging for octoprint.plugins.bambu and then disconnect, reconnect, and get some additional details in octoprint.log and bambu_serial.logs.

5

I don't really know what I'l looking for, but I can see in the logs the following lines:

2025-01-16 16:53:38,982 - octoprint.plugins.bambu_printer.BambuPrinter - DEBUG - Received printer state update: RUNNING
2025-01-16 16:53:38,988 - octoprint.plugins.bambu_printer.BambuPrinter - DEBUG - Received printer state update: RUNNING
2025-01-16 16:53:38,992 - octoprint.plugins.bambu_printer.BambuPrinter - DEBUG - Received printer state update: RUNNING
2025-01-16 16:53:38,998 - octoprint.plugins.bambu_printer.BambuPrinter - DEBUG - Received printer state update: RUNNING
2025-01-16 16:53:38,999 - octoprint.plugins.bambu_printer.BambuPrinter - DEBUG - Changing state from IdleState to PrintingState

Despte the web front end not thinking that I'm printing anything. The serial debug log is no good, it just gives me the printing files over and over again.

serial (1).log (162.8 KB)
Honestly not sure what I'm looking for in the octoprint.log. Does this help?
octoprint.log (3.0 MB)

There was a print running at the time I disconnected and reconnected after upping the debug log.

6

Just as an update, I've uploaded the complete log file after the print has finished. I can confirm thaat i the log it mentions:

2025-01-16 17:47:11,004 - octoprint.plugins.bambu_printer.BambuPrinter - DEBUG - Received printer state update: RUNNING
2025-01-16 17:47:11,010 - octoprint.plugins.bambu_printer.BambuPrinter - DEBUG - Received printer state update: RUNNING
2025-01-16 17:47:11,017 - octoprint.plugins.bambu_printer.BambuPrinter - DEBUG - Received printer state update: FINISH
2025-01-16 17:47:11,019 - octoprint.plugins.bambu_printer.BambuPrinter - DEBUG - Received printer state update: FINISH

Because the log is now over 4mb, I've uploaded it here (hopefully it doesn't expire before someone gets to it)

7

Thanks, this was the bit I was looking for...

2025-01-16 16:55:43,239 - octoprint.plugins.bambu_printer.BambuPrinter.states - DEBUG - No 3mf file found for PrintJob(print_percentage=34, gcode_state='RUNNING', gcode_file='screenbar-webcam v3.stl.3mf', subtask_name='screenbar-webcam v3.stl', start_time=None, end_time=None, remaining_time=40, current_layer=55, total_layers=300, print_error=0, print_weight=0, print_length=0, print_bed_type='unknown')
2025-01-16 16:55:43,243 - octoprint.plugins.bambu_printer.BambuPrinter.serial - DEBUG - >>> Begin file list
2025-01-16 16:55:43,245 - octoprint.plugins.bambu_printer.BambuPrinter.serial - DEBUG - >>> imposs~1.3mf 0 0x5a28229a "Impossible Sphere-nosupports.3mf"
2025-01-16 16:55:43,253 - octoprint.plugins.bambu_printer.BambuPrinter.serial - DEBUG - >>> flippe~1.3mf 761255 0x599bb140 "Flipper Zero WiFi module case.3mf"
2025-01-16 16:55:43,259 - octoprint.plugins.bambu_printer.BambuPrinter.serial - DEBUG - >>> waterp~1.3mf 1045534 0x5a222735 "Waterproof box .3mf"
2025-01-16 16:55:43,265 - octoprint.plugins.bambu_printer.BambuPrinter.serial - DEBUG - >>> imposs~2.3mf 3539216 0x5a26103a "Impossible Passthrough Sphere.3mf"
2025-01-16 16:55:43,272 - octoprint.plugins.bambu_printer.BambuPrinter.serial - DEBUG - >>> sphere~1.3mf 681087 0x5a2b0b88 "Sphere Impossible Passthrough .3mf"
2025-01-16 16:55:43,278 - octoprint.plugins.bambu_printer.BambuPrinter.serial - DEBUG - >>> imposs~3.3mf 6496657 0x5a2880e6 "Impossible Passthrough Sphere Fidget Toy.3mf"
2025-01-16 16:55:43,285 - octoprint.plugins.bambu_printer.BambuPrinter.serial - DEBUG - >>> weepin~1.3mf 52172278 0x5a2981cc "Weeping Angel in Attack Pose _Doctor Who_.3mf"
2025-01-16 16:55:43,292 - octoprint.plugins.bambu_printer.BambuPrinter.serial - DEBUG - >>> stage_~1.3mf 13905865 0x5a2c9a2d "Stage 1 2 Shaft.stl + Stage 1 Planetary Bolts.stl + Stage 1 Planetary Carrier Top Cap.stl + Stage....3mf"
2025-01-16 16:55:43,298 - octoprint.plugins.bambu_printer.BambuPrinter.serial - DEBUG - >>> upper_~1.3mf 15138465 0x5a2d085c "Upper Housing.stl + Upper Internal Toothing.stl + Output Shaft.stl + Lower Internal Toothing.stl ....3mf"
2025-01-16 16:55:43,305 - octoprint.plugins.bambu_printer.BambuPrinter.serial - DEBUG - >>> screen~1.3mf 266797 0x5a31047d "screenbar-webcam v3.stl.3mf"
2025-01-16 16:55:43,319 - octoprint.plugins.bambu_printer.BambuPrinter.serial - DEBUG - >>> End file list

What I'm confused about is why it doesn't see it because it does show screenbar-webcam v3.stl.3mf returning in the file list just after. Once that happens, then the plugin/OctoPrint should identify a printing state running and go into print progress reporting, etc. Maybe something to do with the space in the file name? Can you test with a file that doesn't have that?

All that being said, not sure how much work I'm going to continue to put into this plugin since the recent announcement from Bambu: https://blog.bambulab.com/firmware-update-introducing-new-authorization-control-system-2/

8

Ah right. Looks like removing the space from the file name didn't resolve the issue. I find it really weird because I can't still yet put my finger on why the printer picks up some print files, but not others. It is at present being all sent through on the Bambu Slicer app, but admittedly I've not integrated it with Octoprint.

Here's the re-print of the same STL in progress, but the interface hasn't piocked up the fact that it's printing: Unique Download Link | WeTransfer

I'l play around some more to see if I can figure out why sometimes it triggers and some times it doens't. as yesterday I printed the file name "A1 _ A1 Mini Tool Box with sliding lid.m3f" and it picked up the print (Octoprint told me it failed, but I'm okay with that it was at least monitored). I don't know if I have the log file for that one because I've been playing around wtih logging sorry!

9

Right. So I can confirm it's all in the file name. Anything that has a hyphen/dash in it "-" Octoprint doesn't pick it up as the printer is printing. I just started a print that I pulled of Makerwork straight into Bambu Studio and it doesn't have any hypens in the project name or the print name, and as soon as I threw it at the printer, Octoprint picked it up straight away. Now knowing this, I'll just make sure that my file names don't contain a hypen when sending it to the printer if I can avoid it!

Thanks for putting me on the right track @jneilliii !

1 Like
10

That's an interesting find. Can't say why a hyphen would through a monkey wrench into file name matching/print start detection, but with that information I can definitely troubleshoot further. Can't say I've ever named files with dashes, usually use underscore.

11

Honestly, don't stress if it s a bug I can work around. If it was me, I'd put it into the known issues and leave it be. Like you said, if Bambu are shaking things up again and locking things down, it's probably not worth fixing the bug. I just had dashes in file names because that's what the STL file was that I got from say printables. And I kinda leared something which is that the name of the project doesn't reflect the file that gets sent to the printer. I never noticed the title before on the Bambu Slicer as you hit "Print Plate" it's right at the very top what filename you're sending to the printer. Learn something new every day :slight_smile:

There are some other teething issues like Octoprint saying the print failed when it finished, and the print bar in OctoPrint doesn't know how long the job is going to take, but it's totally fine given it actually finishes printing and creates the time lapse for me using the external webcam. As I think I mentioned, I mostly wanted to hook it up. into OctoEverywhere to keep an eye on if the print goes sideways so I can work around the rest!

Still just wanted to say thank you for the plugin in the first place because it's mostly been seamless.
If you do need me to test any updates in future, please let me know and I'll do my best to give you feedback.