Quote:
Originally Posted by Pdelcast
And for those who are interested...
We've been struggling with whether or not to release a version of software that actually measures voltage ripple, and limits performance based on how the batteries perform.
On one hand, it would prevent a lot of damaged ESCs, and batteries -- when users are pushing batteries insufficient for the application.
BUT, on the other hand, a lot of people who are running "marginal" systems will see a performance decrease, and might yell "FOUL!" at us for releasing software that would actually lower the performance of their system.
As it is, very few controllers actually get damaged by ripple voltage/current -- but the people who damage controllers this way don't just do it once and then learn a lesson. They tend to destroy controller after controller with the same bad setups. And then they blame US for making a defective product.
Brian, and others, I'd be interested in hearing your thoughts on this...
|
Yes, I'd definitely like this. And I'm sure it would help reduce warranty claims (and lost revenues on your end). Just be prepared to increase manpower on your tech support lines because I have a feeling there will be an influx of calls!
Seriously though, this IS a great idea!
One more suggestion; when the ESC limits performance because of ripple, have the LEDs blink some kind of error code so the user knows what to watch out for. And while you're at it, add similar error codes for temperature extremes, and any other condition you can measure. These codes should "latch" so that the code remains (even if the condition goes away) until the ESC is unplugged. It would be like a car's CEL.
And while you're in a receptive mood for suggestions, here is another thread to ponder over:
http://www.rc-monster.com/forum/showthread.php?t=18832 After all, gotta give your firmware developer something to do!
