R-XSR Wiring options

All three schemes are correct.

Hi everyone!

I’m working on my first ever build. I’m using the parts from the tyro 79 and installing them on the reptile cloud 149hd frame.
I have a question about connecting my frsky r-xsr receiver. Since the harness the place of aloe vera planter pot connections that came with the receiver don’t match the connection on the flight controller, can I just pop the pins and pull the wires from the black receiver connector and reinsert them into the white connector that came with the tyro kit? Or how would I go about connecting the r-xsr? I have no idea what I’m doing!
(Hope that makes sense, I included a photo to give you an idea of where I’m at. Thanks for any help!)

Hi, quick question: does the third option ("As Futaba") provide the same functionality (telemetry, openTX integration) as the other two?

No, with the third option (S.Bus only) you cannot have either Integration or telemetry.

Only the S.Bus2 protocol would allow you to be able to transmit telemetry data (but since the telemetry flow of the S.Bus2 protocol is unidirectional, it does not allow you to transmit Integration requests and data from the ground to the model, and therefore Integration would not work), but the S.Bus2 protocol is not handled by FrSky / Smart.Port receivers.

I'm pretty new to FrSky but I'm familiar with iKon.

I'm using a FrSky Neuron 60s ESC. I am wired up as "option 2" as I would say above - a wire soldered to the Bpad of the rxsr going into the signal pin of SAT-1.

I find it interesting that the Ikon software still shows a picture of the telemetry going to the 4-5-6 port.

I'm getting very minimal sensors back with the Neuron 60.  I played with all types of ESC option and I get a lot more sensors back on (YGE, Kontronik, and Castle Creations) but not all of the sensors that the Neuron offers (for instance ESC voltage)

Can anyone offer input or suggestions here?

The question should be put to FrSky support, which is already aware of problems due to various current incompatibilities between their own products.
No firmware has yet been released for the Neuron ESCs that will make them work with the new F.Bus and F.Port protocols. For now they only work with the old and slow S.Port protocol.
Except for the Archer or TD receivers that work with the new F.Bus protocol, the other receivers (and among them the R-XSR) work only with the S.Bus + S.Port protocols or the F.Port protocol.
As for the new transmitters with Ethos operating system, however, the Ethos LUA interpreter communicates via telemetry with the receivers only when using the F.Bus protocol.
Consequently, with FrSky Neuron ESCs and Tandem transmitters with Ethos OS you can have either only ESC telemetry or only LUA integration (but in the latter case, you would also have to change the receiver to an Archer or TD).
Currently, it is unfortunately not possible to have both, but this is not up to MSH Electronics but only to FrSky.
Unless versions of OpenTX or EdgeTX are released for Tandem transmitters that would remove these Ethos incompatibilities.
As for connecting the Neuron ESCs to our flight control units, however, just follow the instructions of the Neuron ESCs: the "PWM" cable should be connected to the Throttle Out (CH1) port of the flight control unit and the cable with the telemetry S.Port signal should be connected to the S.Port signal of the receiver which in parallel also goes to the CH3 port of our flight control units via a "Y" splitter cable.
Then on the transmitter you only need to do a "Discover new sensors" to automatically activate the reception of all sensor values from the Neuron ESC which is connected directly to the receiver.
As for the ESC parameters that can be logged by the flight controller, you will not have to select any particular telemetry other than "Basic Telemetry" because the protocol by which the ESC parameters are read is the same as already established by the communication protocol you selected for the receiver.