New to FrSky - Archer S.Port, SBUS, and F.Port usage/configuration

[doug35]

I'm looking to switch to FrSky (X20s) from Futaba, but am still trying to figure out the rx options before I order.
I need to use SBUS to connect to my existing Aura5 FC's , but I also want to take advantage of FRsky's sensors, like the FLVSS voltage sensor. It looks like F.Port should do both, so can I reconfigure either the existing S.Port or SBUS ports on an Archer Rx to operate as an F.Port? Specifically, I am looking at either SR6 or SR8 Pro recievers and would prefer not to have to make adapters to connect other devices.

 

[Wayne]

Doug,
Think you will be best with Sbus as I doubt the Aura5 will speak F.port just yet..? So with the receiver in Sbus mode, you also have an S.port for the sensors. This is how the receivers are configured stock, so all ready to rip.

Hope this helps.

 

[gnichola]

@doug35 if I were doing it now, I would go with an RS, as long as you can solder since I am not sure the pins come pre-soldered. The FLVSS, which I am a super fan of will connect right into the Smart port, and the SBUS out will go to your Aura. For the FLVSS I am also a fan of soldering on an appropriate connector as I have plugged one in incorrectly before. https://www.digikey.com/en/products/detail/jst-sales-america-inc/B7B-XH-AM(LF)(SN)/1651033

 

[HENNY]

Doug. In order for you to use F.Port the flight controller would need to be aware of F.Port. F.Port is really aimed at the drone guys ( BETA FLIGHT) where they want one connection to the receiver / FC which covers S-Bus and F-Port in a single three wire connection. I agree with Wayne and don't believe the Aura 5 FC supports this. So Frsky external sensors such as the FLVSS are connected in a daisy chain, again connected between the receiver and sensor using a standard servo style connector/cable. This supplies power and has a single wire in a bi directional data connection to the sensor. Each sensor has its own ID which the receiver addresses in a round robin to gather data and transmit it back to the transmitter. At the Transmitter side this data can be configured in a number of ways to either operate a voice warning or simply use the voice to tell you a voltage current or alt depending on which sensors you have on the aircraft. I understand the FRsky S-bus is structured on the Futaba S-Bus so there should be not issues there.

I have the X20S and the Horus X10S. I like both radios their operation are similar but different and it will take you some time for your brain to switch from Futaba to FRsky / OTX way of setting up a model. The X20S wizard is actually very good and will help you to get started. The FRsky radio / model setup takes a bit more effort but gives you much more flexibility in the end.

There is a 153 page PDF manual for Ethos on the Github with a link on the FRsky web site.

Hope it works for you.

 

[doug35]

Doug. In order for to use F.Port the flight controller would need to be aware of F.Port. F.Port is really aimed at the drone guys ( BETA FLIGHT) where they want one connection to the receiver / FC which covers S-Bus and F-Port in a single three wire connection. I agree with Wayne and don't believe the Aura 5 FC supports this. So Frsky external sensors such as the FLVSS are connected in a daisy chain, again connected between the receiver and sensor using a stand servo style connector/cable. This supplies power and has a single wire in a bi directional data connection to the sensor. Each sensor has its own ID which the receiver addresses in a round robin to gather data and transmit it back to the transmitter. At the Transmitter side this data can be configured in a number of ways to either operate a voice warning or simply use the voice to tell you a voltage current or alt depending on which sensors you have on the aircraft. I understand the FRsky S-bus is structured on the Futaba S-Bus so there should be not issues there.

I have the X20S and the Horus X10S. I like both radios their operation are similar but different and it will take you some time for your brain to switch from Futaba to FRsky / OTX way of setting up a model. The X20S wizard is actually very good and will help you to get started. The FRsky radio / model setup takes a bit more effort but gives you much more flexibility in the end.

There is a 153 page PDF manual for Ethos on the Github with a link on the FRsky web site.

Hope it works for you.

Thanks! My X20s and archer receivers are supposed to show up sometime tomorrow, so I am excited to dig in. Hopefully work is slow this week so I can focus on getting a couple of planes configured before the weekend.

 

[HENNY]

Thanks! My X20s and archer receivers are supposed to show up sometime tomorrow, so I am excited to dig in. Hopefully work is slow this week so I can focus on getting a couple of planes configured before the weekend.

Doug If you are purchasing from Aloft they will load the latest firmware on both the TX and RX. This working with firmware is something some people hate but I actually welcome it. It gives you new features all the time, if you are a bit bent on getting the best from your purchase.

 

[doug35]

My X20s arrived today! FedEx took their time getting it here, but I have bound one Rx and updated the firmware packages that released while it was in transit.
I'm impressed so far. Hopefully I can get a couple of planes configured with the basics and ready to fly for Saturday.

 

[Wayne]

Should be pretty easy.. Everytime I play with the one here at the office I come away impressed. She pretty much lives on my desk now.