HAICOM HI-303III GPS

    I was given this item which is strictly a receiver and has no display. It is designed to be connected to a PDA or a computer in order to make use of it. It can be connected to a compact flash connector or with a serial RS232 connection. I used the RS232. mini 1394
    The cable is quite simple except that the GPS uses a mini-1394 connector which are not too common or easy to find. I found them quite cheaply in my travels in China and I built the cable with a DB9 connector for the computer. It is probable that the TXD wire to pin 3 of the DB9 connector is not necessary because, as far as I know, the GPS receiver transmits information but does not receive anything. Still, it is easy to connect anyway.
    The GPS receiver requires 3.3 V power supply and I get it from a USB connector by dropping down the USB 5 V with a couple of diodes. It uses up a USB port of which I have plenty but I might make a short USB extension cable from which I could get the power supply for the GPS and still plug the mouse into the same USB port. Serial Cable
    First I did some basic testing by connecting the GPS receiver to the serial port. I used Hyper Terminal, configured at 4800 baud, and confirmed the computer receives NMEA-0183 sentences. The GPS sends and the computer receives $GPRMC, $GPGGA, $GPGSA, GPGSV and other sentences which contain information about position, speed, etc.
    I then installed Haicom's Viewer software and it does display position, speed, direction and other information but it is only a basic program which has no map or graphic capability.
    Google Earth also has a limited capability. It will receive the GPS data and center the map on that point but it does not allow changing the scale (height of view) or displaying any other data like speed, etc. I have not really used it in any mobile application yet.
HAICOM HI-303III
HAICOM HI-303III

NMEA-0183
NMEA-0183
Serial Configuration (data link layer)
Baud Rate: 4800
Data Bits: 8
Parity: None
Stop Bits: 1 (or more)
Handshake: None

Application Layer Protocol Rules
Each message starting character is a dollar sign.
The next first five characters identify the type of message (talker).
All data fields that follow are comma-delimited.
The first character that immediately follows the last data field character is an asterisk.
The asterisk is immediately followed by a two-digit checksum representing a hex number. The checksum is the Exclusive OR of all characters between the '$' and '*'. According to the official specification, the checksum is optional for most data sentences, but is compulsory for RMA, RMB, and RMC (among others).
<CR><LF> ends the message

 

Examples:

$GPRMC,093721.239,A,4026.2880,N,00341.7718,W,022.4,084.4,190108,,,A*68

Where:
RMC Recommended Minimum sentence C
093721.239 Fix taken at 09:37:21 UTC
A Status A=active or V=Void.
3026.2880,N Latitude 30º 26.2880' N
09341.7718,W Longitude 093º 41.7718' W
022.4 Speed over the ground in knots
084.4 Track angle in degrees True
190108 Date - 19 Jan 2008
003.1,W (Empty fields) Magnetic Variation, W
*6A The checksum data, always begins with *


$GPGGA,093722.238,4026.2426,N,00341.7677,W,1,05,24.7,715.4,M,51.7,M,,0000*7 F

Where:
GGA Global Positioning System Fix Data
093722.238 Fix taken at 09:37:22.238 UTC
3026.2426,N Latitude 30º 26.2426' N
09341.7677,W Longitude 93º 41.7677' W
1 Fix quality: 0 = invalid
1 = GPS fix (SPS)
2 = DGPS fix
3 = PPS fix
4 = Real Time Kinematic
5 = Float RTK
6 = estimated (dead reckoning) (2.3 feature)
7 = Manual input mode
8 = Simulation mode
05 Number of satellites being tracked
24.7 Horizontal dilution of position
715.4,M Altitude, Meters, above mean sea level
51.7,M Height of geoid (mean sea level) above WGS84 ellipsoid
(empty field) time in seconds since last DGPS update
(empty field) DGPS station ID number
*47 the checksum data, always begins with *

Autor: Alfonso Gonzalez Vespa