[teqc] TPS conversion problem

Rui Manuel da Silva Fernandes rmanuel at di.ubi.pt
Wed Nov 3 13:27:44 MDT 2010


Hi Lou,
     I used teqc to translate hourly files (merged into daily files) from a new 
Topcon NET-G3A receiver. The command that I used is a little bit more complex 
(it is inside a script) but this one should present similar results...
<geodac#/home/gpsdata>teqc BNGL1027*.TPS > BNGL3000.10O
However, I noticed a lot of data gaps:
<geodac#/home/gpsdata>teqc BNGL3000.10O > /dev/null
! Notice ! 2010 Oct 27 05:46:30.000: poss. incr. of sampling int. OR data gap of 
480.000 seconds (min. dt found= 30.000 s)
! Notice ! 2010 Oct 27 05:58:00.000: poss. incr. of sampling int. OR data gap of 
60.000 seconds (min. dt found= 30.000 s)
! Notice ! 2010 Oct 27 06:46:30.000: poss. incr. of sampling int. OR data gap of 
2910.000 seconds (min. dt found= 30.000 s)
! Notice ! 2010 Oct 27 07:22:00.000: poss. incr. of sampling int. OR data gap of 
180.000 seconds (min. dt found= 30.000 s)
! Notice ! 2010 Oct 27 07:28:00.000: poss. incr. of sampling int. OR data gap of 
240.000 seconds (min. dt found= 30.000 s)
! Notice ! 2010 Oct 27 07:36:30.000: poss. incr. of sampling int. OR data gap of 
120.000 seconds (min. dt found= 30.000 s)
! Notice ! 2010 Oct 27 07:43:30.000: poss. incr. of sampling int. OR data gap of 
420.000 seconds (min. dt found= 30.000 s)
! Notice ! 2010 Oct 27 08:00:00.000: poss. incr. of sampling int. OR data gap of 
600.000 seconds (min. dt found= 30.000 s)
! Notice ! 2010 Oct 27 08:24:30.000: poss. incr. of sampling int. OR data gap of 
1050.000 seconds (min. dt found= 30.000 s)
! Notice ! 2010 Oct 27 08:31:00.000: poss. incr. of sampling int. OR data gap of 
390.000 seconds (min. dt found= 30.000 s)
! Notice ! 2010 Oct 27 08:59:00.000: poss. incr. of sampling int. OR data gap of 
330.000 seconds (min. dt found= 30.000 s)
! Notice ! 2010 Oct 27 09:00:00.000: poss. incr. of sampling int. OR data gap of 
60.000 seconds (min. dt found= 30.000 s)
! Notice ! 2010 Oct 27 09:02:30.000: poss. incr. of sampling int. OR data gap of 
120.000 seconds (min. dt found= 30.000 s)
! Notice ! 2010 Oct 27 09:31:00.000: poss. incr. of sampling int. OR data gap of 
1020.000 seconds (min. dt found= 30.000 s)

This repeats for other days and other stations.

In order to try to detect the problem, I also used tps2rin (the tool provided by 
Topcon) to convert the files and the merged file does not show any data gaps. 
So, I really suspect that there is some issue in the raw data (TPS) of the new 
Topcon receivers when translated with teqc. Is this related with the issue that 
you detected last year concerning the Javad/Topcon format?

Thanks,
         Rui



-- 
###################################################################
Rui Fernandes
  Professor Auxiliar / Assistant Professor
  DI - UBI - CGUL/IDL - PORTUGAL    rmanuel at di.ubi.pt
    +351275319891
###################################################################
"Better to understand a little than to misunderstand a lot."
###################################################################


More information about the teqc mailing list