Differences

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

--- android:tracker:trackerstories [2015/07/16 23:52]
mikeclapp [Story 4]
+++ android:tracker:trackerstories [2018/08/09 22:59] (current)
mikeclapp [Story 6 SimpleTrack Simplification]
@@ Line 93: / Line 93: @@
 ===== Story 5 =====
-This story is a combination of SimpleTrack and the Trackserver and SimpleTrack may even be spun off as a differently named app variation to distinguish between AGTEK distributed and Store distributed.
+  * Remote configuration
+  * Telemetry statistics
+  * Event Logs
+A small story based on the first out-of-state permanently mounted (powered) sensors. Because these sensors have very little AGTEK interaction there's a desire to control and view more about the sensors programatically.
+=== Remote Configuration ===
+Previous installations were battery constrained and getting to the end of the third day was sometimes a challenge. Powering the sensor allows removing some of the compromises of the battery power. One such compromise was the upload frequency and it is sometime desirable to update faster than 5 minutes. We've added features like updating whenever the cycle line is crossed but setting the upload frequency faster and remotely is another. Along those lines being able to change/fix settings upon server contact.
+Configuration items we should be able to set remotely are:
+  * Update Frequency - And allow for a faster frequency than 5 minutes.
+  * Motion Timeout - Allow change of timeout, disabling entirely, sensitivity (new, how do we represent this?)
+  * Automatic Start - Off/On
+  * **MJA - How to edit, in TM? Assume trigger off of vehicle and associated tracker.**
+  * Logging?
+  * **MJA - Part of configuration. One time checkbox, causes ST to upload. HOW? Send to email?**
+  * **MJA - Need to disable vehicles from TM. In edit vehicle. Prosed screen next.**
+  * {{:android:track:activevehicleproposal.png?200|}}
+=== Telemetry ===
+Items I can think of adding to the tracking are:
+  * Powered Yes/No
+  * Charging State
+  * Motion Sensor State (are we moving/Paused)
+  * **MJA - Proposal of viewing**
+  * {{:android:track:telemetryproposal.png?200|}}
+=== Logging ===
+Not being on site and having equipment moving means that figuring out why we're getting an error needs more information provided. For example we've had one scraper on Rummel SC1017 that has showed a "Paused" State on data collection while all the other equipment has been working fine. It has also had intermittent uploads where it will regularly upload and then not communicate for thirty minutes. A log of the state that is accessible remotely when it does start talking again might be helpful. There are also error codes we get on the main SimpleTrack screen that could probably be pushed further back into the interface if we could get them remotely. Reading them on screen and capturing them on site is not really practical and is better suited to be viewed here at AGTEK for problem diagnosis.
+===== Story 6  SimpleTrack Simplification =====
+SimpleTrack started as a self-reporting G-ray replacement and evolved into a much more capable and cost-effective device than I had imagined. Over time it's acquired some additional complexity to add capability beyond being on a box on the roof and I believe we need to simplify what's there and split the functionality off into it's own application like truck tracking.
+Things like load counts designed for human consumption aren't appropriate for box on the roof.
+==== Story 6 notes applicable as of SimpleTrack 1.28 8-9-2018 ====
+The UK experiment found two inexpensive phones they purchased to not have unique serial numbers. The 1.28 version gives the option of using the IMEI number instead. The default is still to use the shorter, more readable serial number but this gives the option to switch. The serial number "0123456789ABCDEF" has also been blacklisted and when encountered the default will go to IMEI instead. In the odd case that an IMEI doesn't exist with a blacklisted serial number, the system will generate a unique AG###### number that is persistent as long as the program is not uninstalled. The simpletrack bug # is 36.
+===== Story 7  Truck Tracking =====
+Truck tracker constraints
+  * Trucks are often for hire so using a box on the roof isn't optimal. You might not get it back
+  * The phones in trucker's pockets are of mixed operating systems. Accommodating background operations in IOS is one of the technical challenges
+  * Since the truck driver isn't an employee there's a need to avoid the conventional userid/password login
+  * Trucks carry varied loads throughout the day. Tagging the load means there's some sort of user interface required that's probably different than SimpleTrack.
+  * Reporting every 5 minutes is fine for on-site machinery but trucks have varying timeliness requirements. For example, knowing where a truck is in nearly real-time when approaching the job site or hot plant allows the foreman to make tactical adjustments based on his distance.
-SimpleTrack is great if you have employees but in some cases like trucks, the operators are independents. For the most part SimpleTrack functions correctly for even this but because a driver doesn't always work for the company and may even work for several companies there's an idea of creating an App for the Google Play and Itunes store.
-The current implementation uses our standard login/password implementation but with these remote/non employee it would be nice to have a way of giving that user a code that would serve as login/password and potentially route the tracks to the correct project as well. The difficulty is in coming up with a reasonable in length/security/ and uniqueness since this potentially could originate from any company on the server.

AGTEK R & D Wiki

User Tools

Site Tools

Differences

Page Tools