Advertisement
Output SBUS, CRSF or PPM on receiver
By selecting the "Crossfire RX" / "TBS CROSSFIRE RX" or "TBS CROSSFIRE Diversity RX" in the configuration
menu, you can change the output mapping, including the signal format on each pin (SBUS, CRSF, PPM).
Enter the configuration menu and
under "Crossfire RX", pick "Output
Map"
Difference between SBUS and CRSF
SBUS is a high frequency one way communication protocol, up to 150 updates per second (Hz). While our
TBS CRSF (CROSSFIRE) is a two-way, low-latency, error detection, communication protocol which allows
uplink- and model-telemetry (via BST to RX) to be carried back to the remote control.
At the moment the CRSF protocol is supported by the following flight controllers (FC):
•
KISS
•
Betaflight
•
Raceflight
•
iNav
Wiring CRSF to flight controller
Since the CRSF protocol is serial, it has to be connected to a free serial/UART port on a supported flight
controller. On the COLIBRI RACE it must be UART3. If you use the POWERCUBE with FPVision, you can use
also use UART2. The pin-out and wiring layout is shown in the following table.
CROSSFIRE MICRO
V1 RX
Ch./Pin 1 TX
Not available
This lays out all the physical pins
and their source signal format.
CROSSFIRE MICRO
V2 RX
Ch./Pin 1 TX, 5V,
GND
Ch./Pin 2 RX only
CROSSFIRE
DIVERSITY RX
Ch./Pin 8 TX, 5V,
GND
Ch./Pin 7 RX only
4
Pick a output to change. PPM can
be selected in all channels, while
SBUS, CRSF and Serial is restricted
to output 6, 7 and 8.
Clean-/BetaFlight Serial
port (COLIBRI or other)
UART2 or 3 RX, 5V, GND
⇒
UART2 or 3 TX
⇐
Advertisement
