Ballard Technology, Inc. Customer Login | Employment | Search Astronics Corporation
    OmniBus Protocols Home > Products > OmniBus Protocols
Bookmark and Share
 
 
Featured Products...
Featured
CoPilot Software

  • Intuitive Interface
  • Virtual Instruments
  • Scripting
  • Playback

The CoPilot System is a complete line of software and hardware interfaces to MIL-STD-1553, ARINC 429, ARINC 708, ARINC 664 / AFDX® and serial avionics databuse protocols.

OmniBus® Family Protocol Overview

download datasheet
OmniBus® Family
OmniBus Family

Key Family Features

  • Multiple protocols
  • User processor (PowerPC®)
  • IRIG time and synchronization
  • 1 to 4 protocol processors
  • Can be upgraded/reconfigured
  • CoPilot® available (interactive Windows® software)

Platforms

The OmniBus Family

OmniBus is a highly-flexible and high-performance family of avionics databus interfaces combining a selection of industry-standard platforms (PCI/cPCI, VME, PMC and Ethernet/USB) with a wide-viariety of I/O choices (MIL-STD-1553, ARINC 429, ARINC 708, ARINC 717, Serial, CSDB and Discrete). This sophisticated OmniBus design allows users to order the exact number, functionality, and mix of protocol channels that they need. It also lets users upgrade or reconfigure their OmniBus (at the factory) as requirements change.

High-Performance Architecture

OmniBus products are built using an integrated board, core, and module architecture. PCI, cPCI, and Ethernet/USB boards include 1 or 2 cores, VME boards have up to 4, and PMC boards include a single fixed core. Each on-board core has a dedicated protocol processor, IRIG timer, and 3 sync and 3 trigger lines. These cores are the support circuitry for the I/O modules, which contain the interface to the databus protocol(s). Isolating the protocol interface on the I/O module provides the flexibility to create custom, user-specified configurations for single or mixed protocols. The protocol-specific OmniBus architecture provides a better solution with greater performance than general-purpose modular systems (such as IndustryPack™).

OmniBus MIL-STD-1553

All modular OmniBus platforms can be ordered with MIL-STD-1553 capabilities. Each module provides one or two dual redundant 1553 channels. Total channel count and functionality depend on the number and type of modules on the platform. All models provide Bus Controller (BC), Remote Terminal (RT), and monitor operation and support all 1553 message types. Models with multi-terminal simulation and error injection are available.

OmniBus 1553 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 MIL-STD-1553 Specifications

OmniBus MIL-STD-1553 buses are available in five levels of functionality (summarized in the table below). All levels provide Bus Controller, Remote Terminal, or Monitor operation and support all 1553 message types. 1553 databuses can maintain a time-tagged history of bus activity in a Sequential Record file for storage and analysis. All OmniBus 1553 databuses provide software-selectable bus termination. Advanced features include multi-terminal simulation (up to 32) with concurrent monitoring, protocol error injection (word, gap, and message errors), variable transmit amplitude, and zero crossing distortion.

Levels of functionality for OmniBus 1553 channels

 Number of Simultaneous Terminals  A
1
B4
4
B32
32
C
32
D
32
Monitor
Filtering for terminal address
Filtering for subaddress
Concurrent terminal monitoring
 
     
Protocol Error Injection      
Variable Transmit Amplitude        
Zero Crossing Distortion        

Bus Controller

  • Specify no-response timeout value up to 102.4 µs in units of 0.1 µs
  • Automatic schedule (based on specified message frequencies) or custom schedule, including:
    • Multiple frames and programmable frame times
    • Programmable inter-message gap times
    • Conditional retries and branches for exception processing
  • Schedule operation modes:
    • Continuous (until explicitly halted)
    • Specified number of loops
    • Single-step mode (for debugging)
  • Configure schedule to wait for each message to be triggered or for a single starting trigger
  • Custom protocols are supported by variable word lengths and programmable pre-sync pulses
  • Programmable sync out signal on all or selected messages (multiple sync lines available)
  • Insert aperiodic messages into a running BC schedule

Remote Terminals

  • Multi-terminal simulation with up to 31 RTs (Level B4 or higher channels)
  • Configurable response time for MIL-STD-1553A or B (default)
  • Specify a response time value up to 25.5 µs, in units of 0.1 µs
  • Programmable status word bits
  • Auto Busy option automatically sets the Busy bit of the status word after each command
  • Programmable sync out signal on all or selected messages (multiple sync lines available)
  • Configure/legalize all or selected SAs and mode codes
  • Support for all 1553B mode codes
  • Selectable mode code subaddress (00000, 11111, both, or neither)
  • Enable broadcast reception on a per-RT basis
  • RT 31 functions as broadcast terminal or valid RT address

Monitor

  • Monitor concurrently with terminal simulation (Level C or higher channels)
  • Create a sequential record in board memory or stream to file (with a simple program)
  • Monitor and record all traffic on fully loaded buses
  • Capture all traffic or filter by RT, SA, or tagged BC messages
  • Each monitored message includes:
    • Command/status/data words
    • Time-tag
    • Detected errors
    • Transmission bus (A/B)
    • RT response time(s)
  • RT “Shadow Monitor” mode allows message activity of external RTs to be monitored

Message Data

  • Buffering schemes facilitate data handling:
    • Single buffers (default)
    • Ping-pong double buffers ensure data integrity
    • Circular lists transmit a repeated pattern, such as a sine wave
    • FIFO list buffers can handle sequences of data, such as file transfers
  • Data initialization options: zeros, incremental, or command word values
  • Each message record can track activity by min, max, or elapsed time

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

Error Injection

  • Protocol error injection (Level C and above):
    • Parity
    • Bit count
    • Inverted sync
    • Manchester
    • Gap
    • Word count (relative and absolute)
  • Advanced error injection (Level D):
    • Variable transmit amplitude
    • Zero crossing distortion on leading or mid-bit (± 5 to 250 ns, in 5 ns increments)
  • Trigger error injection from an external signal
  • Inject errors in all or tagged messages

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 (BC or RT) are sent or received
    • When the BC schedule halts or pauses
    • When the BC schedule encounters a user-inserted Log Event command
    • When a list buffer is empty or full

 

OmniBus ARINC 429

All modular OmniBus platforms can be ordered with ARINC 429 capabilities. 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.

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 ARINC 429 Specifications

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

 

OmniBus ARINC 708

All modular OmniBus platforms can be ordered with ARINC 708 capabilities. Its receivers and transmitters communicate over the display databus of an ARINC 708 airborne pulse Doppler weather radar. Modules are available with one or two pairs of receivers and transmitters and with variable transmit amplitude (parametric). Software-selectable word lengths and pre-sync pulses support custom protocols.

OmniBus 708 provides the capability to test and simulate weather radar CDUs (Control-Display Unit) and T-R (Transmit-Receive) units. Combined with an OmniBus 429 module, the control functions of a weather radar can also be simulated on a single OmniBus platform.

OmniBus ARINC 708 Specifications

General

  • ARINC 708 modules are available in transmitter/receiver pairs (1R/1T or 2R/2T)
    • Each transmitter and receiver can operate concurrently
    • The transmitter/receiver of each pair can independently operate on either of two buses
  • Parametric 708 modules provide variable transmit amplitude
  • All OmniBus 708 channels support standard ARINC 708 1600-bit words and syncs
  • Custom protocols are supported by variable word lengths and programmable pre-sync pulses
  • Configurable bit order for LSB (default) or MSB order (MIL-STD-1553 order)
  • Easily read and write header fields (such as angle, gain, etc.) and range bins
  • Software-selectable bus termination
  • Internal self-test bus facilitates built-in test and diagnostics

Transmitters

  • Multiple frames facilitate data handling (write to one set of frames while the other set of frames is transmitting)
  • Configurable frame frequency (in Hz) controls the repetition rate of 708 words
  • Trigger options (3 trigger inputs per module):
    • Configure a transmitter to externally trigger each message
    • Assign one trigger to multiple transmit channels for synchronized operation
    • Programmable polarity eases integration with external equipment
    • Use one or more lines and conditions to create multiple unique triggers

Receivers

  • Each received message is stored in a message record that includes:
    • The 1600-bit word
    • Any bits beyond 1600 (for variable bit count mode)
    • Total number of bits (for variable bit count mode)
    • Time-tag
    • Channel number
    • Detected errors
  • Detected errors:
    • Sync
    • Manchester
    • Long word
    • Short word
  • Optional error signaling through digital output(s)

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
    • Fill and halt

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

  • Event log can be polled or configured to 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

ActiveX Weather Radar Control

Contact us about our ActiveX Weather Radar Control. This program building block decodes the ARINC 708 message data and presents it in a highly customizable graphical display.

 

OmniBus ARINC 717

All modular OmniBus platforms can be ordered with ARINC 717 capabilities. OmniBus 717 modules have 4 receive and 4 transmit (4R/4T) channels, which handle both ARINC 717 and its predecessor, ARINC 573. Each channel is independently configurable for Harvard biphase or bipolar return-to-zero operation. Subframes, superframes, and wide range of speeds (words per second) are supported.

OmniBus 717 may be used for testing, simulating, and monitoring Flight Data Recorder systems. It can simulate both a DFDAU (Digital Flight Data Acquisition Unit) and a DFDR (Digital Flight Data Recorder).

OmniBus ARINC 717 Specifications

General

  • Each ARINC 717 module has 4 receive and 4 transmit (4R/4T) channels
  • Each channel is software-configurable for Harvard biphase or bipolar RZ
  • Channel speed may be independently set for 64, 128, 256, 512, 1024, 2048, 4096 or 8192 wps
  • Standard or user-specified sync words for each channel
  • Access words by word, subframe, and/or superframe number
  • Superframe support:
    • User-specified superframe counter location
    • User-specified number of frames per superframe
  • Internal wrap-around self-test bus facilitates built-in test and diagnostics

Transmitters

  • Vary the transmit amplitude under software control
  • Trigger options (3 trigger inputs per module):
    • Configure transmitter to wait for trigger signal
    • Assign one trigger to multiple transmit channels for synchronized operation
    • Programmable polarity eases integration with external equipment
    • Use one or more trigger lines and conditions to create multiple unique triggers
  • Output a sync signal on all or selected subframes (3 sync lines per module)

Receivers

  • Configure receivers to auto-detect speed (default) or specify a fixed speed
  • In-sync and out-of-sync status reporting
  • Optional notification if receiver loses sync (interrupt/log entry)
  • Each received subframe record includes:
    • 12-bit data words
    • Time-tag
    • Channel number
    • Bus speed

Sequential Monitor

  • Create a sequential record in on-board memory or stream to file (with a simple program)
  • Monitor concurrently with transmitter/receiver operation
  • Capture user-selected 717 words
  • Monitor recording modes:
    • Circular
    • Fill and halt

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 words are sent or received
    • When tagged subframes are sent or received
    • When a receive channel loses sync

 

OmniBus Serial

All modular OmniBus platforms can be ordered with RS-422, RS-232, RS-423 asynchronous communications capabilities. OmniBus Serial modules have four independent universal asynchronous receiver transmitters (UARTs), each having one transmitter and one receiver.

Serial interfaces are available with or without ARINC 429 on the same OmniBus module.

OmniBus Serial Specifications

General

  • 4 Transmitters and 4 Receivers per module
  • RS-422, RS-232, or RS-423 per port
  • Select through software and connector wiring

Baud Rates

  • To over 1 Mbps
  • By formula from CLK1 or CLK2:
    • Baud = CLKFreq/[(N + 1)*10]
    • Where: N is in the range of 0 to 4095
      • CLK1Freq = 20 MHz
      • CLK2Freq = 9.216 MHz
    • Special: Custom CLK2 available
Typical Baud Rates
BaudClockPrescale (N)BaudClockPrescale (N)
300CLK2307157,600CLK215
600CLK21535115,200CLK27
900CLK21023230,400CLK23
1,200CLK2767460,800CLK21
1,800CLK2511921,600CLK20
2,400CLK238312,500CLK1159
3,600CLK225525,000CLK179
4,800CLK219150,000CLK139
7,200CLK2127100,000CLK119
9,600CLK295200,000CLK19
14,400CLK263250,000CLK17
19,200CLK247400,000CLK14
28,800CLK231500,000CLK13
38,400CLK2231,000,000CLK11

Word Encoding

  • Start bits: 1
  • Data bits: 8
  • Parity: Odd/Even/Mark/Space/None
  • Stop bits: 1
  • But polarity: Normal/Inverted

FIFO Buffers

  • 4 Kbytes per transmitter
  • 4 Kbytes per receiver
  • FIFO threshold
    • One per FIFO
    • Settable as byte count
    • Reports to Event Log List

Transmitter Gap

  • Insert in data stream
  • Under software control
  • Length: 1 - 255 bit times
  • Repeatable for longer gaps
  • Use to regulate or schedule transmissions

Transmitter Rise/Fall Time

  • S/W selectable slope: High/Low
  • Special: Custom available

Status Reporting

  • Poll FIFO status
  • Poll Event Log List
  • Interrupts from Event Log List

Event Log List

  • Transmitter over threshold
  • Transmitter underflow (empty)
  • Receiver under threshold
  • Receiver overflow (full)
  • Receive error

API Support

  • Access to other board resources (IRIG time and digital I/O)
  • Easy-to-use functions

 

OmniBus CSDB

All modular OmniBus platforms can be ordered with CSDB serial communications capabilities. OmniBus CSDB modules have 4 receive and 4 transmit CSDB channels, which can be combined with ARINC 429 channels on the same module.

OmniBus CSDB may be used for testing, simulating, and monitoring serial digital avionics equipment, including communication and navigation radios. It can also provide general purpose scheduled and asynchronous serial communications.

CSDB 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

Transmitters

  • 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

Receivers

  • 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

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 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

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

 

OmniBus Discrete I/O

All modular OmniBus platforms can be ordered with standard avionics discrete and general-purpose digital IO capabilities. Each OmniBus Discrete I/O module has 32 IO lines configurable as inputs and/or as outputs. Inputs have programmable thresholds and debounce filters, and outputs have protection circuits and can sink up to 200 mA.

OmniBus Discrete is used to sense and control discrete signals in a wide range of applications with up to 40 VDC.

Discrete I/O Specifications

OmniBus Discrete provides interface capability for standard avionics discretes and general-purpose digital IO. OmniBus Discrete has many programmable features that facilitate its use for sensing, controlling, and testing DC circuits at voltages up to 40 VDC.

Each of the 32 IO lines may be configured as as an input and/or an output. The input of an IO line can be used in conjunction with its output for built-in test (i.e., to verify the state of the output) or to sense the state of an ORed circuit. Inputs can be configured as series (voltage/open or voltage/ground) or shunt (open/ground) with a programmable threshold voltage suitable for use from TTL level through 28 VDC. The debounce feature filters the input to eliminate excessive transitions. Outputs are open collector and can sink up to 200 mA.

Protection circuits permit switching of inductive loads and will shut down the output driver in over-current or over-temperature conditions.

 

 
 
Site Map | Privacy Policy | Legal Copyright © 1996-2014 Ballard Technology, Inc. All rights reserved.