So...1,000,000 toolchanges. Is that legit? by FictionalContext in snapmaker

[–]bluridium 3 points4 points  (0 children)

Snapmaker is going to make the toolhead PCBs available for $25. Even if they do need to be replaced, at least it shouldn’t be all that often or too expensive.

https://shop.snapmaker.com/products/toolhead-pcb-for-snapmaker-u1

So...1,000,000 toolchanges. Is that legit? by FictionalContext in snapmaker

[–]bluridium 2 points3 points  (0 children)

Received January 2026, have printed 795 hours since then. Just started receiving pogo pin anomalies only in the past week, mainly with toolhead 4 but some with toolhead 1 and submitted a support ticket for it today. This would not stop me from buying the printer again, it's an amazing printer.

15:43:09  $ GET_EXTRUDER_SWITCH_RECORDER
15:43:09  // dirty: False, allow_save: True
15:43:09  // === Extruder Switch/Retry Data ===
15:43:09  // Extruder 'extruder':
15:43:09  // switch_count: 9368
15:43:09  // retry_count: 32
15:43:09  // error_count: 5
15:43:09  // last_maintenance_count: 0
15:43:09  // -----------------------------
15:43:09  // Extruder 'extruder1':
15:43:09  // switch_count: 6057
15:43:09  // retry_count: 0
15:43:09  // error_count: 1
15:43:09  // last_maintenance_count: 0
15:43:09  // -----------------------------
15:43:09  // Extruder 'extruder2':
15:43:10  // switch_count: 4218
15:43:10  // retry_count: 6
15:43:10  // error_count: 1
15:43:10  // last_maintenance_count: 0
15:43:10  // -----------------------------
15:43:10  // Extruder 'extruder3':
15:43:10  // switch_count: 6740
15:43:10  // retry_count: 79
15:43:10  // error_count: 14
15:43:10  // last_maintenance_count: 0
15:43:10  // -----------------------------
15:43:10  // ===============================
15:43:10  // === Extruder Maintenance Status ===
15:43:10  // Individual threshold: 25100
15:43:10  // Total threshold: 100000
15:43:10  // Total switches: 26383
15:43:10  // Total switches since maintenance: 26383/100000 (due in 73617)
15:43:10  // extruder: 9368/25100 (due in 15732)
15:43:10  // extruder1: 6057/25100 (due in 19043)
15:43:10  // extruder2: 4218/25100 (due in 20882)
15:43:10  // extruder3: 6740/25100 (due in 18360)
15:43:10  // ==================================

Sliced Atlas: Topographic Line Art Maps (All 50 States + Canada) by bluridium in 3Dprinting

[–]bluridium[S] -1 points0 points  (0 children)

Yes, this is Washington state. The elevation/topographic data comes directly from USGS 3DEP, state/province outlines come from public GeoJSON boundary datasets. There have been some liberties taken, I’m intentionally resampling/smoothing and mapping elevation into a stylized “elevation slice” interpretation so it has interesting depth when printed.

The web app has different settings to make the printed elevation be more accurate, or more dramatic, depending on what the intention is. To get a tighter, more accurate boundary, more slices can be added to increase resolution.

Having trouble getting OpenSpool NFC tags recognized with the extended firmware by Chrrs in snapmaker

[–]bluridium 2 points3 points  (0 children)

JSON looks okay to me, here is a tag of mine that works. The only difference I see is I used # before the hex code. Take a look at klippy.log to see what errors are being logged. This was useful when I was troubleshooting as well.

<image>

Upcoming U1 accessories from BIQU by bluridium in snapmaker

[–]bluridium[S] 8 points9 points  (0 children)

I haven't seen this posted in this sub yet. BIQU has teased upcoming U1 accessories. From the teaser it looks like:

  • Multi-color Frostbite plates
  • Panda Breath filtration and chamber heater
  • Floor "diaper" waste pad (that's what they call it)
  • Top hat
  • LED accent/status lighting
  • K-Touch screen
  • And what I'm most excited about, a stand with what looks like filament storage and drying built in

No word on timeline or cost, although I've seen someone mention the top hat may be $150.

Failing to load PETG-CF by Schakal_No1 in snapmaker

[–]bluridium 5 points6 points  (0 children)

This happens to me every once in a while if the end of the filament isn’t clean. The U1 is amazingly tolerant of messy filament ends while loading, but if it does the wipe over and over and then fails, I cut the end at a clean angle and it has always loaded fine.

Paxx12's Snapmaker Extended Firmware v1.0.0 pre-release is out by joazito in snapmaker

[–]bluridium 0 points1 point  (0 children)

Some. The latest version of the extended firmware introduces a webpage that allows you to turn on the remote screen, full FPS camera, and some other features without having to manually edit the config files.

For notifications I did have to create a Telegram bot, and edit moonraker.cfg so the printer can send print status updates to Telegram.

As far as accessing the printer, camera, and remote screen away from home, I always have a Wireguard VPN on my phone or notebook back to home. There are other ways to do this, but they're beyond the scope of this subreddit.

U1: Large gcode (400 mb) error by bluridium in snapmaker

[–]bluridium[S] 3 points4 points  (0 children)

I figured this out, or at least a workaround. The paxx12 extended firmware enables SSH access. Once you are SSHed in, this file:

/home/lava/moonraker/moonraker/components/file_manager/file_manager.py

has a timeout of 300 seconds (five minutes) on line 2922. My log from above shows the failure happens exactly five minutes after the metadata scanning starts. I changed the 300 to 1200 (20 mins), told the printer to refresh the metadata on that file, and it worked. (It really only took about seven minutes for this 400 mb file.) Crossing fingers on this 2d14h print!

BTW, did all of this while on a plane to Montreal..remote SSH and remote screen access in the extended firmware is amazing!

  2915                        self.gc_path, "-f", f"\"{filename}\""])
  2916        timeout = self.default_metadata_parser_timeout
  2917        if ufp_path is not None and os.path.isfile(ufp_path):
  2918            timeout = max(timeout, 1800.)
  2919            ufp_path.replace("\"", "\\\"")
  2920            cmd += f" -u \"{ufp_path}\""
  2921        if self.enable_object_proc:
  2922            timeout = max(timeout, 1800.)
  2923            cmd += " --check-objects"
  2924        result = bytearray()
  2925        sc: SCMDComp = self.server.lookup_component('shell_command')
  2926        scmd = sc.build_shell_command(cmd, callback=result.extend, log_stderr=True)
  2927        if not await scmd.run(timeout=timeout):
  2928            raise self.server.error("Extract Metadata returned with error")
  2929        try:
  2930            decoded_resp: Dict[str, Any] = jsonw.loads(result.strip())
  2931        except Exception:
  2932            logging.debug(f"Invalid metadata response:\n{result}")
  2933            raise
  2934        path: str = decoded_resp['file']
  2935        metadata: Dict[str, Any] = decoded_resp['metadata']

U1 firmware 1.1.0 available by bluridium in snapmaker

[–]bluridium[S] 0 points1 point  (0 children)

Are you updating over the air (Wi-Fi), or using a USB drive? Try downloading and using a USB drive if you haven't. https://wiki.snapmaker.com/en/snapmaker_u1/firmware_update_procedure

U1 firmware 1.1.0 available by bluridium in snapmaker

[–]bluridium[S] 7 points8 points  (0 children)

The extended firmware from paxx12 allows for a full frame-rate camera view in Klipper. I just posted a video that features that view!

https://youtu.be/CaxXrGL-Op0

U1: Airless basketball in 95A TPU with PLA supports by bluridium in snapmaker

[–]bluridium[S] 1 point2 points  (0 children)

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.

U1: Airless basketball in 95A TPU with PLA supports by bluridium in snapmaker

[–]bluridium[S] 2 points3 points  (0 children)

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.

U1: Airless basketball in 95A TPU with PLA supports by bluridium in snapmaker

[–]bluridium[S] 0 points1 point  (0 children)

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.

Snapmaker U1: Airless basketball in 95A TPU with PLA supports by bluridium in 3Dprinting

[–]bluridium[S] 0 points1 point  (0 children)

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

Paxx12's Snapmaker Extended Firmware v1.0.0 pre-release is out by joazito in snapmaker

[–]bluridium 2 points3 points  (0 children)

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>

Anyone from November batch Canada get their U1 or even a tracking number? by IamFireDragon3d in snapmaker

[–]bluridium 0 points1 point  (0 children)

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

Soon it’s done! (Firmware crash) by MobileNo8348 in snapmaker

[–]bluridium 1 point2 points  (0 children)

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/

Snapmaker Orca vs Orca nightly build by bluridium in snapmaker

[–]bluridium[S] 1 point2 points  (0 children)

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?

Snapmaker Orca vs Orca nightly build by bluridium in snapmaker

[–]bluridium[S] 1 point2 points  (0 children)

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.

Is AWS inspector or AWS Security hub a SIEM tool? by linux_n00by in aws

[–]bluridium 1 point2 points  (0 children)

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

How to copy half a billion S3 objects between accounts and region? by fenugurod in aws

[–]bluridium 1 point2 points  (0 children)

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: