- Sun Jan 19, 2014 9:29 am
#167410
<disclaimer>Newbie</disclaimer>
I'm trying to hook up the Copernicus II GPS module, essentially with the same components as the
SFE hookup guide (same antenna too), except using an Arduino Uno (via the 3.3v pin) instead of the FTDI board. And then using a short sketch which essentially copies serial input from the GPS to the serial monitor.
One time only (a week ago) I got expected NMEA output that looked like this:
$GPGGA,182853.00,3849.16540,N,07703.45057,W,12,1,02,1.00,00012,M,-033,M,,*56
$GPVTG,265.8,T,276.3,M,002.9,N,005.4,K,A*20
...
But now I get output like this:
$GPGGA,,,,,,0,00,,,,,,,*66
$GPVTG,,,,,,,,,N*30
(NB: in between I tried reconfiguring the GPS module a few times, including sending the NMEA sentence to reset the module to its factory default settings, which clears the position cache)
Okay, so that says to me that the antenna is not getting a fix, or that the antenna and/or GPS module is defective (which seems to be an issue with others).
Or possibly that that 3.3v Arduino pin can't supply enough mA for both the GPS and antenna, as I've seen suggested elsewhere. So to test that I disconnected my jumper wires from Arduino pins 3.3v and GND and instead plugged them into a [url https://www.sparkfun.com/products/10804]Breadboard power supply stick[/url] outputting a steady 3.3v (verified with my DMM) but with the TX/RX pins still connected to the Arduino. When I do that I get output of... nothing. I also tried connecting XSTBY to VCC as suggested in the Copernicus II manual (although it worked fine w/o this when powered through Arduino) but that didn't help. If I connect the VCC/GND wires back to the Arduino, I start getting NMEA output again (still no fix).
Why would that be? I feel like I'm missing something obvious.
I'm trying to hook up the Copernicus II GPS module, essentially with the same components as the
SFE hookup guide (same antenna too), except using an Arduino Uno (via the 3.3v pin) instead of the FTDI board. And then using a short sketch which essentially copies serial input from the GPS to the serial monitor.
One time only (a week ago) I got expected NMEA output that looked like this:
$GPGGA,182853.00,3849.16540,N,07703.45057,W,12,1,02,1.00,00012,M,-033,M,,*56
$GPVTG,265.8,T,276.3,M,002.9,N,005.4,K,A*20
...
But now I get output like this:
$GPGGA,,,,,,0,00,,,,,,,*66
$GPVTG,,,,,,,,,N*30
(NB: in between I tried reconfiguring the GPS module a few times, including sending the NMEA sentence to reset the module to its factory default settings, which clears the position cache)
Okay, so that says to me that the antenna is not getting a fix, or that the antenna and/or GPS module is defective (which seems to be an issue with others).
Or possibly that that 3.3v Arduino pin can't supply enough mA for both the GPS and antenna, as I've seen suggested elsewhere. So to test that I disconnected my jumper wires from Arduino pins 3.3v and GND and instead plugged them into a [url https://www.sparkfun.com/products/10804]Breadboard power supply stick[/url] outputting a steady 3.3v (verified with my DMM) but with the TX/RX pins still connected to the Arduino. When I do that I get output of... nothing. I also tried connecting XSTBY to VCC as suggested in the Copernicus II manual (although it worked fine w/o this when powered through Arduino) but that didn't help. If I connect the VCC/GND wires back to the Arduino, I start getting NMEA output again (still no fix).
Why would that be? I feel like I'm missing something obvious.
