Difference between revisions of "MTS420 Progress"

From TinyOS Wiki
Jump to: navigation, search
m (Where to find the code: Code is up!)
m (Where to find the code: updated references)
Line 26: Line 26:
  
 
==Where to find the code==
 
==Where to find the code==
The code can all be found in the TinyOS-2.x-Contrib Sourceforge CVS Repository under the rincon folder: tinyos-2.x-contrib\rincon\tos\sensorboards\mts420.  The .sensor file contains a list of all the dependencies that are also needed.  More information and an example application will be included soon.
+
The code is located in the [http://tinyos.cvs.sourceforge.net/tinyos/ TinyOS Sourceforge CVS repository].  The \tinyos-2.x-contrib\rincon\tos\sensorboards\mts420\ directory contains the code that glues all the dependencies together.  The .sensor file contains a list of all the dependencies that are also needed.
 +
 
 +
A simple example is located in \tinyos-2.x-contrib\rincon\apps\tests\TestMts420Gps\It forwards NMEA GGA messages from the GPS over the radio where a mote running the base station app can receive the information. ''The NMEA parsing code is incomplete--users beware.''

Revision as of 13:31, 23 May 2008

Completed Work

Code Organization

The code for a sensorboard consists of multiple layers. This section describes how those layers are organized in the tos directory structure.

  • Independent Chip Code - The sensorboard will be an assembly of different chips. Some of those chips will be complicated enough to merit platform independent code and should be located in tos/chips/<chipname> directory.
  • Sensorboard Dependent Chip Code - Some chips will require code specific to the physical connections made on the sensorboard and the code should be located in tos/sensorboards/<boardname>/chips/<chipname> directory.
  • Platform Dependent Sensorboard Code - Some code will depend on the specific platform it is being connected to (for example, anything that uses buses controlled by the platform). That code should be located in tos/platforms/<platformname>/sensorboards/<boardname>/ and organized in a similar chips/<chipname> sub directory as appropriate.
  • Independent Helper Code - Code that can be written to be independent of the sensorboard should be added in an appropriate tos/lib/<name> directory.
  • Dependent Helper Code - Code that exposes useful features of the sensorboard and is specific to the sensorboard should be located in the tos/sensorboards/<boardname>/ directory and any appropriate sub directories if required.

MTS420CA/CB GPS

TODO

Remaining Work

  • Documentation and Code for all sensors except the GPS on the MTS420CA
  • Documentation for the GPS 420CA
  • Documentation for supporting code
  • Refining and Testing GPS Code
    • SiRF packet reception
    • Controlling GPS
    • Test Power (does GPS_ENA need to be high? what does GPS_PWR do?)
  • How To documentation
    • How to use the code
    • File List

Where to find the code

The code is located in the TinyOS Sourceforge CVS repository. The \tinyos-2.x-contrib\rincon\tos\sensorboards\mts420\ directory contains the code that glues all the dependencies together. The .sensor file contains a list of all the dependencies that are also needed.

A simple example is located in \tinyos-2.x-contrib\rincon\apps\tests\TestMts420Gps\. It forwards NMEA GGA messages from the GPS over the radio where a mote running the base station app can receive the information. The NMEA parsing code is incomplete--users beware.