Good Morning

I quote myself!

It's now working with a R-XSR Archer receiver, firmware 2.1.7

Ethos 1.4.7 / X10s express
Spirit GT with software version 3.4.4

Wiring
Receiver Spirit GT
GND. GND
VIN. VIN
S-Port Rudder Input

I changed the receiver type in the spirit to FRSKY-Fport und changed in the transmitter in receiver setup to Fport.
The receiver has the green and blue LED on.
The integration of the LUA script is working now.

Telemetry not yet tested. I need to reprogram my HW platinum 120a ESC for governer mode via Spirit, but I have to order the ESC programmer first.

Have a nice day

Good Morning

Could anybody provide the wiring for the Archer RS receiver with Spirit GT.

Thanks

Hello,
FPort-Connection see below:




Regards

Thanks

So it is exactly the same wiring as with the R-XSR receiver. Then I have to change my soldering on the archer. I took the inverted S.Port instead of the normal S.Port.

Hello,
first test with FBus-Protocol (Special Firmware) on an Archer R8 Pro in connection with an Spirit GT and an Horus X10S Express transmitter with ACCESS and Ethos 1.47 -
Some channels are exactly at 100 some others need 104,5 to get 100 in Spirit Settings-Software -
The telemetry is working flawless without any drop outs or Sensor lost message !
With the FBus-Protocol the integration is also working flawless -
The connection works via SPort Output (Archer R8 Pro) and the Spirit GT over the Rudder-Port (Striaght Cable) -
That sounds very promising !!
The next I will test is to make an redundancy receiver, here Archer RS, to the Archer R8 Pro - I hope this will work too because that is what I want to have for my 700 Heli (Specter 700 V2 NME) - But this maybe not until the weekend, but I will see -

Regards

Thanks a lot for your infos!

The Archer RS receiver is now working too

I hate to disagree with the guy that developed the Spirit System, but this is inaccurate.

I have a Tarot 450 heli running with a Spirit 1 and it's connected to a FrSky R9MM OTA. This is a 900Mhz. It is connected to the Spirit via S-BUS, and S.Port protocol (see the first post in this thread). I have full integration, even though it's running S-BUS and S.Port, since there is no F.Port support for the 1st generation Spirit FBL.

I'm not sure where this "not allowed by FrSky" is coming from, but obviously it's not correct.

So this is still more of an issue with particular receiver units, rather than "It's not allowed". Yes, it works more reliably, or rather with more receivers via F.Port, but it doesn't mean it won't work with S-BUS and S.port. It's likely the LUA code work more "universally" over the F.port & .BUS protocols, whereas S-BUS and S.port are more picky

Hello,

this is very good. FrSky told us that S.Port is not supported for EthOS and integration.
We know that it works with some receivers but we dont know if this support will still work in the future.
We hope that yes. The list of tested receivers could be great.

_________________
Spirit System developer

I was flying today with SPIRIT GT and FW 3.4.5 rc2 / Geolink V2.
connected over FBus on Frsky XE with Ethos 1.4.7 and receiver TD -R10
additinal Sensor Frsky FAS100 ADV (used only both temp sensors)

I have had no problems, everthing works fine for me. No sensor confict or sensor lost warnings, Flytime 18 min.
Next time i test Geolink Functions Alt Hold and Pos Hold.

Thank you Tomas for your work on ETHOS and FBus

Bye
Jörg