OmniBus® Family for CSDB

Description

Ballard's OmniBus products connect computers or networks to one or more avionics databuses. OmniBus CSDB refers to the Commercial Standard Digital Bus (CSDB) 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 ARINC 717), 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 off-load the host for stand-alone operation. Each module has its own DSP dedicated to protocol processing.

OmniBus CSDB may be used for communicating with and monitoring serial digital avionics equipment including communication and navigation radios. With the addition of ARINC 429 channels, a single OmniBus product can simultaneously communicate with other commercial avionics equipment. OmniBus CSDB may also be used for some general purpose scheduled and asynchronous serial communications.

OmniBus CSDB modules are available with up to 4 receive and 4 transmit (4R/4T) CSDB channels and can be combined with 4 receive and 4 transmit (4R/4T) ARINC 429 channels on the same module. All CSDB receive channels feature independent filtering based on the message label (address byte) and the source identifier field (status byte). Each transmit channel supports continuous, non-continuous, and burst messages. On-board scheduling can accurately maintain message repetition rates.

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

CSDB Functional Specifications

General

• Each CSDB module has 4 receive and 4 transmit (4R/4T) channels
• Programmable parity for each CSDB channel (odd/even/mark/space/none)
• Programmable parity for each 429 channel (odd/even/data)
• Programmable speed options:
• LO: 12.5 Kbps
• HI: 50 Kbps
• Custom
• 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)
• FIFO list buffers can handle sequences of data (receive/transmit)
• Internal wrap-around self-test bus facilitates built-in test and diagnostics

• Vary the transmit amplitude under software control
• Messages scheduled according to bus parameters
• Continuous, non-continuous, and burst transmission supported
• Messages can be tagged for logging/interrupts

• Automatically synchronizes with frame sync block
• Can receive continuous, non-continuous, and burst transmission
• Programmable filtering by label (address byte) and source identifier field (status byte)
• Automatic error detection:
• Bit error
• Parity error
• Frame error
• Detected errors can be logged and can generate interrupts

• Create a sequential record in on-board memory or stream to file (with a simple program)
• Monitor concurrently with transmitter/receiver operation
• Monitor CSDB and ARINC 429 concurrently
• Monitor recording modes:
• Circular
• Fill and halt
• Each monitored message includes the label, status, data, channel number, and time-tag

• 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

• 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

Example Configurations

CSDB Configurations for 2 Modules

• 8R/8T CSDB channels plus 8R/8T ARINC 429 channels
• 4R/4T CSDB channels plus 12R/12T ARINC 429 channels
• 4R/4T CSDB channels plus 4R/4T ARINC 429 channels and 1 or 2 MIL-STD-1553 channels
• 4R/4T CSDB channels plus 4R/4T ARINC 717 channels and 8R/8T ARINC 429 channels

• 16R/16T CSDB channels plus 16R/16T ARINC 429 channels
• 12R/12T CSDB channels plus 20R/20T ARINC 429 channels
• 4R/4T CSDB channels plus 4R/4T ARINC 429 channels plus 4R/4T ARINC 708 channels and 1 or 2 MIL-STD-1553 channels
• 4R/4T CSDB channels plus 4 Serial UARTs plus 4R/4T ARINC 717 channels plus 12R/12T ARINC 429 channels and 2R/2T ARINC 708 channels

Software

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 Numbers—The 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-427 is an OmniBus PCI with a 4R/4T ARINC 429 module.

CSDB Module Part Numbers—The table below lists standard CSDB modules. Contact Ballard for more details.