3/4
ÜberTracker_UG_v071221
ÜberTracker User Guide
1 2 . 2 1 . 2 0 0 7
3) Reset Failure Log
The ÜberTracker keeps a log of how many times it fails to report
data. This can happen in areas of poor network connectivity, but
also if there is a fault with the unit. Keeping track of this number
can help to diagnose a faulty unit. Pressing “3” will allow you to
reset this number.
4) Change Remote Server Address
Pressing “4” will allow you to enter a remote server address to
which you wish to connect and report (setting up a web server is
beyond the scope of this document). The address can be entered
as an IP address in the format “xxx.xxx.xxx.xxx”, or a regular host
name like “
www.sparkfun.com
”. The remote address can be up
to 64 bytes in length. Note: the format for the GPRS report will be
covered later in this document.
5) Change Remote Server Port
Pressing “5” will allow you to change the remote server port
number, from 0 to 65535.
6) Change Mode
Pressing “6” will toggle between four different reporting options:
GPRS, email Google Maps links, email readable text, and email
NMEA standard format.
In all email formats, the subject line will contain the IMEI number of
the unit. This can aid in identification when running multiple units.
Time and date are UTC.
The body format of the Google Maps link emails will be as follows
(for example, SparkFun corporate offices):
11/27/07, 21:52:56,
http://maps.google.com/maps?q=40.064754,
-105.209854
The body format of the text log emails will be as follows:
11/27/07, 21:52:56, 40.064754,-105.209854
The body format of the NMEA standard emails will be as follows:
21.52.56.000,A,4003.8852,N,10512.5912,W,0.03,75.15,271107
This is an abridged form of the NMEA 0183 RMC sentence. For a
complete breakdown of the NMEA standard, please visit
http://
www.gpsinformation.org/dale/nmea.htm.
If the user is intending to operate the ÜberTracker in GPRS mode
and set up their own web server, the user will most likely need a
rather complete description of the data format to facilitate effective
data parsing. The data comes as ascii and is as follows:
$ID<IMEI#, 15 chars><LF><CR>
<LF><CR><Log>
<LF><CR><Log>
<LF><CR><Log>...
+++
Each log is preceded by <LF+CR>, ascii 10 and 13. Also, each
log can vary in length, but is usually around 57 characters. The
format of the log is identical to the NMEA standard RMC sentence
shown above in the previous example. The last log to be sent will
be immediately followed with “+++”. The ÜberTracker will then
kill the connection.
7) Change Email Address
Pressing “7” will allow you to change the email address to which
to send reports. The email address may be up to 32 characters
in length. When you receive your emails, they will show your
address as the sender.
8) Save and Exit
Pressing “9” will save your new settings. After choosing this
option, turn off the ÜberTracker and disconnect it from the
programming adapter. Make sure to insert your AT&T Wireless
®
SIM card into the cell module, and screw the top back on. It’s
now ready to run.
What you’ll see when it’s running...
When the ÜberTracker is first switched on, the status LED will
flash red/blue after initialization. It will then wait for 5 seconds
(no LED) for an external communication link indicator. If none
is found, it will turn on the GPS module to get a position fix,
indicated by the red status LED. When it acquires its location,
it will either wait for the next GPS lock if logs per report is set
to a number greater than one, or it will attempt to report. If
waiting for the next lock to occur, the status LED will go dark.
If reporting, the red LED will go off and the green LED will flash
during cellular operations (more quickly at first, then more slowly
once it acquires a network connection, then quickly again when
it shuts down). If the unit was able to successfully report, the
blue status LED will blink once shortly after the green LED stops
blinking. The unit will then go quiet until the next GPS lock.
You may notice that the ÜberTracker may not always hit the time
marks that you expect, or may add a minute to the reporting
schedule occasionally. This is because the cellular activities
are not a part of the timing, and the time necessary to do the
network communications can be somewhat unpredictable. As an
example, suppose we’re running an ÜberTracker with a 5 minute
interval and 3 logs per report. Every 15 minutes the device will
report. The time count starts at time = 0 and stops at time =
15 minutes, at which time the ÜberTracker will issue a report.
The count effectively stops while the device attempts to “phone
home” and starts up again when it’s done. If it takes 1 minute to
do the network communications, the whole 15 minute frame will
shift 1 minute forward. The reason for doing this is because it’s
possible to set the parameters in such a way that the GPS lock
time could occur before the report has finished if the network
time were inclusive. If that were to occur, the device would go
to sleep for 24 hours. But since the network connection time is
not inclusive to the lock timing, such an overrun cannot occur.
