AI Assistant
teqc and Trimble 4....
 
Notifications
Clear all

teqc and Trimble 4.93 Fixed?

2 Posts
2 Users
0 Reactions
992 Views
paul-in-pa
(@paul-in-pa)
Posts: 6034
Member
Topic starter
Translate
English
Spanish
French
German
Italian
Portuguese
Russian
Chinese
Japanese
Korean
Arabic
Hindi
Dutch
Polish
Turkish
Vietnamese
Thai
Swedish
Danish
Finnish
Norwegian
Czech
Hungarian
Romanian
Greek
Hebrew
Indonesian
Malay
Ukrainian
Bulgarian
Croatian
Slovak
Slovenian
Serbian
Lithuanian
Latvian
Estonian
 

The following is a general email from Lou Estey regarding a problem with Trimble 4.93 files. If you have had recent teqc/Trimble problems you my want to retry one of your errant files.

Congrats and thanks to the hard working teqc crew.

Paul in PA

Series of teqc messages follows:

dear Ted Zhou et al.,

With just some minor information from Trimble and few additions to teqc, it appears
I have the new stuff that Trimble added in fw 4.93 accounted for. So, doing
`teqc +all -O.sum . *.tgd` on the same .tgd file as below, now:

[1785] teqc +all -O.sum . *.tgd
? Error ? translation may have started with GPS week 1828 rather than 1827
(try using '-week 1827' option)
! Notice ! incomplete code for parsing Trimble .dat record 32 (Galileo ion/UTC model) in file '5024K68287201501130000a.tgd' ... skipping
L1 L2 L5 L6 L7 L8 C1 P1 C2 P2 C5 C6 C7 C8 S1 S2 S5 S6 S7 S8
---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ----
G23 846 840 0 0 0 0 846 0 0 840 0 0 0 0 846 840 0 0 0 0
G20 1116 1064 0 0 0 0 1116 0 0 1064 0 0 0 0 1116 1064 0 0 0 0
...
C11 1026 0 0 0 1019 0 1026 0 0 0 0 0 1019 0 1026 0 0 0 1019 0
C06 3 0 0 0 0 0 3 0 0 0 0 0 0 0 3 0 0 0 0 0
C12 823 0 0 0 821 0 823 0 0 0 0 0 821 0 823 0 0 0 821 0
C14 920 0 0 0 920 0 920 0 0 0 0 0 920 0 920 0 0 0 920 0
C08 68 0 0 0 60 0 68 0 0 0 0 0 60 0 68 0 0 0 60 0

All the messages were due to Trimble introducing another counter, in addition to the
previous two counters I knew about, to indicate data from a Beidou SV. This new counter
had to be codified in three functions in teqc.

The pertinent messages from before this change were the ones like:

! Notice ! file '5024K68287201501130000a.tgd' contains unknown SV data 'block type'= 3 'track type'= 28 of unknown type ... skipping
! Notice ! file '5024K68287201501130000a.tgd' contains unknown SV data 'block type'= 6 'track type'= 26 of unknown type ... skipping
! Warning ! constellation ID 10 detected in Trimble_27_57h_6_constellation()
.dat 27/0x57-6: unknown SV type= 10

(The rest were unimportant in this case.)

cheers,
--lou

On 1/14/2015 8:27 AM, Lou Estey wrote:
I'm changing the subject line on this thread.

Our D&T gents, Freddy Blume and Henry Berglund, apparently started looking at 4.93
recently and ran into similar things but hadn't contacted me yet. Anyway, Freddy just
sent me a .t02 file collected on a NetR9 with fw 4.93, with the receiver set to
track all SVs in view here in Colorado, and we get similar messages from teqc.
(Aside: you need to use a relatively recent version of Trimble's runpkr00 to convert
the .t02 to .tgd: version 5.40 works but version 5.31 doesn't.) A quick summary
of the various messages that I'm seeing running just `teqc +all -O.sum . *.tgd`:

! Notice ! GLONASS: bad channel frequency channel #= 54 being rejected @ (min= -7, max= 24)
! Notice ! GLONASS: bad channel frequency channel #= 55 being rejected @ (min= -7, max= 24)
! Notice ! GLONASS: bad channel frequency channel #= 56 being rejected @ (min= -7, max= 24)

! Notice ! SBAS: bad PRN= 162 being rejected @ (min= 20, max= 42)
! Notice ! SBAS: bad PRN= 167 being rejected @ (min= 20, max= 42)
! Notice ! SBAS: bad PRN= 168 being rejected @ (min= 20, max= 42)
! Notice ! SBAS: bad PRN= 170 being rejected @ (min= 20, max= 42)

! Notice ! file '5024K68287201501130000a.tgd' contains unknown SV data 'block type'= 3 'track type'= 28 of unknown type ... skipping
! Notice ! file '5024K68287201501130000a.tgd' contains unknown SV data 'block type'= 6 'track type'= 26 of unknown type ... skipping

! Warning ! constellation ID 10 detected in Trimble_27_57h_6_constellation()
.dat 27/0x57-6: unknown SV type= 10

All of this implies Trimble has added stuff to their record 27 (the main data
payload record in a .tgd file for RT27) in fw 4.93 that I know nothing about.
Therefore it isn't codified in teqc yet.

On the plus side, if I do a translation to RINEX, ignore all these messages, and then
qc the RINEX, I get a fairly complete looking set of data: a normal set of GPS and
GLONASS SVs, four Galileo SVs, and three SBAS SVs (PRNs 133, 135, and 138).

So if you upgrade to Trimble fw 4.93 anytime soon, don't plan on using teqc to read
the .tgd files for getting -- perhaps -- a complete translation until you hear from
me and have a new teqc version than can deal with whatever Trimble added, but for
the most part for the time being, just ignore all the messages that are similar to
the ones above.

--lou

On 1/13/2015 9:02 PM, Lou Estey wrote:
hi Ted,

I don't recall any of our engineers commenting on fw 4.93, but, that aside, I only see
two issues in the messages:

.dat 27/0x57-6: unknown SV type= 10 -- Something new, definitely. Is this perhaps capable of tracking IRNSS?
(The few IRNSS SVs should be visible in Australia.)

! Notice ! GLONASS: bad channel frequency channel #= 54 being rejected @ 2015 Jan 13 22:28:00.000 (min= -7, max= 24) --
Are these are odd, but whatever is going on explains why you aren't seeing any GLONASS: teqc is rejecting it all.

--lou

On 1/13/15 8:44 PM, [email protected] wrote:
Dear Friends:

Does TEQC has any issues with Trimble latest firmware *4.93*?

Since the Trimble receiver with firmware 4.93 has a new option *L2E* and *L2C* for receiver to tracking?

I used *teqc *to convert Trimble raw data *TGD* files into *Rinex*, I got the following error messages:

_______________________________________________
teqc mailing list
[email protected]
http://postal.unavco.org/mailman/listinfo/teqc


 
Posted : January 22, 2015 6:50 pm
UnmannedSurveyor
(@unmannedsurveyor)
Posts: 102
Member
Translate
English
Spanish
French
German
Italian
Portuguese
Russian
Chinese
Japanese
Korean
Arabic
Hindi
Dutch
Polish
Turkish
Vietnamese
Thai
Swedish
Danish
Finnish
Norwegian
Czech
Hungarian
Romanian
Greek
Hebrew
Indonesian
Malay
Ukrainian
Bulgarian
Croatian
Slovak
Slovenian
Serbian
Lithuanian
Latvian
Estonian
 

I don't know, but I loved reading that. :hi5:


 
Posted : January 22, 2015 7:15 pm