Welcome @byronarregui , Did you perform Step #4 within 20 seconds, as per the Guide
Also from the original post:
Welcome @byronarregui , Did you perform Step #4 within 20 seconds, as per the Guide
Also from the original post:
I wonder if you would need an arduino to send the reset command to put it in programming mode? or maybe thats in the quectel app?
upon reading the pdf it does not seem to mention it. Did you select the lg290p in the device setup portion of the app?
If I’m remembering correctly in QGNSS the firmware upgrade mode creates its own window so you should still have access to the QConsole window. Just send the reset command $PQTMSRR*4B when you need to. I think right after you send the new firmware.
Sorry for that, the issue was caused by using the wrong west longitude to look up the geoid separation table. It will be fixed soon.
Either send the reset command @jpb mentioned, or short the /RST pin (it is one of the pins next to PPS on that breakout board) momentarily to ground to reset the LG290P without disturbing the USB to serial chip.
Thanks @Jenn !
@rftop - Quectel has given us another beta. This should fix the orthometric height issue. Please give BETA0224 a try.
Is there some sort of secret incantation required in order to enable GST messages? I have successfully flashed BETA0224 to my LG290P, but nothing I am doing will enable GST.
$PQTMRESTOREPAR*13
$PQTMSRR*4B
$PQTMCFGFIXRATE,W,1000*59
(I’ve found messages go through more reliably if the rate is slowed a bit first, but I have tried with this on 10Hz to the same effect, but I often have to send the configuration string a few times before getting OK back)$PQTMSAVEPAR*5A
& $PQTMSRR*4B
$PQTMCFGMSGRATE,R,GST*13
this returns $PQTMCFGMSGRATE,OK,GST,0*59
$PQTMCFGMSGRATE,W,GST,1*0B
this returns $PQTMCFGMSGRATE,OK*29
$PQTMCFGMSGRATE,OK,GST,1*58
But there are no GST messages sent! I feel like I must be missing something here. I’ve also tried $PQTMCFGMSGRATE,W,1,1GST,1*
to enable on a specific UART, but I see the same behavior, and I’ve tried UART2 as well.
EDIT: Well, never mind! Apparently the GST messages were being sent, but for some reason neither SW Maps, QGNSS, nor PyGPSClient will decode them! I just had to pay closer attention to all the NMEA strings, and I was missing it. I decoded them by hand and as far as I can tell they are valid. Why can’t anything decode these?
Differential GNSS:
$GNGST,012744.000,1.387,1.323,1.108,55.688,1.259,1.181,2.692*44
RTK Fix:
$GNGST,013223.000,1.264,0.011,0.006,66.981,0.010,0.007,0.024*4F
I just now had a chance to test BETA 0224, on RTK V2.1 Final.
The Geoid issue is corrected
What command can I use to activate satellite display? I’ve updated to the version you mentioned, and the satellites automatically stop being displayed, but it continues to process NMEA data. On the Unicore UM980 module, the command that activates satellite display is GNGSV 1, but I’d like to know if there’s a similar one, the LG290P. Thanks.
Welcome @RobCosta ,
You are correct, the GSV sentence is what you’re looking for on the LG290P also.
Are you using a PostCard, or a different breakout board ?
On the PostCard, you would serial connect to it and check the NMEA Sentences, below are the defaults I believe :
Menu: Message NMEA
1) Message RMC: 1
2) Message GGA: 1
3) Message GSV: 1
4) Message GSA: 1
5) Message VTG: 1
6) Message GLL: 1
After updating the RTK Everywhere & the LG290P Firmware, this is how I normally setup my PostCards:
Menu: Message NMEA
1) Message RMC: 1
2) Message GGA: 1
3) Message GSV: 1
4) Message GSA: 0
5) Message VTG: 0
6) Message GLL: 0
7) Message GBS: 0 - Requires firmware update
8) Message GNS: 0 - Requires firmware update
9) Message GST: 1 - Requires firmware update
10) Message ZDA: 0 - Requires firmware update
FYI PyGPSClient version 1.5.5 or later can now parse and decode Quectel LG290P messages, via its underlying pynmeagps NMEA parser. PyGPSClient also supports the complete range of LG290P configuration commands. Check link below for further details:
e.g.
@semuadmin very exciting, thank you for the update! I’m looking forward to testing this out on my LG290P later. I’ll be so glad to not have to use QGNSS2 anymore.
In my case I had to send $PQTMSRR*4B just before I pushed the firmware upgrade button in QGNSS2.0
@semuadmin I’ve done a bit of testing with 1.5.5 and an LG290P now. I have been able to configure the module using the small panel to the right, but there are no presets listed for me - where do these come from? I’ve deleted the json configuration file but it didn’t make any difference.
Also, while the GNGST strings do now show up in the log window, the hacc/vacc values in the header remain at 0.00
RTK Fix:
<NMEA(GNGST, time=16:10:27, rangeRms=1.201, stdMajor=0.008, stdMinor=0.006, orient=91.973, stdLat=0.008, stdLong=0.006, stdAlt=0.032)>
No RTK: (3D)
<NMEA(GNGST, time=16:24:09, rangeRms=1.339, stdMajor=1.39, stdMinor=1.372, orient=117.341, stdLat=1.387, stdLong=1.376, stdAlt=2.818)>
(If it would be better for this to be an issue on the github repo, I can open one there instead.)
Thanks!
For anyone who is wanting to move off the beta firmware, the official v05 has been released with a smattering of improvements, including the fix for the GST bug. You can find the firmware zip here.
@sparky , thanks for that update !
I assume HAS E6 didn’t make it into 1A05S as we were all hoping ?
Unfortunately no, fixes using HAS are not in there yet (as far as I can see). But you can output raw HAS messages:
As already & previously mentioned the use of raw data is completely useless without a parser that makes them intelligible …
Please give a shot for quectel marketing & eng. staff or the only change is for lg680p module,
because of hardware limitation (IMHO) of the 290.
Regards