Onboard Data Manager Framework for Low-Latency UAV Feature Control
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current UAV control systems using remote controls are limited by wireless communication latency and non-extensibility, restricting the command set and sensor integration capabilities, making them inflexible for advanced operations.
Innovation Solution
A data manager system that enables communication between a client device and an onboard data manager in a movable object environment, allowing for dynamic feature management and instruction processing, enabling the extension of available actions and sensor integration through a customizable feature set and communication protocol.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If wireless remote control is used to control UAV, then ease of operation is improved, but communication latency and interference increase
Solution Approach 1:
The system is divided into two independent control paths: a wireless remote control path for basic operations and a wired direct connection path for advanced operations. This segmentation allows each path to be optimized independently, with the wired path eliminating communication latency while the wireless path maintains ease of operation for simple tasks.
Solution Approach 2:
The UAV's controller acts as an intermediary that receives commands from both the wireless remote control and the wired client device. The wired connection serves as a mediator that provides a low-latency communication channel, bypassing the limitations of wireless communication while maintaining system flexibility.
2Device complexity
If predefined command set is used in flight controller, then device complexity is reduced, but adaptability and extensibility deteriorate
Solution Approach 1:
The flight controller is designed with universal interfaces and a standardized command protocol that can accommodate both predefined commands and custom commands from external devices. This multi-functionality allows the same hardware to support simple predefined operations and complex custom operations without increasing device complexity.
Solution Approach 2:
The command set is made dynamic through the ability to load and execute custom commands from a wired client device. The system can adapt its command repertoire in real-time, transitioning from static predefined commands to dynamic custom commands based on operational needs, thereby improving adaptability without permanently increasing complexity.
3Device complexity
If fixed sensor configuration is implemented, then device complexity is reduced, but adaptability for new sensors deteriorates
Solution Approach 1:
The sensor interface is designed with universal communication protocols and standardized data handling mechanisms that can work with multiple sensor types. This allows the same hardware configuration to support various sensors (camera, GPS, accelerometer, etc.) without increasing complexity, as long as they adhere to the standardized interface.
Solution Approach 2:
The sensor configuration is made dynamic through software-based recognition and configuration. When a new sensor is connected via the wired interface, the system can dynamically detect, identify, and configure the sensor without requiring physical reconfiguration or increasing hardware complexity. This enables flexible sensor integration while maintaining a fixed hardware architecture.
Data Source
AI summary
Techniques are disclosed for communicating between a client device and an onboard data manager in a movable object environment. A data manager on a user device can identify an onboard data manager on a movable object. A feature list can be received from the onboard data manager, the feature list identifying at least one feature installed to the movable object. At least one input can be received by the user device, and a user device feature corresponding to the at least one input can be determined. It may be further determined that the user device feature is supported by the onboard data manager based on the feature list. In response to determining that the user device feature is supported, a first instruction corresponding to the at least one input can be sent to the movable object including the onboard data manager.