OmniBusBox™ Ethernet/USB Interface for Multiple Avionics Databuses

Description

The OmniBusBox enables computers and networks to interface with multiple avionics databuses via Ethernet or USB. Applications for the OmniBusBox include simulation, monitoring, and testing of avionics equipment and systems. The OmniBusBox may be configured as a local peripheral to a computer, as a remote data server in a network, or as a stand-alone unit.

The OmniBusBox 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.

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.

user Processor

An on-board PowerPC processor can be programmed by the user to run independently or to off-load other processors in the system. Users can upload programs and may save them in non-volatile on-board memory. The PowerPC can be configured to automatically boot and run independently of the Ethernet or USB ports. Possible applications include data servers, data converters, dynamic data generation/simulation, data filtering, and event triggering. For example, the OmniBusBox could be configured as a stand-alone data converter that translates ARINC 429 to MIL-STD-1553.

Additional Capabilities

• The OmniBusBox provides two Ethernet ports, a USB 2.0 port, two serial RS-232 ports, and a CompactFlash socket
• The OmniBusBox may be controlled remotely through the Ethernet or USB ports
• The two auto-speed sensing 10/100 Ethernet ports are configured as a switch, so the OmniBusBox can be easily added in-line between a computer and its existing Ethernet connection
• 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
• In addition to desktop use, the OmniBusBox can be rack mounted or bolted down

OmniBusBox 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)
CSDB	8 (4R/4T)
serial	4 RS-422/232/423 ports
discrete IO	32 IO lines

Technical Specifications

Interface

• 10/100 Ethernet: 2 ports (internal switch)
• USB 2.0: Full speed and high speed
• RS-232: Two ports (on single RJ12)
• CompactFlash slot: Type I/II
• IRIG modes: A and B

• CoPilot® available (Windows® software)
• BTIDriver™ API included (VB, C/C++, LabVIEW®)
• OS drivers: Windows included; call for availability of Linux, VxWorks®, and others
• 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 (1000+ hours backup)

• Size: 1.7 (1U) x 12 x 9.6 in. (approx. 44 x 305 x 444 mm)
• Weight: 3.5 lbs. (1.6 kg)
• Mounting options:
  • table-top (rubber feet)
  • bolt-down
  • rack mount

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

• Supply (built-in):
• Built-in
• Universal 100-250 VAC, 0.6-0.25 A, 50-60 Hz
• Optional 28 VDC; others available
• Fuses:
• 1 A, 250 V, time lag
• 5 x 20 mm IEC 60127-2

• Temperature: 0° to 50° C
• Convection cooling: internal fan
• Humidity: 0 to 95% (non-condensing)

Software

The easiest way to operate an OmniBusBox 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 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.

Windows drivers are included; call for availability of Linux, VxWorks®, or other drivers. An SDK is available for experienced Linux users to develop software for the PowerPC.

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 162-xxx-xxx is an OmniBusBox with two protocol modules (xxx = module P/N).

P/N	Description
162	two-core OmniBusBox