stunthanger.com

Electric Stunt => ESC Settings => Topic started by: Horby on April 08, 2015, 07:16:34 PM

Title: Huban or esc issue
Post by: Horby on April 08, 2015, 07:16:34 PM
I am throwing this out there for a friend who is using the Castle esc's and Huban timers.
Last year he had one of his planes mysteriously over run on time and wreck expensive batteries because the esc or the timer did not shut things down in time. He ended up trying new batteries and the problem went away. Over the week end it happened to him again but with a differen plane but the exact same issue and puffed up his battery good. Both planes are using the same type esc and timer and now a second plane fell victom to the over run. Can any one shed some light on this? Has any one else using Castle esc with Huban timers run into this before?

Warren
Title: Re: Huban or esc issue
Post by: Tim Wescott on April 08, 2015, 09:37:51 PM
He should describe the problem to Will Hubin.  If this was an ESC issue I think there'd be screaming from all the RC guys about their ESC getting stuck.

He could always swap out the timer or the ESC and try again -- granted, the fact that the problem only happens occasionally makes it hard to know if it's really been fixed.
Title: Re: Huban or esc issue
Post by: Crist Rigotti on April 09, 2015, 08:02:55 AM
What are his ESC settings?  There is a low voltage cutoff in the ESC that can be set to prevent this thing from ever happening regardless of what the timer is doing.  My guess your friend needs to revisit his ESC settings or post a detailed list of his settings.  I'm thinking that the Low Voltage cutoff is set to a "Soft" cutout and not a hard one and his set point is too low like maybe 3 volts?  Should be higher like 3.2 or so.
Title: Re: Huban or esc issue
Post by: John Cralley on April 09, 2015, 02:42:33 PM
 What Crist says. Need details! What were the ESC settings? Which Hubin timer was he using and what were the timer settings? What batteries were being used and how deep were they normally being discharged?

As Crist suggests deep discharge of the batteries with too low a cutoff voltage setting in the ESC could give such a scenario.
Title: Re: Huban or esc issue
Post by: Horby on April 09, 2015, 09:05:08 PM
I am going to try and get him to chime in on this. In further discussions, I think he does not have the LVC set high enough.
But it doesent solve the over run on time. Does the Huban require a min voltage?

Warren
Title: Re: Huban or esc issue
Post by: Tim Wescott on April 09, 2015, 11:12:36 PM
Assuming that the ESC isn't broken, if you're using more than one cell the timer will get a steady five volts.
Title: Re: Huban or esc issue
Post by: Crist Rigotti on April 10, 2015, 09:18:28 AM
Not to nick-pick but it is Hubin not Huban.
Title: Re: Huban or esc issue
Post by: John Cralley on April 10, 2015, 11:27:01 AM
Will Hubin makes a number of timers many have the duration of the flight time set with a screwdriver (adjusting a small potentiometer).

 I suppose that the duration might accidentally changed to increase the flight time and over discharge the battery. This does seem unlikely but just possible.
Title: Re: Huban or esc issue
Post by: Horby on April 11, 2015, 11:29:48 AM
Not to nick-pick but it is Hubin not Huban.

No doubt aboot it, must be my Canadian accent coming through. Lol
Title: Re: Huban or esc issue
Post by: Crist Rigotti on April 11, 2015, 12:36:09 PM
No doubt aboot it, must be my Canadian accent coming through. Lol

LOL!
Title: Re: Huban or esc issue
Post by: Will Davis on April 15, 2015, 05:30:19 PM
Warren,

If your friend logged the data with the esc, it will tell what  data was going into and out of the esc, it will show if the esc  or the timer  were  working properly

I use the fm9 timer  and castle esc with no problems
Title: Re: Huban or esc issue
Post by: Crist Rigotti on April 16, 2015, 11:41:42 PM
Any news?
Title: Re: Huban or esc issue
Post by: Will Hubin on May 11, 2015, 08:29:12 PM
I have tested my timers to voltages down to 2.5 volts and they still work properly, so a low (BEC) voltage would not account for a longer flight time than programmed. The flight time is determined by an internal clock what counts time based on a 50 Hz interrupt, and this is always within a percent or so of exact. A flight time malfunction is about the last thing I would expect, but I would appreciate further details on the timer and the equipment.