![]() |
Mgm 16016-3S
Do ya'll think that the MGM 16016-3S can handle 6S LiPo? It's rated for 16 cells or 5S LiPo (21 volts). I can't imagine that the extra 4.2 would kill it...Hell, the MM is only "rated" for 3S, but it handles 5S...What do ya'll think?
|
I wouldn't chance a six month repair.
|
I don't think nickel cells recover much over 1.3-1.35v per cell after the first pull of the trigger. Lipos will continue to rebound to 4v per cell for some time.
going by that... 16 cells = 21-22v idle volts... and 16-19v under load 6s lipo = 24v idle volts... and 19-21v under load |
I personally don't want to take the risk.
You could get a Warrior 12020 instead. |
Quote:
MGM16024 is better. However, if, God forbids, you got a new controller, squee, and it blew up like the rest, what does this say? |
Well, no worries about it now...I didn't end up getting it. I'm just gonna get Hippies MM for now, and run it on a 7XL in the Revo until I can afford the MGM 9032 for the BPP LSP. I might run 4S2P configuration using 10000mah cells in the Revo. :D 3 hour runtime, here we come. :)
|
isn't a 6 cell li-po only 22.2 volts? I would not think that it would kill it but I still would ask Mike before I thought about it again.
|
20000mah.. wow.. You might need to replace the motors bearings before the battery dumps! ;) :D
|
Quote:
|
More than likely, that rating is based on (very common) 25V components. Teh highest I've seen NIMH cells charge to is 1.45V/cell, which still puts it below 25V. 6S is just over that.
The thing with the MMax is that it seemed to have also used common 25V components, so bumping up from 12 cells to even 16 doesn't put things over spec. The MGM would handle the increased amp load with more headroom tho. 6s A123 would be ok IMO, but 6s Lipo would be asking for it. It may live for a while, but you may get a much reduced lifespan. With the wait and expense, its not as good of platform to experiment on as the MM. |
| All times are GMT -4. The time now is 02:04 PM. |
Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2025, vBulletin Solutions Inc.