Difference between revisions of "Ideal mote"
(→Sensors) |
|||
| (One intermediate revision by the same user not shown) | |||
| Line 22: | Line 22: | ||
==Sensors== |
==Sensors== |
||
* |
* Stores sensor calibration data in NVRAM |
||
==Configuration management== |
|||
==Misc== |
|||
* Has a global unique ID. |
* Has a global unique ID. |
||
* Stores and reports capabilities data |
* Stores and reports the capabilities data: |
||
** MCU, Memory sizes |
** MCU, Memory sizes |
||
** |
** Attached sensors |
||
==Debugging and run time assurance== |
==Debugging and run time assurance== |
||
Latest revision as of 12:34, 10 November 2010
Here be dragons. No, wait... Here be ideas for the bestest mote evah...
But seriously, here we list features (and benefits) for the better sensor node (hardware). Should you have anything good to add, drop a line to Leo.Selavo. His email is at gmail.
Computation
- Multicore
- Has FPGA option
- Frequency throttling
- Core gating (similar to clock gating)
Communication
- SDR
- Supports backcast
- Supports option for in-system error correction, such as Reed Solomon.
Energy
- Zero consumption (plus epsilon)
- Modular harwesting
Sensors
- Stores sensor calibration data in NVRAM
Configuration management
- Has a global unique ID.
- Stores and reports the capabilities data:
- MCU, Memory sizes
- Attached sensors
Debugging and run time assurance
- Reports battery state, e.g. charge level
- Option for power consumption measurements on-demand
