OpenVPX: Profiles for modular embedded hardware
Part of the Open Architecture Field Guide.
OpenVPX, the VITA 65 system standard, defines profiles that relate plug-in modules to slots and backplanes. These profiles turn the flexibility of VPX into explicit system-level interface arrangements.
In this guide
Connecting a processor to the rest of a chassis
A modular embedded computer contains circuit boards that perform different jobs. One board may process sensor data, another may move data between connections, and another may provide an interface to equipment outside the enclosure. The boards need power and physical support, but they also need a defined arrangement of connections through which those jobs can be performed together.
In this setting, a plug-in module is a circuit-board assembly installed in a chassis. A slot is the position and connection provided for that module. The backplane is the board that connects the slots. These three objects describe the hardware from the component outward: what the card provides, what its installed position provides, and how that position connects to the rest of the system.
VPX supplies building blocks for these rugged embedded systems. OpenVPX, the VITA 65 system standard, uses those building blocks to define system-level arrangements called profiles. A profile records a particular allocation of interfaces so that the intended connections can be specified and compared. [1]
Three views of the same connection
A module profile describes the interfaces provided by a card. A slot profile describes the interfaces available at the position where the card is installed. A backplane profile describes the connections among slots. Together, the profiles allow a design to relate a proposed module to the system in which it will operate.
Consider a processor that receives observations from an input module and sends results to another component. The processor's module profile describes its available connections. The selected slot exposes corresponding paths, and the backplane connects those paths to the required destinations. Following the profiles shows how data can travel through the assembled hardware.
Scroll horizontally to inspect the diagram.
This is why a system drawing needs more than a row of labeled cards. The drawing shows where the modules are placed; the profiles describe the interfaces associated with that placement. A replacement processor can then be evaluated against the position it must occupy and the connections its workload requires.
How the wider VITA family supplies the details
OpenVPX builds on specifications that address different aspects of the hardware. VITA 46 establishes the VPX baseline, while related specifications address areas such as power, cooling, optical connections, and radio-frequency connections. VITA 65 organizes the system profiles, and VITA 65.1 supplies profile tables used with the system standard. [1]
Separating these subjects allows the architecture to refer to a defined mechanical or electrical interface while describing the arrangement of the complete system. The backplane designer can work from the selected topology, the module supplier can implement the required connections, and the chassis design can provide the associated physical resources.
A topology is the arrangement of paths between the modules. Some paths may connect modules directly, while others may pass through switching functions. The chosen arrangement follows the application's data movement. A design that distributes observations to several processors has a different communication problem from one that sends each input to a single destination.
Using profiles to plan an upgrade
Suppose the processing workload grows and the program considers a replacement card. The first architectural question is how that card participates in the existing system. Its required data paths, power, management, and cooling must be related to the slot and chassis design. The profiles provide a structured starting point for that examination.
The same approach helps divide supplier responsibilities. The card supplier describes the interfaces the module implements. The backplane and chassis suppliers describe the resources and connections they provide. Integration then verifies the assembled system at those documented boundaries.
SOSA applies selected hardware profiles within a broader sensor-system architecture. CMOSS places modular hardware within the Army's approach to shared mission infrastructure. The OpenVPX profile remains the hardware connection description used within those wider designs.