- Posts: 1016
MoonTop M9916
- SeByDocKy
-
Topic Author
- Offline
I captured some trace of the Syma X11 clone using a XN297 ....
mon-partage.fr/f/6xV4OCda/
For volonteers ....
- Durete
-
- Offline
- Posts: 610
Should work with Eachine H7 implementation from Goebish
- goebish
-
- Offline
- NRF Weirdo
- Posts: 2633
Init sequence is missing from captures, setup a trigger then start capture before powering the TX on.
edit: are you sure this is a xn297 ? Captures are weird.
- Durete
-
- Offline
- Posts: 610
2 different protocols? Who knows...
- Durete
-
- Offline
- Posts: 610
- SeByDocKy
-
Topic Author
- Offline
- Posts: 1016
goebish wrote: It doesn't look like the same protocol at all.
Init sequence is missing from captures, setup a trigger then start capture before powering the TX on.
edit: are you sure this is a xn297 ? Captures are weird.
Yes it's a XN297 ... maybe I plugged uncorrectly wires ....
- SeByDocKy
-
Topic Author
- Offline
- Posts: 1016
Durete wrote:
Ho I should test
- SeByDocKy
-
Topic Author
- Offline
- Posts: 1016
SeByDocKy wrote:
Durete wrote:
Ho I should test
Yes you are right it's binding .... but still have an horrible model for my Devo 7E. Durate, do you have one for the H7 ?
- Durete
-
- Offline
- Posts: 610
SeByDocKy wrote:
SeByDocKy wrote:
Durete wrote:
Ho I should test
Yes you are right it's binding .... but still have an horrible model for my Devo 7E. Durate, do you have one for the H7 ?
Sorry, but I don't have the H7 or M9916
edit: You can start from a fresh model file, and use the suggested channel/values from Goebish at Eachine H7 thread
- goebish
-
- Offline
- NRF Weirdo
- Posts: 2633
SeByDocKy wrote: Yes it's a XN297 ... maybe I plugged uncorrectly wires ....
That's strange because they look like correct SPI bus capture, but not from a xn297...
Anyway, that's cool that H7 and M9916 are using the same protocol, that means I only have to find the flags for picture and video for the M9916, and you're right, I'll rename this protocol to MT99XX or MT991X as the H7 is the MT9911.
- goebish
-
- Offline
- NRF Weirdo
- Posts: 2633
I'll have a look and add the extra features to the currently named "H7" protocol
- goebish
-
- Offline
- NRF Weirdo
- Posts: 2633
- goebish
-
- Offline
- NRF Weirdo
- Posts: 2633
- goebish
-
- Offline
- NRF Weirdo
- Posts: 2633
Also, there's an Atmel EEPROM in the H7 controller (AT24C02, 256 bytes), it can be read via i2c, I've to check, I wonder what's written there, probably TXID, trim values and maybe a few other "secrets" ...
- SeByDocKy
-
Topic Author
- Offline
- Posts: 1016
goebish wrote: There are too much things in the quad_on_TX_on_arming_expert_mode_flip_button_camera_on_camera_off_photo_on_photo_on.logicdata file, I can't understand what flag do what, can you make smaller captures with one feature on / off per file please ?
Ok I will do
- goebish
-
- Offline
- NRF Weirdo
- Posts: 2633
- SeByDocKy
-
Topic Author
- Offline
- Posts: 1016
goebish wrote: I had a look at the EEPROM, it's used only to store trim values, no tx id unfortunately, this would have allowed me to reflash it and have more TX data to really understand the mystery byte (if really needed).
Ok I will check if the MT9916 bind the H7 (at 99% yes) then capture MT9916 TX data when the H7 is bound with its radio
- goebish
-
- Offline
- NRF Weirdo
- Posts: 2633
SeByDocKy wrote: capture MT9916 TX data when the H7 is bound with its radio
That's useless, it's a one way protocol, you don't even need to power the aircraft on
But please start capture *before* powering the TX on (or setup a trigger) so we have a full sequence: init + bind + data.
- SeByDocKy
-
Topic Author
- Offline
- Posts: 1016
goebish wrote:
SeByDocKy wrote: capture MT9916 TX data when the H7 is bound with its radio
That's useless, it's a one way protocol, you don't even need to power the aircraft on
But please start capture *before* powering the TX on (or setup a trigger) so we have a full sequence: init + bind + data.
Ok
- SeByDocKy
-
Topic Author
- Offline
- Posts: 1016
-
Home
-
Forum
-
Development
-
Protocol Development
- MoonTop M9916