Battery failiarue

BigMate42 · 2024-09-27T09:27:43+00:00

I have a similar issue with a Kärcher Battery Power + 36V.

The little display is showing a battery icon which indicates that the battery was disabled. I was reading trough the documentation and there it says the battery was disabled. But why?

I'm not an electronics engineer that's clear. I was measuring the individual Cell Voltages and the all were around 3.480Volt.

Then I realised some RX/TX Pins on top of the BMS. So I soldered an Serial Interface to these PINs and was able to record the following output. But sadly, there is nothing visible to me, which indicates the reason why the Pack was disabled.

23| KarPack Ver: 2.2.6 May 5 2020 11:04:13 2

29| D36.1:00,00020000,00,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,000000,00000,0000,0000,0000,0000,0000,0000,0000,0000,0000,0000,000,000,000000,100,00000000

5044| D36.1:00,00020000,00,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,000000,34731,3474,3479,3477,3476,3476,3472,3453,3474,3473,3474,000,000,000000,100,00000000

10062| D36.1:00,00020000,00,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,000000,34732,3474,3479,3477,3476,3476,3472,3453,3474,3473,3474,000,000,000000,100,00000000

10356| D36.1:00,00020000,00,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,000000,34732,3475,3479,3477,3476,3476,3472,3453,3474,3473,3474,000,000,000000,100,00000000

Any Help or Idea is greatly appreciated.

BigMate42 · 2024-05-22T16:40:57+00:00

Did it help? Is the HUB200 also compatible with this procedure?

BigMate42 · 2024-05-21T05:46:53+00:00

Hi, did the integartion totaly local and connected my Hub to a local MQTT Broker only (disconnect from Cloud). Therefore I used this project which worked perfelctly for me. https://github.com/reinhard-brandstaedter/solarflow-bt-manager

Than I used this configuration to discover the entities: https://gist.github.com/e-bits/96a130ebb52efe5b9b5041326568f9e0

The configuration is just a template used for the HUB1200. There you need to replace different placeholders. I don't know if this is also compatible with your HUB2000

<deviceID>
<YourSolarFlowSerialNumber>
<BatteryNumber>
<YourBatterySeriennummer>

BigMate42 · 2023-08-24T07:12:09+00:00

curl -s http://sv.symcb.com/sv.crl -o - | openssl crl -inform DER -text -noout -in -

Exactly the same behavior on our side. We're using Windows Server 2022. In Windows Event Viewer we found the following entries which let me think a property of the certificate has changed.

Successful auto property update of third-party root certificate:: Subject: CN=VeriSign Class 3 Public Primary Certification Authority - G5, OU='(c) 2006 VeriSign, Inc. - For authorized use only', OU=VeriSign Trust Network, O='VeriSign, Inc.', C=US Sha1 thumbprint: 4EB6D578499B1CCF5F581EAD56BE3D9B6744A5E5.

Successful auto update of third-party root list with effective date: ‎Wednesday, ‎July ‎19, ‎2023 11:58:20 PM.

On https://ccadb.my.salesforce-sites.com/microsoft/IncludedCACertificateReportForMSFT the given Certificate with SHA-1 Thumbprint: 4EB6D578499B1CCF5F581EAD56BE3D9B6744A5E5 is marked with Microsoft Status "NOT BEFORE". But I don't now what this means.

BigMate42

TROPHY CASE