APX¶
Bridging AUTOSAR with modern systems¶
APX (AUTOSAR Port eXchange) connects AUTOSAR Classic software components with applications and devices outside the AUTOSAR environment. Designed specifically for the AUTOSAR Classic Platform, it provides a lightweight, language-independent way to describe ports and exchange their values in real time.
Get an introduction Read the specifications
Teams own their interfaces and can connect their software when it is ready, without centralized configuration or a large up-front integration step.
APX nodes can communicate through the same server regardless of their implementation language, operating system, or processor architecture.
APX definitions are concise text. Port values travel in compact binary data that is suitable for local networks and resource-constrained links.
One virtual signal bus¶
APX nodes publish the definitions of the ports they provide and require. An APX server matches compatible ports and routes value updates between nodes. Each node can use the programming language, operating system, and physical transport that best suits its job.
This makes the server behave like a virtual bus: nodes exchange automotive signals without depending on each other’s implementation details.
Choose a path¶
Learn the core model: nodes, ports, the virtual signal bus, and how APX relates to AUTOSAR.
Follow practical guides for working with APX definitions, nodes, and tools.
Learn about internal protocol architecture, RemoteFile memory-mapped synchronization, and connection session lifecycles.
Read the normative IDL, protocol, and virtual-machine specifications.
Implementations¶
APX implementations maintain their user and API documentation alongside their source code:
c-apx provides the C client and APX server, including support for embedded targets.
cpp-apx provides the C++ implementation.
py-apx provides the Python API, development tools, parsers, and code generators.