Description
Ballard's OmniBus products connect computers or networks to one or more
avionics databuses. OmniBus 717 refers to the ARINC 717 capabilities available for all modular OmniBus platforms. Separate web pages provide information on OmniBus
platforms (PCI,
cPCI,
PMC,
VME,
USB/Ethernet), avionics protocols (MIL-STD-1553,
ARINC 429,
ARINC 708, and CSDB),
serial ports (RS-422/232/423), and discrete IO.
OmniBus products are built around an intelligent platform that can host one
or more protocol modules. This flexible architecture accommodates mixed protocols,
high channel counts, and unsurpassed processing power. An on-board PowerPC®
processor can be programmed by the user to offload the host or for stand-alone
operation. Each module has its own DSP dedicated to protocol processing.
OmniBus 717 may be used for communicating with and monitoring Flight Data Recorder systems. OmniBus 717 can simulate both a DFDAU (Digital Flight Data Acquisition Unit) and a DFDR (Digital Flight Data Recorder). With the addition of ARINC 429 channels, a single OmniBus product can also simulate a control panel or other system components.
OmniBus 717 modules have 4 receive and 4 transmit (4R/4T) channels that support both ARINC 717 and its predecessor, ARINC 573. High-speed capability is provided for compatibility with future systems. Each channel is independently configurable for Harvard biphase or bipolar return-to-zero operation. Superframe support includes user-configurable counter location and number of superframes per frame.
Applications for OmniBus products include testing, simulation, and operational uses
of avionics databuses. With its error detection and generation capability, OmniBus 429
is well suited to product development, production, and system testing. The high channel
count, multi-terminal capability, and on-board PowerPC processor provide the power necessary
for flight simulators and system integration laboratories. An OmniBus product may also be
used as a data server or as a stand-alone converter from one protocol to another.
Software
The easiest way to use OmniBus 717 products in a Windows® environment is with
the included 717 Monitor program.
Users can observe and record word, subframe,
and superframe data in octal and binary formats with just a few clicks of the
mouse. The intuitive interface makes it easy to modify sync word values and play
back recorded data files.
Alternatively, users can develop their own software using the included BTIDriver
API. 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.
An SDK is available for advanced users who are developing software to run on the
PowerPC.
Ordering Information
OmniBus Order NumbersThe order number for an OmniBus product is a
combination of the board part number (see table below) and module part number(s).
For example, order number 111-431 is an OmniBus PCI board with a 4R/4T ARINC 717
module.
|
1 Core |
2 Cores |
4 Cores |
| PCI (short) |
111 |
112 |
|
| cPCI (3U) |
121 |
122 |
|
| VME (6U) |
|
152 |
154 |
| Ethernet/USB |
|
162 |
|
ARINC 717 Module Part NumbersThe table below lists standard
717 modules. Additional configurations and protocols may be supported on
request. Contact Ballard for details.
| P/N |
Description |
| 431 |
4R/4T ARINC 717 |
| 435* |
4R/4T ARINC 717 with 4R/4T parametric 429* |
*On module P/N 435, ARINC 429 and bipolar ARINC 717 channels share the same receivers.