Development journal

Dated notes from the workbench. Each entry says what was checked at the time and what still needed work. Older entries are kept as they were, with corrections marked.

Horizon is the focus, and we are looking for testers.

The website now centres on Horizon. A new interface for Horizon’s flight screens is being designed; so far it has been checked in software only and has not yet run on Horizon hardware or in flight.

Pilots can now apply to test development units. Ground testing comes first; flights follow only when the ground checks allow it, always with an independent backup instrument.

Status summary and a new website

The site now separates what works today from what is being built and what comes later. In short: the Core prototype works; Horizon engineering boards run the display and talk to the XC module over a wired link; VIRON Air connects on Android and iPhone in testing.

Being built: Horizon firmware and screens, flight review and route planning in VIRON Air, and true airspeed measurement, which is technology under development and is not validated or available. ADS-L support is a future item.

Core works. VIRON Air connects on both phone platforms.

Core is working; its own circuit board is not designed yet. Horizon and VIRON Air are under active development.

Reported checks on Android and iPhone cover Bluetooth connection, live data, voice and manual reconnect. The shared permission test set passed 159 tests.

These checks do not cover complete outdoor use, background behaviour or release readiness.

The Horizon appearance is chosen.

The exterior is now the selected look for both Horizon and Horizon XC: a 3.5-inch portrait display, four physical side buttons and one compact visual identity.

This describes the appearance. Internal packaging, fit, manufacturing details and validation may still change before production.

Horizon talks to the XC module.

In a movement test, Horizon sent live GNSS positions to the XC module over a wired connection. Forty-four fresh position messages were sent and acknowledged, with no write failures and no stale positions sent after the movement stopped.

This proves the wired communication path. Receiving traffic over the air has not been demonstrated and is the next major XC test.

The 3.5-inch portrait display is alive.

The first image appeared on the new 3.5-inch display running on real Horizon hardware.

Electrical bring-up is done. Driver integration, the correct resolution and interface work continue before the display is validated.

The first Horizon boards pass bring-up.

The first batch has five assembled four-layer Horizon boards. They power up, accept firmware and run the development display.

These are engineering units, not units for sale. Charging, sensors, GNSS, sound, storage, Bluetooth, buttons and battery life still need deeper validation before enclosure and flight testing.

A test bench inside the app.

The companion app gained a repeatable simulation layer that drives the same data path the real instrument uses. It makes it safer to test flight states, alerts, maps and interface decisions on the ground.

Correction, 2 October 2026: this entry first called the app “VIRON Flight Lab”. The app is VIRON Air; Flight Lab is its simulation and testing part.

Known pilots first. A clear record every time.

The first assembled units will go to selected pilots who can describe what happened and separate a personal preference from a problem that can be repeated.

Ground checks, an independent backup instrument, defined scenarios and logs after each flight are part of the process.

Quantities and specifications in older entries were reported at the time and have not been re-checked for this update. Questions: hello@vironlabs.eu.