Use in deployment
From CSL Wiki
Contents |
Two Modes
There is a "regular" mode (ar.run / ar-sink.run) and "flood only" mode (ar-floodonly.run / ar-sink-floodonly.run). The difference between the two is that the flood only version is simpler; has less processing overhead and works better in low-connectivity situations. The "regular" version provides additional features such as multi-hop IP routing. When in doubt, it may be best to start off with flood-only and later test the other.
Laptop Configuration
Run the ar-sink-floodonly.run file on your laptop (or, ar-sink.run if not flooding mode). This enables your laptop to participate in the network and collect information about it.
- bugs:
- visualizer in flood mode doesnt seem to show both directions of connectivity
- visualizer should use locacation data
- netrec should run in special gateway mode
Viewing Connectivity
You can see the complete connectivity from the laptop. If you have the ar-sink code running on your laptop, you can use:
emview -a localhost
to view data collected via flooding. Use
emview -b wlan0
to view data collected directly from one-hop neighbors. This does not require a full emstar build on the laptop, but will only work single-hop and is more costly in terms of bandwidth.
Issing Commands
- rbsh.
rbsh -b <interface> to broadcast to an IP interface rbsh -U flood to broadcast to all nodes via flooding
emview -a localhost
will display data from flooding
emview -b wlan0
will display any data it sees 1-hop away
- telnet to 10.1.0.nodeid will sometimes work multihop (if mhsync trees are working OK)
* problems when reclustering going on, loss of connectivity
