Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support Creabest BMS / CBT Power #80

Open
snipah opened this issue Apr 12, 2023 · 16 comments
Open

Support Creabest BMS / CBT Power #80

snipah opened this issue Apr 12, 2023 · 16 comments
Labels
new-bms New feature or request

Comments

@snipah
Copy link

snipah commented Apr 12, 2023

Hi Fabian,
it would be great if you could support Creabest-BMS too. Willing to support BMS-Captures of course. Just let me know what I need to do.

@snipah
Copy link
Author

snipah commented Apr 12, 2023

Scanner On.
Device Scanned.
Connected.
Discovered Device Information, Battery Service, FFE0, FFE5, FFF0, FFD0, FFC0, FFB0, FFA0, FF90, FC60, and FE00 Services.
Discovered Characteristics System ID, Firmware Revision String, and Manufacturer Name String for Service Device Information.
Discovered Characteristics Battery Level for Service Battery Service.
Discovered Characteristics FFE4 for Service FFE0.
Discovered Characteristics FFE9 for Service FFE5.
Discovered Characteristics FFF1, FFF2, FFF3, FFF4, FFF5, FFF6, FFF7, FFF8, and FFF9 for Service FFF0.
Discovered Characteristics FFD1, FFD2, FFD3, and FFD4 for Service FFD0.
Discovered Characteristics FFC1 and FFC2 for Service FFC0.
Discovered Characteristics FFB1, FFB2, FFB3, and FFB4 for Service FFB0.
Discovered Characteristics FFA2 and FFA1 for Service FFA0.
Discovered Characteristics FF91, FF92, FF93, FF94, FF95, FF96, FF97, FF98, FF99, and FF9A for Service FF90.
Discovered Characteristics FC64 for Service FC60.
Discovered Characteristics FE01, FE02, FE03, FE04, FE05, and FE06 for Service FE00.
Characteristic System ID has no Descriptors.
Characteristic Firmware Revision String has no Descriptors.
Characteristic Manufacturer Name String has no Descriptors.
Discovered Client Characteristic Configuration for Characteristic Battery Level
Discovered Client Characteristic Configuration for Characteristic FFE4
Characteristic FFE9 has no Descriptors.
Characteristic FFF1 has no Descriptors.
Characteristic FFF2 has no Descriptors.
Discovered Client Characteristic Configuration for Characteristic FFF3
Characteristic FFF4 has no Descriptors.
Characteristic FFF5 has no Descriptors.
Characteristic FFF6 has no Descriptors.
Characteristic FFF7 has no Descriptors.
Discovered Client Characteristic Configuration for Characteristic FFF8
Discovered Client Characteristic Configuration for Characteristic FFF9
Characteristic FFD1 has no Descriptors.
Characteristic FFD2 has no Descriptors.
Discovered Client Characteristic Configuration for Characteristic FFD3
Discovered Client Characteristic Configuration for Characteristic FFD4
Characteristic FFC1 has no Descriptors.
Discovered Client Characteristic Configuration for Characteristic FFC2
Characteristic FFB1 has no Descriptors.
Characteristic FFB2 has no Descriptors.
Characteristic FFB3 has no Descriptors.
Characteristic FFB4 has no Descriptors.
Characteristic FFA2 has no Descriptors.
Discovered Client Characteristic Configuration for Characteristic FFA1
Characteristic FF91 has no Descriptors.
Characteristic FF92 has no Descriptors.
Characteristic FF93 has no Descriptors.
Characteristic FF94 has no Descriptors.
Characteristic FF95 has no Descriptors.
Characteristic FF96 has no Descriptors.
Characteristic FF97 has no Descriptors.
Characteristic FF98 has no Descriptors.
Characteristic FF99 has no Descriptors.
Characteristic FF9A has no Descriptors.
Discovered Client Characteristic Configuration for Characteristic FC64
Characteristic FE01 has no Descriptors.
Characteristic FE02 has no Descriptors.
Characteristic FE03 has no Descriptors.
Characteristic FE04 has no Descriptors.
Characteristic FE05 has no Descriptors.
Characteristic FE06 has no Descriptors.
Device Appearance switched from Generic to Battery.
Disconnected.

@snipah
Copy link
Author

snipah commented Apr 12, 2023

IMG_1026

@snipah
Copy link
Author

snipah commented Apr 17, 2023

Ich glaube rausgefunden zu haben, dass Creabest die Produkte der CBT Power umlabelt und somit auch deren BMS verwendet. Dazu habe ich folgendes gefunden: https://www.mikrocontroller.net/topic/513514
Kommunikationsprotokoll_der_VB-Serie-DE.pdf

Dass ganze ist zwar für serielle Kommunikation, die mein Akku mangels Schnittstelle nicht beherrscht, vielleicht hilft es aber trotzdem.

@fl4p fl4p added the new-bms New feature or request label Aug 20, 2023
@fl4p fl4p changed the title Support Creabest BMS Support Creabest BMS / CBT Power Sep 28, 2023
@joeetti
Copy link

joeetti commented Nov 23, 2023

ich folge mal gespannt.... :-)

@Alex-DeIt
Copy link

Hello snipah,

konntest Du das Problem lösen?
Es ist mir endlich gelungen, Daten zu empfangen, kann aber damitn wenig anfangen, da sie nicht constant sind, sondern continuirlich oszillieren.
Danke und Grüße
Alex

@snipah
Copy link
Author

snipah commented May 20, 2024

Hi Alex! Unfortunately not. Did you receive the data via Bluetooth? Are they of any help for us? I'm not really techy enough to support, but would really love having support for this BMS ;)

@Alex-DeIt
Copy link

Hi snipah,

yes, I receive them via Bluetooth. This is what I am getting through Batmon:
image
The problem which I have is that the values are not constant but oscillating. Hier is for example the graph related to the tension:
image

@Gruni22
Copy link

Gruni22 commented Sep 29, 2024

Hi snipah,

yes, I receive them via Bluetooth. This is what I am getting through Batmon: image The problem which I have is that the values are not constant but oscillating. Hier is for example the graph related to the tension: image

Hi, I would also be interested getting data from Creabest batteries.
How did you manage to receive data?

@snipah
Copy link
Author

snipah commented Sep 29, 2024

Wasn't me, it was Alex-DeIt. But if I remember correctly, he simply used the dummy parameter, which simply outputs fake/dummy-data

@Gruni22
Copy link

Gruni22 commented Sep 29, 2024

@snipah Ah, Now I‘ve read the other issue.
So I guess, you also didn‘t have success, so far.
I am also trying to get data out of a CREABEST Battery.

@7wells
Copy link

7wells commented Sep 30, 2024

Hi @snipah
Have you tried the integration from Patrick? https://github.com/patman15/BMS_BLE-HA
You can add further battery types there on request.

@Gruni22
Copy link

Gruni22 commented Sep 30, 2024

Looks promising, but only reports now Supported Type.
I tried to do some reverse Engineering the Android App and found some useful Information.
I have to continue with further investigation.

@snipah
Copy link
Author

snipah commented Sep 30, 2024

Hi @snipah Have you tried the integration from Patrick? https://github.com/patman15/BMS_BLE-HA You can add further battery types there on request.

Thanks... already filed a request... hopefully we can get this sorted out

@snipah
Copy link
Author

snipah commented Sep 30, 2024

Looks promising, but only reports now Supported Type. I tried to do some reverse Engineering the Android App and found some useful Information. I have to continue with further investigation.

Would be great if you could also report it into my request.. patman15/BMS_BLE-HA#59

@Gruni22
Copy link

Gruni22 commented Oct 3, 2024

I prepared bunch of data of a working (Java) setup.
But I do not know, how to push a branch.
I uploaded my work here.
tools.zip

@snipah
Copy link
Author

snipah commented Oct 7, 2024

@fl4p In case you did not notice: Gruni22 supplied all relevant information to support a new battery brand.

@fl4p fl4p pinned this issue Oct 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
new-bms New feature or request
Projects
None yet
Development

No branches or pull requests

6 participants