[teqc] teqc and "recent" rt27 format change

Lou Estey lou at unavco.org
Wed Jun 6 11:35:42 MDT 2018


Observable measurements are in 0x57.  You can find out the total number with:

[765] teqc -notice +diag . +mds Sample_RT27_log 2>&1 | g "type= 0x57" | wc -l
   33332

The total number of 0x55 records (all subtypes) can be found in a similar way:

[766] teqc -notice +diag . +mds Sample_RT27_log 2>&1 | g "type= 0x55" | wc
     167

Now because this happens:

[769] teqc -notice +all -O.sum . Sample_RT27_log
'Sample_RT27_log' appears to have no usable data

it probably means that Trimble has also introduced a new 0x57 subtype to hold
observable measurements -- and I don't documentation for any of that.  For teqc
users, this is much more significant issue than what ever they added to 0x55 for
position/velocity.

--lou

On 06-Jun-18 10:59 AM, Mathieu Peyréga wrote:
> Hello,
> 
> from the configuration settings that Trimble sent me, this file is supposed to contain measurements, but I have not been able to get them 
> out with teqc and my usual command lines (it's ok for ephemerids)
> 
> I saw there is a new tick box in the i/o page settings for "Include FLL measurements". Also the config is not the one I use on my production 
> chain on other aspects. I've been asking them for a sample with same settings and will see after that... I hope they have not replaced the 
> measurements record with this new 0x55-22 record....
> 
> Best regards,
> 
> Mathieu Peyréga
> -- 
> +33 (0)6 87 30 83 59
> 
> Le 06/06/2018 à 18:16, Lou Estey a écrit :
>> dear Mathieu,
>>
>> With the sample Trimble RT27 file that you sent (and, btw, thanks for that),
>> nothing unexpected happens:
>>
>> [723] teqc +meta Sample_RT27_log
>> ! Notice ! Trimble BSTR 0x55-22 (unknown): no routine in teqc
>> ! Notice ! Trimble BSTR 0x55-22 (unknown): no routine in teqc
>> ! Notice ! Trimble BSTR 0x55-22 (unknown): no routine in teqc
>> ! Notice ! Trimble BSTR 0x55-22 (unknown): no routine in teqc
>> ! Notice ! Trimble BSTR 0x55-22 (unknown): no routine in teqc
>> ! Notice ! Trimble BSTR 0x55-22 (unknown): no routine in teqc
>> ! Notice ! Trimble BSTR 0x55-22 (unknown): no routine in teqc
>> ! Notice ! Trimble BSTR 0x55-22 (unknown): no routine in teqc
>> ! Notice ! Trimble BSTR 0x55-22 (unknown): no routine in teqc
>> ! Notice ! Trimble BSTR 0x55-22 (unknown): no routine in teqc
>> ! Notice ! Trimble BSTR 0x55-22 (unknown): no routine in teqc
>> ! Notice ! Trimble BSTR 0x55-22 (unknown): no routine in teqc
>> ! Notice ! Trimble BSTR 0x55-22 (unknown): no routine in teqc
>> ! Notice ! Trimble BSTR 0x55-22 (unknown): no routine in teqc
>> ! Notice ! Trimble BSTR 0x55-22 (unknown): no routine in teqc
>> filename:                Sample_RT27_log
>> file format:             Trimble BSTR
>> file size (bytes):       3605918
>> start date & time:       2018-06-06 10:05:31.000
>> final date & time:       2018-06-06 10:21:58.000
>> sample interval:         1.0000
>> possible missing epochs: 0
>> 4-char station code:     Samp
>> station name:            -Unknown-
>> station ID number:
>> antenna ID number:       -Unknown-
>> antenna type:            -Unknown-
>> antenna latitude (deg):      47.298988807
>> antenna longitude (deg):     -1.508875865
>> antenna elevation (m):            79.1697
>> antenna height (m):      0.0000
>> receiver ID number:      -Unknown-
>> receiver type:           TRIMBLE
>> receiver firmware:       -Unknown-
>>
>> I'm assuming that record 0x55 subtype 22 is the new thing:
>> > One of the changes states : Improve RT27 longitude velocity subtype
>> ... but you still get out coordinates even with teqc not able to read
>> this new 0x55-22.
>>
>> cheers,
>> --lou
>>
>> On 05-Jun-18 01:43 PM, Mathieu Peyréga wrote:
>>> Hi,
>>>
>>> no I have not tested it yet...
>>>
>>> I would prefer to make sure that teqc is ready to handle the change before doing the upgrade as the station is included in french CORS 
>>> and I would prefer not needding to handle upgrade / teqc fail / downgrade event sequence
>>>
>>> Do you think you are able to ask Trimble some data sample under your NDA regarding RT27 format and check hw teqc behaves ?
>>>
>>> Best regards,
>>>
>>> Mathieu
>>>
>>>
>>>
>>> Le 05/06/2018 à 21:37, Lou Estey a écrit :
>>>> Did you test it?  But given the wording in the release notes, it sounds like Trimble
>>>> has introduced something new in RT27 where code in teqc would have to be changed in order
>>>> to use it.
>>>>
>>>> --lou
>>>>
>>>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>>> 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
>>>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>>>
>>>> On 05-Jun-18 01:03 PM, Mathieu Peyréga wrote:
>>>>> Hello,
>>>>>
>>>>> i'd like to upgrade a Trimble BD970 board receiver that is currently in 5.21 version to the recently released 5.34
>>>>>
>>>>> http://trl.trimble.com/dscgi/ds.py/Get/File-881142/BD9XX_V5.3X%20Release%20Notes.pdf
>>>>>
>>>>> One of the changes states : Improve RT27 longitude velocity subtype.
>>>>>
>>>>> As my Rinex production chain is based on teqc parsing the rt27 datastream, I'd like to make sure that this change will not break things.
>>>>>
>>>>> Did someone tested those new firmwares yet against teqc ?
>>>>>
>>>>> Best regards,
>>>>>
>>>>> Mathieu Peyréga


More information about the teqc mailing list