Astronics Ballard Technology OmniBus II PXI Express Product for Avionics Test
Created Feb 16, 2021
The Astronics Ballard Technology OmniBus II PXIe family provides avionics databus interface capability for the industry-standard PXIe platform. These interfaces are typically used for product development, production, and system test applications.
The OmniBus II PXIe databus interface products combine the standard PXIe interface with MIL-STD-1553 and ARINC 429 Avionics Data Bus interfaces. Interface cards can be ordered with either MIL-STD-1553 only, ARINC 429 only, or both interfaces on the same card. The PXIe interface includes a PCIe x1 interface to the controller as well as support for PXI clock, timing and trigger signals. The included Instrument Driver provides LabVIEW control of the Data Bus and robust examples.
The standard PXIe form factor OmniBus II PXIe interface cards may be installed in your PXIe chassis like most other standard cards. The Instrument Driver is downloadable from NI.com and includes examples, test program, graphical configuration manager, documentation as well as the LabVIEW driver. The following video summarizes the install and general hardware configuration of the card.
The OmniBus II ARINC 429 protocol is supported by the “441” 8-channel module and “442” 16-channel module. As shown in the Hardware video above, each card supports up to 2 modules for up to a total of 32-channels of ARINC 429. Each channel is programmed independently and transmit channels support the definition of message labels and transmission schedules. The schedules may be rate-based or explicitly defined for the utmost in transmission accuracy and control. Message labels may also be tied to discrete triggers or PXI triggers. Configuration is accomplished using the provided Graphical Configuration Manager and reading the provided files within LabVIEW. The video below shows some of the ARINC 429 specific features and options of the OmniBus II LabVIEW family.
As an example for writing an ARINC 429 interface program, an additional label can be added to receive channel in an existing program. Starting with the “Receive Labels” example, the following video shows how easy it is to extend an existing program and its configuration file.
The OmniBus II MIL-STD-1553 protocol is supported by 1 or 2 dual-redundant channel modules with either single-function (BC or RT or BM) or multi-function (any mix of BC, RTs and BM). The “510” and “511” are 1 and 2 channel single function modules. The “550” and “555” are 1 and 2 channel multi-function modules. As shown in the Hardware video, each card supports up to 2 modules for up to a total of up to 4-channels of MIL-STD-1553 on a single card.
Each channel is programmed independently and messages may be defined independently for the Bus Controller and each Remote Terminal and Sub-address. Bus Controller schedules are frame based for the utmost in transmission accuracy and control. Messages may also be tied to discrete triggers or PXI triggers. Configuration is accomplished using the provided Graphical Configuration Manager and reading the provided files within LabVIEW. The video below shows some of the MIL-STD-1553 specific features and options of the OmniBus II LabVIEW family.
As an example for writing a MIL-STD-1553 interface program, an additional sub-address can be added to an existing Remote Terminal in an existing Bus Controller program. Starting with the “BC Schedule and Data Update” example, this video shows how easy it is to extend an existing program and its configuration file.
The Astronics Ballard Technology OmniBus II PXIe Avionics Data Bus Interfaces are designed to test, monitor and control avionics systems in a modern PXIe based test system. Through a comprehensive driver interface, different avionics systems may be easily adapted to augment any test plan. Astronics Ballard Technology’s decades of Data Bus experience delivers a solution which will be supported well into the future.