Hello,
i recently ordered two Development boards with the LC29HBS and LC29HDA
The Firmware versions are:
$PQTMVERNO,LC29HBSNR11A01S,2023/02/13,10:13:06
$PQTMVERNO,LC29HDANR11A03S_RSA,2024/03/19,13:55:31
The RTCM1005 messages Sent by the BS are corrupted i think because decoding it results in the coordinates as x,y/2,z/4 compared to the Position in $PQTMCFGSVIN,R.
Also the DA returns only DGPS Fix when connecting to the BS. Connected to an open base from rtk2go it’s able to get RTK Float and Fix.
Is it possible to get the newest Firmware and instructions for both modules?
Best regards
Hi leonbru，
Both of your FWs are the latest. I am attaching a document here that may help with your setup. Please let me know if you have any questions.
GNSS RTK_Step_by_step_guide.pdf (3.6 MB)
BR,
June
Hello @June_Zhu ,
thanks for the provided Information. I was able to achieve a RTK Float fix with the modules in following Setup:
Raspberry Pi 4 connected with LC29HBS and rtkbase Running.
Raspberry Pi Zero 2w with LC29HDA and a NTRIP Client example in Python from Waveshare. Also connected the LC29HDA to a Laptop and used QGNSS. Both were able to get a RTK Float Fix.
Unfortunately i can only get a DGPS fix when i read the UART Data on the Pi4 directly from the BA-Module and forward the RTCM messages via TCP to the PiZero. The PiZero receives the TCP data and sends it via UART to the LC29HDA. Since i‘m using only one Base and one Rover which are located Close to each other, it would be Great to be able connecting them directly without a full NTRIP (Server/Caster/Client) setup and forward the messages via TCP between the two RPis. But it is my first project with GNSS-Moduls so i don’t know exactly why it gets RTK Float with the first setup but only DGPS when forwarding the messages 1:1. Are there more informations available for Custom Applications with these GNSS-Moduls or any idea how i could achieve a working solution in the Peer-to-Peer setup?
BR
Leon
Hi leonbru，
The difference between the successful and unsuccessful cases lies in how the RTCM data is transmitted. While rtkbase also uses TCP under the hood, it handles RTCM messages in a more professional and structured way. It ensures proper packaging, timing, and delivery of correction data. When using raw TCP transmission, there are several pitfalls to watch out for:
Message truncation
Multiple messages being concatenated (also known as packet sticking)
Transmission delays or inconsistent timing
RTCM messages may not be delivered to the module at the expected interval or in the correct order
BR,
June