openrcforums

The switches on the back are ONLY active when feeding the module with PPM.
When feeding PXX their positions are ignored and the settings come from the radio.

A FET is controlled by voltage, so leaving the pin floating is bad since any stray signal can turn it on. A BJT is controlled by current, so won't turn on unless something actively pushes current through it.

You should look at the R9M manual to see what's supported, it's pretty complex based on the selected region and power levels.

The Naza doesn't let you use manual by default, you have to enable it in the Assistant first.

Yes.

R9M works just the same as an XJT.

Yeah, they have just made it this morning. Not that we're happy about it, it seems every time we complain about things already being "worked on" by too many people in too many different repos without coordination the result is someone opening yet one more to ensure it's going to be months of hell be...

Not that I know of.
How did you do the 3sec timing?

Not at this point, no. But that is in the works:
https://github.com/opentx/opentx/pull/6008

The 7ms rate should not be critical.

Yes OpenTX supports SBUS in some configurations as well, but I had understood you did not want to go through the trainer port input/logic.

Most of the stuff on the Wiki is even older than that. I know of some sources but other people will be more likely to have links at hand.

OpenTX allowed connecting a 2nd module to the trainer port and sending upper channels to it. I think it was the "PPM16" choice.

Yeah currently broken as pointed out here. https://openrcforums.com/forum/viewtopi ... 12#p139412

No. Only thing you can do is pass control data using the trainer inputs.

OK, those I have give you the R:X S:Y when the balance cable isn't connected and it thinks there may be a mismatch, but if it is they just tell you cell count error and don't let you go further. You DO need to pay close attention to that check screen when it appears and dismissing it is a common thi...

Not DIY, but FrSky now make a ready to use product with a built in X receiver.
https://www.horusrc.com/en/frsky-xsr-sim.html

My fault entirely for trusting electronics to stop me making a silly error, but be warned. Well too bad but it DID warn you to check your settings becasue they didn't appear to match and you told it to continue anyway... It is pretty standard behavior with most chargers if you don't connect the bal...

To be clear most of the work on this has been done by us (OpenTX team). There will be 2 firmware variants, one "Standard OpenTX" distributed by us as usual via companion and flashed by default to FlySky-supplied radios, and one UFPV one, also distributed by us via companion and flashed by default to...

Note that you have to be very careful when doing that, if you're replacing the eeprom you will have a transmitter ID that will be the same as anyone else having done that, so if you're at the same place than someone else who has done that you will likely be controlling each other's models..

I believe that companion converts them? So, not a big deal? :) Yep. Although going from 2.0 to 2.2 there have been lots of improvements so there still is some manual work. Handling of telemetry changed entirely in 2.1. But everything related to model control is maintained, it's only "accessory stuf...

He's concerned about the amount of work to convert his models and you're suggesting him something where he'd have to restart everything from scratch?

No. We are working with them, nobody has shipped anything yet, and everything will be in order when they do. The people who got hold of hardware got it illegitimately (they were apparently early protos given to testers for mechanical feedback in China that those decided to sell or otherwise pass on ...

It does not have a separate module with a PPM "bridge" inbetween, the RF transmission is directly managed by the radio's main processor. It thus has the possibility to store the RX ID in each of the model memory's settings. AFHDS2A can only bind one receiver per model. Then the "dumb PPM module" arc...

Because they are different systems and work differently? For some reason in the AFHDS2A system Flysky have decided to store the receiver's ID in the transmitter unlike pretty much every other system out there, and that's a result of it. It causes several convenient things people are used to doing wi...

Maybe describe your use case a bit more, then you can get recommendations.

Or low receiver voltage.

Unfortunately that isn't possible with the AFHDS2A system.

The "snake" with a jack at the end is a cable that makes either an M or an S and that's the trainer connection. USB is the obvious USB symbol. Recording is the usual big dot.

Believe the only ones are trainer cable connected (either master or slave) and logs recording in progress.

PPM is a 50 year old signal, it cannot carry information other than channel positions.
The information could be encoded into one of the channels, but that would require the module to expect that and have a memory system, which is not the case. With the RM0003 you'll just have to deal with rebinding.