Hey guys, I have run into an odd problem I can't figure out.

I killed the RX on my Bat 100 FS-A8S, one of the comments following my FS buyers guide on Oscars blog said that the crazy behaviour that I experience at full throttle can be eliminated by wrapping the RX in tin foil. I had de-cased the RX so I wrapped it in insulation/electrical tape beforehand but bricked despite this! 

I have now changed the RX for a micro PPM and changed the RX settings in BF, and the receiver tab shows everything working fine. However I am getting the runaway throttle problem, I have flashed the ESC's with the latest FW, but the problem persists. 

I wanted to have a look at the 'throttle min check' but don't know where to find it in BF?

Now trying to flash the FC (teeny 1s FC) with newest Omnibus FW (Released  11/01/18), but BF automatically changes the COM port when I try to write the new FW to the board. I can configure the board through COM 11, but when I try to flash it changes to COM 8 and goes through the "opening serial port..." 10 seconds "...serial port closed" and COM 11 has been removed from the drop-down box until I dis and re-connect 

I have tried using the stand alone BF configurator app, and the chrome app, but I am getting the same result regardless of full chip erase, manual Baud rate, etc. I haven't tried jumping the boot pins yet...

Flashing should not change the COM. It should change to DFU. I had Zadig go south on me out of nowhere. See if you can flash a different FC that uses DFU. If it doesn't work, then the driver probably needs reinstalling.

Yeah, needed to reinstall drivers. Zadig didn't work on my old PC, so I didn't use it on my new laptop, but installing it, installed DFU. Sorted Thanks man!

Also figured out (from the underscore!) that throttle min_check is a cli command, OH RIGHT!

Min_throttle is under the ESC/motor features in configuration tab.

Min_check (low stick) is under the receiver tab.

You don't need to go to CLI for these anymore.

Edit: if you are running Dshot then min_throttle doesn't apply. You has to use idle_up.