1. Forum
  3. Development
  5. Protocol Development
  7. MoonTop M9916

MoonTop M9916

More
04 Jul 2015 12:02 - 04 Jul 2015 12:03 #35093 by SeByDocKy
MoonTop M9916 was created by SeByDocKy
Ok,

I captured some trace of the Syma X11 clone using a XN297 ....

mon-partage.fr/f/6xV4OCda/


For volonteers ....
Last edit: 04 Jul 2015 12:03 by SeByDocKy.

Please Log in or Create an account to join the conversation.

More
04 Jul 2015 14:55 #35099 by Durete
Replied by Durete on topic MoonTop M9916
Seby, is not the same protocol as Eachine/Gin H7/Moontop M9912?
Should work with Eachine H7 implementation from Goebish :dry:

Please Log in or Create an account to join the conversation.

More
04 Jul 2015 16:08 - 04 Jul 2015 16:39 #35104 by goebish
Replied by goebish on topic MoonTop M9916
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.
Last edit: 04 Jul 2015 16:39 by goebish.

Please Log in or Create an account to join the conversation.

More
04 Jul 2015 16:23 #35107 by Durete
Replied by Durete on topic MoonTop M9916
I don't have the M9916 or H7, but there are some reports flying the H7 with the M9916 TX :dry:
2 different protocols? Who knows...

Please Log in or Create an account to join the conversation.

More
04 Jul 2015 16:40 #35108 by Durete
Replied by Durete on topic MoonTop M9916

Please Log in or Create an account to join the conversation.

More
04 Jul 2015 17:31 #35109 by SeByDocKy
Replied by SeByDocKy on topic MoonTop M9916

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 ....

Please Log in or Create an account to join the conversation.

More
04 Jul 2015 17:32 #35110 by SeByDocKy
Replied by SeByDocKy on topic MoonTop M9916

Durete wrote:


Ho I should test :)

Please Log in or Create an account to join the conversation.

More
04 Jul 2015 17:34 #35111 by SeByDocKy
Replied by SeByDocKy on topic MoonTop M9916

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 ?

Please Log in or Create an account to join the conversation.

More
04 Jul 2015 17:35 - 04 Jul 2015 17:38 #35112 by Durete
Replied by Durete on topic MoonTop M9916

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 :pinch:

edit: You can start from a fresh model file, and use the suggested channel/values from Goebish at Eachine H7 thread :pinch:
Last edit: 04 Jul 2015 17:38 by Durete.

Please Log in or Create an account to join the conversation.

More
06 Jul 2015 10:57 #35155 by goebish
Replied by goebish on topic MoonTop M9916

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.

Please Log in or Create an account to join the conversation.

More
06 Jul 2015 11:30 #35157 by goebish
Replied by goebish on topic MoonTop M9916
Oh, OK that's just that wires are swapped in the captures, looks fine now :)

I'll have a look and add the extra features to the currently named "H7" protocol ;)

Please Log in or Create an account to join the conversation.

More
06 Jul 2015 12:33 - 06 Jul 2015 12:34 #35159 by goebish
Replied by goebish on topic MoonTop M9916
That would be interesting to check if the H7 stock controller can control the MT9916 (we know it works the other way round), the protocol is pretty similar, but one extra bit of the flags byte is always set on the MT9916 controller, also the "mystery byte" sequence is different from the 2 H7 TX captures I've seen, but looks like this is not a problem.
Last edit: 06 Jul 2015 12:34 by goebish.

Please Log in or Create an account to join the conversation.

More
06 Jul 2015 13:10 #35161 by goebish
Replied by goebish on topic MoonTop M9916
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 ?

Please Log in or Create an account to join the conversation.

More
06 Jul 2015 13:24 - 06 Jul 2015 13:59 #35163 by goebish
Replied by goebish on topic MoonTop M9916
Meanwhile I'll try to guess if the starting value of the "mystery byte" sequence is arbitrary or computed from tx id or common to one TX model... (a dump of the bind sequence of your H7 TX would help ;))

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" ... :) Oh yes I'm curious :P
Last edit: 06 Jul 2015 13:59 by goebish.

Please Log in or Create an account to join the conversation.

More
06 Jul 2015 15:53 #35165 by SeByDocKy
Replied by SeByDocKy on topic MoonTop M9916

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 :)

Please Log in or Create an account to join the conversation.

More
06 Jul 2015 15:59 #35167 by goebish
Replied by goebish on topic MoonTop M9916
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).

Please Log in or Create an account to join the conversation.

More
06 Jul 2015 16:24 #35168 by SeByDocKy
Replied by SeByDocKy on topic MoonTop M9916

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

Please Log in or Create an account to join the conversation.

More
06 Jul 2015 16:26 - 06 Jul 2015 16:28 #35169 by goebish
Replied by goebish on topic MoonTop M9916

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.
Last edit: 06 Jul 2015 16:28 by goebish.

Please Log in or Create an account to join the conversation.

More
06 Jul 2015 17:13 #35170 by SeByDocKy
Replied by SeByDocKy on topic MoonTop M9916

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 :)

Please Log in or Create an account to join the conversation.

More
14 Jul 2015 16:29 #35446 by SeByDocKy
Replied by SeByDocKy on topic MoonTop M9916
New captures : mon-partage.fr/f/QLcDixi3/

Please Log in or Create an account to join the conversation.

  1. Forum
  3. Development
  5. Protocol Development
  7. MoonTop M9916
Time to create page: 0.099 seconds
Powered by Kunena Forum
Force desktop display