Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No accuracy information available with SW Maps or GNSS Master (no NMEA GST) #513

Open
mmoduu opened this issue Jan 13, 2025 · 20 comments
Open

Comments

@mmoduu
Copy link

mmoduu commented Jan 13, 2025

When connecting to RTK Postcard via Bluetooth with SW Maps or GNSS Master, there isn't accuracy information displayed, and GNSS Master even says "No NMEA GST". This does not change if I enable NTRIP client in the app (NTRIP client in the RTK Postcard does not work, I'll create a separate issue if I remember).

However, if I open the serial terminal, you can see status strings that specify the accuracy, so the data is there somewhere.

Weirdly, Quectel also confirm that they do not output that data currently (https://forums.quectel.com/t/the-lg290p-doesnt-seem-to-support-nmea-gst-message/39242), but is it possible that you could inject that data to the output?

@nseidle nseidle transferred this issue from sparkfun/SparkFun_RTK_Postcard Jan 13, 2025
@nseidle
Copy link
Member

nseidle commented Jan 13, 2025

Indeed, I've confirmed the GST message is not supported on the LG290P and requested it in a future firmware release. Quectel says maybe in a future firmware update but I haven't seen any firmware updates yet so who knows.

is it possible that you could inject that data to the output?

Anything is possible but there's not so many hours available. We can generate NMEA easily enough but we don't yet have a scheduler to add messages to the outbound circular buffer (what you see in your GIS app). This feature would be related to the unique ID messages request. Same plumbing, different message to report.

@nseidle
Copy link
Member

nseidle commented Jan 13, 2025

The timing couldn't be better. I was just notified by Quectel that they released new firmware that supports GST.

Quectel_LG290P_Firmware_Release_V0104S.zip

We'll get started implementing this.

@nseidle
Copy link
Member

nseidle commented Jan 14, 2025

GST is working on the Postcard in the release candidate. We have a bunch of docs to update but you should be able to update your LG290P firmware on Postcard with this:

Start the update procedure from QGNSS:

Image

Within 20 seconds, you have to reset the LG290P. Do this from system->hardware->13) LG290P reset for firmware update:

Image

Firmware updates took me about 75 seconds.

Release candidate is scanning for old (< v4) and new (>=v4) firmware types and settings things up accordingly.

Note: GST is currently reporting single decimals so the accuracy during normal 3D Fix will look fine, but in RTK Fix mode, some GIS softwares (ie, SW Maps) will report an unknown lat/lon positional error because of this:

$GNGST,190701.500,0.7,0.0,0.0,85.7,0.0,0.0,0.0*4F

Error in GST is reported as '0.0' when really it's 0.013 (13mm). Their binary protocol confirms this but the GST message is cutting off those all important decimals. I've pinged Quectel to see if there's a remedy.

@mmoduu
Copy link
Author

mmoduu commented Jan 14, 2025

Thanks for the hard work on this!

I need to find an Windows PC first to try that firmware upgrade, I'll report my progress in about 20 hours...

@nseidle
Copy link
Member

nseidle commented Jan 15, 2025

Np! Glad it's coming together. Also, our RTK loader is available on Win/iOS/*inux.

@mmoduu
Copy link
Author

mmoduu commented Jan 19, 2025

Hi!

Sorry for the long delay. I was able to flash the firmware (both ESP32 and LG290P) and see the results. Let's hope Quectel can fix that data problem soon.

@ryanmurray
Copy link

Glad I wasn't the only one. I'm gonna do the firmware upgrade. The hdop and vdop I'm seeing with the L1/l2/L5 antenna far exceed what I saw with the facet making the postcard a winning combo if we can get hrms and vrms

I use surpad but wasn't getting any RMS info so stumbled here

Image

@ryanmurray
Copy link

ryanmurray commented Jan 25, 2025

I flashed the release candidate from Jan 20th, v4 firmware from above, and enabled the gst message in the serial menu. I still get blanks and even though my PDOP is good surpad can't take a point.

@nseidle
Copy link
Member

nseidle commented Feb 5, 2025

As mentioned,

Note: GST is currently reporting single decimals so the accuracy during normal 3D Fix will look fine, but in RTK Fix mode, some GIS softwares (ie, SW Maps) will report an unknown lat/lon positional error because of this:

$GNGST,190701.500,0.7,0.0,0.0,85.7,0.0,0.0,0.0*4F

Error in GST is reported as '0.0' when really it's 0.013 (13mm). Their binary protocol confirms this but the GST message is cutting off those all important decimals. I've pinged Quectel to see if there's a remedy.

@ryanmurray
Copy link

Yes I was able to get 0.000 on surpad so that's solved. If quectel can fix it this chip is phenomenal for surveying. I mean it still is by RMS would be nice to see.

@ryanmurray
Copy link

Anyway to force minimum to equal 0.01 instead of rounding to 0.00? Field genius refuses to store points with no gst value

@nseidle
Copy link
Member

nseidle commented Feb 10, 2025

We could disable the GST sentence the module produces and produce our own GST sentence. Not something I really want to do since this is Quectel's fault. But if it's breaking compatibility with GIS software, I'll consider it.

@ryanmurray
Copy link

Yeah basically on most apps it prevents you from storing a position
On surpad I could get around it but field genius won't let you override the hrms or vrms with 0

I've told quectel we really need more decimals but who knows how long it will take.

The postcard would be a beautiful device if you could possibly fix this one little issue :D

@nseidle
Copy link
Member

nseidle commented Feb 10, 2025

if you could possibly fix this one little issue

Oh, I've heard that one before! We'll do our best :)

@mmoduu
Copy link
Author

mmoduu commented Feb 10, 2025

Should we just bombard Quectel forums? Nothing else we can do I guess?

@ryanmurray
Copy link

Should we just bombard Quectel forums? Nothing else we can do I guess?

I've been doing that and I think sparkfun has too.

nseidle added a commit that referenced this issue Feb 11, 2025
@nseidle
Copy link
Member

nseidle commented Feb 11, 2025

Quectel told me end of Q2 for the next firmware update that fixes the malformed GST sentence so I'm not willing to wait.

I've got a work around in place. It's not completely accurate, but we've extended the GST sentence to include 3 decimals.

Image

Above, GST with a RTK Fix that is waning. Note that the vertical error (that's the 0.066m that follows the two 0.033m fields) is basically made up. 0.033 is the LG290P's reported horizontal error for both the lat and lon error, and the 0.066 is double the horizontal error for the height error. This is just a rough hack until Quectel properly outputs the GST sentence.

Image

Above, SW Maps with a good RTK Fix.

While horzAccuracy * 2 is not correct, it should be good enough to allow GIS software (looking at you Field Genius) to be able to take points.

I haven't tested this on anything but SW Maps so please test today's (Feb 10) RC and let me know.

This work around will only operate on LG290P v4 firmware. So if you've got v3 (no support for GST) or v5 (the upcoming hopefully fixed GST firmware) this code won't run.

@ryanmurray
Copy link

Nathan you are my hero! Thank you for throwing this together that solution is perfect for the meantime. Sparkfun rocks!

@ryanmurray
Copy link

Tested out new RC it works for now :D

@nseidle
Copy link
Member

nseidle commented Feb 11, 2025

Glad to hear it's working! I pushed another small change to prevent this GST patch from being applied unless RTK Fix/Float is happening. I'd rather trust the original GST if the HPA is >0.1m. It's only when we're in the mm range that we need the extra decimals.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants