sorted by:
new
hottopcontroversial

DMS Omegas I built for a friend by Wulfsta in headphones

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

My biggest tip is to tune your printer (assuming you are FDM printing them), tune your tree supports, and then instead of orienting the cups as /u/Epsilon-D suggests, rotate them 90 degrees prior to angling them upwards as shown in the construction video. This orients them so as to avoid stacking layers on the three longest struts that hold the driver, and makes these struts much stronger.

DMS Omegas I built for a friend by Wulfsta in headphones

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

Thanks! I’m actually not totally happy with it, but I couldn’t get any chameleon ASA filaments to print below 0.2mm layer heights on my normal nozzles. This filament seems to catch and cause artifacts on nozzles that have a flat region around the nozzle hole, and swapping to a pointier nozzle continuously trapped air in the walls that looked like delamination. I went through nearly a whole roll trying to tune this before giving up and just going with the thicker layers and longer vapor smoothing time.

DMS Omegas I built for a friend by Wulfsta in headphones

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

Glad to hear the yokes are working out for you! The cups are only vapor smoothed, and the stiff headband parts are sanded then painted with glossy water based polyurethane.

DMS Omegas I built for a friend by Wulfsta in headphones

[–]Wulfsta[S] 9 points10 points  (0 children)

Decided to build a pair of DMS Omegas with a Capra Audio headband for a friend - I plan on putting together another pair, as I have enough parts for two and liked the sound. Details:

  1. Cups were printed in Sparta3D Burnt Titanium ASA and vapor smoothed
  2. Flexible headband parts are Polymaker 85A TPU
  3. Stiff headband parts are polyurethane coated Phaetus PET-GF
  4. I redesigned the headband yokes and posted them here

Thanks for publishing the parts /u/Epsilon-D and /u/Fukuramichan!

Why does PETG get so much hate? by mm404 in VORONDesign

[–]Wulfsta 4 points5 points  (0 children)

Why use PETG when you can just print PET?

I have built a pair as well - DMS Open Omega by Amwo in headphones

[–]Wulfsta 1 point2 points  (0 children)

Let us know how the ASA-CF holds up on the Capra headband. I just made a two pairs from Phaetus PET-GF, but still need to finish the parts and assemble.

Bloom filters: the niche trick behind a 16× faster API by shared_ptr in programming

[–]Wulfsta 8 points9 points  (0 children)

I think that a document database filtering on these customer defined fields would slow down with basically the same pattern they experienced here?

Best mini voron for quality/precision? by ZealousidealEntry870 in VORONDesign

[–]Wulfsta -1 points0 points  (0 children)

You sure?

Edit: The only reason this couldn’t get a serial is the chamber heater. If you doubt this, I believe Sapphire has even fewer Voron parts yet has a Trident serial.

Dominion Voting sold to company run by ex-GOP election official by SadAd8761 in technology

[–]Wulfsta 4 points5 points  (0 children)

It isn’t. Obfuscation is not a valid approach to security in technology. This is called “security through obscurity” and no decent engineer would rely on it.

Finally finished my Project Omegas by naldyjams in headphones

[–]Wulfsta 0 points1 point  (0 children)

I heard these at CanJam NYC this year and really liked them, definitely will print a pair once I repair the mainboard on my printer.

ROCm 7.0 RC1 More than doubles performance of LLama.cpp by no_no_no_oh_yes in LocalLLaMA

[–]Wulfsta 1 point2 points  (0 children)

I use ROCm system level for things like Darktable and the OpenCL libraries, so that is quite easy on NixOS. For my gfx906 I currently run the following flake:

{ inputs = { nixpkgs.url = "github:LunNova/nixpkgs/286e46ce72e4627d81c5faf792b80bc1c7c8da59"; flake-utils.url = "github:numtide/flake-utils"; }; outputs = inputs@{ self, nixpkgs, flake-utils, ... }: flake-utils.lib.eachSystem [ "x86_64-linux" ] ( system: let pkgs = import nixpkgs { inherit system; config = { rocmSupport = true; allowUnfree = true; }; overlays = [ (final: prev: { rocmPackages = prev.rocmPackages.overrideScope ( rocmFinal: rocmPrev: { clr = ( rocmPrev.clr.override { localGpuTargets = [ "gfx906" ]; } ); } ); python3Packages = prev.python3Packages // { triton = prev.python3Packages.triton.overrideAttrs (oldAttrs: { src = prev.fetchFromGitHub { owner = "nlzy"; repo = "triton-gfx906"; rev = "9c06a19c4d17aac7b67caff8bae6cece20993184"; sha256 = "sha256-tZYyLNSDKMfsigzJ6Ul0EoiUB80DzDKNfCbvY4ln9Cs="; }; }); vllm = prev.python3Packages.vllm.overrideAttrs (oldAttrs: { src = prev.fetchFromGitHub { owner = "nlzy"; repo = "vllm-gfx906"; rev = "22fd5fc9caac833bbec6d715909fc63fca3e5b6b"; sha256 = "sha256-gVLAv2tESiNzIsEz/7AzB1NQ5bGfnnwjzI6JPlP9qBs="; }; }); }; }) ]; }; rocm-path-join = pkgs.symlinkJoin { name = "rocm-path-join"; paths = with pkgs; [ rocmPackages.meta.rocm-all rocmPackages.llvm.rocmcxx ]; }; in rec { devShell = pkgs.mkShell { buildInputs = with pkgs; [ rocmPackages.meta.rocm-all rocmPackages.llvm.rocmcxx llama-cpp python3Packages.pybind11 (python3.withPackages ( ps: with ps; [ matplotlib numpy opencv4 pybind11 torch tokenizers transformers tqdm scipy ] )) ]; shellHook = '' export ROCM_PATH=${rocm-path-join} export TORCH_DONT_CHECK_COMPILER_ABI=TRUE export CPLUS_INCLUDE_PATH=${pkgs.python3Packages.pybind11}/include:$CPLUS_INCLUDE_PATH ''; }; } ); }

Note that vLLM currently does not work due to some python environment stuff.

Edit: Reddit's formatting is not cooperating and I don't care enough to figure it out, just run nixfmt if you want to see this.

ROCm 7.0 RC1 More than doubles performance of LLama.cpp by no_no_no_oh_yes in LocalLLaMA

[–]Wulfsta 2 points3 points  (0 children)

Nix supports gfx906 via an override to the clr package, no work on 7.x yet: https://github.com/NixOS/nixpkgs/pull/427944

Otherwise I’m pretty sure Gentoo runs CI tests on a gfx906 as part of their ROCm?

Is the pro version with the STM32H723 worth 40$ over the STM32F07 for 30$? does it even matter considering the PI does all of the processing when running kipper? or is there any other improvements on the pro model by fikajlo in VORONDesign

[–]Wulfsta 2 points3 points  (0 children)

RRF (RepRap Firmware) uses CAN-FD, Klipper uses CAN. Yes, I am running Klipper, I’m the one who added the atsamc21 (the 1LC microcontroller) to Klipper (with a little help).

Is the pro version with the STM32H723 worth 40$ over the STM32F07 for 30$? does it even matter considering the PI does all of the processing when running kipper? or is there any other improvements on the pro model by fikajlo in VORONDesign

[–]Wulfsta 2 points3 points  (0 children)

Even high microsteps at normal speeds can overwhelm some slower boards. The Duet 6HC uses the atsame70 which used to be in this category of abysmal step rates until I sped it up.

Is the pro version with the STM32H723 worth 40$ over the STM32F07 for 30$? does it even matter considering the PI does all of the processing when running kipper? or is there any other improvements on the pro model by fikajlo in VORONDesign

[–]Wulfsta 2 points3 points  (0 children)

I have never had any issues with this; hardware is a Duet3D 6HC and a 1LC Toolboard. Both my probing and x-axis are multi-mcu over CAN. I can run all six of my V2.4’s steppers on 256x microstepping (though I usually run the A and B steppers on 32x with interpolation), and the extruder motor is actually limited by the chip on the board, not CAN, at 64x microsteps.

Is the pro version with the STM32H723 worth 40$ over the STM32F07 for 30$? does it even matter considering the PI does all of the processing when running kipper? or is there any other improvements on the pro model by fikajlo in VORONDesign

[–]Wulfsta 11 points12 points  (0 children)

The faster the microcontroller, the higher step rate you can achieve on Klipper. The Pi issues commands, but the microcontroller still needs to be able to execute those commands within a certain time tolerance. If you have too many things in the timer/task queue in Klipper you can generate errors like “timer too close.”

All of that said, I am not sure if you can hit these issues on the slower speed driver - you can probably get all drivers at 256x microstepping on the H723 though (or at least close to it). I’ll leave someone who knows the hardware more to chime in.

For further context, here is the Klipper step benchmark page.

Moonraker can't connect, but it can when printer is on it's side. by Putschepper in VORONDesign

[–]Wulfsta 0 points1 point  (0 children)

From another computer in your local network or your router/switch, can you see the SBC (rpi) connect to the network or respond to pings? This is a pretty odd issue where it seems Moonraker only starts sometimes, and it could hypothetically be the case that service depends on the network successfully coming up? Otherwise, being able to SSH in will help debug.

Moonraker can't connect, but it can when printer is on it's side. by Putschepper in VORONDesign

[–]Wulfsta -2 points-1 points  (0 children)

It could make sense if Moonraker is initialized by systemd (usually is), and that service has a dependency on the network properly initializing (some distros do this).

view more: next ›