[teqc] strange Leica 1200 conversion

Terry Nygaard tnygaard at sbcglobal.net
Wed Oct 21 20:43:23 MDT 2009


Lou,

Thanks for the quick reply and thats fine as long as Leica is taking a 
look.  My experience with them has been pretty good - they should check 
this out in short order.

Thanks,
Terry

Lou Estey wrote:
> hi Terry,
>
> The answer to your question is no, mainly because I don't have Geo 
> Office,
> but Matt did say off-line to me that he had sent the MDB file to Leica 
> and
> they were going to take a look at it.
>
> Because the data isn't from UNAVCO or in the public domain, I'm not at
> liberty to send anything to anyone without Matt's permission.  But if and
> only if it is ok with Matt, I could snip out the five epoch mentioned 
> below
> and send them to you.
>
> cheers,
> --lou
>
>> I am a Leica 1200 user and I found this very curious the G42G61 prn's 
>> just showing up like this.  Were you able to get the Rinex output 
>> from Leica Geo Office and see if it generates the same obvious 
>> error?  I have the latest version of LGO and I would be willing to 
>> convert the binary to Leica's version  just to see if this same 
>> behavior occurs.
>>
>> Regards,
>> Terry
>>
>> Tx RPLS / Austin Texas
>>
>>
>>
>> Lou Estey wrote:
>>> Dear Matt,
>>>
>>>>> 2. more problematically, when I then try and window that big RINEX 
>>>>> file into a day RINEX files, I get occasional errors of the kind
>>>>>  
>>>>> teqc -st 20090606000000.0 +ds 86399 kns10910_all.09o >! kns11570.09o
>>>>>
>>>>> ! Notice ! setting TIME OF FIRST OBS to match requested window: 
>>>>> 2009 Jun  6 00:00:00.000 ! Notice ! NAVSTAR GPS: bad PRN= 42 being 
>>>>> rejected @ 2009 Jun  6 12:32:00.000 (min= 1, max= 32)
>>>>>
>>>>> teqc: teqc windowed: delta = 86399.000 secfailure to read 
>>>>> '                                G42G61' on line 5461503 of 
>>>>> 'kns10910_all.09o'         (invalid satellite number) ... exiting
>>>>>  
>>>>> G42 and/or G61 appear every now and again. [...]
>>>>
>>>> Clearly we need to find out what's going on in these epochs.  I'll
>>>> need some sample to examine.
>>>>
>>>>> Any desire to look at this file? The other 2 or 3 files I have 
>>>>> also give similar, so not just a single receiver it seems.
>>>>
>>>> If the problem can be isolated to a small enough chunk of the full
>>>> 300 Mb file, I'd be willing to look at, say, 1 Mb worth.
>>>
>>> (Ok, I had to get the full 300 Mb file.)  The interesting thing is the
>>> epoch/SV lists around that epoch are:
>>>
>>>  09  6  6 12 31 40.0000000  0 14G08G10G24G06G03G21G27G15G18G07G29G19
>>>                                 G28G26
>>> ...
>>>  09  6  6 12 31 50.0000000  0 14G08G10G24G06G03G21G27G15G18G07G29G19
>>>                                 G28G26
>>> ...
>>>  09  6  6 12 32  0.0000000  0 14G08G10G24G06G03G21G27G15G18G07G29G19
>>>                                 G42G61
>>> ...
>>>  09  6  6 12 32 10.0000000  0 14G08G10G24G06G03G21G27G15G18G07G29G19
>>>                                 G28G26
>>> ...
>>>  09  6  6 12 32 20.0000000  0 14G08G10G24G06G03G21G27G15G18G07G29G19
>>>                                 G28G26
>>> ...
>>>
>>> therefore the last two GPS PRNs are almost certainly supposed to be
>>> 28 and 26 for these five epochs.  The code in teqc is doing exactly
>>> the same thing reading all the MDB data records 119 (0x77), so I would
>>> assume that this must be an error in the record 119 for epoch
>>> 12:32:00 itself -- unless someone at Leica can demonstrate otherwise
>>> (e.g. Leica demonstrates that the parsing in teqc of this one record 
>>> 119
>>> is wrong.)  The receiver info is:
>>>
>>> [2041] teqc -notice +meta *.m00 | grep ^rec
>>> receiver ID number:      480104
>>> receiver type:           LEICA GX1220+GNSS
>>> receiver firmware:       7.02
>>>
>>> Currently the code in teqc for reading Leica's MDB record 119 is
>>> not doing any sanity check on validity of the reported GNSS satellite
>>> IDs -- because before this I had never seen a case where it was 
>>> necessary --
>>> but maybe one should be added given this example.
>>>
>>> --------
>>>
>>> Also, getting back to the original task that was being attempted:
>>> daily RINEX files from the multi-month Leica MDB .m00 file.
>>>
>>> Matt, why don't you use the new -tbin option to directly create the 
>>> daily
>>> RINEX?  E.g.
>>>
>>> teqc -notice +obs + -tbin 1d name *.m00
>>>
>>> The PRN problem is very intermittent, so some of the daily RINEX 
>>> files will
>>> still have the bogus GPS PRNs, but the majority with be AOK.
>>>
>>> cheers,
>>> --lou
> _______________________________________________
> teqc mailing list
> teqc at ls.unavco.org
> http://ls.unavco.org/mailman/listinfo/teqc
>


More information about the teqc mailing list