Document Number: OAS-GD-2026-001
Version: 1.2
Effective Date: July 1, 2026
Status: Active
Owner: Octocore Autonomous Systems, LLC
Applies To: Octocore technical, proposal, architecture, and customer-facing documentation

Purpose

This guidance establishes Octocore Autonomous Systems terminology for autopilot-capable vehicle control hardware when such hardware is used across multiple vehicle domains.

The immediate issue is that controllers from vendors such as CubePilot, Holybro, SpeedyBee, and similar ArduPilot/PX4-compatible hardware families are commonly called flight controllers when installed in aircraft. That term is appropriate for aircraft but becomes inaccurate when the same general class of device is installed in a ground vehicle, surface vessel, or underwater vehicle.

Octocore will use domain-neutral terminology when referring to the general hardware class and domain-specific terminology when referring to a particular vehicle application. Vendor names may be used as examples or bill-of-materials references, but they should not define the terminology.

Scope

This guidance applies to autopilot-capable vehicle control hardware regardless of vendor, firmware, or form factor. Examples include CubePilot, Holybro Pixhawk-family controllers, SpeedyBee controllers, and other compatible control boards when used as part of an autonomous or semi-autonomous vehicle control stack.

CubePilot hardware may be preferred for some higher-assurance integrations, but Octocore terminology must not imply that CubePilot is the only supported controller family or the only valid implementation path.

Preferred Umbrella Term

The preferred generic umbrella term is:

vehicle motion controller with autopilot

This term describes a device or embedded control computer that can command vehicle motion, close control loops, execute navigation behaviors, and support autopilot functions without implying that the vehicle operates in air.

Acceptable shorter forms are:

  • vehicle motion controller
  • vehicle controller with autopilot
  • vehicle control computer
  • autopilot controller, when speaking within ArduPilot/PX4 or similar ecosystems

For formal Octocore architecture and proposal language, use vehicle motion controller with autopilot on first reference and vehicle motion controller thereafter unless the autopilot function is specifically relevant.

Boundary Note

A vehicle motion controller is not the same as a low-level motor controller, electronic speed controller (ESC), servo controller, actuator controller, or actuator driver.

Those lower-level devices may execute commands from the vehicle motion controller, but they do not by themselves provide the vehicle-level guidance, navigation, control, autopilot, or motion-management role described in this guidance.

Domain-Specific Terms

Use the following terms when the vehicle domain is known:

Vehicle domain Preferred term Acceptable short form
Aircraft flight controller with autopilot flight controller
Ground vehicle ground vehicle controller with autopilot ground vehicle controller
Surface vessel surface vessel controller with autopilot surface vessel controller
Underwater vehicle underwater vehicle controller with autopilot underwater vehicle controller

When the vehicle is a recognized unmanned vehicle class, the following terms are also acceptable:

  • UAV controller with autopilot for unmanned aircraft
  • UGV controller with autopilot for unmanned ground vehicles
  • USV controller with autopilot for unmanned surface vessels
  • AUV controller with autopilot for autonomous underwater vehicles

These acronyms are useful in technical contexts but should be expanded on first use in customer-facing documents.

Usage Rule

Do not use flight controller as a generic term for autopilot-capable vehicle control hardware when the controlled vehicle is not an aircraft.

Correct:

  • The selected controller functions as a vehicle motion controller with autopilot.
  • In the aircraft configuration, the controller is the flight controller with autopilot.
  • In the ground configuration, the controller is the ground vehicle controller with autopilot.
  • In the maritime surface configuration, the controller is the surface vessel controller with autopilot.
  • In the underwater configuration, the controller is the underwater vehicle controller with autopilot.
  • A CubePilot, Holybro, or SpeedyBee controller may be used as the vehicle motion controller when it meets the integration requirements for the vehicle and mission.

Incorrect:

  • The submarine uses a flight controller.
  • The rover uses a flight controller.
  • The surface vessel uses a flight controller.

Relationship to GNC Terminology

In aerospace and defense contexts, GNC means guidance, navigation, and control. The term GNC computer or GNC controller may be used when the emphasis is on the system function rather than the hardware role.

Octocore may use GNC computer in formal systems engineering documents, interface control documents, architecture descriptions, and defense customer material. However, vehicle motion controller with autopilot remains the preferred plain-language umbrella term because it is understandable across aviation, robotics, maritime, and customer-facing contexts.

Recommended distinction:

  • vehicle motion controller with autopilot: the hardware/software role in a vehicle
  • GNC computer: the guidance, navigation, and control system function
  • mission computer: a higher-level compute node that may host autonomy, perception, decision support, payload control, or mission-management software

A mission computer may command or supervise a vehicle motion controller, but the terms should not be treated as synonyms.

Standard Taxonomy

Octocore will use the following taxonomy:

Vehicle motion controller with autopilot
├── Flight controller with autopilot
├── Ground vehicle controller with autopilot
├── Surface vessel controller with autopilot
└── Underwater vehicle controller with autopilot

The taxonomy is based on the controlled vehicle domain, not the vendor, airframe, firmware, or physical device family.

Rationale

This convention prevents aviation-specific language from leaking into non-aviation systems while preserving familiar usage where it is technically correct.

It also supports Octocore’s broader systems architecture language. A controller is not inherently a flight controller simply because its vendor, firmware ecosystem, or market category originated in aviation or drones. It becomes a flight controller when installed in and configured for an aircraft. Comparable hardware may become a ground vehicle controller, surface vessel controller, or underwater vehicle controller when installed in those domains.

This distinction is commercially important as well as technically important. Octocore may choose CubePilot hardware for demanding integrations, but the guidance must preserve vendor flexibility and avoid implying that Octocore supports only one controller family.

The guidance also reduces ambiguity in proposals, technical diagrams, safety analysis, and customer conversations. The controlled vehicle domain should be clear from the noun.

Implementation Guidance

When writing Octocore material:

  1. Use vehicle motion controller with autopilot when discussing the general hardware/software class.
  2. Use the domain-specific term once the vehicle type is known.
  3. Use flight controller only for aircraft.
  4. Use GNC computer when writing for formal aerospace or defense systems engineering audiences.
  5. Use mission computer only for higher-level mission, autonomy, payload, or supervisory compute roles.

Revision History

Version Date Notes
1.0 July 1, 2026 Initial Octocore terminology guidance.
1.1 July 1, 2026 Revised wording to make the guidance vendor-neutral while retaining CubePilot as an example controller family.
1.2 July 1, 2026 Added boundary note distinguishing vehicle motion controllers from low-level motor, ESC, servo, and actuator controllers.