Check out my first novel, midnight's simulacra!

MO-RA3: Difference between revisions

From dankwiki
No edit summary
Line 40: Line 40:
==Wiring==
==Wiring==


Desiring to source the most efficient power possible, I'll run a lengthy PCIe 6-pin cable out the back of my machine, capable of carrying at least 75W on its three 12V pins (6.24A). I'll then use a trivial adapter to take that to SATA or Molex, and thus be able to power nine PF-14s on the front, and nine NF-A14s on the back. I do not intend to put any pumps on the MO-RA3, as I already have three D5s in my workstation. My longest PCIe cables are 75cm long, with a 30cm PCIe-to-Molex adapter.
Desiring to source the most efficient power possible, I'll run a lengthy PCIe 6-pin cable out the back of my machine, capable of carrying at least 75W on its three 12V pins (6.24A). I'll then use a trivial adapter to take that to SATA or Molex, and thus be able to power nine PF-14s on the front, and nine NF-A14s on the back. I do not intend to put any pumps on the MO-RA3, as I already have three D5s in my workstation. My longest PCIe cables are 75cm long, with a 30cm PCIe-to-Molex adapter. This means I can't use the MO-RA3 more than about a meter away from my workstation. If I wanted to run it three meters away, I'd need to use external power (and cut longer tubes).
 
I'll need to run two tubes out to the MO-RA3, but beyond coolant and power, what is necessary? The RGB and PWM of fans must be managed. If I have any temperature or flow sensors on the MO-RA3, they'll need hookups. It ought be possible, however, to control all this from a device local to the MO-RA3. Many people use Aquacomputer products such as the [https://shop.aquacomputer.de/product_info.php?products_id=3420 Splitty] in this role, and run data over a USB or Aquabus cable. I'd instead like to use a SBC with 2.4GHz 802.11n. I will likely break the shield off a [[CODI6]] to get the PWM+RGB headers.