You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I just purchased a brand new JJRC H36 from Aliexpress and was hoping to bind it using the IRangeX IRX4+ with either the MJQx -> E010 or the E010 R5 protocols. Unfortunately, neither of them worked (despite trying different frequency fine tuning settings). I am thus assuming that the current version of the H36 comes with yet another new procotol that is not supported by Multi Module, yet. The board on my drone reads JR-NH010R9.
This is a good start but I need more dumps to try to understand this protocol.
First use the latest XN297Dump protocol version that you can find in the test build https://downloads.multi-module.org/latest-test/
Please run the following dumps in Auto mode:
Capture the original TX in bind mode
Capture the original TX in normal mode
at the end when identify sticks appear, move slowly (really slowly) the following channels A E T R and then press the feature buttons in a specific order that you'll write down and paste here.
Hello Pascal,
I just purchased a brand new JJRC H36 from Aliexpress and was hoping to bind it using the IRangeX IRX4+ with either the MJQx -> E010 or the E010 R5 protocols. Unfortunately, neither of them worked (despite trying different frequency fine tuning settings). I am thus assuming that the current version of the H36 comes with yet another new procotol that is not supported by Multi Module, yet. The board on my drone reads JR-NH010R9.
I also found this discussion on rcgroups that suggests the same: https://www.rcgroups.com/forums/showthread.php?4554145-New-version-of-the-JJRC-H36-%28E010-or-NH010%29
Would you be willing to attempt reverse-engineering this new protocol? What kind of information / support would you need from my side?
Thanks a lot in advance and best regards!
Tobias
The text was updated successfully, but these errors were encountered: