====== TrackReader 2014 ======

TrackReader 2014 is a new pass at reading dedicated GPS dataloggers like the Wintec G-Ray. There is an existing program written for the PC but this is new look that takes into account mobile devices, better connectivity, and the more advanced state of the AGTEK Access Server.


==== Device Differences ====

The 201 and 202 G-Rays are second and third generation devices respectively. The main differences are:
 
  * The 202 contains a motion sensor which very effectively prolongs battery life and minimizes useless points
  * The 202 has greater internal memory (260,000 points) and has the ability to add a mini-SD card for greater storage. 
    * Unfortunately use of the mini-SD card appears to create a situation where the 202 cannot be read or configured via Bluetooth. 






The G-Ray (201 & 202) or equivalent is the lowest tier of tracking for us and provide a delayed source of tracks. Besides being a delayed source of tracks it also has the following limitations:

  * Relatively slow Bluetooth reading




Links to configuration details [[http://wiki.openstreetmap.org/wiki/Wintec|http://wiki.openstreetmap.org/wiki/Wintec]]

Wintec communications{{:android:trackreader:wbt201_t.pdf|}}

===== TrackReader for Android =====

Requirements

  * Uses Bluetooth for device connections. Possible multiple Bluetooth connections to speed G-Ray processing
  * Upload tracks to Access
  * Tag tracks with the project and vehicle
  * Erase tracks that have been successfully uploaded (user initiated)
  * Configure G-Rays. Out of the box they are not setup correctly for us
    * Identify and tag G-Rays uniquely. Perhaps by bluetooth MAC
    * Use with barcodes?


==== Proposed Flow ====

  - Start Program
  - Login (not keyed but for identifying upload destination)
  - Identify all visible G-Rays (need rescan for when I forget to turn one on). If we can, select them all and start the download for each (interface of tabs/trees, lists)
  - Upon download finish, tag the desired project and machine association. The likely case is that all G-Rays are on the same project. This could also be where we could pick from a list of known machines or scan the machine from a barcode.
  - After sending and server acknowledgement, ask if they want to erase the G-Ray.
  - Exit by pressing back and confirming exit.