Hello,
My inverter is a SMA SB 4000-TL20 (running since 2009 in Germany).
I am working with SBFspot 3.3.2.
Since a few month is discovered, I always get error when reading inverter data....
```
### End of Config ###
Mon Jun 5 12:50:01 2017: INFO: Starting...
sunrise: 05:18
sunset : 21:16
Connecting to 00:80:25:0A:1A:C5 (1/15)
Initializing...
SUSyID: 125 - SessionID: 866472527 (0x33A5524F)
SMA netID=01
Serial Nr: 7D2D036C (2100101996)
BT Signal=68.2%
Logon OK
Failed to get current plant time (0)
getInverterData(sbftest) returned an error: -1
getSoftwareVersion returned an error: -1
SUSyID: 78 - SN: 2100101996
Device Name: SN: 2100101996
Device Class: Solar Inverters
Device Type: SB 4000TL-20
Software Version:
Serial number: 2100101996
SUSyID: 78 - SN: 2100101996
Device Status: Ok
SUSyID: 78 - SN: 2100101996
Device Temperature: 36.9°C
SUSyID: 78 - SN: 2100101996
GridRelay Status: Closed
SUSyID: 78 - SN: 2100101996
```
Rest works.
Login in via SMA Sunny Explorer Windows-Software, Time can be read/changed... Software version is displayed..... ?1?
If this was always the case I can't say; I looked closer onto log-data when discvovering "123solar".
From old "SMASpot" I don't have any log-files remaining.
Any ideas?
Comments: Hello, Okay, with ``` SynchTime=0 ``` there is no more error message shown with "-v5" option: ``` Initializing... SUSyID: 125 - SessionID: 832815836 (0x31A3C2DC) SMA netID=01 Serial Nr: 7D2D036C (2100101996) BT Signal=72.2% Logon OK SUSyID: 78 - SN: 2100101996 Device Name: SN: 2100101996 Device Class: Solar Inverters Device Type: SB 4000TL-20 Software Version: 02.07.00.R Serial number: 2100101996 SUSyID: 78 - SN: 2100101996 Device Status: Ok SUSyID: 78 - SN: 2100101996 Device Temperature: 34.1°C SUSyID: 78 - SN: 2100101996 GridRelay Status: Open SUSyID: 78 - SN: 2100101996 ``` With "-v5 -d5" I find TimeOut: ``` Logon OK getInverterData(-2147483648) --------: 00 01 02 03 04 05 06 07 08 09 00000000: 7E 3F 00 41 CD 72 31 83 15 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 90 89 18 33 00000040: 00 00 00 00 00 00 05 80 00 02 00000050: 02 64 00 8C 61 00 FF 8F 61 00 00000060: B6 03 7E 63 Bytes sent getPacket(1) Timeout reading socket No data! getInverterData(sbftest) returned an error: -1 getInverterData(2048) ``` and afterwards several.... ``` cmd=1 PacketLength=85 <<<====== Content of pcktBuf =======>>> --------: 00 01 02 03 04 05 06 07 08 09 00000000: 7E FF 03 60 65 0E 50 7D 00 90 00000010: 89 18 33 00 01 4E 00 6C 03 2D 00000020: 7D 00 01 00 00 00 00 04 80 0D 00000030: 04 FD FF 07 00 00 00 84 03 00 00000040: 00 8B 7E 45 59 00 00 00 00 B8 00000050: B8 B8 B8 88 88 88 88 88 88 88 00000060: 88 5F 83 7E <<<=================================>>> Packet ID mismatch. Expected 6, received 4 getPacket(1) Received 18 bytes Received 67 bytes ``` All in the logfile.... [sbfoutput.20170617-2124.txt](neumi.selfhost.bz/sbfoutput.20170617-2124.txt)
My inverter is a SMA SB 4000-TL20 (running since 2009 in Germany).
I am working with SBFspot 3.3.2.
Since a few month is discovered, I always get error when reading inverter data....
```
### End of Config ###
Mon Jun 5 12:50:01 2017: INFO: Starting...
sunrise: 05:18
sunset : 21:16
Connecting to 00:80:25:0A:1A:C5 (1/15)
Initializing...
SUSyID: 125 - SessionID: 866472527 (0x33A5524F)
SMA netID=01
Serial Nr: 7D2D036C (2100101996)
BT Signal=68.2%
Logon OK
Failed to get current plant time (0)
getInverterData(sbftest) returned an error: -1
getSoftwareVersion returned an error: -1
SUSyID: 78 - SN: 2100101996
Device Name: SN: 2100101996
Device Class: Solar Inverters
Device Type: SB 4000TL-20
Software Version:
Serial number: 2100101996
SUSyID: 78 - SN: 2100101996
Device Status: Ok
SUSyID: 78 - SN: 2100101996
Device Temperature: 36.9°C
SUSyID: 78 - SN: 2100101996
GridRelay Status: Closed
SUSyID: 78 - SN: 2100101996
```
Rest works.
Login in via SMA Sunny Explorer Windows-Software, Time can be read/changed... Software version is displayed..... ?1?
If this was always the case I can't say; I looked closer onto log-data when discvovering "123solar".
From old "SMASpot" I don't have any log-files remaining.
Any ideas?
Comments: Hello, Okay, with ``` SynchTime=0 ``` there is no more error message shown with "-v5" option: ``` Initializing... SUSyID: 125 - SessionID: 832815836 (0x31A3C2DC) SMA netID=01 Serial Nr: 7D2D036C (2100101996) BT Signal=72.2% Logon OK SUSyID: 78 - SN: 2100101996 Device Name: SN: 2100101996 Device Class: Solar Inverters Device Type: SB 4000TL-20 Software Version: 02.07.00.R Serial number: 2100101996 SUSyID: 78 - SN: 2100101996 Device Status: Ok SUSyID: 78 - SN: 2100101996 Device Temperature: 34.1°C SUSyID: 78 - SN: 2100101996 GridRelay Status: Open SUSyID: 78 - SN: 2100101996 ``` With "-v5 -d5" I find TimeOut: ``` Logon OK getInverterData(-2147483648) --------: 00 01 02 03 04 05 06 07 08 09 00000000: 7E 3F 00 41 CD 72 31 83 15 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 90 89 18 33 00000040: 00 00 00 00 00 00 05 80 00 02 00000050: 02 64 00 8C 61 00 FF 8F 61 00 00000060: B6 03 7E 63 Bytes sent getPacket(1) Timeout reading socket No data! getInverterData(sbftest) returned an error: -1 getInverterData(2048) ``` and afterwards several.... ``` cmd=1 PacketLength=85 <<<====== Content of pcktBuf =======>>> --------: 00 01 02 03 04 05 06 07 08 09 00000000: 7E FF 03 60 65 0E 50 7D 00 90 00000010: 89 18 33 00 01 4E 00 6C 03 2D 00000020: 7D 00 01 00 00 00 00 04 80 0D 00000030: 04 FD FF 07 00 00 00 84 03 00 00000040: 00 8B 7E 45 59 00 00 00 00 B8 00000050: B8 B8 B8 88 88 88 88 88 88 88 00000060: 88 5F 83 7E <<<=================================>>> Packet ID mismatch. Expected 6, received 4 getPacket(1) Received 18 bytes Received 67 bytes ``` All in the logfile.... [sbfoutput.20170617-2124.txt](neumi.selfhost.bz/sbfoutput.20170617-2124.txt)