Connection is not the data model.
Communication mechanisms remain distinct from the telemetry parameters engineers work with inside RAQIA.
RAQIA02 / TECHNOLOGY
Different sources.
One parameter model.
RAQIA separates telemetry transport and protocol handling from the engineering parameters used by the rest of the platform.
ARCHITECTURE
A layered telemetry
pipeline.
01Sources
Aircraft, vehicles, test articles, instrumentation, simulation
↓02Transports
Serial / UART, SiK, Ethernet, Wi-Fi, CAN
↓03Protocol adapters
MAVLink, JSON, configurable binary, custom protocols
↓04Mapping + normalization
Incoming data mapped into a common engineering parameter model
↓05RAQIA parameter model
A consistent telemetry representation across sources and protocols
↓06Operations + investigation
Live monitoring, recording, replay, events, mapping, 3D, reporting
CONNECTION + PROTOCOL
01 / INGESTConfigure how telemetry enters the platform.
Connection and protocol configuration remain separate from the engineering parameter model, allowing RAQIA to ingest telemetry through different transports and protocol adapters without tying the workspace to a single source.
Adapters interpret incoming data.
Protocol-specific handling converts incoming messages before parameter mapping and normalization.
Parameters become reusable.
Once mapped into the common model, the same parameters can drive visualization, recording, alerts, replay, and analysis.
MAPPING + NORMALIZATION
02 / NORMALIZETranslate incoming data
into engineering parameters.
Incoming protocol fields can be mapped into RAQIA's normalized parameter model so the rest of the platform can operate on a consistent telemetry representation independent of the original source or protocol.
SOURCE FIELD→MAPPING→PARAMETER
DATA FLOW
RAW TELEMETRYADAPTERMAPPINGNORMALIZED PARAMETERSESSION + WORKSPACE
ABOUT RAQIA
Company →