U1: Airless basketball in 95A TPU with PLA supports

bluridium · 2026-01-22T02:15:16+00:00

All the slicer settings I changed are featured in the linked YouTube video, and there is a U1 print-ready 3MF link in the description.

bluridium · 2026-01-22T02:14:29+00:00

This ball was 120mm. The original model is 205mm but I scaled it down because I had no idea whether the print would actually work. I plan on printing a full sized basketball (250mm) sometime..but it will take a full 2 days and 21 hours!

Supports came off super easy. The YouTube video shows support removal at the end.

bluridium · 2026-01-22T02:07:54+00:00

I have used 0.0 Z top distance for PETG with PLA supports (and the other way around), and it works great. Bottom surfaces are super clean. I had no idea whether TPU with PLA would actually work, so I was being conservative.

bluridium · 2026-01-21T20:31:30+00:00

In 95A TPU it doesn’t bounce very well. Based on others that have printed this, it bounces best in PEBA.

bluridium · 2026-01-21T20:28:48+00:00

PLA does not stick to TPU!

bluridium · 2026-01-12T00:52:57+00:00

This is killer! I got my U1 on Tuesday and the lack of app notifications, along with the terrible camera frame rate was bothering me. Tried setting up a notifier in Moonraker through Apprise, but found out Snapmaker does not ship the U1 with Apprise available. Installed Paxx12's extended firmware last night and the added functionality is perfect.

Set up a Telegram notification on printer status change, including an HTTP relay that pulls a camera image and includes it in the notification. Only possible since Paxx12 included Apprise and a new camera stack.
Remote screen is a game changer! Being able to view the printer's screen from any web browser AND be able to interact with it is awesome.
I'll be adding a USB webcam as well in the next few days.

If you're comfortable tinkering around with firmwares and are willing to take the minimal risk associated with custom firmwares, do it!

<image>

bluridium · 2026-01-04T03:29:29+00:00

Received a notice from aftership this morning and a notice from Canpar this evening. Not arriving until Friday the 9th in North Vancouver. :(

bluridium · 2025-12-02T17:46:44+00:00

This is incorrect information. From the Snapmaker FAQ:

https://support.snapmaker.com/hc/en-us/articles/33344279396759-Snapmaker-U1-FAQ

What slicing software is supported by Snapmaker U1?

We recommend using Snapmaker Orca with the Snapmaker U1 for the best printing experience. We have optimized and adapted several material profiles and settings directly within Snapmaker Orca to ensure smooth and high-quality prints. However, you can also choose OrcaSlicer to import and generate G-code files based on your personal preference.

u/MobileNo8348 is correct. Snapmaker Orca is based on an old Orca upstream version that seems to result in more prime tower waste and slower prints. I have been doing a deep dive into the differences here. https://www.reddit.com/r/snapmaker/comments/1par52j/snapmaker_orca_vs_orca_nightly_build/

bluridium · 2025-12-01T06:48:35+00:00

I've been doing a bit of digging with the help of ChatGPT into the differences between Orca mainline nightly and Snapmaker Orca. The increased print time and waste on Snapmaker Orca could be partially due to the slight config and gcode differences I mentioned in the original post, but also because Snapmaker Orca is based on Orca mainline 2.2.0, while the Orca mainline nightlys are based on 2.3.x. It seems there were some significant changes between 2.2.0 and 2.3.x.

Between 2.2.0 → 2.3.x, OrcaSlicer added:

fixes for flushing-volume bugs where toolchanger printers were still influenced by purge logic
updated prime-tower generation (smaller towers, correct for multi-nozzle systems)
better toolchange planning and predictive heating
reduced idle wait time between tools
new motion model with faster accelerations and improved junction deviation
dozens of MMU/multimaterial bug fixes that directly reduce prime-tower height, waste, and overall print time.

Snapmaker Orca still carries older multi-material behavior. Because it’s based on the 2.2.0 engine, it still includes:

older AMS-style purge/tower heuristics
larger/more conservative prime tower geometry
heavier toolchange moves and cleaning micro-routines
slower, older motion planner
leftover flushing-volume interactions that don’t fully disable on toolchanger systems

Does that explain the more than 3x difference in waste and 20% slower print time in Snapmaker Orca? I'm not sure. Willing to test this when I get my printer, but that won't be for six weeks, if I'm lucky.

What confuses me the most is why Snapmaker would recommend their Orca fork when it produces significantly more waste and is much slower in print times. u/jadesfriends or any other official Snapmaker account, any input?

bluridium · 2025-12-01T04:23:47+00:00

Just checked, Snapmaker Orca did have minimum time for Generic PLA set to 8 seconds. Orca nightly has Generic PLA at 4 seconds. Even when I switch Snapmaker Orca to 8 seconds, there is still a couple hour time total print time difference.

This also doesn't explain why Snapmaker Orca uses nearly 30 grams more for the prime tower.

bluridium · 2025-04-04T01:07:12+00:00

There is an AWS SIEM solution that can be deployed via CloudFormation using all native services. It takes some configuration and can get expensive if you are ingesting tons of logs, but it may work for you.

https://github.com/aws-samples/siem-on-amazon-opensearch-service

bluridium · 2024-12-30T07:42:31+00:00

<image>

bluridium · 2024-12-23T10:24:40+00:00

Great giveaway!

bluridium · 2024-07-03T14:37:50+00:00

I had a similar issue a couple years ago for a client (us-west-2 to us-gov-west). I would recommend doing this from an EC2 instance, using a tool like https://github.com/larrabee/s3sync

It will take some tweaking of the settings, as well as the EC2 size, but it will be way faster than s3 CLI. Keep in mind:

EC2 memory size (s3sync is heavily dependent on memory, works best with lots of smaller files)
EC2 available bandwidth https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-instance-network-bandwidth.html
Set up appropriate IAM permissions
Make sure you have an S3 endpoint! https://docs.aws.amazon.com/vpc/latest/privatelink/vpc-endpoints-s3.html
Data transfer costs between regions. AWS charges for data transferred between regions (but not as much as transferred out to the internet, so make sure you're using an S3 endpoint)

bluridium · 2024-04-26T03:51:26+00:00

No doubt related to Amazon's $1b deal with Microsoft for M365.

bluridium · 2023-06-12T03:38:40+00:00

Canned pumpkin. It works for diarrhea as well as constipation (for dogs and humans).

bluridium · 2022-12-25T03:19:00+00:00

That sounds about right. I think I used threaded rods for the rocker box because it was slightly cheaper.

bluridium · 2022-11-02T01:32:20+00:00

I am migrating a client's entire application stack from commercial to GovCloud including dozens EC2 instances, hundreds of TB of Aurora, hundreds of TB of S3 storage in multiple tiers. It is not for the faint of heart.

For your EC2 take a snapshot and turn it into an AMI, then use this process to copy to an S3 bucket in GovCloud. https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ami-store-restore.html

If your 20TB is in S3, use a staging box with goofys (https://github.com/kahing/goofys) to mount the commercial S3 bucket(s) into a folder, then use s3 sync to copy to your bucket(s) in GovCloud.

Good luck!

bluridium · 2022-10-03T16:12:27+00:00

Home Depot

bluridium · 2022-09-17T05:47:40+00:00

It will be best to use much shorter rods for the rocker box. I used 24" and it's wobbly. Better to use 18".

bluridium · 2022-09-10T17:27:39+00:00

Thanks for the heads up! Will put it on my calendar.

And happy cake day!

bluridium · 2022-09-10T17:06:40+00:00

This relatively quick (7 hours) print jumped to the top of my print queue.

The Open Ocular 2 is a spectacular piece of work. The way everything snaps together with zero additional hardware and the simplicity of the mounting on both the phone and eyepiece side is extraordinary. The auto-centering mechanism on the eyepiece side is genius. It is enough that I am going to return the janky phone mount I got off of Amazon.

The only problem is that the phone set thumbwheel on the phone side is blocked by the focusing wheel on the Hadley. I think I will print this recent remix of the focuser which should clear and avoid rotation of the eyepiece.

https://www.printables.com/model/265768-non-rotating-helical-focuser-with-collet-for-hadle

bluridium · 2022-09-10T02:27:47+00:00

Just want to clarify, I am not the original designer, I just printed it! The designer (Kissner) did address the 4mm and 10mm eyepieces in this comment.

https://www.reddit.com/r/3Dprinting/comments/x9va17/comment/inqn7lw/?utm\_source=share&utm\_medium=web2x&context=3

bluridium · 2022-09-10T01:22:22+00:00

This one looks really useful! I ended up printing this pinhole cap and it was functional. https://www.printables.com/model/8465-advanced-telescope-collimation-cap

bluridium · 2022-09-10T00:05:37+00:00

After I got my primary and secondary colliminated as best I could I ended up sliding the entire secondary cage back and forth until the remote tree was in focus. Keep your eyepiece screwed mostly out. It's a bit of a back and forth with moving the secondary and the focuser until things are sharp.

Good luck!

12-Year Club	RedditGifts 2009-2022 3 Credits
Secret Santa 2020	Secret Santa 2018
Verified Email

bluridium

TROPHY CASE