Date Error

[GoogleCodeExporter]

running -v -d I now get this fairly consistently..

.
.
.
Receiving
    00000000: .. .. .. .. .. .. .. .. .. .. .. .. 7e 1b 00 65 
    00000010: 06 e0 09 25 80 00 21 50 24 98 80 00 01 00 54 00 
    00000020: 00 00 00 00 03 1f 7e  rr=27

65 06 e0 09 25 80 00 21 50 24 98 80 00 01 00 54 00 00 00 00 00 03 1f 7e 
7e 1b 00 65 06 e0 09 25 80 00 21 50 24 98 80 00 01 00 54 00 00 00 00 00 03 1f 
7e 

len=385 data=00 5c 84 2c 4d da 13 54 00 00 00 00 00 88 85 2c 4d da 13 54 00 00 
00 00 00 b4 86 2c 4d da 13 54 00 00 00 00 00 e0 87 2c 4d da 13 54 00 00 00 00 
00 0c 89 2c 4d da 13 54 00 00 00 00 00 38 8a 2c 4d da 13 54 00 00 00 00 00 64 
8b 2c 4d da 13 54 00 00 00 00 00 90 8c 2c 4d da 13 54 00 00 00 00 00 bc 8d 2c 
4d da 13 54 00 00 00 00 00 e8 8e 2c 4d da 13 54 00 00 00 00 00 14 90 2c 4d da 
13 54 00 00 00 00 00 40 91 2c 4d da 13 54 00 00 00 00 00 6c 92 2c 4d da 13 54 
00 00 00 00 00 98 93 2c 4d da 13 54 00 00 00 00 00 c4 94 2c 4d da 13 54 00 00 
00 00 00 f0 95 2c 4d da 13 54 00 00 00 00 00 1c 97 2c 4d da 13 54 00 00 00 00 
00 48 98 2c 4d da 13 54 00 00 00 00 00 74 99 2c 4d da 13 54 00 00 00 00 00 a0 
9a 2c 4d da 13 54 00 00 00 00 00 cc 9b 2c 4d da 13 54 00 00 00 00 00 f8 9c 2c 
4d da 13 54 00 00 00 00 00 24 9e 2c 4d da 13 54 00 00 00 00 00 50 9f 2c 4d da 
13 54 00 00 00 00 00 7c a0 2c 4d da 13 54 00 00 00 00 00 a8 a1 2c 4d da 13 54 
00 00 00 00 00 d4 a2 2c 4d da 13 54 00 00 00 00 00 00 a4 2c 4d da 13 54 00 00 
00 00 00 2c a5 2c 4d da 13 54 00 00 00 00 00 58 a6 2c 4d da 13 54 00 00 00 00 
00 84 a7 2c 4d da 13 54 00 00 00 00 00 b0 a8 2c 4d da 13 54 00 00 00 00 00
Date Error! prev=746871808 current=746948608

nekobasu:/usr/local/src/sma-bluetooth-local

Not sure what it means or why the main loop should need to bail at that point.. 
:)

Original issue reported on code.google.com by b...@ticm.com on 13 Jan 2011 at 7:48

[GoogleCodeExporter]

cool it looks like it is working. The date error is a catch for bad data. It 
makes sure after the first data which is a dummy that all are 5 minutes apart. 
I'll have a look and see what is happening - looks like it is getting out of 
alignment as this isn't the first output. the first value shouldn't have the 00 
its offset by 1. It should start at 5c (the 4d 2c 84 5c (reverse) is the date 
and the 54 13 da (reverse) is the accumulated value at that time (5510106Whrs).

Can you add all the data I particularly need to see the first one and why it 
didn't start at posn 59. 

Original comment by stephenb...@gmail.com on 13 Jan 2011 at 11:20

• Changed state: Accepted

[GoogleCodeExporter]

Haven't had this repeat yet...

Original comment by b...@ticm.com on 16 Jan 2011 at 3:40

[GoogleCodeExporter]

must have just been an aberration. It will still need to catch
 it somehow.

If its working I assume you have a 3000TL

Original comment by stephenb...@gmail.com on 16 Jan 2011 at 5:34

[GoogleCodeExporter]

Yup one 3000TL at the moment and possibly another 1700 with bluetooth dongle in 
a couple of months. It will be interesting if the 1700 can work with this.

Original comment by b...@ticm.com on 16 Jan 2011 at 10:59

[GoogleCodeExporter]

closing

Original comment by stephenb...@gmail.com on 26 Jan 2011 at 7:59

• Changed state: Done