Hi,
I get undescribed $PAIRxxx messages from my LC29H (BA):
$PAIR535,2,1,000000000400000012
$PAIR001,593,135
$PAIR001,593,034
$PAIR593,1,-12,-7,144,194,18,137,7,1813
$PAIR535,2,0,0000000000000008*1F
Is there any description available for $PAIR593 and $PAIR535?
Thanks
pstumbler
Hi Pstumbler,
PAIR535 is the notification of newly updated EPH.
PAIR593 query current UTC correction data.
Standard NMEA message is sufficient to judge the module state. It is suggested to ignore them.
Best regards.
Hi Raphael-Q,
Can you send me newly updated EPH please?
I’m using LC29HBS (Base) and LC29HDA (Rover), but when I try interface 2 module by UART on board, Base don’t send RTCM to Rover, Rover is sometimes only received
$PAIR001,593,135
$PAIR001,593,034
$PAIR593,0*29.
As document at homepage, those are not defined in description.
Thanks a lot guy
Hi Tu_Tang_Quang
You can ignore this statement. If the constellation can be searched, the module will automatically download the latest ephemeris information.
- LC29HBS only outputs RTCM, and you cannot see NMEA statements such as GGA and RMC.
- LC29HDA is an RTK project. You can directly connect the TX of LC29HBS and the RX of LC29HDA. Then connect LC29HDA through the serial port tool. If LC29HDA can enter the RTK state (the bit of the GGA statement becomes 4 or 5.), it means that LC29HBS is working properly.
- You can also use the RTKLIB tool to parse the RTCM data to check whether LC29HBS is working properly.