GPS shows symbols

For anyone interested in a step by step troubleshooting process see here;

GPS Tutorial

l-arc-en-ciel:
That TinyGPS shows "invalid" does that mean my GPS module is not compatible with TinyGPS?

That would depend on the code, or example program, you are using, should we just guess ?

l-arc-en-ciel:
19:27:14.694 -> $GLGSV,1,1,04,65,64,041,27,66,46,249,26,81,60,295,26,87,10,169,1865
19:27:14.788 -> $GNGLL,,,,,172713.00,V,N
55
19:27:15.400 -> $GNRMC,172714.00,V,,,,,,,280719,,,N60
19:27:15.440 -> $GNVTG,,,,,,,,,N
2E
19:27:15.440 -> $GNGGA,172714.00,,,,,0,08,2.48,,,,,,48
19:27:15.473 -> $GNGSA,A,1,22,17,01,09,,,,,,,,,5.17,2.48,4.54
18
19:27:15.539 -> $GNGSA,A,1,65,81,66,87,,,,,,,,,5.17,2.48,4.5413
19:27:15.588 -> $GPGSV,2,1,05,01,37,142,30,03,,,32,09,24,210,30,17,41,262,21
45
19:27:15.671 -> $GPGSV,2,2,05,22,54,087,2444
19:27:15.717 -> $GLGSV,1,1,04,65,64,041,27,66,46,249,27,81,60,295,27,87,10,169,18
65
19:27:15.755 -> $GNGLL,,,,,172714.00,V,N*52

And the GPS has not got a fix, it is outside with a good view of the sky ?

Lots of weak signals being reported there.

19:27:15.400 -> $GNRMC,172714.00,V,,,,,,,280719,,,N*60

The "V" in this sentence indicates no satellite fix. You need to be outside, with a clear view of the sky.

How to get data to the monitor without a sketch? Explained in my post at top of page 2 of this discussion.

Yes, by "monitor" I'm referring to the screen you open in the IDE. That's where the Serial.print & Serial.write statements send their data to.

The monitor is connected to the Arduino board's hardware serial port (pins 0 & 1). Serial data arriving at that port from an external device like a GPS board will appear automatically in the monitor.

This will not work if you have a sketch running that executes the statement "Serial.begin()". So, you either load a sketch like Blink or connect a jumper from the RESET pin to a GND pin. This disables whatever sketch is installed ensuring the port is available to the external device.

Your GPS TX pin shud connect to the Arduino pin 1. If this doesn't work, try pin 0. Observe the onboard lights labelled TX & RX.

It would be useful to see your GPS board. Can you post an image of each side? If not, a link to same device from the supplier is a less than perfect option.

Good luck.

John.

I tried again, outside, in clear sky, no trees or anything around.

jremington's code outputs this:

11:02:12.394 -> $GPGSV,3,2,11,25,11,132,32,26,73,271,26,27,14,263,25,29,39,074,35*7A
11:02:12.480 -> $GPGSV,3,3,11,31,26,207,35,36,26,149,30,49,30,182,33*47
11:02:12.527 -> $GLGSV,3,1,09,69,15,012,,70,14,069,19,75,13,165,30,76,59,194,39*69
11:02:12.598 -> $GLGSV,3,2,09,77,49,312,25,78,03,333,,85,26,050,33,86,81,348,34*6B
11:02:12.664 -> $GLGSV,3,3,09,87,30,240,38*5D
11:02:12.697 -> $GNGLL,5219.25935,N,00613.79403,E,090212.00,A,D*70
11:02:13.046 -> $GNRMC,090213.00,A,5219.25932,N,00613.79401,E,0.071,,300719,,,D*67
11:02:13.095 -> $GNVTG,,T,,M,0.071,N,0.132,K,D*3E
11:02:13.143 -> $GNGGA,090213.00,5219.25932,N,00613.79401,E,2,12,0.74,10.2,M,46.0,M,,0000*76
11:02:13.213 -> $GNGSA,A,3,31,26,29,16,05,21,25,27,,,,,1.26,0.74,1.03*16
11:02:13.262 -> $GNGSA,A,3,75,86,76,87,85,77,,,,,,,1.26,0.74,1.03*17

The fullexample of TinyGPS Plus (I posted this code in my previous post)

outputs this:

FullExample.ino
11:03:14.954 -> An extensive example of many interesting TinyGPS++ features
11:03:14.954 -> Testing TinyGPS++ library v. 1.0.2
11:03:14.954 -> by Mikal Hart
11:03:14.954 -> 
11:03:14.954 -> Sats HDOP  Latitude   Longitude   Fix  Date       Time     Date Alt    Course Speed Card  Distance Course Card  Chars Sentences Checksum
11:03:14.994 ->            (deg)      (deg)       Age                      Age  (m)    --- from GPS ----  ---- to London  ----  RX    RX        Fail
11:03:14.994 -> ----------------------------------------------------------------------------------------------------------------------------------------
11:03:14.994 -> **** ***** ********** *********** **** ********** ******** **** ****** ****** ***** ***   ******** ****** ***   0     0         0        
11:03:16.591 -> **** ***** ********** *********** **** ********** ******** **** ****** ****** ***** ***   ******** ****** ***   659   0         95       
11:03:18.049 -> **** ***** ********** *********** **** ********** ******** **** ****** ****** ***** ***   ******** ****** ***   1119  0         164      
11:03:19.694 -> **** ***** ********** *********** **** ********** ******** **** ****** ****** ***** ***   ******** ****** ***   1795  0         264      
11:03:21.146 -> **** ***** ********** *********** **** ********** ******** **** ****** ****** ***** ***   ******** ****** ***   2252  0         327      
11:03:22.810 -> **** ***** ********** *********** **** ********** ******** **** ****** ****** ***** ***   ******** ****** ***   2881  0         428      
11:03:24.242 -> **** ***** ********** *********** **** ********** ******** **** ****** ****** ***** ***   ******** ****** ***   3364  0         500      
11:03:25.810 -> **** ***** ********** *********** **** ********** ******** **** ****** ****** ***** ***   ******** ****** ***   3964  0         596      
11:03:27.286 -> **** ***** ********** *********** **** ********** ******** **** ****** ****** ***** ***   ******** ****** ***   4475  0         669      
11:03:28.871 -> **** ***** ********** *********** **** ********** ******** **** ****** ****** ***** ***   ******** ****** ***   5047  0         761      
11:03:30.337 -> **** ***** ********** *********** **** ********** ******** **** ****** ****** ***** ***   ******** ****** ***   5584  0         836      
11:03:31.905 -> **** ***** ********** *********** **** ********** ******** **** ****** ****** ***** ***   ******** ****** ***   6130  0         925      
11:03:33.365 -> **** ***** ********** *********** **** ********** ******** **** ****** ****** ***** ***   ******** ****** ***   6693  0         1011     
11:03:34.906 -> **** ***** ********** *********** **** ********** ******** **** ****** ****** ***** ***   ******** ****** ***   7213  0         1093     
11:03:36.420 -> **** ***** ********** *********** **** ********** ******** **** ****** ****** ***** ***   ******** ****** ***   7802  0         1176     
11:03:37.933 -> **** ***** ********** *********** **** ********** ******** **** ****** ****** ***** ***   ******** ****** ***   8296  0         1256     
11:03:39.482 -> **** ***** ********** *********** **** ********** ******** **** ****** ****** ***** ***   ******** ****** ***   8911  0         1347     
11:03:40.971 -> **** ***** ********** *********** **** ********** ******** **** ****** ****** ***** ***   ******** ****** ***   9379  0         1421

I can't make anything out of that, except for that there apparently is a checksum fail, but I can't find what that means.

My GPS is this one:
https://hackerstore.nl/Artikel/153
The label on it says: "TOPGNSS GN-2630G (UART) 180608000"

l-arc-en-ciel:
I tried again, outside, in clear sky, no trees or anything around.

So you were still testing inside !

Note that the GPS now has a fix, displays latitude and longitude, as expected when its outside.

And you sure you are using the same GPS baud rate for the @jremington code (which works) as you are for the ‘fullexample of TinyGPS Plus’ ?

From the tutorial I wrote (link above) the common reasons for GPSs ‘failing to work’ are in order;

  1. GPS is indoors
  2. GPS is connected incorrectly
  3. Arduino program uses the wrong GPS baud rate
  4. Arduino program is not correct
  5. GPS is faulty
  6. Arduino is faulty

Congratulations. You have reached a major milestone in both reliably displaying the NMEA sentences and achieving a fix.

Your receiver's default baud rate is 9600. Mikal's original sketch that you started with used 4800. Are you still using 4800 or have you edited it to 9600? (srnet's diagnostic nose is keen!)

I use Mikal's TinyGPS++ library. You might like to run all his examples at sometime -- they are informative.

There's something interesting about your device's output. It produces sentences from more than one satellite system. This might be why Mikal's sketch isn't printing data (srnet spotted this way back).

"chars RX" says you the sketch is receiving characters; "sentences RX" (always 0) means the characters are not forming sentences. "Checksum Fail" is always increasing. That means the same thing.

Mikal's code extracts navigational data from two sentences: GPRMC & GPGGA. So that might be a problem for you. He does provide instructions on how to extract fields from any sentence. You could also configure your device to emit GP sentences only (srnet again). Making Mikal's sketch work for you might be too difficult.

The u-center program from u-blox is what you need. It will show you so much. Not hard to use.

John.

srnet:
So you were still testing inside !

No, I wasn't, but there were some trees close by. Now I made sure I was under a clear sky.

jpom:
Congratulations. You have reached a major milestone in both reliably displaying the NMEA sentences and achieving a fix.

Your receiver's default baud rate is 9600. Mikal's original sketch that you started with used 4800. Are you still using 4800 or have you edited it to 9600? (srnet's diagnostic nose is keen!)

John.

Thanks! This did the trick, I had to adjust the baud rate in the sketch to 9600 that the GPS uses.

Now I have a proper working GPS! Thanks for all your replies and patience!

So, your sketch is displaying readable data rather than all those asterisks?