borked data in logfile...

[thinrope]

2.5 years, 6 (?) hardware releases and we still have the same (probably) bug...

I just looked at Nano 2046 log and found this:

# NEW LOG
# format=1.2.6nano
# deadtime=on
$BNRDD,2046,2013-07-05T13:46:26Z,41,4,301,A,3539.3570,N,13941.7177,E,59.70,A,14548996,0*74

...

$BNRDD,2046,2013-07-05T21:01:18Z,35,2,16375,A,3539.3450,N,13941.7213,E,61.00,A,6815751,0*47
$BNRDD,2046,2013-07-05T21:01:23Z,34,1,16376,A,3539.3461,N,13941.7210,E,61.30,A,7405575,0*44
$BNRDD,2046,2013-07-05T21:01:28Z,32,2,16378,A,3539.3480,N,13941.7205,E,62.40,A,7405575,0*4B
$BNRDD,2046,2073-50-00T21:01:33Z,33,4,16382,A,3539.3494,N,13941.7211,E,63.10,A,8323079,0*43
$BNRDD,2046,2073-50-00T21:01:38Z,32,3,16385,A,3539.3500,N,13941.7209,E,64.10,A,5963785,0*4C
$BNRDD,2046,2073-50-00T21:01:43Z,36,6,16391,A,3539.3511,N,13941.7205,E,65.30,A,8126472,0*44
$BNRDD,2046,2073-50-00T21:01:48Z,35,3,16394,A,3539.3513,N,13941.7202,E,66.00,A,6291464,0*4F
$BNRDD,2046,2013-07-05T21:01:53Z,35,4,16398,A,3539.3526,N,13941.7203,E,66.10,A,7340040,0*47
$BNRDD,2046,2013-07-05T21:01:58Z,38,5,16403,A,3539.3537,N,13941.7203,E,66.40,A,6029321,0*49
$BNRDD,2046,2013-07-05T21:02:03Z,37,2,16405,A,3539.3535,N,13941.7200,E,66.70,A,5832713,0*4C

....````

That year 2073 might be fine, but month of 50 is definitely not. It has 1.2.7 firmware already, I'll see if I get this bug again :-|