Spirit archeraRS
RUD - ----> GND
RUD+ ----> VIN
AIL PIN ----> Inv-S.Port

So the Inverted S.Port, became an Inverted F.Port when you selected F.Port in the receiver configuration? That's great. That will simplify wiring dramatically, because the way it is right now on my Spirit Pro with the integration cable and additional power, it's pretty messy. I think I may get a couple more Archer RS receivers.

I have a R-XSR handy, which has Inverted port pads, so I'll give it a try first, on my other heli with Spirit II.

yes, i do it this way since the first day on SPort for telemetry and now for FPort

I hope today we will have new firmware with full F.Bus support.
Looks very promising. Also big change is that you no longer need to adjust end points for FrSky. It will be matching directly out of the box with +/- 100%.

_________________
Spirit System developer

That are great news.
Thank you for your efforts to get FrSky FBUS receiver running

Anybody interested in FBus can send me private message with serial numbers of his units.

It should work with all units, except Spirit 1.

_________________
Spirit System developer

Hello Tomas,
i have download the 3.4.5 FW. Thanks a lot.
My Hardware: Frsky XE with Tandem TD-R10
Ethos Version 1.4.6
No FrSky or other sensors at the moment.
I have connected the FBus with stright cable to connector RUD on SPIRIT GT.
I have to adjust the end points of the channels a little bit between 98 and 102. It is much better than in 3.4.4!
I get no warings of sensor conflict and no warnings of sensor lost.
I am running the config about 25 min.
Thanks you very much for your work, it seems that every thing is ok for me.
Next step i will try to connect an additional Frsky sensor. The sensor is called RPM and gives me two temps.

Bye
Jörg

That is great. It should work properly also with SPort regarding telemetry.

_________________
Spirit System developer

No, it does not work without problems.
I have connected the sensor to the TD-R10 to another slot Pin9.
The slot Pin9 of the receiver is defined as S.Port.
I immediately get a Seonsor conflict, although I have not even looked for the new sensors.
I have just ordered a Frsky sensor FAS 100 ADV.
This sensor also has two temperature outputs and I will test it with this one, it is a new FBus Sensor.
I will report when I have news


Ciao
Jörg

Sensor must be FBus. SPort sensors will not work as they dont understand FBus.

_________________
Spirit System developer

I have made a list of all sensors:
Perhaps the Problem is the second U/min sensor with appId 500 and pysId 0x6.
This one and the Temp. 2 and Temp. 1 are coming from the Frsky RPM sensor ( the last three items)
The first U/min sensor has also appId 500 but pysId 0x03 ( SPIRIT GT)
I do not know how to change the appId address

Jörg