Well… it seems to turn itself back on regardless of using 1 or 2 receivers. 1/2 hour later it turned on again. Using the receiver connected to pin5 does turn it on, but I have no idea why it turns itself back on after being turned off.
I’ll probably add Dom’s virtual suspend code soon enough and adapt it for other platforms
Sam
I’m still learning… what happens with a suspend code? From googling, all I can find is suspend to ram, and set a timer to turn back on, but I’m guessing you mean more than just that. Also… according to Raspberry Pi.org, it seems the GPU has power management implemented, just not the ARM. Not sure if that helps or not though.
It seems there are commercial adapters already out there. It looks like it has it’s own eeprom, storing learned codes from the remote.
Raspberry Pi B+ with RemotePi Board Plus 2015 - youtube.
Ok, from this particular point of view you’re right, but considering an attached HD, a powered hub for it, the electric consumption could raise quickly.
5 Million Rapsberry Pi have been sold.
Considering 2/3 of them are Pi 1 and B
Considering an average power of 5v*0.7A = 3.5 Watts = 0.0035 KW
1/3 are Pi 2
Average power of 5v*1.5 = 7.5 Watts = 0.0075 KW
if (theoretically) all of them were swithed ON all the time, this would mean:
[5.10^6 x 2/3 * 3.5.10^-3 ] + [5.10^6 x 1/3 * 7.5.10^-3 ] KW =
11667 + 12500 = 24167 KW = 24.2 MW
Just think about it…