<arossdotme>
looks like theres some differences. not sure what they mean
<arossdotme>
i dont think i need balancing build in? as i will only be using a balancing charger. or does the balancing circuity help keep the cells balanced when discharged? :/
DocScrutinizer05 has quit [Disconnected by services]
DocScrutinizer05 has joined #qi-hardware
sandeepkr has joined #qi-hardware
wildlander has quit [Quit: Saliendo]
xiangfu has joined #qi-hardware
sb0 has quit [Quit: Leaving]
eintopf has quit [Ping timeout: 246 seconds]
eintopf has joined #qi-hardware
xiangfu has quit [Ping timeout: 244 seconds]
sb0 has joined #qi-hardware
sb0 has quit [Quit: Leaving]
sb0 has joined #qi-hardware
<DocScrutinizer05>
arossdotme: yes, balancing also on discharge helps a lot, though in this case it's more the per-cell undervoltage monitor + cutout
<DocScrutinizer05>
that does the trick
<DocScrutinizer05>
the balancing current is too low to actually help during high load discharge
<DocScrutinizer05>
in your last link you posted
wolfspraul has joined #qi-hardware
rjeffries has joined #qi-hardware
rjeffries has quit [Ping timeout: 252 seconds]
<wpwrak>
now, let's see if i can get this voltage regulation redesign done. that stuff's been sitting on my desktop for the better part of three weeks by now. and each time i think i've covered everything i find something's i've overlooked :(
sandeepkr_ has joined #qi-hardware
<eintopf>
good luck :-/
<arossdotme>
DocScrutinizer05, thanks muchly, feel ive been enlightened some more :)
<arossdotme>
my discharge load is a few amps. 3-4A for my audio power amp, 3A for my rgb led light panel, 2-3or4?idk for my netbook
sandeepkr has quit [Ping timeout: 260 seconds]
<arossdotme>
depends on how many things are connected to it
sandeepkr__ has quit [Read error: Connection reset by peer]
sandeepkr__ has joined #qi-hardware
dandon has joined #qi-hardware
<wpwrak>
eintopf: let's hope that it'll have many good years of service life left :)
<eintopf>
wpwrak: I also try to working on short address stuff
<eintopf>
it worksa
<eintopf>
but I did everywhere a /* TODO */ in ipv6 neighbor discovery...
<eintopf>
because it's not easy to make stuff there which is very specific to link-layer handling in a global upper layer implementation
<eintopf>
but I think for 6lowpan we need an own neighbor discovery implementation anyway
<eintopf>
but this is for future, first prepare the neighbor layer (which is used by arp/ipv6 neighbor discovery/ ALSO ATM YEAH!/etc...) to give me the neighbour_priv pointer when calling dev_hard_header
<eintopf>
and I hope they will accept it mainline
<eintopf>
possible othersolution would be 1. backup skb->cb, 2. put pointer into skb->cb, 3. call dev_hard_header, 4. restore skb->cb
<eintopf>
but this is bullshit
<wpwrak>
yeah, sounds very ugly
<eintopf>
I want it as parameter for dev_hard_header
<eintopf>
of course const
<eintopf>
but I first want to make some use-case for short address handling in neighbor discovery cache of ipv6, then all people understands why I need that
<eintopf>
meh, I watched alien at the tv while eating
<eintopf>
the alien blobs out of the guy
xiangfu has joined #qi-hardware
<wpwrak>
while eating, it's best to watch "the meaning of life" by monty python, especially the restaurant scene.
xiangfu has quit [Quit: leaving]
sandeepkr__ has quit [Read error: Connection reset by peer]
sandeepkr__ has joined #qi-hardware
larsc has quit [Ping timeout: 244 seconds]
larsc has joined #qi-hardware
sandeepkr__ has quit [Read error: Connection reset by peer]