The "textured PEI" plates tend to work very well for PLA and PETG. For everything else, I use the Vision Miner Nano Polymer. It's a bit pricey, but it doesn't take much, and you can re-use it at least a dozen times (and counting). It's alcohol based, so when you DO clean it off, you'll need IPA. It works at 50℃ and up (so cool down to below 50℃ before removing).

I use it on the "fancy" textured plates (carbon fiber / diamond / holo) and it works well with PLA, PETG, ASA and TPU (the filaments I've tried to so).

Also, it doesn't leave the residue like glue stick-- prints come off nice and clean.

This should be present by default in the "Textured PEI Plate" profile.

Bambu Studio has those options too now.

My primary factor in the X1C was the much, MUCH improved processor.

True, but the auto-calibration is much faster. I can do flow-calibration on all 4 filaments in the AMS in one pass.

Generally speaking, the difference is not worth the $500.

But.

The benefits are: lidar (calibration, first layer), spaghetti detection (really does work), blocked poop chute (Which I was surprised, but pleased by), higher framerate camera, much more powerful CPU, and a nice touch scsreen. The hardened extruder and slightly higher bed temp are nice, but you can upgrade the extruder on the P1S, and I have yet to need that last 10℃.

All of these are quality-of-life upgrades, rather than necessary upgrades.

If you can comfortably afford the difference, go for it-- you won't regret it.

But you won't be disappointed with the P1S either.

I've had an X1C for 6 months (January), and I've been very happy I've had the lidar many times-- automatic flow calibration is nice, but the three first layer failures that it detected were much more useful.

Have had a couple spaghetti failures detected, but the blocked poop chute alert/pause was REALLY helpful, as it avoided the Blob of Doom.

These arrows point to the screws you were supposed to remove during setup. Since your printer works (I assume), then you set it up correctly, and you may safely ignore these stickers.

Should you decide to repack the printer correctly, and kept all the screws and bits, then those stickers would tell you where to put the screws as you reverse the setup process.

It's not as easy as you think. Spools measure quantity by weight (grams), and the slicer estimates the usage in terms of length (mm). So, IF your density is spot on in your filament profile, then yes, the slicer can track "X" mm used is "Y" grams. But now you have to create a unique id for every spool you use, and you have to tell the slicer which unique ID you're using.

Yes, you can track it for one use of a spool, but now you have no idea what the total amount used / left is which would be the primary reason for doing this.

Alternatively, you could weigh the spool + filament when it's fresh out of the bag (subtract 2kg to get the weight of the spool). Then, assuming you know the density so that you and the slicer agree, any time you want to know if you have enough filament left, weigh the spool + filament, subtract the weight of the spool, and now you know how many grams of filament you have.

That's fair. Some of the Reddit communities have official reps, but I'm not seeing one in the moderator list.

But the fact that they can't get basic environmental conditions to make sense doesn't say much for the development team. I can't believe they're not aware of the problem, so yeah-- this is more venting than expecting an actual response or solution.

I had this crazy idea of a single tool head but with multiple hotends (with mag-style connectors).

Each nozzle would have a filament in it from the AMS. Do a mild retraction to cut down on oozing, cut the filament and park the head. Then grab the new (or previously used) nozzle, heat it up, and shove more filament through it.

Still have to heat up when switching, but you wouldn't have to worry about purging.

... just a thought.

I get that if I'm standing on the sun side of Mercury in a cheap suit, I should baste myself for better flavor when I'm fully cooked.

But I'm standing on Montara Luna in a Mk I Constellation suit, talking to someone in overalls, they're fine, and I'm choking to death.

I did, but it's difficult to complete the mission from inside my ship.

Had to wait nearly 24 hours in total for the storm to pass.

For clarity, is this the "X1" (the original printer) or the X1 Carbon?

Star Wars Return of the Jedi got some hate because of the slave bikini-- I always felt that was a major misread of the situation. Jabba put Leia in that outfit to deliberately humiliate her for her actions-- and her response was to kill the slug with his own chain.

In the novel, it was suggested that Leia was assisted by the Force, as ordinarily, she shouldn't have had the strength to strangle Jabba, but even so-- he tried to humiliate her, and she killed him. That's not a weak character.

Her character was seriously underused in The Empire Strikes Back, though.

An "introductory" clip should stand on it's own. The clip here, while great, is just two guys talking.

I really like the scene on Othala from The Fifth Race.

Reduce chamber fan to 70% or less, and the noise will drop to tolerable levels.

"I'm stuck on a glacier with McGyver!!!!"

Hate to say it, but this really looks like fuzzy skin is enabled for the object.

Does it look like this in the preview in the slicer?

So the default operation is that the printer will contact the Bambu Cloud via the MQTT protocol (SSL/TLS) and register with a broker. That broker will send data to the printer when you start a job, or when Bambu Studio queries the printer. The printer will send it's responses to the broker, which your application will retrieve via https (I believe-- Bambu has a list of necessary ports on their website).

So if your organization has a bastion network, or a non-trusted device network, you could in theory, put the printer there.

Alternatively, you can put it in LAN only mode, and as long as your workstation is allowed to communicate with the printer, you can send jobs, see timelapses, control the printer, etc., and it does *not* communicate with the cloud.

That's assuming that your workstation can communicate to the wireless network-- the X1/P1 will be on the wireless network.

The X1E does all of the above but also has an ethernet port, and speaks higher levels of security for wired / wireless connections. It also has a real chamber heater, instead of the simple enclosed space heated by the print bed of the X1C/P1S.

As for data collected, there's a lot of anti-Bambu FUD (fear, uncertainty, doubt) out there about what gets collected and schlepped around the network. Short form: The .gcode file for the sliced model will be uploaded. The thumbnail image will be uploaded. Your printer's unique ID, possibly including your LAN IP address, along with your Bambu account, will be uploaded. And that's pretty much it.

After that, if you open a support ticket, a fairly large amount of information will be collected from your printer, and sent as part of an (optional) upload.

Everything except the debug log doesn't apply if you're in LAN mode, because you're not connecting to Bambu's servers.

With a few qualifications regarding FAA regulations, it's no different than hiring a PI to spy on the SO.

Since she didn't know he had the drone, it's entirely possible the drone's owner was standing next to the car watching.

As someone who just completed the TRUST course for recreational flying, he must be within line of sight (LOS), and if he intends to fly over a gathering of people, he needs to have a waiver from the FAA. Ideally, the drone should have either prop guards or collision avoidance.

If the drone is under 250g, then the drone doesn't need to be registered, but still not supposed to fly over lotsa people. One or two people in a park isn't really a huge deal.

Now-- She sounded like she didn't know he had a drone, so it's entirely possible the drone's real owner was sitting there watching the drone, and therefore the LOS rule was satisfied.

As it's outdoors in in "public", there is no expectation of privacy, and therefore whether they know about it or not is largely irrelevant.

If you've run Bambu Studio, it should have loaded up your profile. But you can check in the "Bambu Lab X1 Carbon 0.4mm" profile, and look in the Machine Start G-Code for a stanza like this:

;===== for Textured PEI Plate , lower the nozzle as the nozzle was touching topmost of the texture when homing ==
;curr_bed_type={curr_bed_type}
{if curr_bed_type=="Textured PEI Plate"}
G29.1 Z{-0.04} ; for Textured PEI Plate
{endif}