|
FEATURED PRODUCTS
|
Ethernet/USB for ARINC 429
- IRIG Timetag
- PowerPC user processor
- CompactFlash slot
- Parametric
The OmniBusBox enables computers and networks to interface with up to 32 ARINC 429 channels or a combination of ARINC 429 with other protocols via Ethernet or USB.
|
For More Information
800.829.1553
|
|
OmniBus 429
OmniBus 429 refers to the ARINC 429 capabilities available for all modular OmniBus platforms. Each module provides up to 16 ARINC 429 channels. Total channel count and functionality depend on the number and type of modules on the platform. Modules with various receive/transmit combinations, parametric functionality (variable transmit amplitude and programmable frequency), and combinations with ARINC 429, 717, and serial ports are available (see ordering information).
OmniBus 429 offers ease-of-use and many advanced features. On-board processors automatically handle all protocol related activity, freeing users to focus on their applications.
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
- Up to 16 ARINC 429 channels per module (various R/T mixes available)
- Available in parametric versions (programmable transmit amplitude and frequency)
- Programmable parity for each 429 channel (odd/even/data)
- Programmable speed options:
- Auto-detect (on receive channels) or fixed
- 12.5/100 Kbps (default) or custom speeds (on parametric channels)
- Buffering schemes facilitate data handling:
- Single buffer is the default (receive/transmit)
- Ping-pong double buffers ensure data integrity (receive/transmit)
- Circular lists transmit a repeated pattern, such as a sine wave (transmit)
- Asynchronous list buffers support protocols such as ARINC 615 (transmit)
- FIFO list buffers can handle sequences of data (receive/transmit)
- Internal wrap-around self-test bus facilitates built-in test and diagnostics
Transmitters
- Transmit a single message, a schedule, or asynchronous messages (interleaved in schedule)
- Create automatic schedule (based on specified repetition rates) or explicit schedule with:
- Messages (labels)
- Conditional gaps (allow asynchronous transmissions)
- Fixed gaps (do not allow asynchronous transmissions)
- Branches and calls (control schedule sequencing)
- Schedule operation modes:
- Continuous cycle
- Specified number of loops
- Single-step (for debugging)
- Messages can be tagged for error injection, sync out signaling, and logging/interrupts
- Error injection: parity (in all or tagged messages) and inter-message gap (0 to 3 bit times)
- Variable transmit amplitude for parametric transmitters
- Output a sync pulse on all or selected messages (multiple sync lines are available)
- Externally trigger all or selected messages (using any of multiple trigger lines)
Receivers
- Programmable filtering by label/SDI combinations
- Automatic error detection:
- Gap errors (less than 4 bit times)
- Bit timing (timing error in at least one bit)
- Long word (more than 32 bits)
- Short word (time out error)
- Parity
- Detected errors can be logged and can generate interrupts
- Generate a sync out signal on received messages (multiple sync lines available)
Sequential Monitor
- Create a sequential record in on-board memory or stream to file (with a simple program)
- Monitor concurrently with transmitter/receiver operation
- Monitor recording modes: circular or fill and halt
- Monitor sampling modes to reduce total record count: interval mode or delta mode
- Each monitored message includes:
- The 32-bit word
- Channel number
- Bus speed
- Time-tag
- Detected errors
Time-Tags
- Use 32-bit binary timer or 64-bit IRIG timer (displays day/hour/min/sec/ms/µs)
- IRIG timer options:
- Select IRIG-B or IRIG-A format
- Generate IRIG signal or sync up to an IRIG signal (on-board or external)
- Initialize timer to time of day or other value
Interrupts/Logging
- Configurable event log can be polled and can generate interrupts to the host PC
- The following events may be user-selected for logging/interrupts:
- When the monitor is full or halts
- On a user-specified frequency of monitored messages
- When tagged messages are sent or received
- When a message error is detected
- When a schedule halts or pauses
- When a schedule encounters a user-inserted Log Event command
- When a list buffer is empty or full
The Downloads section contains data sheets with complete information on ARINC 429 functionality for OmniBus products.
PCI AND cPCI
 The OmniBus PCI and cPCI boards can host 1 or 2 on-board cores with circuitry to support 1 or 2 protocol modules. Because each on-board core has its own dedicated DSP, the OmniBus PCI/cPCI boards can host up to 32 ARINC 429 channels without relying on the host processor or risking data loss from an overloaded DSP.
Ethernet/USB
 The OmniBusBox device hosts 2 on-board cores with circuitry to support 2 protocol modules. Because each on-board core has its own dedicated DSP, the OmniBusBox device can host up to 32 ARINC 429 channels without relying on the host processor or risking data loss from an overloaded DSP.
|
|
VME
 The OmniBus VME boards can host 2 or 4 on-board cores with circuitry to support up to 4 protocol modules. Because each on-board core has its own dedicated DSP, the OmniBus VME boards can host up to 64 ARINC 429 channels without relying on the host processor or risking data loss from an overloaded DSP.
|
CoPilot
 The easiest way to use the ARINC 429 functionality of your OmniBus board is with CoPilot, Ballard's Windows-based software. CoPilot is an intuitive, interactive program that simplifies the testing and simulation of ARINC 429 systems. 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 429 traffic. Equipment ID and label definitions are built into the CoPilot 429 database. 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.
PowerPC
An SDK is available for advanced users who are developing software to run on the PowerPC (available on OmniBusBox, OmniBus VME, and OmniBus PMC).
|
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
|
112-423-423
|
|
OmniBus PCI board with two 8R/8T ARINC 429 modules
|
|
162-438-822
|
|
OmniBusBox with a 8R/8T parametric ARINC 429 and a 2R/2T parametric ARINC 708 module
|
XXX :: Platform Number
| # | Description |
| 111 | PCI w/ 1 core |
| 112 | PCI w/ 2 cores |
| 121 | 3U cPCI w/ 1 core |
| 122 | 3U cPCI w/ 2 cores |
| 141 | PMC w/ 1 fixed core
(MIL-STD-1553 only) |
| 152 | 6U VME w/ 2 cores and PMC site |
| 154 | 6U VME w/ 4 cores (no PMC site) |
| 162 | OmniBusBox w/ 2 cores |
CoPilot Code
To include CoPilot add "CP-" before the OmniBus order number.
Example: CP-162-438-822
Options
Contact Ballard sales for information on available OmniBus options.
|
|
YYY :: ARINC 429 Module Numbers
| # |
Description |
| 421 |
16R/0T ARINC 429 |
| 422 |
12R/4T ARINC 429 |
| 423 |
8R/8T ARINC 429 |
| 424 |
4R/12T ARINC 429 |
| 425 |
0R/16T ARINC 429 |
| 426 |
8R/0T ARINC 429 |
| 427 |
4R/4T ARINC 429 |
| 428 |
0R/8T ARINC 429 |
| 434 |
4R/4T parametric ARINC 429 |
| 435 |
4R/4T parametric
with 4R/4T ARINC 717* |
| 436 |
4R/4T ARINC 429
with 4 Serial UARTs |
| 437 |
4R/4T parametric ARINC 429
with 4R/4T CSDB |
nR = number of receive channels
nT = number of transmit channels
* On module # 435, ARINC 429 and bipolar ARINC 717 channels share the same receivers.
Multi-Protocol
OmniBus products are capable of concurrently hosting more than one avionics protocol on a single product.
See the OmniBus protocol pages for a list of available module numbers:
MIL-STD-1553,
ARINC 429,
ARINC 708,
ARINC 717,
CSDB,
Serial,
Discrete I/O
|
|
|
Adobe Acrobat is required to view PDF documents. Click Here to download a free version of Acrobat Reader. |
|
|
|