[teqc] helpful tip of week 1964

Lou Estey lou at unavco.org
Wed Aug 30 13:42:13 MDT 2017

This week's tip: the '+eds' options

The '+eds' options are for outputting any "external data strings" that might
be in the raw data being read by teqc:

[1992] teqc +help | grep eds
         +eds .               output any external data string to stdout
         +eds ..              output any external data string to stderr
         +eds name            output any external data string to file 'name'
         ++eds name           append any external data string to file 'name'
         -eds                 don't output external data strings (default)

where the command options above follow the same form as several other options
that have been discussed so far for outputting special parameters, e.g.:

    o '+rx_state' (receiver state parameters) 'tip of week 1926'

    o '+psp' (position solution parameters) 'tip of week 1938'

    o '+diag' (parsing diagnostics) 'tip of week 1939'

What's an "external data string"?  Many higher-end receivers allow for the
input/output, usually via an RS-232 interface, of communicating with one
or more external devices.  A common example is an external meteorological
unit, or "met pack".  The "external data string" from a met pack is the
ASCII string recorded by the receiver for that I/O exchange, often showing
the command string sent to the device and the result string returned to
the receiver from the device.

Here's an example of Trimble .dat file from a NetRS with an attached Vaisala met pack,
using '+eds .' to output the external data strings, as recorded by the NetRS, to stdout
(and also using the '+mds' option to merely suppress creation of RINEX):

[2008] teqc +quiet +eds . +mds *.dat
eds: '514801|0R0|0R0,Dm=327D,Sm=4.3M,Ta=-28.9C,Ua=27.8P,Pa=0.6105B,Rc=0.00M,Hc=0.0M'
eds: '515101|0R0|0R0,Dm=334D,Sm=3.9M,Ta=-28.9C,Ua=27.9P,Pa=0.6105B,Rc=0.00M,Hc=0.0M'
eds: '515401|0R0|0R0,Dm=330D,Sm=4.3M,Ta=-28.8C,Ua=27.9P,Pa=0.6104B,Rc=0.00M,Hc=0.0M'
eds: '515701|0R0|0R0,Dm=338D,Sm=4.4M,Ta=-28.9C,Ua=27.9P,Pa=0.6104B,Rc=0.00M,Hc=0.0M'

Each line of output has the form: "eds: '<string>'".  The <string> in single-quotes
is what the receiver stored.  In this case from the NetRS, the string has three parts
separated by the '|' character: (1) the GPS time in seconds of current GPS week, (2)
the command sent to the Vaisala met pack, and (3) the string returned from the Vaisala.
(The format of the meteorological observables depends on a configuration setting of
the Vaisala met pack.)

And here's an example of a Trimble .tgd file from a NetRS with an attached tilt meter unit:

[2042] teqc +quiet +eds . +mds *.tgd
eds: '309600|*9900XY|$YXXDR,A,-07.485,M,N,A,004.445,M,E,C,05.20,C,T-N7053*49'
eds: '309660|*9900XY|$YXXDR,A,-07.033,M,N,A,004.842,M,E,C,05.20,C,T-N7053*4B'
eds: '309720|*9900XY|$YXXDR,A,-07.519,M,N,A,004.602,M,E,C,05.21,C,T-N7053*4D'
eds: '309780|*9900XY|$YXXDR,A,-07.505,M,N,A,003.976,M,E,C,05.19,C,T-N7053*40'

UNAVCO permanent GNSS stations have had various types of external devices attached to
receivers where one can extract the I/O strings in this way:
    o met packs
    o tilt meters
    o pore-pressure sensors
Other external devices are certainly possible.  If there are multiple devices on the
receiver, the eds output shows the strings from all the various devices in the order
that the strings are encountered in the input file.

Currently, the '+eds' options can show you the external data strings that would be in:
    o Ashtech D-file (from B/E/S/D fileset)
    o Ashtech R-file record 6
    o Ashtech U-file "D" (external data) record
    o Ashtech XDR ("eXternal Data Record") NMEA in MBEN/PBEN stream format
    o BINEX 0x00 comment string (but if and only if format of device is known)
    o BINEX 0x7e-01
    o Javad JPS and Topcon TPS [>>] message
    o Septentrio 4075 record in SBF
    o Trimble .dat/.tgd record 16, subtype 254
    o Trimble 0x57-3 in RT17/RT27 stream
(These are all the ones I know about.  If there are other cases for formats that teqc
can read, let me know and I'll try to add them.)

Perhaps at this point you are saying to yourself, "Well, I always use the '+met'
option to create a RINEX met file to see the meteorological data."  That's fine.
But it's important to understand the main differences between using '+eds' and '+met'.
The '+eds' options show the user all external data strings, as recorded by the receiver,
and the '+met' option shows the user only met external data strings, parsed (if possible)
by teqc and written out in the RINEX met file specification.  So both are useful,
depending on what you need to look at.

Happy teqc-ing!


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

Past helpful tips:

week 1894: using teqc config files - http://postal.unavco.org/pipermail/teqc/2016/002067.html
week 1895: qc of high-rate data - http://postal.unavco.org/pipermail/teqc/2016/002071.html
week 1896: UNIX/Linux shells for Windows - http://postal.unavco.org/pipermail/teqc/2016/002072.html
week 1897: '-' vs. '+' teqc options - http://postal.unavco.org/pipermail/teqc/2016/002076.html
week 1898: auto-identification of formats - http://postal.unavco.org/pipermail/teqc/2016/002092.html
week 1899: auto-identification vs. format flags - http://postal.unavco.org/pipermail/teqc/2016/002096.html
week 1900: square brackets in options - http://postal.unavco.org/pipermail/teqc/2016/002105.html
week 1901: using option '+mds' - http://postal.unavco.org/pipermail/teqc/2016/002108.html
week 1902: qc results w/ problematic nav messages - http://postal.unavco.org/pipermail/teqc/2016/002113.html
week 1903: '-no_orb[it]' and '-no_pos[ition]' options - http://postal.unavco.org/pipermail/teqc/2016/002115.html
week 1904: '-week' option - http://postal.unavco.org/pipermail/teqc/2016/002117.html
week 1905: using '+bcf' for XYZ/geodetic conversion - http://postal.unavco.org/pipermail/teqc/2016/002126.html
week 1906: the '+v[erify]' option - http://postal.unavco.org/pipermail/teqc/2016/002128.html
week 1907: '+C2', '+L5', "+L6', '+L7', '+L8', '+all' options - http://postal.unavco.org/pipermail/teqc/2016/002130.html
week 1908: getting RINEX doppler and L2 - http://postal.unavco.org/pipermail/teqc/2016/002131.html
week 1909: using paths w/ file names - http://postal.unavco.org/pipermail/teqc/2016/002132.html
week 1910: the (un)importance of file names - http://postal.unavco.org/pipermail/teqc/2016/002133.html
week 1911: notices, warnings, and errors - http://postal.unavco.org/pipermail/teqc/2016/002134.html
week 1912: the '-max_rx_SVs' option - http://postal.unavco.org/pipermail/teqc/2016/002137.html
week 1913: the end of '++igs' and '+igs' - http://postal.unavco.org/pipermail/teqc/2016/002140.html
week 1914: splicing together RINEX files - http://postal.unavco.org/pipermail/teqc/2016/002144.html
week 1915: using '-O.int' and '-O.dec' - http://postal.unavco.org/pipermail/teqc/2016/002145.html
week 1916: '+doy' option - http://postal.unavco.org/pipermail/teqc/2016/002146.html
week 1917: '-tbin' and '-ast' options - http://postal.unavco.org/pipermail/teqc/2016/002152.html
week 1918: mp12 RMS before/after Oct 2013 - http://postal.unavco.org/pipermail/teqc/2016/002158.html
week 1919: the global windowing options - http://postal.unavco.org/pipermail/teqc/2016/002159.html
week 1920: '-M.dec' and '-N.dec' options - http://postal.unavco.org/pipermail/teqc/2016/002163.html
week 1921: combining time filtering options - http://postal.unavco.org/pipermail/teqc/2016/002176.html
week 1922: helping me (or someone else on the list) help you - http://postal.unavco.org/pipermail/teqc/2016/002187.html
week 1923: the "build" line - http://postal.unavco.org/pipermail/teqc/2016/002190.html
week 1924: the qc '-w[idth]' option - http://postal.unavco.org/pipermail/teqc/2016/002193.html
week 1925: qc with explicit time windowing - http://postal.unavco.org/pipermail/teqc/2016/002194.html
week 1926: the '+rx_state' option - http://postal.unavco.org/pipermail/teqc/2016/002200.html
week 1927: the '-O.sum' option - http://postal.unavco.org/pipermail/teqc/2016/002204.html
week 1928: the '+meta' and '+mds' options - http://postal.unavco.org/pipermail/teqc/2016/002206.html
week 1930: more on '-O.sum' - http://postal.unavco.org/pipermail/teqc/2017/002207.html
week 1931: the '-O.s[ystem]' option - http://postal.unavco.org/pipermail/teqc/2017/002208.html
week 1932: leap seconds - http://postal.unavco.org/pipermail/teqc/2017/002215.html
week 1936: what you can (and shouldn't) do in a RINEX obs file - http://postal.unavco.org/pipermail/teqc/2017/002229.html
week 1938: the '+psp' option - http://postal.unavco.org/pipermail/teqc/2017/002231.html
week 1939: the '+diag' option - http://postal.unavco.org/pipermail/teqc/2017/002235.html
week 1951: '-n_<system>' and SV filtering options - http://postal.unavco.org/pipermail/teqc/2017/002277.html
week 1953: more with '+diag' option - http://postal.unavco.org/pipermail/teqc/2017/002287.html
week 1954: using '+diag' output to split raw files - http://postal.unavco.org/pipermail/teqc/2017/002290.html
week 1955: current qc notation - http://postal.unavco.org/pipermail/teqc/2017/002302.html
week 1956: the '+qcq' option - http://postal.unavco.org/pipermail/teqc/2017/002304.html
week 1957: using Trimble formats - http://postal.unavco.org/pipermail/teqc/2017/002305.html
week 1958: ToC != ToE messages - http://postal.unavco.org/pipermail/teqc/2017/002310.html
week 1959: receivers vs. formats - http://postal.unavco.org/pipermail/teqc/2017/002311.html
week 1960: when the '-week' option is very wrong to use - https://postal.unavco.org/pipermail/teqc/2017/002314.html
week 1961: "less" is usually best - https://postal.unavco.org/pipermail/teqc/2017/002315.html
week 1962: using GPS L2C with teqc - https://postal.unavco.org/pipermail/teqc/2017/002316.html

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://postal.unavco.org/pipermail/teqc/attachments/20170830/7dd65be4/attachment-0001.html>

More information about the teqc mailing list