I have been using GPGST to provide error estimates to my clients software.
But in 2.10.2 it appears to have disappeared?
Can the message come back?
Please!
No Reply:-(
Hey,
It’s GNGST now. Well, it should have been from the start. GN instead of GP means it’s based on multiple GNSS, not just GPS.
1 Like
@egor.fedorov I have searched and search, but no GNGST does not exist in the nmea output.
I changed my code based on your confident statement, thought I had done it wrong, but today I trawled through the nmea output logs. NO GNGST.
Please can you re-implement GPGST or implement GNGST urgently. I want to ship a unit on Monday that provides this.
Simon
can’ you accept going back to v2.10.0 STABLE ? (firmware reflash…)
There we still have it… but no csv export 
1 Like
No, th improvements in wifi connectivity from 2.10.0 to 2.10.2 were huge. I get 100% discovery of the wifi hotspot that starts up 30 secs before the reach. with 2.10.0 this was 70/30 with intervention required if it did not connect and set up its own hotspot. so 2.10.0 not an option.
1 Like
good to know…
i had soem wifi issues but wasn’t 2.10.2 solves them mostly thanks
As far as I can see, the GNGST message is there. Here’s a sample of NMEA output for v2.10.3:
$GNRMC,181542.40,A,5957.6195618,N,03020.0446501,E,0.03,,050318,,,A*54
$GNGGA,181542.40,5957.6195618,N,03020.0446501,E,1,25,0.0,40.709,M,15.933,M,0.0,*6A
$GPGSA,A,3,02,05,06,12,21,23,25,26,29,31,40,,1.3,0.7,1.1*39
$GLGSA,A,3,66,67,68,73,74,75,76,83,84,85,,,1.4,0.8,1.1*22
$GAGSA,A,3,01,08,26,,,,,,,,,,0.0,0.0,0.0*2E
$GPGSV,3,1,11,02,40,063,42,05,22,107,41,06,08,042,37,12,25,134,38,1*60
$GPGSV,3,2,11,21,07,207,38,23,11,351,36,25,62,161,46,26,19,301,37,1*61
$GPGSV,3,3,11,29,72,238,49,31,42,271,45,40,19,152,34,,,,,1*52
$GLGSV,3,1,10,66,06,332,41,67,24,021,46,68,16,076,40,73,08,167,41,1*79
$GLGSV,3,2,10,74,55,197,45,75,51,306,48,76,09,333,39,83,32,055,41,1*74
$GLGSV,3,3,10,84,88,228,41,85,30,236,44,,,,,,,,,1*71
$GAGSV,1,1,03,01,29,167,42,08,14,039,36,26,56,076,40,,,,,7*4C
$GNGST,181542.40,0.138,,,,1.459,1.440,2.898*61
$GNVTG,,T,,M,0.03,N,0.06,K,A*38
We are currently reviewing this message in RTKLIB, but it would help a lot if you could tell us what exactly is wrong with it.
See attached raw logs both from 2.10.3
The RS has a GPGST sentence. The RTK unit has no GPGST sentence at all.
2.10.3.ReachRS_NMEA.log (42.8 KB)
2.10.3.ReachRTK_NMEA.log (88.9 KB)
2.10.2 has solved the wifi issue very well, but added a GPGST issue.
i can confirm what @egor.fedorov gets, here an example output from a ReachRS running 2.10.3 dev
$GNRMC,092351.00,A,5221.8790976,N,00452.2540766,E,0.28,,060318,,,D*5C
$GNGGA,092351.00,5221.8790976,N,00452.2540766,E,5,10,1.4,18.597,M,42.932,M,1.4,*64
$GPGSA,A,3,05,07,13,15,20,21,27,,,,,,3.3,2.3,2.4*35
$GLGSA,A,3,70,78,85,86,,,,,,,,,5.1,3.0,4.1*27
$GAGSA,A,3,08,,,,,,,,,,,,0.0,0.0,0.0*2B
$GPGSV,2,1,07,05,67,246,31,07,51,064,36,13,39,276,41,15,08,282,40,1*6C
$GPGSV,2,2,07,20,21,311,35,21,08,336,33,27,06,031,31,,,,,1*59
$GLGSV,1,1,04,70,31,312,33,78,44,043,35,85,09,287,33,86,16,339,38,1*75
$GAGSV,1,1,01,08,63,292,43,,,,,,,,,,,,,7*41
$GNGST,092351.00,0.795,,,,0.504,1.283,1.695*62
$GNVTG,,T,,M,0.28,N,0.52,K,A*30Agreed
I see it with the RS
But it isn’t there with the RTK module
We’ve just taken a new Reach unit, flashed and updated it. I can GNGST both with and without solution. Did you make any changes to the internal system?
I have made no changes to the internal system.
The unit is relatively new, less than 3 months old. I think it came with 2.8.x on and I have updated incrementally to 2.10.3
Will use the config log feature later today to sen you a cpopy of internals.
I have a second Reach RTK unit which I checked this evening [ it is installed on my Phantom 4] and that has GNGST. I will take that unit and install it in my other system.
Does mean I have a unit that I cannot use for original purpose tho’
Simon
Thanks for sending the report. Everything appears to be ok. I would suggest reflashing the unit. This should be the fastest way to get back on track, since time is an issue. Please do this and confirm whether you have the message back.
This topic was automatically closed 100 days after the last reply. New replies are no longer allowed.