The bridge experiment was done using Tenet software with
one additional hardware-dependent element 'SampleMDA400'.
This element was required to sample data through MDA400 vibration board.
You can download the Tenet software from the
ENL CVS
Motes will be tasked to reboot and re-start every 70minutes:
sampling will run for one hour, reboot, and 10minute break between every round.
Each mote will sample tri-axis (x, y, z) at 20Hz.
Sampling frequency: why 20Hz?
- MDA400 has sampling frequency range of 200Hz ~ 10kHz.
To go lower, we need to down-sample (by dropping samples)
- But unfortunately, based on my experience,
maximum possible sampling frequency for "continuous" sampling and transmission
without onset detection is (1-hop, single node):
- 75 Hz, single-axis
- 40 Hz, dual-axis
- 25 Hz, tri-axis
All application data will be logged into a file at stargate 121, to the CF-card.
And these files will be backed up to stargate 122 and 124 every hour, between every rounds.
When the stargates boot up, they will automatically run the Tenet stack (sf, router, transport).
Watch-dog script will be running to check whether the Tenet stack is running,
and reboot the stargate otherwise.
Stargate 121 will send out tasks to start all the motes.
After every round, the log-file will be backed up (copied) to stargate 122 and 123.
The file "/root/run_every_hour.log" at stargate 121 will show the progress of the application script.
Motes use 1-hop static routing to their cluster head (Base station).
A mote with id "xy" will have stargate "12x" as their static parent. (ex. 34's parent is 123)
Stargates use statically configure 2-hop routing with the stargate 121 as the center node.
Motes use stream-transport (SendSTR element in Tenet) to send packet to the application at stargate 121.
Stargates use UDP-encapsulation to forward mote packets between each other.