Wahoo V-1.0.6:

Force Wahoo hardware to fresh reset when lose GPS fix for more than 1 hour. During operation
as soon the hardware regains GPS fix, the timer is reset. There are a couple of units in the
field have no reporting because of no GPS lock.

Wahoo V-1.1.4:
Released Date: 07/10/2008

1. Single version for Wahoo and Wahoo-2. This version is based on 21-byte track.
   When new version 1.1.4 starts, first thing to check is if any older 22-byte track is there.
   If it is there then delete it and reset the hardware.
2. Increase ADC1_IN to 1700 mV from 1500 mV according to Jim Chen of Indesign advice.
3. Drop gps data when Lon=0.0 and Lat=0.0 and fix is good.
4. position buffer to replace flash memory access.
5. detect Wahoo-1 and wahoo-2 hardware by looking at pin after gpio initialization state.
6. adding two different shutdown:
   manual shutdown - switch to non operation mode, when switch power off
                     switch to operation mode, when switch power back on.
   soft shutdown - force fast mode hardware watchdog to kick in. The hardware will be reset
   automatically in 20 seconds.
7. when power cut occurs wither way thru manual shutdown or soft shutdown, power cut packet will be
   delivered to the gateway. Particular manul shutdown will make hardware transmit power cut as many
   as possible to drain the super capacitor.

Wahoo V-1.1.5:
Released Date: 07/11/2008

1. Changed back ADC1_IN meter level to 1500 mV, since one Wahoo-2 hardware in the field measure
   between 1500 mV and 1700 mV that cause auto shutdown, reboot, send power cut packet to the
   gateway over and over.
2. Power cut packet included voltage meter (2 bytes) - msgtype is 0x66

Wahoo V-1.1.9:
Released Date: 09/12/2008

Changed code to report track when no gps and Sensors/IGN/PING are triggered by a given last known position.
The fix is to resolve customers complaints about missing track when the vehicle parking in the garage or
spotted gps area. However, it won't fix when vehicle still moving but no gps.

Wahoo V-1.1.16:
Release Date: 10/28/2008

Fixed a bug that happens when out of network coverage with a number of old tracks. After back in the
coverage old tracks queue was purged. It causes missing gps gap. GPStrack.SaveTracks() was replaced
by GPStrack.SaveTracksIns().


Wahoo V-1.1.18:
Released Date: 11/06/2008

Changed code to handle bulk tracks delivery to the gateway when there are old tracks in the queue.
This will improve efficency of packets unload dramatically when number of old tracks are growing so many.
Particularily in a long period of time without radio coverage or bad spotted area. This fix mainly
for customer Recall but should apply to all. Set threshold MAX_TRACKS_PER_XMIT to 50 means 50 tracks
per chunk and using the very first track's transid as a transid, and only one ACK replied from the
gateway. TrackParser.SendOldTracks(GPIOTask task) was modified.

Wahoo V-1.1.19:
Released Date: 11/14/2008

Changed shutdown procedure GPSTask.Shutdown() and replaced hardware watchdog code with AT+FUN=0,1
according to Indesign engineer. This method should resolve unreliable timer of hardware watchdog.

Wahoo V-1.1.21:
Released Date: 11/21/2008

Added GPSTask.Threading() and ThA class to handle splitted radio connection. The goal is to help
GPSTask thread performance that should help to reduce gps gaps.

Wahoo V-1.1.22:
Released Date: 12/02/2008

Added verification code in Profile.GetProperty to handle bad or corrupted profile data issued from
the gateway mainly command sendprofile. If it is corrupted data, hardware will ignore it. If the
corrupted profile data were already existing in the persistent memory, wahoo hardware will only
use the default profile value instead of bad data.

Wahoo V-2.0.0:
Released Date: 12/08/2008

Turned off keep-alive packet. Wahoo I/II doesn't need keep-alive.

Wahoo V-2.0.2:
Released Date: 05/06/2009

The roaming issue at some area in Canada takes more than 20 seconds and hardware watchdog kicks in
then reset the mobile. This roaming issue kept some mobiles resetting every 20 seconds from re-acquire
the network connection. The fix is to prolong the hardware watchdog to extended mode (40 minutes) that
mobile has enough time to regain the normal operation state.