So you have a Garmin GPS and have always been interested in understanding how it really works. You might have read about pseudoranges, code measurements, carrier phase, Doppler shifts, but you have been led to believe that only more expensive geodetic equipment (or bare OEM boards) have all those bells and whistles. Indeed every GPS have to use those things. Otherwise they wouldn't be able to compute your position. It is only that the manufacturers consider you an average consumer that will be satisfied with a simpler 40.38N 136.56W kind of answer. Therefore, the more basic kind of data (so called raw data) never sees the light.

However, it seems that you can get some of that raw data from some Garmins. I have personally tried a GPS12 4.00 and GPS12XL 4.55, but it is also true for other members of the family. Give them a chance.

The raw data is sent through undocumented async messages when enabled with the appropriate command sent to the RS232 port of your unit. Read through the following sections to learn how to do it, and what you can expect (apart from learning a lot of the GPS system and your GPS receiver) from playing with pseudoranges, carrier phases, etc.

I may sound too affirmative in this document when I talk about getting phase carrier or pseudoranges from your GPS12. In many cases, we are not so sure about what we are getting. It is only that it's shorter to write "field so and so corresponds to the integrated carrier phase" than "field so and so shows a certain behavior when compared to this other field, that might lead a gullible Garmin owner to think that is somehow related to integrated carrier phase".

Usual Disclaimer: the official policy of Garmin is to discourage the use of undocumented commands. These were only created for testing purposes and could be discontinued. Worse yet, they could have undesirable side-effects.
In a nutshell, whatever you do to your GPS it is YOUR responsability.

This said, I must add that after a few hours of happy listening to async events I have not observed any trouble. Just enabling async events seems to be reasonably safe. Sending request commands is a completely different thing, though. If you step aside of the documented requests (waypoints, tracks, etc.) anything can happen.

Ultima Modificación: Mon Apr 8 12:18:34 CEST 2002