search

jonneytest / sma-bluetooth

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

Trouble getting this working with my SB4000TL-20, can't work out why. #96

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. smatool on Raspberry Pi (Raspbian Debian based OS)
2. Using my SMA SB4000TL-20 
3. Using my sniffed inverter codes

What is the expected output? What do you see instead?
Having installed it correctly, I'd hope for smatool -v to show my inverter data 
rather than just 'serial' and 'bluetooth signal' lines ie,

bluetooth signal = 73%
serial=7d:33:63:09
bluetooth signal = 73%
bluetooth signal = 73%

What version of the product are you using? On what operating system?
* Smatool 0.18
* Raspberry Pi (Raspbian Debian Linux)
* SMA SB4000TL-20 with version 03.10.37.R

Please provide any additional information below.

I've compiled smatool on the Raspberry Pi, which compiled OK and I can run it 
and obtain debug output.

My Bluetooth is working and I can see the inverter:

raspberrypi:/home/pi/sma-bluetooth# hcitool scan
Scanning ...
        00:80:25:20:92:2F       SMA002d SN: 2100519689 SN2100519689

I've also sniffed my inverter codes by discovering the hex numbers in the 
payloads as below:

32004700430099000bff7d017e3e004000ff00222daeffffffffffff01007eff03606509a0ffffff
ffffff00007800676f9a3600000000000001800002000000000000000000005d267e86

and

32004900450099000bff81017e40003e00ff00222dae2f922025800001007eff03606509e04e0009
63337d5d00007800676f9a36000000000000088000020070f07d3117504462185049b47e86

which has led me to my specific inverter codes are:

Code1 0x67
Code2 0x6f
Code3 0x9a
Code4 0x36
InvCode 0x4e

I've added these to my invcode.in as 4000TL20, and edited my smatool.conf 
accordingly.

Unfortunately, though I believe I've done all the steps required, I still 
cannot get it to work :-(

I will attach my files here also as reference and will provide any more info as 
needed.

Can someone please provide me with some help or suggest what I've done wrong, 
or what I need to do to fix this?  My goal here initially is to grab only the 
real-time power figure, but will later integrate with PVOutput (I'm currently 
using PVBeancounter on Windows to do this)

Thanks in advance :-)

marc

Original issue reported on code.google.com by MarcCarn...@googlemail.com on 19 Aug 2012 at 12:43

Attachments:

GoogleCodeExporter commented 8 years ago 
Here also is my Snoopypro sniff output log, for completeness,

Original comment by MarcCarn...@googlemail.com on 19 Aug 2012 at 12:47

Attachments:

GoogleCodeExporter commented 8 years ago 
Hi Mark, 
I'm running on Arch linux, and am using a HAMA bluetooth dongle.

I went for very simple steps to get something working - I eliminated the mysql 
database settings from the smatool.conf only specifying BTAddress, Password, 
and File. I also tried updating my pi firmware and my arch linux installation.

Then I just ran smatool on it's own and it seemed to work.

The other thing that I was doing wrong early on could have been the time on my 
Pi, which was stuck in 1970, and as I'm running via WiFi using an EdiMax dongle 
I had to make sure that ntpd was being called at the right point in my startup.

I'm still running without database support and have opted to munge the output 
using a simple perl script to make it look like the csv files you get from SMA 
SunnyExplorer, so I can pass them through my chart drawing scripts (using 
Google Chart API, dropbox_uploader, and droppages to upload to a website. 
http://chrisg67.droppages.com/Solar+Panels).

Hope this helps.

Original comment by chris...@gmail.com on 19 Sep 2012 at 10:10