ek.Elisey Kochura
Selected work

Case study 02 / UAV / Embedded / R&D

UAV / Flight Systems

Connecting flight controllers, onboard Linux computers and sensors into a working flight system.

MY ROLE
R&D engineer
CONTEXT
Professional R&D · public overview
FOCUS
ArduPilot / Lua / Embedded Linux / Telemetry
FLIGHT SYSTEM / INTEGRATION

Overview

Hands-on UAV research and development at the intersection of electronics, flight control and onboard software. This public overview describes areas of work without disclosing employer-specific systems or project details.

Problem

A flight system depends on hardware and software working together. Flight controllers, sensors, onboard computers and telemetry links need to be integrated and verified as a complete system.

My role

My work covers UAV electronics integration, flight controller setup, ArduPilot, onboard Linux computers and preparation for ground and flight testing.

  • Sensor and electronics integration
  • Raspberry Pi / Orange Pi onboard computing
  • Lua scripting and telemetry
  • Ground and flight test preparation

Architecture

The conceptual building blocks are a flight controller, sensors, an onboard Linux computer and a telemetry interface. Specific hardware, interfaces, configurations and operating parameters are not part of this public portfolio.

Engineering decisions

The focus is on interfaces between subsystems and verification of the integrated system. Detailed design decisions remain within the relevant project documentation.

Problem
A public case study must explain cross-discipline integration without exposing employer-specific systems.
Decision
Describe subsystem responsibilities and test preparation with a conceptual diagram, omitting hardware configurations and operating parameters.
Reason
Readers can assess the engineering scope while confidential implementation stays within its project.
Trade-off
This public documentation decision limits independent reproduction and makes no claim about undisclosed flight performance.

Challenges

Integration requires reasoning across electronics, software and observable system behavior. Test preparation is part of the engineering work, alongside implementation.

Stack

ArduPilot, flight controllers, Lua, sensors, telemetry, Raspberry Pi, Orange Pi and embedded Linux.

ArduPilotLuaEmbedded LinuxTelemetry

Independent public examples

Separate from the professional R&D work above, the linked ArduPilot Lua repository contains three independently written demonstrations. Employer-specific source code, configurations and operational data are not published.

Validation covers 36 automated host tests with mocked ArduPilot bindings and firmware-write traps. GitHub CI runs Lua 5.3 and a separate stock Lua 5.3.5 build with 32-bit integers and floats. SITL, HIL, physical bench and flight testing have not been performed for these examples. They do not command real actuators or RC overrides; host tests do not establish flight readiness or safety certification.

  • Inertial event: AHRS acceleration reading, input validation, event qualification and hysteresis.
  • Guarded sequence: an explicit state machine with arming/mode guards, timeouts, cancellation and reset behavior.
  • Control lease: virtual resource ownership, rollback and retries after a failed release.

Result

Practical experience taking UAV subsystems through integration and test preparation. No confidential project outcomes or flight-performance figures are disclosed.

Code evidence

Timeout takes priority over a late event

The observation window is checked before accepting an event. An expired window cancels the sequence even if the same sample qualifies.

lua
        elseif self.state == "WATCHING" then
            -- An expired observation window takes priority over a late event.
            if runtime.elapsed(now, entered) >= config.wait_ms then
                transition("CANCELLED", now, "event window expired")
            else
                local _, fired = filter:step(now, sample.magnitude)
                if fired then transition("OBSERVING", now, "qualified event") end
            end

The Lua repository has 36 mocked host tests and two CI runtime configurations. This independent example performs no actuator commands; SITL, bench and flight validation remain unperformed.

View complete example on GitHub (opens in a new tab)
NEXT PROJECT

Lolpul Networking

Networking / Backend