Re: [time-nuts] Lea-6T Math error?

[Azelio Boriani]

Did you use the CFG-TMODE svinVarLimit to set 350 and the svinMinDur
to set 32400?
The CFG-TMODE svinVarLimit is a variance in squared mm, not a standard
deviation...

On Fri, Apr 15, 2016 at 6:27 AM, Bob Stewart  wrote:
> I hope I haven't posted about this before, but it's something that's bugged 
> me for awhile.  When I run a survey-in on an LEA-6T, the 
> CFG-TMODE2->fixedPosAcc value seems to be wrong.  For instance, I ran a 
> survey today and told it to run for 32,400 seconds and reach at least 350mm 
> accuracy.  When it finished, TIM-SVIM reported it had run 38,126 seconds with 
> a mean 3D std deviation of 350mm.  OK, so far.  So, I go look in the 
> CFG-TMODE2 structure and it reports 122mm.  That seems a bit odd, but OK.  
> And then I squared 350, and came up with 122500.  It appears that instead of 
> just moving the 350mm value over to the TMODE structure, they've squared it 
> and divided it by 1000.  I've noticed this happening on at least 2 versions 
> of the 6T.  I suppose I should do the same test on the M8T.
>
> Bob
> ___
> time-nuts mailing list -- time-nuts@febo.com
> To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
> and follow the instructions there.
___
time-nuts mailing list -- time-nuts@febo.com
To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.

Re: [time-nuts] Lea-6T Math error?

[Azelio Boriani]

Yes, I see: the fixedPosAcc should be 18mm not 122.

On Fri, Apr 15, 2016 at 12:15 PM, Azelio Boriani
 wrote:
> Did you use the CFG-TMODE svinVarLimit to set 350 and the svinMinDur
> to set 32400?
> The CFG-TMODE svinVarLimit is a variance in squared mm, not a standard
> deviation...
>
> On Fri, Apr 15, 2016 at 6:27 AM, Bob Stewart  wrote:
>> I hope I haven't posted about this before, but it's something that's bugged 
>> me for awhile.  When I run a survey-in on an LEA-6T, the 
>> CFG-TMODE2->fixedPosAcc value seems to be wrong.  For instance, I ran a 
>> survey today and told it to run for 32,400 seconds and reach at least 350mm 
>> accuracy.  When it finished, TIM-SVIM reported it had run 38,126 seconds 
>> with a mean 3D std deviation of 350mm.  OK, so far.  So, I go look in the 
>> CFG-TMODE2 structure and it reports 122mm.  That seems a bit odd, but OK.  
>> And then I squared 350, and came up with 122500.  It appears that instead of 
>> just moving the 350mm value over to the TMODE structure, they've squared it 
>> and divided it by 1000.  I've noticed this happening on at least 2 versions 
>> of the 6T.  I suppose I should do the same test on the M8T.
>>
>> Bob
>> ___
>> time-nuts mailing list -- time-nuts@febo.com
>> To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
>> and follow the instructions there.
___
time-nuts mailing list -- time-nuts@febo.com
To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.

[time-nuts] Lea-6T Math error?

[Bob Stewart]

I hope I haven't posted about this before, but it's something that's bugged me 
for awhile.  When I run a survey-in on an LEA-6T, the CFG-TMODE2->fixedPosAcc 
value seems to be wrong.  For instance, I ran a survey today and told it to run 
for 32,400 seconds and reach at least 350mm accuracy.  When it finished, 
TIM-SVIM reported it had run 38,126 seconds with a mean 3D std deviation of 
350mm.  OK, so far.  So, I go look in the CFG-TMODE2 structure and it reports 
122mm.  That seems a bit odd, but OK.  And then I squared 350, and came up with 
122500.  It appears that instead of just moving the 350mm value over to the 
TMODE structure, they've squared it and divided it by 1000.  I've noticed this 
happening on at least 2 versions of the 6T.  I suppose I should do the same 
test on the M8T.

Bob
___
time-nuts mailing list -- time-nuts@febo.com
To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.