So printed the same model using the default cold plate that came with the printer (X1-Carbon Combo) with PLA+ (Duramic), ABS (Sunulu) and PETG (Sunulu). Those all printed fine (glue stick also to cal/prime line). Swapped to the PEI plate and PLA+ no problem, but after the 1st ABS print, the printer is giving the msg of ‘Location Marker’ not detected. Looking at the PEI plate, there is no location marker on it as it does on the Cold Plate. Which is odd given that I printed using the settings of ‘Textual PEI’ plate.
The print was perfect other than the msg. Doing the next test print now on PETG.
Wasn’t sure if this is something that I should open a ticket with support or not. Just wondering if anyone else in the community are experiencing similar problem or not.
all official plates have a QR code , but there seems to be some problems with the Hot Plate QR code and possible the Textured plate
but for now it can just be ignored , they are working on a update, so most likely next firmware update those codes get fixed
in meantime the error also does nothing exept reporting it , guess it will only act as soon it is fully working ( maybe in 2 firmware updates )
I wish that my printer firmware could pause printing if missing a hot plate completely, I don’t want to have expensive damage that could be avoided. Granted it is my own forgetfulness not the fault of my printer.
auch bei mir ist es interessant. Nach ca 2 Wochen Drucken mit der Texturierten PEI Platte von Bambulab in denen alles ok ist, wird die Platte nicht mehr “erkannt” und es kommt die Meldung: Build plate marker not detected.
Bei allen anderen Platten funktioniert die Erkennung.
In Bambu Studio habe ich darauf geachtet die jeweilige Platte auch richtig zu zuweisen und die Cars sind sauber.
Hat jemand von Euch eine Idee?
Danke & Grüße aus dem Norden Deutschlands,
Maik
Hello everyone,
it’s interesting for me too. After about 2 weeks of printing with the textured PEI plate from Bambulab, in which everything is ok, the plate is no longer “recognized” and the message appears: Build plate marker not detected.
The detection works for all other disks.
In Bambu Studio I made sure to assign the respective plate correctly and the cars are clean.
just started same problem here today on one of my newest printer… since it was fine before and others so far seem fine… i tried other plate same issue, it is the printer for some reason gone off the rails…
i switch and clean everything did calibration and still no luck… oh well i keep looking for a solution…
For me the biggest problem is that the message I get is ambiguous:
“Build plate localization marker is not found, or the current build plate is not the same as in G-code. Please stop the print job and replace the build plate. You can also tap “Resume” to force resuming the print job. [0300 8006 093010]”
I think it should be split into (something like):
“Build plate localization marker is not found. {%EXPECTED_PLATE_TYPE%} was expected. Please stop the print job and replace the build plate. You can also tap “Resume” to force resuming the print job. [0300 8006 ######]”
and
“Build plate localization marker {%DETECTED_PLATE_TYPE%} was found while {%EXPECTED_PLATE_TYPE%} was expected. Please stop the print job and replace the build plate. You can also tap “Resume” to force resuming the print job. [0300 8006 ######]”
This way when I stand in front of my printer I instantly know if it is fine to continue and don’t have to check in my slicer again if I selected the wrong plate.
I get the message every now and then when the room is (too)bright.
I mostly agree (see below). I just got that message when it was the proper plate last night. Before it was only when I had screwed up.
I wrote a long reply about this. I’m pretty sure a lot of the LIDAR and nozzle cam errors are at least partially from this source. My error last night had a bright “Sunlight Matched” OttLite shining in the cabinet.
I also wonder if it may be related too the latest Firmware update, something may have changed behind the scenes, BL is constantly tuning things.
It’s the nature of software / firmware to pop out new errors when you change something that appears completely unrelated! Much to the distress of the programmers and users. You confidently change ‘Q’ and suddenly ‘D’ and ‘L’ start popping weird errors. LOL
Another odd though occurred just now. In my case last night I also had printed the item (BL PLA) on a PEI plate when I meant to use a Cool Plate. I had an adhesion issue (small part no brim), so I switched to the Cool Plate and resliced. Printed fine but popped the plate error despite being changed and re-sliced.
I wonder if it may be a Studio issue (I’m using the newest OrcaSlicer, 1.5) not picking up the change properly. I think I still have it open, I tend to run with a lot of tasks. OrcaSlicer now has a G-Code examination window, I’ll look and see which plate is specified.
Though that’s a good idea (and one I’d personally like), IDK is they have the room in the firmware to add it. I would think since they’re excellent engineers they have reserved NVRAM space for future improvements, but it’s usually very dear. I doubt they’d do this when there’s only a few plates to choose, and lock themselves out of space needed for something more important in the future.
A couple more months and my printer can finally move to a different room where I can block the sunlight much easier. I hope that will help
As someone who has written software for some years I can only agree
Interesting. I noticed something that looks related. I also had some weird issues with the MicroSD card at that time (slow sending over LAN with a lot of timeouts).
During that time I was sceptic of using the same filename when re-slicing and re-sending. I also use the OrcaSlicer. When I had those issues I was using the previous version (the last one that was named softfever) and after updating to OrcaSlicer 1.5 I did not have the problems any more. For me is feels more like coincidence timing.
The limited NVRAM is a good point. The software I wrote was for Windows computers. So a couple of additional messages where relative cheap so they were usually “just added”. But I can understand that at Bambu they have to be careful with allocating the space and make some difficult choices.
Besides cleaning is there anything else to check for? I’ve been getting this issue for the past week or so. It’s not detecting any of my plates, hot/cold/textures/engineering.
I’m also using a Wham PEX plate that has a qr code sticker that isn’t being detected either. I know other say it works just fine. The Wham PEX plate is working amazingly though!
I have cleaned the camera lens. It randomly started working again for about a week and just yesterday it started having this issue again. I’ve been cleaning it pretty good too. I’ve also got an issue where the lidar goes offline too. I’ve checked all of the connections and resetted a few of them. I’m not sure what else to try but if it fixes itself in a day or 2 that would be really odd.
In addition to the room lighting and shadows seeming to be a factor, I have noticed the printing on the Textured PEI plate is very much lighter (less contrast) than the Cool Plate, etc which have sooth surfaces.
Mine does it rarely so I haven’t noticed if it’s mostly the PEI plate, which is the one I used for at least 80% of my printing …
You could have a PCB that has an intermittent issue. You might check the connections to the LIDAR / Camera as a 1st step but that sounds like it might be worth opening a ticket with BL Support.
Be prepared to be very patient, they’re really overloaded and slow but generally will resolve issues.
The directions are here:
Thanks, I started a ticket for this. The hard part is because of how intermittent it is. I will spend a day cleaning, restarting, checking connections, etc… and it won’t go away. I end up printing just ignoring the error for 2-3 (or more) days and one time it will just stop coming up and print normally for a bit.
Ohhh, that’s sad. Well, ticket time it is. BL Support usually is pretty good on problems with a bad board.
It’s not unusual when you’re producing thousands of machines to have a bad board slip through. Of course, that’s not much comfort when it’s your board!
I’m sure they’ll be happy to send you a new one, and it’s a pretty easy change as these things go. Please do keep us updated on it, k?
Much to the distress of the programmers and users. You confidently change ‘Q’ and suddenly ‘D’ and ‘L’ start popping weird errors. 
LOL
