I just upgraded my ESCs to the Aikon 20A SEFMs.  They were running great and I decided to update the firmware using the BLHELI Configurator.  Here is what I did:
- All seemed to go well when I originally flashed the updates (C_H_20 version 16.x, whatever is the most current version) and reset the ESCs to their Min and Max using BetaFlight / Motror Tab, but after flashing the updated firmware and adjusting the min and max throttle (1020 and 2000) for each ESC, the quad is running rough and then accelerates on its own.  
- I then set the Min and Max throttle back to the original settings (1120 and 1920, that is how they came from Aikon).  I tested again and now one ESCs was really responding until I increased the throttle.  Here is the log from the setup:

2017-05-11 @ 06:02:51 -- Running - OS: MacOS, Chrome: 57.0.2987.133, Configurator: 1.0.13
2017-05-11 @ 06:02:54 -- Serial port successfully opened with ID: 88
2017-05-11 @ 06:02:54 -- MultiWii API version received - 1.31.0
2017-05-11 @ 06:02:54 -- Flight controller info, identifier: BTFL, version: 3.1.7
2017-05-11 @ 06:02:54 -- Running firmware released on: Apr 3 2017 22:27:23
2017-05-11 @ 06:02:54 -- Board: SRF3, version: 0
2017-05-11 @ 06:02:54 -- Unique device ID received - 0x2d002b4334570620393730
2017-05-11 @ 06:02:55 -- Reading setup
2017-05-11 @ 06:02:57 -- Reading setup finished
2017-05-11 @ 06:06:57 -- Writing setup
2017-05-11 @ 06:06:57 -- ESC 1: 112 byte(s) written
2017-05-11 @ 06:06:58 -- ESC 2: 112 byte(s) written
2017-05-11 @ 06:06:59 -- ESC 3: 112 byte(s) written
2017-05-11 @ 06:06:59 -- ESC 4: 112 byte(s) written
2017-05-11 @ 06:07:00 -- Writing setup finished
2017-05-11 @ 06:07:00 -- Reading setup
2017-05-11 @ 06:07:01 -- Reading setup finished
2017-05-11 @ 06:07:04 -- Reading setup
2017-05-11 @ 06:07:06 -- Reading setup finished
2017-05-11 @ 06:07:20 -- Writing setup
2017-05-11 @ 06:07:21 -- ESC 1: no changes
2017-05-11 @ 06:07:21 -- ESC 2: no changes
2017-05-11 @ 06:07:22 -- ESC 3: no changes
2017-05-11 @ 06:07:22 -- ESC 4: 112 byte(s) written  (max throttle was off when I originally changed it.  Change to match other ESCs)
2017-05-11 @ 06:07:23 -- Writing setup finished
2017-05-11 @ 06:07:23 -- Reading setup
2017-05-11 @ 06:07:24 -- Reading setup finished
2017-05-11 @ 06:07:32 -- Reading setup
2017-05-11 @ 06:07:34 -- Reading setup finished
2017-05-11 @ 06:13:43 -- Serial port successfully opened with ID: 92
2017-05-11 @ 06:13:43 -- MultiWii API version received - 1.31.0
2017-05-11 @ 06:13:43 -- Flight controller info, identifier: BTFL, version: 3.1.7
2017-05-11 @ 06:13:43 -- Running firmware released on: Apr 3 2017 22:27:23
2017-05-11 @ 06:13:43 -- Board: SRF3, version: 0
2017-05-11 @ 06:13:43 -- Unique device ID received - 0x2d002b4334570620393730
2017-05-11 @ 06:13:44 -- Reading setup
2017-05-11 @ 06:13:46 -- Reading setup finished
2017-05-11 @ 06:14:49 -- Writing setup
2017-05-11 @ 06:14:50 -- ESC 1: 112 byte(s) written
2017-05-11 @ 06:14:50 -- ESC 2: 112 byte(s) written
2017-05-11 @ 06:14:51 -- ESC 3: 112 byte(s) written
2017-05-11 @ 06:14:52 -- ESC 4: 112 byte(s) written
2017-05-11 @ 06:14:52 -- Writing setup finished
2017-05-11 @ 06:14:52 -- Reading setup


I went back to try re-flashing again, but this is what happened...

Here is the log from when I updated the ESCs:

2017-05-11 @ 06:24:55 -- ESC 2: flashing started
2017-05-11 @ 06:24:56 -- ESC 2: flashing failed - Error: cmd_DevicePageErase 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)
2017-05-11 @ 06:26:40 -- ESC 1: flashing started
2017-05-11 @ 06:26:53 -- Writing setup
2017-05-11 @ 06:26:54 -- ESC 1: 112 byte(s) written
2017-05-11 @ 06:26:54 -- Writing setup finished
2017-05-11 @ 06:26:54 -- ESC 1: flashing finished in 13.997 seconds
2017-05-11 @ 06:26:57 -- Reading setup
2017-05-11 @ 06:26:59 -- Reading setup finished
2017-05-11 @ 06:27:15 -- ESC 2: flashing started
2017-05-11 @ 06:27:29 -- Writing setup
2017-05-11 @ 06:27:30 -- ESC 2: 112 byte(s) written
2017-05-11 @ 06:27:30 -- Writing setup finished
2017-05-11 @ 06:27:30 -- ESC 2: flashing finished in 14.66 seconds
2017-05-11 @ 06:27:54 -- Writing setup
2017-05-11 @ 06:27:55 -- ESC 1: no changes
2017-05-11 @ 06:27:55 -- ESC 2: no changes
2017-05-11 @ 06:27:56 -- ESC 3: no changes
2017-05-11 @ 06:27:56 -- ESC 4: no changes
2017-05-11 @ 06:27:56 -- Writing setup finished
2017-05-11 @ 06:27:56 -- Reading setup
2017-05-11 @ 06:27:58 -- Reading setup finished
2017-05-11 @ 09:18:56 -- Serial port successfully opened with ID: 96

Do you have any idea why the ESCs are running so poorly.  I didn't change anything other than the Max and Min Throttle settings after loading the firmware.   Help!!!!!!!

I ended up replacing the motor (started to fail), re-flashing with the BLHELI Configurator. It was able to get it flying as well as it previously did, but after a few flights, the replaced motor lost power and dropped out of the air. The motor wouldn't start, but after moving the ESC around a bit, it flew again. Until it didn't. Repeated ESC "massage" and it would fly a little more.

Any ideas about what could be causing this with the ESC. Regardless, I am replacing the ESC with a new one. Thanks for any insights.

First, configurator can't cause your motor to run rough or suddenly stop on the air, it either doesn't works at all or spins motor ok, after which point all ESC issues are hardware-related, not software. All this given you've got the "flashing finished" message, if flashing fails like in your case some weird stuff may happen.
Second, the log you've posted is not the right one. Next time you post a log, use "Save Debug Log" button instead of copying random text :-)

Judging by the console output (not log), ESC 2 flashing procedure failed at first attempt but worked ok on the second, that happens sometimes with current BF and we don't really know why. A proper Debug Log could give some clues.

(11-May-2017, 11:07 PM)AndreyM Wrote: First, configurator can't cause your motor to run rough or suddenly stop on the air, it either doesn't works at all or spins motor ok, after which point all ESC issues are hardware-related, not software. All this given you've got the "flashing finished" message, if flashing fails like in your case some weird stuff may happen.
Second, the log you've posted is not the right one. Next time you post a log, use "Save Debug Log" button instead of copying random text :-)

Judging by the console output (not log), ESC 2 flashing procedure failed at first attempt but worked ok on the second, that happens sometimes with current BF and we don't really know why. A proper Debug Log could give some clues.

(11-May-2017, 11:07 PM)AndreyM Wrote: First, configurator can't cause your motor to run rough or suddenly stop on the air, it either doesn't works at all or spins motor ok, after which point all ESC issues are hardware-related, not software. All this given you've got the "flashing finished" message, if flashing fails like in your case some weird stuff may happen.
Second, the log you've posted is not the right one. Next time you post a log, use "Save Debug Log" button instead of copying random text :-)

Judging by the console output (not log), ESC 2 flashing procedure failed at first attempt but worked ok on the second, that happens sometimes with current BF and we don't really know why. A proper Debug Log could give some clues.

Totally agree about the stopping in air thing.  It looks like the ESC has some issue and I am replacing it.  However, the rough running bit happened with 2 sets of ESCs.  Here is the log file from later this afternoon.  Let me know what you think...

(11-May-2017, 11:54 PM)JohnDHoinville Wrote: Totally agree about the stopping in air thing.  It looks like the ESC has some issue and I am replacing it.  However, the rough running bit happened with 2 sets of ESCs.  Here is the log file from later this afternoon.  Let me know what you think...

John, I don't see any log file. Pictures of how you have put your craft together and particularly of how you have mounted the ESCs and how they are connected to power, the flight controller and the motors would be incredibly helpful. As would saying which flight controller and firmware you have.

The more information you can give us, the more people can help.

(12-May-2017, 12:31 AM)unseen Wrote: John, I don't see any log file. Pictures of how you have put your craft together and particularly of how you have mounted the ESCs and how they are connected to power, the flight controller and the motors would be incredibly helpful. As would saying which flight controller and firmware you have.

The more information you can give us, the more people can help.

Betaflight Configuration...

More coming...

(12-May-2017, 12:31 AM)unseen Wrote: John, I don't see any log file. Pictures of how you have put your craft together and particularly of how you have mounted the ESCs and how they are connected to power, the flight controller and the motors would be incredibly helpful. As would saying which flight controller and firmware you have.

The more information you can give us, the more people can help.

It will not allow me to upload a lot of the files.  I have added all of this information and the BLHELI_S Configurator Log file to a Google Drive. Here is the link: https://drive.google.com/drive/folders/0...sp=sharing

This is my first build and I am a nube to Quads this year.  I do understand that some of my build decisions aren't optimal, but I am learning as I go.  Thanks for all of your help.  I really appreciate any help that you can provide.  One final note, the ESC pictured seems to be failing.  I can fly for a while with burst of throttle and LOS flying (certainly not FPVing it with hardware issues).  The weird thing is that after it crashes, the motor will not work.  I will "massage" (rub it back and forth) the ESC and it will work again.   Note, the PIDs and Rates are basically unchanged, since I reset everything to start solving this issue.  Thanks for all your help!
  

Quad Gear:

• Frame: FPV Racing Drone Carbon Fiber Stretch-X Quadcopter Frame QAV-X 210
  
• Motors: 4-Crazepony Cobra 2204 2300KV Brushless Motor / 2s-3s Lipo
  • Soft mounted 3 layers electrical tape
    
• ESCs: 4- AIKON SEFM 20A (BLHELI_S)
  • Soft mounted with foam tape
    
  • BLHELI_S / firmware - C-H-20
    
• Flight Controller: SPRacing
  
• 2.4 Receiver: FrSky XM+ SBUS Mini Receiver
  
• PCB: Lumenier 4Power + Plus PDB (5v/10v Reg, 184A Curr.)
  
• Beeper: random brand
  
• Transmitter: Taranis / X9D Plus
  
• Propellors: Racerstar 5042 5x4.2x3 3 Blade Propeller 5.0mm Mounting Hole
  
• Batteries: Various Tattu 1300 / 3S / 45C - 75C / 
  

FPV Gear:

• OSD: LHI Micro Minimosd Minim OSD Mini OSD
  
• 5.8 GHz Antenna: Bhivorga 2pcs EMAX Pagoda Antenna 5.8G Transmitter Receiver Omnidirectional Omni FPV Flat Panel LHCP SMA Male for RC FPV Racing Drone (White)
  
• Goggles: JJRC JJPRO - F01 FPV Headset Goggles
  
• FPV Camera: Runcam Eagle 800TVL
  
• Transmitter / 5.8 GHz: Eachine TX526 5.8G 40CH 25MW/200MW/600MW Switchable AV Wireless FPV Transmitter RP-SMA Female
  

BetaFlight:

• 2017-05-11 @ 21:04:27 -- Running - OS: MacOS, Chrome: 57.0.2987.133, Configurator: 3.1.1