{"data":{"id":"856755","string_id":"Iepj2y3O","status":"1","parent_id":"0","slug":"Iepj2y3O","order":"18","name":"OneVDLink R30","type":"1","cover":"","cover_alt":"","desc":null,"website":"","contact":"","seo_title":"","seo_keyword":"","seo_desc":"","author":"","published_time":"0","add_time":"1783057221","update_time":"1783063740","corp_auth_id":"0","verify_code_auth_id":"0","editor_type":"1","tags":[],"child":[{"id":"856756","string_id":"xgHnKlS1","status":"1","parent_id":"856755","slug":"xgHnKlS1","order":"0","name":"OneVDLink R30 Networking Link User Manual","type":"2","cover":"","cover_alt":"","desc":null,"website":"","contact":"","seo_title":"","seo_keyword":"","seo_desc":"","share_switch":"0","share_code":"","author":"","published_time":"1783063735","add_time":"1783057240","update_time":"1783063740","corp_auth_id":"0","verify_code_auth_id":"0","editor_type":"2","file_type":"","auth_id":"[\"856756\", \"856755\"]","content":{"content_id":"856756","content":"## Product Introduction\n\n1. 1.4 GHz and 2.4 GHz dual-band communication\n2. Maximum communication distance: 30 km; bandwidth: 30 Mbps\n3. Supports up to 32 communication nodes with star networking\n4. Automatic frequency hopping for strong anti-interference capability\n5. Built-in active cooling design\n6. Optimized specifically for the MAVLink protocol\n\n## Product Specification\n\n| Item | Specification |\n| - | - |\n| Communication frequency band | 2400-2483.5 MHz\u00a0 1427.9-1447.9MHz\u00a0 |\n| Communication bandwidth | 30Mbps |\n| Anti-jamming | Dynamic Frequency Hopping |\n| Power level | 2.4G \u00a025dBm\u00b12\u00a0 1.4G \u00a025dBm\u00b12 (Optional) |\n| Communication range | Max 30 km (one-to-one, interference-free, line-of-sight environment) |\n| Communication node | Maximum 32 |\n| Encryption method | ZUC, SNOW3G, AES \u2014 three selectable encryption methods. |\n| Modulation scheme | Supports QPSK, 16QAM, and 64QAM modulation schemes. |\n| Air Interface Latency | UL one-way latency < 25 ms; DL one-way latency < 25 ms |\n| Sensitivity (BLER<=3%) | 2.4G(Channel 24415):\u00a0 20MHz \u00a0-92dBm(10Mbps)\u00a0 20MHz \u00a0-96dBm(5Mbps) 10MHz \u00a0-89dBm(10Mbps)\u00a0 10MHz \u00a0-92dBm(5Mbps)
1.4G(Channel 14379):\u00a0 20MHz \u00a0-86dBm(20Mbps)\u00a0 20MHz \u00a0-97dBm(5Mbps)\u00a0 10MHz \u00a0-88dBm(10Mbps)\u00a0 10MHz \u00a0-94dBm(5Mbps) |\n| Web page configuration | Supports browser-based login and configuration (Edge recommended) |\n| Interface details | DC IN \u00d71, SBUS IN \u00d71, Serial Port \u00d72, Ethernet Port \u00d71 |\n| Power consumption | Overall operating power consumption < 6 W |\n| Heat dissipation | Built-in Active Cooling |\n| Operating Temperature | -20\u00b0C \uff5e 75\u00b0C\u00a0 |\n| Working voltage |24\u00b110V \u00a0 |\n| Size | \u00a0 91mm\u00d761.2mm\u00d718mm |\n| Weight | \u00a0 132g |\n\n## Interface Definition\n![](https:\/\/resource-wangsu.helplook.net\/docker_production\/loaufg\/article\/c72F31WW\/692ee8d14b960.jpg)\n\n## Usage Notes\n\n1. The distance between the main antenna (MAIN ANT) and the secondary antenna (SLAVE ANT) should be greater than 20 cm. Antenna extension cables are included.\n3. The included omnidirectional antennas should be installed vertically upward on the ground side, and vertically upward or downward on the air side.\n5. The VSWR of the included omnidirectional antennas is lower when folded than when unfolded, resulting in better communication performance in the folded state.\n7. The antennas must not be placed directly against carbon fiber or metal, and there should be no metal or carbon fiber obstructions nearby.\n9. When the ground side and air side are within 2 meters of each other, the flight controller may fail to receive the relayed SBUS signal, and commands uploaded from the ground station may experience significant latency. Please increase the distance between the ground and air links.\n\n\n\n## Wiring method\n### Ground Unit Connection Method\nConnect the ground unit's Ethernet port to your laptop's Ethernet port. Power the ground unit with a 3\u20138S battery. The RC receiver can be connected to the SBUS interface of the OneVDLink.\n> The link supports receiver SBUS signal forwarding.\n> \n![](https:\/\/resource-wangsu.helplook.net\/docker_production\/loaufg\/article\/c72F31WW\/6932890d04017.jpg)\n\n### Air Unit Connection\nThere are two ways to connect the air unit to the flight controller for MAVLink data communication:\n Connect the air unit's Ethernet port to the flight controller's Ethernet port.\nConnect the air unit's UART to the flight controller's TELEM interface.\nUsing the UART connection is recommended, as this leaves the air unit's Ethernet port available for an Ethernet camera or gimbal.\n#### Using UART Communication\nConnect 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).\nManually 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:\n![](https:\/\/resource-wangsu.helplook.net\/docker_production\/loaufg\/article\/c72F31WW\/69328987f36a5.jpg)\n\n\n#### Using Ethernet Communication\nConnect 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.\nConfigure the flight controller network parameters as follows:\nnet_enable=1\nNET_DHCP=0\nNET_P1_TYPE=1\nNET_P1_PORT=15001 (configurable from 0 to 65535)\nNET_P1_PROTOCOL=2\nNET_P1_IP0=192\nNET_P1_IP1=168\nNET_P1_IP2=1\nNET_P1_IP3=20 (The link device has already used 11 and 12 by default; do not configure the same IP)\nOn the ground computer, manually set a static IP address of 192.168.1.20. In Mission Planner, select UDP port 15001 and click Connect.\n![](https:\/\/resource-wangsu.helplook.net\/docker_production\/loaufg\/article\/c72F31WW\/6932897c75d65.jpg)\n\n> Default factory configuration: Point-to-point communication, ground unit IP 192.168.1.11, air unit IP 192.168.1.12, key 0001.\n\n### UART serial port interface configuration\n\n|

Interface<\/div> |

Configuration instructions<\/div> |

Parameter Description<\/div> |\n| :--- | :--- | :--- |\n| **UART0 Switch**
*It is recommended to keep it always on by default from the factory.* | `At^uartipfun=1` | `1`\uff1aOpen |\n| **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\"`\uff1aBaud rate
`14550`\uff1aLocal\/Remote UDP Port
`\"0.0.0.0\"`\uff1aLocal IP (any)
`\"192.168.1.100\"`\uff1aTarget IP address |\n| **UART0 MAVLink 2.0 Protocol Configuration**
*Commonly used, recommended as the factory configuration, though not strictly required in actual testing.* | `at^Uartipfrs=0`
`at^uartipfrl=0`
`at^Uartipfrs=1,1,fd`
`at^uartipfrl=1,0,1,1,12` | Used to configure the start condition, length, and parsing rules of serial data frames. |\n| **UART1\/UART2 Switch**
*It is recommended to keep it always on by default from the factory.* | `At^uartfun=1` | `1`\uff1aOn (UART1 and UART2 share this switch) |\n| **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\"`\uff1aTarget IP
`\"14551\"`\uff1aLocal\/remote ports
`\"B115200\"`\uff1aBaud rate
`\"8\"`\uff1aData bit
`\"1\"`\uff1aStop bit
`\"N\"`\uff1aNo verification |\n| **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\"`\uff1aTarget IP
`\"14552\"`\uff1aLocal\/remote ports
`\"B115200\"`\uff1aBaud rate
`Other parameters are the same as above` |\n\n## Star Networking Tutorial\n\n### **Central Node (Ground Unit)**\n| Central Node | Explanation |\n| :--- | :--- |\n| `AT+CFUN=0` | Soft Shutdown |\n| `AT^DAOCNDI=04` | Set the frequency band to 1427.9\u20131447.9 MHz |\n| `AT^DAPI=\"11223344\"` | Set Access Key |\n| `at^drps=14379,5,\"26\"` | Set the main antenna operating bandwidth to 20 MHz, transmit power to +26 dBm. |\n| `AT^DFHC=1` | Enable Automatic Frequency Hopping |\n| `AT^ddtc=1` | Set as Central Node |\n| `AT^DSONSSF=9,0` | Disable Wideband Adaptive |\n| `AT^DSONSSF=7,0` | Disable Point-to-Point Mode |\n| `AT^DSTC=3` | Set the uplink\/downlink timeslot ratio to 4U1D |\n| `at^netifcfg=2,\"192.168.1.11\"` | Set the network interface IP address to 192.168.1.11 |\n| `AT^POWERCTL=1` | Software Restart |\n| **Power Cycle** | **Physical Power Cycle** |\n\n\n### **Access Node (Air Unit)**\n| Configuration instructions | Explanation |\n| :--- | :--- |\n| `AT+CFUN=0` | Soft Shutdown |\n| `AT^DAOCNDI=04` | Set the frequency band to 1427.9\u20131447.9 MHz |\n| `AT^DAPI=\"11223344\"` | Set Access Key |\n| `AT^ddtc=2` | Set as Access Node |\n| `AT^DSONSSF=9,0` | Disable Wideband Adaptive |\n| `AT^DSONSSF=7,0` | Disable Point-to-Point Mode |\n| `AT^DSSMTP=\"26\"` | Set the access node maximum transmit power to +26 dBm |\n| `AT^DSTC=3` | Set the uplink\/downlink timeslot ratio to 4U1D |\n| `at^netifcfg=2,\"192.168.1.20\"` | Set the IP address of Access Node 1 to 192.168.1.20, then restart after success. |\n| `at^netifcfg=2,\"192.168.1.21\"` | Set the IP address of Access Node 2 to 192.168.1.21, then restart after success. |\n| `at^netifcfg=2,\"192.168.1.22\"` | Set the IP address of Access Node 3 to 192.168.1.22, then restart after success. |\n| `at^netifcfg=2,\"192.168.1.23\"` | Set the IP address of Access Node 4 to 192.168.1.23, then restart after success. |\n| `at^netifcfg=2,\"192.168.1.24\"` | Set the IP address of Access Node 5 to 192.168.1.24, then restart after success. |\n| `AT^POWERCTL=1` | Software restart the device. |\n| **Power Cycle** | **Physical Power Cycle** |\n\n## Frequently Asked Questions Troubleshooting Manual\n\n### 1. Ethernet Port Issue: Unable to Connect to the R30 Web Interface\n\n| Troubleshooting steps | Inspection items | Phenomenon\/Instruction | Judgment and Solution |\n| :--- | :--- | :--- | :--- |\n| **Step 1: LED Indicator** | **PWR (Power) LED: Red** | **Steady on** | Steady on |\n| | | **Off** | Module power supply is abnormal.**Requires return to factory for repair.** |\n| | **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**. |\n| | | **Off** |1. Check that the network cable is properly connected.
2. The Ethernet port chip is operating abnormally; further troubleshooting is required. |\n| **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.
![](https:\/\/resource-wangsu.helplook.net\/docker_production\/loaufg\/article\/IetsqdfT\/692ed3bec20cd.png)|\n| **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**\u3002 |\n\n---\n\n### 2. Link Issue: Web Interface Accessible but Unable to Establish Connection\n\n| Troubleshooting steps | Inspection items | Phenomenon\/Instruction | Judgment and Solution |\n| :--- | :--- | :--- | :--- |\n| **Step 1: External Environment** | **Signal Interference** | - | Check whether there is strong interference from nearby 1.4 GHz or 2.4 GHz signal sources. |\n| | **Antenna Connection** | - | Check that the antennas are correctly and securely connected to the device. |\n| **Step 2: LED Indicator** | **Link Status LED** | **Central Node**\uff1aVIBR blue LED**steady on.**
**Slave Node**\uff1aVFLASH green LED**steady on**, VIBR blue LED**flashing**. | 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. |\n| **Step 3: Web Configuration** | **Access Key** | - | Ensure the**Access Key**is exactly the same on all devices. An incorrect key will prevent link establishment. |\n| | **Operating Frequency Band** | - | Ensure all devices are configured on the**same frequency band**(e.g., 04 or 08). |\n| **Step 4: AT Command Query** | **Continuous Transmission State** | `AT^DSONCTX?` | Query the current continuous transmission state; **it must be OFF**. |","pure_content":"Product Introduction\n\n1.4 GHz and 2.4 GHz dual-band communication\nMaximum communication distance: 30 km; bandwidth: 30 Mbps\nSupports up to 32 communication nodes with star networking\nAutomatic frequency hopping for strong anti-interference capability\nBuilt-in active cooling design\nOptimized specifically for the MAVLink protocol\n\nProduct Specification\n\n\n\n Item\n Specification\n\n\n\n\n Communication frequency band\n 2400-2483.5 MHz\u00a0 1427.9-1447.9MHz\u00a0\n\n\n Communication bandwidth\n 30Mbps\n\n\n Anti-jamming\n Dynamic Frequency Hopping\n\n\n Power level\n 2.4G \u00a025dBm\u00b12\u00a0 1.4G \u00a025dBm\u00b12 (Optional)\n\n\n Communication range\n Max 30 km (one-to-one, interference-free, line-of-sight environment)\n\n\n Communication node\n Maximum 32\n\n\n Encryption method\n ZUC, SNOW3G, AES \u2014 three selectable encryption methods.\n\n\n Modulation scheme\n Supports QPSK, 16QAM, and 64QAM modulation schemes.\n\n\n Air Interface Latency\n UL one-way latency\n\n Sensitivity (BLER 2.4G(Channel 24415):\u00a0 20MHz \u00a0-92dBm(10Mbps)\u00a0 20MHz \u00a0-96dBm(5Mbps) 10MHz \u00a0-89dBm(10Mbps)\u00a0 10MHz \u00a0-92dBm(5Mbps)1.4G(Channel 14379):\u00a0 20MHz \u00a0-86dBm(20Mbps)\u00a0 20MHz \u00a0-97dBm(5Mbps)\u00a0 10MHz \u00a0-88dBm(10Mbps)\u00a0 10MHz \u00a0-94dBm(5Mbps)\n\n\n Web page configuration\n Supports browser-based login and configuration (Edge recommended)\n\n\n Interface details\n DC IN \u00d71, SBUS IN \u00d71, Serial Port \u00d72, Ethernet Port \u00d71\n\n\n Power consumption\n Overall operating power consumption\n\n Heat dissipation\n Built-in Active Cooling\n\n\n Operating Temperature\n -20\u00b0C \uff5e 75\u00b0C\u00a0\n\n\n Working voltage\n 24\u00b110V \u00a0\n\n\n Size\n \u00a0 91mm\u00d761.2mm\u00d718mm\n\n\n Weight\n \u00a0 132g\n\n\n\nInterface Definition\n\nUsage Notes\n\nThe distance between the main antenna (MAIN ANT) and the secondary antenna (SLAVE ANT) should be greater than 20 cm. Antenna extension cables are included.\nThe included omnidirectional antennas should be installed vertically upward on the ground side, and vertically upward or downward on the air side.\nThe VSWR of the included omnidirectional antennas is lower when folded than when unfolded, resulting in better communication performance in the folded state.\nThe antennas must not be placed directly against carbon fiber or metal, and there should be no metal or carbon fiber obstructions nearby.\nWhen the ground side and air side are within 2 meters of each other, the flight controller may fail to receive the relayed SBUS signal, and commands uploaded from the ground station may experience significant latency. Please increase the distance between the ground and air links.\n\nWiring method\nGround Unit Connection Method\nConnect the ground unit's Ethernet port to your laptop's Ethernet port. Power the ground unit with a 3\u20138S battery. The RC receiver can be connected to the SBUS interface of the OneVDLink.\n\nThe link supports receiver SBUS signal forwarding.\n\n\nAir Unit Connection\nThere are two ways to connect the air unit to the flight controller for MAVLink data communication:\nConnect the air unit's Ethernet port to the flight controller's Ethernet port.\nConnect the air unit's UART to the flight controller's TELEM interface.\nUsing the UART connection is recommended, as this leaves the air unit's Ethernet port available for an Ethernet camera or gimbal.\nUsing UART Communication\nConnect 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).\nManually 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:\n\nUsing Ethernet Communication\nConnect 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.\nConfigure the flight controller network parameters as follows:\nnet_enable=1\nNET_DHCP=0\nNET_P1_TYPE=1\nNET_P1_PORT=15001 (configurable from 0 to 65535)\nNET_P1_PROTOCOL=2\nNET_P1_IP0=192\nNET_P1_IP1=168\nNET_P1_IP2=1\nNET_P1_IP3=20 (The link device has already used 11 and 12 by default; do not configure the same IP)\nOn the ground computer, manually set a static IP address of 192.168.1.20. In Mission Planner, select UDP port 15001 and click Connect.\n\n\nDefault factory configuration: Point-to-point communication, ground unit IP 192.168.1.11, air unit IP 192.168.1.12, key 0001.\n\nUART serial port interface configuration\n\n\n\n Interface\n Configuration instructions\n Parameter Description\n\n\n\n\n UART0 SwitchIt is recommended to keep it always on by default from the factory.\n At^uartipfun=1\n 1\uff1aOpen\n\n\n UART0 Basic ConfigurationConfigure the baud rate, UDP port, and destination address.\n at^UARTIP=\"B115200\",0,1,1,14550,\"0.0.0.0\",14550,\"192.168.1.100\"\n \"B115200\"\uff1aBaud rate14550\uff1aLocal\/Remote UDP Port\"0.0.0.0\"\uff1aLocal IP (any)\"192.168.1.100\"\uff1aTarget IP address\n\n\n UART0 MAVLink 2.0 Protocol ConfigurationCommonly used, recommended as the factory configuration, though not strictly required in actual testing.\n at^Uartipfrs=0at^uartipfrl=0at^Uartipfrs=1,1,fdat^uartipfrl=1,0,1,1,12\n Used to configure the start condition, length, and parsing rules of serial data frames.\n\n\n UART1\/UART2 SwitchIt is recommended to keep it always on by default from the factory.\n At^uartfun=1\n 1\uff1aOn (UART1 and UART2 share this switch)\n\n\n UART1 ConfigurationConfigure the network and serial port parameters for UART1.\n AT^UART1SET=\"192.168.1.100\",\"14551\",\"14551\",\"B115200\",\"8\",\"1\",\"N\"\n \"192.168.1.100\"\uff1aTarget IP\"14551\"\uff1aLocal\/remote ports\"B115200\"\uff1aBaud rate\"8\"\uff1aData bit\"1\"\uff1aStop bit\"N\"\uff1aNo verification\n\n\n UART2 ConfigurationConfigure the network and serial port parameters for UART2.\n AT^UART2SET=\"192.168.1.100\",\"14552\",\"14552\",\"B115200\",\"8\",\"1\",\"N\"\n \"192.168.1.100\"\uff1aTarget IP\"14552\"\uff1aLocal\/remote ports\"B115200\"\uff1aBaud rateOther parameters are the same as above\n\n\n\nStar Networking Tutorial\nCentral Node (Ground Unit)\n\n\n\n Central Node\n Explanation\n\n\n\n\n AT+CFUN=0\n Soft Shutdown\n\n\n AT^DAOCNDI=04\n Set the frequency band to 1427.9\u20131447.9 MHz\n\n\n AT^DAPI=\"11223344\"\n Set Access Key\n\n\n at^drps=14379,5,\"26\"\n Set the main antenna operating bandwidth to 20 MHz, transmit power to +26 dBm.\n\n\n AT^DFHC=1\n Enable Automatic Frequency Hopping\n\n\n AT^ddtc=1\n Set as Central Node\n\n\n AT^DSONSSF=9,0\n Disable Wideband Adaptive\n\n\n AT^DSONSSF=7,0\n Disable Point-to-Point Mode\n\n\n AT^DSTC=3\n Set the uplink\/downlink timeslot ratio to 4U1D\n\n\n at^netifcfg=2,\"192.168.1.11\"\n Set the network interface IP address to 192.168.1.11\n\n\n AT^POWERCTL=1\n Software Restart\n\n\n Power Cycle\n Physical Power Cycle\n\n\n\nAccess Node (Air Unit)\n\n\n\n Configuration instructions\n Explanation\n\n\n\n\n AT+CFUN=0\n Soft Shutdown\n\n\n AT^DAOCNDI=04\n Set the frequency band to 1427.9\u20131447.9 MHz\n\n\n AT^DAPI=\"11223344\"\n Set Access Key\n\n\n AT^ddtc=2\n Set as Access Node\n\n\n AT^DSONSSF=9,0\n Disable Wideband Adaptive\n\n\n AT^DSONSSF=7,0\n Disable Point-to-Point Mode\n\n\n AT^DSSMTP=\"26\"\n Set the access node maximum transmit power to +26 dBm\n\n\n AT^DSTC=3\n Set the uplink\/downlink timeslot ratio to 4U1D\n\n\n at^netifcfg=2,\"192.168.1.20\"\n Set the IP address of Access Node 1 to 192.168.1.20, then restart after success.\n\n\n at^netifcfg=2,\"192.168.1.21\"\n Set the IP address of Access Node 2 to 192.168.1.21, then restart after success.\n\n\n at^netifcfg=2,\"192.168.1.22\"\n Set the IP address of Access Node 3 to 192.168.1.22, then restart after success.\n\n\n at^netifcfg=2,\"192.168.1.23\"\n Set the IP address of Access Node 4 to 192.168.1.23, then restart after success.\n\n\n at^netifcfg=2,\"192.168.1.24\"\n Set the IP address of Access Node 5 to 192.168.1.24, then restart after success.\n\n\n AT^POWERCTL=1\n Software restart the device.\n\n\n Power Cycle\n Physical Power Cycle\n\n\n\nFrequently Asked Questions Troubleshooting Manual\n1. Ethernet Port Issue: Unable to Connect to the R30 Web Interface\n\n\n\n Troubleshooting steps\n Inspection items\n Phenomenon\/Instruction\n Judgment and Solution\n\n\n\n\n Step 1: LED Indicator\n PWR (Power) LED: Red\n Steady on\n Steady on\n\n\n \n \n Off\n Module power supply is abnormal.Requires return to factory for repair.\n\n\n \n ETH (Ethernet) Green LED\n Steady on\n 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.\n\n\n \n \n Off\n 1. Check that the network cable is properly connected.2. The Ethernet port chip is operating abnormally; further troubleshooting is required.\n\n\n Step 2: AT Command Query\n Check the actual IP configuration.\n AT^NETIFCFG?\n 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.\n\n\n Step 3: Initialization\n Restore factory settings\n AT^RECOVSET=1\n When encountering other special situations, try initializing the module.Note: After initialization, the IP will revert to the default 192.168.1.12\u3002\n\n\n\n\n2. Link Issue: Web Interface Accessible but Unable to Establish Connection\n\n\n\n Troubleshooting steps\n Inspection items\n Phenomenon\/Instruction\n Judgment and Solution\n\n\n\n\n Step 1: External Environment\n Signal Interference\n -\n Check whether there is strong interference from nearby 1.4 GHz or 2.4 GHz signal sources.\n\n\n \n Antenna Connection\n -\n Check that the antennas are correctly and securely connected to the device.\n\n\n Step 2: LED Indicator\n Link Status LED\n Central Node\uff1aVIBR blue LEDsteady on.Slave Node\uff1aVFLASH green LEDsteady on, VIBR blue LEDflashing.\n 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.\n\n\n Step 3: Web Configuration\n Access Key\n -\n Ensure theAccess Keyis exactly the same on all devices. An incorrect key will prevent link establishment.\n\n\n \n Operating Frequency Band\n -\n Ensure all devices are configured on thesame frequency band(e.g., 04 or 08).\n\n\n Step 4: AT Command Query\n Continuous Transmission State\n AT^DSONCTX?\n Query the current continuous transmission state; it must be OFF.","is_draft":"0","editor_type":"2","file_path":"","add_time":"1783057240","update_time":"1783063740"},"pure_content":"Product Introduction\n\n1.4 GHz and 2.4 GHz dual-band communication\nMaximum communication distance: 30 km; bandwidth: 30 Mbps\nSupports up to 32 communication nodes with star networking\nAutomatic frequen"},{"id":"856757","string_id":"iuz9eiVl","status":"1","parent_id":"856755","slug":"iuz9eiVl","order":"0","name":"WebUI User Manual","type":"2","cover":"","cover_alt":"","desc":null,"website":"","contact":"","seo_title":"","seo_keyword":"","seo_desc":"","share_switch":"0","share_code":"","author":"","published_time":"1783063740","add_time":"1783057259","update_time":"1783065809","corp_auth_id":"0","verify_code_auth_id":"0","editor_type":"2","file_type":"","auth_id":"[\"856757\", \"856755\"]","content":{"content_id":"856757","content":"# Computer network configuration\n## Setup steps\n1. The PC needs to be configured with an IP address on the same subnet as the terminal device. For example, if the terminal device IP address is 192.168.1.11, configure the PC as follows:\n - Ethernet Properties \u2192 Internet Protocol Version 4 (TCP\/IPv4) Properties\n - Select \"Use the following IP address\"\n - IP address: 192.168.1.150\n - Subnet mask: 255.255.255.0\n - Default gateway: (leave blank)\n - DNS server address: (configure as needed or leave blank)\n\n> **Note**: The PC must be configured on the same subnet as the terminal device to ensure normal access to the WebUI interface, and its IP address must not conflict with the master or slave device IPs.\n\n# WebUI Instructions\n## User login\n- Default username and password: admin \/ admin\n- Default IPs in the initial version: ground unit 192.168.1.11, air unit 192.168.1.12\n- Default login URL: http:\/\/192.168.1.12\/#\/login\n![](https:\/\/resource-wangsu.helplook.net\/docker_production\/loaufg\/article\/sBX9BuOr\/69683e65ec580.png)\n## Network status\n## 1.1 Network Information\n- Displays the core networking information of the device, including CPU temperature, operating frequency, operating bandwidth, number of online nodes, number of neighboring nodes, and the automatic link information update interval.\n- ![](https:\/\/resource-wangsu.helplook.net\/docker_production\/loaufg\/article\/sBX9BuOr\/6968403482e37.png)\n\n- Link Information Details: Detected neighbor node's IP, EARFCN (operating frequency), RSRP (Reference Signal Received Power), SNR (Signal-to-Noise Ratio), DISTANCE (distance to the critical point).\n- Update Interval: Configurable time interval for updating link information with neighboring nodes.\n## 1.2 Network Topology\n- After successful networking, the Network Topology page displays the current network topology. It auto-refreshes by default and supports manually setting the refresh interval.\n ![](https:\/\/resource-wangsu.helplook.net\/docker_production\/loaufg\/article\/sBX9BuOr\/69683f7c3ea19.png)\n\n- In automatic update mode, you can click the Pop-up or Full-screen button to display the topology interface in a pop-up window or in full-screen mode.\n## 1.3 Frequency Scan\n- Function: Scan the surrounding radio environment for interference.\n- Operation: Supports scanning by selecting different frequency points. The more frequency points selected, the longer the scanning time.\n ![](https:\/\/resource-wangsu.helplook.net\/docker_production\/loaufg\/article\/sBX9BuOr\/69684160c1176.png)\n\n- Interference Judgment Criteria: Compare the sampled value with the threshold set in the AT command. If it exceeds the threshold, interference is considered present; otherwise, no interference is detected.\n\n# Basic Settings\n## Frequency band setting\n- Default supported frequency points are all selected by default. Click the checkbox to deselect or select the frequency band to configure.\n- Operation: Click \"OK\" to save and apply the settings.\n![](https:\/\/resource-wangsu.helplook.net\/docker_production\/loaufg\/article\/sBX9BuOr\/696842b8e6118.png)\n\n## Networking Settings\n- This interface allows configuration of the node's operating mode, frequency hopping, bandwidth, power, and frequency points. Detailed configuration instructions are as follows:\n- Work Mode: The device defaults to point-to-point mode and can be configured for two operating modes, including star networking.\n- Frequency Hopping: Enable or disable the frequency hopping function. Click the blue area next to the button to change the configuration; the change is automatically saved and takes effect immediately.\n- Node Settings: Allows configuration of the master node, slave node, and uplink\/downlink settings.\n- Bandwidth: Default bandwidth is 20 MHz. Five options are available: 20M, 10M, 5M, 3M, and 1.4M. After configuration, click OK at the bottom of the interface to save and apply the settings.\n- Output Power: Default transmit power is 26 dBm, adjustable according to actual conditions. After configuration, click OK at the bottom of the interface to save and apply the settings.\n- Frequency Point Setting: Grayed out by default. The frequency hopping function must be disabled before configuring the primary and secondary frequency points of the device.\n ![](https:\/\/resource-wangsu.helplook.net\/docker_production\/loaufg\/article\/sBX9BuOr\/6968431ac14a7.png)\n\n\n## Key setting\n- Function: Key configuration management and encryption algorithm settings\n- Key configuration requirements:\n1. All devices must have exactly the same key, otherwise they cannot form a network.\n2. The key must be a hexadecimal number (0\u20139, A\u2013F or a\u2013f).\n3. It must not exceed 64 characters (i.e., 32 bytes).\n4. The key must have an even number of characters.\n- Encryption algorithm: Default is SNOW3G. Four options are provided: \"NONE\", \"SNOW3G\", \"AES\", \"ZUC\". When forming a network, the encryption algorithm must be configured identically on all devices.\n ![](https:\/\/resource-wangsu.helplook.net\/docker_production\/loaufg\/article\/sBX9BuOr\/69684458d8130.png)\n ### Equipment Management\n- Function: Restart the device or restore factory settings.\n- Restart Device: Click the \"Restart Device\" button, and the device will restart automatically. Some parameter changes require a restart to take effect, which can be performed using this button.\n- Restore Factory Settings: Click the \"Restore Factory Settings\" button, and all device configurations will be restored to factory defaults.\n![](https:\/\/resource-wangsu.helplook.net\/docker_production\/loaufg\/article\/sBX9BuOr\/696844c2d3104.png)\n\n## Network Settings\n### IP Management\n- Function: Configure the device's IP address, subnet mask, gateway, and DNS according to actual conditions.\n- The configuration interface provides input fields for the corresponding parameters. After filling them in, save to apply the settings.\n![](https:\/\/resource-wangsu.helplook.net\/docker_production\/loaufg\/article\/sBX9BuOr\/6968450915700.png)\n\n\n## User Management\n### Add user\n- Function: Add administrator users or manage existing administrator accounts.\n- Steps:\n1. Click the \"Add User\" button to open the Add User interface.\n2. Enter a username and a password of at least 6 characters.\n3. Click \"OK\" to complete adding the administrator.\n- The interface includes an \"Add User\" button and a list of added users (displaying user status and other information).\n![](https:\/\/resource-wangsu.helplook.net\/docker_production\/loaufg\/article\/sBX9BuOr\/69684532c75f7.png)\n\n## Change password\n- Function: Change the administrator account password (default administrator username and password: admin\/admin).\n- Interface: Contains Old Password, New Password, and Confirm New Password input fields. Fill them in and submit to apply the change.\n ![](https:\/\/resource-wangsu.helplook.net\/docker_production\/loaufg\/article\/sBX9BuOr\/696845518b961.png)\n\n# Debugging and diagnostics\n## AT Debugging\n- Function: Configure, restart, reset, etc. the device by entering AT commands.\n- Operation: Enter an AT command in the input box and click OK to send the command; the Clear received data button clears the display of execution results.\n\n![](https:\/\/resource-wangsu.helplook.net\/docker_production\/loaufg\/article\/sBX9BuOr\/6968456aaa08e.png)\n## Shell debugging\n- Function: Manage the device by executing certain shell commands.\n- Interface: Includes a command input area and an execution result display area (showing device running status information, such as uptime, etc).\n![](https:\/\/resource-wangsu.helplook.net\/docker_production\/loaufg\/article\/sBX9BuOr\/696845af0c8a4.png)\n\n## Log switch\n- Function: Enable or disable the device LOG function. When LOG is enabled, the device automatically generates system LOGs in the background.\n ![](https:\/\/resource-wangsu.helplook.net\/docker_production\/loaufg\/article\/sBX9BuOr\/6968462d47ec8.png)\n- Export LOG method:\n1. After generating logs, use an FTP client to connect to port 200 of the device.\n2. Drag the LOG folder from the \"Remote site\" to the \"Local site\" to export the device logs.\n3. Device logs can also be deleted via this FTP connection.\n![](https:\/\/resource-wangsu.helplook.net\/docker_production\/loaufg\/article\/sBX9BuOr\/696846464c040.png)\n\n# Version Information\n- The interface displays the device's current full system version information and modem version information (e.g., C77K-11002, CV.10.02R262023102_WFFL, SONV3.10.02R26_20231012_WFHS, etc.).\n# Language settings\nSwitchable between Chinese and English\n![](https:\/\/resource-wangsu.helplook.net\/docker_production\/loaufg\/article\/sBX9BuOr\/696849b7f2476.png)\n\n# Exit Management\n- Operation: Click the \"Exit\" button on this interface to display the logout confirmation dialog.\n- After confirming, you will be logged out of the device management interface and returned to the login page.","pure_content":"Computer network configuration\nSetup steps\n\nThe PC needs to be configured with an IP address on the same subnet as the terminal device. For example, if the terminal device IP address is 192.168.1.11, configure the PC as follows:\n\n\nEthernet Properties \u2192 Internet Protocol Version 4 (TCP\/IPv4) Properties\nSelect \"Use the following IP address\"\nIP address: 192.168.1.150\nSubnet mask: 255.255.255.0\nDefault gateway: (leave blank)\nDNS server address: (configure as needed or leave blank)\n\n\nNote: The PC must be configured on the same subnet as the terminal device to ensure normal access to the WebUI interface, and its IP address must not conflict with the master or slave device IPs.\n\nWebUI Instructions\nUser login\n\nDefault username and password: admin \/ admin\nDefault IPs in the initial version: ground unit 192.168.1.11, air unit 192.168.1.12\nDefault login URL: http:\/\/192.168.1.12\/#\/login\n\n\n\nNetwork status\n1.1 Network Information\n\n\nDisplays the core networking information of the device, including CPU temperature, operating frequency, operating bandwidth, number of online nodes, number of neighboring nodes, and the automatic link information update interval.\n\n\n\n\n\nLink Information Details: Detected neighbor node's IP, EARFCN (operating frequency), RSRP (Reference Signal Received Power), SNR (Signal-to-Noise Ratio), DISTANCE (distance to the critical point).\n\n\nUpdate Interval: Configurable time interval for updating link information with neighboring nodes.\n\n\n1.2 Network Topology\n\n\nAfter successful networking, the Network Topology page displays the current network topology. It auto-refreshes by default and supports manually setting the refresh interval.\n\n\n\nIn automatic update mode, you can click the Pop-up or Full-screen button to display the topology interface in a pop-up window or in full-screen mode.\n\n\n1.3 Frequency Scan\n\n\nFunction: Scan the surrounding radio environment for interference.\n\n\nOperation: Supports scanning by selecting different frequency points. The more frequency points selected, the longer the scanning time.\n\n\n\nInterference Judgment Criteria: Compare the sampled value with the threshold set in the AT command. If it exceeds the threshold, interference is considered present; otherwise, no interference is detected.\n\n\nBasic Settings\nFrequency band setting\n\nDefault supported frequency points are all selected by default. Click the checkbox to deselect or select the frequency band to configure.\nOperation: Click \"OK\" to save and apply the settings.\n\n\n\nNetworking Settings\n\nThis interface allows configuration of the node's operating mode, frequency hopping, bandwidth, power, and frequency points. Detailed configuration instructions are as follows:\nWork Mode: The device defaults to point-to-point mode and can be configured for two operating modes, including star networking.\nFrequency Hopping: Enable or disable the frequency hopping function. Click the blue area next to the button to change the configuration; the change is automatically saved and takes effect immediately.\nNode Settings: Allows configuration of the master node, slave node, and uplink\/downlink settings.\nBandwidth: Default bandwidth is 20 MHz. Five options are available: 20M, 10M, 5M, 3M, and 1.4M. After configuration, click OK at the bottom of the interface to save and apply the settings.\nOutput Power: Default transmit power is 26 dBm, adjustable according to actual conditions. After configuration, click OK at the bottom of the interface to save and apply the settings.\nFrequency Point Setting: Grayed out by default. The frequency hopping function must be disabled before configuring the primary and secondary frequency points of the device.\n\n\n\nKey setting\n\nFunction: Key configuration management and encryption algorithm settings\nKey configuration requirements:\n\n\nAll devices must have exactly the same key, otherwise they cannot form a network.\nThe key must be a hexadecimal number (0\u20139, A\u2013F or a\u2013f).\nIt must not exceed 64 characters (i.e., 32 bytes).\nThe key must have an even number of characters.\n\n\nEncryption algorithm: Default is SNOW3G. Four options are provided: \"NONE\", \"SNOW3G\", \"AES\", \"ZUC\". When forming a network, the encryption algorithm must be configured identically on all devices.\n\n\n\nEquipment Management\n\nFunction: Restart the device or restore factory settings.\nRestart Device: Click the \"Restart Device\" button, and the device will restart automatically. Some parameter changes require a restart to take effect, which can be performed using this button.\nRestore Factory Settings: Click the \"Restore Factory Settings\" button, and all device configurations will be restored to factory defaults.\n\n\n\nNetwork Settings\nIP Management\n\nFunction: Configure the device's IP address, subnet mask, gateway, and DNS according to actual conditions.\nThe configuration interface provides input fields for the corresponding parameters. After filling them in, save to apply the settings.\n\n\n\nUser Management\nAdd user\n\nFunction: Add administrator users or manage existing administrator accounts.\nSteps:\n\n\nClick the \"Add User\" button to open the Add User interface.\nEnter a username and a password of at least 6 characters.\nClick \"OK\" to complete adding the administrator.\n\n\nThe interface includes an \"Add User\" button and a list of added users (displaying user status and other information).\n\n\n\nChange password\n\nFunction: Change the administrator account password (default administrator username and password: admin\/admin).\nInterface: Contains Old Password, New Password, and Confirm New Password input fields. Fill them in and submit to apply the change.\n\n\n\nDebugging and diagnostics\nAT Debugging\n\nFunction: Configure, restart, reset, etc. the device by entering AT commands.\nOperation: Enter an AT command in the input box and click OK to send the command; the Clear received data button clears the display of execution results.\n\n\nShell debugging\n\nFunction: Manage the device by executing certain shell commands.\nInterface: Includes a command input area and an execution result display area (showing device running status information, such as uptime, etc).\n\n\n\nLog switch\n\nFunction: Enable or disable the device LOG function. When LOG is enabled, the device automatically generates system LOGs in the background.\n\n\nExport LOG method:\n\n\nAfter generating logs, use an FTP client to connect to port 200 of the device.\nDrag the LOG folder from the \"Remote site\" to the \"Local site\" to export the device logs.\nDevice logs can also be deleted via this FTP connection.\n\n\n\nVersion Information\n\nThe interface displays the device's current full system version information and modem version information (e.g., C77K-11002, CV.10.02R262023102_WFFL, SONV3.10.02R26_20231012_WFHS, etc.).\n\nLanguage settings\nSwitchable between Chinese and English\n\nExit Management\n\nOperation: Click the \"Exit\" button on this interface to display the logout confirmation dialog.\nAfter confirming, you will be logged out of the device management interface and returned to the login page.","is_draft":"0","editor_type":"2","file_path":"","add_time":"1783057259","update_time":"1783065809"},"pure_content":"Computer network configuration\nSetup steps\n\nThe PC needs to be configured with an IP address on the same subnet as the terminal device. For example, if the terminal device IP address is 192.168.1.11,"},{"id":"856758","string_id":"RAjaLYb3","status":"1","parent_id":"856755","slug":"RAjaLYb3","order":"0","name":"Quick Start Guide","type":"2","cover":"","cover_alt":"","desc":null,"website":"","contact":"","seo_title":"","seo_keyword":"","seo_desc":"","share_switch":"0","share_code":"","author":"","published_time":"1783063740","add_time":"1783057277","update_time":"1783066008","corp_auth_id":"0","verify_code_auth_id":"0","editor_type":"2","file_type":"","auth_id":"[\"856758\", \"856755\"]","content":{"content_id":"856758","content":"apm\u56fa\u4ef6\u7f51\u53e3\u901a\u4fe1\n\n\n\u9ed8\u8ba4\u53c2\u6570\u914d\u7f6e\n\u5730\u9762\u7aef\n\u7ec4\u7f51\u6a21\u5f0f\uff1a\u70b9\u5bf9\u70b9\u901a\u4fe1\n\u672c\u673aip\uff1a192.168.1.11\n\u5bc6\u94a5\uff1a0001\n\u53d1\u5c04\u529f\u7387\uff1a26dBm\nuart0:\u901a\u4fe1\u6ce2\u7279\u7387115200\uff0c\u76ee\u6807ip\uff1a192.168.1.100\uff0c\u901a\u4fe1\u7aef\u53e314550\nuart1:\u901a\u4fe1\u6ce2\u7279\u7387115200\uff0c\u76ee\u6807ip\uff1a192.168.1.100\uff0c\u901a\u4fe1\u7aef\u53e314551\nuart2:\u901a\u4fe1\u6ce2\u7279\u7387115200\uff0c\u76ee\u6807ip\uff1a192.168.1.100\uff0c\u901a\u4fe1\u7aef\u53e314552\n\n\u5929\u7a7a\u7aef\n\u7ec4\u7f51\u6a21\u5f0f\uff1a\u70b9\u5bf9\u70b9\u901a\u4fe1\n\u672c\u673aip\uff1a192.168.1.12\n\u5bc6\u94a5\uff1a0001\n\u53d1\u5c04\u529f\u7387\uff1a26dBm\n\n\u53ef\u4f7f\u7528UART\u6216\u8005\u7f51\u53e3\u6765\u5b8c\u6210\u98de\u63a7\u548c\u5730\u9762\u7ad9\u901a\u4fe1\n\u4e32\u53e3\u901a\u4fe1\u65b9\u5f0f\uff1a\n \u63a5\u7ebf\uff1a\u5929\u7a7a\u7aef\u7684uart1\u63a5\u98de\u63a7telem1\uff0c\u5730\u9762\u7aef\u7f51\u53e3\u63a5\u7535\u8111\u7f51\u53e3\n \u98de\u63a7\u914d\u7f6e\uff1aserial1_protocol\u8bbe\u7f6e115\n \u7535\u8111\u8bbe\u7f6e\u9759\u6001ip\uff1a192.168.1.100\n mission planner\u9009UDP\uff0c\u7aef\u53e314551\uff0c\u8fde\u63a5\u901a\u4fe1\u3002\n\n\u7f51\u53e3\u901a\u4fe1\u65b9\u5f0f\uff1a\n\u63a5\u7ebf\uff1a\u5929\u7a7a\u7aef\u7684\u7f51\u53e3\u63a5\u98de\u63a7\u7f51\u53e3\uff0c\u5730\u9762\u7aef\u7f51\u53e3\u63a5\u7535\u8111\u7f51\u53e3\n\u98de\u63a7\u914d\u7f6e\uff1a","pure_content":"apm\u56fa\u4ef6\u7f51\u53e3\u901a\u4fe1\n\u9ed8\u8ba4\u53c2\u6570\u914d\u7f6e\n\u5730\u9762\u7aef\n\u7ec4\u7f51\u6a21\u5f0f\uff1a\u70b9\u5bf9\u70b9\u901a\u4fe1\n\u672c\u673aip\uff1a192.168.1.11\n\u5bc6\u94a5\uff1a0001\n\u53d1\u5c04\u529f\u7387\uff1a26dBm\nuart0:\u901a\u4fe1\u6ce2\u7279\u7387115200\uff0c\u76ee\u6807ip\uff1a192.168.1.100\uff0c\u901a\u4fe1\u7aef\u53e314550\nuart1:\u901a\u4fe1\u6ce2\u7279\u7387115200\uff0c\u76ee\u6807ip\uff1a192.168.1.100\uff0c\u901a\u4fe1\u7aef\u53e314551\nuart2:\u901a\u4fe1\u6ce2\u7279\u7387115200\uff0c\u76ee\u6807ip\uff1a192.168.1.100\uff0c\u901a\u4fe1\u7aef\u53e314552\n\u5929\u7a7a\u7aef\n\u7ec4\u7f51\u6a21\u5f0f\uff1a\u70b9\u5bf9\u70b9\u901a\u4fe1\n\u672c\u673aip\uff1a192.168.1.12\n\u5bc6\u94a5\uff1a0001\n\u53d1\u5c04\u529f\u7387\uff1a26dBm\n\u53ef\u4f7f\u7528UART\u6216\u8005\u7f51\u53e3\u6765\u5b8c\u6210\u98de\u63a7\u548c\u5730\u9762\u7ad9\u901a\u4fe1\n\u4e32\u53e3\u901a\u4fe1\u65b9\u5f0f\uff1a\n\u63a5\u7ebf\uff1a\u5929\u7a7a\u7aef\u7684uart1\u63a5\u98de\u63a7telem1\uff0c\u5730\u9762\u7aef\u7f51\u53e3\u63a5\u7535\u8111\u7f51\u53e3\n\u98de\u63a7\u914d\u7f6e\uff1aserial1_protocol\u8bbe\u7f6e115\n\u7535\u8111\u8bbe\u7f6e\u9759\u6001ip\uff1a192.168.1.100\nmission planner\u9009UDP\uff0c\u7aef\u53e314551\uff0c\u8fde\u63a5\u901a\u4fe1\u3002\n\u7f51\u53e3\u901a\u4fe1\u65b9\u5f0f\uff1a\n\u63a5\u7ebf\uff1a\u5929\u7a7a\u7aef\u7684\u7f51\u53e3\u63a5\u98de\u63a7\u7f51\u53e3\uff0c\u5730\u9762\u7aef\u7f51\u53e3\u63a5\u7535\u8111\u7f51\u53e3\n\u98de\u63a7\u914d\u7f6e\uff1a","is_draft":"0","editor_type":"2","file_path":"","add_time":"1783057277","update_time":"1783063740"},"pure_content":"apm\u56fa\u4ef6\u7f51\u53e3\u901a\u4fe1\n\u9ed8\u8ba4\u53c2\u6570\u914d\u7f6e\n\u5730\u9762\u7aef\n\u7ec4\u7f51\u6a21\u5f0f\uff1a\u70b9\u5bf9\u70b9\u901a\u4fe1\n\u672c\u673aip\uff1a192.168.1.11\n\u5bc6\u94a5\uff1a0001\n\u53d1\u5c04\u529f\u7387\uff1a26dBm\nuart0:\u901a\u4fe1\u6ce2\u7279\u7387115200\uff0c\u76ee\u6807ip\uff1a192.168.1.100\uff0c\u901a\u4fe1\u7aef\u53e314550\nuart1:\u901a\u4fe1\u6ce2\u7279\u7387115200\uff0c\u76ee\u6807ip\uff1a192.168.1.100\uff0c\u901a\u4fe1\u7aef\u53e314551\nuart2:\u901a\u4fe1\u6ce2\u7279\u7387115200\uff0c\u76ee\u6807ip\uff1a192.168.1.100\uff0c"},{"id":"856759","string_id":"bDLppc4x","status":"1","parent_id":"856755","slug":"bDLppc4x","order":"0","name":"Connect to Third-party GCS","type":"2","cover":"","cover_alt":"","desc":null,"website":"","contact":"","seo_title":"","seo_keyword":"","seo_desc":"","share_switch":"0","share_code":"","author":"","published_time":"1783063740","add_time":"1783057288","update_time":"1783066549","corp_auth_id":"0","verify_code_auth_id":"0","editor_type":"2","file_type":"","auth_id":"[\"856759\", \"856755\"]","content":{"content_id":"856759","content":"1. Confirm the flight controller's TELEM baud rate (default: 115200).\n2. Enter the AT command on the master node.\n

\n3. Set the ground station IP.\n4. Open the ground station software.\n

\n5. Click [Link Aircraft]\n6. Click [Wireless Link]\n7. Select [UDP]\n

\n8. In the remote address field, enter the air unit's IP address 192.168.1.100 (default is 192.168.1.12), and enter port 14551.\n9. Click\u3010OK\u3011\n

\n10. Complete the link.","pure_content":"Confirm the flight controller's TELEM baud rate (default: 115200).\nEnter the AT command on the master node.\n\n\nSet the ground station IP.\nOpen the ground station software.\n\n\nClick [Link Aircraft]\nClick [Wireless Link]\nSelect [UDP]\n\n\nIn the remote address field, enter the air unit's IP address 192.168.1.100 (default is 192.168.1.12), and enter port 14551.\nClick\u3010OK\u3011\n\n\nComplete the link.","is_draft":"0","editor_type":"2","file_path":"","add_time":"1783057288","update_time":"1783066549"},"pure_content":"Confirm the flight controller's TELEM baud rate (default: 115200).\nEnter the AT command on the master node.\n\n\nSet the ground station IP.\nOpen the ground station software.\n\n\nClick [Link Aircraft]\nClic"},{"id":"856761","string_id":"RGwUw0TQ","status":"1","parent_id":"856755","slug":"RGwUw0TQ","order":"0","name":"Serial Forwarding of RTK Base Station Data","type":"2","cover":"","cover_alt":"","desc":null,"website":"","contact":"","seo_title":"","seo_keyword":"","seo_desc":"","share_switch":"0","share_code":"","author":"","published_time":"1783063740","add_time":"1783057316","update_time":"1783067787","corp_auth_id":"0","verify_code_auth_id":"0","editor_type":"2","file_type":"","auth_id":"[\"856761\", \"856755\"]","content":{"content_id":"856761","content":"### Functional Overview\nThe RTCM data from the base station is transmitted via UART2 of the ground VDLink R30 to the UART2 interface of the air-side R30, enabling RTK differential high-precision positioning.\n### Wiring method:\nTaking the OneRTK UM982 as an example:\n\nFor the base station: connect the base station's TX to the R30's RX, and GND to GND. An external 5V UBEC is required to power the RTK module, or you can use a Type-C power supply, in which case the DP and DM signal lines on the Type-C cable must be disconnected (since UART2 and the Type-C interface share the same serial port on the OneRTK UM982).\n\nFor the rover: connect the rover's RX to the R30's TX, and GND to GND. The module communicates with the flight controller via CAN.\n\n### RTK Base Station Configuration:\nFor example, when using the OneRTK UM982 as a base station to output RTCM data, configure UART2 of the module to a baud rate of 115200. The detailed tutorial is as follows:\nhttps:\/\/portal.helplook.net\/content\/266977\n### RTK Rover Configuration:\nThe serial baud rate of the RTK rover also needs to be configured to 115200. For example, the OneRTK UM982 has UART2 set to 115200 by default.\n\n### VDLink R30 Configuration:\nFor example, the IPs are as follows: the destination address in each case is the VDLink R30 on the opposite end, and is independent of the host computer's IP.\nGround unit IP: 192.168.1.11\nAir unit IP: 192.168.1.12\n#### Ground Unit AT Configuration\nConnect to the R30 via the Ethernet port and access the web interface. Navigate to [Debug & Diagnostics] \u2192 [AT Debug], enter the following commands. After the commands take effect, the execution result will display ok.\nAT^UARTIPFUN3=1\nAT^UARTIP3=\"B115200\",0,1,1,9002,\"192.168.1.11\",9001,\"192.168.1.12\"\n![](https:\/\/resource-wangsu.helplook.net\/docker_production\/loaufg\/article\/XjXjKybu\/69e5ddfc71320.png)\n![](https:\/\/resource-wangsu.helplook.net\/docker_production\/loaufg\/article\/XjXjKybu\/69e5de2293229.png)\nFor the AT command described above, on Board A, the local IP is 192.168.1.11, the local port is 9002, the remote IP is 192.168.1.12, and the remote port is 9001.\nThis AT command encapsulates UART2 data into UDP network packets with a source port of 9002, source IP of 192.168.1.11, destination port of 9001, and destination IP of 192.168.1.12, using a serial baud rate of 115200.\n\n#### Air Unit AT Configuration\nConnect to the R30 via the Ethernet port and access the web interface. Navigate to [Debug & Diagnostics] \u2192 [AT Debug], enter the following commands. After the commands take effect, the execution result will display ok.\nAT^UARTIPFUN3=1\nAT^UARTIP3=\"B115200\",0,1,1,9001,\"192.168.1.12\",9002,\"192.168.1.11\"\n![](https:\/\/resource-wangsu.helplook.net\/docker_production\/loaufg\/article\/XjXjKybu\/69e5de71edc7e.png)\n![](https:\/\/resource-wangsu.helplook.net\/docker_production\/loaufg\/article\/XjXjKybu\/69e5de899d73d.png)\nFor the AT command described above, on Board B, the local IP is 192.168.1.12, the local port is 9001, the remote IP is 192.168.1.11, and the remote port is 9002.\nThis AT command encapsulates UART2 data into UDP network packets with a source port of 9001, source IP of 192.168.1.12, destination port of 9002, and destination IP of 192.168.1.11, using a serial baud rate of 115200.","pure_content":"Functional Overview\nThe RTCM data from the base station is transmitted via UART2 of the ground VDLink R30 to the UART2 interface of the air-side R30, enabling RTK differential high-precision positioning.\nWiring method:\nTaking the OneRTK UM982 as an example:\nFor the base station: connect the base station's TX to the R30's RX, and GND to GND. An external 5V UBEC is required to power the RTK module, or you can use a Type-C power supply, in which case the DP and DM signal lines on the Type-C cable must be disconnected (since UART2 and the Type-C interface share the same serial port on the OneRTK UM982).\nFor the rover: connect the rover's RX to the R30's TX, and GND to GND. The module communicates with the flight controller via CAN.\nRTK Base Station Configuration:\nFor example, when using the OneRTK UM982 as a base station to output RTCM data, configure UART2 of the module to a baud rate of 115200. The detailed tutorial is as follows:\nhttps:\/\/portal.helplook.net\/content\/266977\nRTK Rover Configuration:\nThe serial baud rate of the RTK rover also needs to be configured to 115200. For example, the OneRTK UM982 has UART2 set to 115200 by default.\nVDLink R30 Configuration:\nFor example, the IPs are as follows: the destination address in each case is the VDLink R30 on the opposite end, and is independent of the host computer's IP.\nGround unit IP: 192.168.1.11\nAir unit IP: 192.168.1.12\nGround Unit AT Configuration\nConnect to the R30 via the Ethernet port and access the web interface. Navigate to [Debug & Diagnostics] \u2192 [AT Debug], enter the following commands. After the commands take effect, the execution result will display ok.\nAT^UARTIPFUN3=1\nAT^UARTIP3=\"B115200\",0,1,1,9002,\"192.168.1.11\",9001,\"192.168.1.12\"\n\n\nFor the AT command described above, on Board A, the local IP is 192.168.1.11, the local port is 9002, the remote IP is 192.168.1.12, and the remote port is 9001.\nThis AT command encapsulates UART2 data into UDP network packets with a source port of 9002, source IP of 192.168.1.11, destination port of 9001, and destination IP of 192.168.1.12, using a serial baud rate of 115200.\nAir Unit AT Configuration\nConnect to the R30 via the Ethernet port and access the web interface. Navigate to [Debug & Diagnostics] \u2192 [AT Debug], enter the following commands. After the commands take effect, the execution result will display ok.\nAT^UARTIPFUN3=1\nAT^UARTIP3=\"B115200\",0,1,1,9001,\"192.168.1.12\",9002,\"192.168.1.11\"\n\n\nFor the AT command described above, on Board B, the local IP is 192.168.1.12, the local port is 9001, the remote IP is 192.168.1.11, and the remote port is 9002.\nThis AT command encapsulates UART2 data into UDP network packets with a source port of 9001, source IP of 192.168.1.12, destination port of 9002, and destination IP of 192.168.1.11, using a serial baud rate of 115200.","is_draft":"0","editor_type":"2","file_path":"","add_time":"1783057316","update_time":"1783067787"},"pure_content":"Functional Overview\nThe RTCM data from the base station is transmitted via UART2 of the ground VDLink R30 to the UART2 interface of the air-side R30, enabling RTK differential high-precision positioni"}],"content":{"icon":"","desc":"","content_id":"856755","add_time":"1783057221","update_time":"1783057221","content":"","is_traffic_less":"0","file_type":""},"hot_list":[],"user_read_num":"0","is_auth":"0"},"msg":"Success","code":200}