-
Notifications
You must be signed in to change notification settings - Fork 12
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
Comments
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.
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. |
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. |
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: Within 20 seconds, you have to reset the LG290P. Do this from system->hardware->13) LG290P reset for firmware update: 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:
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. |
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... |
Np! Glad it's coming together. Also, our RTK loader is available on Win/iOS/*inux. |
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. |
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. |
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. |
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. |
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?
The text was updated successfully, but these errors were encountered: