Erratic program behavior while reading SMA 3000TL

[GoogleCodeExporter]

What steps will reproduce the problem?
1. just running ./smatool 

What is the expected output? What do you see instead?
The program is successful and properly does what it should do OR it fails with 
the message "bad extracting timestring". There is apparently no reason why it 
fails ~75% of the times. I tried to change bluetooth dongle, I tried to run 
smatool with and without options, result is always similar. 

What version of the product are you using? On what operating system?
sma-bluetooth-0.14, running NSLU2 with Debian (Linux nslu2 2.6.26-2-ixp4xx #1 
Mon Sep 19 09:19:39 UTC 2011 armv5tel GNU/Linux)

Please provide any additional information below.
In attachment what I get while running ./smatool -d -v for an unsuccessful and 
a successful case. 

Any help/advise is highly appreciated! 

Regards.

Alessandro

Original issue reported on code.google.com by cardini....@gmail.com on 5 Oct 2011 at 7:25

Attachments:

• smatool-ok.log
• smatool-bad.log

[GoogleCodeExporter]

SOLVED, maybe. 

After more studies I discovered that by increasing the check on failedbluetooth 
value from 10 to 60 solved ALL the problems (at least this whole afternoon). 
Still I do not understand why this should happen, comments are welcome.

Thanks again for this great program! 

Original comment by cardini....@gmail.com on 7 Oct 2011 at 7:33

[GoogleCodeExporter]

Ok, it seems that this problem is really solved! 

smatool has never failed in reading data from the inverter in the last day. 

I would like to recommend the authors to include this change in the official 
code.

Thanks again and best regards,

Alessandro

Original comment by cardini....@gmail.com on 8 Oct 2011 at 4:24

[GoogleCodeExporter]

this is in 0.15 as well as another when the 3000TL fails after exacly 1 year

Original comment by stephenb...@gmail.com on 27 Nov 2011 at 4:18

• Changed state: Fixed