![]() |
MRC 989 problem.
Hi all,
I have a problem with my 989 charger. My charger works fine for 4S lipos but when I connect a 5S lipo it always says that the voltage is too high and it reads 39.06V. I have tried with a friends 989 and it works fine with his. It seems as if the voltage reader is broken but it works for 4S? Has anyone had this problem? /Håkan |
That's a weird problem Hakan;
Did you measured the voltage on the pack? Does it immediately give this error or is it after a little bit of charging? you could try your friends powersupply. |
Did you make sure all the setting are correct? It may seem obvious, but you may have missed one important setting for a 5 cell...
|
There is a mode before you start the actuall charging that measures the voltage on the pack. This works for my 4S but as soon as i plug in my 5S it reads 39.06V.
The 5S pack is ok I can charge it in another charger. Its really weird I thought that maybe someone else had seen this problem... /Håkan |
Quote:
I use a MRC 989 for just about everything I charge. I have alot of different rechargeable things around the house too. I made a connector harness for my charger that has just about every type of connector on it that you can imagine. Some of the connectors, such as "M" style won't carry alot of current and sometimes don't make a good connection every time. I get the same type of behavior when I have a bad connection. It will read the voltage, then apply the charging current. If the connection is too "Loose" to carry the charging amperage, mine behaves exactly like what you just described. I then have to reset by powering down the power supply and start over. By establishing a better connection, it will charge. I bet you have a weak connection somewhere. It could be where the harness plugs into the side of the charger. Check it out :yes: |
Quote:
|
Strange problem, the lipo shouldn't be that high. That is the max voltage of the 989 output.
|
| All times are GMT -4. The time now is 10:48 AM. |
Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2025, vBulletin Solutions Inc.