Currently we have a new firmware version, but it still does not support OSNMA feature. The release for the OSNMA feature is estimated at around Q2 this year. I will send the latest firmware via email, please let me know if you have difficulty in downloading it.
Dear YongHuang
you seem to be the source for relevant files:
Hi there,
I somehow got my lc29h bs module confused trying to provide it with a Quectel-Lizenz/Activation für RTCM/RTK.
For this I issed a flash_download .cfg file with content
“0x08000000 0x100000 0xFFFFFFFF”
and send it with:
"flash_download.cfg,“QGNSS-V2.2-20260117104732526.fp”
Now green LED is not flashing any more and module is stuck.
Kindly send relevant files for firmware and Quectel-Lizenz/Activation für RTCM/RTK* mailto:mikadei2304@gmail.com
As next module on my way is LC29h DA, you may have latest relevant files for me too.
Thank you for sending over the latest firmware for the LC29HDA. I have successfully installed it, but I have a question regarding the Maximum Differential Age setting.
In the Release Notes document, there is a list of commands, including $PQTMCFGRTK (added in LC29HDANR11A02S_RSA). However, I can’t find any instructions in the Protocol Specification v1.4 on how to use this command.
I would like to change the Maximum Differential Age from the current default 120 seconds down to 10 seconds. Could you please clarify whether this is possible on the LC29HDA and, if so, how this setting can be configured?
The command for the LG290P is this $PQTMCFGRTK,W,1,1,10*41
but for the LC29H_v4 I doubt there is the timing feature, even on the v5 Quectel_LC29H(BA,CA,DA,EA)_DR&RTK_Application_Note_V1.5.pdf (2.0 MB)
U can read the setup with $PQTMCFGRTK,R*69
Regards
Or… here’s a novel concept… How about the company just make the firmwares available for download? This idea of having to request the firmware, and then wait for an email is REDICULOUS!
After updating the firmware on the LC29H-DA module, I can confirm that the device now obtains an RTK FIX very quickly. Previously, the module was not able to connect properly and did not achieve an RTK FIX.
It seems that the firmware update resolved the issue.