Zero-Draw, Solid State Contactor w/Precharge (Arduino)

Just so that I am clear and not confusing folks...

I have tabled the SSR design for a month or two because I am out of HVC breakers and I need to get production going again. What I am working on right now is a simple module that will do anything *but* the discharge path between the pack and controller.

They should be small and light and cheap - such that someone can buy 2 or 3 of them and use one for HVC, one for LVC (if they want) and one for playing around with. That kind of cheap - but we will see.

Then... once I have those in production to meet this summers needs I am going to turn back and take what I learned to get the original SSR project going. I would do both at once but I am so f'ing burred in projects over here that it is just staggering.

I built an Electric motorcycle :p

-methods
 
CR2016: http://data.energizer.com/PDFs/cr2016.pdf

Very thin. 4 of them can stack in this holder
http://www.batteryholders.com/part.php?pn=BHX2-2032-SM&original=CR2032&override=CR2032
http://www.batteryholders.com/searc...ype=CR2032&term=Surface mount&override=CR2032
http://www.digikey.com/scripts/DkSearch/dksus.dll?v=61&WT.z_supplier_id=61&k=BHX2-2032-SM&cur=USD

4S is a nice number.
12V out of the package
8V at rated output (a little shy but enough)
about 900 hours @ 100uAh
Over a year of service if used 2 hours every day

This is a crazy site that has more battery holds than I have ever seen in one spot.
http://www.batteryholders.com/search.php?cat=Coin+Cell+Holder&num=&type=CR2032&term=
This is just the CR2032 holders (and dual holders). Other cells fit - as seen in the above link. 4pcs of thinner bats fit this dual bat holder

100uA is a generous budget - even for an off the shelf, low parts count fet driver.

Footprint would be about a square inch, and 1/4" thick

Total cheeser way to solve it. If I were going to an automated assembly house I would just use 4 diodes and 4 caps - but placing and baking 8 parts (although much cheaper) is a lot more work and not worth it. 4 cell stack FTW.

Until I change my mind again

-methods
 
Just a thought... as the CR2016 cells die at 2 or 3 years... will they inadvertently put you into a failure mode where the gate drive is insufficient and keep the FETs in their linear mode and they go "poof..." on a power cycle? How to prevent operation with say the cell stack at 3 or 4 volts and below the miller plateau?
 
That is why I keep looking for a gate-driver solution and not something more simple. All of those have a low voltage cut-off.... so I pay 100uA and I get simplicity, strong gate drive, and insurance that I wont burn up the fets.

Second method I thought of was a large Mohm voltage divider on the stack fed into the A/D of the uC. Once per day I measure the voltage - once I see 2V/cell average (or whatever) I set a Flash flag and shut down permanently.

This little project has brought up more got-cha's than the last 2 or 3 things I have played with. It is forcing me to do a lot of thinking and I am enjoying it.

-methods



bigmoose said:
Just a thought... as the CR2016 cells die at 2 or 3 years... will they inadvertently put you into a failure mode where the gate drive is insufficient and keep the FETs in their linear mode and they go "poof..." on a power cycle? How to prevent operation with say the cell stack at 3 or 4 volts and below the miller plateau?
 
I solved the HVC Breaker.
There were two "requirements" that I got suck on that were not true requirements
I am going to write it up and post it - it will take a little while

Uses almost no parts - like 5
Good for charging up to something absurd like 80S @ 40A+ with no cooling
Shuts itself off before gate gate threshold is an issue (using BOD)
Uses a single coin cell holder with two large cells stacked in series
No regulators
Draws nearly nothing - tens of uA - should last years and years
Uses a pair of dirt cheap, commonly available power mosfets
No drivers, no clap-trap, no charge pumps
No crystal, caps, or any of that crap - internal clock
Uses super simple to set parts - nothing difficult - so good for home production
PWM capable (testing will show - external inductor may be needed)

I only like to make circuits that are simple and beautiful - like so clean that they look like the "example" picture in a datasheet. No frigging claptrap!!!

It is going to work awesome.

Will be capable of cool things that a "dumb" circuit can not do... for instance I can set up the LVC input to take user codes... so the user can BEEP BEEP BEEP and set a charger time limit of 1 hour for safety.... or if it is being used to power an accessory device - like an LED light - it can be set to softly throttle the output when the battery starts hitting LVC.

Ok - I have to go clean the filter on our well and then I am going to write it up

-methods
 
Can't wait to see it.

PWM without inductors is possible on the charging line since the voltage differential is typically not much. As I learned with my older BMS circuit, some chargers will have indigestion with a PWM in a certain frequency range. Lowering the frequency to like 10Hz generally solves this. Even then, not all chargers will be happy with this, but should not cause destruction. Around 1000Hz is where they can blow up easily.

What does the stuff you get out of the water filter look like?
 
fechter said:
Can't wait to see it.

I am burnt - tomorrow morning after I consume my coffee :D

PWM without inductors is possible on the charging line since the voltage differential is typically not much.

I totally agree. On my LTC BMS V3 and V4 I did 4khz PWM. The chip I was using could do something like 4khz or 20khz. The noise was horrible but it worked fairly well. Needed 10uF of ceramic to keep it from going thermal tho - that was 4pcs of IRFB4115 doing 105V.

As I learned with my older BMS circuit, some chargers will have indigestion with a PWM in a certain frequency range. Lowering the frequency to like 10Hz generally solves this. Even then, not all chargers will be happy with this, but should not cause destruction. Around 1000Hz is where they can blow up easily.

On my version 2 we had no bypass caps and ended up having to run 1hz PWM :mrgreen: It was pretty lame....

What does the stuff you get out of the water filter look like?

Its all over my pants... this is an iron eating bacteria. Today I was cleaning the tank. Its a 5,000G tank. Inside is a 2" PVC pipe and around that is a very large filter. Ozone is pumped to the bottom of the pipe creating a lifter pump. As the bubbles rise and expand they pull water through the main filter and out the top. Creates a circulating current in the tank, kills all the organics, and traps all the damn redish brown milky crap.

There are 4 other 5,000G tanks next to it with a mix of untreated well water and sump water. Up on the hill we have another two 5,000G tanks full of sump water.

Anyway - the well pump itself has to be pulled once a month and cleaned out else the flow rate takes a dump. Alternative is to dump expensive crappy acid down the well to try and eat it up. That's a fail method - working on a win method.

-methods
 
Back on track...

Mosfet Choice
IRLB4030

This is a logic controlled 100V 4mOhm HexFet
4.5V will turn it completely on - 4.2V will get it close enough
2 x CR2030 coin cells in series (stacked in one holder) will drive in respectably across their full capacity
Driven directly off the uController pins - 85mA peak drive each - so a few uSeconds turn on time (~100nC Total Gate Charge)
On-Chip BOD will guarantee that we never drive the mosfets with less than 4.2V
Each mosfet is good for about 20A @ 2W of dissipation, so 40A average current with no external cooling.

I realize that there are no pull-down resistors on the Gates - I am going to handle that with the Tri-State/internal diodes of the ATTiny. I am pretty sure it will work - if it doesn't then I can always hang some post-facto. There are a ton of ways to dump charge off the gate and keep it off... like staying on 24/7 and actively holding it down.

Voltage Range
The mosfets are strapped with a 90V 1.5KW TVS Diode.
The actual DC voltage the mosfet will see is Vcharge - Vbat.

Code:
#_Cells	LVC	HVC	Delta
1	3	4	1
2	6	8	2
3	9	13	4
4	12	17	5
5	15	21	6
6	18	25	7
7	21	29	8
8	24	34	10
9	27	38	11
10	30	42	12
11	33	46	13
12	36	50	14
13	39	55	16
14	42	59	17
15	45	63	18
16	48	67	19
17	51	71	20
18	54	76	22
19	57	80	23
20	60	84	24
21	63	88	25
22	66	92	26
23	69	97	28
24	72	101	29
25	75	105	30
26	78	109	31
27	81	113	32
28	84	118	34
29	87	122	35
30	90	126	36
31	93	130	37
32	96	134	38
33	99	139	40
34	102	143	41
35	105	147	42
36	108	151	43
37	111	155	44
38	114	160	46
39	117	164	47
40	120	168	48
41	123	172	49
42	126	176	50
43	129	181	52
44	132	185	53
45	135	189	54
46	138	193	55
47	141	197	56
48	144	202	58
49	147	206	59
50	150	210	60
51	153	214	61
52	156	218	62
53	159	223	64
54	162	227	65
55	165	231	66
56	168	235	67
57	171	239	68
58	174	244	70
59	177	248	71
60	180	252	72
61	183	256	73
62	186	260	74
63	189	265	76
64	192	269	77
65	195	273	78
66	198	277	79
67	201	281	80
68	204	286	82
69	207	290	83
70	210	294	84
71	213	298	85
72	216	302	86
73	219	307	88
74	222	311	89
75	225	315	90
76	228	319	91
77	231	323	92
78	234	328	94
79	237	332	95
80	240	336	96
81	243	340	97
82	246	344	98
83	249	349	100

This basically shows that we can control charge on nearly any pack up to hundreds of volts. The very high power TVS diode will sink all the nasty current spikes that happen at connection and removal. After that it is simply the DC voltage of the charger minus the DC voltage of the cells - SO SIM PO :mrgreen: Many folks overlook this options - and it is probably because they have seen many mosfets blow up in this configuration. The secret is the ultra high speed TVS diode that eats noise and shits happiness.

THE PCB
As I have stated - when it comes to PCB's (especially those I will be producing myself) I am a minimalist. I have the board down to only 9 parts! The secret here is looking at every single thing you can eliminate... because every one of those is a part you have to buy, test, lay out, procure in bulk, paste for, tweezer down, then inspect. Anyone who has not done medium scale production in a home environment knows nothing... until you do it... hundreds of hours of solder pasting, carefully placing parts with tweezers, baking, inspecting... you just can not appreciate what eliminating 1 part means. Later if I decided to send these out to a board house - yea sure - go crazy and focus only on parts cost - but for my production method - count is >> cost.

Any way, here is the full circuit as it sits right now. No details hidden.

Tiny.jpg

Ok... Ok... before all you uController savvy guys start telling me that there are a bunch of parts missing - check this out holmes :p

Crystal and load caps
I eliminated the 3 parts by using the internal ossilator. Normally you need to place a crystal and two small caps. That is THREE PARTS! So the internal ossilator is a little sloppy - maybe +/-10% un-calibrated or or 2% if I decide to calibrate them. Totally fine.

Reset Pull-up
I am using the internal 40K-60K internal reset pull-up. It draws basically nothing so long as nothing is connected. The fear people have here is noise, and the solution to that is a solder-jumper that allows me to hard-wire the Reset to VCC if noise becomes an issue. Solder jumpers are little pads that are spaced perfectly to either bridge (or not bridge) at the time of manufacture. They work by sizing the solder paste window. Bridging the RESET to VCC just means that to program one has to touch it with a soldering iron. The main power switch will work JUST FINE to cause a reset condition... as every AVR powers on into reset.

HVC Trigger Interrupt only 1 pin
Basically this has an internal pull-up to VCC. Static draw is sub 1uA 99.999% of the time. In the event that an HVC edge comes we wake up on that pin asynchronously. Current draw spikes when the opto's are tripped - but this can be instantly killed by turning the pull-up off. SO SIM PO.

Power - 2 x CR2030 Coin Cells in series in one stacked holder
So... the absolute maximum voltage for the chip is 6V. I am totally pushing that limit, which make the chip suck power like crazy, and it is quite possible that I may put a schottky diode inline with the battery to drop anywhere from 0.3V to 0.6V. This would get me down to the totally reasonable 5.5v... but for starters I am going to go big or go home. Direct 6V power to the chip FTW. The chip will work down to at least 4.5V before the BOD kicks in - so that is 2.25V per cell... which is basically when they are dead - so if we drop another half of a volt total that puts us at 2.5V per cell... not ideal and I dont want to do it but I will if I have to. For starters - lets see what happens if we just run at 6V :twisted:

Noise
I am going to roll the dice on this one. I have the standard 0.1uF on the chip and i am adding a very large 22uF next to the coin cell to handle the big inrush blips (like mosfet turn-on, chip wakeup, etc). I think this combination of caps will provide enough stability (considering our power source is like 2mm away) to keep the boogieman away. Only testing will tell - and only rich guys can afford to dangle every bit of protective crap all over the place. Better to try to do what you can and fail, than to see that you cant do it the "best way possible" and never try.

Power Switch
The circuit shows a power switch. That really will be a 2-hole header that goes off to an optional handlebar power switch. This is not useful for normal HVC breaking, but for those who want to use the circuit to do other things... I want to keep the option open. The circuit as it stands could go between 100V and the controller regulator to implement an LVC that would not require wiring into the throttle and would totally shut off system draw. In this case we really are limited to 100V - unless we want to start getting clever :) So for some users they may put a switch on their handle-bar to act as the controller main switch. Instead of physically bringing the switch to the outside of the controller box, or doing it Lyen style, they could do it this style

ISP
I am not sure exactly how I am going to implement this - but the circuit will have an In Circuit Serial Programming port. This will allow for end user reprogramming if they have a programmer. I will probably just make an ultra-cheap ($5) Arduino based programmer that folks can use if they want.

Programming Functionality
By using the HVC Trigger Input we can program in any number of user preferences. Simple things like Charger Timeout, Soft Start, etc will surely come up later and I am ready to implement fun functions

Expanded Use - PWM etc
I have selected the two mosfet pins to be PWM pins. This means that we *may* be able to hang a big DIY ghetto inductor off the front of the board and use it for discharge. As it sits it is probably good for about 40A average - which in many cases could be a 100A current limit (depending on the KV match of the voltage/motor, wheel size, etc, etc).

So... that is where I am at today.
This is intended to fill the hole that my HVC breaker has left open. I think it will be able to do everything the HVC breaker could do but for cheaper, lighter, smaller, less current, wider voltage range, MUCH simpler production, wider function range, easier expansion, and just cooler. I can then pass my savings on to the members and try to get more people into LVC/HVC protection. I am considering a package deal for the future that will have as many LVC/HVC/Parallel boards are needed, one of these for charge breaking, and one of these for Discharge breaking, and all the balance taps etc for a reduced cost. I want more people to have cell level protection - that is how you win, and that is how you preserve batteries and have peace of mind.

Possible Changes

I may reconsider the power switch. The circuit draws such little current (it will last YEARS) that I may just want to leave it powered all the time and have the power switch run into one of the ports. The "power state" could be recorded in FLASH and in that case we would actively hold down the gates of the power mosfets. This is a good compromise... as the amount of power I would burn staying powered 24/7 is probably LESS than I would burn hanging resistors off of the mosfet gates.

Ok - I have to go take care of some other business... I am sure I forgot a bunch of stuff but this is where I am at


-methods
 
How are you going to turn off the FETs if BOD is hit?
BOD alone will cost you constant 20-25uA and max I/O pin current is 40mA (just in case you haven't noticed).
 
Methy,

Great idea - truly great, and much needed as a central method for disconnect of a pack before damage can take place.

When you get in the testing stage let me know if you want help, also quite adept with Arduino and AVR C++ code.

Regard,
Mike

PS: Are your HVC/LVC/Parallel Boards Still Available if ordered from your website?

PPS: I know your coin cells will last "forever" but how about adding a 2S 1000ah pack of Lipo which can charge at the same time as the main pack if needed? Too much complexity?
 
Njay said:
How are you going to turn off the FETs if BOD is hit?
If the tristate is not enough to pull the fet down I will hang a very large resistor out there - or try something clever with a cap.

BOD alone will cost you constant 20-25uA and max I/O pin current is 40mA (just in case you haven't noticed).

BOD is an absolute must to protect the mosfet, so I have no choice. Hanging another 200K out at the gate will double that. WIll do it if I have to.

Max IO may be RATED at 40mA but it will put out well over 85mA per channel (shown in the datasheet) and I am running two channels. I could double those up and run 2 per gate if I need to. Chip is rated for 200ma, and all of those are continuous. I could run 4 pins per gate and hang a huge cap on the input and hit the gate pretty hard.

-methods
 
mwkeefer said:
Methy,

PS: Are your HVC/LVC/Parallel Boards Still Available if ordered from your website? Yes

PPS: I know your coin cells will last "forever" but how about adding a 2S 1000ah pack of Lipo which can charge at the same time as the main pack if needed? Too much complexity?
I have been thinking about using the rechargable coins - but they are 47mAh as opposed to 200mAh. Can always design for both.... but I really want to make something with a coin cell.
 
Now that you mention you plan on integrating cell level to all this too, will you consider making the LVC boards with a higher voltage for lvc I mean isn't 3.0v already too late for LIPO ?

At the same time could additional boards be made for lifepo4 ~2.9v lvc this way people could use your boards with a123 20ah or headway cells and dump all the stupid BMS's that always seem to fail.
 
migueralliart said:
Now that you mention you plan on integrating cell level to all this too, will you consider making the LVC boards with a higher voltage for lvc I mean isn't 3.0v already too late for LIPO ?

Where did you get that information? LIPO can go down to 2.7V or even 2.5V. 3.0V is absolutely industry standard. Discharging to 3.6V is what we promote for longer cell life and avoiding driving lower cells into the ground (for those who do not have cell level LVC)

At the same time could additional boards be made for lifepo4 ~2.9v lvc this way people could use your boards with a123 20ah or headway cells and dump all the stupid BMS's that always seem to fail.

The LiFe market is covered. There must be 100 different solutions - surely one must be good? btw: LiFe goes way lower than 2.9V - that is resting voltage. More like 2.0V is what you want.

-methods
 
So given that your lvc and hvc boards are setup for multiple packs in parallel let's say 5 parallel that's 25ah per bank. In a typical ebike application people discharge let's say 50 amps max. That means 2c. If you get to 2.7v like you said or even 3v you're way below the cliff. Does that make sense?
 
No, it does not make sense at all. The dynamic voltage of the pack is not what you are worried about, only the static resting voltage. This means that if you load your pack down to 50C and **under load** you hit 3.0V... this is totally ok... because once the load is removed the cells will settle back up to 3.6V or whatever.

The "cliff" is only related to the resting voltage of the cells. I am not saying that it is good for cells to see very high loads, but what I am saying is that a cell that droops down to 3.1V under heavy load is totally ok. Limiting cells to only be able to dip to something like 3.5V will severely limit your high discharge range.

More importantly - it is the job of the cell level LVC to give a HARD LIMIT. If you want to "go easy" on your packs.. well that is the job of the CONTROLLER or CA. Set the PACK LEVEL LVC to something equ to 3.5V per cell if that is what you want - but IMHO you always want your hardware protection at the true hardware limit... then you set your software protection and your preferred limit.

-methods

Edit: Also... this cliff you speak of... it is at 2.7V or 3.0V per cell... so whether you reach that under dynamic load or sitting static... if you are still at 3.0V you are - by definition - not over the cliff. By cliff I mean damage point. Perhaps you refer to the cliff representing usable capacity... but when you are 5 miles from home, at the bottom of a hill, and made a bad decision with a 100lb bike - I guarantee you will want to use that last Ah of capacity you have - so the hardware limit should let you drain as much from the cells as you can without damaging them. To get the last AH you can turn down the pack level LVC in your CA or on your controller.


migueralliart said:
So given that your lvc and hvc boards are setup for multiple packs in parallel let's say 5 parallel that's 25ah per bank. In a typical ebike application people discharge let's say 50 amps max. That means 2c. If you get to 2.7v like you said or even 3v you're way below the cliff. Does that make sense?
 
Njay said:
How are you going to turn off the FETs if BOD is hit?
BOD alone will cost you constant 20-25uA and max I/O pin current is 40mA (just in case you haven't noticed).

I thought some more about what you said.

Now that i am running at 5.5V instead of 3V the stakes are a little higher. I think I am going to change things to look like this:

* The switch will not remove power from the system - the system will remain powered at all times. The switch will go to a pin input
* When the switch is off or after the HVC is triggered the system will go into "Deep Sleep". BOD off, everything off, so like 14uA resting current
* When the switch is turned on, or the switch is toggled to clear the HVC event, then at that time BOD will be turned back on and the fets will be turned on
* When the fets are on the BOD will be on and we will sleep, waiting for a trigger from either HVC or from the switch

I will show some test data later on what kind of current you can actually get out of the pins. I think I might forgo the PWM ability to use 4 pins to drive the two mosfets... that will give much faster rise times... AND faster drop in the case of power loss.

When a chip is unpowered it has about 400K to ground. Two pins in parallel would be 200K to ground. That is plenty to safely pull a gate down... though possibly not a Logic level gate - tests will tell.

Also - I need to see what the tristate pins look like while in BOD lockup.

Thanks for your input.

-methods
 
methods said:
No, it does not make sense at all. The dynamic voltage of the pack is not what you are worried about, only the static resting voltage. This means that if you load your pack down to 50C and **under load** you hit 3.0V... this is totally ok... because once the load is removed the cells will settle back up to 3.6V or whatever.

The "cliff" is only related to the resting voltage of the cells. I am not saying that it is good for cells to see very high loads, but what I am saying is that a cell that droops down to 3.1V under heavy load is totally ok. Limiting cells to only be able to dip to something like 3.5V will severely limit your high discharge range.

More importantly - it is the job of the cell level LVC to give a HARD LIMIT. If you want to "go easy" on your packs.. well that is the job of the CONTROLLER or CA. Set the PACK LEVEL LVC to something equ to 3.5V per cell if that is what you want - but IMHO you always want your hardware protection at the true hardware limit... then you set your software protection and your preferred limit.

-methods

Edit: Also... this cliff you speak of... it is at 2.7V or 3.0V per cell... so whether you reach that under dynamic load or sitting static... if you are still at 3.0V you are - by definition - not over the cliff. By cliff I mean damage point. Perhaps you refer to the cliff representing usable capacity... but when you are 5 miles from home, at the bottom of a hill, and made a bad decision with a 100lb bike - I guarantee you will want to use that last Ah of capacity you have - so the hardware limit should let you drain as much from the cells as you can without damaging them. To get the last AH you can turn down the pack level LVC in your CA or on your controller.


migueralliart said:
So given that your lvc and hvc boards are setup for multiple packs in parallel let's say 5 parallel that's 25ah per bank. In a typical ebike application people discharge let's say 50 amps max. That means 2c. If you get to 2.7v like you said or even 3v you're way below the cliff. Does that make sense?

If they are at 3v no load they are discharged. They won't do 5 miles uphill with a 100lb bike ?

The cliff is when the voltage starts to drop fast under load and it does not take much load either. You know, like on a discharge graph.

Once it starts to happen then discharge should be stopped.

That is a problem with a bms. They can't tell when that starts to happen. They stop the discharge after the cells go off the cliff.

If they are under load while riding how can you know the static voltage unless you stop or go downhill ?

A loud lipo alarm that you can adjust the alarm voltage works best, like a beeper that can be set in your car to go off if there is a 1/4 tank left or set it too go of if there is 1/8 tank left.
 
etriker said:
If they are at 3v no load they are discharged. They won't do 5 miles uphill with a 100lb bike ?

I changed subjects and did not change paragraphs. Read it again.... I was carrying on the idea that you set a pack level LVC to something like 3.3V per cell, then you can bypass that and run all the way down to the hardware LVC

The cliff is when the voltage starts to drop fast under load and it does not take much load either. You know, like on a discharge graph.

Once it starts to happen then discharge should be stopped.

Yes I know it well - but your second statement is more a guideline than a rule. You should stop discharging before your cells drop to a point where they will be damaged. That is why a HARDWARE limit should be set at the DAMAGE THRESHOLD which has nothing to do with the performance cliff and everything to do with the resting voltage. If you want to keep your cells in the "good operating range" then use your adjustable pack level LVC to do this. Setting hardware cell level LVC to anything over 3.0V does not make sense.

That is a problem with a bms. They can't tell when that starts to happen. They stop the discharge after the cells go off the cliff.

Ok - now I am getting irritated. Who told you of this CLIFF? A cliff implies that there is no going back. The only real cliff in Lipo is driving them down to 1V or 0.5V. THAT IS A CLIFF - one that you cant get back up - one where the cells are permanently damaged. Discharging your cells past the "cliff" you speak of simply means discharging all the way to the industry accepted level of 2.7V or 3.0V

If they are under load while riding how can you know the static voltage unless you stop or go downhill ?

You dont need to know. You just cut output if hte cells reach 3.0V - be that dynamic voltage or static voltage. Please drop the cliff analogy - it is not helping.

A loud lipo alarm that you can adjust the alarm voltage works best, like a beeper that can be set in your car to go off if there is a 1/4 tank left or set it too go of if there is 1/8 tank left.

The only thing a loud lipo alarm accomplishes is putting your packs out of balance and eventually killing the pack if left on long enough. We have all been there and done that 5 years ago... and that is why my cell level LVC detectors draw only 3uA (0.000003A) and do not draw the 3mA or whatever many of these cheap crap buzzers draw

A buzzer is NOT the way to do it. The proper way to "do it" is to set your CA pack level LVC to something that sums to 3.3V per cell or 3.6V per cell. The CA will then start to *softly* retard your power output alerting you to the fact that you have reached the near-end of your pack.

If you must run a buzzer then you want one that will turn on at a certain level - then turn off at a lower level - otherwise it will slowly destroy your pack. I did this myself just a few months ago by hooking a buzzer up to a 4S pack I was using to start an old pickup truck. I was driving the truck on the starter using the 4S pack and wanted audio indication that I was almost out of capacity. Well. I never heard it and I moved the truck.. then forgot the pack in there... and the buzzer then beeped for a week (my father heard it and asked about it). When I got back to the pack it was dead. There is an anecdote for you.

-methods
 
When I am done riding there is nothing hooked to my cells.

I unhook everything.

I have been in electronic repair since 1986 and have seen a lot of leaky transistors and caps.

And transistor and cap quality has really gone downhill.

If my cells fail I will know it was not my $3 lipo alarms or $32 controller ?

I don't forget to put gas in the truck or turn it off when I am done driving it either ? :)
 
etriker said:
When I am done riding there is nothing hooked to my cells.
I unhook everything.

Good, you are one of the few. That is wise... but you could leave mine hooked up :wink:

I have been in electronic repair since 1986 and have seen a lot of leaky transistors and caps.

That is why this thread is here - to make an SSR to isolate the pack after riding is done.

If my cells fail I will know it was not my $3 lipo alarms or $32 controller ?

A guy who has been in electronic repair since 1986 should know how to take a current reading fro time to time and see if any leaks have developed

I don't forget to put gas in the truck or turn it off when I am done driving it either ? :)

That is a very poor analogy. A truck rumbles and bumbles and stinks. You can hear it. It burns gas. An EV can quietly sit with a tiny draw happening that you are unaware of - that could only cause damage over a month or two time.

A truck also has to be taken to a gas station to be refilled - so people have learned not to screw up. A bike can be charged almost anywhere if your charger is on board... so it is not that big of a deal.

-methods
 
Feel free to rebut my last set of statements... then please folks - I have no interest in talking about these things. This subject has been covered ad nauseum - then again - then again. There are more threads on lipo care on the internet then there are nude pictures... and I prefer nude pictures.

-methods
 
They are bright and out in the open. I have never forgot to unhook then. I get off the bike and right away after every ride want to see what they say then unhook them.

Takes not a lot of time.

If they trick you up and ruin your cells then don't use them. They don't trick me at all and beep real loud. :)
 
If it works for you then I am happy. Please promote that others use them and tell them of your good experiences.

I need something more fool proof because I am lucky if my wife even turns her bike off.

-methods
 
methods said:
Feel free to rebut my last set of statements... then please folks - I have no interest in talking about these things. This subject has been covered ad nauseum - then again - then again. There are more threads on lipo care on the internet then there are nude pictures... and I prefer nude pictures.

-methods

Right ? Like A123 M1 cells have very little left in them at 3v resting voltage.

Almost all laptop cells have very little left when the resting voltage is at 3v.

What cells do you think are not almost done at 3v resting voltage ?
 
Back
Top