[teqc] Re: teqc Digest, Vol 89, Issue 3

Lou Estey lou at unavco.org
Wed Oct 12 07:47:16 MDT 2011


On 10/11/2011 10:00 PM, Guilherme Poleszuk wrote:
> Yesterday the TEQC users received a big surprise! The latest version of TEQC
> is available with several improvements (cooming soon PPP too?).

I don't know about soon, but, yes, hopefully PPP improvements will
be in the future.

> I'd like to ask about RT27 data conversion (again!).
>
> When I type
>
> teqc -G1-24,26-32 -R -S -E +L5 -O.obs L1L2L5 recv285d37.11rt27 | more
>
> TEQC translate it (I'm cutting header information to be more objective)
> (where is L2?! Please, wait and see the next test...)
>
>    2011    10    12     3    36   58.0000000     GPS         TIME OF FIRST OBS
>                                                              END OF HEADER
>   11 10 12  3 36 58.0000000  0  1G25
>   109996403.390 9                  82140209.297 9
>   11 10 12  3 36 59.0000000  0  1G25
>   109994672.677 9                  82138916.877 9
>   11 10 12  3 37  0.0000000  0  1G25
>   109992942.220 9                  82137624.658 9
>
> But, when I type
>
> teqc -G1-24,26-32 -R -S -E +L5 -O.obs L1L2L5C1C2C5 recv285d37.11rt27 | more
>
> TEQC (as I expected!) translate it (I'm cutting header information, again, to be more objective)
>
>    2011    10    12     3    36   58.0000000     GPS         TIME OF FIRST OBS
>                                                              END OF HEADER
>   11 10 12  3 36 58.0000000  0  1G25
>   109996403.390 9  85711387.918 8  82140209.297 9  20931597.156    20931609.250
>    20931608.621
>   11 10 12  3 36 59.0000000  0  1G25
>   109994672.677 9  85710039.313 8  82138916.877 9  20931267.813    20931279.906
>    20931279.273
>   11 10 12  3 37  0.0000000  0  1G25
>   109992942.220 9  85708690.902 8  82137624.658 9  20930938.516    20930950.605
>    20930949.973
>
> My question: Why, in the first command, I got only L1 L5 (not L2!) and, in the second
> command I got L1L2L5, when I add the parameters w.r.t codes (C1C2C5) in the key -O.obs?
> Are Codes necessary to TEQC extract L2 or I'm committing a foolish mistake?

First, before answering, including the option '+L5' really has no impact
on either of the above two commands.  The options '+L5' and '+C2' are
just shortcuts -- if they have been coded for the format being used -- so
that the following observables will be additionally included if and only
if an observable list is not supplied with -O.obs:

'+L5' => include L5, C5, S5
'+C2' => include C2 (GPS L2C code pseudorange); and when C2 is present
          the L2, S2, and D2 values will also be from L2C tracking, otherwise
          the L2, S2, and D2 values are from L2P(Y) tracking as usual

Second, before answering, after some quick tests it appears that '+L5' did
not make it as a shortcut when reading Trimble formats.  ('+C2' works fine
for Trimble formats.)  Workaround: use -O.obs.

Now to answer your question:

No, it not necessary to include the corresponding pseudorange codes to get the
phase values.  Here's an RT27 .tgd file from a NetR9:

[2116] teqc +quiet -O.obs l1+l2+l5 CUT2201009300200a.tgd | more
      2.11           OBSERVATION DATA    M (MIXED)           RINEX VERSION / TYPE
teqc  2011Oct11     Lou Estey           20111012 13:20:50UTCPGM / RUN BY / DATE
...
      3    L1    L2    L5                                    # / TYPES OF OBSERV
...
                                                             END OF HEADER
  10  9 30  2  0  0.0000000  0 23G24G19R23G31G22G32R08R07R22G17R01G14
                                 G11G06G20G03R09R16R24R10G23E51E52
  107832572.998 8  84025393.96647
  112147033.976 8  87387289.14846
  104905120.524 8  81592883.014 8
  122412140.715 7  95385981.59845
  133317954.065 6 103884155.68742
  109757424.219 8  85525310.88047
  107960391.151 8  83969196.438 8
  120107804.478 7  93417178.605 6
  114663165.957 7  89182459.359 7
  132675875.238 5 103383817.88042
  115212863.150 7  89609907.596 6
  118531206.728 7  92361967.34645
  112991834.234 8  88045644.95846
  130254403.521 5 101496882.45043
  115799042.223 8  90233223.62046
  122438476.599 6  95406627.81043
  123229919.793 6
  123478563.561 7  96038925.707 6
  117114498.318 7  91089074.542 7
  121186587.300 7  94256212.174 5
  123890540.152 7  96538128.36144
  130693614.887 7
  141171992.300 6                 105421751.246 5

I'd have to get your file recv285d37.11rt27 to see what's going on, because
given how you collected it below, the format is definitely Trimble's streaming
format, not their .dat/.tgd format:

> Details about my experiment with TEQC (2011Oct11)
>
> RT27 data streaming of Trimble NetR8 receiver were collected under Windows XP SPIII using
>
> lynx -dump -mime_header http://receiver_ip:port > recv285d37.11rt27
>
> TEQC version
>
> C:\Temp\teqc20111011>teqc -ver
> executable:  C:\Temp\teqc20111011\teqc
> version:     teqc  2011Oct11
>*build:       MSXP|IAx86-PII|bcc32 5.0|MSWin95->XP|486/DX+
>
> I think that I saw it in previous TEQC versions, but never sent a message to you reporting this "event".

Well, if users don't report things, then problems go undetected and don't
get fixed.

cheers,
--lou


More information about the teqc mailing list