Hi guys, purchased some gear from you in December. Finally getting a chance to have a look.
Using a uno controller, gps ublok neo-6m
Was working well last night and today it is not.
Photos attachedUploading: C40714C4-9E43-4B35-B2BC-3A61EE920A2E.png…
Hi Ty,
Could you please include a photo of the actual device and connections?
Uploading: E19A66F2-FCF1-41A2-B64D-8446EED23F32.png… Uploading: 2E5E3A76-2DCD-484D-9F2C-ADD2FAC1CE20.jpeg… Uploading: E634F09E-FD0E-4AFD-8CB4-BD02C680FF2C.jpeg…
Looks like something went wrong when you shared those photos.
Can you fix the photo upload, and, share a GGA sentance from the device.
This time in a PDF.
I only get the intro lines about the library and then get location invalid
Date time invalid.
Inside and outside. Last night got a blue light flashing on the gps card and data today neither
There is no PDF attached on your last, either.
The device is constantly outputting NMEA data, which you can interpret via the Arduino. Libraries aside, the GGA sentance (raw) will show what’s going on with satelite lock.
Without some data to work with, a stab in the dark would be that yesterday the weather conditions were better suited for indoor reception. Today, something has changed (cloud cover, etc). Perhaps try with the device outside (not just by a window). GPS doesn’t work well with line of sight obsticals, such as clouds (water), trees, buildings, etc.
1 Like
DeviceExample.ino
A INVALID INVALID
Location: INVALID Date/Time: INVALID INVALID
DeviceExample.ino
A simple demonstration of TinyGPS++ with an attached GPS module
Testing TinyGPS++ library v. 1.0.2
by Mikal Hart
Location: INVALID Date/Time: INVALID INVALID
Location: INVALID Date/Time: INVALID INVALID
I will get the pictures sorted. I will take the library out and see if I can get that data
I am getting a blue light again now.
The code I am using is this:
#include <TinyGPS++.h>
#include <SoftwareSerial.h>
/*
This sample sketch demonstrates the normal use of a TinyGPS++ (TinyGPSPlus) object.
It requires the use of SoftwareSerial, and assumes that you have a
4800-baud serial GPS device hooked up on pins 4(rx) and 3(tx).
*/
static const int RXPin = 4, TXPin = 3;
static const uint32_t GPSBaud = 4800;
// The TinyGPS++ object
TinyGPSPlus gps;
// The serial connection to the GPS device
SoftwareSerial ss(RXPin, TXPin);
void setup()
{
Serial.begin(115200);
ss.begin(GPSBaud);
Serial.println(F(“DeviceExample.ino”));
Serial.println(F(“A simple demonstration of TinyGPS++ with an attached GPS module”));
Serial.print(F("Testing TinyGPS++ library v. "));
Serial.println(TinyGPSPlus::libraryVersion());
Serial.println(F(“by Mikal Hart”));
Serial.println();
}
void loop()
{
// This sketch displays information every time a new sentence is correctly encoded.
while (ss.available() > 0)
if (gps.encode(ss.read()))
displayInfo();
if (millis() > 5000 && gps.charsProcessed() < 10)
{
Serial.println(F(“No GPS detected: check wiring.”));
while(true);
}
}
void displayInfo()
{
Serial.print(F(“Location: “));
if (gps.location.isValid())
{
Serial.print(gps.location.lat(), 6);
Serial.print(F(”,”));
Serial.print(gps.location.lng(), 6);
}
else
{
Serial.print(F(“INVALID”));
}
Serial.print(F(" Date/Time: “));
if (gps.date.isValid())
{
Serial.print(gps.date.month());
Serial.print(F(”/"));
Serial.print(gps.date.day());
Serial.print(F("/"));
Serial.print(gps.date.year());
}
else
{
Serial.print(F(“INVALID”));
}
Serial.print(F(" “));
if (gps.time.isValid())
{
if (gps.time.hour() < 10) Serial.print(F(“0”));
Serial.print(gps.time.hour());
Serial.print(F(”:"));
if (gps.time.minute() < 10) Serial.print(F(“0”));
Serial.print(gps.time.minute());
Serial.print(F(":"));
if (gps.time.second() < 10) Serial.print(F(“0”));
Serial.print(gps.time.second());
Serial.print(F("."));
if (gps.time.centisecond() < 10) Serial.print(F(“0”));
Serial.print(gps.time.centisecond());
}
else
{
Serial.print(F(“INVALID”));
}
Serial.println();
}
Now that the blue light is flashing again do you have connectivity? You should be able to test the GPS by just reading the Serial data that it is outputting. Your problems may be this library that you are using.
it may be that. I did not change the library from last night when it is working.
I will try the adafruit library with code from your page and get back to you.
I think I was lucky with wiring connections last night. I will have a look in the shop for some better connectors to make it more stable. I am now getting NO GPS DETECTED, Check Wiring.
So it is finding the board and I am getting a blue light. Just seems to be connections.
You will find this happens a lot when using breadboards and prototyping wires. To help reduce the risk of these errors it is best to use wires that are as short as possible and to keep components close to each other on the board. Another good practice that can help is to use decoupling capacitors(10uF cap between external DC supplies and ground). For final designs it is also a good idea to get things made on PCBs as they are much less prone to these issues. (Though sadly you need to go through the prototype phase as PCB are not very flexible in terms of design changes.)
Ty,
If the GPS module is powered and healthy, it will be putting NMEA sentences onto its TX pin. It will do this whether or not it has a navigational fix. Your first task is to read those sentences without, repeat without, using a sketch on the UNO.
Open the IDE monitor at 9600 baud rate. Connect the TX pin of the GPS to pin 0 or 1 of the UNO. Press and hold the UNO’s reset button. Legible NMEA sentences should flow to the monitor (if you picked the correct pin).
I say pin 0 or 1 as there is confusion about which is the UNO’s serial receive pin. On mine it is pin 1,others say it is pin 0. Observe the UNO’s onboard LEDs labelled TX and RX. When you’ve got it right, the LED labelled RX will flash at 1Hz.
If the sentences appear as many commas with nothing between them, that means teh GPS is not getting satellite data.
John.
Can you provide a link to the site from where you purchased the GPS module so we can see photo of it?
I got this when I did that.
20:26:16.638 -> $GPGSA,A,1,99.99,99.99,99.9930
20:26:16.685 -> $GPGSV,1,1,0079
20:26:16.685 -> $GPGLL,102617.00,V,N49
20:26:17.501 -> $GPRMC,102618.00,V,260419,N79
20:26:17.547 -> $GPVTG,N30
20:26:17.594 -> $GPGGA,102618.00,0,00,99.99,6A
20:26:17.641 -> $GPGSA,A,1,99.99,99.99,99.9930
20:26:17.688 -> $GPGSV,1,1,0079
20:26:17.688 -> $GPGLL,102618.00,V,N46
20:26:18.519 -> $GPRMC,102619.00,V,260419,N78
20:26:18.566 -> $GPVTG,N30
20:26:18.566 -> $GPGGA,102619.00,0,00,99.99,6B
20:26:18.613 -> $GPGSA,A,1,99.99,99.99,99.9930
20:26:18.660 -> $GPGSV,1,1,0079
20:26:18.707 -> $GPGLL,102619.00,V,N47
20:26:19.525 -> $GPRMC,102620.00,V,260419,N72
20:26:19.570 -> $GPVTG,N30
20:26:19.570 -> $GPGGA,102620.00,0,00,99.99,61
20:26:19.617 -> $GPGSA,A,1,99.99,99.99,99.9930
20:26:19.663 -> $GPGSV,1,1,01,30,237A
20:26:19.710 -> $GPGLL,102620.00,V,N4D
20:26:20.698 -> $GPRMC,102621.00,V,260419,N73
20:26:20.698 -> $GPVTG,N30
20:26:20.745 -> $GPGGA,102621.00,0,00,99.99,60
20:26:20.792 -> $GPGSA,A,1,99.99,99.99,99.9930
20:26:20.839 -> $GPGSV,1,1,01,30,1973
20:26:20.839 -> $GPGLL,102621.00,V,N4C
20:26:21.536 -> $GPRMC,102622.00,V,260419,N70
Well done. You’re now reading the NMEA sentences
This is what I get when my GPS does not have a fix:
22:54:56.622 -> $GPRMC,V,N 53
22:54:56.622 -> $GPVTG,N 30
22:54:56.669 -> $GPGGA,0,00,99.99, 48
22:54:56.716 -> $GPGSA,A,1,99.99,99.99,99.99 30
22:54:56.716 -> $GPGSV,1,1,00 79
22:54:56.763 -> $GPGLL,V,N 64
22:54:57.653 -> $GPRMC,V,N 53
22:54:57.653 -> $GPVTG,N 30
22:54:57.653 -> $GPGGA,0,00,99.99, 48
22:54:57.700 -> $GPGSA,A,1,99.99,99.99,99.99 30
Doesn’t quite match what you’re getting.
The timestamp is coming from the IDE, not the GPS.
There are 6 sentences being generated, repeating each second. The RMC sentence contains the UTC time. In yours it gives 10:26:18 which aligns with your timestamp. That is coming from the GPS and it is getting that from the satellites.
The “V” following UTC means invalid. Then comes the latitude: “260419”. That’s 26.04 degrees. Would that be right for your location?
Your sentences aren’t complete. There should be more data. In mine you can see where the data will appear (between the commas) when I get a fix. “V” means not valid. Those “99.99” also mean no fix.
So you don’t have a fix but the device is working at it. Can’t explain why you don’t have the commas with emty data fiels between.
The apparent italics seems to be produced by the forum editor.
I’ll post an example of when I have a fix.
Stick with it.
Looks like the posting editor is modifying our posts. Here is a sceren shot of mine:
Here’s what I get when the GPS starts to get good data from the satellites, but not enuf for a fix:
I was wrong about 26.0419 being yr latitude. I got that as well. It’s the date…derrr
Here’s what I get when I have a fix. I’ve blotted out some of the lat & long.:
Make sure that tiny antenna connection at the board is good. Makes a big difference if it isn’t.
