Welcome to DIY-Multiprotocol-TX-Module Discussions!

[pascallanger]

👋 Welcome!

We’re using Discussions as a place to connect with other members of our community. We hope that you:

• Ask questions you’re wondering about.
• Share ideas.
• Engage with other community members.
• Welcome others and are open-minded. Remember that this is a community we
  build together 💪.

To get started, comment below with an introduction of yourself and tell us about what you do with this community.

[Gaylian]

I'm new to this discussion. I have a Jumper T16 Pro with Multiprotocol module. I usually use FRSKY D16 and Jumper R1 Rx's. I have a FRSKY TFR6 Rx I was hoping to use but it seems as though there is no FASST protocol for this RX. My question is does the module support FASST protocol.

[ANS-HAFEEZ]

Hi, I also have jumper R1 D16 receiver but it won't bind with my multi-protocol module. After some search I found that it has D16 v2.1 and can't bind with mutiprotocol module.
Can you please guide me in this regards?
Thanks:)

[pascallanger]

Futaba FASST is not supported and won't be since the multi module does not have the hardware to add it.

[wollenagold]

Hy, i'm New in this Diskussion and my question is the Support of the fhss-Protokoll of the carson wheel pro tx. I didnt find a protokoll and posibility to bind the iRange x-Modul i use in my frsky x-lite s with the receiver carson Reflex wheel pro 4ch-rx. I searched the Web but i did not find anything that helps me.
Thanks for a helpfull answer if that is possible or not.

[pascallanger]

The Carson protocol is not supported.

[Duncandan1]

Hi I'm Dan, been flying RC for a number of years mostly glider and powered gliders.I've been using a Taranis X9D for 6-7 yrs but decided to buy the Radiomaster T16S. Open TX makes it great because I know a bit about it. I recently bought a toy style drone and the multiprotocol module is new to me. I can get my FrSky receivers and a Tactic. My question is how do I figure the protocol for a drone that isn't on the list.
https://hobbyking.com/en_us/2-million-pixel-camera.html?___store=en_us Thanks DAN

[pascallanger]

Hi, No idea what protocol it can use or if it's even supported...
2 options:

• Write on rcgroups to see if someone as an idea: https://www.rcgroups.com/forums/showthread.php?2165676-DIY-Multiprotocol-TX-Module
• Try every protocol and subprotocols

[Duncandan1]

Thanks pascallanger, shall do

[vojtas81]

Hi, I want to use my TX16S to fly with Hubsan Spy Hawk 301s and everything seems to work fine. The only issue I have is, that my transmiter doesn`t receiwe any telemetry data. My question is, am I doing something wrong, or there are simplny no telemtery data sended in to my transmiter? Thank you

[vojtas81]

Thank you for fast reply. Yes, I have launched sensor discovery, but without success. Do you mean "Detect new sensors" on "Telemetry" page?

[pascallanger]

Yes, that's where they should appear. The discovery should be launched when the quad is powered and bound to the radio.

[vojtas81]

Ok, that's what I do. I have no idea what might be wrong then. Also transmitter and multi module is updated.

[pascallanger]

Do you see the multi module version and status where you select the protocol?

[vojtas81]

Sorry for language, it is Czech version.

[FPVxfun]

Dear Pascal, is it possible to add FAILSAFE to DSM (Spektrum) protocol?

Thanks in advance

[pascallanger]

The DSM protocol does not allow failsafe to be transmitted.
If your RX is compatible with DSM forwarding then use this LUA script otherwise failsafe is done on the RX itself.

[Wesie]

Hi,
first at all: Thx a lot for your great work.
Uncomfortable I couldn't found any information, which protocol is incl. in the precompiled FW on the DL Side. In my special case the question is more relevant for the 4:1 AVM Modul, because the memory is limited and also in history only a subset of protocols found place.
It will be a nice idea to have this information on the Download page, because of the included or excluded protocols the decision must make for DL and flash or complied by his own

[pascallanger]

It's in the file name. The A7105 build has all the protocols running with this RF component. The cyrf build has all the protocols running with this RF component. Same for the cc2500.
These are mostly test builds.
Compiling your own version for an avr module is a must.

[kvdelsen]

Hey there! Just a quick question: is frsky ACCESS coming to mpm? And is there any firmware available on this github page for my RM TX16S? I could only find firmware on the MultiProtocolModule website which was labeled for it...

[pascallanger]

#487
https://www.multi-module.org/using-the-module/firmware-updates

[kvdelsen]

Oh allright, so that site does have the correct version, was a bit confused wether firmware would be here or there, thanks! How about the access support?

[pascallanger]

#487

[adso85swe]

Hi Pascal. Great work with the multiprotocol support! Amazing stuff.

I am wondering about the reson for the lack of failsafe on the WFLY protocol. Are there technical limitations for such support or is it simply due to lack of demand from the users?

[pascallanger]

One drive is fine. But I'm not sure seeing the video will help troubleshooting...

[adso85swe]

Let me know if you have managed to see it. I will probably remove the link after that. I guess you can download the video locally for your own reference.

[pascallanger]

I can't see it. I thought it was my mobile phone yesterday evening but same on the PC this morning.

[pascallanger]

Ok I can see the video now.
You do not rebind the RX as you previously stated...
When you launch a bind as you do, you just relaunch the protocol which is the same as turning off/on the radio.
To emulate the radio on/off you can either launch a bind or change the RX number back and forth 0,1,0,1,0...
My guess is that your RX does not like some of the frequencies being used. Since they are selected randomly at each start up sometimes it works and not other with no direct correlation.
The RX I have do not do the same. I still don't know if this is linked to the ID or not.
The only way to troubleshoot further is to connect a FTDI to your module to see which frequencies are causing issues and if I use your ID I can reproduce the behavior.

[adso85swe]

Interesting. I am not an expert in how these Tx/Rx protocols work by any means. If the Rx doesn't like some of the frequencies chosen by the Tx, does it mean that the emulation of the WFLY protocol in the Tx is slightly incorrect? I.e., does the Tx choose frequencies that are not supported in the "real" WFLY protocol?

No matter what the technical problem is, with this behaviour, do you still think that there is no risk with triggering such a frequency mismatch during flight?

Btw, just to be clear, I did not yet try your new software that supports custom failsafe setting. This was still the latest official release.

[MasuFPV]

Thank you for providing a great mechanism and I am having a good radio life.

I really like the quick response of the REDPINE protocol and the feel of the futaba 18sz radio gimbal. So, I would like to connect jp4in1 to futaba radio and use REDPINE protocol.
I was able to connect jp4in1 to the futaba radio with PPM and use the REDPINE protocol, but I could not get the quick response of the REDPINE protocol. So, I would like to connect jp4in1 to futaba radio in serial mode.

I understood the connection method for serial connection by referring to the CRSF example, but futaba radio cannot send protocol specification or bind command to jp4in1 in serial mode. Is there a way to connect and use jp4in1 in serial mode with futaba radio?

I thought that it could be solved by editing config.h in the case of serial mode on the jp4in1 side and specifying to use the REDPINE protocol, but I did not know how to realize it. .. Thank you.

[kilrah]

PPM is the only thing a T18SZ can output and it'll obviously be slow, so time to get used to another radio...

[MasuFPV]

Thank you for reply!
I'm not familiar with it, but futaba has a serial protocol called s-bus.
https://os.mbed.com/users/Digixx/notebook/futaba-s-bus-controlled-by-mbed/

I wanted to use a radio that I was familiar with.
But I may have been too greedy.
Thank you.

[pascallanger]

The SBUS they are talking about here is the output of the RX not the TX...

[pascallanger]

And adding the module behind a few will increase the latency even more so no point in doing this.

[MasuFPV]

I am very happy to have your support.
I was able to understand well.
Thank you.

[wollenagold]

Thanks for the  Information. Change the RX Holen Sie sich Outlook für Android

[asaerong]

Hello, I am Albert and new here in the discussion. I just wanted to say thanks to Pascal for the great work on multiprotocol! and hoping to get advice on my case.

I was using a Jumper T-Lite and the internal multi module works great, and I can easily clone my old XJT JR module and use Frsky D8 cloned and FrskyX D16 cloned with my old quads (DII4R and XSR). But I recently moved to use TBS Tango 2 and bought TBS MPM with the thought that I will have the same experience as with my jumper which apparently it wasn't. Both are at the latest firmware (mpm 1.3.2.77, tango 1.3.29). cloning the TX works fine but FrskyD cloned sub type is missing in TBS MPM version, also FrskyX (skipped). The only available clone subtype is in FrskyX2, which is can't be used for my purpose.

Pascal stated in rcgroups about 7 months ago that it was freedomtx (tango)'s problem because of they are using old multicode, which seems hasn't been fixed until now, in the meantime, seems that their github was already abandoned because it's last release posted there was 1.1.3 while actually the latest recent version supposed to be 1.2.9. so not sure raising the issue there will be read by them.. is there way to make it work or a workaround from mpm side? or it is just a given that until freedomtx fixed their thing, Frsky radio cloning feature does not fully work in TBS Tango 2+mpm....

Worst case, i'll re-bind everything (9 of them :) LoL) with tbs mpm and make it as a master, and have the jumper as mybackup to clone the mpm instead of my old XJT. but it would be great if I don't have to go that route :)

[pascallanger]

You posted the same question on RCG and I've answered there.

[asaerong]

Yep, got it. Thanks Pascal!

[Winslow87]

Hi Pascal,
I use a Horus X12S with external iRangeX+ module ( firmware v1.3.2.77).
All worked fine 'til OpenTX v2.3.11 but since updating to v2.3.12, I get a message "Invalid protocol" when selecting "MULTI". Downgrading to 2.3.11 fix the problem.
Any idea ?
Thanks for your nice job.
Pascal

[pascallanger]

Upgrade your module to v1.3.2.86: https://downloads.multi-module.org/latest-test/

[Winslow87]

Thanks for your help.

I've upgraded multi module to v1.3.2.86 but that don't fix the issue for OpenTx versions higher than 2.3.11 (message "invalid protocol" instead "module fw version" in "Module status" box and the protocol is stuck on "Assan".
Note : if the module is not present, it is possible to scroll throught all protocols an "Module status" is "No telemetry...".
I launched "Multi module" tool in "system/tools" menu : I got the message "Module not configured" or something like that (my Tx language is french).
I 've done the same test after downgrading OpenTx to v2.3.11 : the message is "External Multi detected - Protocol "name of the selected protocol" - Channels..."

Regards
Pascal