Well I probably shouldn't even admit this, but I smoked my FC (Naze 32 Full Rev6)  I had everything hooked up and had flashed it with cleanflight and then I unplugged everything and removed it (don't remember to do what).  Anyway...plugged everything back up and when I plugged the battery back in......POOF!  Damn Damn Damn.  As best I can tell I think I reversed the polarity on the Vbat hook up (I was in a hurry, it was late, dtc. all the usual excuses).  Once I replaced some wires and made SURE I had the polarity right, I plugged it in again.  All the lights come on and the green light flashes about once a second (I don't remember if it did that before or not), but when I plug it into cleanflight it starts doing some weird stuff.  For instance, if I change some settings and tell it to save and reboot, it appears to do everything right, except the sliders on that page all return to their default positions.  When I try to spin the motors over they spin.....as long as my cursor is moving the slider for that motor.  As soon as I stop moving it, the motor stops.  My guess is that I fried the memory chip...just a guess.

Anyway...."damn the torpedoes, full speed ahead".......I've got another one on the way. : )

Ok.....well, now I am not sure I actually fried the FC. My new one is acting the same way. It comes on and after it goes through it's bootup and calibration routines, I have one blue light on steady and the green one is flashing....usually at one second intervals, but sometimes it varies. After much research, I think I may have a failsafe issue. I could not remember what I set the Min and max throttle values to in the ESC's which I tried to read them via clean flight (which I have flashed onto the new Naze32). I had originally flashed the ESC's (Rotergeeks 20A) with BLHeli using SILABS. When I go to read these, it lets me know that it found 4 ESC's, but does not specify SILABS or ATMEL. When I hit "OK", it immediately gives me a com port error (says it can't find the port if I recall) and does not read anything. Seems to me that it has already found the port if it got t hat far to begin with. If anyone has any ideas on this, I would greatly appreciate the help, as I am about to fire this whole mess into the garbage can......(not really). It's not a crime to be stupid, but it sure is inconvenient (and expensive). Thanks All.

so just to clarify, you are trying to flash 4 x RG20A ESC via passthrough ? (via Cleanflight option in the BLHeliSuite)?

RG20A ESC should come with BLHeli Bootloader, so that should work... alternatively does it work with a programmer rotorgeek provides?

I originally programmed it with the programmer that rotorgeeks provided and had no problems. I was just trying to read the ESC,s via Cleanflight as I could not remember where I had set the Min and max throttle values (I know....should have saved the setups). I thought I might be getting a conflict based on the failsafe values set in cleanflight, causing the LED to flash? IDK......obviously in over my head here. The ESC's work because when I go to be motor tabs as long as I am moving the tab in the cleanflight interface, the motors spin. As soon as I stop moving the motor tab the motor stops.....I'm wondering if that is a manifestation of some kind of conflict with the failsafe values too. Sorry for rambling...it's how my brain works....

---

Follow up......I have not tried again with the rotorgeeks programmer because of course I cut the signal leads and soldered them directly to the PDB thinking I could use the FC via cleanflight to do it from then on. I would have to desolder the signal leads from the PDB...which I can do....I'm was just trying to avoid that if I can.

I THINK I figured it out. It's not a problem with the FC or the ESC's. I've got a problem with windows. The error message was a bit ccritic and although it said to check the connection to the flight controler, it didn't say exactly what was wrong. Upon a little investigation, I found that I am getting an "access denied" error on COM port5. I am not sure why this is happening, but I am hoping that logging in as admistrator will fix that ...at least temporarly. I'll check it out as soon as I have a chance. : )

(29-Mar-2016, 02:18 AM)sirdude Wrote: I THINK I figured it out.  It's not a problem with the FC or the ESC's.  I've got a problem with windows.  The error message was a bit ccritic and although it said to check the connection to the flight controler, it didn't say exactly what was wrong.  Upon a little investigation, I found that  I am getting an "access denied" error on COM port5.  I am not sure why this is happening, but I am hoping that logging in as admistrator will fix that ...at least temporarly.   I'll check it out as soon as I have a chance. : )

Damn you Microsoft !

What Biggles said. That was it. I still had a little trouble even as admin getting the damn thing to see COM 5, but after "fiddling" with it a bit, it worked. All is currently well in fiasco land. Also I figured out that I don't think there is anything wrong with the FC I thought I had fried....it appears to work perfectly. Hmmmm......well with another FC just laying around, it only makes sense that I will HAVE to build another one after I am finished with this one.....at least that'll be my argument with the wife............. Thanks Oscar and Biggles, I really appreciated the input! : )

(29-Mar-2016, 12:40 PM)sirdude Wrote: What Biggles said.   That was it.  I still had a little trouble even as admin getting the damn thing to see COM 5, but after "fiddling" with it a bit, it worked.  All is currently well in fiasco land.  Also I figured out that I don't think there is anything wrong with the FC I thought I had fried....it appears to work perfectly.   Hmmmm......well with another FC just laying around, it only makes sense that I will HAVE to build another one after I am finished with this one.....at least that'll be my argument with the wife.............  Thanks Oscar and Biggles, I really appreciated the input! : )

Really glad to hear you at least found out what the problem was, and the upside is, as you said..another build has to happen now, You just cannot have a FC just laying around doing nothing.

Yes...that would just be criminal!! : )