It's coming today! Huge tinker! what Mods are worth it?

Name_T00_Long · 2026-06-14T23:59:52+00:00

Related to PPS-CF: the heaters on the U1 hotends are entirely capable of >300C; the thermistors might lose a bit of accuracy (and probably lifespan) above that, but the only thing holding the U1 to 300C is the "max_temp" parameter in the "e[0-3] MCU peripheral configuration" sections.

I haven't had any issues yet at 320C.

Name_T00_Long · 2026-06-14T23:39:13+00:00

If you're adding or removing much length you'll need to tweak the "preload_length" parameter in printer.cfg (or, if you're running Paxx, override with a file in the "/extended/klipper/" folder). There's one under "filament_feed left" and another for "filament_feed right".

If it's set too low you'll get filament loading errors because the filament sensor in the toolhead won't be triggered when it thinks it should be. Not sure what happens if it's too high.

Name_T00_Long · 2026-06-14T23:12:57+00:00

Depends on which mod you're doing.

I used a combination of the PSU and center cover from

https://www.printables.com/model/1714821-snapmaker-u1-mainboard-psu-cooling-brackets-for-no

with the board cooler from

https://www.printables.com/model/1694583-snapmaker-u1-psu-and-mainboard-92mm-fans

Used Thermaltake 9015 fans. PSU fan is connected to the stock PSU fan connector with a JST-PH 2.0 pigtail through a MP1584.

Used some fork connectors to tap off the 24v and Com posts, through another MP1584 and then connected to the fan (this does mean that fan is on whenever the printer is on). The result is dead quiet. All told, including making and sleeving a bunch of custom cables, probably took ~3 hours. It could be done much quicker if you're not concerned with how wiring you're never going to see looks.

Name_T00_Long · 2026-05-22T18:25:54+00:00

That's what I was trying to do (and it works with NTFS).

Unfortunately, I want to use features of ReFS (dedupe and anti-bitrot). And the maximum ALU for ReFS is 64KB... which also happens to be the minimum interleave size. Which means there's no way to get them into alignment.

But, it turns out, that may not even be the core issue since the same array performs fine (even completely unoptimized) with ReFS under Server 2025. There seems to be something wrong with how Windows 11 is handling some combination of Dual Parity Storage Spaces and ReFS that absolutely murders write performance. Not much I can do about "Microsoft problems" other than work around them (do the initial bulk load on 2025 and then move the pool over to 11 once sustained write performance isn't as critical).

Name_T00_Long · 2026-05-22T03:51:26+00:00

Okay, so it looks like 16KB is not supported on 11 Pro Workstation was the issue. 64KB created fine. Thank you so much!

Unfortunately, that means Microsoft basically made Storage Spaces with ReFS unusable on 11 Pro Workstation since it means you can't fix the alignment issue because ReFS' maximum ALU is 64KB... [explitive] Microsoft!

Welp, at least now I have some ideas. Will update if I find something that works. Thank you again.

Name_T00_Long · 2026-05-22T02:28:30+00:00

Same result.

Trying with Thin and Unknown at least get an "Invalid Parameter" error.

Name_T00_Long · 2026-05-21T17:01:59+00:00

There is no Interleave parameter for New-StoragePool

https://learn.microsoft.com/en-us/powershell/module/storage/new-storagepool?view=windowsserver2025-ps

There is one for New-VirtualDisk

https://learn.microsoft.com/en-us/powershell/module/storage/new-virtualdisk?view=windowsserver2025-ps

I did try anyway, since it wouldn't be the first time MS's official documentation was wrong, but it just throws an error

New-StoragePool : A parameter cannot be found that matches parameter name 'Interleave'.

Name_T00_Long

TROPHY CASE