TinyHawk S BNF - Manual

https://drive.google.com/open?id=1IA1k_RG2U16OZPO2UPAGEjdNmDkAyR09


TinyHawk S BNF - Firmware

Use target MatekF411RX version 4.0.0. If you are using an older E6 Transmitter and are having trouble binding, please use the following custom version of MatekF411RX 4.1.0:

https://drive.google.com/open?id=1cHhAOn7JFWtcEac6jmUxFYJt5vO7eOqo


TinyHawk S BNF - CLI

https://drive.google.com/open?id=1V0gbu_1x09Wp00MqnD7TWtQGEJqTGH-V



--------------------------------------------

1. Download/Install 
Betaflight Configurator 10.5.1 https://github.com/betaflight/betaflight-configurator/releases/tag/10.5.1 
For full compatibility with the firmware on your drone, do NOT use other versions of Configurator, even the newer 10.6. 

2. Connecting Drone
Connect the drone to computer via USB data cable (some are power/charging only). Open Betaflight Configurator by clicking Connect. (Don't worry about which COM port number your computer chooses for you.) 
 

3a. Flash Stock Firmware (OPTION 1 - Should work for most setups.)
Click the Update Firmware button in Configurator, and select MatekF411RX target version 4.0.0 from the drop-down menus. Then click Load Firmware [Online].   Click Flash Firmware. (If you encounter some error: please unplug the USB cable, plug it back in, and then click Flash Firmware again.)

3b. Flash Custom Firmware (OPTION 2 - Try this if using E6 Transmitter and first method cannot bind.) 
Download custom MatekF411RX 4.0.0 firmware (filename "EMAX_Custom_Betaflight_4.0.0_MATEKF411RX.hex") and save it to your desktop.

Connect drone to computer via USB data cable (some are power/charging only). Open Betaflight Configurator. Click Update Firmware. Click Load Firmware [Local]. Select the firmware you downloaded. Click Flash Firmware. (If you encounter some error: please unplug the USB cable, plug it back in, and then click Flash Firmware again.)

4. CLI Settings
Open the CLI dump linked below. (You can also download/save the text file to your desktop.) Select/highlight all of the text within the document and "copy" it (i.e. right-click the highlighted text and select "copy" from your computer's menu). 


TinyHawk S CLI MATEKF411RX (M41R) 4.0.0 BNF (Stock Setup - Generally the one to use, especially with your own transmitter)
https://drive.google.com/open?id=1V0gbu_1x09Wp00MqnD7TWtQGEJqTGH-V

(OPTION - Use this only if using a TinyHawk RTF E6 radio control transmitter, but must use the custom MatekF411RX 4.0.0 Hex File from step 3b)
TinyHawk S CLI MATEKF411RX (M41R) 4.0.0 using E6/RTF Transmitter
https://drive.google.com/open?id=1q3fIdnGv_kv__jGoPgm3WgFbGQBVxpQF

Click the CLI tab in the left-hand column. Right-click on the command line (e.g. "Write your command here"), and select "paste" from your computer's menu. Then press "enter" on your keyboard. The settings should load and save. (Don't worry if you get some kind of serial device error, as it's a known bug which doesn't affect anything.) Disconnect your drone from the USB cable. 


5. Binding Drone
Plug a charged lipo battery to the drone. The next step is easier if the battery is hanging free, out of the battery mount. Using a non-metallic object (or even just pushing/flexing the battery mount), hold the Bind button on the bottom of the main board for several seconds. Bind your radio transmitter in D8 mode. Keep the transmitter at least 5 feet away from the drone to allow for proper binding. Unplug the lipo battery from the drone. Turn off the transmitter. Congratulations, everything is now ready to be powered up for flight!


(* CLI Method for D16 Only: Use this if forced to bind in D16 (i.e. newer ACCESS-based FrSky radios, but with ACCST16 firmware update). First, change the receiver protocol in the Configurations tab of Betaflight to SPI-based receiver, Frsky_X protocol (which is for D16; the default is Frsky_D for D8). Next, try using CLI commands to bind. Enter into the CLI, "bind_rx_spi" to get into binding mode. Activate the bind function in the transmitter in D16 protocol. The drone's LED's may not change back to blinking, but continue. Then enter into the CLI, "set frsky_x_rx_num". If the rx/receiver number changed to the number that matches the receiver number shown on your transmitter, then the bind was successful. Finally, enter into the CLI, "save".)