My wife has several rtf tinyhawk kits in her classroom.. Recently a student plugged a battery into a tinyhawk backwards and toasted the regulator... I have been looking at using other FCs in these quads as they hard becoming harder to locate and the newer boards are almost $80...and the e-6 controller will work with any d-8 RX.... so I thought....
Apparently, this is not always the case. I have replaced the bad fc with a working one from a tinyhawk freestyle. But the controller does not work with it... here is the issue..
The controller is bound to the (toasted) fc and if I plug the fc into betaflight I get stuck movements, modes etc..
BUT, if I “bind” the controller to the “new” fc I get nothing in betaflight or response.
Since this fc was from a freestyle, instead of remapping motors and such, I did a cli dump from the toasted fc (bf 4.0.0) and changed the freestyle fc to match, copied and saved the cli to the freestyle fc. Well, it did what it was supposed to do, orientation, motors, osd, modes, etc. is correct but no stick / switch movements ..did the “bind” procedures (controller green/red lights-fc blinking to solid blue after) .. still no movements Betaflight is set to spi-Frsky D (not x).. both controllers are matek411rx..
The freestyle fc WILL bind and works correctly with my teranis AND another Emax E-6 controller..but for some reason this E-6 controller is “locked” to the original fc...
I have dug, searched, and found only one little “blurb” where someone was asking about binding issues with another small quad after they lost their tinyhawk, and was told “unfortunately, “you probably have the old version of this transmitter, nothing you can REALY do here unfortunately “(Brushlesswhoop.com)
I can not confirm, but I believe this rtf kit was purchased by my wife and this tinyhawk has the original fc...
So, is it possible that this controller will not bind / work with another d-8 fc if it was “locked” to rhis one fc from the factory?? Can the controller be “updated”? I know these controllers are not the greatest and reasonably cheap ($30)...I’m more curious for the knowledge and in case someone else thought they were losing their mind trying to get one of these to work with another d-8 rx...

   
I may have answered my own question...found info on Emax site regarding “older controllers” and freestyle binding... I’ll post the pic when I get to my laptop

Made progress.. tried the first suggestion.. no luck..
The second however (custom hex and cli dump) has now given me “stick movements” in betaflight.. should only be a matter of remapping motors, fc orientation and modes and ready for fall students ...
I will just have to remember this controller will only be able to be used with TH FCs ....

Progress made, bound, motors mapped.. modes set.. flight good...
I hope this info helps someone else that may have this issue...

(18-May-2021, 09:53 PM)Rob Axel Wrote: Made progress.. tried the first suggestion.. no luck..
 The second however (custom hex and cli dump) has now given me “stick movements” in betaflight.. should only be a matter of remapping motors, fc orientation and modes and ready for fall students ...
 I will just have to remember this controller will only be able to be used with TH FCs ....

Any chance I could get that custom hex and CLI? I’m trying to sort pairing a bunch of tinyhawk II’s with old E-6’s for a summer camp and they’re giving me quite the heacache

I got it from the emax site...have no idea where (if) i still have it. I will say, the e6 controllers are giving me a headache as well. She brought home all the tinyhawks (what is left)... I began to do repairs (antennas, frames, soldering motors directly to the fcs. One has a fried esc, no big...she got 8 new ez pilot pro setups... and another would not respond to any of the e6 controllers.... so i installed a external d-8 rx in the tinyhawk (the antenna got ripped off, i thought the spi rx was dead... well, I cant for the life of me get the NEW rx to bind either, it binds to my taranis and betafpv controller no problem... leading me to believe the controllers are going bad. Remember, these are middle schoolers, these look like X-box gaming controlers... and get treated as such. the old parts / hawks will be phased out and used for parts.. the new controllers HOPEFULLY will take a bit more abuse. I cant complain, they lasted 2 good school years....\
I just wish there was a way to confirm they are not transmitting / working correct.. I get all the indicators that they are in "bind mode" but the RX doesnt repond .
Any one have any info on these , other than toss them, I would greatly appreciated it..
If you have the first edition of the controlers, ( I doubt you do) dont bother...I have the feeling your controllers are going bad also.. do u have a different one u can test the hawks on other than the e6s?

well, this is a weird situation... the e6 controller will NOT bind with the tinyHAWK SPI or the frsky pro v1 rx (d8) that I installed...BUT the controllers will bind to my newbee drone beebrain bl with a frsky rx. The tinyhawk will bind to my Taranis and Betafpv, and new Emax ez pro pilot controllers. So I know the RX works, the binding sequence is correct. its just WEIRD that the E6 will bind to some d8 rx but not others... No, no "updates" can be done (that I know of)..
I have other emax d8 rxs I may try. One thing I did notice, the sweep of the throttle in betaflight is TERRIBLE! no wonder the kids were having crashing issues...I may try cleaning them.. or just phase them out completely.