This shows you the differences between two versions of the page.
Both sides previous revision Previous revision | |||
android:trackreader:trackreaderstories [2014/05/06 19:37] mikeclapp [Device Differences] |
android:trackreader:trackreaderstories [2014/05/09 21:35] (current) mikeclapp [Device Differences] |
||
---|---|---|---|
Line 27: | Line 27: | ||
Wintec communications{{:android:trackreader:wbt201_t.pdf|}} | 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. | ||
+ | |||
+ | |||
+ | |||
+ | |||