My work flow changed from using one printer to using 8 of them. Octoprint is great but I haven’t taken the time or expense to set so many up since each would need their own pi. They are hard to find these days for a reasonably price. It was great when I did everything off the one printer though, I used an aftermarket runout sensor for filament on the gpio pins of the pi. I also kept track of my filament usage, used the webcam for monitoring from my house to the garage, and arc welder plugin to improve some of the prints. I am still a supporter of the program but I now just organize my SD cards neatly and manually sync them all with updated files. If my operation was bigger I would probably organize a networked solution like octoprint though.
grepLeigh|3 years ago
If your operation expands and you want to chat about wrangling networked printer management software, shoot me an email leigh@printnanny.ai. I want to make it dead-simple to manage 10+ printers running a menagerie of software (OctoPrint, Moonraker/Mainsail) and firmwares (Marlin/Klipper). Happy to trade notes!
Ancapistani|3 years ago
oynqr|3 years ago
grepLeigh|3 years ago
There are a lot of small papercuts, like OctoPrint using `vcgencmd` to measure CPU throttling. `vcgencmd` is part of Raspberry Pi's userland. Not a big deal (aliased to another util). I've also added WebRTC-based streaming to my build.
The recommended way to use OctoPrint is the OctoPi image, which is based on Raspbian / Raspberry Pi OS. The OctoPi image includes extras like haproxy and mjpg streamer for HTTP-based JPEG frame stream. If you end up baking a RockPi image, here's the OctoPi root file system for reference: https://github.com/guysoft/OctoPi/tree/devel/src/modules/oct...
stirfish|3 years ago
sitzkrieg|3 years ago
at this point the mere thought of setting up a sbc that isnt a raspberry pi is job security and frankly im not sure why. its not like the rasberry pi 1 days
sgtnoodle|3 years ago