A surveillance arrangement where the aircraft broadcasts its own position and the ground listens. This line was opened as the aviation-side counterpart to our body of work in electronic design and embedded software.
An aircraft broadcasts its own position and identity at regular intervals, on its own. This broadcast, sent by a Mode S transponder without waiting for a query, is called a squitter; its extended form, which also carries position and speed data, is called ADS-B. The work on the ground side is to collect these broadcasts, decode them, and turn them into surveillance data that decisions can be made on.
This isn't the work of a single discipline. The antenna and receiver side, the embedded software that decodes the message, the network layer that carries the data, and the interface that makes it traceable all have to be built at the same time; if one is missing, the others working correctly doesn't mean much. Building this chain from sensor to cloud, from one place, is work we've done for years. What changes in aviation isn't the chain itself, but the standards it's bound to and the burden of verification.
We opened this line as a research and development program. We don't have a station installed in the field today; the items below show the program's scope, not products already delivered. With an organization that has a need in this area, we define the work together, starting from feasibility.
What changes in aviation isn't the chain itself, but the standards it's bound to and the burden of verification.
A receiver station that collects extended squitter broadcasts: antenna and front-end selection, signal processing, message decoding, and timestamping. The station standing on its own in the field, recovering itself after an outage, and being remotely updatable are all kept in scope from the first day of design.
Decoding message formats; extracting position, speed, identity, and status fields; filtering out faulty and duplicate messages. The decoding layer is built to also store the raw data, because in a surveillance system, a record you can't look back on doesn't settle an argument.
The direction running from the ground to the aircraft: broadcasting traffic and weather information, designing the broadcast plan and coverage area. Since this direction is subject to heavier constraints than the receiving side, it stands as a separate item in the program.
Exposing collected data to external systems through a standard interface and showing it on its own dashboard. Device health, data continuity, and alarm behavior are also this layer's job; expected data not arriving is as important a signal as a threshold being exceeded.
In aviation, a device working isn't enough — how it was verified has to be on record too. Determining which broadcast and surveillance standards apply, setting up the measurement rig, and writing the acceptance procedures is a heading of its own within the program.
This line is an open development program and is run through the research and development area. If you have a need on the aviation side, we first work out its solvability and scope together.
Türkçe
English
Deutsch
Français
Español
Русский
Български
العربية
