I wish I would have seen this post. I bought the same board and having the exact same issues as extin and santh. I’m hoping support can give us some direction. I’ll post my serial number and have them check if it’s a legit module.
This is what QGNSS returns with $OPTIVERNO query: $OPTIVERNO,LG290_SDK.1.2.5a_GNSS.1.1.9,2024/12/20,18:24:13*6D
Here’s what I get for a unique ID:
$OPTIUNIQID,OK,8,00001C023EBBD110*6E
Support,
Please let me know if this is legit and what I need to do to resolve getting the correct FW.
Thank you!
(post deleted by author)
Nope, I’t didn’t work commanding a software reset either.
I used a separate serial port for sending the command. Tested the firmware update on UARTs 1 and 2. The QGNSS always reports the sync error after 20s of trying, Sync the serial failed,err: 0x400. I can see the tool sending the sync packets but the LG290P does not respond.
Bummer.
So it would seem that the update protocol might be different as well.
Seems that only option is that we get support from Quectel.
Just noticed, that your FW version is newer than mine, I have LG290_SDK.1.2.0_GNSS.1.1.6,2024/11/18,20:06:08.
I also received similar board that extin has. Difference is that the commands seem to be not working:
[2025-04-06 10:46:37.224 Uart Tx:0012 B] $OPTIVERNO
[2025-04-06 10:46:37.290 Uart Rx:0086 B] $OPTIVERNO$command,$OPTIVERNO,response: PARSING FAILD NO MATCHING FUNC $OPTIVERNO*60
[2025-04-06 10:45:03.301 Uart Rx:0080 B] $PQTMVER$command,$PQTMVER,response: PARSING FAILD NO MATCHING FUNC $PQTMVER*60
[2025-04-06 10:48:25.238 Uart Tx:0013 B] $PQTMUNIQID
[2025-04-06 10:48:25.319 Uart Rx:0089 B] $PQTMUNIQID$command,$PQTMUNIQID,response: PARSING FAILD NO MATCHING FUNC $PQTMUNIQID*60
All PQTM command need to start $OPTI, eg. if the command is $PQTMUNIQID it has to be changed to $OPTIUNIQID.
And you need to turn on NMEA checksums:
In console right bottom there’s Advance->Checksum->NMEA.
Then the console will add correct checksum to the message. See attached picture. And you need to add asterisk, * to the end of command for the checksum to be calculated.
1 Like
Thank you!
[2025-04-06 22:20:19.032 Uart Tx:0015 B] $OPTIVERNO*42
[2025-04-06 22:20:19.097 Uart Rx:0063 B] $OPTIVERNO,LG290_SDK.1.2.5a_GNSS.1.1.9,2024/12/20,18:24:13*6D
For those of us with the Alternative FW, I can’t get the $OPTICFGMSGRATE,W,OPTISVINSTATUS,1* to work after successfully running the Survey In option. Are you running into this problem?
Thank you!
Prova con
$OPTICFGMSGRATE,W,OPTISVINSTATUS,1,1*58
$OPTICFGMSGRATE,W,OPTISVINSTATUS,0,1*59
Enable the Survey-In observation results
$PQTMCFGMSGRATE,W,PQTMSVINSTATUS,1,1*58
Disable the Survey-In observation results
$PQTMCFGMSGRATE,W,PQTMSVINSTATUS,0,1*59
My apologies, I did enter $OPTICFGMSGRATE,W,OPTISVINSTATUS,1,1*58 and received the “OK” message, but the messages never appear. I was hoping that this new module requires other commands to view it or enable it.
One other thing, the $OPTIVER query does not work on this module with this FW, however, it does return “version” when I use $OPTISRR.
Can you please forward the FW to my email. Thank you!
What output am I supposed to be seeing for $OPTICFGMSGRATE,W,OPTISVINSTATUS,1,1*58?
I might be mistankenly misreading the data Im seeing.
After enable and done e.g ```
$PQTMCFGSVIN,W,1,3600,15,0,0,0*23
Set the Survey-In observation for 3600 s
vinstatus is for ```
Look at <MeanAcc> survey-in mean position accuracy in metres
$PQTMSVINSTATUS,1,383462000.0,2,,55,1,0,X.8019,Y.8467,Z.4197,0.1108*0D
``` where 0.1108 is the accuracy obtained because I have inject ntrip corrections also in base mode
so it is unuseful if done only in single mode...the result return a mediated average only.
Imho need an rtk fix for set a base properly
$PQTMCFGSVIN,W,2,0,0,X704517.8019,Y298190.8467,Z093137.4197*cheksumAs I suspected, it’s not working for me.
Hello Quectel Support team,
Any chance you can provide support regarding the FW update from LG290_SDK versions to the latest LG290 firmware?
$OPTIVERNO,LG290_SDK.1.2.5a_GNSS.1.1.9,2024/12/20,18:24:13*6D
Thanks in advance!
After some back and forth with my board supplier it seems that the board is a mix with an Unicore UM960/UM980. I don’t know if the hardware is a LG290P but with Unicore firmware or if it is a UM960/980 with a Quectel rebrand.
The board responds to many commands from the “NebulasIV High Precision Products” that confirm the firmware is based on the Unicore one.
[2025-04-11 13:34:40.641 Uart Tx:0010 B] VERSIONA
[2025-04-11 13:34:40.720 Uart Rx:0187 B] $command,VERSIONA,response: OK*45
#VERSIONA,84,GPS,FINE,2361,473698900,0,0,18,18;"LG290","LG290_SDK.1.2.5a_GNSS.1.1.9","20381121","12141001010","00006FE9326C38D1","2024/12/20"*38B26E89
Also my board supplier did send me a firmware update tool that works, but does not consider the Quectel firmware package as valid. It only does work with the “opti_gnss.pkg” they sent me.
Now I wonder what I actually bought and what performance should I expect …
I’ve been working with my supplier to. I found the exact same findings.
I had the exact same experience. The seller also sent me opti_gnss.pkg along with a program.
On the positive side, RTK worked quickly and achieved a fix rapidly.
But the question remains: What hardware is it? 
LGXX0P高精度模组产品数据接口协议-20250401.pdf (906.8 KB)
Updated to English