Without seeing your setup or code, my best guess is that you have swapped RX and TX. Remember that RX on the GPS is TX on the board, and if you’re using NewSoftSerial the RX pin is first in the constructor. Are you using NewSoftSerial?

Mikal

I’m trying to run your example on an Arduino Mega with a Sparkfun GPS shield and EM-406A.

Beyond the demo startup message, I’m not seeing squat!

I have the UART/dlink switch in the dlink position, RX is on pin 3, TX on pin 2, GPS baud rate is 4800.

There is an option on the Sparkfun shield to route the GPS serial pins in through another UART, As the Mega has more than 1 UART is this a better way to do it?

Any idea’s what I’m doing wrong?

Mikal

So if i had understand you say that “flat” or “flon” have the higher resolution? that depends of the gps unit?

I assume you mean 10^-6 degrees? GPS units report latitude and longitude with (up to) 9 digits: 3 for degrees and 6 for minutes. The six minutes digits are interpreted as MM.MMMM, so the smallest possible resolution is 1/10000 of a minute or 1/600000 of a degree. This is not quite 10^-6 degrees, but pretty close. The values returned by TinyGPS’s get_position and f_get_position simply return whatever is reported by the GPS.

Does that answer your question?

Mikal

i have a question: it’s possible to return the “lat” an “long” resolution of 10^6 degrees?

compliments for the good work on TinytGPS library

Simone

It’s not too hard to add new values to the code. My suggestion is to find a similar-as-possible value that is already supported and then mimic what I did for that.

Mikal

First of all, good work on the TinyGPS library!

Just wondering if it would be possible/easy to modify the library to output PDOP values?

Regards,

Dan

Thanks,

Mikal