LogoLogo
  • Welcome
  • Vehicle Operation
    • Getting started
    • Auterion Suite
      • Dashboard
      • Fleet Management
        • Vehicles
          • Cloud Features
          • Groups
        • Flights
        • Compliance
      • Manufacturer
        • Service Bulletins
      • Administration
      • User Management
      • Simulations
    • Auterion Mission Control
      • Installation
      • First steps
      • UI Breakdown
        • Navigating between the views
        • Fly View
          • Fly View UI Overview
          • Vehicle status indicator
          • Flight mode selector
          • Quick actions sidebar
          • Connection manager
          • Vehicle Dashboard
          • Flight Map
          • Camera View
          • Monitoring the Flight
          • Flying Manually (RC/Joystick)
          • Flying a Mission
        • Plan View
          • Plan UI Overview
          • Plan tools
            • Mission Menu
            • Waypoint Missions
            • Survey Patterns
              • Area Survey
              • Corridor Scan
          • Mission Summary
          • Mission Editor Tab
            • Start Section
            • Mission Section
            • End Section
            • Extras
          • Terrain visualization
          • GeoFence
          • Rally Points
        • Quick Vehicle Menu
          • Pre-Flight Checklist
          • Connectivity
        • Photo Gallery
        • Settings
        • Pilot Login
      • Useful resources
        • Mission Planning
          • Mission Cloud Sync
          • Terrain Following
          • Import Geo-Awareness data or KML overlays
        • Maps and Custom Overlays
          • Using Offline Maps
          • Importing GeoPDF overlays
        • Track GCS as Smart Asset in Suite
        • Live PX4 Log Streaming
        • Monitor Local Flights with ADS-B
        • GPS Denied Workflow
        • Windows Crash Logs Analysis
        • Screen Recordings
    • Remote Controllers
      • Skynav Remote Controller
        • Installing Mission Control
        • Joystick and Button Mapping
        • Using LTE for Online Maps in the Field
        • Advanced Radio Settings
        • Drop Guards and Chest Strap
        • Unit Serial Number
    • Settings & Maintenance
      • Vehicle Setup
      • WiFi Setup
      • Compass Calibration
      • Safety Setup
      • Joystick Setup
      • Vehicle Web UI
      • Software Update
      • Remote ID
        • How Remote ID works
        • Remote ID indicators in AMC
        • Frequently Asked Questions
    • Precise Flight
  • App development
    • Getting Started
      • Development environment Setup
      • Connecting to a device
      • Application Development
    • App Framework
      • Building your First App
      • Apps API
      • Sensor Data
      • Video Streams
      • Photos
      • Hardware Peripherals
      • Persistent Storage
      • MAVLink
      • Native Docker Compose
      • App Parameters
      • Log App Data to Auterion Suite
        • How to log Time Series Data
        • How to log basic Text Output
      • How to store an App's Binary Data on Skynode
      • User Web Interfaces
      • Build Arguments
      • Debugging apps with SSH
      • Debugging Apps with gdb
      • PX4 Messages in ROS 2
      • DDS / ROS2 Configuration
      • Structuring Applications with Multiple Services
    • Auterion SDK
      • Installation
      • Write Your First App
      • SDK API
      • Flight Mode API
        • Flight Mode API
        • Dynamics in Body Frame
        • Dynamics in Local Frame
        • Go-To in Local Frame
      • System State API
      • Peripheral Actuator Control API
      • Camera API
      • Navigation Input API
        • Global Navigation
        • Local Navigation
      • Visual Tracking API
    • Simulation
      • Virtual Skynode
        • Simulation-Gazebo Reference
        • Simulation-AirSim Reference
        • Connecting from other Computers
        • Resetting Virtual Skynode
        • Multiple Virtual Skynodes on single machine
      • Physical Skynode
    • Resources
      • Cross Compilation - Faster Builds
      • Auterion CLI Reference
      • Troubleshooting
      • App Tutorial
      • Skynode Vision Kit S
        • Set up the Vision Kit
        • Install and test a simple vision app
    • Legacy app workflow
      • App Development
      • MAVLink
      • Using the App Template
      • Example Applications
        • Autopilot Telemetry (C++)
        • Autopilot Telemetry (Python)
        • Photo Gallery
  • Hardware Integration
    • Getting started
      • Required Sensors
      • Wiring Skynode to the Vehicle
      • Actuators Setup
      • Sensors Setup
        • Set Orientations
        • Compass Calibration
        • Gyroscope calibration
        • Accelerometer calibration
        • Level horizon calibration
        • Airspeed calibration
      • Bench Test
      • Tuning
      • Creating Airframe Configurations for APX4
    • Skynode
      • Skynode X
      • Skynode ENT/GOV
      • Skynode X Integration and Development Kit
        • Get Skynode ready
        • Power Skynode
        • Register Skynode
        • Connect Skynode to AMC
        • Sensors and Peripherals
        • Next steps
      • Payloads
        • Generic USB Webcams (UVC)
        • Workswell Wiris Pro
        • Trillium HD40-LV
        • NextVision Gimbals (with TRIP2)
        • Sony Alpha a7R IV
        • Phase One iXM-100
        • Gremsy Gimbals
      • Connectivity
        • USB-C Network Connection
        • WiFi
        • LTE Setup
        • SIYI MK15
        • Microhard Data Link
        • Data Link Wiring
        • Silvus Data Link
        • Doodle Labs Data Link
        • Custom Data Link
        • Ethernet Interface Configuration
      • Skynode LED Meanings
      • Troubleshooting
      • Legacy DSM/DSMX Support
      • Peripherals
        • Power Module
        • 12S Power Module
        • Pixhawk Adapter Board
        • Pixhawk Payload Bus
        • Data Link Module
        • PX4 F9P GPS
        • Freefly RTK GPS
        • Airspeed Sensor
        • LIDAR
        • USB camera
        • See3CAM_24CUG
    • Skynode S
      • Datasheet
      • Interfaces
      • Basic Vehicle Integration
      • Add LTE to Skynode S
      • Skynode S LED status indicator
      • Skynode S flight logs
    • AI Node
      • Datasheet
      • Evaluation Kit
        • Power AI Node
        • Wiring AI Node to Skynode
        • Internet sharing with Skynode
        • Activate AI Node on Suite
      • Dimensions and CAD model
      • Interfaces
      • Connectivity
        • USB Network Connection
        • Serial Debug Connection
        • AI Node as Network Bridge
        • Standalone Internet Access
      • Updating AuterionOS
    • Advanced Airframe Integration
      • Custom power setup
      • Wiring without Breakout Boards
      • Gripper Integration
        • Setting up Payload Delivery with Gripper
      • ESC Calibration
      • Camera Calibration
        • Camera Calibration on a Computer
        • Camera Calibration on Skynode
      • Serial Port Configuration
    • Flight controller customization
      • AMC's Advanced Mode
      • Flight Controller Shell
      • Micro XRCE-DDS
    • AuterionOS Customization
      • OEM Tools Installation
      • Adding SSH keys
      • Changing the Root Password
      • Modifying Environment Variables
      • Pre-install Applications
      • Suite Manufacturer Tools
    • AuterionOS System Guide
      • Introduction
      • Flashing PX4 Binary and Vehicle Config
      • Building and Flashing PX4 Firmware
      • SSH Access
      • Filesystem and partitions
      • Environment Variables Reference
      • Types of AuterionOS Images
      • Mavlink Routing and Endpoints
      • Packaging AuterionOS Image
    • Additional Resources
      • Remote ID
        • How Remote ID works
        • Vehicle Serial Number
        • Communication Diagram
        • Remote ID configuration
        • How Auterion tested
      • Auto-Tuning
  • Release Notes
    • APX4
      • APX4 3.2
        • APX4 3.2.10
        • APX4 3.2.1
      • APX4 3.1
        • APX4 3.1.1
        • APX4 3.1.0
      • APX4 3.0
        • APX4 3.0.8
        • APX4 3.0.5
      • APX4 2.7
        • APX4 2.7.37
        • APX4 2.7.25
        • APX4 2.7.20
        • APX4 2.7.12
        • APX4 2.7.7
        • APX4 2.7.6
      • APX4 2.6
        • APX4 2.6.1
      • APX4 2.5
        • APX4 2.5.14
        • APX4 2.5.13
        • APX4 2.5.8
        • APX4 2.5.7
        • APX4 2.5.5
        • APX4 2.5.4
        • APX4 2.5.0
      • APX4 2.4
        • APX4 2.4.2
        • APX4 2.4.1
      • APX4 2.3
        • APX4 2.3.0
      • APX4 2.2
        • APX4 2.2.2
        • APX4 2.2.0
      • APX4 2.1
        • APX4 2.1.1
        • APX4 2.1.0
      • APX4 2.0
        • APX4 2.0.2
        • APX4 2.0.0
    • AuterionOS
      • AOS for AI Node
        • AI Node AOS 1.1.0
        • AI Node AOS 1.0.2
        • AI Node AOS 1.0.0
        • AI Node AOS 0.7.0
        • AI Node AOS 0.6.1
        • AI Node AOS 0.6.0
        • AI Node AOS 0.5.0
        • AI Node AOS 0.4.0
      • AOS for Skynode
        • AOS 3.7
          • AOS 3.7.25
          • AOS 3.7.9
        • AOS 3.6
          • AOS 3.6.14
        • AOS 3.5
          • AOS 3.5.13
        • AOS 3.3
          • AOS 3.3.9
        • AOS 3.2
          • AOS 3.2.9
        • AOS 2.19
          • AOS 2.19.14
        • AOS 2.15
          • AOS 2.15.10
          • AOS 2.15.7
        • AOS 2.12
          • AOS 2.12.8
        • AOS 2.10
          • AOS 2.10.2
        • AOS 2.8
          • AOS 2.8.1
        • AOS 2.7
          • AOS 2.7.15
        • AOS 2.6
          • AOS 2.6.1
        • AOS 2.5
          • AOS 2.5.14
          • AOS 2.5.13
          • AOS 2.5.8
          • AOS 2.5.7
          • AOS 2.5.5
          • AOS 2.5.4
          • AOS 2.5.0
        • AOS 2.4
          • AOS 2.4.1
        • AOS 2.3
          • AOS 2.3.0
        • AOS 2.2
          • AOS 2.2.2
          • AOS 2.2.0
        • AOS 2.1
          • AOS 2.1.1
          • AOS 2.1.0
        • AOS 2.0
          • AOS 2.0.2
          • AOS 2.0.0
    • Auterion Mission Control
      • AMC 1.34
        • AMC 1.34.21
        • AMC 1.34.14
      • AMC 1.33
        • AMC 1.33.13
      • AMC 1.32
        • AMC 1.32.7
      • AMC 1.30
        • AMC 1.30.17
      • AMC 1.29
        • AMC 1.29.7
      • AMC 1.26
        • AMC 1.26.8
      • AMC 1.22
        • AMC 1.22.3
      • AMC 1.19
        • AMC 1.19.5
      • AMC 1.18
        • AMC 1.18.3-1
        • AMC 1.18.3
      • AMC 1.17
        • AMC 1.17.10
        • AMC 1.17.9
      • AMC 1.15
        • AMC 1.15.0
      • AMC 1.14
        • AMC 1.14.6
        • AMC 1.14.0
      • AMC 1.13
      • AMC 1.12
      • AMC 1.11
      • AMC 1.10
        • AMC 1.10.1
        • AMC 1.10.0
      • AMC 1.9
        • AMC 1.9.1
        • AMC 1.9.0
      • AMC 1.8
    • Hardware
      • Skynode Rev 11 (Jan 2022)
Powered by GitBook
On this page
  • Create a Structure Scan Mission
  • To create a structure scan mission:
  • Structure Scan Editor (Settings)
  • Camera Tab
  • Grid Tab
  1. Vehicle Operation
  2. Auterion Mission Control
  3. UI Breakdown
  4. Plan View
  5. Plan tools
  6. Survey Patterns

Structure Scan

Last updated 1 year ago

A Structure Scan mission is used for the visual inspection of buildings or creating 3-dimensional models of structures. It defines a layered grid flight pattern that captures images over vertical surfaces (e.g. walls) around a structure with an arbitrary polygonal (or circular) ground footprint.

The image above shows a structure scan. The green inner-polygon marks out the ground footprint of the structure, while the white line around it indicates the vehicle flight path. The green numbered circle on the flight path is the scan entry/exit point (where the scan starts).

The scan divides the structure evenly into layers; the vehicle flies all the way around the structure at a particular altitude and scan distance, then repeats the process at each layer until the whole surface has been scanned.

Users can set the scan bottom altitude to avoid obstacles at the bottom of the structure, and the entrance/exit altitude to avoid obstacles as the vehicle travels to/from the scan.

This topic shows how to create a structure scan mission and the various settings that can be configured in the Structure Scan Editor.

Create a Structure Scan Mission

The easiest way to define a structure scan mission is to use the Plan view > Pattern** > Structure Scan** tool.

This creates a template for a simple end end-to-end structure scan mission for the current vehicle type. Often all the user has to do is define the scan area (any items that require configuration are shown with a red border in the mission item list).

If a more complex mission is needed, the basic mission can be extended by adding other items before the return item.

To create a structure scan mission:

  1. Open the Plan View and select the Pattern > Structure scan button. This creates a basic structure scan mission appropriate for the current vehicle type (clearing any existing mission).\

  2. From the Mission editor, select the Mission to edit the Structure scan settings.\

  3. Choose your survey area:

  • Basic: Create a polygon footprint starting from a rectangle. The filled circles (vertices) and center can be moved where needed (using the map). New vertices can be created by selecting the markers between existing vertices, and then moved.Move and create vertices as needed so that the green area overlays the edges of the structure to be scanned.

  • Circular: Create a circular footprint. The filled circles in the center and on the circumference can be moved on the map to change the circle's position and size. Center the scan on a circular structure and then adjust the radius until the green area overlays the edges of the structure.

  • Trace: Trace around the shape of the target scan footprint. The filled circles can be moved on the map while tracing (you cannot move the center point or create new vertices). Select the Done Tracing button to stop tracing and display the Polygon Tools.

Note that the Structure Scan editor has a red border. This indicates that the item is undefined and must be explicitly set before saving the mission.

Structure Scan Editor (Settings)

The mission Structure Scan Editor is used to configure Camera and Grid settings. The trash/bin icon can be used to delete the whole item

Set the camera first, before configuring the grid (camera capabilities affects the grid settings).

Camera Tab

Users can select a predefined camera, custom camera, or "manual camera". The main difference is that using a predefined camera allows Auterion Mission Control to calculate an optimal layer height for a trigger distance, and visa versa while using a manual camera means that these parameters need to be manually calculated (and are therefore harder to change).

Grid Tab

The Grid tab is used to set the properties of the scan.

The screenshot below shows the properties when using a predefined or custom camera.

The scan settings allow users to choose a desired image overlap and set either desired scan distance or image resolution for the structure surface (automatically calculating the other value).

Setting
Description

Overlap

Overlap between each image capture.

  • Front Lap is image overlap from top to bottom (increasing shrinks layer height and increases layer count).

  • Side Lap is image overlap at sides (increasing takes more images in each lap/layer scan)

Scan Distance

Distance of vehicle from structure during scan (affects Ground Res).

Ground Res

Ground resolution for each image (affects Scan Distance).

For a manual camera, the grid settings are instead specified as shown. Note that if any of these settings need to change, then they may all need to be manually recalculated.

Setting
Description

Scan Distance

Distance from vehicle to structure during scan.

Layer Height

The height of each layer.

Trigger Distance

Horizontal distance over ground between each camera shot.

Note that the camera is only triggered while flying the layer path. It does not trigger images while transitioning from one layer to the next.

Scan Panel

The Scan section configures the order in which layers are captured, gimbal pitch, and other settings that ensure a clear flight path before, during, and after the scan.

Setting
Description

Start Scan From Top/Bottom

The direction in which layers are scanned (top to bottom, or bottom to top).

Structure Height

The height of the object being scanned.

Scan Bottom Alt

This setting is used to avoid obstacles around the base of the structure. It adjusts the bottom of the structure to be above the ground, and hence the altitude of the first scan (the height of the lowest layer flight path is shown in the scan statistics as Bottom Layer Alt).

Entrance/Exit Alt

The vehicle will fly from the last waypoint to the Entrance/Exit point at this altitude and then descend to the initial layer to start the scan. The vehicle will ascend to this altitude after completing the scan and then move to the next waypoint. The setting is used to avoid obstacles between the structure to be scanned and the preceding/following waypoints.

Gimbal Pitch

Gimbal pitch for the scan.

Rotate entry point

Toggle the start/finish point to the next vertix/position on the flight path.

Statistics Panel

The Statistics panel summarizes the calculated scan information: number of layers, layer height, top and bottom layer altitudes, photo count, photo interval, and resolution.

Check that the item settings are correct for the planned scan. In particular that the altitude (Waypoint altitude) is high enough to avoid obstacles when travelling to the structure.

Select the Done with Tracing button when the scan footprint is defined. This will allow other properties of the survey to be edited in the .

The camera settings are exactly the same as for surveys (and for Corridor Scans). For more information see: .

Structure Scan Editor
Structure Scan Camera Settings: Custom Camera
Structure Scan Grid Settings: Predefined/Custom Camera
Mission Start
Survey > Camera