[teqc] corrected version of teqc on-line (6 June 2012)

Lou Estey lou at unavco.org
Wed Jun 6 11:32:36 MDT 2012


A rare post-"Venus transit" event!  A re-release of teqc!  Get rid of
the 25 May 2012 version (now!), and get this reissue for 6 June 2012:


As usual, save a copy of your current executable in case there is some
unexpected problem with the new executable.

Three things were fixed from 25 May:

* a set of missing flags caused the reading of Javad JPS and Topcon TPS
formats to output the GPS L1 phase, SNR, and doppler observables from
the GPS L1P(Y) signal rather than from the L1C/A signal by default or
even if trying to override with the '+CA_L1' option (note: other GPS
signals, and signals from other constellations were not effected)

* the reading of GLONASS phase from BINEX 0x7f-03 was not correct in
the 25 May version or any earlier versions, all builds (note: the
coding error also caused the 25 May Borland build for Windows to
give a floating point exception error when trying to read GLONASS
data in BINEX 0x7f-03)

* the reading and writing of BINEX 0x7f-03 would not have been correct
for the HP-UX native compiler build for the 25 May version (note: the
gcc-compiled build for HP-UX would have been correct, except for the
GLONASS phase problem mentioned above)

One new item was added:

* added auto-identification of the Trimble GNSS-Ti chokering antenna
(TRM59900.00) in the pertinent records of a Trimble .dat/.tgd file

All previous fixes and changes from 11 Oct 2011 reported for the 25 May
builds also apply, and are repeated here for completeness:

* The code has been readied for the next insertion of a leap second into UTC
(which occurs in the last minute of 30 June 2012).  This next leap second
will be the first mid-year leap second insertion since 30 June 1997.
Data management facilities may want to consider testing and switching to
this version of teqc prior to 1.0 July 2012.  (We've been testing essentially
the same code here at UNAVCO on Solaris Sparc and Solaris Intel/x86 for
about the last month, and have had no significant problems, just a couple
minor tweaks that have been made for this release.)

* There were a couple of GLONASS orbit issues in the last release (e.g. one
involving an infrequent floating point exception fault that only occurred
on Windows). From what we can tell, and from users who have been trying out
interim builds with fixes for the problems that were found, all is well.

* A gcc 4.2 build for Mac OSX Intel/x86 10.6 (Snow Leopard) and 10.7 (Lion)
is available:


* If you are using Mac OSX 10.5 (Leopard) or 10.6 (Snow Leopard) with a
PowerPC processor or with an Intel/x86 processor and have Rosetta installed
(so that you can run PPC executables), then two other builds are available,
one compiled with gcc 3.3 and one with gcc 4.0:


Our recommendation is to try the one compiled with gcc 4.0, and only
use the one compiled with gcc 3.3 as a fallback.  (So if you are running
OSX 10.6 with an Intel processor and have Rosetta installed, then you have the
option of using three executable builds for this release; we recommend
starting with the one compiled with gcc 4.2 on an Intel platform in this case.)

* Reading and writing of BINEX 0x7f-03 (supported, for example, by Javad
Triumph-1, Delta, Sigma, and Alpha receivers and Trimble NetRS, NetR3,
NetR5, NetR8, and NetR9 receivers) has been totally overhauled to
fully support the 0x7f-03 extensions proposed by Javad last year for
Galileo/GIOVE, Beidou-2/Compass, and QZSS, and to correct some previous
errors for GLONASS.

* This version of teqc should be able to read QZSS and Beidou-2/Compass from:
     - BINEX 0x7f-03 and 0x7f-05
     - Trimble RT27 .tgd (and maybe from 0x57-6 -- untested)
     - Javad JPS

(Topcon TPS, Leica MDB, and Septentrio SBF will be reviewed and updated
after the next release.)

For example, you will be able to get a good picture of what observables
were tracked in all constellation by using '+C2 +L5 +L6 +L7 +L8 -O.sum .'

The problem here is RINEX 2.11, which officially does not include QZSS or

official 2.11:
  | GPS     L1         1575.42     C1,P1       L1         D1         S1       |
  |         L2         1227.60     C2,P2       L2         D2         S2       |
  |         L5         1176.45      C5         L5         D5         S5       |
  |                                                                           |
  | GLONASS G1         1602+k*9/16 C1,P1       L1         D1         S1       |
  |         G2         1246+k*7/16 C2,P2       L2         D2         S2       |
  |                                                                           |
  | Galileo E2-L1-E1   1575.42      C1         L1         D1         S1       |
  |         E5a        1176.45      C5         L5         D5         S5       |
  |         E5b        1207.140     C7         L7         D7         S7       |
  |         E5a+b      1191.795     C8         L8         D8         S8       |
  |         E6         1278.75      C6         L6         D6         S6       |
  |                                                                           |
  | SBAS    L1         1575.42      C1         L1         D1         S1       |
  |         L5         1176.45      C5         L5         D5         S5       |

However, we're going to allow you to do so, using an "extended" 2.11, which will
also allow for GPS L1C (which won't be available for a few years yet) and
GLONASS L3 (available only from GLONASS-K, which currently is only GC # 701,
which is still in 'flight tests' and not part of the official constellation),
reusing the same set of two-character observable designations:

2.11 "extended":
  | GPS     L1C        1575.42      C7         L7         D7         S7       |
  |                                                                           |
  | GLONASS G3         1202.025     C7         L7         D7         S7       |
  |                                                                           |
  | Compass B1/E2  I/Q 1561.098     C1         L1         D1         S1       |
  |         B2/E5b I/Q 1207.14      C7         L7         D7         S7       |
  |         B3/E6  I/Q 1268.52      C6         L6         D6         S6       |
  |         B1-2/E1I/Q 1589.742     C2         L2         D2         S2       |
  |                                                                           |
  | QZSS    L1C/A      1575.42      C1         L1         D1         S1       |
  |         L1C        1575.42      C7         L7         D7         S7       |
  |         L1-SAIF    1575.42      C8         L8         D8         S8       |
  |         L2C        1227.60      C2         L2         D2         S2       |
  |         L5 I/Q     1176.45      C5         L5         D5         S5       |
  |         LEX S/L    1278.75      C6         L6         D6         S6       |

You will need to use '+relax' to get out QZSS and/or Beidou-2/Compass observables
in 2.11 "extended" RINEX obs.  Such files are for your own use and should not
be disseminated.

We'll send out a separate note soon as what receivers are actually tracking.

* Galileo/GIOVE and QZSS ephemerides can be output to a 2.xx-like format (again,
unofficial), and these can be extracted from:

     - BINEX 0x01-04 (Galileo/GIOVE) and 0x01-06 (QZSS)
     - Trimble .tgd record 28 (and maybe from 0x55-9 -- untested)
     - Topcon TPS and Javad JPS [EN] (Galileo/GIOVE)
     - Javad JPS [QE] (QZSS)

(Again, Topcon TPS, Leica MDB, and Septentrio SBF will be reviewed and updated
after the next release.)

To create the 2.xx-like RINEX nav files for Galileo/GIOVE and QZSS, the '+nav'
option was extended:

+nav[file(s)] list   output any NAV records in native format to RINEX filename 'list'
                      where 'list' == system filename(s) ordered GPS[,GLONASS[,SBAS[,Galileo[,-,QZSS]]]]
                      (or use - or _ to omit a specific system)

(Note: The spot between Galileo and QZSS is a placeholder for Beidou-2/Compass.)

Automatic creation of these additional RINEX 2.xx nav files has also been added
to the '-tbin' option.

A note on the Galileo IOV navigation messages: The last time checked (about
three weeks ago) the two IOV SVs were not broadcasting complete navigation
messages: all the clock parameters (af0, af1, and af2) and all the perturbation
parameters (Crs, Crc, Cus, Cuc, Cis, Cic) were zero, and the SV health was
likewise set to "unhealthy".

* qc has been extended to allow input of 2.11 "extended" RINEX obs (automatically;
no need to include '+relax'), and:
     - the 2.xx RINEX nav files for Galileo/GIOVE and/or QZSS can be used
       and, if so, the SV positions are calculated and used
     - the qc for QZSS is done the same as for GPS, allowing mp1, mp2,
       mp15, mp51 and so on (using the *1, *2, and *5 observables defined
       above the the 2.11 "extended"
     - the 'N' designator in the ASCII time plot for GLONASS data with
           no frequency channel number has been extended for Beidou-2/Compass
           data -- so you can see where there is Compass data, but no qc
           is done on the measurements yet

Happy teqc-ing!

--lou & stu

p.s. Thanks to the several groups and individuals who quickly found and reported
the problems that are now fixed: Leica, NGS/CORS, and JPL.

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
    WWW:  http://www.unavco.org   http://jules.unavco.org

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

Stuart Wier, Ph.D.                 office:  [+001] 303-381-7538
UNAVCO, 6350 Nautilus Drive           FAX:  [+001] 303-381-7451
Boulder, CO  80301-5554            e-mail:     wier  unavco.org
http://www.unavco.org              http://geon.unavco.org/

More information about the teqc mailing list