Upon selecting “synchronize filament list from AMS” loads a different set of filaments to that on the printer page. Printer page is the correct loading
See below:-
They look identical to me, which one is different?
1 Like
No 3 is empty on AMS and TPU is external NOT no 4
For clarity the lower picture, though from printer tab of software represents the AMS loading correctly
I wonder if its different now they map at print. Before it represented a1 to A4
Its down to mapping and resynchronization
is it possible to download the earlier version/downgrade version? can’t print!
Welcome to the forum.
Yes you can download previous versions.
1 Like
That one is correct I think… But numbering like that is stupid.
Click on a filament and you should see A1, A2, etc.
For me, the bug is that it does not sync on startup as the “Presets” implies.
I have similar problem after upgrading to ver 2 MAC version. In my case I used to be able to choose which filament I wanted to load on AMS at print stage. Now it only shows Filament position 1 and no others are shown. If I use the iPad version it allows me to select which filament I want from the list of 4.
Definitely a bug in Studio version 2.
1 Like
I have similar problem after upgrade to 2.0.0.95.Now it only shows Filament position 1 and no others are shown.
1 Like
Also, using Print Profiles (3MF) messes things up in ways I can’t even begin to describe.
The logic should be very simple; Never, EVER, deviate from what is physically loaded in the AMS units. Sure, mapping is needed -but not like this.
Flow calibration is totally broken. The printer just sits on heating nozzle part. Filamenta wont sync. Damn they broke ao much… My goes is they relied on open source devs to check nightly builds. And now all left the project and left for home assistant or orca. Serves you right. But im still left with ab almost useless printer for printing
After 30 minutes i get this.
Downgrade of the bambulab studio does not work.
Restart does not work… they just broke somthing on their servers…
I dont like to go to lan mode but dam you are making me.
1 Like
yes, I’m having trouble with mapping in my AMS after upgrading. Now if I use a generic roll, It wont give me any option to pick it in the AMS…Thats ■■■■, I’ve just bought 10kg of anycubic PLA. I’ve restarted both printer and computer, taken all other filaments out of the AMS, tried using it from the spool…still no option. I tried to put it on a bambu lab spool, but the cardboard spool is too small.
Well yeah, I never had that ‘failed to get AMS mapping table’ error until today and even with the 1.x version and with orca slicer.
I entered a new Filament today and started FD calibration. The print started an got stuck with the errormessage above.
Powercycle, SD-Card format, different slot… all the same.
I updated BS to 2.0.0 and to 2.0.1…
Now, when I go to calibration it shows all non bambulab filaments as incompatible!
I can reselect the loaded filament and then I can select it for calibration.
Lets see how far it goes now.
Calibration went through.
But why did it fail before?
Same on the Flow Rate calibration.
When I sync the AMS it shows ‘incompatible’ for all non bambu filaments and they cannot be selected.
Then I select the filament from the list and I can select it and start the calibration printz.
I have the same problem. When I load a part from Maker World with for example two colours and cklick then on synchronize then the colours match not to the colours shown in the device in Bambu Studio and the last one (nr. 8) is alway empty. I must add then one. When I cklick on each arrow on top of the filament in the device windows and synchronize again, then it works.
AMS1
AMS2
After sync…
I am also experiencing a similar issue. Never happened to me before today. Loaded a new (non-bambu) filament into my AMS and I was unable to update the filament type/profile in the editor.
A little lost as to how I can resolve this problem, if I can at the moment.
I’m experiencing the same thing right now. I can’t select any of the AMS slots in the new sync window. Bambu or not.
Release 1.10.2 Public Release
With this Version, everything works again for me… Just a bit sad that since over a month, studio 2.x doesnt work with the ams and my p1s
1 Like