Hello,
I just set up today my new A1 + AMS lite. It’s my first Bambu lab printer, after a few years with an Ender 3.
I installed everything according to instructions, updated the formware, and printed the first tests - a benchy, and a scraper support from the included SD card. Then I printed a waste poop basket from the community, and that worked too.
But now whenever I try to print any object from the SD card, it fails with the message “the selected printer (A1) is incompatible with the chosen printer profile in the slicer ()”. I checked the profiles in the “Prepare” and “Preview” tabs, and they are correct. And besides, it correctly reports that the selected printer is A1 but it somehow expects a “blank” profile, i.e. there’s nothing in the brackets. Have a look at the attached pictures, one is for printing a community object, the other for printing something from the SD.
I tried searching around, but other messages about this error all refer to actual mismatches in printer profile.
I tried restarting the app and rebooting the printer, to no avail.
I’m using the latest beta slicer on Ubuntu linux.
Cristian
.postdeletedinprotestofdangerousgoods.
Thanks. But they worked, just a few hours ago. So I don’t think it’s the gcode. It’s possible that it happened after I upgraded the firmware, but I’m not sure. I have not upgraded the app or anything else, just the firmware.
Are we talking about files you sent to the SD card or copied on there?
Or are we talking about the files that came with the SD?
Not sure if Bambu updates the files but the pre-sliced and included files can be found here.
Maybe replacing them with newer versions makes them work with the new firmware.
But you can just download the STL files and slice them yourself.
It’s the files that came with the SD. I didn’t touch them in any way. I didn’t try copying newly sliced files to the SD.
What seems strange to me, is that the error appears to say that there is a printer specified in the gcode (A1) which does not match what is selected in the slicer. The profile in the gcode is correct. It seems to not find the profile indicated in the slicer. It looks as if the software misses the profile check in the slicer, when the selected file does not come from the slicer itself. I don’t know if I chose the right words, but I hope you got my point.
That is why I suggested replacing the files…
If the firmware changed it is quite possible the old g-code files cause a problem.
Can’t find anything in the Wiki though.
A g-code file can only printed, so no profile change possible, that only works if you have the source files as STL or STEP.
Hence me suggesting to download those and to slice yourself 
.postdeletedinprotestofdangerousgoods.
1 Like
Yes, I understand, and it’s possible that it will work (I’ll try later today). But, since as you say there’s no profile in the gcode, why does the software not recognize the slicer profile, and give a mismatch? It’s as if it checks for the profiles in two places: the “selected printer” and the “printer profile”. One of the two correctly reports “A1”, while the other reports a blank, hence the mismatch.
Also, by re-slicing, I would loose some specific setting, like for example the super-fast benchy included in the sd: if I re-slice it, it will print much slower, unless I manually tweak the profile, which I don’t know how to do…
.postdeletedinprotestofdangerousgoods.
Update: I still haven’t tried slicing another file, but I tried printing the old files on the SD, directly from the printer itself (without using BambuStudio). And it works perfectly. So apparently the firmware handles the old gcodes without problems, it’s the slicer that chokes on them.
1 Like
.postdeletedinprotestofdangerousgoods.
