Ballard Technology, Inc. Avionics Databus and Embedded Solutions Customer Login | Contact Us | Site Map
    OmniBus cPCI
Bookmark and Share
 
 
Featured Products...
Featured
OmniBusBox

  • IRIG Timetag
  • PowerPC user processor
  • CompactFlash slot
  • Mixed protocols
  • High channel counts

The OmniBusBox enables computers and networks to interface with multiple avionics databuses via Ethernet or USB.

OmniBus® cPCI Interface for Multiple Avionics Databuses

download datasheet
OmniBus cPCI Interface for Multiple Avionics Databuses
OmniBus cPCI

OMNIBUS cPCI

OmniBus cPCI refers to the Compact PCI platform for OmniBus protocol modules. It may be ordered with one or two modules to support a variety of avionics databus protocols. OmniBus cPCI cards include general purpose digital I/O and IRIG sourcing and synchronizing.

OmniBus Product Family

Ballard's OmniBus products connect computers or networks to one or more avionics databuses. Separate web pages provide information on OmniBus platforms (PCI/cPCI, PMC, VME, USB/Ethernet), avionics protocols (MIL-STD-1553, ARINC 429, ARINC 708, ARINC 717, and CSDB), serial ports (RS-422/232/423), and Discrete I/O.

Applications for OmniBus products include testing, simulation, and operational uses of avionics databuses. 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.

General

  • OmniBus Modules: 1 or 2
  • Memory: 16MB SDRAM
  • DIO: 2 inputs, 2 outputs plus
    • 3 inputs, 3 outputs per module
  • IRIG A/B input and output

Interface

  • PCI/cPCI Rev. 2.1 to 3.0 compatible
  • Universal Card (5V or 3.3V signaling)
  • 32-bit; 33 MHz/66 MHz
  • Plug and Play

Physical

  • Size: 3U x 4HP (single slot, standard)
  • Weight: 5.3 oz. (150 g), plus 1 oz. per module

The Downloads section contains data sheets with complete information on functionality for OmniBus products.

MIL-STD-1553

Up to 2 dual-redundant 1553 channels per module - BC, RT, Monitor, multi-terminal, and advanced error injection. Five levels to choose from. More...

 

ARINC 429

Up to 16 ARINC 429 channels per module. Available with parametrics, ARINC 717 and CSDB channels, and serial ports. More...

ARINC 708

Up to 4 ARINC 708 channels (2R/2T) per module. Available in parametric versions. More...

 

ARINC 717

Up to 8 ARINC 717 channels (4R/4T) per module. Software-selectable between biphase/bipolar. More...

CSDB

8 channels of CSDB (4R/4T) per module. Available with ARINC 429. More...

 

Serial Ports

4 Serial UARTs per module. Available with ARINC 429. More...

Discrete I/O

32 Discrete I/O lines per module. More...

   

CoPilot

The easiest way to use your OmniBus cPCI board is with CoPilot, Ballard's Windows-based software. 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. In CoPilot, you can quickly build transmit schedules and enter and display data in meaningful engineering units. The Sequential Monitor captures, records, filters, displays, and exports databus traffic. CoPilot features include virtual instruments, hardware and software playback modes, and scripting. CoPilot also supports MIL-STD-1553, ARINC 708, ARINC 664/AFDX and limited serial communications. Because CoPilot can host multiple cards, channels, and databuses, it is the ideal tool for operating OmniBus products. CoPilot may be purchased as part of an OmniBus system or separately.

 

BTIDriver API

Alternatively, software developers can use the included Application Program Interface (API) to quickly develop custom applications. OmniBus products can be easily configured and operated with only a few API calls. The comprehensive library also includes a broad range of functions for specialized needs.

Drivers

Driver software is available for Windows®, Linux®, LabVIEW, LabVIEW RT, VxWorks®, INTEGRITY® and other operating systems. Availability varies by product. Contact Ballard for specific details for your desired Omnibus product.

OmniBus Part Numbers

The part number for an OmniBus product is a combination of the platform number, module number(s), CoPilot code, and options. This results in thousands of possible part number combinations. Contact Ballard sales for assistance in determining the best OmniBus order number to fit your needs. Each platform core can accept one module. A core without a module may be used for future expansion.

Example Part Numbers

122-544-423   OmniBus cPCI board with a two channel 1553 (level C) and a 8R/8T ARINC 429 module
122-438-822   OmniBus cPCI board with a 8R/8T parametric ARINC 429 and a 2R/2T parametric ARINC 708 module

Board Part Number + Module Part Numbers

XXX :: Platform Number

#Description
111PCI w/ 1 core
112PCI w/ 2 cores
1213U cPCI w/ 1 core
1223U cPCI w/ 2 cores
141PMC w/ 1 fixed core
(MIL-STD-1553 only)
1526U VME w/ 2 cores and PMC site
1546U VME w/ 4 cores (no PMC site)
162OmniBusBox w/ 2 cores

CoPilot Code

To include CoPilot add "CP-" before the OmniBus order number.

Example: CP-122-544-423

Options

Contact Ballard sales for information on available OmniBus options.

 

YYY :: MIL-STD-1553 Module Numbers

See the OmniBus 1553 product page for a complete list of 1553 module numbers.

Example: 544 = Two level C channel module

YYY :: ARINC 429 Module Numbers

See the OmniBus 429 product page for a complete list of 429 module numbers.

Example: 427 = 4R/4T module

YYY :: ARINC 708 Module Numbers

See the OmniBus 708 product page for a complete list of 708 module numbers.

Example: 811 = 2R/2T module

YYY :: ARINC 717 Module Numbers

See the OmniBus 717 product page for a complete list of 717 module numbers.

Example: 431 = 4R/4T module

YYY :: Serial Module Numbers

See the OmniBus Serial product page for a complete list of Serial module numbers.

Example: 432 = 4 Serial UARTs module

YYY :: CSDB Module Numbers

See the OmniBus CSDB product page for a complete list of CSDB module numbers.

Example: 433 = 4R/4T module

YYY :: Discrete I/O Module Numbers

See the OmniBus Discrete I/O product page for a complete list of Discrete I/O module numbers.

Example: 832 = 32 Discrete I/O line module

Recomended Accessories



Browse all accessories
TypeTitleDate
  Datasheet OmniBus 429 Datasheet 7/6/2004
  Datasheet OmniBus 708 Datasheet 7/1/2004
  Datasheet OmniBus 717 Datasheet 7/19/2004
  Datasheet OmniBus 1553 Datasheet 7/19/2004
  Datasheet OmniBus Serial Datasheet 10/28/2004
  Datasheet OmniBus CSDB Datasheet 4/18/2005
  Datasheet OmniBus Discrete IO Datasheet 4/18/2005
  Datasheet OmniBus PCI-cPCI Datasheet 7/19/2004
X Product Manual OmniBus PCI-cPCI Manual 6/12/2003
X Product Manual OmniBus Discrete IO Manual 9/14/2007
X Product Manual OmniBus CSDB Manual 6/12/2003
X API Manual BTIDriver 1553 Manual 6/13/2011
X API Manual BTIDriver 429 Manual 6/14/2011
X API Manual BTIDriver 708 Manual 10/23/2009
X API Manual BTIDriver 717 Manual 6/15/2011
X API Manual BTIDriver 717 Repeater Addendum 8/31/2004
X API Manual BTIDriver Serial Manual 11/23/2004
X Driver OmniBus cPCI Driver Win32/64 6/10/2011
X Examples OmniBus C Examples 6/10/2011
X Examples OmniBus VB Examples 6/10/2011
X Examples OmniBus LabVIEW Examples 6/10/2011
X Examples OmniBus VB.NET Examples 6/10/2011
X Examples OmniBus C-Sharp Examples 6/10/2011
X Examples Williamsburg Library and Examples 3/3/2010
Get Adobe Reader

Adobe Acrobat is required to view PDF documents. Click Here to download a free version of Acrobat Reader.

Databus Analyzer & Simulator

LFH to 2 D-sub connectors

LFH to LFH connector

LFH to 4 MIL-STD-1553 twinax cables and 1 D-Sub connector
 
 
Employment | Privacy Policy | Legal Copyright © 1996-2012 Ballard Technology, Inc. All rights reserved.