sbfspot / sbfspot Goto Github PK

I have a dual SB2000HF-30 inverter setup. I noticed some weird outputs for string 2. I have tried with different versions of SBFspot (2.0.6, 2.4.1, 2.4.5).

The returned values for string 2 are allways the same:
String 2 Pdc: 1934451.817kW - Udc: 7789238.54V - Idc: 878461.746A

According to SBF this is a bug, since all String 2 values should be zero since a SB2000HF-30 has only 1 MPP tracker.
(http://www.sma-benelux.com/nl_BE/producten/omvormers/sunny-boy/sunny-boy-2000hf-2500hf-3000hf.html - Aantal van de onafhankelijke MPP-ingangen / strings per MPP-ingang).

See attachment for examples

Attachments

outputs.txt
debug.zip

This work item was migrated from CodePlex

CodePlex work item ID: '41'
Assigned to: 'SBF'
Vote count: '1'

Hello,

i update to Version 2.4.

Everything works, but following message appears when update smaspot with command -u:

There ist somethin wrong with "getSystemData"

Hier the debug-Log (-d5 -v5)

ExportEventsToCSV()
PVOutput::getSystemData()
getSystemData() returned -1: Unknown error
PVOutput::Export()
OK 200: Added Status

This work item was migrated from CodePlex

CodePlex work item ID: '15'
Vote count: '1'

hi,

When I try to configure the mail settings for the watchdog on my raspberry Pi I get an 404 not found on the below file.

wget http://cache.gawker.com/assets/images/lifehacker/2010/06/muttrc-gmail.txt

Is this still available?

Bart

This work item was migrated from CodePlex

CodePlex work item ID: '22'
Vote count: '1'

type: missing default setting for parameter
impact: minor (since no one has reported this since . . . )
version: v240 (but expected to apply to previous as well)

description:
result of regression test on v240-rc4203

in the present release (and previous ones):
-output path is an obligatory parameter
-when the parameter is omitted then the default path is not applied

the std-err.txt gives "Missing OutputPath."

note that the part of the code that handles the config has been drastic modified
-in version v156 the code still caters for the default path for windows or linux

kr wim

This work item was migrated from CodePlex

CodePlex work item ID: '12'
Vote count: '1'

After starting SMAspot the inverters will be not connected but an error occures:

pi@Raspberry-Server ~/SMAspot24/bin/Release $ ./SMAspot -cfgSolarpark_TEST.cfg
SMAspot V2.4.0
Yet another tool to read power production of SMA solar inverters
(c) 2012-2014, SBF (https://smaspot.codeplex.com)
Compiled for Linux 32 bit

Commandline Args: -cfgSolarpark_TEST.cfg
Missing timezone.0x52284

This work item was migrated from CodePlex

CodePlex work item ID: '14'
Vote count: '1'

Feature request:

enable SBFspot to read data from the SMA Energy Meter. Protocoll is documented at EB-Systeme.de. Site is unfortunatelly in German, if you need a translation, I can support you.

With having this feature implemented, it would be possible to see also the consumption and feed in data and not only the producing side of the inverter. Based on this information it would be easily possible to do some usage optimization with i. e. FHEM Home Automation to start and stop electric components based on the availability of solar power.

This work item was migrated from CodePlex

CodePlex work item ID: '44'
Assigned to: 'SBF'
Vote count: '17'

The day archive fails after a DST switch.

The bug is found in 2.06 as well as in 2.2.11, the fix is for 2.2.11

the fix is as follows:
*** bug/SMAspot.cpp 2014-01-22 13:36:48.000000000 +0100
--- fix/SMAspot.cpp 2014-03-30 11:11:21.664330942 +0200

*** 576,581 ****
--- 576,583 ----
puts("********************");
}

startTime -= 86400; // to overcome problem with DST transition - RB@20140330

E_SMASPOT rc = E_OK;
struct tm start_tm;
memcpy(&start_tm, localtime(&startTime), sizeof(start_tm));

*** 583,588 ****
--- 585,591 ----
start_tm.tm_hour = 0;
start_tm.tm_min = 0;
start_tm.tm_sec = 0;

start_tm.tm_mday += 1; // to overcome problem with DST transition - RB@20140330
startTime = mktime(&start_tm);

if (VERBOSE_NORMAL)

This work item was migrated from CodePlex

CodePlex work item ID: '23'
Assigned to: 'SBF'
Vote count: '2'

if this text is bad readable this is due to automated text treatment by codeplex sorry for that
(i'm trying to understand what magical trics i need to overcome that microsoft broll and fix this)

dear all, this issue reflects the results on tests about the usage of the option -aenn
the option (see wishlist and new-in-v240) allows to retrieve the archived events from an inverter
note: the archive events option is also part of the functions offered by SunnyExplorer

at present SMAspot creates a file with the events, the name is coded as yyffmf01-yyttmt01
where
yyff stands for year-from mf is monthfrom day is allways 01
yytt stands for year till mt is month till day is allways 01

based on my experience i will open a seperate feature enhancement request for extension-improvements
may i ask
to handle comments about further evolution of this function via issue-CP010
comments on the actual functionality to be treated via this issue-CP009

issue-09-1 the DaTim-TILL yyttmt01 is named one month to early
example on 11februari2014 the code 20140201 is used instead of 20140228 or 20140301
rounding up to (the first second of) the next month is ok

issue-09-2 the DaTim FROM yyffmf01 is named also one month to early
example the file that holds events since 01dec2013 has the code 20131101 in stead of 20131201

issue-09-3 if the option ae0 is used then an empty file is created
it should be more logic that there is NO file generated at all
this is a minor issue
note: for this issue that file is named 20140201-20140201 (status 11feb)
about workarounds:

since the filename is specific, one can treat this by deleting once a month the files of previous month
from the directory with the output-events,

alternative, if in the CLI opion ae0 is used one can direct these unneeded files to a trash directory
by entering that path in the SMAspot cfg
this might be easier to remove/delete these files (since in a distinct environment)

issue-09-4 simular to the issue on the missing last record on the monthly file
refer to a similar issue for the last record of the month when using -am1
see discussions and issues in google-code

--short-description
when at the first of a month the option -ae1 is used then the last events
(end of day on last day of previous month) might not get in the archives

issue-09-5 when in the outputpath-events the option%d is used (idem for %m)
the archive events module does not translate the option %d into the day (it remains %d) (better is 00)
this issue is to be treated together with the older issues documented in google-code
abouth the options %y%d%m for output path
note: this is also the case when "outputpath-events" is not specified and the default options apply
the archive events module does not cope with %d%m as part of the pathname for "outputpath"

issue-09-6 for a number of events the values for old and/or new are not meaningfull

rational: some events do not have an old or new value,
in this case the value is 0d-1 or an equivalent
examples: time-set events

proposal: depending on the event (step-step) evolution
SMAspot can provide an interpretation of the -1 value and put either "" or NAv in the events table
compare to SunExplo

kr wim

Attachments

SMAspot-5a.cfg

This work item was migrated from CodePlex

CodePlex work item ID: '9'
Vote count: '1'

My 4000TL is regularly logging "Isolat.Resistance" events, this something my installer is looking into.

These show up regularly and accurately on the Sunny Bean, however SMAspot (v241) is not decoding the events correctly. I've attached the March event log and there are some interesting dates in there as well as bogus events.
I am unable to attach April's event log since one of the time_t values is causing a core dump ...

gdb output:

Program received signal SIGSEGV, Segmentation fault.
0x0000000000434e52 in strftime_t (format=0x7fffffffe6f0 "%d/%m/%Y %H:%M:%S", rawtime=-7705658810006515610) at misc.cpp:56
56 memcpy(&tm_struct, localtime(&rawtime), sizeof(tm_struct));

I'm up and running again with -ae0, but would like to get events working and can help debug the issue while I have a plentiful supply of events.

Attachments

shineytiles-User-Events-201403-201403.csv

This work item was migrated from CodePlex

CodePlex work item ID: '30'
Vote count: '1'

My Raspberry Pi stopped uploading data collected from my two SMA inverters. It stopped after updating ONE reading this morning: 2017/10/11
The log updates with error messages.
Herewith the first entries of the day:
[05:45:38] INFO: Uploading 2 datapoints, starting with 20171022,05:40,1688167,0,
,,17.6,243.4 => OK (200)
[05:45:48] INFO: Uploading 2 datapoints, starting with 20171022,05:40,1785710,0,
,,18,243.01 => OK (200)
[05:50:39] ERROR: Uploading datapoint: 20171022,05:50,1688178,20258148,,,19.6,24
3.64 Bad request 400: Power value [20258148] too high for system size [3328]

Herewith the last two lines from my log file.
[12:44:39] ERROR: Uploading 82 datapoints, starting with 20171022,05:50,1688178,
20258148,,,19.6,243.64 Bad request 400: Power value [20258148] too high for syst
em size [3520]
[12:44:48] ERROR: Uploading 82 datapoints, starting with 20171022,05:50,1785720,
21428652,,,19.7,243.34 Bad request 400: Power value [21428652] too high for syst
em size [3655]

The capacity for the strings in PVOutput are: 3655 Watt & 3520 Watt

05h50 in the morning only 120Watt was generated (About the same as in the passed)

I also rebooted the Pi just in case - stays the same.

Some pointers would be appreciated.

Regards

Frits

dear luc,

I'd like to reopen the issue 021(&047) as reported via "google code" - on the codeplex platform
various causes for this issue have been identified earlier
freek found that the issue does still appear in version 2.2.10
nb: see googlecode for freek's info
kr wim

This work item was migrated from CodePlex

CodePlex work item ID: '3'
Assigned to: 'SBF'
Vote count: '2'

Hi Luc,

I know it is not really a new issue, but decided to add it... as I'd really appreciate to benefit from the important new features of the promising 3.0.

Issue => SMAspot MIS added from 2.1.x is incompatible with the SMA Webbox.

The reason is the SMAspot i/o protocol used till 2.06a ('brute' direct access to the inverter) was replaced by a SMA BT network access aimed to be compatible with SMA standard network protocol.

This SMAspot 2.1.x BT network protocol has however always had a limited compatibility... in particular, SMAspot does not work at all when a Webbox is present on the network.

We agree the compatibility issue is unmanageable, as your hobby lab does not have a Webbox.

You suggested me to try MIS=0. This has not solved the problem as it appears disabling multi-inverter access does not instruct SMAspot to switch from the network protocol back to the original direct access one.

The Webconnect protocol has been added since. So it looks SMAspot is modular enough to support multiple protocols. Then, why not adding (reintroducing) support of the SMA inverter direct BT access protocol which was used till 2.06a ?

This work item was migrated from CodePlex

CodePlex work item ID: '36'
Vote count: '1'

I would like to suggest the the -finq cli flag should also force uploading to pvoutput (or other online monitoring tools), alternatively, if SMAspot determines it is nighttime it should log a debug message "skipping upload to online monitoring (pvoutput etc) when it is dark", rather than silently skipping the upload.

I spent about an hour troubleshooting pvoutput uploads the other night, until I found a reference (in the old forums) that pvupload is skipped when it is dark: https://groups.google.com/d/msg/sma-spot/eMRrJ1GSjeQ/6WdqcOp1E0UJ

This work item was migrated from CodePlex

CodePlex work item ID: '29'
Vote count: '1'

I had one inverter and SMAspot 206 and everything was fine.
Now i have 2 inverters, inverter 1 still works fine with 206.
i made a 2nd cfg for inverter 2 but it does not work:
Commandline Args: -cfgSMAspot2.cfg -v
Tue Apr 1 11:33:13 2014: INFO: Starting...
sunrise: 06:53
sunset : 19:43
Connecting to 00:80:25:2D:28:2E (1/10)
...
Connecting to 00:80:25:2D:28:2E (10/10)
Tue Apr 1 11:34:05 2014: CRITICAL: BT_Connect() returned -1

i tried the 2.4.2 version, but it also reads my radio controlled sockets and adds them to my output and this is the result:
Bad request 400: Energy value [2147483647] too high for system size [3675]
Tue Apr 1 11:30:29 2014: INFO: Done.

Commandline Args: -v5
Reading config './SMAspot.cfg'
Tue Apr 1 11:38:00 2014: INFO: Starting...
sunrise: 06:53
sunset : 19:43
Connecting to 00:80:25:A4:83:A2 (1/10)
Initializing...
SUSyID: 125 - SN: 808578481 (0x3031EDB1)
SMA netID=04
SUSyID: 138 - SN: 2130135834
SUSyID: 191 - SN: 172000934
SUSyID: 191 - SN: 172004298
SUSyID: 191 - SN: 172002669
SUSyID: 138 - SN: 2130282887
BT Signal=76%
Logon OK

the SN beginning with 172 are the radio sockets with some strange readings:
SUSyID: 191 - SN: 172004298
Pac max phase 1: 1299333462W
Pac max phase 2: 1715692655W
Pac max phase 3: 1096167015W
...
SUSyID: 191 - SN: 172004298
Energy Production:
EToday: 7020378737416761.000kWh
ETotal: 3760841250522883.000kWh
Operation Time: 7719.34h
Feed-In Time : 1623830055690497.50h

...
SUSyID: 191 - SN: 172004298
DC Spot Data:
String 1 Pdc: 1835353.125kW - Udc: 8253074.00V - Idc: 1919252.125A
String 2 Pdc: 224685.656kW - Udc: 12287478.00V - Idc: 779249.000A

and so on...how can i fix this?

This work item was migrated from CodePlex

CodePlex work item ID: '25'
Vote count: '1'

Hello.
to use MariaDB10, the port is changed to 3307. Can I change the port in SBFspot, 3.12 is running here. Adding the port in my.cnf don't work.

greets, mike

It seems the efficiency value in de spot file (column) 22, now displays values between 0 and 2106521984000

Those are quite high percentage numbers ;)

This work item was migrated from CodePlex

CodePlex work item ID: '18'
Vote count: '1'

dear luc, - since this is the new working environment

I'll tried to put a new comment on the wishlist, but could not find an option to do this
kr wim

This work item was migrated from CodePlex

CodePlex work item ID: '1'
Vote count: '1'

When i use SMAspot -v5 -d5

it gives me the values

Energy Production:
EToday: 0.000kWh
ETotal: 8092788451938808.000kWh
Operation Time: 929751122702104.50h
Feed-In Time : 2245421862777695.00h

I have a new STP-7000TL20

Any suggestion ?
Im using SMAspot V2.4.1
I've already set the CalculateMissingSpotValues=0

Attachments

logfile.txt

This work item was migrated from CodePlex

CodePlex work item ID: '27'
Vote count: '1'

Dear SMAspot team,
I have an issue with smaspot on my system. make release is successfull, but SMAspot stops with a segmentation fault. See attached strace file for more information.

Thanks,
doolro

Attachments

strace.txt

This work item was migrated from CodePlex

CodePlex work item ID: '2'
Vote count: '1'

Hi All,

I have 2 SMA SunnyBoy SB 3000HF-30 and i want to log the data on SQL DB.
I test yet on Windows 8.1 x64 but in future i want to install on raspberry PI.

My problem is i can't connect on my 2 inverters. I find with -scan the 2 MAC address but if a specified one on .cfg file i receive this error :
C:\SMA\SMAspot_V241_Win32>SMAspot.exe -d5 -v5
SMAspot V2.4.1
Yet another tool to read power production of SMA solar inverters
(c) 2012-2014, SBF (https://smaspot.codeplex.com)
Compiled for Windows 32 bit

Commandline Args: -d5 -v5
Reading config 'SMAspot.cfg'
Mon Mar 17 18:08:26 2014: INFO: Starting...
sunrise: 06:53
sunset : 18:48
Connecting to 00:80:25:29:F9:96 (1/10)
Connecting to 00:80:25:29:F9:96 (2/10)
Connecting to 00:80:25:29:F9:96 (3/10)
Connecting to 00:80:25:29:F9:96 (4/10)
Connecting to 00:80:25:29:F9:96 (5/10)
Connecting to 00:80:25:29:F9:96 (6/10)
Connecting to 00:80:25:29:F9:96 (7/10)
Connecting to 00:80:25:29:F9:96 (8/10)
Connecting to 00:80:25:29:F9:96 (9/10)
Connecting to 00:80:25:29:F9:96 (10/10)
Mon Mar 17 18:09:26 2014: CRITICAL: bthConnect() returned 10060

On Windows in Bluetooth setting a can connect on Inverter with the password 0000. Also is not a password problem.

Have you a solution ?

Thank You.

Attachments

SMAspot_left.cfg

This work item was migrated from CodePlex

CodePlex work item ID: '19'
Vote count: '1'

Hi,

Apparently my Inverter is unknow and smaspot throws this exception:

0x00002351 and Inverter Type=...

regards,

Bart

This work item was migrated from CodePlex

CodePlex work item ID: '21'
Vote count: '1'

For some reason it wouldnt give me data.

I've tried 2 different bt dongels. Those bt dongels worked for me with other inverters. (sb 1200, STP 10000, STP 6000).

But with my STP8000-tl10 not.

I've updated the inverter firmware, tought it's maybe a bug or something.

Any idea how to solve this problem?

Here's my debug info.

SMAspot V2.2.10
Yet another tool to read power production of SMA solar inverters
(c) 2012-2013, SBF (http://code.google.com/p/sma-spot)
Compiled for Linux 32 bit

Commandline Args: -d5 -v5
Mon Jan 27 16:27:35 2014: INFO: Starting...
sunrise: 08:26
sunset : 17:24
Connecting to 00:80:25:26:4E:D6 (1/10)
Initializing...
SUSyID: 125 - SN: 957697851 (0x39154F3B)
--------: 00 01 02 03 04 05 06 07 08 09
00000000: 7E 17 00 69 00 00 00 00 00 00
00000010: 01 00 00 00 00 00 01 02 76 65
00000020: 72 0D 0A
23 Bytes sent
getPacket(2)
MAX_CommBuf is now 18 bytes
Received 18 bytes
Received 13 bytes
--------: 00 01 02 03 04 05 06 07 08 09
00000000: 7E 1F 00 61 D6 4E 26 25 80 00
00000010: 00 00 00 00 00 00 02 00 00 04
00000020: 70 00 03 00 00 00 00 01 00 00
00000030: 00
cmd=2
<<<====== Content of pcktBuf =======>>>
--------: 00 01 02 03 04 05 06 07 08 09
00000000: 7E 1F 00 61 D6 4E 26 25 80 00
00000010: 00 00 00 00 00 00 02 00 00 04
00000020: 70 00 03 00 00 00 00 01 00 00
00000030: 00
<<<=================================>>>
MAX_pcktBuf is now 31 bytes
SMA netID=03
--------: 00 01 02 03 04 05 06 07 08 09
00000000: 7E 1F 00 61 00 00 00 00 00 00
00000010: D6 4E 26 25 80 00 02 00 00 04
00000020: 70 00 03 00 00 00 00 01 00 00
00000030: 00
31 Bytes sent
getPacket(10)
Received 18 bytes
Received 13 bytes
--------: 00 01 02 03 04 05 06 07 08 09
00000000: 7E 1F 00 61 D6 4E 26 25 80 00
00000010: 00 00 00 00 00 00 0A 00 D6 4E
00000020: 26 25 80 00 01 ED 57 50 DD 09
00000030: 00
cmd=10
<<<====== Content of pcktBuf =======>>>
--------: 00 01 02 03 04 05 06 07 08 09
00000000: 7E 1F 00 61 D6 4E 26 25 80 00
00000010: 00 00 00 00 00 00 0A 00 D6 4E
00000020: 26 25 80 00 01 ED 57 50 DD 09
00000030: 00
<<<=================================>>>
Root device address: 00:80:25:26:4E:D6
Local BT address: 00:09:DD:50:57:ED
getPacket(5)
Received 18 bytes
Received 2 bytes
--------: 00 01 02 03 04 05 06 07 08 09
00000000: 7E 14 00 6A D6 4E 26 25 80 00
00000010: 00 00 00 00 00 00 0C 00 02 00
cmd=12
Received 18 bytes
Received 16 bytes
--------: 00 01 02 03 04 05 06 07 08 09
00000000: 7E 22 00 5C D6 4E 26 25 80 00
00000010: 00 00 00 00 00 00 05 00 D6 4E
00000020: 26 25 80 00 01 01 ED 57 50 DD
00000030: 09 00 02 01
cmd=5
<<<====== Content of pcktBuf =======>>>
--------: 00 01 02 03 04 05 06 07 08 09
00000000: 7E 22 00 5C D6 4E 26 25 80 00
00000010: 00 00 00 00 00 00 05 00 D6 4E
00000020: 26 25 80 00 01 01 ED 57 50 DD
00000030: 09 00 02 01
<<<=================================>>>
MAX_pcktBuf is now 34 bytes
Device 0: 00:80:25:26:4E:D6 -> Inverter
Device 1: 00:09:DD:50:57:ED -> Local BT Address
--------: 00 01 02 03 04 05 06 07 08 09
00000000: 7E 15 00 6B ED 57 50 DD 09 00
00000010: D6 4E 26 25 80 00 03 00 0A 00
00000020: AC
21 Bytes sent
getPacket(4)
Received 18 bytes
Received 5 bytes
--------: 00 01 02 03 04 05 06 07 08 09
00000000: 7E 17 00 69 D6 4E 26 25 80 00
00000010: ED 57 50 DD 09 00 04 00 0A 00
00000020: 00 00 AC
cmd=4
<<<====== Content of pcktBuf =======>>>
--------: 00 01 02 03 04 05 06 07 08 09
00000000: 7E 17 00 69 D6 4E 26 25 80 00
00000010: ED 57 50 DD 09 00 04 00 0A 00
00000020: 00 00 AC
<<<=================================>>>
--------: 00 01 02 03 04 05 06 07 08 09
00000000: 7E 14 00 6A ED 57 50 DD 09 00
00000010: D6 4E 26 25 80 00 03 00 02 00
20 Bytes sent
getPacket(4)
Received 18 bytes
Received 6 bytes
--------: 00 01 02 03 04 05 06 07 08 09
00000000: 7E 18 00 66 D6 4E 26 25 80 00
00000010: ED 57 50 DD 09 00 04 00 02 00
00000020: 00 00 84 03
cmd=4
<<<====== Content of pcktBuf =======>>>
--------: 00 01 02 03 04 05 06 07 08 09
00000000: 7E 18 00 66 D6 4E 26 25 80 00
00000010: ED 57 50 DD 09 00 04 00 02 00
00000020: 00 00 84 03
<<<=================================>>>
--------: 00 01 02 03 04 05 06 07 08 09
00000000: 7E 15 00 6B ED 57 50 DD 09 00
00000010: D6 4E 26 25 80 00 03 00 01 00
00000020: 01
21 Bytes sent
getPacket(4)
Received 18 bytes
Received 5 bytes
--------: 00 01 02 03 04 05 06 07 08 09
00000000: 7E 17 00 69 D6 4E 26 25 80 00
00000010: ED 57 50 DD 09 00 04 00 01 00
00000020: 00 00 01
cmd=4
<<<====== Content of pcktBuf =======>>>
--------: 00 01 02 03 04 05 06 07 08 09
00000000: 7E 17 00 69 D6 4E 26 25 80 00
00000010: ED 57 50 DD 09 00 04 00 01 00
00000020: 00 00 01
<<<=================================>>>
Waiting for network to be built...
getPacket(255)
Timeout reading socket
No data!
getPacket(255)
Timeout reading socket
No data!
getPacket(255)
Timeout reading socket
No data!
getPacket(255)
Timeout reading socket
No data!
getPacket(255)
Timeout reading socket
No data!
getPacket(255)
Timeout reading socket
No data!
Mon Jan 27 16:28:36 2014: CRITICAL: Failed to initialize communication with inverter.

This work item was migrated from CodePlex

CodePlex work item ID: '4'
Vote count: '1'

Several times a day I got the following error with Sunny Island 6.0H logon:

SMAspot V2.2.11
Yet another tool to read power production of SMA solar inverters
(c) 2012-2014, SBF (https://smaspot.codeplex.com)
Compiled for Windows 32 bit

Commandline Args: -finq -v
Sun Feb 02 21:50:48 2014: INFO: Starting...
sunrise: 08:18
sunset : 17:34
Connecting to Local Network...
Initializing...
SUSyID: 125 - SN: 996845127 (0x3B6AA647)
Inverter IP address: 192.168.0.136 found via broadcastidentification
Sun Feb 02 21:50:48 2014: CRITICAL: Logon failed. Check 'USER' Password

Currently I am running SMAspot every 2 minutes. The error disappears after some minutes of failed logons. Then everything is fine until the next logon error.

Attachments

SMAspot242.zip
island.jpg

This work item was migrated from CodePlex

CodePlex work item ID: '5'
Vote count: '1'

The by the -wsl parameter generated string, shows only data for the first inverter on a multi inverter plant.

How to output the inverter data for all inverters? Any way to log the whole data in a csv file?

This work item was migrated from CodePlex

CodePlex work item ID: '35'
Vote count: '1'

Hi,
I cannot get the tool running, because it does not find the config file.
D:\Downloads\SMAspot>SMAspot.exe
SMAspot V2.4.0
Yet another tool to read power production of SMA solar inverters
(c) 2012-2014, SBF (https://smaspot.codeplex.com)
Compiled for Windows 32 bit

Commandline Args:
Error! Could not open file SMAspot.exeSMAspot.cfg

Trying to pass the cfg parameter:
D:\Downloads\RaspberryPi\SMAspot>SMAspot.exe -cfgSMASpot.cfg
SMAspot V2.4.0
Yet another tool to read power production of SMA solar inverters
(c) 2012-2014, SBF (https://smaspot.codeplex.com)
Compiled for Windows 32 bit

Commandline Args: -cfgSMASpot.cfg
Error! Could not open file SMAspot.exeSMASpot.cfg

btw: I love SMASpot :-)

Attachments

wsi7g051.4211F-tst-CPl008.txt
sunny.cmd

This work item was migrated from CodePlex

CodePlex work item ID: '8'
Assigned to: 'SBF'
Vote count: '1'

Hi I downloaded the 2.4.4. release and compiled it for linux (raspberry pi). When I run the application this is the output:

sudo ./SMAspot -v -u -finq
SMAspot V2.4.2
Yet another tool to read power production of SMA solar inverters
(c) 2012-2014, SBF (https://smaspot.codeplex.com)
Compiled for Linux 32 bit

Commandline Args: -v -u -finq
Reading config './SMAspot.cfg'
Invalid value for 'PVoutput_SID' (>0)

The PVoutput_SID is entered and correct (checked it with an older version of SMAspot)

This work item was migrated from CodePlex

CodePlex work item ID: '34'
Vote count: '1'

For a yet unknown reason I have hanging SMAspot invocations, occurred both with 2.2.10 and 2.4.5 on a Raspberry Pi, hanging around, which I have to kill in order to get rid of them. My solution is to put "timeout 4m " in front of the command to start SMAspot in the shell script scheduled in the cronjob.

This work item was migrated from CodePlex

CodePlex work item ID: '43'
Vote count: '1'

dear all,
be aware that for v240 - rc4203 the following files must be copied to the prog.dir (the dir where SMAspot)

all files can be found in the "sources"
date_time_zine.csv
tagfiles (for all languages) at least the default one for "en-us"

insert in your smaspot.cfg file the parameter (example given): timezone=europe/brussels

for windows users:
if you have an error that indicates that the wrond .dll is looked for, you can use the below workaround
(info from s.b.f)
-- install Microsoft Visual C++ 2010 SP1 Redistributable Package (x86)
can be found at: http://www.microsoft.com/en-us/download/details.aspx?id=8328

remark: boost is not absolute needed

a minor issue:
even when using the option -ae0 there will be an empty archive events file created

NOTE: the problem with -ae0 is documented in a seperate issue (dd11feb)

kr wim

This work item was migrated from CodePlex

CodePlex work item ID: '6'
Assigned to: 'SBF'
Vote count: '1'

First day of month I get the message: "There is no data to export!" on every run (5 minute cronjob):
/usr/local/gvs_cron/SMAspot240/bin/Release/SMAspot -ad2 -am2 -v0 -q -d0
This happend last month as well.

This work item was migrated from CodePlex

CodePlex work item ID: '26'
Vote count: '1'

Hi,

I have data missing in pvoutput.org. To be sure I first queried the converter to (re)get the data with the SBFspot -ad65 option (in my case 65 days would more than cover the missing data). I also tried deleting the last few months in the database and reget the data from the converter. The data is visible in the database and has the pvoutput field set to null. However, the upload daemon won't upload this data. Is this because after the set of 'null' values there are more recent records with pvoutput=1 and the 'gap' of null values is not seen? I would expect the upload daemon to upload everything that has pvoutput value null.

To be clear, the daemon is uploading recent records just fine.

https://www.pvoutput.org/list.jsp?userid=45550
Data missing from 25 aug to 20 sep this year. This data is available in the sqlite database (with the null values).

Also am I right in assuming that the daemon will just upload everything without 'negotiating' with pvoutput.org if the records are needed?

Regards,
Arjan

First of all: Great work. Many thanks for creating this. The manual is fantastic, specially for non experienced users. I do have a question though (sorry, I realize that this is mainly because of the lack of knowledge):
I followed the manual and for downloading the sourcecode I thought to be clever and to change the download command to the latest version 240 on this site
(wget https://smaspot.codeplex.com/downloads/get/SMAspot_SRC_240_Linux_Win32.tar)
.That worked like a charm and the system dowloaded the file and I could see the file in the directory. However I could not extract this file with the "tar" command. I got the following response:
-This does not look like a tar archive
-tar: Skipping to next header
-tar: Exiting with failure status due to previous errors

If I just download the version in the manual from the googlecode site (wget https://sma-spot.googlecode.com/files/SMAspot_SRC_206_Linux_Win32.tar) everything works as expected.

Do I do something wrong?

Small other question: I saw some remarks regarding date_time changes to be made. Is this also applicable for version 206?
Many thanks

This work item was migrated from CodePlex

CodePlex work item ID: '7'
Vote count: '1'

dear s.b.f.

i recently found that the time-out for a succesfull connect has slightly increased

in earlier versions (i have not yet gone through my log-files to identify from which version this changed)

time-out for 10060 was about 50seconds (10 * 5sec)

to-day (since ??) this time-out is slightly above 60seconds (10 * 6sec)??)

as such this actual behaviour creates a problem when using SMAspot in repeat mode

repeats < or = 60seconds

as i informed earlier: - from the statistics i do gather form my scripts
it has been observed that >99%connects were succefull within 20seconds (4 * 5seconds)
till to-day no success connect has been observed that lasted between 5<->10 * 5 seconds

so from observation one can state that the connect time-out can be reduced to <28 (5 * 5) or (4*6) seconds

note: i refer to our earlier wishliss demand from ron and myself:
?? introduce an option to modify (reduce) the number of repeats ?? eg to 5
nb: some sections in the code are prepared to use parameters: -nbr-of-repeats; -time-out-value-per-try

note: i did find that time-out for 10050 - 10051 is now 0,?seconds (10 * 0,?? <=1seconds)
(i have not gone through my old log-files to identify whether this is equal to older versions)

This work item was migrated from CodePlex

CodePlex work item ID: '28'
Vote count: '1'

Inverter SMA 6000TL-21 dont work .

This work item was migrated from CodePlex

CodePlex work item ID: '20'
Vote count: '1'

I'm using SMAspot for SB4000 and SB3000. On the SB3000, the Pdc is not decoded correctly, see below:

Energy Production:
EToday: 10.173kWh
ETotal: 7364.535kWh
Operation Time: 11282.59h
Feed-In Time : 10233.37h

SUSyID: 99 - SN: 2001716598
DC Spot Data:
String 1 Pdc: 1917271.250kW - Udc: 316.00V - Idc: 8.112A
String 2 Pdc: 1934451.875kW - Udc: 7789238.50V - Idc: 878461.750A

SUSyID: 99 - SN: 2001716598
AC Spot Data:
Phase 1 Pac : 1635021.625kW - Uac: 234.00V - Iac: 10.379A
Phase 2 Pac : 1730176.375kW - Uac: 0.00V - Iac: 0.000A
Phase 3 Pac : 543451.500kW - Uac: 0.00V - Iac: 0.000A

Udc and Idc are fine for DC spot data (only string 1 is in use).
It might also make sense to provide better detection for unused strings instead of displaying fantasy data.

This work item was migrated from CodePlex

CodePlex work item ID: '39'
Vote count: '1'

Hi all,
first of all I want to express my thanks to all involved in developing this cool software.
I set up a Raspberry Pi for collecting two Inverter's (one SB5000TL-20 and SB4000TL-20) energey production.
I installed the newest version of wheezy on the Pi, connected a BT dongle supported by wheezy (ASUS USB-BT211).
With "hcitool -scan" I can see both Inverters.
I installed SMAspot V2.4.2 and compiled it.
Also I created two config files for each converter, and put the BT-Address in there.
Now I am facing a problem with the communication between the inverters and SMAspot:
Tue Apr 15 19:43:37 2014: CRITICAL: Failed to initialize communication with inverter.
I tried other USB sticks, and just to make sure I took the Pi to a friend's house where I could read the Inverter's data without any issues.
But with the inverters here it just don't work.
Has anybody an idea what could be wrong? Find below the output of SMAspot started with the debugging option.
Any help is highly appreciated.
Thanks a lot!
Christian

root@sunnyboygate:/home/pi/smaspot/bin/Release# ./SMAspot -finq -v -d5__SMAspot V2.4.2
Yet another tool to read power production of SMA solar inverters
(c) 2012-2014, SBF (https://smaspot.codeplex.com)
Compiled for Linux 32 bit

Commandline Args: -finq -v -d5
Reading config './SMAspot.cfg'
Tue Apr 15 19:45:20 2014: INFO: Starting...
sunrise: 04:21
sunset : 18:02
Connecting to 00:80:25:08:6C:FB (1/10)
Initializing...
SUSyID: 125 - SN: 986811088 (0x3AD18AD0)
--------: 00 01 02 03 04 05 06 07 08 09
00000000: 7E 17 00 69 00 00 00 00 00 00 
00000010: 01 00 00 00 00 00 01 02 76 65 
00000020: 72 0D 0A 
23 Bytes sent
getPacket(2)
MAX_CommBuf is now 18 bytes
Received 18 bytes
Received 9 bytes
--------: 00 01 02 03 04 05 06 07 08 09
00000000: 7E 1B 00 65 FB 6C 08 25 80 00 
00000010: 00 00 00 00 00 00 02 00 00 03 
00000020: 70 00 02 01 00 00 00 
cmd=2
<<<====== Content of pcktBuf =======>>>
--------: 00 01 02 03 04 05 06 07 08 09
00000000: 7E 1B 00 65 FB 6C 08 25 80 00 
00000010: 00 00 00 00 00 00 02 00 00 03 
00000020: 70 00 02 01 00 00 00 
<<<=================================>>>
MAX_pcktBuf is now 27 bytes
SMA netID=02
--------: 00 01 02 03 04 05 06 07 08 09
00000000: 7E 1F 00 61 00 00 00 00 00 00 
00000010: FB 6C 08 25 80 00 02 00 00 04 
00000020: 70 00 02 00 00 00 00 01 00 00 
00000030: 00 
31 Bytes sent
getPacket(10)
Received 18 bytes
Received 9 bytes
--------: 00 01 02 03 04 05 06 07 08 09
00000000: 7E 1B 00 65 FB 6C 08 25 80 00 
00000010: 00 00 00 00 00 00 07 00 08 00 
00000020: 03 01 00 00 00 00 00 
cmd=7
Received 18 bytes
Received 13 bytes
--------: 00 01 02 03 04 05 06 07 08 09
00000000: 7E 1F 00 61 FB 6C 08 25 80 00 
00000010: 00 00 00 00 00 00 0A 00 FB 6C 
00000020: 08 25 80 00 01 10 1E 3F 72 02 
00000030: 00 
cmd=10
<<<====== Content of pcktBuf =======>>>
--------: 00 01 02 03 04 05 06 07 08 09
00000000: 7E 1F 00 61 FB 6C 08 25 80 00 
00000010: 00 00 00 00 00 00 0A 00 FB 6C 
00000020: 08 25 80 00 01 10 1E 3F 72 02 
00000030: 00 
<<<=================================>>>
MAX_pcktBuf is now 31 bytes
Root device address: 00:80:25:08:6C:FB
Local BT address: 00:02:72:3F:1E:10
getPacket(5)
Received 18 bytes
Received 16 bytes
--------: 00 01 02 03 04 05 06 07 08 09
00000000: 7E 22 00 5C FB 6C 08 25 80 00 
00000010: 00 00 00 00 00 00 05 00 FB 6C 
00000020: 08 25 80 00 01 01 10 1E 3F 72 
00000030: 02 00 02 01 
cmd=5
<<<====== Content of pcktBuf =======>>>
--------: 00 01 02 03 04 05 06 07 08 09
00000000: 7E 22 00 5C FB 6C 08 25 80 00 
00000010: 00 00 00 00 00 00 05 00 FB 6C 
00000020: 08 25 80 00 01 01 10 1E 3F 72 
00000030: 02 00 02 01 
<<<=================================>>>
MAX_pcktBuf is now 34 bytes
Device 0: 00:80:25:08:6C:FB -> Inverter
Device 1: 00:02:72:3F:1E:10 -> Local BT Address
--------: 00 01 02 03 04 05 06 07 08 09
00000000: 7E 3F 00 41 10 1E 3F 72 02 00 
00000010: FF FF FF FF FF FF 01 00 7E FF 
00000020: 03 60 65 09 A0 FF FF FF FF FF 
00000030: FF 00 00 7D 5D 00 D0 8A D1 3A 
00000040: 00 00 00 00 00 00 02 80 00 02 
00000050: 00 00 00 00 00 00 00 00 00 00 
00000060: 05 E5 7E 
63 Bytes sent
getPacket(1)
Received 18 bytes
Received 5 bytes
--------: 00 01 02 03 04 05 06 07 08 09
00000000: 7E 17 00 69 FB 6C 08 25 80 00 
00000010: 00 00 00 00 00 00 01 00 7E FF 
00000020: 03 60 65 
cmd=1
PacketLength=23
<<<====== Content of pcktBuf =======>>>
--------: 00 01 02 03 04 05 06 07 08 09
00000000: 7E FF 03 60 65 
<<<=================================>>>
Invalid chk 0xFF00 - Found 0x6003
Tue Apr 15 19:45:22 2014: CRITICAL: Failed to initialize communication with inverter.__

This work item was migrated from CodePlex

CodePlex work item ID: '31'
Vote count: '1'

Hi there,
the old SMAspot website is dead, the new SBFspot one not public. Any chance sharing what's going on?
Cheers,
Andreas

around line 390: in SBFspot.cpp
for (int inv=0; Inverters[inv]!=NULL && inv<MAX_INVERTERS; inv++)
{
Inverters[inv]->calPdcTot = Inverters[inv]->Pdc1 + Inverters[inv]->Pdc1;

Should be
Inverters[inv]->calPdcTot = Inverters[inv]->Pdc1 + Inverters[inv]->Pdc2;

This work item was migrated from CodePlex

CodePlex work item ID: '40'
Vote count: '1'

Can you please enable to output configurable data fields to fields v7-v12. By configurable data I mean that I can decide which inverter data field will be moved to each v field.
Tx

This work item was migrated from CodePlex

CodePlex work item ID: '32'
Assigned to: 'SBF'
Vote count: '1'

Hi there,

I have an up to date Raspberry Pi, and attempted to build the current version, and hit the following issue:

xxxx@pi1 ~/build $ make
test -d bin/Debug || mkdir -p bin/Debug
test -d obj/Debug || mkdir -p obj/Debug
g++ -Wall -g -c Bluetooth.cpp -o obj/Debug/Bluetooth.o
g++ -Wall -g -c Ethernet.cpp -o obj/Debug/Ethernet.o
g++ -Wall -g -c TagDefs.cpp -o obj/Debug/TagDefs.o
In file included from SMAspot.h:44:0,
from TagDefs.cpp:34:

boost_ext.h:39:53: fatal error: boost/date_time/posix_time/posix_time.hpp: No such file or directory
compilation terminated.
make: *** [obj/Debug/TagDefs.o] Error 1

Are you aware of this one?

Ta

Dave

This work item was migrated from CodePlex

CodePlex work item ID: '33'
Vote count: '1'

Hi,

I get the error message above when executing SBFspot 3.3.1. Interestingly the first time I executed SBFspot there was no such issue:
https://pastebin.com/PnYZnTcb

From now on I get the current output:
https://pastebin.com/Z0UCZb0D

Here is another log with "-d5 -v5" options:
https://pastebin.com/X3kF8Wbb

So actually a timeout occurs when SBFspot tries to read the current plant time. This didn't happen on the first time starting SBFspot.

Can you help me? Thanks!

Hello,

I'm using SMAspot 2.4.1 on a raspberry pi.

I have a STP 12000TL-10 inverter, a SMA homemanager and three SMA bluetooth plug-in receiver (Funksteckdose)

If the homemanager is connected to the inverter via bt i can only use installer mode do connect. Then I get data from all three plugins, but the first one has strange values. The second and third one has always 0.0 values. It looks like, as if the plug-ins are treated as an inverter.
From the inverter i somtimes get data and somtimes not.

How can i remove the bluetooth plug-in from the list and get only data from the inverter? Do you have an idea? And how can i use the normal login instead of the installer login during a connection to the homemanager is active? If i should deliver more data dont hesitate to ask. ;-)

Here is the Output from SMAspot from tonight.
SMAspot V2.4.1
Yet another tool to read power production of SMA solar inverters
(c) 2012-2014, SBF (https://smaspot.codeplex.com)
Compiled for Linux 32 bit

Commandline Args: -v -finq -installer -password:Xxxxx
Reading config './SMAspot.cfg'
Wed Feb 19 21:43:44 2014: INFO: Starting...
sunrise: 07:20
sunset : 17:40
Connecting to 00:80:25:xx:xx:Xx (1/10)
Initializing...
SUSyID: 125 - SN: 886832786 (0x34DBFE92)
SMA netID=02
SUSyID: 128 - SN: xxxxxxxxxx
SUSyID: 191 - SN: xxxxxxxxxx
SUSyID: 191 - SN: xxxxxxxxxx
SUSyID: 191 - SN: xxxxxxxxxx
BT Signal=75%
Logon OK
Local Time: 19/02/2014 21:43:46
TZ offset (s): 3600 - DST: Off
SUSyID: 191 - SN: xxxxxxxxxx
Device Name: Computerschrank 463
Device Class: Verbraucher
Device Type: SMA Funksteckdose
Software Version: 12.12.108.R
Serial number: xxxxxxxxxx
SUSyID: 191 - SN: xxxxxxxxxx
Device Name: Büro 566
Device Class: Verbraucher
Device Type: SMA Funksteckdose
Software Version: 12.12.108.R
Serial number: xxxxxxxxxx
SUSyID: 191 - SN: xxxxxxxxxx
Device Name: Waschmaschine 890
Device Class: Verbraucher
Device Type: SMA Funksteckdose
Software Version: 12.12.108.R
Serial number: xxxxxxxxxx
SUSyID: 128 - SN: xxxxxxxxxx
Device Name: SN: xxxxxxxxxx
Device Class: Solar-Wechselrichter
Device Type: STP 12000TL-10
Software Version: 02.55.13.R
Serial number: xxxxxxxxxx
SUSyID: 191 - SN: xxxxxxxxxx
Device Status: Ok
SUSyID: 191 - SN: xxxxxxxxxx
Device Status: Ok
SUSyID: 191 - SN: xxxxxxxxxx
Device Status: Ok
SUSyID: 128 - SN: xxxxxxxxxx
Device Status: Ok
SUSyID: 191 - SN: xxxxxxxxxx
Device Temperature: 8423488.0°C
SUSyID: 191 - SN: xxxxxxxxxx
Device Temperature: 0.0°C
SUSyID: 191 - SN: xxxxxxxxxx
Device Temperature: 0.0°C
SUSyID: 128 - SN: xxxxxxxxxx
Device Temperature: 0.0°C
SUSyID: 191 - SN: xxxxxxxxxx
Pac max phase 1: 1299333462W
Pac max phase 2: 1715692655W
Pac max phase 3: 1096167015W
SUSyID: 191 - SN: xxxxxxxxxx
Pac max phase 1: 0W
Pac max phase 2: 0W
Pac max phase 3: 0W
SUSyID: 191 - SN: xxxxxxxxxx
Pac max phase 1: 0W
Pac max phase 2: 0W
Pac max phase 3: 0W
SUSyID: 128 - SN: xxxxxxxxxx
Pac max phase 1: 12000W
Pac max phase 2: 12000W
Pac max phase 3: 12000W
SUSyID: 191 - SN: xxxxxxxxxx
Energy Production:
EToday: 7020378737416761.000kWh
ETotal: 3760841250522883.000kWh
Operation Time: 12800.92h
Feed-In Time : 1623830055690497.50h

SUSyID: 191 - SN: xxxxxxxxxx
Energy Production:
EToday: 0.000kWh
ETotal: 0.000kWh
Operation Time: 12801.27h
Feed-In Time : 0.00h

SUSyID: 191 - SN: xxxxxxxxxx
Energy Production:
EToday: 0.000kWh
ETotal: 0.000kWh
Operation Time: 12794.29h
Feed-In Time : 0.00h

SUSyID: 128 - SN: xxxxxxxxxx
Energy Production:
EToday: 11.542kWh
ETotal: 21033.739kWh
Operation Time: 7448.15h
Feed-In Time : 7247.82h

SUSyID: 191 - SN: xxxxxxxxxx
DC Spot Data:
String 1 Pdc: 1835353.125kW - Udc: 8253074.00V - Idc: 1919252.125A
String 2 Pdc: 224685.656kW - Udc: 12287478.00V - Idc: 779249.000A

SUSyID: 191 - SN: xxxxxxxxxx
DC Spot Data:
String 1 Pdc: 0.000kW - Udc: 0.00V - Idc: 0.000A
String 2 Pdc: 0.000kW - Udc: 0.00V - Idc: 0.000A

SUSyID: 191 - SN: xxxxxxxxxx
DC Spot Data:
String 1 Pdc: 0.000kW - Udc: 0.00V - Idc: 0.000A
String 2 Pdc: 0.000kW - Udc: 0.00V - Idc: 0.000A

SUSyID: 128 - SN: xxxxxxxxxx
DC Spot Data:
String 1 Pdc: 0.000kW - Udc: 0.00V - Idc: 0.000A
String 2 Pdc: 0.000kW - Udc: 0.00V - Idc: 0.000A

SUSyID: 191 - SN: xxxxxxxxxx
AC Spot Data:
Phase 1 Pac : 1734755.250kW - Uac: 9623587.00V - Iac: 1684957.625A
Phase 2 Pac : 778333.500kW - Uac: 8084665.00V - Iac: 1936287.125A
Phase 3 Pac : 1316110.750kW - Uac: 11133384.00V - Iac: 1735292.250A
Total Pac : 1936606.125kW

SUSyID: 191 - SN: xxxxxxxxxx
AC Spot Data:
Phase 1 Pac : 0.000kW - Uac: 0.00V - Iac: 0.000A
Phase 2 Pac : 0.000kW - Uac: 0.00V - Iac: 0.000A
Phase 3 Pac : 0.000kW - Uac: 0.00V - Iac: 0.000A
Total Pac : 0.000kW

SUSyID: 191 - SN: xxxxxxxxxx
AC Spot Data:
Phase 1 Pac : 0.000kW - Uac: 0.00V - Iac: 0.000A
Phase 2 Pac : 0.000kW - Uac: 0.00V - Iac: 0.000A
Phase 3 Pac : 0.000kW - Uac: 0.00V - Iac: 0.000A
Total Pac : 0.000kW

SUSyID: 128 - SN: xxxxxxxxxx
AC Spot Data:
Phase 1 Pac : 0.000kW - Uac: 0.00V - Iac: 0.000A
Phase 2 Pac : 0.000kW - Uac: 0.00V - Iac: 0.000A
Phase 3 Pac : 0.000kW - Uac: 0.00V - Iac: 0.000A
Total Pac : 0.000kW

SUSyID: 191 - SN: xxxxxxxxxx
Grid Freq. : 18192434.00Hz
SUSyID: 191 - SN: xxxxxxxxxx
Grid Freq. : 0.00Hz
SUSyID: 191 - SN: xxxxxxxxxx
Grid Freq. : 0.00Hz
SUSyID: 128 - SN: xxxxxxxxxx
Grid Freq. : 0.00Hz

ArchiveDayData() *

startTime = 5303E5F0 -> 19/02/2014 00:00:00
ExportDayDataToCSV()

ArchiveMonthData() *

startTime = 52ECD3B0 -> 01/02/2014 12:00:00
ExportMonthDataToCSV()
There is no data to export!
Reading events: 2014-Feb-01
ExportEventsToCSV()
Wed Feb 19 21:43:54 2014: INFO: Done.
pi@piusb ~/fhem/sma241/bin/Release

Attachments

Archiv.zip
Archiv.zip

This work item was migrated from CodePlex

CodePlex work item ID: '16'
Vote count: '1'

Hi,

I just had a new SMA inverter installed yesterday that replaced three older units (the 17 year-old one had finally died). I wanted better logging than the new inverter supports and came across this software. Thanks so much, but it only grabs the data from the first two strings.

I've made the following changes, but seem to be missing something. And I should add that the last time I worked in C or C++ regularly was 1994, so I am a little rusty.

In SBFspot.cpp

Around line 425:
Was: "Inverters[inv]->calPdcTot = Inverters[inv]->Pdc1 + Inverters[inv]->Pdc2"
Is: "Inverters[inv]->calPdcTot = Inverters[inv]->Pdc1 + Inverters[inv]->Pdc2 + Inverters[inv]->Pdc3;"
Added extra printf line for the String 3 information (copied from String 2 and modified)

Around line 2600:
In "SpotDCPower" case
Was: "last = 0x00251EFF;"
Is: "last = 0x004524FE;"
In "SpotDCVoltage" case
Was: "last = 0x004521FF;"
Is: "last = 0x004524FE;"
I was just guessing that the data structures would be the same size and that seemed to work...

Around line 2900:
In "DcMsWatt" case:
Added a case for cls == 3
In "DcMsVol" case:
Added a case for cls == 3
In "DcMsAmp" case:
Added a case for cls == 3

I was just starting to work on the CSV and SQL sections, but feel like I am not following the flow of the code properly.

So, is there an easier way to go about this update? I am glad to dig in or open up the firewall so you can address my inverter directly to help with the debugging the code against the new model.

Thanks

Randy

Hi,
I am using smaspot for a couple of days now. Its working in combination with FHEM (a open source home automation tool) which calls smaspot every 10 minutes and stores the information in a local log file as well as generates some graphs with it.

It all runs smooth beside the fact that shortly before the end of the day (the production day for my solar "plant") there is suddenly a really high value for total_pac with something around 23000.

To me it looks like the last value before total_pac goes to 0 is always this high value. Its been happening for a few days now, so I thought I report it as a bug here.

Not sure if it helps but I have also attached the log file.

Best
Martin

Attachments

Solar-2014-03.log
solar.log
solar_at_1940.log
solarerror_morning.log
solarerror_evening.log

This work item was migrated from CodePlex

CodePlex work item ID: '24'
Vote count: '2'

Hi,

When running SMAspot in linux the resulting lines in the CSV files are not ended with CR/LF but with LF only like is custom with linux text files.

The header is indicating that the line endings are CR/LF but they are not. I don't see any flag in the config to force alternate line endings.

Cheers,

Wim

Attachments

2014-05-27_1153.png

This work item was migrated from CodePlex

CodePlex work item ID: '37'
Vote count: '1'

dear all, this is an item for the wishlist,
including a request for comment by:

the users that had problems that did raise the question for this option

candidate/users of this option

rational: in the past several issues have been raised by the users that were related to:

last day in a month missing in the monthly file
last records "minutes" missing in the daily file

last records missing in the events file (new in v240)

a simple workaround is that one should execute SMAspot with the options -am2 -ad2 -ae2
in stead of the default values (1),
the drawback, more interaction with the inverter, can be handled with two different cron or scheduler tasks

one that runs each 5minutes, options -am0 -ad0 -e0, which requests only for the SPOTvalues

one that is run less often, eg each hour, options -am2 -ad2 -ae2 -sp0, for other then SPOTvalues

as is explained in Google-issue G083 there is as well a benefit for a cumulative output,
resulting in the options:

wishitem-13-1 - for cumulative month results
-amcumul this gives a table with the end-of-day records of the last 40days,

wishitem-13-2 - for cumulative daily results
-adcumul this gives a table with the 5min-records of the last 48hours,

wishitem-10-1 - for cumulative events
-aecumul this gives a table with alle events during the last 48hours, (this wish is = w10-1)

in view of the expected usage of these options, the outputs from SMAspot (.csv and output-log) can bear a fixed name (eg via a parameter "outputpath-cumul"=path\filename)
if that parameter is not used then the default filenames apply

kr wim

This work item was migrated from CodePlex

CodePlex work item ID: '13'
Vote count: '1'

SMAspot will not produce a daily file for the DST (US) change over date. An (almost) empty file is created with the name: Squireoaksfarm-19691231.csv. Today 3/10/20014, the day after DST, SMAspot is running fine.
O.S.: Raspbian
Releases effected:
SMAspot V2.2.10
SMAspot V2.4.1

Execution: smaspot -d5 -v5 -am0 -ae0 -ad2 -cfg/home/ron/sq1/sq1.cfg > smaspot.out

Attached files:
SMAspot.out
sq1.cfg
Squireoaksfarm-19691231.csv

(I must be the only person in the US running SMAspot on a Raspberry PI :) )

Attachments

smaspot.out
Squireoaksfarm-19691231.csv
sq1.cfg
wsi7h111.analysis-DLS-ron.txt
iss17-4331.wim-Day4Mont2.std-2Aout.txt
iss17-4330.wim-Day4Mont2.std-2Aout.txt

This work item was migrated from CodePlex

CodePlex work item ID: '17'
Assigned to: 'SBF'
Vote count: '2'

It seems that the option for multi inverter support is not working.
Selecting MIS_Enabled = 0 still reports my both inverters
Version 244
Harry Verjans

This work item was migrated from CodePlex

CodePlex work item ID: '38'
Vote count: '2'

dear all, this is an item for the wishlist,
including a request for comment by:

the users that did raise the question for this option

candidate/user of this options

wishlist-10-1: provide cumulative archive of events
-rational: the present implementation extracts a single file with the last events (eg one month)
to obtain a continious file one needs to execute again-again a command -ae400
-proposal:
if the text 'cumul' is used as part of -aecumul then SMAspot extracts the events of the last 2 months
and merges them with the earlier created arch-events files
impact: this implies sorting the events (is now already done) and eleminate doubles

wishlist-10-2: provide archive-events in seperate files on month or year base

rational: for easy recup of information one might want that events of one month/year are written
to a file with month/year indicated or as a file into a directroy per year/month
the latter is similar to the file and directory naming options for month/daily files
see older demands on google-code

proposal:
implement the options %m %y also for archive events
if the option %d is encountered (either in the default or events settings) read this is 00

wishlist-10-3: provide extract of only last events (examples or since last extract or last nn)
-rational: for automated supervision/alarms of the plant
one can apply several methods read this as or/and combinations
or one extracts information from daily and spot values (if available)
or one investigates the events files

proposal:
if the text 'last' is used as part of the option -aelast
then SMAspot reads the events (choice: to-day | since-last-read )
since this is about instant decisions to be made after the run
the impact is that in the debug out, the read-of-events gets translated into text for the events
compare with the visualisation for month, daily, spot-values

wishlist-10-xx: up-to-you

This work item was migrated from CodePlex

CodePlex work item ID: '10'
Vote count: '1'

Output ./SMAspot is directed to a file using " >file" right after the command, error messages are directed to the same file using " 2>&1" after that. In that file I have:
....
PVOutput::getSystemData()
getSystemData() returned 23: Failed writing received data to disk/application
PVOutput::Export()
OK 200: Added Status

Before having " 2>&1" in the command line I got the message:
getSystemData() returned 23: Failed writing received data to disk/application
in the log of the cronjob.

This work item was migrated from CodePlex

CodePlex work item ID: '42'
Vote count: '1'