Vivid LINQ Superchips, Руководство пользователя

Страница: 30 / 48

30
MAINTENANCE MINDER
The Maintenance Minder is an
application that helps the user keep
track of when they need to service
their vehicle. A default list of service
items is copied to a table in the
database for each vehicle the VIVID
attaches to. This allows the VIVID
device to keep track of the service
information for multiple vehicles.
The need to service the vehicle for an item is determined by the mileage traveled since
the last service. This requires the VIVID to be able to track the miles traveled. The
LINQ provides a running counter. This counter is not the actual odometer reading of
the vehicle. Because of this, the VIVID software allows you to enter the vehicle’s
actual odometer value and keeps track of the offset from the actual value to the
running counter the LINQ is reporting. From then on, this offset is used to calculate
the odometer reading to use throughout the Maintenance Minder.
Since the calculation of the free running timer will not always be 100% accurate, an
adjustment factor is also created each time you update your vehicle odometer reading
in the Maintenance Minder. You can open this dialog and enter the new odometer
reading any time. From then on, the calculated adjustment factor is used to adjust the
odometer value used by the Maintenance Minder.
The Maintenance Minder is separated into TWO parts. The fi rst part is the main
Maintenance Minder interface application. This application shows the global settings,
list of service items, and individual values for the currently selected service item.
The second part is a background service that keeps track of the odometer and compares
it to the active service items to see if they are due for service. This background service
notifi es the user of its status using the Android notifi cation system. You can see the icon
in the notifi cation area change. You can also drag the notifi cation down and see how
many items are coming due and how many are past due. You can tap on the notifi cation
and be taken to the Maintenance Minder application no matter what application you
are currently in.
Because the Maintenance Minder requires the LINQ to send the running odometer
counter during this process, the user MUST be in one of the VIVID suite of applications
that actually DAQs with the vehicle for the Maintenance Minder system to be working.
If you are not in a DAQ application, the notifi cation service will not be accurate if the
vehicle is moving.
Note: DAQing apps are DAQ and Gauges
The running counter is kept on the LINQ, so the next time DAQ is started the odometer
value and notifi cation service will all update properly. If you drive the vehicle with
the LINQ disconnected completely, the system will not be accurate and will require
the user to reconcile the vehicle’s odometer value with what is entered into the
Maintenance Minder.