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.61k stars 432 forks source link

Kyosho Syncro KR-331 receiver not binding #903

Closed RichW012 closed 6 months ago

RichW012 commented 9 months ago

Hi there, my Radiomaster TX16s will not bind to a Kyosho RC Car receiver. The list of protocols includes Kyosho FHSS, my receiver is the KR-331. The original TX is the KT_231P+ I have tried all settings combinations and I have the latest EdgeTX "Providence" v2.9.1. and the module firmware V1.3.3.33. I've been told this is a multi protocol issue. Thanks

pascallanger commented 9 months ago

Who told you it's a multi protocol issue? As far as I know it works, so I would like some proof.

RichW012 commented 9 months ago

Ive been on the Radio Master Products User Group on Facebook and that's what they said. Im not an expert in this so I bow to the greater knowledge. Its just been a case of trying everything with a receiver that is known to work, with a radio that's got no problems, and this is whats left. I understand the MiniZ receivers bind OK, but its my RTR Car ( Neo inferno3 )that won't. How can I supply proof?

pascallanger commented 9 months ago

Do you have any protocol working with the A7105 RF component?

RichW012 commented 9 months ago

No I don't have any other receivers that uses a protocol using that component, so guessing where you are going, I need to test it somehow and make sure its not just a faulty A7105 RF component in my TX, is that possible with a multi-meter? I do have a diagram of the chip.

pascallanger commented 9 months ago

A multimeter won't help. Do you know anyone around you with a flysky receiver? This is quite a known brand.

pascallanger commented 9 months ago

I've been able to borrow a mini-z with a kt-531 TX. I'll have it on Saturday so I can test.

pascallanger commented 9 months ago

My friend came with his mini-z FHSS with KT-531 radio. I've been able to bind his mini-z right away and control it with my TX16S. Bind procedure: On the mini-z FHSS push the bind button and power it on -> led flashing quickly. Then launch a bind on the TX16S using KYOSHO/FHSS. That's it, you have full control of the car including CH4 which is for the front LEDs. Here is the video: https://youtu.be/vBmwb3wiUTg

pascallanger commented 9 months ago

If it still doesn't work when doing a proper bind sequence https://www.manualslib.com/manual/1220526/Syncro-Kt-331.html?page=4#manual then it means that the transmitter KT_231P+ and KR-331 are not using the same "FHSS" protocol as the KT-531p. If you want this protocol to be added then you need either to ship me the TX+RX to France or sponsor the purchase of a TX+RX set locally (around 55€ incl shipping).

pascallanger commented 9 months ago

Ok I think here it is: https://www.kyosho.com/jpn/support/instructionmanual/digital_prcs/pdf/82146_KRG-331_IM_A4.pdf It's not the Kyosho FHSS protocol but what they call the "Syncro" protocol. Syncro TX are KT-231P, KT-231P+, KT-331, KT-432PT, KT-431S, KT-631ST.

RichW012 commented 9 months ago

Thank you for all your help Pascal! We have got to the bottom of the mystery! I will consider sponsoring the purchase, however I am in the process of moving and don't have spare money right now. As RadioMaster have just released the MT12 Surface Radio others might want to help. Thanks again

Wandereradi commented 8 months ago

With the subject to this subject, I also have a query for binding KR-331 to RadioMaster MT-12.

As I own 5 receivers and want to keep damage of buying a new tx low.

Since KT-331 is failing with throttle stick.

Any help would help in decision making.

Note: I did ask on RadioMaster chat on the webpage but no help.

pascallanger commented 8 months ago

As already mentioned, unless I get my hands on a TX+RX nothing is going to happen. So either ship a set to my attention in France or sponsor the purchase.

WazabiQc commented 7 months ago

I was having the same issue with a Kyosho Blizzard, KT-431S radio with a KR-632 receiver.. I thought it was Kyosho FHSS at first as well because it's written all over it.. Would that be the same issue then ?

Wandereradi commented 7 months ago

@pascallanger Well i am game with whatever you need, I was out of country so couldn't reply back.

So now let know if I could use a Logic Analyser and share the output from the TX to the A7105 chip.

or a Link from where i could ship you a TX RX. Mind you I am in India so there is no way to return the radio to me ( it would be your)

other option I am confident enough do the the Logic analyser stuff if you have a thread on how to. Pretty good with soldering and stuff, I cant code thats all but analyser will not need coding so i am pretty ok, with a little guidance.

Wandereradi commented 7 months ago

@pascallanger please send me your details as to where to ship a new KT331 with a receiver. I tried a couple dataloggers ( clone ) but was not successfull.. thanks in advance

pascallanger commented 7 months ago

@Wandereradi you can contact me at pascal _ langer @ yahoo . fr

Wandereradi commented 7 months ago

@pascallanger I have recorded the Logic for as below on the TX side. using 4MS/s CH 0 -> EN, CH1 -> CLK, CH2 -> SDIO. Binded Receiver - TX Logic Powered on Binded Receiver - TX Forward & Reverse Binded Receiver - TX Left & Right Binded Receiver - TX Channel 3 Fresh Receiver - TX Bind

If there is any issue with the data please let me with what Sample rate should i Capture. KT331 Dump with 4MS_s.zip

pascallanger commented 7 months ago

I've started to look at the dumps. Just by curiosity, is it an A7105 or another RF chip? Strangely they access an unknown register on the A7105, or there is something else. I had to rewrite part of my decoder since you are using a Logic 2 version on which the SPI decoder is buggy... Logic 1 is fine. Anyway I can see what's going on. The payload is huge with 37 bytes! The radio is sending bind packets at every power up then switch to normal mode. The RX does not send anything to the TX so you don't need to power the RX when doing dumps. They are using the same ID as Flysky and other Kyosho TXs: 0x5475c52A I've quickly checked the RF channels, a sequence is repeating but not more than that for now. I've checked the throttle capture, they transmit this channel on 2 bytes (LSB first) 1000 low 2000 high which is directly the PWM value. So the same will be true for all the others. More to come...

pascallanger commented 7 months ago

I should be able to code this protocol with what I have understood. I need to check this proto against the existing kyosho protocols to see if it's a variant.

pascallanger commented 7 months ago

It's nearly a copy of the kyosho FHSS protocol. I need to check exactly why you can't bind, there is only one byte difference in the payload and RF channels are the same. Normal mode has also a few bytes difference. What I haven't looked at all is the init of the component, may be that's where the real difference is.

Wandereradi commented 7 months ago

Hi @pascallanger here are the pics from the RF board on the KT331. you mentioned above that Logic2 has a issue so you mean to see the application installed on the laptop right? which version are you using so i will also capture as per that. just in case. Yes the receiver has blinking light for a few seconds afte the Tx has powered up - may be 2secondish or max 3.

RF Power TX chip KT331 TX chip KT331

pascallanger commented 7 months ago

Interesting it's an A7105 but they are accessing a register which doesn't exist, a bug in their fw probably so I don't care... What happens when you try to bind the receiver with the Kyosho/FHSS protocol? Do you see something on the RX LED?

Wandereradi commented 7 months ago

its a A7106 not 5

no it keeps blinking as is, let me try it again.

edit - it just Blinks no change

pascallanger commented 7 months ago

I should put my glasses on 😄 The A7106 has this additional register but I don't think it matters. Ok the init of the A7105/6 is the same as the Kyosho FHSS. The ID is also the same. The bind packet has only 1 byte difference. I'm going to create a sub protocol Syncro and change this byte to see if that's what preventing to bind.

pascallanger commented 7 months ago

I've pushed all the differences I've seen between FHSS and Syncro. Let's see if it works, you can download the test version v1.3.3.44 here: https://downloads.multi-module.org/latest-test/ I think most of the changes are useless, so if it works I would like to come back on some of them to lighter the code so I would need you to do some more tests.

Wandereradi commented 7 months ago

I've pushed all the differences I've seen between FHSS and Syncro. Let's see if it works, you can download the test version v1.3.3.44 here: https://downloads.multi-module.org/latest-test/ I think most of the changes are useless, so if it works I would like to come back on some of them to lighter the code so I would need you to do some more tests.

Hi Pascal, I forgot to inform I have Radiomaster MT12 4 in 1 tx, so i would need a build for that.

Also correct me - I would need to put this Bin file in the firmware folder and run firmware from firmware in the sys page

pascallanger commented 7 months ago

The zip file on the test link contains all the builds. You most likely want to use this one: mm-stm-serial-aetr-v1.3.3.44.bin Place it in the firmware folder of the SD card then on the radio in SYS navigate to the SD card -> firmware -> click on the above bin file and flash it the internal module (if the bin file doesn't appear reduce the file name length).

Wandereradi commented 7 months ago

The zip file on the test link contains all the builds. You most likely want to use this one: mm-stm-serial-aetr-v1.3.3.44.bin Place it in the firmware folder of the SD card then on the radio in SYS navigate to the SD card -> firmware -> click on the above bin file and flash it the internal module (if the bin file doesn't appear reduce the file name length).

Uploading the firmware to the Tx , fingers crossed.

Edit - when i scroll the protocols, and come to Kyosho, it shows Subtype FHSSSY for a second and than changes to FHSS and i do not see a "Syncro"

Wandereradi commented 7 months ago

Update - If i use Kyosho FHSS, it does not pair.

Also - when we select a protocol and again try to change, aplhabetic order is not maintained for the list of type. However when i move out to main screen and return back using Model key and enter the Protocol selection the Aplhabetic order is maintained

pascallanger commented 7 months ago

You should see Kyosho FHSS->Hype->Sync. Sync is really the one you should choose to bind the RX. If you don't see that it means that you are either using an old version of EdgeTX (most likely) or the module is not talking anymore to the radio (you should see the module version displayed under the model where you select Multi

pascallanger commented 7 months ago

Ok I made a typo on the subproto which might cause what you describe (FHSSHy). Download the version v1.3.3.45 from the same place and try. I'm not at home and I don't have any hw to test my code against.

Wandereradi commented 7 months ago

Ok I made a typo on the subproto which might cause what you describe (FHSSHy). Download the version v1.3.3.45 from the same place and try. I'm not at home and I don't have any hw to test my code against.

I uploaded the new 1.3.3.45 but i do not see Syncro under Kyosho and FHSS doe pair.

pascallanger commented 7 months ago

Do you see the hype subprotocol (Kyosho FHSS->Hype->Sync)? Do you see the firmware version under multi?

Wandereradi commented 7 months ago

Do you see the hype subprotocol (Kyosho FHSS->Hype->Sync)? Do you see the firmware version under multi?

I do see what you mentioned above but do not see Firmware # AETR

Update - when i am scrolling the Firmware # AETR line disappears, after i reboot the remote I can see it. Unable to pair with Hype Subtype either

pascallanger commented 7 months ago

Can you take pictures of your radio screen ?

pascallanger commented 7 months ago

Update your version of edgetx

Wandereradi commented 7 months ago

Update your version of edgetx

1 3 3 45 Image 2 1 3 3 45 Image 1 ![Uploading 1.3.3.45 Image 3.jpeg…]()

Wandereradi commented 7 months ago

Update your version of edgetx

How do I update the Edge Tx on RadioMaster MT12 4-in-1

pascallanger commented 7 months ago

"No telemetry" is the issue here

pascallanger commented 7 months ago

Update your version of edgetx

How do I update the Edge Tx on RadioMaster MT12 4-in-1

Download companion for edgetx and follow the instructions. I'm sure you will find plenty of tutorials

Wandereradi commented 7 months ago

Update your version of edgetx

How do I update the Edge Tx on RadioMaster MT12 4-in-1

Download companion for edgetx and follow the instructions. I'm sure you will find plenty of tutorials

the Edge Buddy does not support MT12 radio that i have, ie do not see it in the list. Also I see only FHSS and Hype, when Kyosho is selected and there is no "Syncro" - 1.3.3.45

Update - I installed Companion but it also does not have RadioMaster MT12

image

pascallanger commented 7 months ago

They give you the link to the latest version on the screen above. Until the message no telemetry is displayed on the screen it won't work...

Wandereradi commented 7 months ago

They give you the link to the latest version on the screen above. Until the message no telemetry is displayed on the screen it won't work...

I have re-installed the edge tx firmware seen on above screenshot using the bootloader method but it is the same version.

pascallanger commented 7 months ago

If you create a new model and select multi with whatever protocol (not Kyosho), do you see the version or no telemetry ?

Wandereradi commented 7 months ago

If you create a new model and select multi with whatever protocol (not Kyosho), do you see the version or no telemetry ?

Hi Pascal,

Yes, when i am using the 1.3.3.33, and bind with Flysky 2A - I do see Version, and sometimes - I sometimes see Version # Binding.

Update - I will retest.

Update Tested - I do not see "telemetry" with my radio's firmware from MPM download page. So i guess the RadioMaster MT12 code would be different probably

I am off to bed its 3 am for me :P

Radio No Telemetry

pascallanger commented 7 months ago

No the fw for the Mt12 is not different. I bet that if you load that model with the new firmware it will work. I must have introduced a bug in the Kyosho protocol which is preventing the main code to run and therefore the radio is not receiving info from the module. I should be home tomorrow and I'll investigate further.

Wandereradi commented 7 months ago

No the fw for the Mt12 is not different. I bet that if you load that model with the new firmware it will work. I must have introduced a bug in the Kyosho protocol which is preventing the main code to run and therefore the radio is not receiving info from the module. I should be home tomorrow and I'll investigate further.

I have created a new model when I was testing the code, but the behavior was same. Unless I am missing something

pascallanger commented 7 months ago

You are not doing what I was asking or talking about but forget anyway this was like I was thinking a crash when you select the protocol kyosho/fhss... Please test v1.3.3.46

Wandereradi commented 7 months ago

You are not doing what I was asking or talking about but forget anyway this was like I was thinking a crash when you select the protocol kyosho/fhss... Please test v1.3.3.46

Viola - it binds, screen does not go funny and rebooting receiver does not break the bind.

I will be able to test throttle and 3d channel tomorrow morning.

Thank you Sir ☺️ IMG_1508

Wandereradi commented 7 months ago

@pascallanger Observations: 1) When the Rx power cycle's binding is not affected ( TX was constally on ) 2) When Tx power cycle's with the new build - Internal Rf Mode -> Off and i have manually turn it to Multi and select Kyosho 3) When we are trying to bind, FHSS also works but Only Syncro should work. 4) If i use a Flysky2A protocol receiver and power cycle the TX, it re binds and "Internal RF" - Mode is mantained and RX automatically binds