OmniBus VME Interface for Multiple Avionics Databuses

Description

The high-performance OmniBus VME may be used for simulating, monitoring, and testing avionics databuses. OmniBus VME are members 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.

TOP OF PAGE

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 combinations 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 users may upgrade or reconfigure their OmniBus with additional functionality, channels, and protocols as their requirements change.

TOP OF PAGE

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).

TOP OF PAGE

User Processor

An on-board PowerPC processor can be programmed by the user to off-load or run independently of the host computer. 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. Possible applications include data servers/converters, dynamic data generation/simulation, data filtering, and event triggering.

TOP OF PAGE

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.

TOP OF PAGE

OmniBus VME Configurations

Channel Count per Module

Protocol	Maximum Channels
1553	2 (both dual-redundant)
429	16 (various R/T configurations)
708	4 (2R/2T)
717	4R/4T (biphase/bipolar selectable)
serial	4 RS-422/232/423 ports
CSDB	8 (4R/4T)
discrete IO	32 discrete IO lines

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 16 ARINC 429 channels plus 8 ARINC 717 channels and 4 serial ports

• 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

TOP OF PAGE

Technical Specifications

Interface

• Tundra Universe II VME:
• A32/A24/A16 master and slave
• D64/D32/D16/D08 master and slave
• MBLT, BLT, ADOH, RMW, LOCK, location monitors
• PMC site (P/N 152 only):
• PrPMC compatible
• Monarch or non-Monarch modes
• Ethernet: 10/100 auto-speed sensing
• RS-232: Two ports (on single RJ12)
• CompactFlash slot: Type I/II
• IRIG modes: A and B

• BTIDriver™ API included (VB, C/C++, LabVIEW®)
• CoPilot® available (Windows® software)
• Source-level OS drivers included
• Embedded Linux installed; SDK available

• Processor: IBM PowerPC (405GPr), 333 MHz
• Memory: 64 MB SDRAM, 4 MB Flash
• DIO: 2 inputs, 2 outputs (additional 3 inputs and 3 outputs per core)
• Other: real-time clock (200+ hrs. backup)

• Size: 6U x 4HP (233 x 160 x 20 mm)
• Weight: 3.5 lbs. (1.6 kg)

• 60-pin Molex® LFH™ (per core)
• Various cables and connectors available

• Contact Ballard Technology for details

• Temperature: 0?55° C (extended temperatures available)
• Humidity: 0?95% (non-condensing)

TOP OF PAGE

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, and ARINC 708), it is the ideal tool for OmniBus. CoPilot may be purchased separately or bundled with OmniBus hardware.

Software developers can use the included BTIDriver API library to quickly develop custom applications. 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.

Source-level drivers are included for interfacing to the OmniBus VME board. An SDK is available for experienced Linux users to develop software for the PowerPC.

TOP OF PAGE

Ordering Information

The order number for an OmniBus product is a combination of the board part number and module part number(s). For example, a 152-xxx-xxx is an OmniBus VME board with two protocol modules and a PMC site (xxx = module P/N).

P/N	Description
152	two-core VME with PMC site
154	four-core VME (no PMC site)

TOP OF PAGE

Download Brochure

Adobe Acrobat is required to view the PDF.
Click here to download a free version of Acrobat Reader

Top