RTCM1004 and RTCM1077 pseudo-range fields don't match .. ? #759
Unanswered
jonathanmuller
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
First of all thank you a lot for all this amazing project.
I'm trying to use RTCM message from a local basestation to calculate the location of my receiver using DGPS and state of the art algorithm.
I had success using RTCM1004 message, but not RTCM1077, even if their fields should contain the same value, but with different accuracy (if I understand correctly).
Here is my logic, and where is fails :
I'm looking at RTCM1004 and RTCM1077 messages from the same base-station, recorded at the same time, and compare the signal from the same satellites. I expected the pseudorange from both message (for the same satellite) to be the same, within few millimeters. However, There seem to have a problem with the DF405 field, or the way I use it.
Index 1 of RTCM1004 matches index 5 of RTCM1077, both are satellite 15
0.640625*299792458/1000=192054.54340625
4.433095455169678e-05*299792458/1000=13.29...
It looks to me : the time, PRN, etc, all match. But for some reasons DF405 is completely ... random ?
I'm probably using it wrongly, but based on RTCM documentation it looks like the full range was divided into smaller fields : DF397, DF398 and DF405
What am I doing wrong, are RTCM1004 and RTCM1077 not representing the same "kind" of pseudo-range ?
Full code to replicate, with output.
Beta Was this translation helpful? Give feedback.
All reactions