Unable to get the LC29HEA module to respond to any commands through QGNSS V2.0

Technical Subjects
1

Was able to connect and get NEMA data from the module with no problem.
as an example i just issued a cold restart command
$PQTMCOLD*
with checksum 1C and Advanced setting of ASCII / NEMA / CRLF
nothing happened.

[2024-11-07 19:19:27.175 Uart Rx:0254 B] $GNGGA,011930.300,3513.903327,N,09741.335228,W,1,34,0.53,402.8,M,-25.0,M,,*42
$GNRMC,011930.300,A,3513.903327,N,09741.335228,W,0.015,357.09,081124,,,A,V*2D
$GNGLL,3513.903327,N,09741.335228,W,011930.300,A,A*52
$GNVTG,357.09,T,,M,0.015,N,0.029,K,A*24
**[2024-11-07 19:19:27.206 Uart Tx:0014 B] $PQTMCOLD*1C**
[2024-11-07 19:19:27.283 Uart Rx:0276 B] $PQTMCOLD,ERROR,3*77
$GNGGA,011930.400,3513.903327,N,09741.335228,W,1,34,0.53,402.8,M,-25.0,M,,*45
$GNRMC,011930.400,A,3513.903327,N,09741.335228,W,0.015,357.09,081124,,,A,V*2A
$GNGLL,3513.903327,N,09741.335228,W,011930.400,A,A*55
$GNVTG,357.09,T,,M,0.015,N,0.028,K,A*25
[2024-11-07 19:19:27.379 Uart Rx:0254 B] $GNGGA,011930.500,3513.903328,N,09741.335228,W,1,34,0.53,402.8,M,-25.0,M,,*4B
$GNRMC,011930.500,A,3513.903328,N,09741.335228,W,0.017,357.09,081124,,,A,V*26
$GNGLL,3513.903328,N,09741.335228,W,011930.500,A,A*5B
$GNVTG,357.09,T,,M,0.017,N,0.031,K,A*2F
[2024-11-07 19:19:27.487 Uart Rx:0254 B] $GNGGA,011930.600,3513.903328,N,09741.335228,W,1,34,0.53,402.8,M,-25.0,M,,*48
$GNRMC,011930.600,A,3513.903328,N,09741.335228,W,0.018,357.09,081124,,,A,V*2A
$GNGLL,3513.903328,N,09741.335228,W,011930.600,A,A*58
$GNVTG,357.09,T,,M,0.018,N,0.032,K,A*23
[2024-11-07 19:19:27.581 Uart Rx:0254 B] $GNGGA,011930.700,3513.903328,N,09741.335228,W,1,34,0.53,402.8,M,-25.0,M,,*49
$GNRMC,011930.700,A,3513.903328,N,09741.335228,W,0.014,357.09,081124,,,A,V*27
$GNGLL,3513.903328,N,09741.335228,W,011930.700,A,A*59
$GNVTG,357.09,T,,M,0.014,N,0.026,K,A*2A
[2024-11-07 19:19:27.674 Uart Rx:0254 B] $GNGGA,011930.800,3513.903329,N,09741.335228,W,1,34,0.53,402.8,M,-25.0,M,,*47
$GNRMC,011930.800,A,3513.903329,N,09741.335228,W,0.009,357.09,081124,,,A,V*25
$GNGLL,3513.903329,N,09741.335228,W,011930.800,A,A*57
$GNVTG,357.09,T,,M,0.009,N,0.017,K,A*24
[2024-11-07 19:19:27.782 Uart Rx:0254 B] $GNGGA,011930.900,3513.903329,N,09741.335228,W,1,34,0.53,402.8,M,-25.0,M,,*46
$GNRMC,011930.900,A,3513.903329,N,09741.335228,W,0.012,357.09,081124,,,A,V*2E
$GNGLL,3513.903329,N,09741.335228,W,011930.900,A,A*56
$GNVTG,357.09,T,,M,0.012,N,0.022,K,A*28
[2024-11-07 19:19:28.012 Uart Rx:1806 B] $GNGGA,011931.000,3513.903330,N,09741.335228,W,1,34,0.54,402.8,M,-25.0,M,,*41
$GNRMC,011931.000,A,3513.903330,N,09741.335228,W,0.013,357.09,081124,,,A,V*2F
$GNGLL,3513.903330,N,09741.335228,W,011931.000,A,A*56
$GNVTG,357.09,T,,M,0.013,N,0.024,K,A*2F
$GNGSA,A,3,02,07,13,14,15,17,19,21,22,30,08,,1.06,0.54,0.91,1*0F
$GNGSA,A,3,66,67,68,75,76,77,85,86,87,,,,1.06,0.54,0.91,2*0C
$GNGSA,A,3,02,07,15,27,29,30,34,36,,,,,1.06,0.54,0.91,3*03
$GNGSA,A,3,19,27,28,30,36,37,,,,,,,1.06,0.54,0.91,4*0F
$GNGSA,A,3,,,,,,,,,,,,,1.06,0.54,0.91,5*0B
$GPGSV,3,1,10,02,41,076,43,07,43,143,29,13,32,287,38,14,61,332,45,1*6F
$GPGSV,3,2,10,15,08,309,17,17,57,231,42,19,26,225,42,21,29,057,30,1*60
$GPGSV,3,3,10,22,46,303,45,30,77,166,37,1*60
$GPGSV,1,1,03,08,06,048,25,14,61,332,43,30,77,166,44,8*5E
$GLGSV,3,1,09,66,09,239,20,67,15,289,18,68,04,335,17,75,19,100,38,1*76
$GLGSV,3,2,09,76,58,035,44,77,35,326,31,85,18,029,36,86,62,080,40,1*75
$GLGSV,3,3,09,87,43,172,35,1*4B
$GAGSV,2,1,07,02,10,083,22,07,29,217,35,15,32,146,30,27,50,309,44,7*7E
$GAGSV,2,2,07,29,31,281,26,30,54,049,41,34,38,080,39,7*46
$GAGSV,3,1,09,02,10,083,20,07,29,217,32,08,00,176,21,15,32,146,28,1*7A
$GAGSV,3,2,09,27,50,309,43,29,31,281,33,30,54,049,45,34,38,080,44,1*78
$GAGSV,3,3,09,36,09,034,25,1*40
$GBGSV,2,1,06,19,04,251,15,27,71,111,41,28,35,048,33,30,38,199,28,1*79
$GBGSV,2,2,06,36,24,308,27,37,40,107,38,1*70
$GBGSV,2,1,06,19,04,251,24,27,71,111,45,28,35,048,34,30,38,199,33,5*76
$GBGSV,2,2,06,36,24,308,32,37,40,107,42,5*7D
$GQGSV,1,1,00,1*65
$GQGSV,1,1,00,8*6C
$GNGGA,011931.100,3513.903330,N,09741.335228,W,1,34,0.53,402.8,M,-25.0,M,,*47
$GNRMC,011931.100,A,3513.903330,N,09741.335228,W,0.015,357.09,081124,,,A,V*28
$GNGLL,3513.903330,N,09741.335228,W,011931.100,A,A*57
$GNVTG,357.09,T,,M,0.015,N,0.028,K,A*25
[2024-11-07 19:19:28.075 Uart Rx:0254 B] $GNGGA,011931.200,3513.903330,N,09741.335228,W,1,34,0.53,402.8,M,-25.0,M,,*44
$GNRMC,011931.200,A,3513.903330,N,09741.335228,W,0.015,357.09,081124,,,A,V*2B
$GNGLL,3513.903330,N,09741.335228,W,011931.200,A,A*54
$GNVTG,357.09,T,,M,0.015,N,0.028,K,A*25

I have tried many different commands and get no reply.
From the screen the FW version is LC29HEANR11A03S_RSA
SN is P1Y24IM2H000013

It also shows:
11 GPS
6 BDS
9 GLONASS
8 GALILEO

but still does not show a fix mode.
It does show the Lat and Long except that the Longitude should have a - in front of it and it does not.
This appears to keep the map and 3d fix from working.

Can someone assist in a fix?

2

If you are using a Mozihao module, most likely you have one of the USB/UART switches in the wrong position. If you are using the USB connection, then BOTH switches should be towards the antenna connector.

Oh, and since you are a new member and will only be able to post 1 message in 24 hrs, let me also make sure that you are sending the command to the module by clicking on the arrow symbol, rather than pressing return…

On the longtitude, yes, QGNSS seems to omit the - on the data view and map view, but if you look at your GGA messages, it shows it correctly as West.

3

I have the switches in the correct position, and am using the arrow.
I also just found a link to QGNSS V1.10 and downloaded it and connected. It shows 3S fix and the correct Longitude so that is a bug in V2.0
The Online map is spot on as well.
when sending the same cold start command i now get an error

W->
   HEX: 24 50 51 54 4d 43 4f 4c 44 2a 31 43 0d 0a
String: $PQTMCOLD*1C

$PQTMCOLD,ERROR,3*77

which is something i did not get before.
Still not taking the command but at least responding in V1.10

4

If you are using the V1.3 LC29H Protocol Spec dated 24-03-12, it appears the latest released firmware is only at R11A03S_RSA,2023/10/31,16:52:14, so doesn’t support those commands yet. Quectel support has not released any firmware beyond that, which is strange, given that the spec is out…

As a new member, you are now limited in your ability to post anymore, so I am Messaging you my email, if you want to continue discussing. I know it was frustrating for me when I first got on here and couldn’t discuss issues further…

1 Like
5

using V1.10 I was able to switch the module to output RTCM3

Here is the module I have
Quectel LC29H High-precision LC29HEA RTK Board GNSS module LC29HEAMD LC29H-EA GPS L1 L5 GLONASS BDS Galileo - AliExpress 30

6

It hasn’t told me I can’t keep posting yet so - So far so good?
LOL
I was board and went through the “Training” with the discobot when i signed up so perhaps it’s cutting me a break…

Oh that time it said i had to wait 1 more min before posting again…

So basically I am trying to use this module to set up a base station.
Following this guy’s walkthrough for now, may be a better one out there somewhere of course.

This is my first real foray into the RTK space so I have a TONE to learn but that’s what keeps old men alive they tell me so here we go!

7

That’s good. Maybe doing the training did it. Your profile shows you as ‘Certfied’, so that may be it.

That guide does a good job on the steps. FYI, other than missing the - on the lon, which results in the map not working, QGNSS 2.0 seems to work fine for communication, setup, etc, so I don’t know why you needed V1.10 in order to finally send commands to it…

I play around with these RTK GNSS solutions as well, and have my own RTK Base station, as well as Rover applications, so feel free to post here. If I can help, I will…

1 Like
8

QGNSS V2.0 Fix for missing - in Longitude is to send $PAIR062,1,0* with checksum with Advance setting of Ascii / NEMA / CRLF
Sending $PAIR062,1,1* will set it back to default which removes the - for Western Longitude

This is the NMEA_SEN_GLL setting.

9

All this essentially does is disable the sending of the GLL message. Strange that disabling the GLL message would make QGNSS V2.0 display the Longitude correctly…

I tested this with the LG290P module as well and the same thing happens. However, all the apps I use don’t have a problem with GLL and displays the location correctly…I never noticed that QGNSS V2.0 didn’t display the - correctly as I had only used it to configure the module.

Good catch…I guess that’s why many people still use QGNSS V1.10. I know the firmware upgrade process is also broken in V2.0, so I keep V1.10 around as well…

10

Ok ran it in survey in mode with XYZ of 000 for well over 24 hours and the drift is down to about 1 meter in a 30 min time frame, just restarted the survey in mode with XYZ of the current reported XYZ so we will see if it gets any better.
Does this sound about right? From what I can tell there is not RTK base station I can access within 50+ miles so this si what I have to start from.

11

I’ve never used survey-in mode and I don’t know how accurate you can get, even after days of surveying. I was fortunate to have a public DOT owned RTK base within 4 miles of where I am, so I was able to get a very accurate position of my antenna. Of course, this only matters if you need ABSOLUTE position vs repeatable position ACCURACY. If all you need is repeatable position, then the absolute position of your Base is less important.

If you are trying to get absolute accurate position, then maybe what you can do is sign up for the free trial on this network:

https://pointonenav.com/states/oklahoma/

Once you’ve achieved RTK Fix on your base antenna, you can use the fixed survey-in mode with your accurate manually entered antenna location.

Hh, I forgot to add, the other way to get a more accurate base station location is to collect raw data for 24 hours and send it off for RINEX processing. I did this and compared it to my RTK Fix location and it was off more than I care to use. I’ve compared an absolute location on my property using the DOT RTK Base station, as well as my own Base station, using the manual RTK Fixed antenna location, and they are spot on, so I have confidence in the location…

12

Mainly I’ll be running rover mowers and quads / other rover stuff so repeatable acc would be what’s actually important. I hadn’t thought of that, If i get it wrong then it should just set the entire place to “off by that much” but equally so if i understand it correctly.

13

Yes, your rovers absolute position would be off by the same amount your Base position is off. Not an issue for what you’re doing..

Having said that, it would be nice if you could get temporary access to an accurate base station and lock in your absolute antenna position…