Posts: 304 Threads: 45 Likes Received: 55 in 46 posts Likes Given: 10 Joined: Aug 2020 Reputation: 2 Hi all. Day 2 of my quad experience and it's dead  I'm trying to troubleshoot but I can't find any suitable manual for the FC (GEP-12A-F4 AIO - came with Thinking P16). I can get a wiring diagram but that is all. If I power it up, I get the usual sounds (da-da-da------daa---daaaa) but no response to TX and motors don't spin on armed. RX is showing a green light and I can see a link from the TX. FC is showing 3 LED's, a red, green and blue, but I can't find anything to what they indicate. Reason I think it's the FC is that I had it plugged into pc for betaflight. While doing that I was setting up my OSD and so had to power it up from battery for the DJI Vista to operate. But I didn't unplug it for some time and when looking into the goggles there was a temperature warning. I powered down quickly and let it cool. However, when connecting to pc again, the drivers wouldn't load and the FC was unrecognised. I was toubleshooting driver issues for about an hour when I thought I'd just check and noticed it doesn't respond at all. So, have I fried the FC due to leaving plugged in? Can anyone provide me some guidance on the LED's or easy way to isolate the problem? Thanks Alan ![[-]](https://intofpv.com/images/collapse.png) • Posts: 21,218 Threads: 583 Likes Received: 8,948 in 6,622 posts Likes Given: 1,425 Joined: Jun 2018 Reputation: 786 02-Sep-2020, 01:35 PM (This post was last modified: 02-Sep-2020, 01:41 PM by SnowLeopardFPV.) If you're getting all 5 motor sounds on startup then the FC must be working because the last two tones indicate a valid throttle signal from the MCU on the FC. The temperature warning would likely have been from the Vista and not the FC. The Vista Units have known issues with overheating. As far as I'm aware, the MCU overheat warning for the FC isn't one of the warning elements that the DJI goggles are currently capable of displaying.
Are you currently getting any LED activity at all from the FC, or nothing whatsoever? • Posts: 304 Threads: 45 Likes Received: 55 in 46 posts Likes Given: 10 Joined: Aug 2020 Reputation: 2 02-Sep-2020, 01:44 PM (This post was last modified: 02-Sep-2020, 01:44 PM by AlanB1976.) Yeah, I get a green, blue and red ones light up. Colour me confused.
Picture attached. The green and blue are right next to each other so you can't see on the pic (green one is small)
edit: my pics aren't attaching so can't show you now, sorry. • Posts: 21,218 Threads: 583 Likes Received: 8,948 in 6,622 posts Likes Given: 1,425 Joined: Jun 2018 Reputation: 786 The green and blue LEDs will be firmware status LEDs. Is the blue one blinking?
The red LED indicates power on the 3.3V rail which the MCU needs to function.
So the FC as a whole isn't dead. Are you able to connect to the FC from Betaflight Configurator? • Posts: 304 Threads: 45 Likes Received: 55 in 46 posts Likes Given: 10 Joined: Aug 2020 Reputation: 2 02-Sep-2020, 01:59 PM (This post was last modified: 02-Sep-2020, 02:00 PM by AlanB1976.) Ok, weird. The thread shows "closed" to me yet if I click on it I can still reply.
So just repeating what I PM'ed SnowLeopard with in case anyone else out there has had this issue.
LED's are constant.
No connectivity to betaflight as PC not recognising the device anymore and not loading drivers. I've tried all the recomended tricks (e.g. zadig) but none working • Posts: 21,218 Threads: 583 Likes Received: 8,948 in 6,622 posts Likes Given: 1,425 Joined: Jun 2018 Reputation: 786 Did you try the ImpulseRC Driver Fixer from the following web page? https://impulserc.com/pages/downloads • Posts: 304 Threads: 45 Likes Received: 55 in 46 posts Likes Given: 10 Joined: Aug 2020 Reputation: 2 Yeah. Just gets stuck with trying to find the FC • Posts: 21,218 Threads: 583 Likes Received: 8,948 in 6,622 posts Likes Given: 1,425 Joined: Jun 2018 Reputation: 786 Try and get into bootloader mode by holding down the boot button on the FC and plugging in the USB cable and see if the port in Betaflight Configurator then shows "DFU" as the port. • Posts: 304 Threads: 45 Likes Received: 55 in 46 posts Likes Given: 10 Joined: Aug 2020 Reputation: 2 Yeah. That works. Does that mean I'll have to flash it to recover? • Posts: 21,218 Threads: 583 Likes Received: 8,948 in 6,622 posts Likes Given: 1,425 Joined: Jun 2018 Reputation: 786 Yes, just re-flash the firmware. It sounds like you might have corrupt firmware on the FC. Make sure you also switch on the "Full chip erase" option before you do the re-flash. • Posts: 304 Threads: 45 Likes Received: 55 in 46 posts Likes Given: 10 Joined: Aug 2020 Reputation: 2 Thanks for the help!  Just a quick question, as I can't seem to find the exact board specs (model description says the GEP-12A-F4 AIO but pictures of that one online show differently, and Betaflight doesn't list that model directly), would there be an issue if I flashed the wrong board or would just mean I need to go and flash the correct one after? • Posts: 21,218 Threads: 583 Likes Received: 8,948 in 6,622 posts Likes Given: 1,425 Joined: Jun 2018 Reputation: 786 Flashing the wrong target doesn't usually cause any damage. It just won't work. I think I have exactly the same board. If you post a picture of yours I can see if it's the same as mine and then check the actual target for you. • Posts: 304 Threads: 45 Likes Received: 55 in 46 posts Likes Given: 10 Joined: Aug 2020 Reputation: 2  02-Sep-2020, 03:08 PM Finally I managed to get an image attached ![[Image: 74DT4ZEl.jpg]](https://i.imgur.com/74DT4ZEl.jpg) • Posts: 21,218 Threads: 583 Likes Received: 8,948 in 6,622 posts Likes Given: 1,425 Joined: Jun 2018 Reputation: 786 Yes, it's the same FC as I have. You need to use the GEPRCF411 Betaflight target. • Posts: 304 Threads: 45 Likes Received: 55 in 46 posts Likes Given: 10 Joined: Aug 2020 Reputation: 2 Great, thanks for your time on this. Let me give that a go now (not that I've done much work the entire day).
Now to learn Betaflight setup ... • |
