Differences

This shows you the differences between two versions of the page.

--- android:track:trackstories [2014/02/21 19:44]
mikeclapp [Settings]
+++ android:track:trackstories [2014/03/28 00:29] (current)
mikeclapp [Identifying the machine at startup]
@@ Line 269: / Line 269: @@
 {{:android:track:smarttrack_-_settings-about.png?400|}}
+==== Identifying the machine at startup ====
+The key to deeper statistics and analysis is machine identification. Without some sort of identification the tracks are more difficult to analyze and don't as easily lend themselves to mobile analysis. We need to have the capability to edit the machine to tracker association in many places but perhaps the easiest place is at the tracker and machine itself.
+The simplest path is inputting nothing (pressing cancel) at the Vehicle selection window. All we can do in this case is log a unique identifier and attach the tracks to it.
+The second simplest path is picking a predefined machine the first time and confirming that vehicle choice at the start of every session. This is probably the desired first release behaviour.
+For a more dynamic environment where machine-tracker associations change frequently, implementing a bar code scanning function could be more desirable than picking from a list.
+The startup selection screen might look something like this:
+{{:android:track:startupmachineselection.png?300|}}
+The imagined flow is this:
+  - Start SmartTrack and background login occurs. Do we have to scan for new vehicles and download them here?
+  - Display the Vehicle selection. Pressing select assigns the machine in the combo box. Picking from the combo box displays the vehicle characteristics. Pressing Cancel bypasses machine assignment and then all we have is a tracker id.
+  - After vehicle selection SmartTrack needs to check with the server for configuration and/or configuration changes and load them.
+Other future options may include bar codes or RFID tags. RFID would be fairly unobtrusive to the user but dependent on mounting that I'm not sure we can rely on. Scanning requires user action in scanning the codes and also limits devices to those with cameras.
 ==== Information Flow & Requirements ====
 One of the themes of this system besides low friction to implement is giving each of the users something and getting some simple sort of data in return. It's not unlike a database where the collective small inputs of many people yield a result that is greater than the input required. The users/consumers are:

AGTEK R & D Wiki

User Tools

Site Tools

Differences

Page Tools