-
-
Notifications
You must be signed in to change notification settings - Fork 444
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New protocol for JJRC H36 (yet another) #1048
Comments
Small update: I just made an XN297 Dump with the IRX4+ (see attachment). Would this be sufficient for figuring out the protocol? |
This is a good start but I need more dumps to try to understand this protocol.
|
Thanks a lot for these instructions! Here are the logs for the different channels and modes: If something is missing or I can test further things, let me know! |
Ok so I started to look at your dumps. |
Cool, thanks for looking into it! You need to go from 0 to +100% throttle (TX beeps once) then to -100% (beeps again, drone flashes to indicate that it's bound). |
XN297, address length=5, bitrate=1M, Scrambled BindRF channel: 50 Packet NormalRF channel: 43, 49, 54, 58
Address: CC 6C 47 90 53 => same as bind Packet |
I'm confused by how you name the sticks... |
Yes, right. I didn't know how they are typically called for drones. :) |
I'm trying to figure out the crc right now... |
Ok I've got the crc figured out... Took me a lot of hours (4+) for something in the end relatively easy... |
Please try the test version 1.3.4.25 protocol H36, documentation: https://github.com/pascallanger/DIY-Multiprotocol-TX-Module/blob/master/Protocols_Details.md#h36---103 If you set the receiver number to 0 (default) it will use your original H36 TX ID as a test to make sure everything works fine (some channels might be reversed, I didn't pay attention, so let me know and I'll add it). But if you increase the RX number it will use your own radio ID. |
Wow, good work! Everything works absolutely perfectly out of the box. I tried a few different RX numbers between 0 and 63 and was able to rebind with all of them. Also, all the channels are correct, I did not have to reverse anything. Regarding the speed mode, I am assuming that it always uses the faster one now and I could reduce the channel weights myself in Edge TX if I wanted the drone to be slower, right? In any case: Thanks a lot for your effort! |
Yes... I usually set the rate to high with all the models since you can control everything on the radio side like adding expo or dual rate which is better than just low rate.
If you appreciate my work and want to offer me a beer, here is the page: https://github.com/pascallanger/DIY-Multiprotocol-TX-Module/blob/master/docs/Donations.md |
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: