pascallanger / DIY-Multiprotocol-TX-Module

Multiprotocol TX Module (or MULTI-Module) is a 2.4GHz transmitter module which controls many different receivers and models.
https://www.rcgroups.com/forums/showthread.php?t=2165676&goto=newpost
GNU General Public License v3.0
1.65k stars 439 forks source link

Microzone Protocol Support #795

Open richardclli opened 1 year ago

richardclli commented 1 year ago

Microzone protocol Radio: MC10 Receiver: MC9002 (M2 sub-protocol) Chip used: A7105

Will provide SPI dumps in this issue.

richardclli commented 1 year ago

Dump for controller switch on without receiver, chip init sequences.

Switch-On.zip

richardclli commented 1 year ago

The Microzone supports 6 different sub-protocols, and now only the first 4 (M1,M2,M3,M4) is used, M5 and M6 is reserved.

I have summarized the A7105 commands from M1 to M6 in the attached Excel file.

M1 is quite different from others. M2 and M3 are quite similar. M4-M6 uses a different payload size.

Switch-On-SubProtocols.xlsx

richardclli commented 1 year ago

Dump for binding a receiver (M2 subprotocol)

  1. Power on receiver
  2. Press binding button and let receiver goes in binding mode
  3. Start SPI capture
  4. Power on radio
  5. Bind done

Bind.zip

richardclli commented 1 year ago

For channel encodings, M2 sub-protocol can support max 8 channels:

Payload length: 11 bytes Bits per channel: 10 bits Ch1 = packet[0] + (packet[1] & 0x03) << 8 Ch2 = packet[1] >> 2 + (packet[2] & 0x0F) << 6 Ch3 = packet[2] >> 4 + (packet[3] & 0x3F) << 4 ......

Final byte is always 0, not sure whether it has other purpose.

richardclli commented 1 year ago

@pascallanger Interested in working out this protocol together?

richardclli commented 1 year ago

Freq Hoping seems follows a fixed sequence: 0x11, 0x61, 0x4D, 0x9D, 0x25, 0x75, 0x07, 0x57, 0x1B, 0x6B, 00x39, 0x89, 0x2F, 0x7F, 0x43, 0x93

pascallanger commented 1 year ago

Sure we can have a look. I've been quite busy lately so don't expect prompt responses.

richardclli commented 1 year ago

Sure we can have a look. I've been quite busy lately so don't expect prompt responses.

No problem, I will work out more details first.

richardclli commented 1 year ago

@pascallanger Could you suggest which protocol source code is best for me I start the coding?

pascallanger commented 1 year ago

I think you need to create a new protocol.

richardclli commented 1 year ago

I think you need to create a new protocol.

Yes, any suggestion on which protocol source should I copy and code for this new protocol.

MRC3742 commented 1 year ago

Not sure if this helps but I have an older Airfield branded Microzone (MC6DR) receiver that binds and operates on the Kyosho - Hype sub protocol.

This was out of an Airfield Corsair 1450mm RTF plane and the MC6S TX FCC ID comes up as a Microzone Product.

This protocol may be the same as the M1 of your MC10 ?

Rich

richardclli commented 1 year ago

Thank you for your information. Let me verify this.

Not sure if this helps but I have an older Airfield branded Microzone (MC6DR) receiver that binds and operates on the Kyosho - Hype sub protocol.

This was out of an Airfield Corsair 1450mm RTF plane and the MC6S TX FCC ID comes up as a Microzone Product.

This protocol may be the same as the M1 of your MC10 ?

Rich

richardclli commented 1 year ago

@pascallanger Not sure if you may have some time to take a look on what is captured. I may need some guide in doing the programming.

pascallanger commented 1 year ago

Have you ever finished this protocol ?

richardclli commented 1 year ago

Not yet, better to get some help from you.

pascallanger commented 1 year ago

Sure, can you explain me what you've done so far? (Sorry just trying to catch up with things lately)

richardclli commented 1 year ago

I just captured the SPI, then try to find the samples of M1 to M6 receivers, but can only got a M2. Well, we can just work out M2 first, anyway. So please see if you may have time to take a look to the SPI dumps attached with this issue, thanks.

pascallanger commented 1 year ago

Ok so let's go for M2

richardclli commented 1 year ago

Ok so let's go for M2

Yeah!

richardclli commented 12 months ago

@pascallanger So we can start with the spi dumps attached with this issue.