Receiver
SBUS
output
The
CROSSFIRE
8ch
diversity
receiver
as
well
as
the
CROSSFIRE
micro
receiver
support
SBUS
and
n.i.SBUS
(non-inverted)
respectively.
The
diversity
receiver
exposes
this
functionality
on
output
port
8,
selectable
via
the
output
port
mapping
menu.
The
micro
receiver
only
has
one
output
port,
and
it
is
either
PWM,
PPM,
SBUS
or
n.i.SBUS
capable.
The
setting
for
this
is
also
available
via
the
output
port
mapping
menu.
Receiver
RSSI
or/and
LQ
output
To
get
digital
(PWM)
RSSI,
LQ
(Link
Quality)
or
RSSI/LQ
output
for
use
on
OSD
and
similar
equipment,
pick
a
free
channel
and
set
the
output
to
signal
type
you
need.
You
can
also
output
one
of
those
signals
by
injecting
it
into
the
PPM
stream
for
processing
on
an
OSD
or
FC.
Use
the
“PPM
Mapping”
menu
for
this.
Beside
of
RSSI
the
receiver
can
also
output
link
quality
(LQ)
or
a
combined
value
(RSSI/LQ).
The
RSSI/LQ
value
will
always
show
the
worse
value
of
both.
This
is
mostly
useful
if
the
used
OSD
only
has
one
input
for
link
statistics.
It
will
show
you
an
estimation
for
your
range
based
on
RSSI
but
you
will
also
see
if
the
LQ
drops
when
you
have
bad
reception
because
of
interference
or
any
other
reason.
Serial
bridge
The
bridge
feature
gives
you
the
ability
to
pass
any
kind
of
serial
uart
data
from
any
device
connected
to
the
receiver
to
any
device
connected
to
the
transmitter.
If
you
select
“Bridge
TX”
on
output
8,
then
output
7
will
automatically
change
to
“Bridge
RX”
and
channel
6
to
“Bridge
RTS”.
Please
connect
your
device
according
to
this
information.
The
baudrate
is
set
to
57600
8N1
and
the
voltage
level
is
3.3V
only.
The
RTS
pin
will
change
to
logical
high
when
the
internal
FIFO
is
almost
full
and
low
if
the
FIFO
is
almost
empty.
There
is
no
hardware
flow
control
for
the
uplink
as
the
wireless
close
range
telemetry
module
does
not
support
it.
The
app-link
mode
on
the
TX
will
automatically
change
to
bridge
on
the
first
few
bytes
sent
down
from
the
receiver
if
the
mode
is
not
set
to
“OFF”.
MAVLink
MAVLink
is
a
very
lightweight,
header-only
message
marshalling
library
for
air
vehicles.
Most
of
the
common
flight
controller
support
MAVLink
message
format.
For
specific
message
documentation
please
refer
here:
MAVLink
Messages
If
you
select
“MAVLink
TX”
on
output
8,
then
output
7
will
automatically
change
to
“MAVLink
RX”.
There
is
no
hardware
flow
control
required
as
we
support
software
flow
control
(RADIO_STATUS
message)
on
both
ends.
You
can
connect
it
to
any
telemetry
port
of
a
MAVLink
compatible
FC.
The
MAVLink
baudrate
is
set
to
57600
baud.
The
MAVLink
TX
pin
(output
8)
needs
to
be
connected
to
the
FC
telemetry
RX
pin
and
the
MAVLink
RX
pin
(output
7)
need
to
be
connected
to
the
FC
telemetry
TX
pin.
The
app-link
mode
on
the
TX
will
automatically
change
to
MAVLink
on
the
first
frame
sent
down
from
the
receiver
if
the
mode
is
not
set
to
“OFF”.
28