[teqc] Unexpected behavior when using -tbin with multi-day Trimble 5700 or R7 data

Neville Palmer N.Palmer at gns.cri.nz
Thu Dec 13 18:46:19 MST 2018


I have recently noticed that when using the -tbin option to convert Trimble 5700 or R7 dat files to RINEX I am seeing different observable values in the resulting file(s) when compared with an equivalent RINEX file created without the -tbin option.

I have not seen this with any Trimble NetR9, NetRS or Septentrio data files. These produce identical files with either method described below.

The raw data files I am converting are 24 hour (daily) files covering multiple consecutive days. I am converting these to 24 hour (daily) RINEX files using -tbin in order to simplify file handling, file naming, etc.

The following is an example of a -tbin command I am using;
                teqc -tbin 1d XXXX +obs + *.dat

I am comparing the RINEX output from this with the output from a simple day by day conversion similar to this;
                teqc XXXXddd?.dat > XXXXddd0.18o
where "ddd" is the day number.

If I compare the first day of the -tbin output with the corresponding day-by-day output, the results are identical, as expected.

For every subsequent day, the -tbin output appears to keep incrementing the L1 & L2 observables from one day to the next, whereas the day-by-day output starts with new baseline values for each day/file.

These continually incrementing -tbin generated files appear to produce valid results if processed and teqc qc does not report any issues. The RINEX just looks unusual when viewed in a text editor.

I have found the unexpected output when using data from the following receivers;
Trimble 5700 firmware versions 2.32 or 1.20
Trimble R7 firmware version 2.32

I have also used the -tbin option with data from the following receivers and not encountered the unusual output. The results are effectively identical with RINEXing files day by day;
                Trimble NetR9
                Trimble NetRS
                Septentrio PolaRx5

I have one example where a 5700 receiver was logging continuously for 57 days. If I run the daily -tbin option on all these files then the L1 & L2 observables continue to increase until reaching values of around 4.99e9 after 35 days. On this day, as each SV reaches this value it appears to 'roll over' and start counting again from a value on the order of 1e6. I have not attempted to process this file yet, but teqc qc does not report any issues with the file.

I have tested this with versions 2018Dec12 and 2018Mar15 on Windows and Linux with the same result. I am not aware of any issues caused by the resulting files so far, but thought it worth raising.

The examples below show output from the two methods for exactly the same data.

I am happy to provide example raw or RINEX files if that would be useful.

Example using -tbin;
This is the first epoch on the 3rd day.
==================================================================
  2018     1    31     0     0   30.0000000     GPS         TIME OF FIRST OBS
                                                            END OF HEADER
18  1 31  0  0 30.0000000  0  6G06G02G17G12G19G24
-265042946.33258-205252780.55157  19965958.3914                   19965957.5784
        52.0004         42.7504
-264318709.69158-205136702.92256  21287641.7504                   21287636.7974
        49.2504         36.5004
-242632276.93857-188935855.59854  21476697.0234                   21476693.5594
        46.7504         28.7504
-261460722.21157-203631684.75854  22254935.5394                   22254932.4144
        47.7504         29.5004
-251829505.80957-195772771.53155  20869876.0314                   20869871.4344
        47.0004         35.2504
-252921611.22755-197109399.84053  22377847.7504                   22377848.8244
        35.0004         19.2504
18  1 31  0  1  0.0000000  0  6G06G02G17G12G19G24
-265008452.04348-205225901.88747  19972522.1334                   19972522.2034

=====================================================================
Example using basic teqc command for a single raw file/day.
Exactly the same epoch as above.
=====================================================================
  2018     1    31     0     0   30.0000000     GPS         TIME OF FIRST OBS
                                                            END OF HEADER
18  1 31  0  0 30.0000000  0  6G06G02G17G12G19G24
  -6674066.33258  -3926380.55157  19965958.3914                   19965957.5784
        52.0004         42.7504
  -5949829.69158  -3810302.92256  21287641.7504                   21287636.7974
        49.2504         36.5004
  15736603.06357  12390544.40254  21476697.0234                   21476693.5594
        46.7504         28.7504
  -3091842.21157  -2305284.75854  22254935.5394                   22254932.4144
        47.7504         29.5004
   6539374.19157   5553628.46955  20869876.0314                   20869871.4344
        47.0004         35.2504
   5447268.77355   4217000.16053  22377847.7504                   22377848.8244
        35.0004         19.2504
18  1 31  0  1  0.0000000  0  6G06G02G17G12G19G24
  -6639572.04348  -3899501.88747  19972522.1334                   19972522.2034

Regards
Neville Palmer
Notice: This email and any attachments are confidential and may not be used, published or redistributed without the prior written consent of the Institute of Geological and Nuclear Sciences Limited (GNS Science). If received in error please destroy and immediately notify GNS Science. Do not copy or disclose the contents.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://postal.unavco.org/pipermail/teqc/attachments/20181214/bb26c3cb/attachment.html>


More information about the teqc mailing list