Configuring a video/data link module can now also be assisted by an AI Agent.

The LQ10 is a 5.8 GHz long-range video/data link module that combines high bandwidth, low latency, long range, and flexible networking capabilities. In broadband mode, measured bandwidth can reach 100 Mbps at 1 km and up to 80 Mbps within 1.5 km. In narrowband mode, reliable ground-to-air communication distance can reach 7 km, meeting the needs of video transmission, control commands, and mission data transmission for drones, unmanned ground vehicles, robots, and other applications.

In the past, the LQ10 was mainly configured through a web page, which was suitable for debugging a single device. However, in batch deployment scenarios, logging in to each device one by one, modifying parameters item by item, then saving and rebooting separately is inefficient and can easily lead to missed configurations, incorrect settings, or inconsistent parameter records.

This LQ10 firmware update does two things: it resolves a series of stability issues reported by users, and it also completes the AT command module. Combined with the Agents.md configuration file, users can let an AI Agent automatically generate configuration plans and AT command procedures based on natural-language requirements, making batch deployment, engineering integration, and later maintenance more efficient.

If you are using the LQ10, or need to deploy wireless video/data link modules in batches, you can quickly complete configuration by using the LQ10 Agents.md configuration file together with the AT command set.

A link to the configuration file is provided at the end of this article for one-click access.

01

Configuration Method Upgrade

After the LQ10 supports the AT command set, many parameter settings that previously had to be completed in the web page can now also be completed through terminal commands.

This means engineers can query device status, set network parameters, adjust wireless modes, configure serial-port parameters, and establish serial-to-UDP/TCP routing rules in a more direct way. The configuration process can be copied, saved, reviewed, and more easily organized into scripts, host-computer tools, or automated deployment workflows.

The value of AT commands is not just "another input method." They turn the configuration process from manual clicking into engineering steps that are recordable, reusable, and integrable.

The current AT command coverage is as follows:

System Management

AT+FWVER? - Query software and hardware version numbers

AT+DEVID? - Query the unique device ID

AT+UPTIME? - Query system uptime

AT+REBOOT - Reboot the system

AT+APPRESET - Reset the application

 

Network Configuration

AT+IPCFG - Set and query IP address / subnet mask / gateway

 

Wireless & RF

AT+RFINFO? - Query current RSSI and RF mode (narrow / wide)

AT+WIFIMODE - Switch Wi-Fi mode (AP / STA)

AT+WIFICFG - Detailed Wi-Fi configuration (SSID, channel, encryption method, password)

AT+WBMODE - Switch between narrowband and broadband modes

AT+NRCFG - Configure narrowband rate (adaptive / manual)

 

Logical Interfaces

AT+MSS - MSS switch

AT+STP - STP spanning tree protocol switch

 

Serial Port & Routing

AT+UARTCFG - Configure serial-port parameters (baud rate, data bits, parity, etc.)

AT+UARTRULE - Serial-port-to-network UDP / TCP routing rules

AT+UARTGET - Query current serial-port configuration and routing

02

AI Involvement

After the AT command set is completed, the LQ10 also has the foundation for working with an AI Agent. In the past, users needed to repeatedly consult Wiki documentation to understand parameter meanings, command formats, and configuration sequences. The more complete the documentation and the richer the product capabilities, the higher the learning cost can become.

As AI Agents develop, hardware products need to consider a new direction from the beginning of their design: how to help AI understand product capabilities more accurately and assist users in completing configuration and operations.

This requires not only complete product functionality, but also a standardized and structured command system. The LQ10 support for a unified AT command set is one step in this direction. With the Agents.md file, an AI Agent can quickly understand device capabilities and generate configuration plans and operating procedures according to user needs, greatly lowering the barrier to learning and use.

03

Batch Configuration Example

Take a typical scenario as an example: you have 10 LQ10 modules and need to configure them as 1 base-station unit and 9 mobile units.

Previously, an engineer would first need to check the documentation, plan each device role, IP address, wireless parameters, and serial-port rules, then enter the web page for each device or manually write commands one by one. Now, the requirement can be entered directly into an AI Agent:

"I have 10 LQ10 modules. Please configure them as 1 base-station unit and 9 mobile units, and generate the corresponding configuration plan and AT command procedure for each device."

Based on the LQ10 Agents.md configuration file, the AI Agent will automatically generate a batch configuration plan and the corresponding AT commands. The plan can include device roles, IP addresses, wireless parameters, serial-port parameters, and verification procedures.

Next, the engineer only needs to execute the commands step by step and confirm the configuration results through query commands. For batch deployment, the greatest value of this method is configuration-process standardization: how each device is configured, what has been configured, and how to verify it can all be clearly recorded for review and later maintenance.

04

Stability Fixes

In addition to completing the AT command set, this firmware update also focuses on resolving a number of stability issues reported by users.

The first improvement is atomic firmware updating. Previously, users reported that if power loss or an unexpected reboot occurred during a firmware upgrade, the device might fail to start normally. In this update, the mechanism has been changed to atomic updating: either everything is written and takes effect, or the device remains unchanged. In other words, even if the upgrade is unexpectedly interrupted, the device can still run the previous firmware version after power is restored, helping avoid device lock-up caused by upgrade failure.

The second improvement is a fix for the reconnection issue in narrowband mode. In narrowband mode, the LQ10 occasionally failed to reconnect automatically after disconnection and required a manual reboot. This update identifies and fixes that issue. Narrowband mode provides long coverage distance and strong penetration capability. After this fix, communication stability in long-distance scenarios is further improved, providing more reliable communication support for long-range drone operations.

05

Experience Optimization

The web management interface has also been optimized in this update.

The web backend now supports switching between Chinese and English, making it more convenient for overseas customers and teams. Some interaction bugs on web pages have also been fixed, making operation feedback smoother.

The firmware upgrade page has also been redesigned in terms of interaction. Step prompts during the upgrade process are clearer, and progress display is more intuitive. The goal is to let users complete the upgrade process more smoothly without repeatedly checking the manual.

These experience optimizations may seem like details, but they are important for deployment and maintenance in real projects. Especially during on-site debugging of multiple devices, clear interface prompts and stable interaction feedback can reduce misoperations and improve overall maintenance efficiency.

06

Upgrade Recommendations

The focus of this update is to further improve the LQ10 in stability, maintainability, and engineering integration efficiency. If you are using the LQ10, we recommend upgrading as soon as possible.

For devices with older firmware versions, you can directly use the bridge update package to complete the upgrade in one step. Previously, older devices might have required step-by-step upgrades across versions. Now, the bridge package enables cross-version upgrading and reduces maintenance cost.

If the device is already on a newer version, you can continue using the normal incremental update package. Minor-version upgrades still use incremental packages, which are faster and consume less traffic. Before upgrading, it is recommended to back up the current configuration to avoid having to recheck key parameters after the upgrade.

The command-set documentation, firmware package, and Agents.md configuration file can be obtained through the official Wiki or by contacting technical support.

07

Final Thoughts

The LQ10 support for the AT command set is not only an update to the configuration method. It also reflects a new way for hardware products to embrace AI: by using a structured command system, an AI Agent can understand device capabilities and convert complex requirements into executable, verifiable, and maintainable operating procedures.

From web-page configuration, to the AT command set, to the Agents.md configuration file and AI Agent-generated plans, the LQ10 is making the configuration workflow for wireless video/data link modules more standardized, more efficient, and better suited to system integration scenarios involving drones, unmanned ground vehicles, robots, and other platforms.

Resource Link

Configuration file:

https://gitee.com/amovlab/lqaiconfig

(Click "Read more" at the lower left of the original article to jump to the link.)