New GNS 2000 bluetooth GPS issue

[evanhood]

I just received a new GNS 2000 (details here: //http://www.gns-gmbh.com/index.php?id=233&L=1) and Locus seems to be having a problem with the NMEA messages coming from it. Most of the time it reports no fix even though a bunch of satellites are visible and have strong signal. Android App Ultra GPS Logger doesn't have this problem.

The GNS 2000 supports GLONASS and running the NMEA messages through gpsview throws up errors on those $GLGSV messages, not sure if Locus is expecting them or not?

A quick scan through the messages and I don't see any proprietary ones like the problem with the XGPS-150 you fixed (here: //http://forum.locusmap.eu/viewtopic.php?f=10&t=2660&p=17806&hilit=bluetooth+fix#p17806)

I've attached a sample NMEA output and below are some lines:
$GPGGA,160818.000,5203.8295,N,00042.6982,W,2,10,0.89,56.1,M,47.2,M,0000,0000*49
$GNGLL,5203.8295,N,00042.6982,W,160818.000,A,D*57
$GNGSA,A,3,29,12,31,25,24,02,04,14,,,,,1.81,0.89,1.58*11
$GNGSA,A,3,84,75,,,,,,,,,,,1.81,0.89,1.58*17
$GNRMC,160818.000,A,5203.8295,N,00042.6982,W,62.04,125.08,230513,,,D*58
$GPVTG,125.08,T,,M,62.04,N,114.96,K,D*0D
$GPGGA,160819.000,5203.8196,N,00042.6754,W,2,10,0.89,56.3,M,47.2,M,0000,0000*4F
$GNGLL,5203.8196,N,00042.6754,W,160819.000,A,D*53
$GNGSA,A,3,29,12,31,25,24,02,04,14,,,,,1.81,0.89,1.58*11
$GNGSA,A,3,84,75,,,,,,,,,,,1.81,0.89,1.58*17
$GPGSV,3,1,11,25,85,012,31,12,50,076,34,29,44,194,34,14,41,242,22*74
$GPGSV,3,2,11,31,34,304,27,02,28,080,38,33,28,198,29,04,18,044,34*7F
$GPGSV,3,3,11,24,17,137,27,32,04,315,19,20,01,340,15*43
$GLGSV,2,1,08,74,79,067,42,84,61,159,28,83,48,047,28,75,37,312,35*66
$GLGSV,2,2,08,73,29,118,35,85,19,191,,66,15,342,,65,13,288,*62
$GNRMC,160819.000,A,5203.8196,N,00042.6754,W,62.01,124.98,230513,,,D*51
$GPVTG,124.98,T,,M,62.01,N,114.90,K,D*06

It is worth mentioning that I have seen Locus intermittently finally detect there is a fix but it seems like it's only when I have a poor signal indoors, almost like the device is reporting more satellites than Locus is expecting and once it drops below a threshold (or stops getting $GPGSV messages?) then it's happy.

[Menion]

I'm quite surprised that NMEA may contain in one file so much types ... GPGGA, GNGSV, GLGSV ... do you know what first two letter means? Locus currently handled only these with "GP" at start, so this was problem

In next version, will this be fixed, but I'm still curious ...

EDIT: and thanks for NMEA file, it helped a lot

[jusc]

I'm quite surprised that NMEA may contain in one file so much types ... GPGGA, GNGSV, GLGSV ... do you know what first two letter means?

you can find this here:
ftp://ftp.macrogroup.ru/Support/SkyTraq ... 2M1_v6.pdf