PSU Cover + Pi3 + 1 Channel Relay
I re-designed the PSU Cover to accommodate Raspberry Pi3 and 1 Channel Relay. You could find it here: https://www.thingiverse.com/thing:2524826
Re: PSU Cover + Pi3 + 1 Channel Relay
Looking at this tweet ( https://twitter.com/josefprusa/status/911279647719067649 ), this cover will be obsolete 😆
Looks like the new Prusa i3 MKX will have board which we can install Raspberry Pi (Pi Zero ?) on top of it. Plus, 5V extra for LED ?
Re: PSU Cover + Pi3 + 1 Channel Relay
That may be true, but what if you want a camera mount/look at your print that is connected to the rasberry pi? I can't seem to find a 15-pin wide to cable adapter. There's also the speed difference, after watching a few videos on Octoprint, there seems to be different hardware that works for managing a 3d printer without a PC. (Like the beefier BeagleBone.)
Personally, I'm a fan of a RJ45 connection vs wireless. The complaints I have about the other types of Octoprint hardware, is that they all use alot more power than a Raspberry Pi Zero W.. :X
I've also seen people combine the raspberry with a 7 inch touchscreen. 😯
War... War never changes.
Re: PSU Cover + Pi3 + 1 Channel Relay
Yes, I agree. I was reading somewhere that Pi Zero is not powerful enough to stream the video. For me, I don't know why I can't make mine working. So, I stick with Pi3.
Re: PSU Cover + Pi3 + 1 Channel Relay
OctoPi is a branch off of OctoPrinter, specifically designed to make OctoPrinter work on a Raspberry Pi.
mjpg-streamer is a command line project that utilizes the input_raspicam plugin to import data from the raspberry pi camera ribbon cable connector.
Looking further into this page:
https://www.raspberrypi.org/forums/viewtopic.php?f=43&t=45178
Rather interesting to read, it seems higher fps with better resolution images requires:
a) Tweaking C code from one or more github repositories.
b) You are supposed to go into the raspberry console, and statically compile source code. (Alternative with dynamic links via apt-get?)
c) Some rather involved knowledge is required of CentOS/Redhat. (ie; how to write custom services with locks to prevent duplicates, creating temp directory utilizing ram caching for image slices, monitoring/implementing different image libraries, correct program arguments)
d) Camera dependent software (Some are using usb camera, others use the raspberry 5MP camera IMX219 or OV5647.)
e) Some streamer methods saturate the raspberry (>100 MB/s network, or entire CPU processing).
Having read 82 posts regarding the matter, perhaps this is why there is no intended upgrade plan for a built in webcam 😛
I still would like to toy with the two different methods though... 
CuraEngine seems to be the library used to convert models into GCode on the fly. I can't say for certain what the difference is in performance. I only preordered the MK3 yesterday. Apparently Utilmaker hired the programmer who wrote the Cura engine. I read online that sometimes files take a "few seconds" to convert to GCode, and that some prefer to simply upload (the already sliced) GCode to OctoPi, so that important settings are not overwritten by Raspberry.
War... War never changes.