I got my new Aurora 90 today and appears that BLHeli configurator bricked it.   

When I attempted to flash to the latest version, it started the update and failed on all of the ESC's.   Now it won't even read the ESC's.   Luckily I thought I have a spare 6A 4 in 1 esc, it was pretty old and running 16.4 firmware.

So I pulled apart the aurora and put the new ESC on, went to flash and just tried to do each individually.   ESC 1 is toast!   Flash Failed...   It can still be seen but I cannot flash it.   Fails everytime, and now it doesn't work anymore. 

I have tried everything, is there a way to fix a flash failed esc?   

Also getting a bunch of errors in BLHeli Configurator.   

Here is a callstack where it failed in BLHeli Configurator...

sending cmd_DeviceRead 980 128
received cmd_DeviceRead ACK_D_GENERAL_ERROR 980 0
received cmd_DeviceRead ACK_D_GENERAL_ERROR 980 0
ESC 1: flashing <span style="color: red">failed</span> - <strong>Error: cmd_DeviceRead ACK_D_GENERAL_ERROR
    at recvCallback (chrome-extension://mejfjggmbnocnfibbibmoogocnjbcjnk/js/_4way_if.js:198:37)
    at chrome-extension://mejfjggmbnocnfibbibmoogocnjbcjnk/js/_4way_if.js:296:29
    at Array.forEach (native)
    at Object.onread (chrome-extension://mejfjggmbnocnfibbibmoogocnjbcjnk/js/_4way_if.js:278:18)
    at read_serial (chrome-extension://mejfjggmbnocnfibbibmoogocnjbcjnk/js/serial_backend.js:234:15)
    at EventImpl.dispatchToListener (extensions::event_bindings:388:22)
    at Event.publicClassPrototype.(anonymous function) [as dispatchToListener] (extensions::utils:149:26)
    at EventImpl.dispatch_ (extensions::event_bindings:372:35)
    at dispatchArgs (extensions::event_bindings:244:26)
    at dispatchEvent (extensions::event_bindings:253:7)</strong>

You should provide full log, not the last lines from it. Regarding your 4in1 ESC, only way to recover it is using an Arduino.

I don't have an Aurora90 kit and neither do have spare $100 to get one, therefore I can't debug this issue.

Something is up with it's FC, ESCs, or both. It has real high failure rate unlike other quads.

(04-Mar-2017, 01:07 PM)AndreyM Wrote: You should provide full log, not the last lines from it. Regarding your 4in1 ESC, only way to recover it is using an Arduino.

I don't have an Aurora90 kit and neither do have spare $100 to get one, therefore I can't debug this issue.

Something is up with it's FC, ESCs, or both. It has real high failure rate unlike other quads.

How can I hook an arduino to the 4 in 1 esc?   I found some tutorials but all of them are for individual esc's and using plugs.   I am assuming I would have to solder some wires from the arduino to the esc?   

Also can I use an arduino nano?   Any help would be greatly appreciated.

You can use a Nano. 4in1 ESCs are just what the name suggests, four separate ESCs on one PCB. Having never owned the Aurora nor seen any detailed photos of the ESCs I can't help with the location of C2 pads, you'll have to identify them yourself.

Ugh. I appear to have bricked my Aurora ESC as well and would appreciate a little assistance identifying the correct pads if I wanted to try and reflash manually.  It was flying - but would semi randomly death spin like crazy (during flips / or hitting something) - one motor was reversed with BLHeli and I was trying to update and undo that as some mentioned that caused issues.  Going from BLHeli 16.5 to 16.6.  I was trying to update the ESC's to the latest BLheli when it just lost communication with one ESC. Interestingly, the one it lost was the one that had a reverse motor orientation.  I don't have a Nano - ... only USBAsp and an FTDI (can i just flash the prop hex file with an FTDI?), which I doubt can resolve the issue? I guess I could get a nano, but maybe it's not worth it .... are these photos sufficient for help in identifying the correct pads (taken from another one that I have ...)

BLHeliSuite Error:


Side 1 (traces):

Side 2 (names):

Side 2 (traces):

Side 2 (names):

Or is this correct / do you even think this issue can be resolved with reflashing or is this thing just borked?

I seem to be able to connect via BLHeli Configurator with the Chrome app - but no joy on the normal configurator. It just sits on the "Power esc's or cycle power" or whatever.

I tried to do mine with a arduino nano and was never successful.  I tried those pads you have identified in every possible configuration and BLHeli Suite never found it.   So as of now this is just sitting in a drawer in my garage, soon will probably throw it out and chalk it up to 40 wasted dollars, since thats what a replacement cost.   

I just assumed since BLHeli Configurator works like a charm for everything else I have had it would of with this, also I had seen someone else somewhere mentioning that it's impossibly for BLHeli configurator to brick them.   But appears thats not true.  

(19-Mar-2017, 09:17 PM)jlgaustin Wrote: I tried to do mine with a arduino nano and was never successful.  I tried those pads you have identified in every possible configuration and BLHeli Suite never found it.   So as of now this is just sitting in a drawer in my garage, soon will probably throw it out and chalk it up to 40 wasted dollars, since thats what a replacement cost.   

I just assumed since BLHeli Configurator works like a charm for everything else I have had it would of with this, also I had seen someone else somewhere mentioning that it's impossibly for BLHeli configurator to brick them.   But appears thats not true.  

Darn. Well thanks for the followup! - I wonder if people are just distinguishing between BRICKING and FRYING. I'm leaning towards the possibility that this thing has fried itself somehow which is indeed different from bricking.  Whether or not it's the FC or ESC that's responsible - I don't know.

The more I read about the Aurora / anything using the minicube - the more reports I'm seeing of glitches and deathrolls like crazy (just like mine did). So, now I'm thinking is just bad. Ugh. What a waste of time and money.

Thanks again for your follow up. Appreciated.

---

Oh, quick question: So you're using the Aurora FC / Minicube FC? And it's working ok with new ESCs?

So FWIW I was able to get this sorted. The diagram above is correct.

I soldered up to it and connected it to an Arduino Nano (connecting the knock off Arduino Nano was the hardest part - the University's electronics vending machine sells knock off arduino's for like $3) Didn't know they were knock offs and needed a weird driver (http://www.wch.cn/download/CH341SER_ZIP.html)


I followed this tutorial and the information here from AndreyM.  No fault against him. I've done this before - I got so fixated on the C2D and C2K ports that I almost forgot to attach the ground.  This is the second time (fool me once) I've taken someone very literally when they say "you only need to connect two pins.. etc..." when you really need to connect 3 (including ground).  This isn't me complaining! I'm very grateful for the advice - I'm just a noob and am putting this out there for anyone that's as nooby as me and doesn't realize the obvious.  I just soldered a wire to the GND on the battery pads.  Jammed the pins into the nano, plugged in the battery, and connected right up to BLHeli.  Side Note: I think this FC is browning out occasionally and probably did that during the upgrade causing the "bricking" (not really bricked though in my case).

But it was pretty easy. BLHeli didn't see it as having any real issues.  It actually recognized the ESC's old software just fine - but after installing the latest BLHeli, betaflight was able to control the ESC and motor again and the passthrough works again.

Interface method was SiLabs C2 (4way-if)

Too bad you didn't take a flash dump so we could know how it looked after being "bricked".

(21-Mar-2017, 10:34 PM)AndreyM Wrote: Too bad you didn't take a flash dump so we could know how it looked after being "bricked".

oh sorry   i would've had I known it could've been helpful.
I know "bricked" was the wrong word - but it summed up the state of affairs nicely. Flashing ESC's is pretty new to me and I didn't really know about this method of reviving them.

It was very weird. When connected through the passthrough to the chrome app or blheli it threw errors as shown above. But as soon as I connected to a single ESC - it appeared to recognize everything as if there was no problem at all. It read all settings, firmware version, etc... no "locked" messages or unrecognized anything. Just voila.  I had flashed the others to a new firmware - so I just kinda ignored the seeming "it just works" of it all and flashed 16.6, disconnected. And connected to BF to spool up the motors and try the passthrough. Tried changing some settings, too.

Everything was fine.

I did, however, remove everything from the FC. No RX, no VTX.  Like I said, it's have a really hard time when it's loaded up - I'm guessing a little change in power was enough to take the board out at a critical time during an update.  After a hard maneuver it just spazzes out (notice the OSD cuts out, too - and it doesn't just die ... it goes full power on certain motors):



here's AndyRC's restting out with a full load:

https://youtu.be/Qzyl4DWR0zk?t=23m48s

Hi,
I had this or at least a very similar problem (flashing 16.6 failed which left the ESC unusable), I was using the normal (not Chrome version) BLHeli suite app.
After many attempts the ESC would not respond, I could not read it or flash it and "u" appeared in the ESC 1 and 2 windows.
My fix was to:
- Download the Chrome version of BLheli suite and use that instead of the normal app
- As per the instruction manual for the 4in1 esc I changed the COM port to no. 255 (I found this on the BangGood website)
- Re-started my PC and quad
- Disconnect the camera
- Connected the battery and PC (my FC board is V1.1) to the FC board
- Connect to the board using the Chrome version of BLHeli suite
- Followed the instructions and Flashed BLHeli 16.6 (F-H-40)
This did take several attempts but it eventually worked and flashed the ESCs.
I hope this helps someone, it saved me taking the unit apart and trying to solder to the back of the ESC etc.
If you are reading this because your ESC stopped communicating then good luck,
David

This could be moved to electronics problem would help people to find it much easier.

I do have similar issue with my one ESC 3 not detected and took me forever to find this on google

Regards