Logon problem Sunny Island

SBFspot commented 6 years ago

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

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'

SBFspot commented 6 years ago

[SBF@3/02/2014] Can you send us a full debug log? smaspot -d5 -v5

thanks

SBFspot commented 6 years ago

[dezi3@7/02/2014] Of course...

Commandline Args: -finq -d5 -v5 Fri Feb 07 16:54:00 2014: INFO: Starting... sunrise: 08:10 sunset : 17:43 Connecting to Local Network... Initialising Winsock... Initializing... SUSyID: 125 - SN: 944963338 (0x3852FF0A) --------: 00 01 02 03 04 05 06 07 08 09 00000000: 53 4D 41 00 00 04 02 A0 FF FF 00000010: FF FF 00 00 00 20 00 00 00 00 20 Bytes sent to IP [239.12.255.254] MAX_CommBuf is now 60 bytes Received 60 bytes from IP [192.168.0.45] --------: 00 01 02 03 04 05 06 07 08 09 00000000: 53 4D 41 00 00 04 02 A0 00 00 00000010: 00 01 00 02 00 00 00 01 00 04 00000020: 00 10 00 01 00 01 00 04 00 20 00000030: 00 00 00 01 00 04 00 30 C0 A8 00000040: 00 2D 00 04 00 40 00 00 00 01 00000050: 00 02 00 70 EF 0C 00 00 00 00 Inverter IP address: 192.168.0.45 found via broadcastidentification --------: 00 01 02 03 04 05 06 07 08 09 00000000: 53 4D 41 00 00 04 02 A0 00 00 00000010: 00 01 00 26 00 10 60 65 09 A0 00000020: FF FF FF FF FF FF 00 00 7D 00 00000030: 0A FF 52 38 00 00 00 00 00 00 00000040: 01 80 00 02 00 00 00 00 00 00 00000050: 00 00 00 00 00 00 00 00 58 Bytes sent to IP [192.168.0.45] ethGetPacket() MAX_CommBuf is now 98 bytes Received 98 bytes from IP [192.168.0.45] --------: 00 01 02 03 04 05 06 07 08 09 00000000: 53 4D 41 00 00 04 02 A0 00 00 00000010: 00 01 00 4E 00 10 60 65 13 90 00000020: 7D 00 0A FF 52 38 00 A0 21 01 00000030: D3 5F 29 4B 00 00 00 00 00 00 00000040: 01 80 01 02 00 00 00 00 00 00 00000050: 00 00 00 00 00 03 00 00 00 FF 00000060: 00 00 00 00 00 00 01 00 21 01 00000070: D3 5F 29 4B 00 00 0A 00 0A 00 00000080: 00 00 00 00 00 00 05 00 00 00 00000090: 01 01 00 00 00 00 00 00 <<<====== Content of pcktBuf =======>>> --------: 00 01 02 03 04 05 06 07 08 09 00000000: 00 00 10 60 65 13 90 7D 00 0A 00000010: FF 52 38 00 A0 21 01 D3 5F 29 00000020: 4B 00 00 00 00 00 00 01 80 01 00000030: 02 00 00 00 00 00 00 00 00 00 00000040: 00 00 03 00 00 00 FF 00 00 00 00000050: 00 00 00 01 00 21 01 D3 5F 29 00000060: 4B 00 00 0A 00 0A 00 00 00 00 00000070: 00 00 00 05 00 00 00 01 01 00 00000080: 00 00 00 00 <<<=================================>>> logoffSMAInverter() --------: 00 01 02 03 04 05 06 07 08 09 00000000: 53 4D 41 00 00 04 02 A0 00 00 00000010: 00 01 00 22 00 10 60 65 08 A0 00000020: FF FF FF FF FF FF 00 03 7D 00 00000030: 0A FF 52 38 00 03 00 00 00 00 00000040: 02 80 0E 01 FD FF FF FF FF FF 00000050: 00 00 00 00 54 Bytes sent to IP [192.168.0.45] logonSMAInverter() --------: 00 01 02 03 04 05 06 07 08 09 00000000: 53 4D 41 00 00 04 02 A0 00 00 00000010: 00 01 00 3A 00 10 60 65 0E A0 00000020: FF FF FF FF FF FF 00 01 7D 00 00000030: 0A FF 52 38 00 01 00 00 00 00 00000040: 03 80 0C 04 FD FF 07 00 00 00 00000050: 84 03 00 00 98 01 F5 52 00 00 00000060: 00 00 B8 B8 B8 B8 88 88 88 88 00000070: 88 88 88 88 00 00 00 00 78 Bytes sent to IP [192.168.0.45] ethGetPacket() Received 66 bytes from IP [192.168.0.45] --------: 00 01 02 03 04 05 06 07 08 09 00000000: 53 4D 41 00 00 04 02 A0 00 00 00000010: 00 01 00 2E 00 10 60 65 0B 90 00000020: 7D 00 0A FF 52 38 00 01 21 01 00000030: D3 5F 29 4B 00 01 10 00 00 00 00000040: 03 80 0D 04 FD FF 07 00 00 00 00000050: 84 03 00 00 98 01 F5 52 00 00 00000060: 00 00 00 00 00 00 <<<====== Content of pcktBuf =======>>> --------: 00 01 02 03 04 05 06 07 08 09 00000000: 00 00 10 60 65 0B 90 7D 00 0A 00000010: FF 52 38 00 01 21 01 D3 5F 29 00000020: 4B 00 01 10 00 00 00 03 80 0D 00000030: 04 FD FF 07 00 00 00 84 03 00 00000040: 00 98 01 F5 52 00 00 00 00 00 00000050: 00 00 <<<=================================>>> Fri Feb 07 16:54:00 2014: CRITICAL: Logon failed. Check 'USER' Password

SBFspot commented 6 years ago

[SillieWimons@8/02/2014] hello dezi,

from your description, there are two distinct points, -1- what triggers the logon failure, ??? from your obesrvation - do you have an extimate whether failure appaears with a ??fixed?? interval and if so what that interval might be

-2- what is the reset reason / tempo to get to normal operation, ??? can you inform whether the retun to normal operation is after about 15minutes (900seconds)

let me be honnest - from the actual information i have not yet found an indication for a cause ??? can you inform what material is part of your set-up -> there is: -- an inverter "Sunny Island 6.0H" (combined with ???) -- i expect a RPi or system that runs SMAspot (unix <-> windows - battery support) -- i expect a router/hub to be on the the speedwire bus (router / . . . ) note - if the ip addresses get disturbed/reset during comm's phase, this will influence -- what other systems are involved

- - - - to allow further investigation

-1- to identify the trigger and the conditions - it is needed to capture the historic of the runs, ??? is it possible for you to implement a method to capture the set of 4 debug logs that are related to the transition: correct operation -> logon failed to explain what i mean - i identify the debug logs in reverse order -d- the second one after "Logon failed" -c- the first one that is confronted with the "Logon failed" -b- the successfull one that preceded the "Logon failed" -a- the last but successfull that precede the "Logon failed"

nb: the one that you have included in your previous answer was a good start one that debug-log that you capture during correct operation - will also be usefull -- for the cause analysis we need references to check for the delta's in the operation

note that I'm not aware of your system, neither skills to install this, read the below as a description:

 how should i do this   (the cron will call a script in stead of direct calling SMAspot)
 the script must contain the following (the example indicates the method and not the exact syntax)

 echo SMAspot started at: %date - %time 1>>log-execution.txt
 smaspot.exe -d5 -v5  1>nameoffile.std-out.txt 2>nameoffile.std-er.txt
 /* push down the history
 delete nameoffile.std-out.ex-4txt
 delete nameoffile.std-er.ex-4txt
 rename nameoffile.std-out.ex-3.txt nameoffile.std-out.ex-4txt    (or move or copy&delete)
 rename nameoffile.std-er.ex-3.txt nameoffile.std-er.ex-4txt 
 rename nameoffile.std-out.ex-2.txt nameoffile.std-out.ex-3txt 
 rename nameoffile.std-er.ex-2.txt nameoffile.std-er.ex-3txt 
 rename nameoffile.std-out.ex-1.txt nameoffile.std-out.ex-2txt 
 rename nameoffile.std-er.ex-1.txt nameoffile.std-er.ex-2txt 
 /* write last log to the push-down series
 rename nameoffile.std-out.txt nameoffile.std-out.ex-1txt 
 rename nameoffile.std-er.txt nameoffile.std-er.ex-1txt 
 /* control info to save    (and control as well the return to normal operation)
 if find "Logon failed" in "nameoffile.std-out.ex-2txt" eq false
 then
      if find "Logon failed" in "nameoffile.std-out.ex-3txt" eq true
      then
          echo logon fail ended at: %date - %time 1>>log-execution.txt
      /*
      else       /* nothing to do
      /*
 else           /* then there is  a logon failure in log -2
      if find "Logon failed" in "nameoffile.std-out.ex-3txt" eq false
      then              
          echo logon fail started two runs earlier then: %date - %time 1>>log-execution.txt
          /* delete older logs 
          delete SMAspot.v2211\issueC07.dir\nameoffile.std-*
          /* save logs
          copy nameoffile.std-* to SMAspot.v2211\issueC07.dir\
      else 
           /* nothing to do
/*

-2- it is needed to identify the conditions that end the lock-up and the reason in first instance one can expect a time-out (eg 900seconds = 15minutes) the above given pseudo-script includes a detection of the return in normal operation

          note that:
               in the above pseudo script  one can easy insert a way to capture the debug-logs at reset

SBFspot commented 6 years ago

[SillieWimons@8/02/2014] dear dezi3 - can you provide a copy of the SMAspot.cfg file that you are actually using

kr wim

SBFspot commented 6 years ago

[berndh1@11/03/2014] I have the same problem with login after a Time.

SMASpot works out of tthe Box. Windows, running in Konsole, every Minute. But sometimes it lose the Connection to the Inverter. "Inverter IP address: 192.168.6.12 from SMAspot.cfg Tue Mar 11 09:42:30 2014: CRITICAL: Logon failed. Check 'USER' Password"

I have do disconect the Island and SunnyHomeManger from the Network, after some Minutes it start working again. Ip-Adresse ist fixed in the Fritzbox, an Island is answering if i Ping him.

My debug Log

C:\SMA>smaspot -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'
Tue Mar 11 09:49:29 2014: INFO: Starting...
sunrise: 06:55
sunset : 18:27
Connecting to Local Network...
Initialising Winsock...
Initializing...
SUSyID: 125 - SN: XXXXXXXX (XXXXXXXXX)
Inverter IP address: 192.168.6.12 from SMAspot.cfg
--------: 00 01 02 03 04 05 06 07 08 09
00000000: 53 4D 41 00 00 04 02 A0 00 00
00000010: 00 01 00 26 00 10 60 65 09 A0
00000020: FF FF FF FF FF FF 00 00 7D 00
00000030: 8F 9D AE 37 00 00 00 00 00 00
00000040: 01 80 00 02 00 00 00 00 00 00
00000050: 00 00 00 00 00 00 00 00
58 Bytes sent to IP [192.168.6.12]
ethGetPacket()
MAX_CommBuf is now 98 bytes
Received 98 bytes from IP [192.168.6.12]
--------: 00 01 02 03 04 05 06 07 08 09
00000000: 53 4D 41 00 00 04 02 A0 00 00
00000010: 00 01 00 4E 00 10 60 65 13 90
00000020: 7D 00 8F 9D AE 37 00 A0 21 01
00000030: 3F 62 29 4B 00 00 00 00 00 00
00000040: 01 80 01 02 00 00 00 00 00 00
00000050: 00 00 00 00 00 03 00 00 00 FF
00000060: 00 00 00 00 00 00 01 00 21 01
00000070: 3F 62 29 4B 00 00 0A 00 0A 00
00000080: 00 00 00 00 00 00 05 00 00 00
00000090: 01 01 00 00 00 00 00 00
<<<====== Content of pcktBuf =======>>>
--------: 00 01 02 03 04 05 06 07 08 09
00000000: 00 00 10 60 65 13 90 7D 00 8F
00000010: 9D AE 37 00 A0 21 01 3F 62 29
00000020: 4B 00 00 00 00 00 00 01 80 01
00000030: 02 00 00 00 00 00 00 00 00 00
00000040: 00 00 03 00 00 00 FF 00 00 00
00000050: 00 00 00 01 00 21 01 3F 62 29
00000060: 4B 00 00 0A 00 0A 00 00 00 00
00000070: 00 00 00 05 00 00 00 01 01 00
00000080: 00 00 00 00
<<<=================================>>>
logoffSMAInverter()
--------: 00 01 02 03 04 05 06 07 08 09
00000000: 53 4D 41 00 00 04 02 A0 00 00
00000010: 00 01 00 22 00 10 60 65 08 A0
00000020: FF FF FF FF FF FF 00 03 7D 00
00000030: 8F 9D AE 37 00 03 00 00 00 00
00000040: 02 80 0E 01 FD FF FF FF FF FF
00000050: 00 00 00 00
54 Bytes sent to IP [192.168.6.12]
logonSMAInverter()
--------: 00 01 02 03 04 05 06 07 08 09
00000000: 53 4D 41 00 00 04 02 A0 00 00
00000010: 00 01 00 3A 00 10 60 65 0E A0
00000020: FF FF FF FF FF FF 00 01 7D 00
00000030: 8F 9D AE 37 00 01 00 00 00 00
00000040: 03 80 0C 04 FD FF 07 00 00 00
00000050: 84 03 00 00 1A CE 1E 53 00 00
00000060: 00 00 B8 B8 B8 B8 88 88 88 88
00000070: 88 88 88 88 00 00 00 00
78 Bytes sent to IP [192.168.6.12]
ethGetPacket()
Received 66 bytes from IP [192.168.6.12]
--------: 00 01 02 03 04 05 06 07 08 09
00000000: 53 4D 41 00 00 04 02 A0 00 00
00000010: 00 01 00 2E 00 10 60 65 0B 90
00000020: 7D 00 8F 9D AE 37 00 01 21 01
00000030: 3F 62 29 4B 00 01 10 00 00 00
00000040: 03 80 0D 04 FD FF 07 00 00 00
00000050: 84 03 00 00 1A CE 1E 53 00 00
00000060: 00 00 00 00 00 00
<<<====== Content of pcktBuf =======>>>
--------: 00 01 02 03 04 05 06 07 08 09
00000000: 00 00 10 60 65 0B 90 7D 00 8F
00000010: 9D AE 37 00 01 21 01 3F 62 29
00000020: 4B 00 01 10 00 00 00 03 80 0D
00000030: 04 FD FF 07 00 00 00 84 03 00
00000040: 00 1A CE 1E 53 00 00 00 00 00
00000050: 00 00
<<<=================================>>>
Tue Mar 11 09:49:30 2014: CRITICAL: Logon failed. Check 'USER' Password

SBFspot commented 6 years ago

[berndh1@11/03/2014] And my SMAspot.cfg

# SMA Inverter's Bluetooth address
# Windows: smaspot -scan
# Linux  : hcitool scan
# IMPORTANT FOR SPEEDWIRE USERS: COMMENT OUT BTADDRESS (PUT # IN FRONT)
#BTAddress=00:00:00:00:00:00

# SMA Inverter's Speedwire IP address
# If IP_Address is not set or is 0.0.0.0 SMAspot will try to detect the speedwire inverter by broadcast
# If IP_Address is set to a valid IP, SMAspot will try to connect directly to that IP without broadcast detection
IP_Address=192.168.6.12

# User password (default 0000)
Password=0000

# MIS_Enabled (Multi Inverter Support: Default=0 Disabled)
# +------------+-------+-------------+
# | #Inverters | NetID | MIS_Enabled |
# +------------+-------+-------------+
# |      1     |   1   | Don't Care  |
# +------------+-------+-------------+
# |      1     |   >1  |      0      |
# +------------+-------+-------------+
# |      >1    |   >1  |      1      |
# +------------+-------+-------------+
MIS_Enabled=0

# Plantname
Plantname=Ahornweg

# OutputPath (Place to store CSV files)
# 
# Windows: C:\TEMP\SMA\%Y
# Linux  : /home/sbf/Documents/sma/%Y
# %Y %m and %d will be expanded to Year Month and Day
OutputPath=C:\TEMP\SMA

# OutputPathEvents (Place to store CSV files for events)
# If omitted, OutputPath is used
OutputPathEvents=C:\TEMP\SMA\Events

# Position of pv-plant http://itouchmap.com/latlong.html
# Example for Ukkel, Belgium
Latitude=51.44
Longitude=7.23

# Calculate Missing SpotValues
# If set to 1, values not provided by inverter will be calculated
# eg: Pdc1 = Idc1 * Udc1
CalculateMissingSpotValues=1

# DateTimeFormat (default %d/%m/%Y %H:%M:%S)
# For details see strftime() function
# http://www.cplusplus.com/reference/clibrary/ctime/strftime/
DateTimeFormat=%d/%m/%Y %H:%M:%S

# DateFormat (default %d/%m/%Y)
DateFormat=%d/%m/%Y

# DecimalPoint (comma/point default comma)
DecimalPoint=comma

# TimeFormat (default %H:%M:%S)
TimeFormat=%H:%M:%S

# SynchTime (default 1 = On)
# If set to 1 the Inverter time is synchronised with pc time
# Some inverters don't have a real-time clock
SynchTime=1

# SunRSOffset
# Offset to start before sunrise and end after sunset (0-3600 - default 900 seconds)
SunRSOffset=900

# Locale
# Translate Entries in CSV files
# Surpported locales: de-DE;en-US;fr-FR;nl-NL;es-ES;it-IT
# Default en-US
Locale=de-DE

# Timezone
# Select the right timezone in date_time_zonespec.csv
# e.g. Timezone=Europe/Brussels
Timezone=Europe/Brussels

###########################
### CSV Export Settings ###
###########################
# With CSV_* settings you can define the CSV file format

# CSV_Export (default 1 = Enabled)
# Enables or disables the CSV Export functionality
CSV_Export=0

# CSV_ExtendedHeader (default 1 = On)
# Enables or disables the SMA extended header info (8 lines)
# isep=;
# Version CSV1|Tool SMAspot|Linebreaks CR/LF|Delimiter semicolon|Decimalpoint comma|Precision 3
# etc...
# This is usefull for manual data upload to pvoutput.org
CSV_ExtendedHeader=1

# CSV_Header (default 1 = On)
# Enables or disables the CSV data header info (1 line)
# dd/MM/yyyy HH:mm:ss;kWh;kW
# This is usefull for manual data upload to pvoutput.org
# If CSV_ExtendedHeader is enabled, CSV_Header is also enabled
CSV_Header=1

# CSV_SaveZeroPower (default 1 = On)
# When enabled, daily csv files contain all data from 00:00 to 23:55
# This is usefull for manual data upload to pvoutput.org
CSV_SaveZeroPower=1

# CSV_Delimiter (comma/semicolon default semicolon)
CSV_Delimiter=semicolon

# CSV_Spot_TimeSource (Inverter|Computer default Inverter)
CSV_Spot_TimeSource=Inverter

# CSV_Spot_WebboxHeader (Default 0 = Off)
# When enabled, use Webbox style header (DcMs.Watt[A];DcMs.Watt[B]...)
CSV_Spot_WebboxHeader=0

#################################
### Online Monitoring Systems ###
#################################
#
# In the future, multiple online monitoring systems can be defined
# Here we can activate the ones we like
#
################################
### PVoutput Upload Settings ###
################################
# PVoutput (default 0 = Disabled)
# Enables or disables the upload functionality to pvoutput.org
# When enabled, be sure to use -u switch on the command line
PVoutput=0

#PVoutput_SID
#Sets PVoutput System ID
PVoutput_SID=

#PVoutput_Key
#Sets PVoutput API Key
PVoutput_Key=

# VoltageLogging sets AC or DC logging.
# Possible values are:
# NONE (disabled)
# MAX(AC) (default)
# AC(PH1) or AC(PH2) or AC(PH3)
# MAX(DC) or DC(ST1) or DC(ST2)
VoltLogging=MAX(AC)

# InverterTemp (default 0 = disabled)
# Enables or disables the upload of the inverter's temperature
InverterTemp=0

# InverterTempMapTo (default v5 = Use standard PVoutput Temperature Graph)
# In Donation Mode only, map inverter's temperature to extended data field (v7..v12)
# For more info, see http://pvoutput.org/help.html#donations 
InverterTempMapTo=v5

# CumulativeEnergy (default 0 = Today's Energy)
# Set the cumulative flag = 1 when you wish to pass lifetime energy or 0 for today's energy
# WARNING!!! DO NOT CHANGE THIS FLAG DURING DAYLIGHT AS THIS WILL MESS UP YOUR PVOUTPUT GRAPHS
CumulativeEnergy=0

SBFspot commented 6 years ago

[berndh1@11/03/2014] Mnh, after 3H20Min its running normal. Not at home, so i havent do something. Strange

SBFspot commented 6 years ago

[SBF@11/03/2014] I tried to analyse the logfiles and it seems the inverter returns an unexpected code in response to the logon request (well, at least unexpected for SMAspot)

0x0000 = OK
0x0100 = Wrong password
0x0010 = ???

As a test, I suggest to do a small modification in the logonSMAInverter() function in SMAspot.cpp file

Change this:

rc = (pckt->ErrorCode == 0) ? E_OK : E_INVPASSW;

to:

rc = (pckt->ErrorCode == 0x0100) ? E_INVPASSW : E_OK;

SBFspot commented 6 years ago

[berndh1@12/03/2014] I just use the Ready for use Win Exe. Can you do this for me?

SBFspot commented 6 years ago

[SBF@12/03/2014] Here it is: V2.4.2 for Windows with the proposed change

SBFspot commented 6 years ago

[SBF@14/03/2014] Note: The attachment for 2.4.2 can be found in the first item of this thread... stupid codeplex... or should I say stupid complex ;-) SBF

SBFspot commented 6 years ago

[berndh1@14/03/2014] Thanks!!!!

SBFspot commented 6 years ago

[berndh1@17/03/2014] Login works but the Output is corrupted. Switch back to V2.4.1, and change the interval to 5 Min. seems that works a bit better.

By the way, is it possible to get the In/Out Ah to calculate the Time to the next Fullcharge or Equalizezyklus?

Bernd

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 Windows 32 bit

Commandline Args: -v -finq
Reading config 'C:\SMA\SMAspot.cfg'
Fri Mar 14 18:17:36 2014: INFO: Starting...
sunrise: 06:48
sunset : 18:32
Connecting to Local Network...
Initializing...
SUSyID: 125 - SN: xxxxxxxxxxxxxxxxxxxxxx
Inverter IP address: 192.168.6.12 from SMAspot.cfg
Logon OK
SetInverterTime() not executed! We're still testing...
SUSyID: 289 - SN: xxxxxxxxxxxxxxx
Device Name:      x;
Device Class:     
Device Type:      
Software Version: 
Serial number:    1261003327
SUSyID: 289 - SN: 1261003327
Device Status:      ?
SUSyID: 289 - SN: 1261003327
Device Temperature: 0.0øC
SUSyID: 289 - SN: 1261003327
Pac max phase 1: 0W
Pac max phase 2: 0W
Pac max phase 3: 0W
SUSyID: 289 - SN: 1261003327
Energy Production:
    EToday: 0.000kWh
    ETotal: 0.000kWh
    Operation Time: 0.00h
    Feed-In Time  : 0.00h
SUSyID: 289 - SN: 1261003327
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: 289 - SN: 1261003327
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: 289 - SN: 1261003327
Grid Freq. : 0.00Hz
********************
* ArchiveDayData() *
********************
startTime = 53223870 -> 14/03/2014 00:00:00
**********************
* ArchiveMonthData() *
**********************
startTime = 5311BDB0 -> 01/03/2014 12:00:00
Reading events: 2014-Mar-01
Fri Mar 14 18:17:36 2014: INFO: Done.

SBFspot commented 6 years ago

[SBF@17/03/2014] One of the items on the wishlist is to have an option for "looped mode". By leaving the connection open it is possible to have shorter delays between readouts.

For In/Out Ah... if SE can read it, SMAspot can read it too You can send me a screenshot of SE showing the values you want. I'll see what I can do - and in what timeframe, as I'm working on version 3 now

SBFspot commented 6 years ago

[berndh1@18/03/2014] Ok, here it is. I need the Part under "Diagnose" The Calc for Fullcharge is the "Abgegebene Ladungsmenge / Batteriekapazität.

Thanks a lot!

SBFspot / SBFspot

Logon problem Sunny Island #12

Attachments

This work item was migrated from CodePlex