Hi All,
Does anyone have a dbc file or even a datasheet for the canbus messages required for BMS into a gx device. I know what can id’s the Fogstar batteries are sending in as I have analysed the output from one of there batteries. I can decode some of the messages but it would be a lot quicker if there was a dbc file or datasheet giving me all the information that Victron can receive?
Victron does not publish their spec to the public. Interested manufacturers can request access from their regional sales manager.
As a community we can’t share that data, though some of it is wafting around the internet if you search.
I found some info but not all of it. I’ll ask the local dealer to request the information
Is this enough?
If not, what do you need more?
The minimum CAN-IDs required for the core functionality are 0x351, 0x355, 0x356 and 0x35A.
Thank you for that, there is a fair bit of conflicting information out there. I have can inspected the Fogstar batteries I use with the protocol on Victron and some id’s differ. The main ones above are the same but the pylon datasheet is different to what I’m getting but maybe that’s out of date.
Please tell about your conflicting info to see if I can shed some light…
Below are the can id’s out of the fogstar battery, pylontech talk about a 0x359 which is for protection and modules numbers but that’s not coming out of the Fogstar but still getting the protection and modules number messages on the gx device.
| Can ID |
|---|
| 377 |
| 378 |
| 379 |
| 35A |
| 351 |
| 355 |
| 356 |
| 35E |
| 35F |
| 370 |
| 371 |
| 372 |
| 373 |
| 374 |
| 375 |
| 376 |
Latest I could find…
Both infos were posted by the respective manufacturers on the web, but later withdrawn.
Thanks to Wayback Machine, here they are, at year 2021 level.
Victron BMS info.
Pylontech BMS info.
That is ideal. Thank you
@mattie170
pls. have a look into Stuart Pittaway’s “diyBMS”. BTW it’s worse having a look into the whole open source HW and SW by Stuard.
Or send me an email (bk-ve@gmx.de) with your github user and I point you to some more open-source projects.
Got the newer 2023 version from victron and wrote the combiner in node red on a pi.
It’s fully functioning and working, can build it to accept as many banks as you like, just need more pi’s. Plus I have written it so you can run 2 pi’s in shadow mode so if the master fails the second will take over in 2 seconds. I will do this on my system at work as it is mission critical.
Can you share, kindly please?
Thank you in advance.
If you need to figure it out, simply scan all address ranges and echo what responds.
The problem isn’t finding the sdo, rather the interpretation.
Can’t just echo it, its got to be combined and that’s where all the work is, decoding out of a buffer, calculate it then send it out again in a new buffer. There is also the extra messages that you need to create that don’t get sent normally. Well by Fogstar anyway.
Was a fun project to get sorted.
That just for the initial attack vector.
I got the actual definitions from the unencrypted binary.
It would appear they use a single firmware for all their batteries, the object extraction seems like it would work across the board.
Again, can you please share the newer 2023 version?
Thanks in advance!
I said I wouldn’t share it to get it. Ask your dealer and they should be able to get it for you! It only took a couple of weeks.
Thanks for the answer !
Give me some time, I’m close to getting it.
The problem is stiching
