For GPS accuracy, the magic words to look up in the AT command set are Dilution of Precision. You should be able to get at least the PDOP, HDOP and VDOP values which will give estimates of the current accuracy of location in the horizontal (HDOP) plane, vertical (VDOP) plane and an overall indication (PDOP).
Ciao, Dave
EDIT: try enabling the GSA sentence (GPS_NMEA_GGSA_EN) using AT+GPSNMEA. This sentence contains all the active satellites used in the current fix, the signal strength of these satellites as well as HDOP, VDOP and PDOP values.
I don’t have the HL6528 Development Kit on hand yet.
Will try your recommendations once DevKit arrived.
I’m studying AT commands as of the moment and maybe missed that GPS accuracy command or it may not be explicitly stated in AT commands reference guide.
Will update this thread once tested.
EDIT: looks like HL6528 doesn’t have the HL6528-G. If so, testing of GPS can only be done during board bring-up.
It’s not explicitly stated as an AT command - you have to know what’s available in the NMEA sentences.
You could also look at what’s available in the PVT output - that might be easier to parse than having to dig through multiple NMEA sentences to grab a bit from one and more from another…
I doubt it - +kjam is to do with GSM radio jamming, not GPS. The GSA NMEA sentence gives you the signal strengths of the satellites (Space Vehicles or SVs) used to generate the current GPS fix.
If you’re interested in the GSM radio signal strength, start with +CSQ to get the rssi and ber. The also appears to be $ CSQ which is similar. There are other commands to dig out the cell signal info etc. Search the at guide for signal quality and signal strength.
The best way to work out the quality (and thus the accuracy) of the fix (or Position Solution) is to use the [H|D|P] Dilution of Precision values. These are supplied by the GPS engine and are based on the SV’s used to generate the fix. There is a table that maps the DOP values to an estimated position accuracy - have a look at this wiki article.
SV signal strength is available straight from the NMEA sentence if you’re trying to do something funky and map signal propagation or something. But it’s only for the SVs listed… and as GPS uses multiple SVs (min 3 for 2D solution, preferably 4 or more for 3D solution) you don’t know WHICH SVs the GPS engine has used for the solution.
For some good info on GPS and how it works, have a look at the Whitepapers section on the GPSd site.
That proprietary sentence sounds like a good plan.
Also, have a look at the section in the manual about PVT sentences. One of the problems with NMEA output is that you need to get a number of sentences to get a complete solution. I understand that the PVT sentences bring out more of the complete solution information in less sentences.
i am working on the Vehicle tracking & i am using HL6582-G2.8V module with Firmware “HL6N_003_00_200F_p7176B”
i am starting the GNSS by applying AT+GPSSTART=0 & AT+GPSNMEA=1,1,0005,81 to collect the NMEA Frames & logging in txt pad for 9 to 10 Hours.
then plotting these data’s in Google map using gpsvisualizer.com/ & i observe there is no stability in location data its wandering.(image attached for reference)
due to this issue when i measure distance travel report for the vehicle i am getting around 10KM & above even when the vehicle is in stable position.