3DPrinting
3DPrinting is a place where makers of all skill levels and walks of life can learn about and discuss 3D printing and development of 3D printed parts and devices.
The r/functionalprint community is now located at: !functionalprint@kbin.social or !functionalprint@fedia.io
There are CAD communities available at: !cad@lemmy.world or !freecad@lemmy.ml
Rules
-
No bigotry - including racism, sexism, ableism, homophobia, transphobia, or xenophobia. Code of Conduct.
-
Be respectful, especially when disagreeing. Everyone should feel welcome here.
-
No porn (NSFW prints are acceptable but must be marked NSFW)
-
No Ads / Spamming / Guerrilla Marketing
-
Do not create links to reddit
-
If you see an issue please flag it
-
No guns
-
No injury gore posts
If you need an easy way to host pictures, https://catbox.moe/ may be an option. Be ethical about what you post and donate if you are able or use this a lot. It is just an individual hosting content, not a company. The image embedding syntax for Lemmy is 
Moderation policy: Light, mostly invisible
view the rest of the comments
That should all be fine, I'm pretty sure the cable in the Sprite pro upgrade kit terminates into jst connectors for the old style boards.
As for octoprint it will run with Klipper but I think it has trouble when trying to push speed, seems like most people recommend mainsail or fluid for the Klipper host.
Ah good to know. When the new Ender gets here it will probably inherit the Octoprint setup then. I'm slowly accepting that I'll need to upgrade the old mainboard to use Klipper and get the most out of the motors/etc. I just know that once I'm sitting and looking at the old board and extruder, I'm going to be wanting to turn them into a third machine... 🤦♂️
I highly recommend switching to fluidd or mainsail. They don't require any more CPU power than octoprint (possibly a bit less, actually). They are more modern and polished interfaces than octoprint.
Second this, I run mainsail for my voron and octoprint for my prusa, mainsail is just way nicer of an interface Imo, especially on mobile.
Do "more modern and polished UIs" make up for the loss of extensibility via plugins? Octoprint has bazillion of them, and I would take killer and productive ones like spool manager over subjectively better look
The architecture is a bit different than octoprint. Fluidd and mainsail are purely client side UI's, while Moonraker provides the server side API for them to connect to. So any additional functionality would need to integrate with Moonraker - not Fluidd/Mainsail.
A lot of functionality that is plugin based in octoprint is core to Moonraker and fluidd/mainsail. Things like cameras, mesh bed tools, gcode viewer, UI layout customization, power device control, etc are all included.
Spool manager is not something I've personally needed or used, but this would probably be a good option: https://github.com/Donkie/Spoolman
Yeah, that's what strikes me about Moonraker and its UIs: they seem more rigid and limiting than octoprint and its plugins ecosystem (I can spin one up in mere minutes to do pretty much anything), but those who love fluidd and mainsail them love them very much. I'd like to have someone explain to me why Moonraker is getting the lion share of the nerdier side of the community, it feels like I'm missing something obvious :)