search

bravohe / sma-bluetooth

Automatically exported from code.google.com/p/sma-bluetooth
0 stars 0 forks source link

support for SB1600TL #81

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 

Hi, I bought a SB1600TL and use the smatool to capture data. In the smatoo.conf 
I entered 2100TL, because all other types give segmentation faults.
Is there any chance that the support for the 1600TL will be added?

Original issue reported on code.google.com by sendtore...@gmail.com on 28 May 2012 at 12:28

GoogleCodeExporter commented 9 years ago 
Here is an xml logfile from a trace:

Original comment by sendtore...@gmail.com on 28 May 2012 at 7:09

Attachments:

GoogleCodeExporter commented 9 years ago 
It seems that in the xml spaces are added in the raw data. The codes I found 
are:

Code1       0xd2  
Code2       0xe1  
Code3       0x46  
Code4       0x37  
InvCode     0xFF

Original comment by sendtore...@gmail.com on 29 May 2012 at 8:52

GoogleCodeExporter commented 9 years ago 
I have now been using a Raspberry Pi with the 1600TL and SMA-bluetooth for 8 
days without a problem using these codes:

Inverter         1600TL
Code1            0x36
Code2            0xE1
Code3            0x38
Code4            0x3B
InvCode          0x63

Full details of the install process can be found here:
http://ictoblog.nl/raspberrypi-pvoutput

Original comment by P.Goris...@gmail.com on 20 Aug 2012 at 3:25

GoogleCodeExporter commented 9 years ago 
Hi,

I'm having trouble getting this up and running on my 1600TL on a Raspberry Pi. 
I get the following error shown when running smatool -d -v:

[21] 2012-11-30 10:27:44 looking for: 7e 22 00 5c cb e1 a4 25 80 00 00 00 00 00 
00 00 05 00 cb e1 a4 25 80 00
[21] 2012-11-30 10:27:44 received:    7e 1f 00 61 cb e1 a4 25 80 00 00 00 00 00 
00 00 02 00 00 04 70 00 01 00 00 00 00 01 00 00 00

[21] 2012-11-30 10:27:44 Did not find string

I have been using the codes in comment 3 above. Output from hciconfig is below:

hci0:   Type: BR/EDR  Bus: USB
        BD Address: 00:15:E9:F5:BC:C2  ACL MTU: 377:10  SCO MTU: 16:0
        UP RUNNING PSCAN
        RX bytes:11556 acl:208 sco:0 events:246 errors:0
        TX bytes:3059 acl:110 sco:0 commands:103 errors:0

I'm kind of stuck now, does anyone have any suggestions?

Original comment by brad.hen...@digsilent.co.nz on 29 Nov 2012 at 11:32

GoogleCodeExporter commented 9 years ago 
I resolved my issue - bad bluetooth dongle. I replaced it with a dongle that 
has a Cambridge silicon radio chipset and data is now being downloaded - hurray!

Original comment by brad.hen...@digsilent.co.nz on 4 Dec 2012 at 11:36