From Github · · 1m 10s
Onboardapi links sensors and software
Rheinmetall's onboardapi defines a shared data layer for sensor systems, apps, and evolving vehicle software.
In brief
Rheinmetall's onboardapi defines a shared data layer for sensor systems, apps, and evolving vehicle software. Onboardapi is a DDS-based middleware layer that keeps sensor data exchange fast, typed, and version-tolerant across languages. Originally reported by Github.
A shared data layer
Onboardapi is an interface library and middleware for sensor systems and software components. Its data model gives different hardware and software pieces a common way to talk.
“standardized data model”
Built on ddkit
The library sits on Rheinmetall's ddkit software development kit. It uses the OMG Data Distribution Service standard for data-centric publish and subscribe messaging.
“Data Distribution Service (DDS)”
Fast data exchange
DDS is meant for demanding systems where timing matters. Onboardapi uses that architecture to move data with reliability and low latency.
“reliable, low-latency data exchange”
Versions can coexist
DDS XTypes and XCDR2 encoding let older and newer software versions keep communicating as the data model changes over time.
“full backward compatibility”
C++ at the core
The main library is C++, but teams are not locked into one language. Wrappers support Java, C# and .NET, and Python integrations.
“wrappers for Java, C# / .NET, and Python”
Docs map the path
The documentation points developers to architecture concepts, examples, configuration, interface references, changelogs, and license terms.
“Browse the Data Model and all interfaces”
Here's the gist
Onboardapi is a DDS-based middleware layer that keeps sensor data exchange fast, typed, and version-tolerant across languages.
