Programming/Deployment
From NESTFE Wiki
In order to deploy the nodes, I will need one person with me at RFS each day. As of now, I am not sure how long each day's work will be. Please put your information below and I will attempt to get a schedule worked out to help with deployment.
Name Email Cell Phone (mark if NOT cell phone) ----------------------------------------------------------------------- Jay Taneja taneja@eecs *censored* Prabal Dutta prabal@cs *censored* Bruno Sinopoli sinopoli@eecs *censored* Gilman Tolle get@eecs *censored* Mike Manzo mpm@eecs *censored* Tanya Roosta roosta@eecs *censored* Sukun Kim binetude@eecs *censored* Jaein Jeong jaein@eecs *censored* Songhwai Oh sho@eecs *censored* Phoebus Chen phoebusc@eecs *censored* Shawn Schaffert sms@eecs *censored* Travis Pynn travisp@eecs *censored* Bonnie Zhu bonniez@eecs *censored*
Contents |
Deployment Status
8/27: There are a whole lot of nodes in the field. Something like 600 or so.
8/17: Deployed more nodes to create a grid of 5 meter spacing. Total node count is now 61 (some nodes from original 16 were removed). The node ID numbers and orientation can be found in this text file. In the text file, the orientation is as follows:
(0,0) - SE corner of blue trapezoid Decreasing X - away from shack Increasing Y - further from EPA building (towards Bldg. 164) Units are done by nodes e.g. (3,0) is three nodes away from (0,0) There is a Tier 2 node adjacent to node 1063.
8/9: Deployed 16 nodes in a 4 x 4 grid at 10 meter spacing. Nodes do not have GPS information, but eventually will. The Node ID numbers are 1001-1016.
Pre-programming and Testing Procedure
1. Program USB EEPROM (FTDI)
NEW DIRECTIONS
Update: Step 1 of this process has been replaced by the "autoftdi.pl" script found on the nestfe-tier3-laptop-1 Debian linux laptop. It scripts the process of flashing the FTDI with the appropriate information. Step 2 (testing the Trio) still needs to be performed.
OLD DIRECTIONS
A Telos node shipped from a manufacturer cannot be programmed with TinyOS tools until it is branded as "Telos" in its USB EEPROM. In order to program USB EEPROM, we use 'MProg'. The following web page from Moteiv corporation explains the step except a few UCB details:
http://moteiv.com/community/Repair_USB_EEPROM_in_Windows
For NESTFE, we want manufacturer, product description and serial number prefix as follows:
Manufacturer: UC Berkeley Product Description: Telos (Rev B 2004-09-21) Serial Number Prefix (2 digits): UC
The most frequently used functions of 'MProg' is 'Scan' and 'Program' commands.
- 'Scan' shows how many motes are USB programmed or not.
- 'Program' programs the motes with the given parameters.
These are the steps to run 'MProg'
(1) Start 'MProg'.
- If this is the first time 'MProg' is started
- Create a new setting by selecting the menu item, File -> New.
- Set the device type as 'FT232BM', Manufacturer as 'UC Berkeley', Product Description as 'Telos (Rev B 2004-09-21), Serial Number prefix as 'UC'.
- Save the setting as any name, e.g. ucb.ept
- If this is not the first time 'MProg' is started, open an existing setting.
(2) Plug a mote and check the status of it by running a 'Scan' command. If it is a brand new device, 'MProg' will say that it has detected 1 unprogrammed device and 0 programmed device.
(3) Program EEPROM by running 'Program' command.
(4) Check the status of the mote by running a 'Scan' command again. It should report that it has detected 1 programmed device.
Sometimes, 'MProg' shows an error message that it cannot program a mote even though it was a blank device. In that case, try to unplug a mote and plug it again. If Windows asks for the driver for the device. Just press 'Ok' or 'Contitue'. After that you should be able to detect the mote as a programmed device.
(5) Type 'motelist' in your cygwin or linux console. If the mote is correctly programmed, it shows up.
2. Program a test app for checking radio and PIR sensor.
The page in the following links shows how to program 'TestTrio' app with a java tool. If you can successfully get a PIR sensing data over radio messages from a mote, the mote is in working condition.
http://today.cs.berkeley.edu/nestfe/index.php/Trio_Demo#Testing_a_Trio_mote
Assembly/Programming Procedure
1. Format flash.
CVS update tinyos-1.x/contrib/nestfe/nesc/apps/FormatFlash make telosb install green LED turns on when finished
2. Program node.
tinyos-1.x/contrib/nestfe/nesc/apps/SafeKraken make telosb install,<node id>
3. Download golden image.
run serial forwarder tinyos-1.x/contrib/nestfe/nesc/apps/SafeKraken make telosb redeluge,0
Steps 1-3 will be performed by a script. This script will be running on many machines in parallel. The script operates in an infinite loop, waiting for a Trio to be connected. Once connected, the script will run steps 1-3.
4. Affix label with node ID barcode to side of Trio. Label indicates that Trio is ready for deployment.
Deployment Procedure
(this will likely change as we figure out the best mechanics)
Two people – person 1 carries GPS backpack (all powered on), tablet PC (or PDA) running GPS-GUI, and duffel bag containing 12-15 Trios (with Velcro hooks) and bird spikes (with Velcro loops). Person 2 carries barcode scanner (connected to Person 1's PDA), barcode ruler, and duffel bag with 12-15 tripods. As the bags are emptied and nodes are deployed, the bags will be refilled.
As the two people arrive at each node location (approximately 15 meter spacing), they should perform the following procedure:
- Person 1 screws in Trio to tripod (given by Person 2).
- Person 2 scans grass height (from barcode ruler) using barcode scanner.
- Person 1 places Trio connected to tripod, making sure solar panel is facing south.
- Person 2 scans node ID using barcode scanner.
- Person 2 adjusts Trio node height to above grass and scans node height (from barcode ruler) using barcode scanner.
- Person 1 attaches bird spikes to top of Trio using Velcro (already on Trio and bird spikes).
Nucleus Mote Map
http://128.32.129.147/rfs/index.html
This link has the location data also.
