[teqc] Trimble RTX and teqc

Evon Silvia esilvia at quantumspatial.com
Wed Feb 21 15:17:43 MST 2018


I don't see L5 in your SUM files, but we've seen the Trimble conversion
software drop L2C when L5 records are present from a particular satellite.
This can be corrected by ensuring that you're writing RINEX 2.11 and not
RINEX 2.10, which is the default for the Trimble software. Moral of the
story is make sure you're using RINEX 2.11 in all conversion steps.

May or may not help in your situation, but it seemed relevant.

Evon

On Wed, Feb 21, 2018 at 12:36 PM, Lou Estey <lou at unavco.org> wrote:

> Ok, what we've learned here is that the Trimble conversion is
> including GPS L2C data and excluding GPS L2P(Y) pseudorange data compared
> to the default teqc translation.  (However, the Trimble translation
> must be including GPS L2P(Y) phase data because the RINEX L2 count
> is non-zero for the GPS SVs where the RINEX C2 count is zero.
> That's sort of odd ...)
>
> However, you say that the teqc-produced RINEX in the RTX processing
> is handling GPS ok, but not GLONASS.  For GLONASS, the big difference
> is the lack of G1SA phase data in the teqc-produced RINEX.  This is
> definitely not normal, but then again most of our GLONASS experience
> from Trimble receivers is from the NetR9, not an R10 like you are
> using.
>
> I guess this will take looking at the raw data file from R10, which
> you can email to me.  (Any short file will suffice.)
>
> --lou
>
>
> On 2018 Feb 21, 12:34 PM, John Hamilton wrote:
>
>> So here is the output from the trimble conversion:
>>           C1    C2    L1    L2    P2
>>          ----  ----  ----  ----  ----
>>     G01   240   240   240   240   240
>>     G10   240   240   240   240   240
>>     G12   232   232   232   232   232
>>     G14   240     0   240   240   240
>>     G22   240     0   240   240   240
>>     G25   240   240   240   240   240
>>     G31   240   240   240   240   240
>>     G32   240   240   240   240   240
>>     G26   170   170   170   170   170
>>     G03   154   154   154   154   154
>>     R02   240   240   240   240   240
>>     R03   240   240   240   240   240
>>     R04   240   240   240   240   240
>>     R12   170     0   170     0     0
>>     R13   240   240   240   240   240
>>     R14   240   240   240   240   240
>>     R15    82    82    82    82    82
>>
>> and the teqc conversion...
>>           L1    L2    C1    P2    S1    S2
>>          ----  ----  ----  ----  ----  ----
>>     G10   240   240   240   240   240   240
>>     G32   240   240   240   240   240   240
>>     G14   240   240   240   240   240   240
>>     G31   240   240   240   240   240   240
>>     G25   240   240   240   240   240   240
>>     G22   240   240   240   240   240   240
>>     G01   240   240   240   240   240   240
>>     G12   232   232   232   232   232   232
>>     G26   170   170   170   170   170   170
>>     G03   154   154   154   154   154   154
>>     R04     0   240   240   240     0   240
>>     R14     0   240   240   240     0   240
>>     R13     0   240   240   240     0   240
>>     R12     0     0   170     0     0     0
>>     R03     0   240   240   240     0   240
>>     R02     0   240   240   240     0   240
>>     R15     0    82    82    82     0    82
>>
>> I was not using any options, just teqc 42400510.tgd>42400510.18o. In the
>> past I always used -tr d but discovered that was not necessary
>>
> _______________________________________________
> teqc mailing list
> teqc at postal.unavco.org
> https://postal.unavco.org/mailman/listinfo/teqc
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://postal.unavco.org/pipermail/teqc/attachments/20180221/27936864/attachment.html>


More information about the teqc mailing list