| Item | Specification |
|---|---|
| Communication frequency band | 2400-2483.5 MHz 1427.9-1447.9MHz |
| Communication bandwidth | 30Mbps |
| Anti-jamming | Dynamic Frequency Hopping |
| Power level | 2.4G 25dBm±2 1.4G 25dBm±2 (Optional) |
| Communication range | Max 30 km (one-to-one, interference-free, line-of-sight environment) |
| Communication node | Maximum 32 |
| Encryption method | ZUC, SNOW3G, AES — three selectable encryption methods. |
| Modulation scheme | Supports QPSK, 16QAM, and 64QAM modulation schemes. |
| Air Interface Latency | UL one-way latency < 25 ms; DL one-way latency < 25 ms |
| Sensitivity (BLER<=3%) | 2.4G(Channel 24415): 20MHz -92dBm(10Mbps) 20MHz -96dBm(5Mbps) 10MHz -89dBm(10Mbps) 10MHz -92dBm(5Mbps) 1.4G(Channel 14379): 20MHz -86dBm(20Mbps) 20MHz -97dBm(5Mbps) 10MHz -88dBm(10Mbps) 10MHz -94dBm(5Mbps) |
| Web page configuration | Supports browser-based login and configuration (Edge recommended) |
| Interface details | DC IN ×1, SBUS IN ×1, Serial Port ×2, Ethernet Port ×1 |
| Power consumption | Overall operating power consumption < 6 W |
| Heat dissipation | Built-in Active Cooling |
| Operating Temperature | -20°C ~ 75°C |
| Working voltage | 24±10V |
| Size | 91mm×61.2mm×18mm |
| Weight | 132g |

Connect the ground unit's Ethernet port to your laptop's Ethernet port. Power the ground unit with a 3–8S battery. The RC receiver can be connected to the SBUS interface of the OneVDLink.
The link supports receiver SBUS signal forwarding.

There are two ways to connect the air unit to the flight controller for MAVLink data communication:
Connect the air unit's Ethernet port to the flight controller's Ethernet port.
Connect the air unit's UART to the flight controller's TELEM interface.
Using the UART connection is recommended, as this leaves the air unit's Ethernet port available for an Ethernet camera or gimbal.
Connect UART1 of the air unit to TELEM1 of the flight controller, and set the flight controller parameter serial1_baud=115200 (a restart is required after modification).
Manually configure a static IP of 192.168.1.100 on the ground computer. In Mission Planner, select UDP port 14551 and click Connect. As shown below:

Connect the air unit's Ethernet port to the flight controller's Ethernet port, and connect SBUS OUT to the flight controller's SBUS IN. Refer to the diagram below.
Configure the flight controller network parameters as follows:
net_enable=1
NET_DHCP=0
NET_P1_TYPE=1
NET_P1_PORT=15001 (configurable from 0 to 65535)
NET_P1_PROTOCOL=2
NET_P1_IP0=192
NET_P1_IP1=168
NET_P1_IP2=1
NET_P1_IP3=20 (The link device has already used 11 and 12 by default; do not configure the same IP)
On the ground computer, manually set a static IP address of 192.168.1.20. In Mission Planner, select UDP port 15001 and click Connect.

Default factory configuration: Point-to-point communication, ground unit IP 192.168.1.11, air unit IP 192.168.1.12, key 0001.
Interface |
Configuration instructions |
Parameter Description |
|---|---|---|
| UART0 Switch It is recommended to keep it always on by default from the factory. |
At^uartipfun=1 |
1:Open |
| UART0 Basic Configuration Configure the baud rate, UDP port, and destination address. |
at^UARTIP="B115200",0,1,1,14550,"0.0.0.0",14550,"192.168.1.100" |
"B115200":Baud rate14550:Local/Remote UDP Port"0.0.0.0":Local IP (any)"192.168.1.100":Target IP address |
| UART0 MAVLink 2.0 Protocol Configuration Commonly used, recommended as the factory configuration, though not strictly required in actual testing. |
at^Uartipfrs=0at^uartipfrl=0at^Uartipfrs=1,1,fdat^uartipfrl=1,0,1,1,12 |
Used to configure the start condition, length, and parsing rules of serial data frames. |
| UART1/UART2 Switch It is recommended to keep it always on by default from the factory. |
At^uartfun=1 |
1:On (UART1 and UART2 share this switch) |
| UART1 Configuration Configure the network and serial port parameters for UART1. |
AT^UART1SET="192.168.1.100","14551","14551","B115200","8","1","N" |
"192.168.1.100":Target IP"14551":Local/remote ports"B115200":Baud rate"8":Data bit"1":Stop bit"N":No verification |
| UART2 Configuration Configure the network and serial port parameters for UART2. |
AT^UART2SET="192.168.1.100","14552","14552","B115200","8","1","N" |
"192.168.1.100":Target IP"14552":Local/remote ports"B115200":Baud rateOther parameters are the same as above |
| Central Node | Explanation |
|---|---|
AT+CFUN=0 |
Soft Shutdown |
AT^DAOCNDI=04 |
Set the frequency band to 1427.9–1447.9 MHz |
AT^DAPI="11223344" |
Set Access Key |
at^drps=14379,5,"26" |
Set the main antenna operating bandwidth to 20 MHz, transmit power to +26 dBm. |
AT^DFHC=1 |
Enable Automatic Frequency Hopping |
AT^ddtc=1 |
Set as Central Node |
AT^DSONSSF=9,0 |
Disable Wideband Adaptive |
AT^DSONSSF=7,0 |
Disable Point-to-Point Mode |
AT^DSTC=3 |
Set the uplink/downlink timeslot ratio to 4U1D |
at^netifcfg=2,"192.168.1.11" |
Set the network interface IP address to 192.168.1.11 |
AT^POWERCTL=1 |
Software Restart |
| Power Cycle | Physical Power Cycle |
| Configuration instructions | Explanation |
|---|---|
AT+CFUN=0 |
Soft Shutdown |
AT^DAOCNDI=04 |
Set the frequency band to 1427.9–1447.9 MHz |
AT^DAPI="11223344" |
Set Access Key |
AT^ddtc=2 |
Set as Access Node |
AT^DSONSSF=9,0 |
Disable Wideband Adaptive |
AT^DSONSSF=7,0 |
Disable Point-to-Point Mode |
AT^DSSMTP="26" |
Set the access node maximum transmit power to +26 dBm |
AT^DSTC=3 |
Set the uplink/downlink timeslot ratio to 4U1D |
at^netifcfg=2,"192.168.1.20" |
Set the IP address of Access Node 1 to 192.168.1.20, then restart after success. |
at^netifcfg=2,"192.168.1.21" |
Set the IP address of Access Node 2 to 192.168.1.21, then restart after success. |
at^netifcfg=2,"192.168.1.22" |
Set the IP address of Access Node 3 to 192.168.1.22, then restart after success. |
at^netifcfg=2,"192.168.1.23" |
Set the IP address of Access Node 4 to 192.168.1.23, then restart after success. |
at^netifcfg=2,"192.168.1.24" |
Set the IP address of Access Node 5 to 192.168.1.24, then restart after success. |
AT^POWERCTL=1 |
Software restart the device. |
| Power Cycle | Physical Power Cycle |
| Troubleshooting steps | Inspection items | Phenomenon/Instruction | Judgment and Solution |
|---|---|---|---|
| Step 1: LED Indicator | PWR (Power) LED: Red | Steady on | Steady on |
| Off | Module power supply is abnormal.Requires return to factory for repair. | ||
| ETH (Ethernet) Green LED | Steady on | 1. The Ethernet port chip is functioning normally. 2. Check the computer IP: Ensure it is on the same subnet as the R30 (e.g., 192.168.1.xx) and that the IP addresses do not conflict. |
|
| Off | 1. Check that the network cable is properly connected. 2. The Ethernet port chip is operating abnormally; further troubleshooting is required. |
||
| Step 2: AT Command Query | Check the actual IP configuration. | AT^NETIFCFG? |
Connect via USB and use the LCcom Tool to send the command to query the R30's current actual IP address, and verify it against the computer settings.![]() |
| Step 3: Initialization | Restore factory settings | AT^RECOVSET=1 |
When encountering other special situations, try initializing the module.Note: After initialization, the IP will revert to the default 192.168.1.12。 |
| Troubleshooting steps | Inspection items | Phenomenon/Instruction | Judgment and Solution |
|---|---|---|---|
| Step 1: External Environment | Signal Interference | - | Check whether there is strong interference from nearby 1.4 GHz or 2.4 GHz signal sources. |
| Antenna Connection | - | Check that the antennas are correctly and securely connected to the device. | |
| Step 2: LED Indicator | Link Status LED | Central Node:VIBR blue LEDsteady on. Slave Node:VFLASH green LEDsteady on, VIBR blue LEDflashing. |
1. Verify that the device is correctly configured as a Central (Master) node or an Access (Slave) node. 2. Incorrect master/slave configuration will prevent link establishment. |
| Step 3: Web Configuration | Access Key | - | Ensure theAccess Keyis exactly the same on all devices. An incorrect key will prevent link establishment. |
| Operating Frequency Band | - | Ensure all devices are configured on thesame frequency band(e.g., 04 or 08). | |
| Step 4: AT Command Query | Continuous Transmission State | AT^DSONCTX? |
Query the current continuous transmission state; it must be OFF. |