Ethos 1.5 Series User Manual

Ethos v1.5.7 and X18, X20 series User Manual
Application ID
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.
Device Application ID
(hex)
Parameter
Vario 010x Altitude
011x Vertical Speed
FLVSS Lipo Voltage Sensor 030x Lipo Voltage
FAS100S Current Sensor 020x Current
021x VFAS
040x Temperature 1
041x Temperature 2
Xact Servo 680x Current, Voltage, Temp,
Status
Above are a few example Application IDs. Please note that the Application ID parameter
in Device Config presents a drop-down list of 4 digits to choose from; the default 4
th
digit
is 0, but may be changed in a range of 0 to F hex (0,1,2,3,4,5,6,7,8,9,A,B,C,D,E,F) to
ensure that all Application IDs are unique.
Please also note that:
a) A device may have more than one range of Application IDs, see for example the
Current Sensor above.
b) Where two redundant receivers have their S.Port telemetry ports connected, then
packets for a particular sensor received by either receiver will be merged even if the
redundant receiver is on a different band or module.
S.Port key features:
Each value received via telemetry is treated as a separate sensor, that has its own
properties such as
 the sensor value
 the S.Port Physical ID number and Data ID (aka Application ID)
 the name of the sensor (editable)
 the unit of measurement
 the decimal precision
 option to log to the SD card or eMMC
The sensor also keeps track of its min/max value.
As already mentioned more than one of the same sensor type can be connected, but the
Physical ID must be changed in ‘Device config’ (or using the FrSky Airlink App or SBUS
servo changer SCC) to ensure that each sensor in the S.Port chain has a unique Physical
ID. Examples are a sensor for each cell in a 2 x 6S Lipo, or monitoring individual motor
currents in a multi-motor model.
209 rev 2

Ethos 1.5 Series Specifications

General

Brand	Ethos
Model	1.5 Series
Category	Remote Control
Language	English