FrSky ETHOS Xact Servo FBUS Daisy Chain Programming and Configuration for Y-Cable Connections

A quick example to show how two XACT servos are programmed by FBUS to :
CH2 for Elevator
CH4 for Rudder
First I have programmed the TD R18 to have FBUS on Pin18 by way of [RF System] - [Set] - [Options]
The servos are connected individually and programmed with different Physical ID and Application ID and the channel set to the corresponding channel. Click 'Save to Flash' to set the servo settings permanently.
Then the servos are connected by a Y-cable to the same Pin18 and are able to operate independently on their assigned channels.
This allows for simple wiring connection by way of Y-cables to connect the [Elevator + Rudder], [Left Aileron + Left Flap] and [Right Aileron + Right Flap] to simplify the wire management.
Note: At 1:47 I say "Aileron" but I meant "Elevator"

[@jjames5928]

This dosnt draw to much current through the Y cable ?
I mean like if your using them on say a 3D plane or large scale with fast movments or high torque can the wire handle the current going to 2 servos ?

[@airman9820]

I would run 4 servos on my warbirds with one lead when I used to fly jr xbus. So I would assume it would be no problem with the x20.

[@mohfar6197]

What is the Application id option? Should I choose a random number?

[@frskyrc-ben]

Each sensor may have multiple Application IDs, one for each sensor value being sent.
The Physical ID and the Application ID are independent and unrelated. For example the
Variometer sensor has just one Physical ID (default 00), but two Application IDs: one for
Altitude (0100) and the other for Vertical Speed (0110).
Another example is the FLVSS Lipo Voltage sensor, which has a Physical ID (default 01),
and an Application ID for Voltage (0300). If you want to use two FLVSS sensors to
monitor two 6S Lipo packs, you will need to use Device Config to change the Physical ID
of the second FLVSS to an empty slot (say 0F hex), and also to change the Application ID
from say 0300 to 0301. Because the Physical ID and the Application ID are independent
and unrelated, both must be changed. The Physical ID must be changed for exclusive
communication with the host receiver, and the Application ID must be changed so the
receiver can distinguish between the data from Lipo 1 and 2
This information can be found on the Smart Port telemetry
section of ETHOS manual (pages 221-222 on v1.5.12 manual)