Thanks Kevin,

I rolled mine back to v3.2 (I was using Castle Link v3.26 and esc firmware 3.24 beta (or it may have been 3.23, whatever the latest beta version available). However, it may have been too late for my brand new controller. I went out this evening to test fly the new controller setup and after 4 flights it fried. I put my old one back in (the one that reset the settings) and it worked fine.

I am a bit frustrated right now. I have lost two HV85's in the span of 3 days. If it is bad firmware (not sure how that could be) then Castle owes me 2 new controllers. It seems that the controllers blew up on arming. I had just flown and let things cool down. It was hot out, about 98F. I checked the temps after each flight and the highest temp that the heat sink on the ESC was 127F. That was immediately after one flight with a lot of verticals. The other flights were at 120-123F. Certainly not hot enough to be causing any damage. The motor was running fine as I taxied back in and shut it down. Upon arming for the next flight, I got no response from the ESC. That is exactly what happened to my second unit.

I brought it home, rechecked the settings, reprogrammed it, redownloaded settings and it was indeed dead.

As a precaution I rolled my only remaining HV85 back to v3.2. I hope it holds. I'm really trying to make it to the Miramar contest this weekend but I am not very confident that this thing will last.

I'm not a happy camper right now.

Steve