Hello - I've been playing around with GPS for the last couple of days using
http://www.arduino.cc/cgi-bin/yabb2/YaBB.pl?num=1267027090 to get started - it has GREAT info and Kevin has been nice to help, but I still didn't get it working.
There is a snippet of code there that says it will cause the NEMA sentences to display on the serial monitor that I used. Should I have changed anything for my setup?
void setup(){
Serial.begin(4800);
}
void loop(){
if (Serial.available() > 0){
Serial.write(Serial.read());
}
}
I then went to playground for: http://www.arduino.cc/cgi-bin/yabb2/YaBB.pl?num=1267027090 and did a copy 'n paste of the code - the code compiles and loads nicely. BOTH systems give exactly the same results - garbage on Arduino serial monitor set to COM6. Yes, I do have the baud set at 4800 in all places.
I have used NEMA 0183 output from two different GPS with the exact same results - on the Arduino serial monitor I get:
ÊÖn⾶ÊòN:":
.*F.NúN2>2>F":>.NÆN>
"*6F
6N¢N>F>.N*
F:
N:2:>
not sure why that did not display on same line - on the serial monitor it's all a single scrolling line.
If I put either of the two GPS engines direct to COM4 port and monitor the NEMA 0183 sentences with either TerraTermPro or even with Arduino serial monitor (setting both to COM4 and 4800 baud) they both display the correct NEMA 0183 sentence.
$GPRMC,173847.915,A,3030.7112,N,08752.9299,W,0.06,98.08,180310,,*20
There are a lot of other lines displayed and they look good, but the $GPRMC sentence is where all the lat/long, speed, etc is located - those are correct for my location.
From the results printed to serial monitors without going thru the Arduino we can tell the GPS is talking in NEMA sentences. The only wiring required is to put the GPS TX wire to digital pin 0 to see output. The Arduino is on COM6 (for USB connection).
Any suggestions and ideas would be appreciated. I did not paste the code as it is an exact copy 'n paste from the playground area. If desired, I can add the code.
I'm using a desktop, ASUS MB, XP-SP2 with Arduino IDE 0018.
Thanks for any and all help,
Ken H.