Ballard Technology, Inc. Customer Login | Employment | Search Astronics Corporation
  ARINC 664 Home > Products > ARINC 664 > ARINC 664 Products
Bookmark and Share
Possible Replacements...
There are currently no products designated for replacement.

Interfaces for the ARINC 664 / AFDX Protocol

PCI, cPCI, and PMC Interfaces for the ARINC 664 / AFDX Protocol
ARINC 664 PMC, PCI, and cPCI
  • 2 ports at 10 or 100 Mbps
  • Dual-redundant or independent
  • Transmit, receive, and monitor
  • On-board integrity, redundancy, and flow control
  • Gathers wide range of statistics (MIB support)
  • Packet time tagging
  • Extensive filtering
  • Error detection and injection
  • Available in PCI, cPCI, and PMC
  • Interactive and API software
  • Optimized onboard recording and VL/Port processing offloads host processor
  • CoPilot® and API software

Obsolete Product

This is an obsolete product and is no longer available for sale. For replacements of this product and for all new applications please consider the "Possible Replacements" at left, or browse our other products.


Ballard's ARINC 664 products interface various computer platforms with Ethernet based aircraft data networks. They enable computers with PCI, cPCI, or PMC expansion slots to receive and transmit data over an ARINC 664 Part 7 Avionics Full Duplex Switched Ethernet network, also known as AFDX®, a registered trademark of Airbus. These products meet the demanding requirements of ARINC 664, which is used on many of the newest aircraft.

Engineers and technicians use these Ballard interface cards for development, production, and maintenance of ARINC 664 equipped products and systems. Ballard products are used as testers of end systems, as simulators of network switches and end systems, and as databus analyzers for measuring and recording network performance. Applications are found in engineering laboratories, in avionics and airframe factories, on the flight-line, and in maintenance facilities.


A powerful dedicated on-board processor (PowerPC) handles the protocol, freeing the host processor for user applications. Integrity checking, redundancy management, and flow control (scheduling) are all built-in to the firmware running on the on-board processor.

Levels of functionality

Ballards ARINC 664/AFDX® compatible interface cards include models with varying levels of functionality. The base model permits functional operation of the transmitters and receivers or capturing bus activity through a sequential monitor. More advanced models allow operation of the transmitters and receivers while concurrently monitoring. All models capture numerous network characteristics, providing a statistical record of errors and performance. User controlled filters can limit the results to only those of interest. Additionally, advanced models can also be programmed to transmit different kinds of errors for the purpose of verifying how equipment or systems respond to error conditions.

Features Model
Transmit and Receive
Bus Monitor
Concurrent with Tx/Rx  
Error injection  


  • Redundant or independent operation
  • VL support
  • Sub-VL support
  • Queuing and sampling ports
  • No pre-determined limit to number of VLs or ports per VL
  • Non-standard addressing support (MAC, IP, etc.)
  • Standard MIB (Management Information Base) usage
  • Configurable RSN (Redundancy Sequence Number) usage
  • Packet time-tagging at 1 microsecond resolution


  • Traffic shaping using BAG (Bandwidth Allocation Gap)
  • Automatic scheduling based on VL's BAG and port rates
  • Flexible custom scheduling of VLs and ports
  • Asynchronous single-shot transmission of any packet
  • Packet to network control (A/B/A&B)
  • Configurable queuing port depth
  • Actively modify transmit data
  • Configurable frames (headers and payload)


  • Configurable integrity and redundancy checking
  • VL and port filtering
  • Default port for non-filtered 664 packets
  • Non-664 packet handling for host processing
  • Configurable queuing port depth


  • Records packets with time-tag, header, data, and status information
  • Monitor all or a selective group of packets (filtering)
  • Filtering options
    • VL, port, network
    • Packets with errors
    • Undefined packets
    • Protocol
  • Summary mode records header information without payload
  • Continuous or fill and halt operation

Error Injection

Timing Errors

  • BAG violation
  • Inter-frame gap (4-63 byte times)
  • Packet flooding

Logical Errors

  • Frame size
  • Data alignment
  • Layers 2, 3, 4 (i.e., IP address, IP version, CRC, length, etc.)

Protocol Errors

  • Multiple sources for same destination port
  • Port rate
  • Redundancy


  • PMC form factor (149 mm x 74 mm)
  • PCI/PCI-X interface
    • 32/64-bit
    • 33/66 MHz
    • 66-133 MHz (PCI-X)
    • 3.3V I/O


  • cPCI Carrier (3U) with PMC Module
  • PCI bridge (i21154)
  • 32/64-bit
  • 33/66 MHz
  • 5V/3.3V I/O


  • PCI Carrier (short) with PMC Module
  • PCI/PCI-X (i31154)
    • 32/64-bit
    • 33/66 MHz
    • 66-133 MHz
    • 5V/3.3V I/O


The easiest way to use Ballard products for the ARINC 664/AFDX® protocol in a Windows environment is with Ballard's CoPilot software, which provides interactive access to network information and data without software programming. The intuitive Windows environment enables users to quickly and easily analyze and simulate ARINC 664 network activity.

Application Program Interface

The Application Program Interface (API) provides high-level functions that enable custom software applications to be developed with only a few function calls. API functions configure the hardware to handle the desired Virtual Links (VLs), sub-VLs, sampling ports, and queuing ports. Extensive scheduling capability allows the user to control the sequencing of packets transmitted on the network. The API accesses data through sampling and queuing ports either in raw form or in user-defined engineering units.

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