OmniBus VME™ Interface for ARINC 429

Description

The high-performance OmniBus VME may be used for simulating, monitoring, and testing up to 64 ARINC 429 channels or a combination of ARINC 429 with other protocols. OmniBus VME is a member of Ballard's OmniBus product line, a family of avionics databus interfaces that takes flexibility and power to a new level. With the demand for products with high channel counts and multi-protocol capability comes the need for more processing power, not only for handling the protocol but also for running the user's application. The OmniBus family has addressed these requirements through modularity and by adding multiple processors.

ARINC 429 Channels

All ARINC 429 receive channels feature automatic speed detection and independent label and SDI filtering. Each transmit channel automatically maintains accurate label repetition rates. To support data transfer protocols, aperiodic words may be transmitted without altering the timing of periodic words. Both receive and transmit channels may be independently set for standard high or low speed (12.5 or 100 Kbps). Independently of normal operation on transmit and receive channels, the Sequential Monitor concurrently stores a time-tagged record of all or selected channel activity. This filtered record may be streamed to a file for later playback or analysis.

OmniBus ARINC 429 channels with parametric capability have variable transmit amplitude and user-configurable frequency. The transmit amplitude can be individually set in software for each channel. Configurable frequency, also set in software for each channel, allows both transmit and receive channels to operate at non-standard frequencies. Thus, 429 channels may also be used with equipment that varies from the ARINC 429 standard (such as some implementations of ARINC 575).

The OmniBus 429 page contains complete information on ARINC 429/575 functionality for OmniBus products.

ARINC 429 channels can be mixed with other protocols. See the OmniBus VME Configurations section below for examples.

Flexible Configuration

Through modularity, Ballard can provide unique, user-specified configurations on short notice at minimum cost. The flexibility of this design allows more protocol and channel count configurations to be developed and stocked than is practical with fixed configurations. The unique OmniBus architecture offers higher performance than general-purpose modular systems. Modularity also means that user may upgrade or reconfigure their OmniBus with additional functionality, channels, and protocols as their requirements change.

Multiple Processors

OmniBus modularity allows additional processors to be added as more channels and/or protocols are added. Because each module has its own DSP (see diagram below), OmniBus products provide high channel count and mixed protocol capability without relying on the host processor or risking data loss from an overloaded DSP. By including more channels, protocols, and processing power in a single product, OmniBus provides better economy of scale and requires less computer space (slots).

User Processor

An on-board PowerPC processor can be programmed by the user to off-load or run independently of the VME system processor. Users can upload programs and may save them in non-volatile on-board memory. The PowerPC can be configured to automatically boot and run without host intervention. OmniBus VME can function as a VME system controller or as an intelligent I/O board. Possible applications include data servers/converters, dynamic data generation/simulation, data filtering, and event triggering.

Additional Capabilities

• OmniBus VME provides a 10/100 Ethernet port, two serial RS-232 ports, and CompactFlash socket.
• In addition to normal operation through the VME backplane, the OmniBus VME may be controlled remotely through the Ethernet port.
• The VME interface is implemented with the Universe II from Tundra, which provides a wide range of address and data transfer modes.
• For additional flexibility, OmniBus VME can be ordered with a PrPMC-compatible PMC site that can operate in Monarch or non-Monarch modes.
• IRIG circuits allow channels, boards, and other equipment to be synchronized to a standard clock time. The IRIG time can come from an outside source or be generated on board.
• All OmniBus modules include various digital input and output signals.

OmniBus VME Configurations

Module Count per Board

Model	Modules	PMC
152	2	1
154	4	0

Channel Count per Module

Protocol	Maximum Channels
1553	2 (both dual-redundant)
429	16 (various R/T configurations)
708	4 (2R/2T)
717	Mix (biphase and bipolar)
Serial	4 UART Ports
CSDB	8 (4R/4T w/ parametrics)

Example Configurations for 2 Modules

• Up to 4 MIL-STD-1553 channels
• Up to 32 ARINC 429 channels
• 1 or 2 MIL-STD-1553 channels plus up to 16 ARINC 429 channels
• Up to 16 ARINC 429 channels plus 2 or 4 ARINC 708 channels
• Up to 24 ARINC 429 channels plus 8 ARINC 717 channels

Example Configurations for 4 Modules

• Up to 8 MIL-STD-1553 channels
• Up to 64 ARINC 429 channels
• 1 or 2 MIL-STD-1553 channels plus up to 48 ARINC 429 channels
• Up to 48 ARINC 429 channels plus 2 or 4 ARINC 708 channels
• Up to 40 ARINC 429 channels plus 2 or 4 ARINC 708 channels and 8 ARINC 717 channels

Technical Specifications

Physical

• 6U x 4HP (233 x 160 x 20 mm)
• Convection cooling
• 0° to +55° C (standard); extended temperatures available

• IBM 405GPr processor
• Tundra Universe II VME interface
  • A32/A24/A16 master and slave
  • D64/D32/D16/D08 master and slave
  • MBLT, BLT, ADOH, RMW, LOCK, location monitors
• OmniBus module sites: 2 or 4
• PMC site (model 152 only)
  • PrPMC-compatible
  • Monarch or non-Monarch modes
• Ethernet 10/100
• RS-232 serial: two ports (on single RJ11/RJ12)
• CompactFlash socket
• IRIG modes A and B

Software

The easiest way to operate an OmniBus VME card is with Ballard's CoPilot software running on a Windows computer. CoPilot is an intuitive, interactive program that simplifies the simulation and testing of avionics systems. CoPilot auto-detection, engineering units conversion, and other features increase user productivity. The Plus version of CoPilot adds graphical displays, a powerful scripting engine, and playback. Because CoPilot can host multiple devices, channels, and databuses (MIL-STD-1553, ARINC 429, ARINC 708, and serial), it is the ideal tool for OmniBus. CoPilot may be purchased separately or bundled with OmniBus hardware.

Software developers can use the Application Program Interface (API) to quickly develop an application. Although each OmniBus product can be easily configured and run with only a few API calls, the comprehensive library includes a broad range of functions for specialized needs. All OmniBus products run Ballard's universal BTIDriver™ API, so applications developed for one platform or product can be easily ported to another.

Windows 2000/XP drivers are included as well as source-level drivers for interfacing to the OmniBus VME board. A software development kit (SDK) is available to implement applications for the on-board PowerPC processor.

Ordering Information

The OmniBus VME card can be ordered in many combinations of modules and features. The complete order number for an OmniBus VME card is a combination of the main model number, module number(s), and options. Ballard Technology also offers a variety of cables and other accessories that interface with our products as well as various databuses. Please contact Ballard Technology for specific ordering information.