AVEONI
Current Product: Aveoni Studio Aveoni Studio

Connect flight controllers and companion computers in one project

Studio is the part of the platform with verified capability today. Connect to Betaflight flight controllers over USB and read their device identity, connect a companion computer on the local network, install modules on it, and deploy a CPU model to a Raspberry Pi 5 companion with read-back.

What you can do today

Available

Connect to Betaflight and read device identity over USB

Configuration writes are not hardware-verified.

Available

Connect a companion

Raspberry Pi 5 or NVIDIA Jetson Orin Nano. The Pi 5 session is recorded over a direct Ethernet link, dated 2026-09-16.

Available

Install, start and stop modules

On the reference companion. A started module is not a health check.

Available

Deploy a CPU model and read it back

Raspberry Pi 5 reference companion. Deployed means installed and read back as sent. It does not mean running.

Limited

ArduCopter 4.6.2 over USB

One reference board. Connection and identity read. ArduPlane is not claimed. ArduPilot through a companion is not supported, and Studio refuses it by name.

Available

Discover UVC cameras

Through the companion, on the Raspberry Pi 5 bench. Discovery only; video is not part of this.

Engineering Evidence

Two kinds of proof, so you know exactly what works

For every capability we answer two questions separately. Has it run on real hardware? And can you reach it in Studio today? Only a dated run on a named board counts as hardware proof, so nothing here is promised beyond what has actually been shown. Neither answer on its own means production-ready.

Hardware verified

A dated physical run on named hardware is recorded. Code alone never counts. One run on one board is evidence for that board and that run only.

Studio accessible

A user can reach the capability in the Studio interface. Reachable does not mean verified on hardware.

Reachable in Studio

A user can reach the capability in Studio. A test run does not count.

Software verified

Automated tests cover the behaviour. Fakes are not hardware evidence.

Physically verified

A dated run on named hardware is recorded.

Production UI accessible

A user can reach it in the released Studio. An automated test run does not count.

CapabilityPhysically verifiedProduction UI accessibleStatus
Connect to Betaflight and read device identity over USBYes Tykho Lit S4, Betaflight 4.5.1. Connect and identity read on one Lit S4, 2026-10-07, 37 of 37 checks. This run wrote no configuration.Yes Device workspaceAvailable
ArduCopter 4.6.2 over USBYes One Tykho Lit S4 only. ArduCopter 4.6.2, run of 2026-09-28. ArduPlane is not claimed as physically verified.Yes Devices flowLimited
Read Betaflight identity through a companionYes Betaflight only. Read-only identity through the companion broker: Tykho Lit S4 through a Raspberry Pi 5 (recorded 2026-09-18). Configuration through a companion is not verified.Partly The route can be chosen in Studio. Use through the production interface is not separately verified.Limited
Raspberry Pi 5 companionYes Raspberry Pi 5 (aarch64), connection and compute discovery, reached over a direct Ethernet link. Session record dated 2026-09-16. Local-network discovery is not shown in that record.YesAvailable
NVIDIA Jetson Orin Nano companionYes NVIDIA Jetson Orin Nano. Connection and stack only (recorded 2026-09-18).YesAvailable
Companion Module RuntimeYes Raspberry Pi 5 reference companion: install, start and stop. Starting a module is not a health check. The record is undated.YesAvailable
CPU model deploy and read-backYes One Raspberry Pi 5 reference companion: transfer, validation, install and read-back. The hardware record is undated.Yes AI models pageAvailable
UVC camera discoveryYes Raspberry Pi 5 bench, discovery only. One UVC camera reported by the companion, in a run artifact dated 2026-10-08. Video is not part of this record.YesAvailable
Running inference on the deviceNo Test suites ran on a Raspberry Pi 5. No inference on a deployed model is recorded.NoPlanned
Engineering Evidence

See it work on real boards

Every claim on this page traces back to a recorded run on real hardware. Each record tells you which board was on the bench, when it ran, what Studio did and exactly where the run stopped, so your team can judge the fit for its own hardware before a single meeting. Each record is one run on one board, not a claim of production readiness.

Engineering evidence (this page)

Specific runs on named hardware, with their limits.

Platform vision

The complete intended architecture, with the maturity of each part. See the status of every platform layer.

Recorded 2026-10-07

Connect & Read

A direct USB connection to a flight controller, with its identity read and the connection cycled.

Hardware
Tykho Lit S4 reference board, Betaflight 4.5.1, MSP API 1.46. Direct USB, no companion.
Record
Hardware run, 2026-10-07, 37 of 37 checks passed.
What it showed
Connected over USB. Read the board's identity and unique chip ID over MSP. Disconnected and reconnected.
Limits
Betaflight only. The unique chip ID read is verified on Betaflight only. It is not verified on ArduPilot. The stored project was unchanged by the hardware part of the run.

Where this record stops. Configuration is not part of this record.

Recorded 2026-09-25

Companion route

Studio opened a session to a Betaflight flight controller through a Raspberry Pi 5 companion on the local network, with the route derived from the system topology.

Hardware
Tykho Lit S4 reference board, Betaflight 4.5.1, MSP API 1.46. Raspberry Pi 5 companion aveoni-cc-fb7355.
Record
Acceptance run, 2026-09-25, 27 of 27 checks passed.
What it showed
The route was derived with no manual choice. The board identity was read through the companion, read-only: BTFL, 4.5.1, API 1.46, TYKHOTLS4V1.
Limits
One board, Betaflight only. ArduPilot through a companion is refused by name. Direct USB remains the primary path.

Where this record stops. No configuration write is included.

Recorded 2026-10-08

Companion route on NVIDIA Jetson

The same kind of flight controller, now reached through an NVIDIA Jetson Orin Nano companion, with the route derived from the declared wire.

Hardware
Tykho Lit S4 reference board, Betaflight 4.5.1, MSP API 1.46. NVIDIA Jetson Orin Nano companion aveoni-cc-d5e38f.
Record
Hardware run, 2026-10-08, 34 of 34 checks passed.
What it showed
The route was derived with no manual choice, and the board identity was read through the Jetson on two sessions. The first attempt hit a defect on the companion side; Studio named the refusal instead of failing silently, the defect was fixed and the run repeated.
Limits
One board, Betaflight only. No model ran on the Jetson in this run.

Where this record stops. No configuration write is included.

Recorded 2026-09-28

ArduPilot over USB

A direct USB connection to a flight controller running ArduCopter, recognised from the board itself.

Hardware
Tykho Lit S4 reference board, ArduCopter 4.6.2 over MAVLink v2. Direct USB; a Raspberry Pi 5 companion was connected and deliberately not used.
Record
Hardware run, 2026-09-28, 6 of 6 and 28 of 28 checks passed across its two scenarios.
What it showed
Connected over USB, recognised ArduCopter from the board and read its unit identity.
Limits
One board. ArduPlane is not claimed. ArduPilot through a companion is not supported.

Where this record stops. Configuration is not part of this record.

Recorded 2026-10-08

Two devices, one project

A Betaflight flight controller over USB and a live NVIDIA Jetson Orin Nano companion in the same project, each reported on its own.

Hardware
Tykho Lit S4 reference board, Betaflight 4.5.1, MSP API 1.46, direct USB. NVIDIA Jetson Orin Nano companion, online throughout.
Record
Hardware run, 2026-10-08, 51 of 51 checks passed.
What it showed
The board identity was read and read again after a reconnect. The companion stayed online before, during and after, and reported NVIDIA compute (CUDA 12.6, TensorRT 10.3), read live in the run.
Limits
Reported compute is detection, not model execution. TensorRT execution is not verified.

Where this record stops. No model ran on the Jetson in this record.

Recorded 2026-09-28

A refusal you can trust

Asked to reach an ArduPilot board through a companion, a route Studio does not support, Studio refused it by name and never touched the board.

Hardware
Tykho Lit S4 reference board with ArduCopter. Raspberry Pi 5 companion aveoni-cc-fb7355, live and offered as a route.
Record
Hardware run, 2026-09-28, 22 of 22 checks passed.
What it showed
A named refusal, not a generic connection error. No port was requested or opened, nothing was sent to the companion, and the saved project was byte-identical before and after.
Limits
It proves the refusal. ArduPilot through a companion is not supported.

Where this record stops. This record shows what Studio will not do.

From an empty project to a mapped drone, in four steps

Create a project, add the flight controller and companion from the library, inspect each device and draw how they connect. Studio keeps an honest picture as you go: every device reads NOT CHECKED or NOT CONNECTED until real hardware answers, as in these screenshots, taken with nothing plugged in.

Studio screenshot 1: creating a project, with no hardware connected
1. Create a project
Studio screenshot 2: adding components, with no hardware connected
2. Add components
Studio screenshot 3: inspecting each device, with no hardware connected
3. Inspect each device
Studio screenshot 4: connecting the parts, with no hardware connected
4. Connect the parts

What comes next

Studio today is the foundation. These are the next capabilities on the roadmap, and none of them is available yet. If one of them matters to your product, an Engineering Pilot is where we can discuss it.

  • On-device AI. Running models on the companion, next to the camera. Not yet available.
  • Live video. Camera video in the browser, and camera frames reaching a model. Planned.
  • Developer platform. The public SDK, accounts and fleet tools. Planned.
  • Drone Kits. Development airframes built for the platform. In development.
  • Motor testing and firmware flashing. Not yet published or run on hardware, and they will come with safety warnings.
  • Not supported today: ArduPilot through a companion. ArduPilot connects directly over USB.
Explore an Engineering PilotDeveloper AccessSee the full platform
Developer Access

Developer Access: Studio on your own bench

Developer Access is planned for developers and R&D teams who want to try Studio hands-on: build a project, connect the reference boards and see every device report exactly what it is.

  • What you will work with. A Betaflight or ArduPilot flight controller over USB, a Raspberry Pi 5 or NVIDIA Jetson Orin Nano companion, and model deployment to the companion, on the reference boards.
  • Where it stands. Access is not open yet, and no registration or onboarding is running. The access terms and the request route are still being confirmed.
  • Until then. The verified scope on this page shows exactly what Studio does today.