<p>There are many different communication protocols used for radio controlled models and even for the same vendor the parts/versions are not always compatible. While most use the same chips to build their systems everybody uses a different protocol and so the different parts do not understand each other.</p>
<p>Most of the companies do not release official information how the protocols works and are not interested to make their products compatible with a competing vendor.</p>
<p>So if a drone claims to be DSM2 compatible there are two options: a genuine spektrum receiver is used or somebody found out how the protocol is working by reverse engineering the system.</p>
<p>Most cheap drones do not use genuine receivers since the product costs less than the receiver alone. The drone you linked does not state DSM2 compatiblity so I'd say the problem is that you have no compatible tx. But information on the product page is not sufficient to tell what they are using.</p>
<p>You could try to find out what protocol the drone uses and check if the multiprotocol project supports it: <a href="https://github.com/pascallanger/DIY-Multiprotocol-TX-Module/blob/master/Protocols_Details.md" rel="noreferrer">https://github.com/pascallanger/DIY-Multiprotocol-TX-Module/blob/master/Protocols_Details.md</a></p>
<p>But even in that case you would need to buy a multiprotocol module and make sure it works with your DX5e.</p>

CC BY-SA 4.0
2020-09-15T07:21:13.220Z
2020-09-15T07:21:13.220Z
bingo-fuel
<p>I picked up a really cheap generic drone mostly for the purpose of tinkering and testing with something that I wouldn't mind losing or destroying. However I can't seem to bind to it with any of my controllers. The main one that I use is the DX5e (DSM2, as it says on the front), but I don't think it's working. Is there a standard/universal procedure that I can use to be fairly sure that the drone is incompatible or broken? Does a difference in rx/tx protocol always make it completely incompatible? I have a few other &quot;toy&quot; transmitters that I tried a little as well.</p>
<p>It's something like <a href="https://www.wish.com/product/5de8eba0d63e2835308f1248?from_ad=goog_shopping&amp;_display_country_code=US&amp;_force_currency_code=USD&amp;pid=googleadwords_int&amp;c=%7BcampaignId%7D&amp;ad_cid=5de8eba0d63e2835308f1248&amp;ad_cc=US&amp;ad_lang=EN&amp;ad_curr=USD&amp;ad_price=44.02&amp;campaign_id=6948791183&amp;guest=true&amp;gclid=EAIaIQobChMIs_bfrJPl6wIVFz2tBh0t4AjeEAQYBCABEgIeU_D_BwE&amp;hide_login_modal=true&amp;share=web" rel="noreferrer">this</a> RCtown SH5 (Wish.com).</p>

<transmitter><receiver><toy-grade-drone><transmitter-protocol>
Binding DX5e (or any other hobby controller) to generic "toy" drone - protocol compatability
Galaxy
# Binding DX5e (or any other hobby controller) to generic "toy" drone - protocol compatability

(Asked by: username_0 on 2020-09-14)

I picked up a really cheap generic drone mostly for the purpose of tinkering and testing with something that I wouldn't mind losing or destroying. However I can't seem to bind to it with any of my controllers. The main one that I use is the DX5e (DSM2, as it says on the front), but I don't think it's working. Is there a standard/universal procedure that I can use to be fairly sure that the drone is incompatible or broken? Does a difference in rx/tx protocol always make it completely incompatible? I have a few other "toy" transmitters that I tried a little as well.

It's something like [this](https://www.wish.com/product/5de8eba0d63e2835308f1248?from_ad=goog_shopping&_display_country_code=US&_force_currency_code=USD&pid=googleadwords_int&c=%7BcampaignId%7D&ad_cid=5de8eba0d63e2835308f1248&ad_cc=US&ad_lang=EN&ad_curr=USD&ad_price=44.02&campaign_id=6948791183&guest=true&gclid=EAIaIQobChMIs_bfrJPl6wIVFz2tBh0t4AjeEAQYBCABEgIeU_D_BwE&hide_login_modal=true&share=web) RCtown SH5 (Wish.com).

**Tags:** transmitter, receiver, toy-grade-drone, transmitter-protocol

---

## 1 answers

### Answer by username_1 on 2020-09-15. Score: 5 | Accepted answer

There are many different communication protocols used for radio controlled models and even for the same vendor the parts/versions are not always compatible. While most use the same chips to build their systems everybody uses a different protocol and so the different parts do not understand each other.

Most of the companies do not release official information how the protocols works and are not interested to make their products compatible with a competing vendor.

So if a drone claims to be DSM2 compatible there are two options: a genuine spektrum receiver is used or somebody found out how the protocol is working by reverse engineering the system.

Most cheap drones do not use genuine receivers since the product costs less than the receiver alone. The drone you linked does not state DSM2 compatiblity so I'd say the problem is that you have no compatible tx. But information on the product page is not sufficient to tell what they are using.

You could try to find out what protocol the drone uses and check if the multiprotocol project supports it: <https://github.com/pascallanger/DIY-Multiprotocol-TX-Module/blob/master/Protocols_Details.md>

But even in that case you would need to buy a multiprotocol module and make sure it works with your DX5e.


---

