QGNSS V1.10 does not seem to apply RTK data to LC29HEA fixes

DaleCKramer · May 31, 2024, 8:25pm

I have firmware LC29HEANR11A03S_RSA,2023/10/31,16:52:14*2B

I am connected to an RTCM3 NTRIP mount point and I am receiving RTK data every second but the RTK data does not seem to be applied to my fixes in QGNSS V1.10.

Any ideas why? Here is QGNSS V1.10 screenshot:

Thanks,
Dale

bamarcant · June 1, 2024, 10:50am

I think the latest firmware does…
I don’t know what is the matter, try some suggestion from this list.

$PAIR382,1*2E → Test command for lock system sleep enabled
$PAIR003*39 → power off GNSS system
$PAIR514*3A  Clear the current configuration and restore the default settings set via $PAIR
$PAIR512*3C  clear all data
$PQTMRESTOREPAR*13 # restore $PQTM params to default
$PAIR023*3B   reboot  module
$PAIR007*3D → Full cold start and clears system and user configurations
$PQTMGNSSSTOP*09  same of power off GNSS system
$PQTMCFGRCVRMODE,W,1*2A  # set receiver to rover mode
$PQTMCFGRCVRMODE,R*32  ask & get result
$PAIR863,0,0*37  ask & get bit_mask config [♣default is $PAIR863,1791*15 (DEFAULT)]
$PQTMSAVEPAR*5A # save PQTM params to flash

###for useful     $PAIR002*38 → power on GNSS system
$PAIR023*3B   reboot  module
$PAIR062,1,0*3F   # turn off GLL messages (1
$PAIR062,2,0*3C  # turn off GSA messages (2
$PAIR062,3,0*3D  # turn off GSV messages (3
$PAIR062,5,0*3B  # turn off VTG messages (5
$PAIR063,-1*0F  ask if done: see pos. after -1       $PAIR063,-1,1,0,0,0,1,0*0F
                                                                 0,1,2,3,4,5            
$PQTMCFGNMEADP,W,3,8,3,3,3,3*39  -->configure ALL to MAX decimals
$PAIR050,200*21 # set pos output interval to 200 ms
$PQTMCFGFIXRATE,R*71  ask & get result
$PQTMCFGFIXRATE,W,200*6A  same as set pos output interval to 200 ms
$PAIR753,1*26   enhance the PPS output timing accuracy but remove SBAS/QZSS effects)
$PQTMSAVEPAR*5A # save PQTM params to flash
$PAIR023*3B   reboot  module

####for testing
$PAIR410,1*22  enable sbas satellite 
$PAIR410,0*23  disable
$PAIR411*3E  ask
$PAIR400,2*20  enable sbas input dgps
$PAIR400,1*23   **enable rtcm correction input dgps**
$PAIR401*3F  ask & get status
$PAIR035*3C  get fix status
$PAIR864,0,0,460800*16 set baud 
$PAIR864,0,0,115200*1B
$PAIR865,0,0*31   Queries the baud of uart_port  and response. 
$PAIR062,0,1*3F  # Keep on GGA messages
$PAIR062,4,1*3B # Keep on RMC messages
$PAIR100,1,0*3A  1: **ASCII NMEA v4.1 output** only
$PAIR511*3F\r\n  Save current navigation data from RTC RAM to flash
$PAIR432,1*22\r\n ==> set RTCM3.x output with type MSM7  only in base_mode *but not save setting after reboot*
$PQTMCFGMSGRATE,W,PQTMEPE,1,2*1D          how accurate is the obtained position
$PAIR862,0,0,239*22  for base_mode special bitmask
$PQTMCFGSVIN,W,2,0,0,x,y,z*<Checksum> in ecef
$PAIR604,<Enable>,<Mode>,<Para1>,<Para2>,<Para3>*CS<CR><LF>
$PAIR604,1,0,x,y,z*<Checksum>  in ecef
$PAIR604,1,1,La,Lo,H*<Checksum>  in WGS84, (Lat,Lon,Height)
$PQTMCFGRTK,R*69   $PQTMCFGRTK,OK,1,1*3F     $PQTMCFGRTK,W,1,1*6C  default_set.
$PAIR473,1*27   Enable EPO flash aiding

DaleCKramer · June 1, 2024, 1:45pm

Where does the RTK base station data get applied to the GPS coordinates?

I would like to assume that the LC29HEA should receive the RTK NTRIP client data from the internet by USB and then combine it internally so that NEMA data that is output from the LC29HEA should be ~1CM fixes.

I have tried a bunch of your commands with no luck for getting RTK fixes but it is very curious that the setting for the fix rate to 200ms does not seem to work as shown here:

bamarcant · June 1, 2024, 4:40pm

what is the output, it seems not in rover mode…
rcvrmode
https://forums.quectel.com/uploads/short-url/gJTnPOK8MkEJIgLFR7QgjvrpUey.pdf
https://forums.quectel.com/uploads/short-url/ncdKSn5cRYyDbOpfYmvGGs1vEIA.pdf

DaleCKramer · June 1, 2024, 5:16pm

I have been using that last doc for EA model and I use online NMEA checksum calculator https://nmeachecksum.eqth.net/
I had already checked the rover mode (it was already in rover mode when I first queried it but I did it again, here is result:

bamarcant · June 1, 2024, 5:19pm

Ok, and now should do apply for 200ms…once rebooted or not?

DaleCKramer · June 1, 2024, 5:30pm

Here is a reboot and then again no ability to set to 200ms (no response from LC29HEA when attempted):

bamarcant · June 1, 2024, 5:55pm

Strange…can U print and redo PQTMVERNO*58 ?

DaleCKramer · June 1, 2024, 8:47pm

is

$PQTMVERNO,LC29HEANR11A03S_RSA,2023/10/31,16:52:14*2B

bamarcant · June 2, 2024, 7:21am

Hello Dale , it seems that your module has not ingested the new firmware…if after a new fw_update procedure U see no difference, open a new topic and describe the situation by saying what kind of evb card you have where you bought , what was the original fw etc. and explicitly request support in addition to an “[official
flash
]” firmware.
P.s. at least moves to 1hz with $PQTMCFGFIXRATE,W,1000*59 ?
let me know
Marco

DaleCKramer · June 2, 2024, 11:22am

Hi Marco,

But first, just another data point here…

This morning I woke up and just tried setting to 200ms again and surprisingly I got a response that confirmed it heard me and then requested the current fix rate status and it had appeared to change it to 200ms as you can see here:
FixRateUpdated

That was good news but when I filtered to RMC text data I was still receiving fixes at 100ms as you see here:
ButStillGetting100msFixes

I will now start a topic to ask for a link to latest firmware since I do not have any .cfg (etc) files…

Thanks,
Dale

bamarcant · June 2, 2024, 11:34am

Good for now, the native pair command should go directly to the new fix rate: $PAIR050,200*21 → set pos output interval to 200 ms 5 Hz , however save $PAIR513*3D save file system and reboot $PAIR023*3B reboot module for take effect.Later see message_box.
Bye
Marco