by StuartL » Fri May 02, 2008 7:30 am
by StuartL
Fri May 02, 2008 7:30 am
tom_chang79 wrote:StuartL wrote:Seems that the NiMHs have finally given up. One of the packs just turned into a furnace and seriously melted the CM-5 case. The CM-5 PCB and top part of the case appears to be unaffected but the bottom part is completely distorted and the battery is, of course, a write off.
StuartL, was there any indication of a failure before it turned into a furnace?
Well, there was a smell and a fizzing...
I'm sure that there was a drastic temperature increase but at the time I was out and Matt was making tea, so he heard the fizzing and came running.
I'm a little alarmed from your experience...
So am I. Matt is still shocked nearly a week later. He's got visions of his house burning down. While that's an excessive reaction it does illustrate the point.
Also, how long have you had the Bioloid and what is your rough estimate of how often you charged the stock NiMH battery pack?
Ok, I'm a slack geek. I bought the Bioloids for RoboGames 2007 but missed the actual games with them (they were on a plane somewhere). Around that time I probably spent a while using the Bioloid charging mechanism (i.e. Bioloid firmware and manually starting the charging) and then, because I started writing the library, I started running off the PSU.
In hindsight I think that there's a fair chance that one of the bugs in example.c that I duplicated in my library was to turn the charging circuit on permanently on startup. Over the few weeks I developed last year this probably caused a degree of over-charging.
The Bioloids were then relegated to project back-burner while other projects took my attention (anyone say ADD? Oooh look! Shiny!). This year they've been developed in anger and Matt has taken on one of the kits which I converted into a snake. He's been mucking around with it for a few months and certainly for a part of that the charging bug still existed.
As per this and the other thread I spotted this bug and worked on a proper charging algorithm. I believe the algorithm is largely fine but undoubtedly has the same problem as the Robotis one, which is that the resolution of the ADC doesn't allow accurate end-of-charge detection.
I do not know how Robotis have done their end-of-charge detection (timer, delta-peak, current monitoring) but I'm guessing they undercharge the pack sacrificing battery life for safety. I was unaware of such concerns so I concentrated on getting the pack fully charged.
I think between the development last year, the bug in example.c and the constant PSU running this year for snake development the pack was slowly destroyed by overcharging, and eventually had nothing to burn off except itself.
I suspect from circumstantial evidence that the Robotis charging algorithm doesn't have this problem because it just under-charges the pack instead, hence the 8-15 minute run times people are getting. With charged 2.3Ah NiMH cells a Humanoid should easily run for an hour, maybe even more.
tom_chang79 wrote:StuartL wrote:Seems that the NiMHs have finally given up. One of the packs just turned into a furnace and seriously melted the CM-5 case. The CM-5 PCB and top part of the case appears to be unaffected but the bottom part is completely distorted and the battery is, of course, a write off.
StuartL, was there any indication of a failure before it turned into a furnace?
Well, there was a smell and a fizzing...
I'm sure that there was a drastic temperature increase but at the time I was out and Matt was making tea, so he heard the fizzing and came running.
I'm a little alarmed from your experience...
So am I. Matt is still shocked nearly a week later. He's got visions of his house burning down. While that's an excessive reaction it does illustrate the point.
Also, how long have you had the Bioloid and what is your rough estimate of how often you charged the stock NiMH battery pack?
Ok, I'm a slack geek. I bought the Bioloids for RoboGames 2007 but missed the actual games with them (they were on a plane somewhere). Around that time I probably spent a while using the Bioloid charging mechanism (i.e. Bioloid firmware and manually starting the charging) and then, because I started writing the library, I started running off the PSU.
In hindsight I think that there's a fair chance that one of the bugs in example.c that I duplicated in my library was to turn the charging circuit on permanently on startup. Over the few weeks I developed last year this probably caused a degree of over-charging.
The Bioloids were then relegated to project back-burner while other projects took my attention (anyone say ADD? Oooh look! Shiny!). This year they've been developed in anger and Matt has taken on one of the kits which I converted into a snake. He's been mucking around with it for a few months and certainly for a part of that the charging bug still existed.
As per this and the other thread I spotted this bug and worked on a proper charging algorithm. I believe the algorithm is largely fine but undoubtedly has the same problem as the Robotis one, which is that the resolution of the ADC doesn't allow accurate end-of-charge detection.
I do not know how Robotis have done their end-of-charge detection (timer, delta-peak, current monitoring) but I'm guessing they undercharge the pack sacrificing battery life for safety. I was unaware of such concerns so I concentrated on getting the pack fully charged.
I think between the development last year, the bug in example.c and the constant PSU running this year for snake development the pack was slowly destroyed by overcharging, and eventually had nothing to burn off except itself.
I suspect from circumstantial evidence that the Robotis charging algorithm doesn't have this problem because it just under-charges the pack instead, hence the 8-15 minute run times people are getting. With charged 2.3Ah NiMH cells a Humanoid should easily run for an hour, maybe even more.