Abstract: Techniques are disclosed for performing custom waypoint missions using an onboard computing device in communication with a movable object. The movable object can include a flight controller, and a communication system. The flight controller can be in communication with the onboard computing device which includes a processor and an onboard data manager. The onboard data manager can receive at least one input, determine one or more instructions to be performed by the at least one movable object based on the at least one input, generate movement commands to implement the one or more instructions, and send movement commands to the flight controller to be executed.

Abstract: 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.

Abstract: A method of tracking performance of a movable object includes creating a process log for a movable object manager of the movable object, the movable object manager operating in a software environment; creating a movement record of the movable object from two or more sensors including two or more of a global positioning system (GPS) sensor, a motion sensor, an inertial measurement unit (IMU), a proximity sensor, an image sensor, an attitude and heading reference system (AHRS), a radar sensor, a lidar sensor, an ultrasound sensor, and an infrared sensor; and transmitting at least one of the process log or the movement record to a movable object monitoring station.

Abstract: Techniques are disclosed for real-time mapping in a movable object environment. A real-time mapping system can include at least one movable object including a computing device, a scanning sensor electronically coupled to the computing device, and a positioning sensor electronically coupled to the computing device. The computing device can include at least one processor and a mapping manager, the mapping manager may be configured to obtain mapping data from the scanning sensor and obtain positioning data from the positioning sensor. The mapping manager can associate the mapping data with the positioning data based at least on time data associated with the mapping data and the positioning data, and then generate a map in a first coordinate system based at least on the associated mapping data and positioning data.

Abstract: A system for tracking and analyzing performance of a movable object and methods of making and using the same. Movable object performance can be tracked by creating a process log for a movable object manager of the movable object, and creating a movement record of the movable object for comparison to the process log. The process log can include, for example, records of application call processes to a movable object interface, protocol call processes transmitted to and from the movable object, and/or metadata. A movable object event can be analyzed by correlating the process log with the movement record. The present systems and methods are particularly suitable for tracking and analysis of unmanned aerial vehicles (UAV).

Abstract: Techniques are disclosed for user interface management in a movable object environment. A user interface manager can request sensor data associated with a movable object from a data manager. The user interface manager can provide the sensor data to one or more user interface elements associated with the user interface element. A first rendering of the at least one user interface element can be caused to be displayed in a user interface, the first rendering determined based on a type or amount of the sensor data associated with the movable object.

Abstract: Techniques are disclosed for performing custom waypoint missions using an onboard computing device in communication with a movable object. The movable object can include a flight controller, and a communication system. The flight controller can be in communication with the onboard computing device which includes a processor and an onboard data manager The onboard data manager can receive at least one input, determine one or more instructions to be performed by the at least one movable object based on the at least one input, generate movement commands to implement the one or more instructions, and send movement commands to the flight controller to be executed.

Abstract: Techniques are disclosed for user interface management in a movable object environment. A user interface manager can request sensor data associated with a movable object from a data manager. The user interface manager can provide the sensor data to one or more user interface elements associated with the user interface element. A first rendering of the at least one user interface element can be caused to be displayed in a user interface, the first rendering determined based on a type or amount of the sensor data associated with the movable object.

Abstract: Techniques are disclosed for performing custom waypoint missions using an onboard computing device in communication with a movable object. The movable object can include a flight controller, and a communication system. The flight controller can be in communication with the onboard computing device which includes a processor and an onboard data manager. The onboard data manager can receive at least one input, determine one or more instructions to be performed by the at least one movable object based on the at least one input, generate movement commands to implement the one or more instructions, and send movement commands to the flight controller to be executed.

Abstract: A method for managing communication with a movable object includes receiving a request for movable object data from a requester in a movable object environment. The request includes a movable object data key that has data fields configured to identify a movable object component that corresponds to the movable object data. The method further includes determining whether movable object data corresponding to the request is available in a cache by determining whether the movable object data corresponding to the movable object data key exists in the cache and, in response to determining that the movable object data is available in the cache, providing the movable object data in the cache to the requester.

Abstract: Techniques are disclosed for inspection management in a movable object environment. An inspection application can receive data from an inspection application and use this data to generate one or more inspection missions. When a user selects an inspection mission in the inspection application, the inspection application can instruct a movable object to perform the selected inspection mission. The movable object can follow one or more dynamically generated paths around a target object and capture a plurality of images. The images can be viewed in a viewing application to perform an inspection of the target object.

Abstract: A system for managing communication with a movable object includes one or more processors configured to receive a request for movable object data from a requester in a movable object environment, determine whether movable object data corresponding to the request is available in a cache associated with a movable object manager, and, in response to determining that the movable object data is available in the cache, provide the movable object data in the cache to the requester.

Abstract: Techniques are disclosed for inspection management in a movable object environment. An inspection application can receive data from an inspection application and use this data to generate one or more inspection missions. When a user selects an inspection mission in the inspection application, the inspection application can instruct a movable object to perform the selected inspection mission. The movable object can follow one or more dynamically generated paths around a target object and capture a plurality of images. The images can be viewed in a viewing application to perform an inspection of the target object.

Abstract: 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.

Abstract: Techniques are disclosed for performing custom waypoint missions using an onboard computing device in communication with a movable object. The movable object can include a flight controller, and a communication system. The flight controller can be in communication with the onboard computing device which includes a processor and an onboard data manager. The onboard data manager can receive at least one input, determine one or more instructions to be performed by the at least one movable object based on the at least one input, generate movement commands to implement the one or more instructions, and send movement commands to the flight controller to be executed.

Abstract: A system for managing communication with a movable object includes one or more processors configured to receive a request for movable object data from a requester in a movable object environment, determine whether movable object data corresponding to the request is available in a cache associated with a movable object manager, and, in response to determining that the movable object data is available in the cache, provide the movable object data in the cache to the requester.

Abstract: A system for tracking and analyzing performance of a movable object and methods of making and using the same. Movable object performance can be tracked by creating a process log for a movable object manager of the movable object, and creating a movement record of the movable object for comparison to the process log. The process log can include, for example, records of application call processes to a movable object interface, protocol call processes transmitted to and from the movable object, and/or metadata. A movable object event can be analyzed by correlating the process log with the movement record. The present systems and methods are particularly suitable for tracking and analysis of unmanned aerial vehicles (UAV).

Abstract: Techniques are disclosed for inspection management in a movable object environment. An inspection application can receive data from an inspection application and use this data to generate one or more inspection missions. When a user selects an inspection mission in the inspection application, the inspection application can instruct a movable object to perform the selected inspection mission. The movable object can follow one or more dynamically generated paths around a target object and capture a plurality of images. The images can be viewed in a viewing application to perform an inspection of the target object.

Abstract: Techniques are disclosed for user interface management in a movable object environment. A user interface manager can request sensor data associated with a movable object from a data manager. The user interface manager can provide the sensor data to one or more user interface elements associated with the user interface element. A first rendering of the at least one user interface element can be caused to be displayed in a user interface, the first rendering determined based on a type or amount of the sensor data associated with the movable object.