oldswamm
100 W
Hi Filip, <edited for spelling,, sorry Filip>
Trying to address your points in order.
You can keep it as simple as possible, or anywhere in between.
I'm trying to come up with a replacement for the switched supplies normally used for bulk charging, and providing for some optional 'bells and whistles' in the process, although my board could be used in a simpler configuration as well, just leave out all the parts but the processor and a few resistors.
As to complexity, the most complicated version of what I'm trying to design is FAR simpler than ANY switched charger. In my opinion, at it's 'worst', with 6 different caps, current sensing, and serial ID chips with temp sensors on the batteries, it's STILL quite simple.
This technology allows us to charge a 4s or 30s from the same charger, something no switched supply that I've seen can do.
We can monitor the voltage at the charge connector, so I don't see an advantage in monitoring a subset of cells as I understand you're suggesting. Also the reason for using wireless battery ID would be to keep the wiring/connections simple.
I'm trying to design in 'foolproofedness' (the spell checker doesn't think that's a word!
).
With a switch, it's easy to use the wrong switch position... Also we might want more than 3 settings. You might want to charge the racer to 4.22 and the commuter to 4.15 for example.
If your Arduino setup has an HVC shutdown input, it will shut off the relay and you wouldn't have high voltage across your BMS. I wouldn't plan on using an external HVC shutdown with this setup, complicated or simple.
If you don't want to use a processor, the analog circuit fechter proposed would be fine. If you're using a processor, it would be overkill (IMHO). I guess you could use it for redundancy, if you're worried about processor failure, in which case I would use redundant relays, but I still think that's overkill, (and you would still have to figure out how to program the redundant circuit for different batteries and keep it foolproof).
Bob
Trying to address your points in order.
You can keep it as simple as possible, or anywhere in between.
I'm trying to come up with a replacement for the switched supplies normally used for bulk charging, and providing for some optional 'bells and whistles' in the process, although my board could be used in a simpler configuration as well, just leave out all the parts but the processor and a few resistors.
As to complexity, the most complicated version of what I'm trying to design is FAR simpler than ANY switched charger. In my opinion, at it's 'worst', with 6 different caps, current sensing, and serial ID chips with temp sensors on the batteries, it's STILL quite simple.
This technology allows us to charge a 4s or 30s from the same charger, something no switched supply that I've seen can do.
We can monitor the voltage at the charge connector, so I don't see an advantage in monitoring a subset of cells as I understand you're suggesting. Also the reason for using wireless battery ID would be to keep the wiring/connections simple.
I'm trying to design in 'foolproofedness' (the spell checker doesn't think that's a word!
With a switch, it's easy to use the wrong switch position... Also we might want more than 3 settings. You might want to charge the racer to 4.22 and the commuter to 4.15 for example.
If your Arduino setup has an HVC shutdown input, it will shut off the relay and you wouldn't have high voltage across your BMS. I wouldn't plan on using an external HVC shutdown with this setup, complicated or simple.
If you don't want to use a processor, the analog circuit fechter proposed would be fine. If you're using a processor, it would be overkill (IMHO). I guess you could use it for redundancy, if you're worried about processor failure, in which case I would use redundant relays, but I still think that's overkill, (and you would still have to figure out how to program the redundant circuit for different batteries and keep it foolproof).
Bob