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.62k stars 435 forks source link

Kyosho Syncro KR-331 receiver not binding #903

Closed RichW012 closed 7 months ago

RichW012 commented 10 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 7 months ago
  1. Ok
  2. Wy would the internal rf turns off? It has nothing to do with the multi firmware since the radio stores the info on its own so most likely a bug in the MT12 firmware. It's normal if the internal RF modules is off that you have to reselect Kyosho/Sync
  3. This is what I would have expected. The 2 protocols are so closed that only one byte is preventing the Sync RX to bind with FHSS. I think could even modify the FHSS protocol to bind FHSS and Sync RXs without having to add Sync...
  4. Does the internal module stays on after power cycle if you select Kyosho/FHSS? (my expectation is yes)

Please redownload the latest test firmware and test it. The version will be the same but I've done some code cleanup.

Wandereradi commented 7 months ago
  1. Does the internal module stays on after power cycle if you select Kyosho/FHSS? (my expectation is yes) -> Yes it as you mentioned But if we have selected Syncro than at power cycle of tx, the internal module is off and also a random protocol is selected.

I will test the new code in a bit.

pascallanger commented 7 months ago
  1. Does the internal module stays on after power cycle if you select Kyosho/FHSS? (my expectation is yes) -> Yes it as you mentioned But if we have selected Syncro than at power cycle of tx, the internal module is off and also a random protocol is selected.

It proves that it is a MT12 EdgeTX firmware bug. You can try the latest nightly to see if they have fixed it. As a temporary fix, bind in Syncro and go back to FHSS.

Wandereradi commented 7 months ago
  1. Does the internal module stays on after power cycle if you select Kyosho/FHSS? (my expectation is yes) -> Yes it as you mentioned But if we have selected Syncro than at power cycle of tx, the internal module is off and also a random protocol is selected.

It proves that it is a MT12 EdgeTX firmware bug. You can try the latest nightly to see if they have fixed it. As a temporary fix, bind in Syncro and go back to FHSS.

I do not see a MT12 EdgeTx firmware nightly build, do you have a link?

pascallanger commented 7 months ago

https://github.com/EdgeTX/edgetx/releases the MT12 fw is in the zip file. But you can do all that from the companion tool if you install it as I already suggested

Wandereradi commented 7 months ago

https://github.com/EdgeTX/edgetx/releases

https://github.com/EdgeTX/edgetx/releases/tag/nightly - This one?

pascallanger commented 7 months ago

If you click the link I sent you above it's the first top entry called nightly... The MT12 fw is in the zip file. But you can do all that from the companion tool (not buddy) if you install it (installation files are on the same link as above but from the stable release edgetx-cpn-xxx-v2.9.3.zip) as I already suggested, in the settings you can ask it to install the latest nightly or latest stable on the radio for you...

Wandereradi commented 7 months ago

If you click the link I sent you above it's the first top entry called nightly... The MT12 fw is in the zip file. But you can do all that from the companion tool (not buddy) if you install it (installation files are on the same link as above but from the stable release edgetx-cpn-xxx-v2.9.3.zip) as I already suggested, in the settings you can ask it to install the latest nightly or latest stable on the radio for you...

I installed the Nightly build -> Installed the Syncro build -> Turned on the Internal Module -> Set Kyosho -> Syncro, Binded the receiver, -> power cycled the tx -> worked as expected i.e. RX was bound back on power on.

When i have Binded the Rx using Syncro protocol, and than I change the sub type to FHSS - it get bound back. same is the case with FHSS and Powercycle on TX.

ODD observation was monkeying around with the protocol while the TX was on and found that Flysky2A Binds to RX

pascallanger commented 7 months ago

Have you tried the latest test version?

Wandereradi commented 7 months ago

Have you tried the latest test version?

Yeah, it was the you told me where you did some clean up and the version would be same.

Wandereradi commented 7 months ago

@RichW012 and @WazabiQc Guys could you also assist in testing the Build for KR331 receviers, I have had an accident with my car. and trying with a desk setup.

@pascallanger thank your this quick turnaround, Really appriciate the help. Also I will be further testing the code, currently trying to get the trims and dual rate set up on the MT12 ( completely new on EdgeTx)

pascallanger commented 7 months ago

Please test the latest v1.3.3.47 version available here: https://downloads.multi-module.org/latest-test/ The sub protocols are FHSS and Hype. FHSS will bind and control both FHSS and Syncro receivers.

Wandereradi commented 7 months ago

Please test the latest v1.3.3.47 version available here: https://downloads.multi-module.org/latest-test/ The sub protocols are FHSS and Hype. FHSS will bind and control both FHSS and Syncro receivers.

Tested the 1.3.3.47 build, Observation - 1) Syncro is no longer displayed. 2) Fresh binding is a bit slowe compared to when we had subtype syncro - my understanding is that now Tx is sending 2 types bind's so its taking time. 3) I do not have the Kysosho FHSS receiver so some one will need to test that is not affected in any ways. 4) Protocol Flysky2A also binds the tx to Syncro Rx but When i use a Flysky FS2A 4channel Receiver with Kyosho FHSS - RX does not bind. 5) 3r channel on the Syncro RX is also working - Tested using the 3way switch on tx.

so far so good ( happy )

I will test more on the weekend or tonight and repot back here.

pascallanger commented 7 months ago
  1. Ok
  2. Not really... I haven't touched the total bind time. What you could observe is the RX accepting the bind packets 250ms after you press bind on the TX and not right away.
  3. Too bad. But I think we are ok.
  4. The bind payload size of Flysky2A is the same as Kyosho/FHSS and they use the same ID. So depending exactly on what the RX is checking it can just accept the bind but won't be controllable.
  5. Good

I think I can close this issue now but let me know.

Wandereradi commented 6 months ago

@pascallanger

  1. The bind payload size of Flysky2A is the same as Kyosho/FHSS and they use the same ID. So depending exactly on what the RX is checking it can just accept the bind

For #4 from above I am able to control the Kyosho. kR331 even if I have selected the FLYSKY2A protocol.

Range is all is good - have been able to control my car for around 100mts which was more than enough for me.

When would this code come to Release is what I wanted to know.

Also I sent you an email some time back for some help. Would you have time to help on it.

Also could we have Weight changed to Dual Rate or D rate

dogesTV commented 1 month ago

@pascallanger hey i have this same issues are you able to explain how to connect kr-331 to Mt12 because its pretty chaotic to follow this conversation thank you :)

pascallanger commented 1 month ago

Install the latest test firmware available on the main page and it should work flawlessly.

dogesTV commented 1 month ago

Install the latest test firmware available on the main page and it should work flawlessly.

Yes it worked thank you very much