Observer Nodes: Difference between revisions
No edit summary |
No edit summary |
||
| Line 8: | Line 8: | ||
{| | {| | ||
|The custom add-on card connected to the Raspberry Pi 3 embeds a power and latency profiling unit, as well as a GPIO tracing unit. The power profiling unit captures voltage and current using a 125 kHz simultaneous-sampling 12-bit current and voltage | |The custom add-on card connected to the Raspberry Pi 3 embeds a power and latency profiling unit, as well as a GPIO tracing unit. The power profiling unit captures voltage and current using a 125 kHz simultaneous-sampling 12-bit current and voltage analog-to-digital converter. | ||
The GPIO tracing and latency profiling units allow simultaneous tracing and actuation of up to 8 GPIO pins per target platform. Observer nodes equipped with a GPS unit can generate precise timestamps for externally triggered events. Nodes without direct GPS connectivity can synchronize to the rest of the network using NTP with a typical accuracy well below 10μs. Target nodes can be individually powered on/off in software, hence allowing to control the network density and to emulate node failures (e.g., due to an early battery depletion) by software. | The GPIO tracing and latency profiling units allow simultaneous tracing and actuation of up to 8 GPIO pins per target platform. Observer nodes equipped with a GPS unit can generate precise timestamps for externally triggered events. Nodes without direct GPS connectivity can synchronize to the rest of the network using NTP with a typical accuracy well below 10μs. Target nodes can be individually powered on/off in software, hence allowing to control the network density and to emulate node failures (e.g., due to an early battery depletion) by software. | ||
|[[File:empty.png|left|275px]] | |[[File:empty.png|left|275px]] | ||
Revision as of 11:00, 10 November 2019
Under construction.



