Thanks, that is exactly all I have in place.
Only question that remains is can I use a Y-lead for the Wifilink and the RX8R S.Bus or do I indeed need to swap connections when I want to change programming via the wifilink (indeed not a big deal to do.
Awaiting delivery of FrSky RX8R Pro and sensors and Spirit FRSky integration cable

Tomas probably knows this answer to this question.

You will need to swap the cables. Both protocols are incompatible, so it will not work together.

_________________
Spirit System developer

Thanks!

Need some help. I have sensors connected to my RX8R Pro Smart Port.
Now I also need to connect my RX8R Pro to the Spirit Pro SYS via the Smart Port. Since there is only 1 Smart Port on the RX8R Pro, can I use a Y-lead or how should I connect this?

Update
I tried an Y-lead and putting everything in chain. I discovered that I will have to choose.
Or using frsky sensors telemetry
Or using Spirit telemetry
Both together does not work. Apparently Spirit Pro does not forward telemetry data from attached sensors.
Would this be possible to implement in a future release or is this impossible due to hardware limitations?

You can connect everything with Y-cable. It must be connected at the receiver side, not at the Spirit side after FrSky integration cable.

Which servos do you mean? In theory there is no hardware limitation.

_________________
Spirit System developer

Hi,

i am currently in the process from switching the spirit (FW 3.2.2) from jeti rsat2 to frsky archer-rs.
(with jeti the spirit worked flawless and was a pleasant experience to setup)

first try was to just switch the protocol from jeti to sbus, with mixed results, channel mapping / channel range / channel center where all wrong...

so looked trough the forum. (thanks LapinFou for your post on the mater)

changed:
channel order/direction in TX to get it right in spirit setup
channel range in TX to get 100% in the spirit diag tool

did the setup/factory reset a few times now finaly everything looks correct, except the tail.

moving the sticks on the TX the tail servo travels only like 50% of its total way (in servo limits/endpoints in spirit tool it moves the full/expected way).
no mather what i tried in the TX it does not change the way traveled.
do i need to run the setup a few more times till this also gets correct or i am missing something?


there are lua scripts for three frsky radios, i have a an xlite-pro, none of the scripts seam to work, all throw an error, but i think that is as it should seeing another thread with the same results.


so far my two cents on trying with frsky.
now with 3 adapter cables (sbus / telemtry / esc integration), the heli looks like a cluster fuck
please think about implementing fport / fport 2.0, this frsky/sbus is somewhat of a pain

Hi ALFI,

Which RX are you using?
Which version of OpenTX?
Are you sure the tail servo is correctly declared in the Spirit Setup (neutral, narrow-band, etc...)?
Ideally, could you post a pic of how your RX is wired to the Spirit?

Seb

>Which RX are you using?
frsky archer rs with fw 2.1.8 (latest on the frsky webside)


>Which version of OpenTX?
2.3.11 (which i belive is the latest stable)

>Ideally, could you post a pic of how your RX is wired to the Spirit?
RX sbus_out > spirit sbus cable > spirit rud port
RX s.port > spirit frsky cable > spirit sys port (fport/fport2 disabled in the rx settings, which means "old" s.port is enabled)

telemetry and controls work, so i think cabling is working correctly

>Are you sure the tail servo is correctly declared in the Spirit Setup (neutral, narrow-band, etc...)?
spirit software limits tab, tail is set to near the max mechanical way:


tail operated with the TX:

opentx servo monitor shows +-82.8, spirit diags show this as -+100.

also attached my opentx model for that heli, but it is nothing fancy: