This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
content:meshextender:prototyping_on_mk808 [23/04/2013 21:47] Paul Gardner-Stephen [Comparing Power Consumption of the various devices] |
content:meshextender:prototyping_on_mk808 [14/05/2013 23:18] (current) |
||
---|---|---|---|
Line 12: | Line 12: | ||
We are considering a few options for this, which are described below. | We are considering a few options for this, which are described below. | ||
+ | Most of these are centred around the low-cost low-power Android stick-PCs manufactured by Tronsmart (http:// | ||
===== Comparing Power Consumption of the various devices ===== | ===== Comparing Power Consumption of the various devices ===== | ||
- | * MK808B (idle, HDMI display connected and on, Serval Mesh not installed, no serial adapter plugged in): averaging 0.187A - 0.198A @ 4.995V | + | ==== Summary ==== |
- | * MK808B (idle, HDMI display disconnected, | + | |
- | * MK808B (idle, HDMI display disconnected, | + | |
- | * MK808B (idle, HDMI display disconnected, | + | |
- | * MK808B (idle, HDMI display disconnected, | + | |
- | * MK808B (idle, HDMI display disconnected, | + | |
+ | An MK808B will use about the same amount of power as the TP-LINK WR703N platform we are currently using, but with much, much better performance. | ||
+ | Total power budget will be between 1.0W and 1.3W, plus the power to run servald. | ||
+ | An aggregate average consumption of 1.3W is probably reasonable. | ||
+ | |||
+ | Assuming an 80% efficient power supply, and 24 hours of endurance, this indicates that we will need a 40Wh battery. | ||
+ | |||
+ | To allow for charging a typical phone, we should allow another 10Wh, for a total of 50Wh for a system that can endure and support a smart-phone for 24 hours. | ||
+ | |||
+ | We need to test the assumption about servald energy consumtion to have confidence in these figures. | ||
+ | |||
+ | What is pleasing is that the MK808B does NOT use the 1.1W - 2.2W when idle that some sources on the internet have claimed. | ||
+ | |||
+ | === Processing platform === | ||
+ | |||
+ | The TP-LINK WR703N + Wi-Fi AP+ad-hoc + USB hub + USB memory stick uses about 1W to run servald, minus USB serial adapter and RFD900 radio. | ||
+ | |||
+ | The MK808B, not running servald, and Wi-Fi in AP mode only (we don't know how to do simultaneous ad-hoc + AP uses on it) uses about 0.75W, less than the WR703N. | ||
+ | |||
+ | The MK802ii uses about 1W to do the same job as the MK808B, which is more than the MK808B uses. So the MK802ii is out on the basis of inferior power consumption and performance compared with the MK808B. | ||
+ | |||
+ | The MK808B, apart from the lack of simultaneous AP+ad-hoc Wi-Fi looks like the clear winner at this stage, provided that servald doesn' | ||
+ | |||
+ | === USB/Serial adapters === | ||
+ | |||
+ | The CP210x adapter uses about 0.14W, while the FTDI adapter cable uses about 0.12W. However, the cable is too large for the slight power saving that is offers. | ||
+ | |||
+ | === RFD900 Radio idle consumption === | ||
+ | |||
+ | The RFD900 adds between about 0.04W and 0.3W when operating at a TX power of 100mW. | ||
+ | |||
+ | ==== Raw Measurements ==== | ||
+ | * MK808B (idle, Wi-Fi client mode, HDMI display connected and on, Serval Mesh not installed, no serial adapter plugged in): averaging 0.187A - 0.198A @ 4.995V = 0.94W - 0.99W | ||
+ | * MK808B (idle, Wi-Fi client mode, HDMI display disconnected, | ||
+ | * MK808B (idle, Wi-Fi client mode, HDMI display disconnected, | ||
+ | * MK808B (idle, Wi-Fi AP mode, HDMI display connected and on, Serval Mesh not installed, no serial adapter plugged in): averaging 0.187A - 0.201A @ 4.995V = 0.94W - 1.01W | ||
+ | * MK808B (idle, Wi-Fi AP mode, HDMI display disconnected, | ||
+ | * MK808B (idle, Wi-Fi off, HDMI display connected and on, Serval Mesh not installed, no serial adapter plugged in): averaging 0.143A - 0.144A @ 4.995V = 0.71W - 0.72W | ||
+ | * MK808B (idle, Wi-Fi off, HDMI display disconnected, | ||
+ | * MK808B (idle, Wi-Fi client mode, HDMI display disconnected, | ||
+ | * MK808B (idle, Wi-Fi client mode, HDMI display disconnected, | ||
+ | * MK808B (idle, Wi-Fi client mode, HDMI display disconnected, | ||
+ | * MK808B (idle, Wi-Fi client mode, HDMI display disconnected, | ||
+ | * FTDI cable + RFD900 (TX @ 100mW) with link but no traffic: 0.048A - 0.09A @ 4.995V = 0.24W - 0.45W | ||
+ | * FTDI cable + RFD900 (TX @ 250mW) with link but no traffic: 0.037A - 0.12A @ 4.995V = 0.19W - 0.60W (but peaks are likely reduced due to sampling issues in our test environment). | ||
+ | * CP210x cable + RFD900 (TX @ 100mW) with link but no traffic: 0.066A - 0.1A @ 4.995V = 0.33W - 0.50W | ||
+ | * MK802ii (idle, HDMI display connected, Serval Mesh not installed): 0.21A - 0.30A @ 4.995V = 1.05W - 1.50W | ||
+ | * MK802ii (idle, HDMI display disconnected, | ||
+ | * TP-LINK WR703N (idle, no USB hub, memory stick, USB serial adaptor or RFD900 radio): 0.099A - 0.110A @ 4.995V = 0.50W - 0.55W | ||
+ | * TP-LINK WR703N (idle, Wi-Fi in simulatenous ad-hoc & AP mode, USB hub, memory stick, running servald, no USB serial adaptor or RFD900 radio): 0.191A - 0.21A @ 4.995V = 0.96W - 1.05W | ||
====== MK808B Android Stick PC + RFD900 Radio ====== | ====== MK808B Android Stick PC + RFD900 Radio ====== | ||