Support latest BambuLab P/X/A firmwares & AMS 2/HT

[Noisyfox]

How to download this

To download the latest test version of this PR, click the "Checks" tab on top of this page, then click "Build All", then you will find the latest build:

---

About this PR

An option has been added in preference to toggle between the new network plugin and the legacy one:

By default it uses the legacy network plugin, which does not come with the authentication feature. You can use it if your printer is on an old firmware and do not need to use the new AMS 2 pro/HT etc.

To support the new AMS 2 or if you just decided to update to the latest firmware, uncheck this option and restart Orca, which will tell it to use the latest bambu network plugin. I don't have X1/A1 so I could not test it to see if you could still use the BambuCloud print with the new plugin, or maybe you have to switch to Lan/Dev mode. However cloud print does still work for P1 with firmware 1.8.0.

Other updates:

• Support print all plates for P1P/P1S
• Support showing humidity percentage
• Support showing info of AMS 2 pro
• Work with AMS HT properly
• Show AMS temp & drying

[RyanHir]

Perhaps these are out of scope for this PR, but I think its best to still comment on it.

It does not appear that raw humidity readings is exposed with this PR. In Bambu Studio I am able to get a humidity and temperature reading from my AMS on the P1S, but in Orca it is still the 1-5 number.

Other interesting thing I want to note is that in Bambu Studio the usage of the AMS is inferred from the filament selected. But with this PR you must enable/disable the AMS manually to select either external or AMS filament.

[Disttrack]

I don't know if it has to do with this PR, but from OrcaSlicer, when the k factor of a filament is set in the AMS, it is deleted after a few seconds. I have to set it from BS so that OrcaSlicer detects it correctly and does not delete it.

[Noisyfox]

Perhaps these are out of scope for this PR, but I think its best to still comment on it.

It does not appear that raw humidity readings is exposed with this PR. In Bambu Studio I am able to get a humidity and temperature reading from my AMS on the P1S, but in Orca it is still the 1-5 number.

Other interesting thing I want to note is that in Bambu Studio the usage of the AMS is inferred from the filament selected. But with this PR you must enable/disable the AMS manually to select either external or AMS filament.

I'll prioritise things that are essential for using Orca with new fw/printers (such as fixing the ams k factor issue), and not on other improvments, due to the fact that I could not debug the app when using the new network plugin.

[Noisyfox]

I don't know if it has to do with this PR, but from OrcaSlicer, when the k factor of a filament is set in the AMS, it is deleted after a few seconds. I have to set it from BS so that OrcaSlicer detects it correctly and does not delete it.

Which printer do you have? How many ams do you connect? What AMS version do you have?

[Disttrack]

I don't know if it has to do with this PR, but from OrcaSlicer, when the k factor of a filament is set in the AMS, it is deleted after a few seconds. I have to set it from BS so that OrcaSlicer detects it correctly and does not delete it.

Which printer do you have? How many ams do you connect? What AMS version do you have?

I have one P1S with one AMS (original) and one AMS2-Pro connected.

I can do some tests if you need.

[Noisyfox]

I don't know if it has to do with this PR, but from OrcaSlicer, when the k factor of a filament is set in the AMS, it is deleted after a few seconds. I have to set it from BS so that OrcaSlicer detects it correctly and does not delete it.

Which printer do you have? How many ams do you connect? What AMS version do you have?

I have one P1S with one AMS (original) and one AMS2-Pro connected.

I can do some tests if you need.

Which AMS did you set the K factor to that triggers this bug? Or both?

[zpriddy]

With this PR, and an X1C running firmware 01.09.00.01, I am able to see the device/start the camera, browse files and do more than before, but I am unable to actually control the printer (no way to raise/lower the bed).

Sending a print job using the cloud also does not work:

It is nice though that it isn't throwing MQTT errors though while just viewing the device, and being able to use the camera.

[Noisyfox]

With this PR, and an X1C running firmware 01.09.00.01, I am able to see the device/start the camera, browse files and do more than before, but I am unable to actually control the printer (no way to raise/lower the bed).

Sending a print job using the cloud also does not work: It is nice though that it isn't throwing MQTT errors though while just viewing the device, and being able to use the camera.

X1 has auth enabled in latest firmwares, so you could not control / start print via cloud unless using bbs.

[reynol3232]

I've encountered a bug using the new build. Whenever I click on one of the AMS slots in Orca (or edit one of the filaments, which subsequently selects it), the AMS will roll the filament back and forth for a couple of seconds. Happens every time I click on one of the filaments, on both my AMS and AMS 2 Pro.
I've checked this in Bambu and it does nothing when I click on a filament, as I'd expect.

This should now been fixed in last commit

Confirmed that this is now fixed.
Equipment: P1S and AMS1, Orca 2.3.0.
I've had this issue for a few years. I've used Orca exclusively since about day2 of owing my P1S so I thought the Filament rollback was normal (although super annoying). I've updated to 2.3.1-dev to see if this corrects the issue.

Right now I can't get Orca to work because I update the Firmware on the P1S to 1.08.01.00 and now I'm getting the "Failed to get AMS mapping table" error.

[saintwolf]

I've encountered a bug using the new build. Whenever I click on one of the AMS slots in Orca (or edit one of the filaments, which subsequently selects it), the AMS will roll the filament back and forth for a couple of seconds. Happens every time I click on one of the filaments, on both my AMS and AMS 2 Pro.
I've checked this in Bambu and it does nothing when I click on a filament, as I'd expect.

This should now been fixed in last commit

Confirmed that this is now fixed.
Equipment: P1S and AMS1, Orca 2.3.0.
I've had this issue for a few years. I've used Orca exclusively since about day2 of owing my P1S so I thought the Filament rollback was normal (although super annoying). I've updated to 2.3.1-dev to see if this corrects the issue.

Right now I can't get Orca to work because I update the Firmware on the P1S to 1.08.01.00 and now I'm getting the "Failed to get AMS mapping table" error.

01.08.01.00 firmware should work, as it's what I use. Have you unchecked the "Use legacy network plugin" option?

[claym001]

I've encountered a bug using the new build. Whenever I click on one of the AMS slots in Orca (or edit one of the filaments, which subsequently selects it), the AMS will roll the filament back and forth for a couple of seconds. Happens every time I click on one of the filaments, on both my AMS and AMS 2 Pro.
I've checked this in Bambu and it does nothing when I click on a filament, as I'd expect.

This should now been fixed in last commit

Confirmed that this is now fixed.
Equipment: P1S and AMS1, Orca 2.3.0.
I've had this issue for a few years. I've used Orca exclusively since about day2 of owing my P1S so I thought the Filament rollback was normal (although super annoying). I've updated to 2.3.1-dev to see if this corrects the issue.

Right now I can't get Orca to work because I update the Firmware on the P1S to 1.08.01.00 and now I'm getting the "Failed to get AMS mapping table" error.

01.08.01.00 firmware should work, as it's what I use. Have you unchecked the "Use legacy network plugin" option?

This is what I had to do, and it works fine for me. I also have a P1S running 01.08.01.00. Unchecking the legacy plugin fixes it.

[ProtoSpyre3D]

With this PR, and an X1C running firmware 01.09.00.01, I am able to see the device/start the camera, browse files and do more than before, but I am unable to actually control the printer (no way to raise/lower the bed).

Sending a print job using the cloud also does not work:

It is nice though that it isn't throwing MQTT errors though while just viewing the device, and being able to use the camera.

X1 has auth enabled in latest firmwares, so you could not control / start print via cloud unless using bbs.

Is the future aspect of this build release going to enable cloud print/camera/printer controls? I just downloaded this due to frustrating encounters via LAN and DEV MODE on the latest firmware for the X1C. I have all printers using new AMS 2 systems and would love full functionality of drying and use of OS like before.

[Noisyfox]

With this PR, and an X1C running firmware 01.09.00.01, I am able to see the device/start the camera, browse files and do more than before, but I am unable to actually control the printer (no way to raise/lower the bed).

Sending a print job using the cloud also does not work:

It is nice though that it isn't throwing MQTT errors though while just viewing the device, and being able to use the camera.

X1 has auth enabled in latest firmwares, so you could not control / start print via cloud unless using bbs.

Is the future aspect of this build release going to enable cloud print/camera/printer controls? I just downloaded this due to frustrating encounters via LAN and DEV MODE on the latest firmware for the X1C. I have all printers using new AMS 2 systems and would love full functionality of drying and use of OS like before.

Cloud mode won't work for X1 with latest firmware.

[ProtoSpyre3D]

With this PR, and an X1C running firmware 01.09.00.01, I am able to see the device/start the camera, browse files and do more than before, but I am unable to actually control the printer (no way to raise/lower the bed).

Sending a print job using the cloud also does not work:

It is nice though that it isn't throwing MQTT errors though while just viewing the device, and being able to use the camera.

X1 has auth enabled in latest firmwares, so you could not control / start print via cloud unless using bbs.

Is the future aspect of this build release going to enable cloud print/camera/printer controls? I just downloaded this due to frustrating encounters via LAN and DEV MODE on the latest firmware for the X1C. I have all printers using new AMS 2 systems and would love full functionality of drying and use of OS like before.

Cloud mode won't work for X1 with latest firmware.

That's what I gathered from the initial statement from Bambu Lab. What I'm trying to figure out is now reading their wiki page on "Bambu Connect" I see different methods of which it seems like users could implement the "Authenticator - Bambu Connect" themselves? In the end I'm looking to use the new AMS 2 but I'm forced to upgrade firmware in order to use it with the new upgrades. I want to continue with OrcaSlicer due to it simply being superior in processing models & feature wise.

I understand SoftFever stated this was not going to be implemented due to the added time and complexity of which isn't and shouldn't be needed in the first place and that's completely understandable. But am I able to add it to my own version? Network? I appreciate what you've done here for P1 users at least.

[Noisyfox]

With this PR, and an X1C running firmware 01.09.00.01, I am able to see the device/start the camera, browse files and do more than before, but I am unable to actually control the printer (no way to raise/lower the bed).

Sending a print job using the cloud also does not work:

It is nice though that it isn't throwing MQTT errors though while just viewing the device, and being able to use the camera.

X1 has auth enabled in latest firmwares, so you could not control / start print via cloud unless using bbs.

Is the future aspect of this build release going to enable cloud print/camera/printer controls? I just downloaded this due to frustrating encounters via LAN and DEV MODE on the latest firmware for the X1C. I have all printers using new AMS 2 systems and would love full functionality of drying and use of OS like before.

Cloud mode won't work for X1 with latest firmware.

That's what I gathered from the initial statement from Bambu Lab. What I'm trying to figure out is now reading their wiki page on "Bambu Connect" I see different methods of which it seems like users could implement the "Authenticator - Bambu Connect" themselves? In the end I'm looking to use the new AMS 2 but I'm forced to upgrade firmware in order to use it with the new upgrades. I want to continue with OrcaSlicer due to it simply being superior in processing models & feature wise.

I understand SoftFever stated this was not going to be implemented due to the added time and complexity of which isn't and shouldn't be needed in the first place and that's completely understandable. But am I able to add it to my own version? Network? I appreciate what you've done here for P1 users at least.

Basically their new workflow will be to slice the project in Orca, then send the result to printer via their new Bambu Connect app.

[ProtoSpyre3D]

With this PR, and an X1C running firmware 01.09.00.01, I am able to see the device/start the camera, browse files and do more than before, but I am unable to actually control the printer (no way to raise/lower the bed).

Sending a print job using the cloud also does not work:

It is nice though that it isn't throwing MQTT errors though while just viewing the device, and being able to use the camera.

X1 has auth enabled in latest firmwares, so you could not control / start print via cloud unless using bbs.

Is the future aspect of this build release going to enable cloud print/camera/printer controls? I just downloaded this due to frustrating encounters via LAN and DEV MODE on the latest firmware for the X1C. I have all printers using new AMS 2 systems and would love full functionality of drying and use of OS like before.

Cloud mode won't work for X1 with latest firmware.

That's what I gathered from the initial statement from Bambu Lab. What I'm trying to figure out is now reading their wiki page on "Bambu Connect" I see different methods of which it seems like users could implement the "Authenticator - Bambu Connect" themselves? In the end I'm looking to use the new AMS 2 but I'm forced to upgrade firmware in order to use it with the new upgrades. I want to continue with OrcaSlicer due to it simply being superior in processing models & feature wise.
I understand SoftFever stated this was not going to be implemented due to the added time and complexity of which isn't and shouldn't be needed in the first place and that's completely understandable. But am I able to add it to my own version? Network? I appreciate what you've done here for P1 users at least.

Basically their new workflow will be to slice the project in Orca, then send the result to printer via their new Bambu Connect app.

Understandable, I hope for a 1-click resolution in the future. I did find a slight workaround for now that's suitable enough for the meantime. Using [2.3.1 Dev] OrcaSlicer > Load Model > Slice > Send > Start Print via Handy App

What's weird is it states file failed FTP via OS but the file is still transferred onto SD Card @ machine and can be started remotely. Sooo what exactly is the point of this authentication? lol

[Disttrack]

Will this PR be incorporated into the mainline at some point?

[anonim1133]

Will this PR be incorporated into the mainline at some point?

I hope it will. As without it, P1S wont start print, it's stuck in heating phase.