Ghost Manual 2.3
Ghost Manual 2.3
3 - Mar 2022
Introduction, and History
Back in early 2013, when FPV was still in its infancy, and mini-quads hadn’t been invented yet,
ImmersionRC introduced the EzUHF 433MHz remote control system.
In the early days, this system was used for some of the most iconic fixed-wing FPV flights, pushing
limits out past 10s of km.
Since then, FPV has evolved massively, and now, 7 years later (4 years after development started), it
is time to bring a new innovative R/C link to the market.
Ghost doesn’t run on 433MHz, nor does it run on 868/900MHz. Ghost uses an innovative new
chipset on the 2.4GHz band for some very good reasons.
In Europe, the 868MHz band, commonly used for controlling hobby-class drones, has a couple of
serious limitations. Firstly, the entire (legal) band is only 2MHz wide (vs. 76MHz for 2.4GHz). This is
just not enough bandwidth to run more than a small number of systems simultaneously, and is just
not suitable for racing.
Secondly, duty-cycle limitations which allow other potentially life-saving equipment (fire alarms,
home automation, medical systems) to co-exist on this band, make it a poor choice for low-latency,
high duty-cycle model control.
The chirp-spread-spectrum technology used by the Internet of Things (LoRa WAN, etc.) when run on
the 2.4GHz band has some serious advantages, including:
- Tiny antennas, 2.4GHz antennas are only 36% of the size of the equivalent on 868MHz
- Much wider band, 76MHz vs. 2MHz on 868MHz (or 26MHz on 915MHz)
- Much better sensitivity (= much longer range) than traditional 2.4GHz systems
- Much better selectivity (adjacent channel rejection) than traditional 2.4GHz systems
- Much smaller directional antennas for the really crazy long range missions
- More range than 99% of pilots need, and with a higher gain (but still small) Tx antenna,
comparable range with 868/915MHz systems.
- Enough bandwidth to run 250Hz+ modes using the advantages of LoRa modulation
- Lower power consumption than Sub-GHz systems for longer radio battery life
Ghost Protocol
Modulation Chirp Spread Spectrum + Adaptive FHSS 3 (With LBT for EU versions)
Binding Bidirectional, with confirmation and protocol negotiation
RF Profiles Solid250, Race500, Race250, Pure Race, Race, ‘Normal’, and Long Range, more to come
Ghost Transmitter
Uplink Tx Power 16uW - 350mW (100mW EU LBT) (+/- 0.5dB) 3
Frame Rate 500Hz (Race500), 250Hz (PureRace), 250Hz (Race250, Solid250), 160Hz (race), 55Hz
(normal), 15Hz (long range)
Format Standard JR Module, tested with most common OpenTx compatible radios or
Standard ‘Lite’ Module, testing with most X-Lite™ and similar radios.
UberLite Module for Orqa FPV.Ctrl.
Antennas JR Module: Twin antenna, with Tx-side diversity. Antennas are 2.1dBi Dipoles
Lite Module: Single antenna via RP-SMA.
UberLite Module: Internal 2.4GHz Dipole
Serial Formats SBus, GHST 1 - Auto-Sense
Firmware USB Upgradable (with OTA updates for receivers)
Power Supply JR/Lite Modules: 6V-20V, 1.75W @ 350mW, ~250mA at 7.4V
UberLite Module: 5V
General Features
Tx-side Spectrum Analyzer Supported, full frequency range
Rx-side Noise Floor Analysis Auto on power-up, or on demand from the tx
2
Sbus is inverted by definition, SBus Inverted flips it over so that it doesn’t require inverters on F4 FCs
3
Some specifications vary depending upon the regionally-specific product SKU
For transmitters which do not yet support this protocol, OpenTx release 2.3.12 is highly
recommended. This is a stable release that supports the GHST protocol, the Ghost ‘Lua’ menus, and
the synchronized packets that provide extremely low latency.
The Ghost transmitter auto-senses the R/C control protocol, no need to set anything.
For more details on the OpenTx build, along with the telemetry sensors that it supplies, refer to
section ‘OpenTx Custom Builds for GHST’ later in this document.
Make sure to disable the Internal RF when using the Ghost. Newer OpenTx builds will
enforce this, but will mean that if Internal RF is enabled, GHST doesn’t appear in the protocol list.
New Receivers
New Receivers are shipped with bind mode enabled. For new receivers, just power them on, power up
the Tx, enter the Binding menu, and start the bind sequence.
Note: To prevent surprises if the bind button is pressed during flight, the bind button is deactivated 30
seconds after the Rx is powered up. Simply cycle Rx power to re-enable if bind was intentional.
Deja Vu Binding
Deja Vu Binding records all receivers used by a Ghost transmitter and can bind to them in the future
without the need to touch the bind button on the receiver.
Receivers, after powered on, and before they have a valid connection to a Ghost transmitter,
periodically scan for transmitters attempting to bind.
This feature also enables the Ghost Updater to transfer firmware updates only for receivers that you
own.
2G4 Zepto
By far the smallest receiver in the hobby. 10x10mm. Pinout is the same as the 2G4 Atto shown
above, meaning the Zepto and Atto may be used interchangeably on Proton Packs.
Note that the antenna connector on the Zepto is an MHF4, and not a standard U.FL.
For racing where every packet counts, and for long range use where multiple antenna polarities are
useful, the Duo version is preferred.
Wherever possible, the GHST protocol should be used. It is available in development builds of most
flight controller firmware. For BetaFlight it will be released in the 4.3 major release.
GHST is an extremely fast (tight) protocol, with short packets, low latency, and 12-bit data for the
primary flight channels.
PWM should be used for fixed-wing flight, with 4 PWM outputs capable of driving servos, and motor
ESC. PWM3 is a version requested by Wing pilots, with 3 PWM channels, but full Tramp control.
SBus is offered (with it’s ‘Fast’ variant) as a compatibility mode, since it is supported by most flight
controllers, whether running Betaflight, iNav, PX4, etc.
Note: Watch out when using fast RF modes with the SBus protocol. SBus packets are relatively slow, and FC
firmware such as iNav can have a problem with SBus at 250Hz., and won’t work at all at 500Hz.
For flight controllers which cannot be updated to a version that supports GHST, SRXL-2 is the
preferred protocol. Betaflight 4.2 and later support SRXL-2, and it supports passing Link Quality (LQ)
to the OSD for a little more confidence while flying.
Protocol Frame Time Baud Rate Packet Channels Telemetry vTx Control
Duration
GHST Same as RF 420k 300us 12 Yes Full (Tramp)
PWM 20ms N/A N/A 4 None None
PWM3 20ms N/A N/A 3 None Full (Tramp)
SBus Same as RF 100k 3ms 12 None Full (Tramp)
SBus Fast Same as RF 200k 1.5ms 12 None Full (Tramp)
SRXL-2 Same as RF 400k 800us 12 LQ passed as Full (Tramp)
RSSI
Pin Value
Gnd Ground
5V Power Clean 5V Power, from FC pin
Serial Out Wire to TX pin on an unused UART. No inversion required (incompatible with most S.Bus inputs)
Tramp Tel Optionally wire to Tramp Telemetry pin, for Ghost control of Tramp vTx channel
Note that F4 flight controllers may require a ‘cli’ command to enable the high speed SRXL-2 mode:
set srxl2_baud_fast = ON
Pin Value
Gnd Ground
5V Power Clean 5V Power, from FC pin
Serial Out Wire to TX pin on an unused UART. No inversion required (incompatible with most S.Bus inputs)
Tramp Tel Optionally wire to Tramp Telemetry pin, for Ghost control of Tramp vTx channel
Pin Value
Gnd Ground
5V Power Clean 5V Power, from FC pin
Serial Out Wire to SBUS pin on an unused UART. FC pin generally labelled SBus
Serial In Optionally wire to Tramp Telemetry pin, for Ghost control of Tramp vTx channel
NOTE: If your Flight Controller does not detect a valid serial connection from the Ghost Rx,
ensure that the Ports tab in the Betaflight Configurator only has one single port enabled for
Serial Rx. If more than one is selected, the serial Rx will not work.
Specification Value
CH1 Serial Output ‘S’
CH2 Tramp Telemetry Pin ‘T’
CH3 ‘3’ Pad on bottom side of PCB
CH4 ‘4’ Pad on bottom side of PCB
Note: Production PCBs have ‘3’ and ‘4’ marked on the bottom of the board, pre-production doesn’t have the
markings, but pad location and function is the same.
Specification Value
Power 20mW downlink
Sensitivity (approx) Variable, -112dBm Normal Mode, -106dBm Race/PureRace
-117dBm Long Range, -105dBm Race250
PWM Channels 4
UARTs One, Serial_TX/Telemetry
Protocols SBus, SBus Fast (200k)
USB None
Firmware Upgrades Over the air (OTA)
For the 5.8GHz Transmit antenna, routing the cable directly over the PCB is really not recommended,
and can cause power level increases that can affect other pilots flying on adjacent channels.
Avoid the ‘red zone’, try to route the transmitter cable around the outside of the board where possible.
If using other protocols, the link quality may be passed down an unused R/C channel, and betaflight
configured to that channel’s value as RSSI.
To set the channel/power, joystick click left from the main Ghost screen.
Move up/down to change settings, then click Send.
Note that Receivers will remember the requested vTx parameters, and will reload them into the vTx
upon next powerup.
Note also that from v1.0.4.0 firmware and later, channels which are not permitted in the currently
selected region are marked as ‘! Not Auth !’, and cannot be selected.
If for any reason the Ghost Tx display does not turn on, power up the module with the joystick
pressed to force boot load mode.
NOTE: When not in update mode, the FPV.Ctrl presents itself as a game controller (HID) device to
the connected host. When in update mode, the FPV.Ctrl presents itself as a COM port (CDC).
Note that as with the other members of the ghost transmitter family, the Uberlite contains storage
for receiver firmware images for all supported Ghost receivers.
When binding using the button on the uberlite module, the module will automatically update
connected receivers without prompting.
When using the Ghost menu system via a bluetooth connection, as with previous transmitters, it is
possible to skip the update if required.
If a Rx firmware update was necessary, once complete, don’t immediately power down the Rx,
leave it for 10-20 seconds to finalize the update. (LED will flash a few times to indicate update
progress)
To comply with current FCC regulations the JR module uses RP-SMA (reverse-polarity SMA)
antennas, an unfortunate departure from ImmersionRC’s traditional SMA bias.
Running the Ghost transmitter without antennas, or without an antenna on the port(s) selected
in the Antennas menu can cause permanent damage, and should be avoided.
Note that for any antenna used on the Ghost transmitters equipped
with dual SMAs, it is advisable to orient them about 90 degrees from
each other, in a ‘V’.
The Tiny Zepto receivers use a similar antenna, but with slightly shorter cable, and a smaller
‘MHF4/IPEX4’ connector instead of the traditional U.FL.
Try to space the two antennas as much as possible if maximum range is required, as should be
common practice for any FPV control system.
When removing, try to pull vertically, with a finger-nail each side. Pulling to the side can damage the
antenna-side of the connector.
When inserting, make sure that the connector is lined up correctly before putting any pressure on the
connector. If it is lined up, it will easily click into place.
The supplied heat-shrink should be applied after connecting the antenna, and will keep the U.FL in
place, preventing any surprises in-flight.
Note that ghost antennas sold since late 2020 are equipped with a ‘locking U.FL’ connector to prevent
accidental disconnection during flight/crashes.
To connect this connector to the Ghost receiver, carefully slide the metal locking part away from the
cable, mate the connector with the PCB-mounted female connector, and carefully slide the locking
part towards the cable.
JR Module
The main OLED user interface is navigated using the left/right joystick functions. The following
‘pages’ are available.
Note: Latency numbers in these images are from a PC-based simulator, and don’t reflect actual performance.
Link Page
The link page is shown by default by the
transmitter, and contains all data relating to the
‘health’ of the control link.
Channels Page
The channels page shows the positions of each
of the R/C channels. Up/Down to scroll through
all 12/16 channels..
Latency Page
The latency page shows an estimation of the
current system latency, using both fixed
elements, and measured values.
vTx Page
A Tramp (Nano, or HV), connected to the ‘T’ pin
of a Ghost Rx is controlled using the vTx page.
Bind Menu
Receivers are bound from the Bind menu Two
options are available, a simple ‘Bind’, which
preserves all Rx-specific setup (Rx Protocol,
etc.), and a ‘Bind + Setup’, which allows all Rx
parameters to be specified (including Rx ID for
team racing).
Spectrum Menu
The Spectrum Analyzer may be used to analyze
noise floor on the 2.4GHz band.
Set the start/stop frequencies, and press Start.
Tx Power Menu
Auto power mode will decide which power level
to use for the uplink transmission based on the
signal strength received at the receiver.
Failsafe Menu
Used only when a Rx is set in PWM mode. Set
the servo positions to be used in the event of a
failsafe.
This mirrors the Ghost menu system on the radio’s LCD, and avoids the need to keep turning the radio
around.
Refer to the manual for the specific radio that you use to learn how to enter this tools menu.
(TX16s requires holding the Sys button for example).
GHST protocol support without Sync capability is available in OpenTx release 2.3.11, with full support
in the public 2.3.12 release..
For up to date information on firmware, and open source tool support (OpenTx, Betaflight, etc.) please
refer to the following page:
https://www.immersionrc.com/ghostlatestrelease/
Sensor Purpose
VFrq Video tx frequency, in MHz
VPwr Video tx power, in mW
VBan Video tx band name
RSSI Ghost receiver RSSI in dB
RQly Ghost receiver link quality
RSNR Ghost receiver signal to noise ratio
TPWR Ghost transmitter transmit power, in mW
FRat Ghost link frame rate, in Hz
TLat Total estimated latency, in microseconds
RFMD RF Mode name
RxBT Pack Voltage *
Curr Instantaneous Current Consumption *
Capa mAh Consumed *
RxID Team Race Receiver ID 2
*
Introduced with Betaflight 4.3
2
Introduced with Ghost v1.0.2.0
3
Introduced with Ghost v1.0.4.0
Binding
Updating Firmware
...
Team Race mode, receiver active, but not currently selected.
Hint: Some say that if receiving packets, and staring at the RGB LED, while shaking your head, you can see
‘ghost trails’...
Range Estimations
To estimate the range of the Ghost 2G4 link the following assumptions will be made:
With these values we can estimate range in each of the 3 primary modes as follows:
Note: Tool used to estimate FSL (Free Space Loss) is an online IRC tool located here:
https://www.immersionrc.com/rf-range-demystified/
Note that these numbers don’t take into consideration factors such as antenna cross-polarization,
interference on the Rx end of the link, atmospheric effects, etc.
Source: fpvlab.com
Place the transmitter on (ideally) a non-conducting object, in the RF mode that you wish to test, with
Transmitter power set to 16uW.
Power up the receiver, with antenna attached, and walk away from the Tx until the LED starts blinking
erratically, and eventually stops blinking.
Measure that distance, and multiply it by approx. 148x to get the range on full Tx power 350mW.
Note: the 148x number comes from the difference in power between 16uW, and 350mW, in dB, of 43.44dB.
Each 6dB increase in power results in double range, so 43.55dB corresponds to a range increase of 148x.
After testing, remember to restore the Tx power back to the normal setting (typically 100mW)
before flying to avoid any unnecessary surprises.
In modern control systems most of these items occur synchronously, except the synchronization
between R/C control data reaching the RF module, and RF packets being sent over the air.
In 2019, thanks to some awesome work by the OpenTx team, the first two items may now be
synchronized with the RF packets sent over the air.
OpenTx v2.4, along with some private development builds, include this feature, and this is used by
ImmersionRC’s GHST protocol described here.
Frame 1 Frame 2
Sticks R/C RF RX Sticks R/C RF RX
Ghost was designed with latency minimization in mind, and has optimized each part of this process.
In PureRace mode, with a version of OpenTx that supports ‘mixer synchronization’, and the GHST
protocol installed in the radio, latencies of around 4.2ms from start of R/C packet to end of Rx packet
are achievable.
Note that for the first item in the latency list, this is the only variable part of the ‘latency stack’
remaining in modern systems. RF packets are sent at regular intervals, but the time from the
stick/switch movement to these regular packets is still variable, and varies between zero, and the
frame period.
Note for reviewers: Ghost always prioritizes the first 4 flight channels, critical for crisp, precise model control.
When testing latency, don’t use a switch assigned to anything but these first 4 channels.
The Ghost family supports (currently) 6 different RF modes, each of which has its own tradeoff
between telemetry, frame rate, and range.
For all of the faster modes (Race, PureRace, Race250, Race500, Solid250) use the GHST protocol
between the R/C transmitter and the Ghost transmitter, and also between the Ghost receiver
and the flight controller.
Solid250
A unique mode, not available on any other R/C link, fuses antenna diversity, frequency diversity, and
time diversity, to provide a packet-loss rate which is unmatched.
The preferred protocol for racers who don’t need telemetry, but not ideal for long range.
Race500
For those who want the absolute minimum control latency, Race500 provides it.
Race250
Faster than most pilots will ever need. Fastest link which includes full telemetry, for racers who need
it.
Pure Race
A robust LoRa protocol suitable for racing in noisy environments where telemetry feedback is not
required. To take advantage of this mode (or Race mode) ensure that the GHST protocol is used
between the R/C Transmitter (OpenTx) and the Ghost module.
Normal
Normal is the default mode, and is a good compromise between performance and range. Certainly for
beginners, this is a suitable mode.
Safe control ranges of 20-30km are very possible in this mode.
Long Range
Not very appropriately named, since all of these 4 modes above will get you further than most pilots
will ever fly.
Long range mode prioritizes range over frame rate, but still achieves a frame rate that for most
extreme range flights is quite flyable.
Note that auto mode switching is NOT supported yet (and may never be). A couple of years of testing
has convinced us that reliably doing this, especially in a RF polluted race environment, doesn’t reach
the reliability level that we desire.
Another good solid choice is PureRace, which runs a little faster (300Hz vs. 250Hz), and will certainly
get you on the podium also.
Both of these modes will do fine on 25mW, or 100mW in noisy environments. No need to go crazy
power-wise, blasting out your fellow pilots with 1W of inefficient power isn’t nice :-)
‘I just want to fly around my local field, and chase neighborhood cats’
You can’t really go wrong with any of the modes. If you want telemetry, Race is fine, if you don’t care
about telemetry, PureRace will give a stick feel that you are probably not used to (even without being
a pro pilot)
‘I am a hardcore freestyler’
For freestyle, bando flying, Solid250, or PureRace, should work fine, and will out-fly 5.8GHz video in
pretty much all cases.
For those bandos that go on forever, and for 20 storey elevator-shaft dives, bump the power level to
350mW (assuming your local regulations allow it), and if you have any serious LQ drops, drop back to
Race mode, or even Normal.
If running 350mW transmitter power, the uplink range is approx. 4x the downlink (telemetry)
range. So if you are getting 15km with good telemetry, you can keep going until close to
60km before getting into trouble
Solid250 is not a great choice for pushing the limits of long range flight, since it will bend
over backwards to avoid dropping packets for as long as possible (as desired by racers), but
when it does start to drop, it will drop off quite quickly.
The Team Race menu supports assigning up to two switches (or banks of buttons) to the selection of
the active receiver. These switches then support split-second switching between up to 16 quads.
To define the receiver ‘ID’ of a Ghost, configure it in the bind menu. Once defined, that receiver will
only emit serial data to the flight controller when selected. When not selected, the receiver’s LED will
illuminate Cyan.
Note that the team race support also controls the video transmitter, without the need for complex
configurations on the flight controller side.
When a receiver is de-selected, the video transmitter will automatically shut down. When a receiver is
selected, the video transmitter will be enabled (assuming any assigned vTx enable switch is also
selected).
All of this functionality is just as useful in the simple race scenario, where selecting quickly between a
primary, and backup quad is required.
To clone a transmitter (or rather a transmitter ID) you need to run the PC/MAC based Ghost Updater
app (v1.6 or later).
3) Connect the slave transmitter (the one that will inherit the Master transmitter’s ID, and click i.d.
Write Slave.
If this is no longer required (or two enable/disable the clone ID in the field, use the Clone Tx menu.
As a bonus, add a dab of heat sink compound under the vTx before soldering and the entire PCB
becomes an extra heat sink.
Silicone ‘gummies’ should always be used to reduce the damage caused by vibration and shock during
the more extreme ‘landings.
For a simple install, without worrying too much about stack height, simply use the header as-is,
leaving the black plastic part between the proton pack and the Tramp/Ghost.
For a cleaner, low profile install, which requires a bit more ‘fiddling:
1) Insert the headers from the bottom of the proton pack, until the black plastic shroud touches the
board. Turn the board over, and flow some solder into the holes that the pins poke through (doesn’t
need much).
2) Install the Tramp Nano/Ghost on the correct side of the board, until it is touching the Proton Pack.
For the Tramp, a small dab of thermal paste on the two black ICs that will touch the Proton Pack will
improve thermal performance (this is available from any computer store).
3) Solder the pins to the Tramp/Ghost, and trim them very carefully, ensuring that the cutters do not
knock any of the tiny components from the PCBs.
4) Turn the board over, and with cutters, very carefully remove the black plastic shroud, and trim the
pins flush with the PCB.
As an example, this shows the wiring for the Diatone Mamba F722, with a Ghost Atto/Zepto, and
Tramp nano, using SRXL-2 mode.
2. Bridge the two solder jumper pads on bottom side of the FPV.Connect, as shown below:
3. Connect the FPV.Connect antenna and Ghost Rx antenna connector with small U.FL to U.FL
cable.
This cable is available from the Orqa FPV Store, here.
Alternatively any short u.fl to u.fl cable may be used
6. Follow the standard Ghost binding procedure for the Atto that was just installed, with one
exception, select Goggles1 instead of Rx1 when binding.
The Rx protocol does not matter, and will be automatically set.
If the bind requests an update, update the Ghost Atto with the latest firmware.
7. Enter the goggle’s Receiver Settings (Rx) menu, and under Module selection, select
rapidFIRE
8. Enter the goggle’s Connectivity -> Ghost menu, Turn Power switch to On. Turn the VTX mode
to Automatic.
A high power transmitter in such close proximity to the receiver can create issues for the upgrade
process.
A ‘feature’ of many new FrSky™ radios is that the interface to the external module has it’s voltage
levels halved (down to 2.0V peak to peak) when the internal module is enabled.
This means that the Rx initialization failed, check the circled component on the Atto PCB. It is located
quite close to the solder pads, and is easy to accidentally remove with a soldering iron.
The part is a 0201 ‘600z’ ferrite bead, used for noise suppression, and in most cases may be simply
shorted out with a thin strand of wire.
Failed to find the small flash memory device. Generally caused by a prop strike (where the device is
removed from the board), or excessive flexing in the case of the hybrid.
This type of failure will require a repair by one of our service centers ([email protected])
Internal firmware error, failed to bind the receiver, may be caused by incompatible firmware versions.
Switch the Tx to Normal RF Mode and try to bind again.
Duo Receivers only - caused by one of the two receivers being defective.
This type of failure will require a repair by one of our service centers ([email protected])
Rx ‘Unbricking’
Over-The-Air (OTA) updating of tiny devices without handy serial ports always raises the question
about how to avoid ‘bricking’, which renders a device unusable.
In theory, all firmware releases will be fully forwards/backwards compatible, so that when you grab a
2-year old ghost-equipped Whoop™ from under the bed and want to go fly, everything should just
work…
Reality is that this isn’t always possible, and the chances of you remembering the firmware version
that was installed on this under-bed Whoop™ is about the same chances of you remembering your
mother’s birthday.
So we have built in a mechanism to learn the firmware version installed in any ghost receiver.
Simply hold down the bind button while applying power and make a note of what the LED is doing.
As an example:
V1.0.0.0 would flash
Once the Rx firmware version is known, use the Ghost Updater to find a matching transmitter update,
flash the transmitter to that version, and then update to the latest and greatest.
If you experience any problems with your product, please use the following resources.
Retailer Support
Your retailer is generally located close to you, speaks your language, no inter-country customs, and
can replace a failed product quicker than we can. Please contact them first if you have any issue that
looks like equipment failure.
ImmersionRC Support
Repair centers located in the West coast of the USA, and the UK (covering the EU). A quick email to
[email protected] starts the support/repair process.
Even though most responses happen within a few hours, please give this small team at least 48 hours to
respond to you.
System Integrators/Manufacturers
ImmersionRC is open to discuss with manufacturers who wish to integrate Ghost into other systems
(Hobby, or Industrial). An embedded Ghost receiver occupies approx. 10x10mm of PCB space.
For customers interested in Sub-GHz versions of Ghost (~200MHz -> 1GHz) for Industrial/Law
Enforcement (for appropriately licensed frequency bands) we also have solutions.
This is accomplished by selling multiple transmitter models (SKUs) which enable only the modes
permitted within a geographic region.
Note that for race organizers with special licensing permissions (Drone Champions League, DCL for
example), and races in multiple geographic regions, special models are available which can comply
with their licensing agreements.
In September 2000, this requirement was suspended indefinitely, permitting again the use of
RP-SMA connectors.
(https://docs.fcc.gov/public/attachments/DA-00-2225A1.pdf)
3.0 Warranty
ImmersionRC Limited Hong Kong provides a 2-year warranty to the products it sells or otherwise distributes, but this
warranty is limited to manufacturing defects and does not cover normal wear and tear nor abuse or use for purposes the
products have not been designed for. ImmersionRC Limited Hong Kong is not liable in case you cause injury to yourself
and/or others or if you damage or destroy property with any of the products you purchased and/or otherwise received from
ImmersionRC Limited Hongkong, no other warranties are expressed or implied.