Larry,

I had the same thing happen to me a few days ago. I was just finishing a flight (just over the top finishing the clover leaf). I landed safely and then carefully inspected and tested everything before flying again. I also checked the esc flight log, and nothing there suggested anything went wrong....but something did. Finally, I came across a post on this forum suggesting that the IceLite series of esc's from Castle sometimes fault and shut down when the current limit shut down was set to "sensitive." I believe "sensitive" is 50 amps, and I know I never drew that much current (if the Castle log can be trusted).

I lost a motor and esc last summer due to lines hooking the grass on takeoff and subsequent attempt at lawn mowing by the E25 and 12/6.5wep. Wanting to avoid another costly episode, I changed the over current setting from Normal to "sensitive." I had flown MANY flights after setting it to sensitive, without incident, so I was reluctant to accept that as the cause of my intermittent fault. Anyway, unable to find anything wrong, I crossed my fingers, I reset the esc to "Normal" sensitivity, and all has been well since (about 30 flights now). If you exhaust all other possibilities (broken wire, bad battery pack, bad connector, etc.) you might want to consider this.

Bob

Hi Larry,

More details about your settings would be helpful.

One thing comes to mind, do you have the Auto-Lipo Volts/Cell set above 3.2 volts? If this is set too high you may save your battery at the expense of losing your plane. I assume you are using the Governor mode and if the ESC thinks your battery is too low, it will go into reduced power to allow you to land safely and shut down. This assumes that you are flying a helicopter and do not want to suddenly drop from the sky.The extra demand of the wing-over could trigger the reduced power. I my earlier E-control line days I once set the cutoff at 3.5 volts and had the pleasure of trying to stay aloft with reduced power until the timer finally ended the flight.     

The problem with my idea is that, if the above is what happened, why didn't it happen repeatedly on other wing-overs etc.?

I know Hubin timers appears to be the timer of choice but it seem to me that the KR timer is a better choice.  It has built in prop strike protection and will operate a dumb (cheep) speed controller.  It also will work with an expensive controller with the ESC rpm set mode turned off.  With this setup you will still have data logging.  Seems like a much better (safer) setup.  I also like the fact that it is field programable without a computer.  I am a new commer to electric stunt so I may be missing something here but so far I love my KR timer driving a $30 speed controller.

       

Thanks Phil.  I will check the timer.  Mike & I got in 4 flights in at NAS with no problems, it was nice