ng.sa
Member
- Joined
- Apr 4, 2017
- Messages
- 92
The current BMS's are way to 'smart' and expensive.
What we do not want firstly
- An app. to connect to the BMS
- these apps are g8 to debug a pack, but way to complex for end users who just want to plug and play and walk away
- Multi lingual ( English only )
- LED screen
- WiFi connectivity
- Bluetooth connectivity
What our basic requirements are
- 29.xV and below 7s2p 1865 and 2170 cell monitoring
- Store output log to a FAT32 filesystem on a removable media
- Monitor cycles
- Monitor temperature
- Programmatically set high and low water marks
Obviously would prefer to COtS ( Common Off the Shelf ) but, I have designed and built hardware / software systems for dod.gov.au and private ent. so I understand how much time and effort to start from scratch.
One possibility would be for a current manufacturer to de-spec. a smart BMS, I have seen this approach with white goods that use remote controls, you only allow a few features of a unit to be accessed via the remote, but the chip set is the same in all of the units. We call this badge engineering, all units internally are exactly the same you re-badge and send a different remote in the packaging.
The only novel part of this projects is the writing to the media and the management of the .bms files.
We already have a soft. sys. that sends email due to monitoring alerts to NOC ( Network Oper. Centre ) so we just need to be able to read the .BMS files to gen. an email when the charge ( high water ) dis-charge ( low water ) marks have been meet.
What we do not want firstly
- An app. to connect to the BMS
- these apps are g8 to debug a pack, but way to complex for end users who just want to plug and play and walk away
- Multi lingual ( English only )
- LED screen
- WiFi connectivity
- Bluetooth connectivity
What our basic requirements are
- 29.xV and below 7s2p 1865 and 2170 cell monitoring
- Store output log to a FAT32 filesystem on a removable media
- Monitor cycles
- Monitor temperature
- Programmatically set high and low water marks
Obviously would prefer to COtS ( Common Off the Shelf ) but, I have designed and built hardware / software systems for dod.gov.au and private ent. so I understand how much time and effort to start from scratch.
One possibility would be for a current manufacturer to de-spec. a smart BMS, I have seen this approach with white goods that use remote controls, you only allow a few features of a unit to be accessed via the remote, but the chip set is the same in all of the units. We call this badge engineering, all units internally are exactly the same you re-badge and send a different remote in the packaging.
The only novel part of this projects is the writing to the media and the management of the .bms files.
We already have a soft. sys. that sends email due to monitoring alerts to NOC ( Network Oper. Centre ) so we just need to be able to read the .BMS files to gen. an email when the charge ( high water ) dis-charge ( low water ) marks have been meet.