Please for the love of my Sanity...

I'm Totally new to this whole hobby and OMG, I had no Idea of what it takes to get a Drone to talk to a Radio.

So, I have been trying to get my drones to bind for over a month, my Tiny Hawk, and Nazgul to my TX12. No Luck with either. Running the latest Open TX for the Radio. I finally gave up with the Naz which had a XM+ rcvr, using the FRSKYXM2 radio protocol and I finally the changed the Rcvr to an ELRS and bought the Zorro ERLS for it which I still have not tried to bind yet. Never could get the TX 12 to talk to it. I Bought the Tinyhawk2 Whoop BNF with the D8 FRSKY Rcvr. just to try a different drone and I still Cannot get the radio to bind to it. Updated the TH2 and the TX12 Radio to latest firmware, no luck.

Betaflight would not show any binding to the TX12, no inputs from the TH2. Now after trying to get Betaflight to read firmware on the TH2, all I get it a solid blue light. No communication from Beta when trying to connect USB. The light is the same when connected to the computer or a LIPO. The Cable is Good, use for many devices with Data Needs. Any firmware I try to flash for the Matek411RX? I am not at my home computer so unsure of exact target, it will not load firmware. I downloaded the factory Firmware and CLI Dump, with no luck.
 So far I have not been able to find any information on a Solid Blue Light.

After watching hours of videos, reading forums, how to's and anything else I can get my hands on to figure all this out, I am about to toss it all in the trash. I do not have the firmware for all the gear in front of me it's written down at home. So this is what I kinda remember, the Radio was I think, 2.3.1 Open TX with updated SD card contents, using FRSky with D8 no Telem, Betaflight was 4.3 ver 10.8 and the Tinyhawk was was the Matek411RX (I think) latest from Betaflight. I tried to flash back to Factory CLI and Firmware but no joy.

 I am afraid to do any updating to the ERLS drone and radio because I am sure I will kill something else.

I'm willing to give it another try If I can get the TH2 communicating.

With all that said, does anyone know how to fix the TH2 and could recommend a radio that will play nice with the TH2. I have about $200 I can spend on getting something going.


Apologies for the rambling and Very Appreciative of any and All Help.

Thanks Everyone.

I got ur back.. my wife uses Tinyhawks in her classroom.. I think she is up to 15 now.. so somehow some where I should be able to get some of this untangled..
I’m at work now , give me some time..

That Sir, would be amazing. Thank you.

Ok.. had to work late, did a cli dump on one of the tinyhawks.. apparently this one was a TH3 according to the dump..not to worry. I’m pretty sure I have a th2 cli.. just have to locate it..
First.. you are going to have to back install a older version of betaflight to use one of these.. I had not updated them.. some are straight from Emax.. with only the rates changed..
See about locating back to 4.1.*..
Also check the target..

I have 10.6 BetaFlight installed as well as 10.8. I will try again to retro grade the firmware back to the Factory firmware and CLI. Last time I tried, BetaFlight wouldn’t do anything to write the original firmware. I still get the solid blue light no other light up.

ELRS is pretty easy to sort out. First thing to do is see what ELRS is already installed on the Zorro and the receiver. If they both have say v2, don't flash anything. Just bind them and fly. Even saying that, if say the Zorro has v2 and the rcvr has v1, it's not that hard of a thing. Follow pretty much any of the guides on this site, or any of the YT vids that walks you through it. Also go on the ELRS discord and ask questions. Failing all of that, member V-22 on here is really knowledgable with this stuff and is often found on the ELRS discord.




As for a radio that will bind to a Tinyhawk, just get anything. Jumper T-Lite or T-Pro Multi Protocol, or even a cheap BetaFPV Literadio Multi Protocol would do. If you get the TX12 running, then use the cheap radio for simulator usage.

(03-Aug-2022, 06:13 PM)stargazin Wrote: I have 10.6 BetaFlight installed as well as 10.8. I will try again to retro grade the firmware back to the Factory firmware and CLI. Last time I tried, BetaFlight wouldn’t do anything to write the original firmware. I still get the solid blue light no other light up.

That’s the BF configurator… what version of betaflight do You have on ur tiny hawk? I will “update” one I have to the version you have and see if we can’t save u some confusion.
The new configurator will not show older betaflight versions.. you have to go to the GitHub pages and search the target hex file…This can be very daunting if ur not familiar with it..
Let’s make sure we are both on the same betaflight versions AND have the same target.

Well I cannot get a different computer new install of BetaFlight 10.6, this computer has never had any version installed on it. Different cables, still A solid blue light and no communication with BetaFlight. So I cannot tell you what is loaded. Sorry ?

Betaflight configurator on your computer is totally different then the betaflight on the flight controller.
I had the same issue when I first started out….
There is a TON of videos on line, Joshua Bardwell, fpv
360, tmacfpv, just to name a few that have helped me. You may have to view some “older” videos that talk about betaflight up dates (to 4.?.?). Most of this is all about updating the Flighr controller, but sometimes they do explain that you need to update the BF configurator on your computer in order to do the flight controller updates.
It’s like not being able to update a app on your phone untill you update the operating system on the phone first.
Clear as mud?
Plug in your fight controller, list what you see in the top left hand corner.. (see my pic from before) this will give us a starting point..
I screwed up a bunch of stuff when I got started, I changed PIDS thinking it was “rates”.. flashed the wrong firmware on flight controllers.. I’m still learning about rpm filtering and bi-directional D-shot.. it may seem like a lot to take in.. it kinda is.. but in time it will be second nature .. take time watch videos..they helped me ALOT!
And this has nothing to do with the controllers / receivers.. that can get messed up with updates also.

(04-Aug-2022, 11:30 AM)Rob Axel Wrote: Betaflight configurator on your computer is totally different then the betaflight on the flight controller.
 I had the same issue when I first started out….
There is a TON of videos on line, Joshua Bardwell, fpv
360, tmacfpv, just to name a few that have helped me.  You may have to view some “older” videos that talk about  betaflight up dates (to 4.?.?). Most of this is all about updating the Flighr controller, but sometimes they do explain that you need to update the BF configurator on your computer in order to do the flight controller updates.
 It’s like not being able to update a app on your phone untill you update the operating system on the phone first.
 Clear as mud?
 Plug in your fight controller, list what you see in the top left hand corner.. (see my pic from before) this will give us a starting point..
 I screwed up a bunch of stuff when I got started, I changed PIDS thinking it was “rates”.. flashed the wrong firmware on flight controllers.. I’m still learning about rpm filtering and bi-directional D-shot.. it may seem like a lot to take in.. it kinda is.. but in time it will be second nature .. take time watch videos..they helped me ALOT!
 And this has nothing to do with the controllers / receivers.. that can get messed up with updates also.

Ok, So I tried several computers to see if there was a driver issue, Nothing will talk to the TH2. Different known working data cables, different computers, nothing is talking to the drone. I cannot get BF to look at it to see what version of BF is installed on the TH2. No other LED's will light up not even a flicker, only the Blue Light of Death. It's looking like one can Brick a TinyHawk 2. Arrggh.

Try hold down the the “boot” loader button on the FC then plug it into betaflight ..
If u only have a solid blue led when u plug it in.. I’ll have to check into this.. never ran into it..

Well, now what (near to sobbing)?

It seems that even doing that, which was an arduous task in itself, trying to hold that tiny button while while plugging in the cable and constantly slipping off the goofy little thing resulted in No Joy. Why the Expletive's, couldn't they make them with even a small indent... anyway I digress, it was fruitless. While performing great feats of dexterous skill, nothing.
No lights no communication with BF. I Tried various combinations of button holds, releases and still nothing.

I have always been able to stubbornly plod my way through issues like this and get resolutions, yet this, this is taking it's toll. With all that I finally reached out to Emax.

So we'll see what wisdom they can bestow upon me.

Folks, I do greatly appreciate all your efforts and help in this dilemma/crisis trying to get this working. I've not tossed in the can yet as I am still holding out for hopes and Flying Time in this endeavor.

Jeff.

.. it’s all a part of learning this hobby.. unfortunately, you may have discovers it faster than others.. I promise… you will look back on this one day and say .. “yup, oh I remember back when..” and laugh.

Just to confirm.. you pushed the “boot” button… correct? This board has 3 buttons.. one underneath (rx-bind) one on top of the “sister board”(vtx-channel) and the last (boot) is on the top surface of the fc just to the right of the usb.

The one Marked Boot. Yep The little button that is hard to keep pressed when connecting the USB cable, right next to the USB Port.