GEPRC ELRS NanoSE Receiver|FPV Video Transmitter
Product prices and stock are subject to actual confirmation; in case of stock shortage or abnormal pricing, we will proactively contact you to offer a refund or cancel the order.
GEPRC ELRS NanoSE Receiver|FPV Video Transmission Equipment
Official GEPRC FPV video transmission equipment. Names, categories, and payment methods have been organized according to Taiwanese customer usage habits. Please confirm specifications, connectors, frequency bands, polarization direction, voltage, and relevant regulatory requirements before placing an order.
Summary
GEPRC ELRS NanoSE receiver is a new generation remote control system developed based on the ExpressLRS open source project. ExpressLRS sets new standards for long-range connection, low latency, and a maximum refresh rate of 500Hz.
GEPRC ELRS NanoSE receiver operates at a frequency of 2.4 GHz. Compared with the Nano receiver, the NanoSE receiver uses an integrated SMD ceramic antenna, which further reduces its size while ensuring signal reception, making it more suitable for use on drones with limited space and light weight.
Note: ELRS products now shipping have been pre-flashed with 2.x firmware. 2.x is not compatible with version 1.x, so you need to upgrade the transmitter to 2.x for proper frequency matching.
Specifications
Size: 12.1mm*10.4mm
Weight: 0.4g
Chips: ESP8285, SX1281
Frequency band: 2.4GHz ISM
Refresh rate: 25Hz-500Hz
Input voltage: 5V
Antenna: Integrated SMD Ceramic Antenna
Feature
Small size
0.4g weight
WIFI Upgrade firmware
ELRS open source project, remote control
Integrated SMD Ceramic Antenna
Maximum refresh rate of 500Hz
Simple operation
ELRS NanoSE Receiver Diagram
Package Included
1 x NanoSE receiver
2 x Heat shrink tube
4 x Silicone cable (black, red, yellow, green)
1 x Pin (4pin)
1 x Instruction manual
1 x Sticker
LED Status indication
Instructions
ELRS NanoSE receiver and FC connection diagram:
Open Betaflight Configurator, go to the “
Ports
” tab and enable the corresponding UART as a
Serial Rx
(e.g., UART2 as shown below). Save and restart.
On the “
Configuration
” tab, click on “
Serial-based receiver
” on the “
Receiver
” panel, and select “
CRSF
”
Binding
1. The receiver is powered on and off for three consecutive times (within an interval of 1 second);
2. Receiver’s LED does double flashing, indicating that the receiver has entered binding mode;
3. Make the RF Tx module or radio transmitter enter binding status. Once the LED status changes to solid light, the binding is successful.
FAQ
Q: Why is the GEPRC ELRS rx always on and cannot work when powered up?
A: Recently, many users have reported that on some F4 flight controls, if the Uart 2 port is wired according to the CRSF receiver in the manual, the ELRS receiver is always on and cannot work.
After data inquiry and testing, it is determined that for receivers with an ESP chip, if the TX interface is placed at low Vil Mode,
This is not a bug in the firmware.
This problem is well known: some FCs cause the receiver TX line to go low at power on, which forces the ESP into bootloader mode, hence the solid LED.
This is not a failure of the flight control or the receiver, but the ELRS project was not popular during the development of these flight control models, and this problem was not optimized. The chips of ELRS and black sheep receiver are different, so the same CRSF connection for a black sheep receiver can be used normally. Subsequent flight control launches will solve this problem.
There are a couple of potential fixes/workarounds.
In addition, if there is a need for this type of flight control to use an ELRS receiver, try the following methods:
1. Power on repeatedly several times (low efficiency)
2. Remove some components on the flight control (high risk)
3. Add a pull-up resistor to port 2 (reply from the developer)
You can try to add a small value (300ohm-1kohm) pull-up resistor (to 3.3V) to the receiver TX line.
4. Change the version of flight control firmware (this problem occurs in some firmware of version 4.2)
5. ELRS receiver is connected to port 1, which can be used normally (Troubleshooting perfectly)
More details please check the link below: