On May 16, 2018, at 15:01, Mark Sims wrote:
>
> Many thanks Peter for confirming what I suspected. The problem with the
> Trimble receivers is that requesting the satellite C/A code data can hose up
> a lot of them. So, I'm stuck with calculating the integer number of
> milliseconds. How
On May 16, 2018, at 13:58, Peter Monta wrote:
>
> "Code phase" represents where you are along the 1023-bit C/A code (each bit
> or "chip" of this code lasts ~1 microsecond or ~300 meters). The
> scaled-by-16 code phase will thus range from 0 to 16*1023. To get the full
> pseudorange, though,
Chris,
You don't need to do that. The SiLabs part will accept the 10MHz sin from an
OCXO directly into the XA pin. That pin normally connects to a crystal, so
there is a high gain amp in the chip to square it up already... I did the tests
a while back, see the thread here:
https://www.silabs
