SMA - inverter reading out at 00:00

Topics: 1. General
Dec 10, 2015 at 5:34 PM
First of all the tool is working very well in combination with the RasPi.
To read the data I use: /usr/local/bin/sbfspot.3/SBFspot -ad2 -fing
But I have a problem if I want to read the inverter between 00:00 and 09:30. Then I get only the datas of the current day. Regarding to the manual it is correct.
Is there any idea?
Coordinator
Dec 10, 2015 at 8:49 PM
Check date/time of your inverter (use -v5 or SunnyExplorer)
Dec 11, 2015 at 1:12 PM
Edited Dec 11, 2015 at 10:29 PM
hej heilu, please provide following information for the analysis of this problem:

-a- execute sbfspot with the options
sbfspot -d5 -v5 -finq -ad3 -am2 1>heilu-out-log.txt 2>heilu-err-log.txt

the options "-d5 -v5" result in a detailed output by sbfspot
the options "-ad3" and "-am2" are usefull for your case
the options "1>heilu-out-log.txt" and "2>heilu-err-log.txt" will write results to text files
note: the directory where xxx.txt files will be written depends on your OperSyst

you can send the files - via private mail
or you open a new issue and attach the file

kr
Dec 12, 2015 at 6:54 PM
Hej WillieSimons,

thanks for your answer. I have done your suggestion, the err-log-file is empty (so no error?) the log-file has realy a lot of informations.
Regarding, I am new on this forum, where or how can I attache a mail?

LR
Dec 13, 2015 at 12:34 PM
Edited Dec 13, 2015 at 3:47 PM
hej, lr

the discussion part on the "sbfspot" forum does not allow to attach files
i did send a private message to you with my email address,
  • to send a private message click on the name: eg "williesimons" in the first column
  • that opens a window with some information and a button "contact", click the contact button
  • the "contact" button can be used to initiate a private message, (but still without files)
    note: "codeplex" will send a private message AND will deliver your email adress" to the other party
note: if all worked correct you will have received a "private mesaage" from me (using this method)

krwim
Dec 16, 2015 at 5:08 PM
dear heilu, i did receive your data file

but grgrgr issue not visible

this execution was done at 19h41 so the problem that you did refer is not shown
??? be aware that - - for the analysis it is also important to obtain the conditions that trigger the effect

please - can you provide an output file but then at an early morning run,
  • reading your first input
    -> i expect that you need to execute SBFspot before 08h00 (sunrise at your position) to (re)produce the problem
before you send the log of the execution can you control that your problem did occur on that day
it might be that you need more then one trial to catch the info
  • please keep us informed about the condtions that the problem is WELL / NOT appearing
kind reg. wim
Dec 16, 2015 at 5:44 PM
Dear Wim,

I will try to make the file tomorrow morning.

Kind regards
Lutz
Coordinator
Dec 23, 2015 at 10:51 PM
Did you check the inverter time? This is important to know.
Dec 24, 2015 at 8:27 AM
Yes I did., it's the same as the computer time and the same as the local time.

Have a nice X-MAS!
Dec 24, 2015 at 4:14 PM
dear heilu alias lutz most important have a nice X-mas and enjoy the new year

after analysis of your file it is clear that we need further assistance from you

reason: when a program is executed with the instruction to send the "output" to a file
then the OperatingSystem's (no matter whether Linux or Windows) uses a two-step approach
-a- output is continue written to a temporary location in memory
-b- from memory that text info is written block/block to the output file

for some type of failures,
  • eg "program-hangs", "endless-loop", "function-does-not-reply", . . .
then the last part of the program execution, is not transferrer to the output file

there are two ways to overcome this:

-1- the more simple method to catch that last part of the execution is

you run the program from a "command-window" (as you have been doing before)
you apply the same commandstring as before but exclude the redirect to file (theoption "1>yourfilename" )
on screen you will see the complete log of the execution including that last part w're searching for

after execution stopped,
you can extract - select - copy - paste to a file be aware i expect that we need the last 40lines of the information

;-) since i'don't know your setup - you have to find yourself how this is to be done

one can extract the last output from "screen" (read the window)

the drawback is that for large outputs on "screen", only the last nnn lines can be recuperated

-2- the complex method is: redirect the output AND to a file AND to screen
the instruction to obtain this depends on the operating system

kind regards wim
Dec 26, 2015 at 3:03 PM
Hi, Wim,

I hope you had a nice X-mas. (We in Germany have a second day-off, so we have really a long weekend!
That's the reson why I will do the first method in the begining of next week.

By the way, many thanks for the analyse.

Kind regards Lutz
Dec 26, 2015 at 11:27 PM
dear lutz,

after a review/compare of your information from 12dec <-towards-> your information from 21dec,
i found it to be helpfull if you can provide some extra information

rational: to evaluate the output from the failing execution
it is handy to compare that output with the output of a correct execution of the same day

can you please:
-a- aside of the test as i did ask you (capture info from screen for the failing execution -- early morning)

-b- execute, after 09h30, the program with the options "sbfspot -d5 -v5 -ad3 -am2 -finq 1>heilu-decxx-out.txt 2>heilu-decxx-err.txt"

by comparing these two outputs side<->side will be easier to concentrate on the problem

thanks for this additional work - kind regards wim