Preventing Second Layer Issues After LIDAR on X1C

But where did you get this information ? :sweat_smile:

From the very same source from where I got this one


…obviously, from BL

My bad! I wasn’t thinking about that. I just did a Google search with “Bambu Lab Status Cloud” and I found this: status.bambulab.com

Yeah. Like Google said …what I said that BL “told” me :grin:

That’s okay, I got it. But I thought it was a different connection at first. I admit that this is the first time I see the cloud so sick.

It’s again the story of a trainee who spilled his coffee on the server socket… :sweat_smile: :rofl: :joy:

What temp is your petg droping down to when it scans the bed?

Yeah, it’s Dave story written all over it :grin:

The scan is done at 210°C, which is way too high. There isn’t enough cooling time before starting the scan.

Breaking news, the latest and the most relevant info on the matter

Apparently the incident has been solved and closed a few minutes ago.
Took them, from their own incident logs not less than 5 h and 21 minutes to get to the bottom of the incident and resolve the issue. For a cloud based and operated service, it’s unjustifiably too long…it’s like they don’t have any backup servers, no BCP or DRP in place … chaos.

Yes, that’s what I just saw. It’s great to see full and effective services again.

getting this exact same problem and i have to turn off first layer inspection too
i think the head should be parked for longer on the chute to allow for ooze