TBS CROSSFIRE R/C System Revision 2021-10-14 Adaptive Long Range Remote Control System The TBS CROSSFIRE (XF) system is an R/C link system made for FPV enthusiasts. It features unheard-of range without sacrificing basic functionality such as being immune to interference from onboard equipment, low latency control, or two-way communications including telemetry functionality.
Table of content Attention Getting ready FAQ Note Updating Hardware overview Standard TX pinout Radio connection JR-bay radios Other radios RC input Signals Antennas Antenna cover Adapter boards FrSky inverter mod Which transmitter is affected by this? How to install the inverter mod Software mod General functions Binding General note/ model match When do I need to bind again Binding issue - Double green flashing Binding issue - OpenTX 2.3.
Failsafe setup General setup Cut Failsafe position Transmission frequency Transmission power RF power switch Operating modes Transmitter LED status indicator Receiver LED status indicator MyVTX (available up to FW 4.XX) VideoTX (Since FW 6.03) RC by MAVLink Team Race Special functions - Standard/ Lite TX only External power Status display Up- and downlink status Oled Menu Find mode Real-time telemetry by Bluetooth Head-tracking Receiver functions Output map CRSF Serial SBUS N.i.
DSMX RSSI LQ RSSI/LQ SmartAudio Channel number RF Profile Telemetry Available sensors with OpenTX Missing sensors In-built Voltage monitoring BST connection Additional information TBS CLOUD Menu Initiate the WiFi module Connection to a WiFi hotspot OpenTX setup for CROSSFIRE LQ warning in OpenTX Model match in OpenTX (and FreedomTX on TANGO 2) VTX connection by CRSF VTX connection by SmartAudio SmartAudio or CRSF for the VTX? VTX button not working Connection to an FC General wiring CRSF with BetaFlight and
Wireless configuration with ArduPilot/ PX4 by Bluetooth Wireless configuration with ArduPilot/ PX4 by WiFi Wireless telemetry Bluetooth WiFi WiFi telemetry with BetaFlight/ iNav Wireless configuration with BetaFlight/ iNav by Bluetooth Signal strength in BetaFlight - BF < 4.1 and DJI OSD Signal strength in BetaFlight - BF 4.1 and later CLI commands Signal strength in iNav - iNav < 3.xx Signal strength in iNav - iNav 3.
Specifications Type: Long Range Two-Way Remote Control System Band: Europe: 868 MHz SRD Band America: 915 MHz ISM Band RF power Radio Signal & Telemetry downlink: Micro TX V1: Selectable 25mW to 250mW, V2: Selectable 25mW to 1W Standard/ Lite TX: Selectable 10mW to 2W diversity, Micro and Nano RX: 40mW Receiver sensitivity: Up to -130dBm Antenna: TX: 1x omnidirectional dipole antenna RX: depends on the receiver type (U.
Attention These Long Range Systems are capable of radio frequency transmissions and output power that may be not allowed in your country. Please always check your local RF legislation to set the frequency and output power according to the regulation. A general rule for RC aircrafts is that they must be controlled always under sight of view, check your RC regulation to keep up to date with regulations. Getting ready Getting set up and ready to fly is a quick and simple task.
Hardware overview The following diagram indicates the essential inputs and features of the transmitters and receivers.
Micro transmitter module (V1 + V2): The Micro TX V2 has the same features and layout as the V1 but with a USB-C connector Nano transmitter module : The Nano transmitter includes the same internals and functions as the Micro TX V2. It is designed to fit into the mini-module bay of newer FrSky radios, TANGO 2 module bay, and any other radio with the mini-module bay. If you already own a Micro TX V2 you can get a retro-fit set to change the housing from JR-style to Mini module style.
Micro receiver: Nano receiver: 10
Nano receiver PWM version: This RX is the same as the Nano RX but with 6 servo connectors installed. This Saves you the need for the PWM adapter board.
Sixty9 (FW 6.04 or later required): The Sixty9 can not yet be controlled by SmartAudio! If your FC firmware supports VTX commands by CRSF, it can be done by the main CRSF connection (e.g. KISS). Otherwise, setup can be done by the CROSSFIRE Sixty9 menu or VideoTX menu via Agent X/ M/ Lite.
Wiring example: #Todo: bild SmartAudio am fc 13
Mounting: 30.5x30.5 20x20 Direct mount, double-sided tape Be sure to fasten with an additional zip tie, or bolt down the case with provided Phillips screws.
Standard TX pinout Radio connection JR-bay radios If you use a radio with a standard jr-bay style module bay, you can easily plug the CROSSFIRE transmitters into them.
JR-bay issue When you have set up everything properly in OpenTX but your module still stays off, the radio pins did not slide into the CROSSFIRE TX. In this case, you can bend all the pins in the JR bay just a little bit to the right or left side and plug the module bag in. Other radios If you own a radio without a JR-bay, you need to use the Standard/ Lite transmitter with their input pins for many trainer-port connectors, which you then connect to the RC In plug.
Futaba-cable Custom PPM cable 17
RC input Signals Depending on the remote and firmware you use, there are different input protocols available: ● PPM ● CRSF V1/ 2/ 3/ CRSFShot In Agent X/ M/ Lite the detected signal can be found under Transmitter/ About/ RC Input PPM PPM should only be used with radios not supporting CRSF. It got a high latency and no telemetry CRSF V1/ 2 CRSF enabled telemetry since version 2 and runs with low latency. CRSF V2s The s indicates that the lower communication speed has been enabled in the radio.
Antennas You got a big variety of antennas for your transmitter and receiver. The antennas that come with your devices work fine and don’t need to be replaced in general. Depending on your environment, your drone, and your purpose, you can change them anyway. Here are some of them: Flexible antenna MicroVee antenna PCB Race antenna Other antennas can be found at the TBS webshop or premium antenna suppliers such as VideoAerialSystems.
Antenna cover If you order your CROSSFIRE transmitter after mid-2020, you will notice a cover over the antenna. The antenna can be turned by 90° (both directions) to align it with your receiver antenna. If you want to use a different one or just detach it after the flight, you need to unscrew the cover and break it.
Adapter boards There are many ways of installing the CROSSFIRE RX into a model like these mounting boards: On some of them, you can connect a Unify Nano32 with the CROSSFIRE receiver and use the CRSF connection to control the VTX. FrSky inverter mod When you receive your CROSSFIRE transmitter, there is a small inverter chip included.
Which transmitter is affected by this? The older QX7 radio from FrSky with the S-Port pin at the bottom of the radio. Newer ACCESS radios and older radios than the QX7 (with bottom S-Port pin) don’t need this hardware mod. How to install the inverter mod There is a detailed how-to available at phillip seidels blog Software mod Instead of installing the hardware mod, you can simply lower the speed at which the radio communicates with your radio.
General functions Binding Binding a receiver to your CROSSFIRE is an easy task and does not require 3 hands or any special jumpering. General note/ model match You will notice that you can control any r/c model, even if you changed the model in your radio*. This is caused by the fact that the CROSSFIRE does not monitor the radio model. This means you have to make sure that you selected the right model in your radio before you power up the receiver.
up a model number. In this case, just change it back to 00 and your receiver should be bound again. Transmitter First, you need to set your transmitter in bind mode. For this you got a variety of options, depending on the radio and transmitter type you use: Agent L (OpenTX radio only): TBS TANGO 1: 1. Turn on your radio 1. Turn on your radio 2. Navigate to the CROSSFIRE Lua script and 2. Hold the rocker switch to enter the main execute it menu 3. Open the CROSSFIRE Transmitter 3.
Receiver After your transmitter is in bind mode, you need to do the same with the receiver. This procedure is the same for all receiver types available: 1. Power up the receiver 2. Within 1 minute, push the bind button on the receiver Receiver Update (OTA) Depending on the firmware on your transmitter and the receiver, you might need to update your receiver.
After the update wait for Agent X to synchronize the device with your TBS account. This is done when the dot on the top of the device turned green Connect your CROSSFIRE to the internet via the built-in WiFi module. You can provide access point information from your nearest WiFi hotspot, or create a temporary one on your phone. Wait for it to switch to “Online” under XF WiFi/ About After a few seconds, you can navigate back to XF Transmitter/ About. Now you should see your user id.
Binding ● ● ● If you’ve got a bound receiver, just bind/ update it with Multi-bind turned off, and while it’s connected turn Multi-bind on. Wait for a few seconds, then the link will come back again. On a new receiver, you can just bind it by the button as usual. On the other CROSSFIRE TX, just enable “Multi-bind”. When the first TX is shut down, you can power up the second transmitter. It should bind to this receiver within a few seconds.
Real-world example The most common combination is that you already own a CROSSFIRE transmitter to which all your receivers are bound and now you have a second transmitter like the TANGO 2. Here is how you get them both running with Multi-bind, assuming that you already got your user id on both transmitters: 1. Make sure both radios got the same firmware version 2. Power up your “old” transmitter and make sure Multi-bind is turned off for now 3.
Failsafe setup The TBS CROSSFIRE supports two failsafe behaviors: cut and failsafe position. Setting them up correctly is crucial for the safety of your model. General setup The failsafe setting is located in the receiver menu. To change the behavior: 1. Navigate in the receiver menu by your radio/ Lua script/ Agent X 2. Open the General menu 3. Change the FS.
Standard/ Lite TX shortcut For these two transmitters you can run a shortcut to set the failsafe position: - Set the sticks and switches, in the position you want them - Push the joystick down - Push and hold it up for a few seconds - Failsafe Set will appear Failsafe test When you have set up or changed the failsafe behavior, it’s important to test the correct function on the ground. To test it: 1. Remove the propeller of your aircraft 2. Power up the radio and the model 3.
Transmission frequency CC Wikipedia The TBS CROSSFIRE supports two different frequency bands, depending on your local regulation. Below is a general overview of the primary frequency segmentation.
You can choose between several frequencies: Frequency Setting Frequency Max.
Transmission power The transmitter’s RF output power is highly configurable and can be selected dynamically via the menu. With 100mW you can achieve 15 km of safe range in rural conditions. It is recommended to use the dynamic power option. This will allow you to fly at very low power and the system will increase the power automatically (faster than you can hit the power switch yourself) if you are about to lose the link.
Dynamic transmission power The system can automatically choose the power level most suitable for the situation at hand. For instance, if you fly close to the transmitter you normally only require minimal TX power and the system will therefore switch to the lowest possible TX power level required to maintain a good up-link. The maximum TX power level the system is allowed to use can be defined by changing “Max Power” in the configuration menu. RF power switch Since FW 6.03 you can select the max.
Note: Forced Telemetry is not meant to be used in normal conditions. The best practice is to not use it. Transmitter LED status indicator The RGB LED on the transmitter gives you at any moment an indication of your link status.
MyVTX (available up to FW 4.XX) With the MyVTX menu, you can set all your VTX’s to the same channel, band, and output power without accessing all of them. This is useful if you are on a race with multiple drones and have to set them all to the same channel. If you enable MyVTX, all other VTX settings will be overridden temporarily, till you disable it again.
VideoTX (Since FW 6.03) The Video TX menu is the successor of MyVTX. The function behind it remains the same: it allows for a global VTX setup without the need to set up each drone by itself. As soon as the drone powers up, the settings will be applied to the VTX. As with MyVTX, the VTX must be connected directly to the CROSSFIRE receiver by SmartAudio, CRSF, or by a KISS FC.
RC by MAVLink If you use MAVLink to connect to your FC, you can send your RC data over the same connection. Depending on the MAVLink version used in your FC, you can send up to 12 channels by this (MAV V2) or 8 (MAV V1, used on CROSSFIRE FW below 3.8). As there are some rumors around: - The RC data will not stop being sent if the CROSSFIRE telemetry breaks up - It’s as fast/ a bit faster than SBus Team Race When on a team race or using multiple drones on the same run, you can use the team race menu.
Special functions - Standard/ Lite TX only External power Your Standard/ LIte TX can go up to 2W transmission power. If your Radio can not handle the current for this or you don’t want to drain your radio battery as fast you need to attach an external battery to the XT30 connector. You can use any 2(1) - 3S LiPo for this. To make sure the CROSSFIRE uses the external battery, the voltage needs to be higher than the voltage in the JR bay. Mostly the supply voltage in the bay is the same as your radio battery.
Oled Menu When you scroll to the left/ right, you can see the other diagnostic screens, showing you information of your link, etc: Find mode The Find-mode provides you with a way to locate a downed aircraft. A GPS signal is currently required to use this mode. Install our TBS GPS module by BST or any other GPS, connected to a flight controller. In normal use, the GPS coordinates are continuously updated and the latest data is displayed on the “Find mode” screen.
certain trigger events have happened. See the operation flow diagram attached on the following page. Direction finder Using the transmitter antenna together with a DIY parabolic reflector, you can estimate the heading of the receiver by looking at the signal strength indicator. Use this option only if the GPS position is inaccurate or you don’t have a GPS connected. How does Find mode work? Please see the flowchart to see when the receiver decides to shut down or enter Find mode.
Preparations The Find mode needs to be armed before it will take any action. ● Receiver only: ○ ● Receiver with GPS: ○ ● Power up the receiver and transmitter and make sure they are connected. Make all steps above and ensure the GPS is having a solid sat lock. Receiver with GPS and TBS CORE PRO: ○ Make all steps above and simulate a takeoff. This can be done throttle above 3A or walking your receiver until you see the takeoff message on the OSD.
Link regained Once you got your link back to your copter/plane you can now try to find it. It’s recommended to keep the mode you got your signal back no matter if it’s in Find mode or selected operation mode. ● GPS source attached to a receiver ○ The receiver will share the latest coordinates with the transmitter and display them on the OLED.
Real-time telemetry by Bluetooth The Standard TX (not the Lite version) got a built-in Bluetooth module that you can use for real-time telemetry or wireless configuration of your FC. Depending on the incoming data, the CROSSFIRE selects the Mode for the Bluetooth module for you.
Head-tracking The standard TBS CROSSFIRE transmitter supports standard head-tracking input via the right 3-pin HT port. Solder the included pigtail cable to suit your particular head-tracking setup. Only a two-wire connection between TBS CROSSFIRE and the head-tracker is required. The PPM feed from the head-tracker needs to be connected to the PPM pin of the PPM pin and ground needs to be connected to ground of the 3-pin PPM cable. The status display will indicate if the signal has been recognized properly.
Receiver functions Output map On all receivers, you can select what it should output on which pin. The available options for each differ for the receivers: Note: since FW 6.0 the PWM output map has changed. The older options are in brackets: Receiver pin Output type diversity RX (standard) Default 1 PWM CH1 (PWM Ch1 to 12), PPM, RSSI, LQ, RSSI/LQ PWM Ch. 1 2 PWM CH2 (PWM Ch1 to 12), RSSI, LQ, RSSI/LQ PWM Ch. 2 3 PWM CH3 (PWM Ch1 to 12), RSSI, LQ, RSSI/LQ, SBUS, n.i.
Receiver pin Output type Micro V2/ Nano RX/ 6Ch Nano Pwm RX/ Sixty9 Default 1 PWM CH1 (PWM Ch1 to 12), PPM, RSSI, LQ, RSSI/LQ, SBUS, n.i. SBUS, CRSF TX, MAVLink TX, SmartAudio*, DSMX CRSF TX 2 PWM CH2 (PWM Ch1 to 12), RSSI, LQ, RSSI/LQ, CRSF RX, MAVLink RX CRSF RX 3 PWM CH3 (PWM Ch1 to 12), RSSI, LQ, RSSI/LQ, CRSF RX, MAVLink RX PWM Ch. 3 4 PWM CH4 (PWM Ch1 to 12), RSSI, LQ, RSSI/LQ, SBUS, n.i.
N.i. SBUS Not inverted SBUS is the same as SBUS except that the signal is not inverted. This can be used for FCs that have no signal inverter built-in and require SBus as input signal. MAVLink MAVLink is a very lightweight, header-only message marshaling library for air vehicles. Most of the common flight controllers support the MAVLink message format.
LQ Translates the Link Quality from 0 -100% to a PWM signal from 1000µs to 2000µs. This can be used for old-style OSD’s with only analog RSSI input. In 150Hz mode, the LQ indicator will remain at 100% as it’s not relevant to monitor it in the mode. RSSI/LQ Combines the LQ and RSSI and translates them from 0 -100% to a PWM signal from 1000µs to 2000µs. The RSSI/LQ value will always show the worse value of both SmartAudio SmartAudio is a protocol developed by TBS for OSD to VTX communication.
Channel number The transmitted number of channels. Can be set to 8 or 12 channels. Use the 8 channels setting whenever you can. This ensures the best performance for your RC link. RF Profile Lock the CROSSFIRE to a fixed frequency or let it select it by the quality of the link. ● Dynamic: The CROSSFIRE selects the RF profile due to the internal algorithm based on the quality of the link. It will switch between 150Hz on ideal conditions and 50Hz when the link is no longer perfect.
Available sensors with OpenTX With an OpenTX based radio you can receive the following sensors, depending on your connected hardware: Datapoint Description Data source 1RSS Uplink - received signal strength antenna 1 (RSSI) TBS CROSSFIRE RX 2RSS Uplink - received signal strength antenna 2 (RSSI) TBS CROSSFIRE RX RQly Uplink - link quality (valid packets) TBS CROSSFIRE RX RSNR Uplink - signal-to-noise ratio TBS CROSSFIRE RX RFMD Uplink - update rate, 0 = 4Hz, 1 = 50Hz, 2 = 150Hz TBS CROSSFIR
Missing sensors If you got issues finding sensors or only a few appear, make sure you disabled Ignore Instances in the telemetry settings page of your radio In-built Voltage monitoring The CROSSFIRE receivers are capable of measuring the voltage of their power supply. This becomes handy when you use an RC glider where space matters. This feature works on up to a 2s LiPo (max. Operation voltage for all receivers!) for almost all receivers, except for the Nano RX rev 43 and lower.
If you own a Nano RX, there is no longer the complete BST plug available on it. In this case, just connect SCL to SCL and SDA to SDA on all devices.
Additional information TBS CLOUD All TBS CROSSFIRE transmitters and the FUSION video receivers include a built-in WiFi module that allows you to connect all your gear through the TBS CLOUD. This allows using features like VTX follow, dynamic VTX power with a FUSION module, and other upcoming features.
● About ○ WiFi: name of the WiFi hotspot/ Network your CROSSFIRE is connected to ○ IP: IP address the CROSSFIRE module was assigned by the WiFi network ○ Server: connection status ○ firmware: the version number of the WiFi firmware ○ Hardware: hardware revision of the WiFi module ○ Bootloader: the version number of the WiFi Bootloader firmware ○ Serial Number: serial number of the WiFi module Initiate the WiFi module To use the CLOUD functions, you need to initiate the WiFi module first: ● D
Connection to a WiFi hotspot Once your WiFi module is initiated, you can now connect to an external hotspot. The easiest way is to connect it by the Web-UI: ● Connect the CROSSFIRE TX to your radio and power it up ● On your PC or phone search for a new WiFi network like “TBS_XF_AP_xxxxxx” ● Connect your pc/ phone with this network. On Windows machines, this can take up to one minute ● Open your browser and enter IP in the address bar: 192.168.4.
Using CRSF will give you the lowest possible latency from your stick to the drone and full telemetry back to your radio. LQ warning in OpenTX The setup for the radio is relay simple: What they mean: L01: Monitors the CROSSFIRE frequency mode, activated when it's not in 150Hz mode L02: Active when the Link quality drops below 80% (pre-warning) AND 50 or 4 Hz mode is active L03: Same as L02 but with the critical warning level at 70% L02 and L03 also got a small delay (0.
With the logical switches, the voice alerts will be triggered every time they are active. What they mean: SF1: when L02 is active, plays the selected track ones -but not at the startup SF2: same as SF1 for the critical warning For the sounds, you can create your own with a free TTS creator on the internet. Model match in OpenTX (and FreedomTX on TANGO 2) Model match enables you to make sure that a specific receiver and drone with it only bind if the correct radio model is selected.
Model Id (Model Match) in FreedomTX (TANGO 2) Model Id (Receiver No.
VTX connection by CRSF All Unify32 and EVO line VTX’s from TBS FC are capable of using CRSF to communicate with the CROSSFIRE ecosystem.
VTX connection by SmartAudio If you own any Unify or any other VTX with SmartAudio capability, you can connect it to your CROSSFIRE receiver as well. ● Select a free output pin capable for SA (check the output map section for available outputs) ● Connect them (CROSSFIRE TX to VTX RX/ SmartAudio pad) SmartAudio or CRSF for the VTX? Both protocols had their advantages and disadvantages: ● SmartAudio ○ Single wire connection.
VTX button not working When the Unify32 detects a signal on the SmartAudio Signal-in pad, it will disable the button. To change the VTX to CRSF or SA, you can unsolder the wire (FC connection) or force your CROSSFIRE RX to not output any signal.
If you use an F4 FC, make sure you don’t use UART’s with labels with SBUS or S-PORT. Those UART’s got a hardware-inverter installed which does not work with CRSF.
CRSF with KISS/ FETTEC Depending on the KISS Fc you are using, connect the CROSSFIRE by CRSF to the Fc’s RC input port. In the configurator, enable CRSF as RC Type: Any other FC Depending on your FC, set the output map according to the protocol that it can use.
BST to Eagletree Vector If you use an EagleTree vector Fc, you can connect the ET bus to the BST bus to get LQ and RSSI in the osd as well as telemetry from the FC back into the CROSSFIRE. To wire it up, just connect SCL to SCL and SDA to SDA. A common ground should already exist by the RC connection to the FC. MAVLink with MAV FC’s If you use an FC with MAVLink like ArduPilot/ PX4, you can use the MAVLink capabilities of the CROSSFIRE. Connect a MAVLink capable output to the Telemetry port of your FC.
If you use MAVLink, you can also use the RC over MAVLink option to save the extra wiring. The details can be found in this section. If you use the PX4 firmware, you don’t need to configure the telemetry port to get it running. For the best experience, you should use ArduPilot 4.10 CROSSFIRE 6.09 and WiFi 2.03 or later.
Wireless configuration with ArduPilot/ PX4 by Bluetooth As soon as the receiver receives valid MAVLink packages, the Bluetooth module switches to MAVLink as well. If you encounter issues, you can check the module settings in the Transmitter/ General settings: In Mission Planner, QGroundControl, or any other app, set the Baud Rate of your PC’s Bluetooth module to 57600baud.
Wiring diagram Wireless telemetry Bluetooth Depending on the FC firmware you use, you have to set your Bluetooth module to MAVEmu or MAVLink. Use MAVEmu if you use non-MAVLink FC firmware. Otherwise, the CROSSFIRE will set the Bluetooth module to MAVLink by itself (if MAVLink data are incoming to the receiver). Then connect your mobile device to the CROSSFIRE Bluetooth module.
WiFi telemetry with BetaFlight/ iNav For the WiFi telemetry, you need to wire up your FC with an extra MAVLink connection, as the MAVLink emulation is not (yet) supported by the WiFi firmware: Settings in BetaFlight/ iNav On the port where you got your extra MAVLink connection installed, enable MAVLink with 115200 Baud (since FW 6.xx, 57600 before 6.xx) in the PORTS tab for that UART. Note: You need to cancel the “loading parameter” dialog in MissionPlanner etc, as it will not get past this dialog.
Wireless configuration with BetaFlight/ iNav by Bluetooth With the serial passthrough function of the Bluetooth module (Standard TX only), you can connect to your BetaFlight/ iNav Fc without a USB connection. For this to work, you need to connect a second connection between the CROSSFIRE RX and the FC Note: This will only work while your CROSSFIRE is in the 150hz mode.
Signal strength in BetaFlight - BF < 4.1 and DJI OSD If you use an older BetaFlight version or a new one but with a DJI HD system, you need to assign the LQ sensor to a channel. Keep in mind that the LQ will remain at 100% while the CROSSFIRE is in 150Hz mode! In the CROSSFIRE receiver channel mapping, assign LQ to an unused channel. If you set it up by LUA, you can assign it to channel 1, even when you use the 8 channel mode of the CROSSFIRE.
For the OSD tab, set it up like this: Signal strength in BetaFlight - BF 4.1 and later Since version 4.1 BetaFlight can read the link information from the CRSF stream. This will give you the RSSI reading in dBm (0 - -130) and the LQ reading similar to the TBS OSD (300 - 0 %). To use this new method, you need to disable the RSSI channel setting in the receiver tab and activate the following elements in the OSD tab.
CLI commands Rf mode dynamic or forced 50Hz: set osd_link_quality_alarm = 70 set osd_RSSI_dbm_alarm = -100 Rf mode forced 150Hz: set osd_link_quality_alarm = 40 set osd_RSSI_dbm_alarm = -100 Signal strength in iNav - iNav < 3.xx In iNav, it’s almost the same as with the old BetaFlight method, except that you don’t need to assign LQ to a channel in the channel map menu. iNav reads the LQ from the CRSF stream and outputs it automatically on Channel 17 (from iNav). Signal strength in iNav - iNav 3.
RSSI Relative signal strength indicator How “loud” the signal is, that the receiver “hears”. But this also includes noise. The RSSI is exponential which results in a massive drop at the beginning and slows down the lower it gets. In general: double the range will result in a drop of -6dBm. An example: ● RSSI at 0m = -10dBm ● RSSI at 1m = -16dBm ● RSSI at 2m = -22dBm The CROSSFIRE can go down to -130dBm before the link breaks up.
What should I use in my OSD or radio The easiest way to set up your OSD or radio warning is by using LQ. It is linear which makes it easier to monitor for most people, while RSSI got a logarithmic scaling which makes it drop rapidly at the beginning and then slower the further you go.
Racing environment When using TBS CROSSFIRE control link, it is a requirement that all pilots use the same power output. The use of CROSSFIRE has the same requirement as the management of video transmission power output when it comes to racing.
Emergency Update When the update for the receiver fails, it will no longer work. In this case, you need to use the built-in emergency update feature: Standard diversity RX The standard diversity receiver comes with an onboard USB connection. Therefore you can connect the receiver with your TBS Agent X and update him straight away. Micro/ Nano/ Nano diversity RX Since FW 2.
FLARM FLARM is a collision-avoidance system developed in swiss and mainly used by sailing planes and helicopters. With the TBS CROSSFIRE, you can send and receive the FLARM track signal and make the airspace a bit safer. What you need The needed license and hardware base depends on what you want to do. In general, you need the TBS GPS puck (the one in the black enclosure, not the cheap small m8n GPS!) and a standard diversity receiver (the Nano diversity receiver is not yet supported).
If you lost the email with the key, open a ticket, including the receiver serial number. Activation of a license When you receive your email with the code, you need to get the old TBS Agent (Agent X is in development for this). After the installation: ● Connect the CROSSFIRE diversity RX via USB with your Pc ● Open the Agent ● Ignore the message from the Agent (Device not recognized.
Status display If you own a Standard or Lite TX, you can see the actual status of your FLARM set up in one of the main screens of the OLED display: Status: no Sat Fix/ Fix - are enough satellites found by the GPS Transmitter: Active/ Inactive - Position transition is enabled (to other airplanes) Receiver: Active/ Inactive - Active if a license is installed Req. Upd. by: XX.XX.
Your aircraft is the center of the radar.
FAQ Some common and some special outlier questions for the CROSSFIRE system. ● ● TBS CROSSFIRE Seems not to work with Futaba T18SG ○ It required you to use an external battery to power the TBS CROSSFIRE ○ Go to Trainer port settings and select ACT, Student, and 8 Ch. or 12 Ch. Does the transmitter forget the receiver when I bind a new receiver ○ No. The receiver stores the serial number of the transmitter. Everything is based on this. So you can bind as many receivers as you want.
