[teqc] Trimble RTX and teqc

Lou Estey lou at unavco.org
Wed Feb 21 10:15:42 MST 2018


hi John,

The response from Trimble's RTX support is basically void of information (since they
are not familiar with teqc and their response is pure speculation), so I suggest
first getting some real preliminary information:

On both the teqc-produced and Trimble utility-produced RINEX, run teqc with the
'-O.sum .' option and at least see which SVs and observables are in each RINEX
file.  (See https://postal.unavco.org/pipermail/teqc/2016/002204.html.)

Also, which options are you using with teqc to translate to the RINEX that
Trimble's RTX service?

--lou

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Louis H. Estey, Ph.D.              office:  [+001] 303-381-7456
UNAVCO, 6350 Nautilus Drive           FAX:  [+001] 303-381-7451
Boulder, CO  80301-5554            e-mail:  lou  unavco.org

"If the universe is the answer, what is the question?"
                                                 - Leon Lederman
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~


On 2018 Feb 21, 8:18 AM, John Hamilton wrote:
> If I convert a data file from a Trimble receiver (R10) using teqc and send it to the Trimble RTX service (PPP), it only uses the GPS satellites,
> and ignores the other constellations. But, if I convert to rinex using the trimble utility, it processes all of the constellations. So, I
> contacted RTX support, and here is the response I got back...
>
> I think the issue lies with using the teqc converter to convert your files to RINEX – I’m not intimately familiar with this tool, but perhaps
> there is a misconfiguration, or the RINEX file being generated is not standard.
>
> I always use teqc because I thought it would the the "most standard".
>
>
>
> --
> John Hamilton, PA PLS
> Terrasurv, Inc
> Pittsburgh, PA
> Voice: +1-412-341-5620
> Fax: +1-412-535-5185
> File Transfer: terrasurv.wetransfer.com <http://terrasurv.wetransfer.com>


More information about the teqc mailing list