[time-nuts] Thunderbolt code phase measurement
D. Jeff Dionne
Jeff at SE-Instruments.co.jp
Wed May 16 02:10:59 EDT 2018
On May 16, 2018, at 15:01, Mark Sims <holrum at hotmail.com> 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 to do that? I do know my position to a few feet.
You can calculate the location of the SV from it's Ephemeris given the time of the set of Observations.
Another Oh! Can the TBolt be made to send us Ephemeris data? If so, and if it will also give Code Phase, I'd like a simple way to get that in a compact structure and onto our local LAN from the machine running Heather :)
> I have Lady Heather generating RINEX files for the Ublox timing receivers, the NVS-08, the Furuno GT-87, and the Ashtech Z12 (with both L1/L2 data). It would be nice to be able to support the Trimble receivers. With L1 only data I am getting results in the < 200 mm range. The Z12 with L1/L2 data gets me to around 40 mm.
>> If you know your position to within 150 kilometers (0.5 ms), you can
> dispense with the pseudorange-assembly arithmetic and just use the code
> phase directly, after adding in the appropriate integer number of
> milliseconds, only one of which will put you within your known
> 300-kilometer-diameter (1 ms) sphere.
> time-nuts mailing list -- time-nuts at febo.com
> To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
> and follow the instructions there.
More information about the time-nuts