Avionics Blog

Preventing VME Obsolescence

Posted by Troy Troshynski on Sep 1, 2017 1:08:34 PM

Back in 1979 VME began as a bus system for the Motorola 68000. Within a few years it became a standardized bus in Europe and North America (ANSI/IEEE 1014-1987). Since then, designers at military and civilian avionics suppliers have used the VME architecture in thousands of test and simulation systems, and many of these systems require MIL-STD-1553 and ARINC 429 avionics bus interfaces..

With a sizeable global installed base and the ongoing requirement for test and simulation of legacy avionics products, VME-based systems will remain in active use well into the future. The reasons are simple:

  • The support horizon for commercial and military avionics is at least 10 years, usually 20 years. Many VME systems are only a few years old and must be available for another one or two decades.
  • A decision to obsolete VME systems and replace them with more up-to-date test and simulation systems is particularly unattractive—especially in light of the large software investment that is often greater than the cost of the physical system itself.

In short, VME-based systems remain functionally robust, and there is no compelling technical or economic reason to invest in new form factors—particularly in testing or simulating legacy avionics.

Nevertheless, VME has been around a long time and subsystem and component end of life (EOL) issues loom large.

The EOL Dilemma

Most VME systems in use today employ the PCI bus (or its variants) to control and communicate with VME-based instrumentation. A carrier or adapter board accomplishes the translation between the PCI and VME environments. The traditional heart of these adapter boards—including those from AIT—has been the TSI148 VME to PCI-X Bridge chip.


VME Block Diagram.png


However, the TSI148 has been obsoleted and is no longer supported by its manufacturer. TSI148 obsolescence presents a dilemma to both users and their suppliers, who are committed to keeping these VME systems in operation for another ten to twenty years.

How Not to Solve the Problem

One approach (already taken by some VME suppliers) has been to simply cease building or supporting VME-to-PCI adapter boards, forcing their customers to find support elsewhere.

An alternative but still unappealing solution would be for VME system suppliers to scour various sources, attempting to buy up scarce (and expensive) TSI148 inventories. This strategy would enable ongoing customer support but at a high cost and above all, an uncertain future. Scarcity also translates to long lead times and a high risk of VME-to-PCI adapter board EOL happening sooner rather than later. After all, once chip inventory is exhausted the original problem simply rears its head again.

What’s Required for a Long Term Solution

We’ve already observed that both commercial and military VME users will continue to require long term VME legacy support for another one or two decades, whether the reason is contractual, economic, or both. Customers lacking internal design engineering resources to implement a long-term fix to the TSI148 problem are likely to demand that their VME suppliers to solve this and other EOL problems as they arise.

AIT remains committed to supporting the VME market for the long term. In tangible terms, this entails fulfilling three fundamental requirements:

  • A means to supply VME-to-PCI bridge capability absent the TSI148 chip.
  • Continuing to supply compatible hardware in terms of form, fit, and function for various manifestations of VME test and simulation systems, including:
  • Laboratory use
  • Extended temperature use
  • Conduction-cooled systems
  • Providing ongoing software support such a porting customer apps to APIs, as well as developing new general software tools that include VME functionality.

But unless AIT achieves VME-to-PCI bridge functionality in the absence of the TSI148 chip, all the other requirements become moot.

Solving the TSI148 Bridge Chip Problem

AIT has redesigned its VME 1553 and 429 adapter boards to use a Xilinx FPGA that incorporates AIT-developed and owned intellectual property (IP). This hardware and firmware—the “FPGA solution”—resolves the adapter EOL issue by eliminating the TSI148.*

AIT’s practical solution is not a gauzy promise of a future product development. The FPGA solution proves our long-term commitment to 1553 and 429 VME test and simulation systems—exactly what’s needed for VME users to continue to rely on their VME investment.

We’ll discuss the how AIT’s VME-to-PCI solution is an example of AIT’s long term commitment to VME in our next blog post.

* Of course one could argue that Xlinx could discontinue supplying its FPGA. However, given its widespread use in thousands of applications, we this EOL risk is diminishingly small. In any event, since AIT owns the IP, it could easily port the firmware to an alternative device.

Topics: MIL-STD-1553, ARINC 429, VME

Avionics Network Technologies

From legacy shared busses to multi-gigabit networks

From MIL-STD-1553 and ARINC 429 to Avionics Ethernet and Fibre Channel ... we've go you covered. Whether your building lab test & simulation systems, designing flight test data acquisition systems, or integrating on aircraft avionics networks we are here to provide hardware and software solutions to lower your project's budget & risks.

We are experts in: 

We provide hardware, software, and most importantly expertise to support

Subscribe to Email Updates

Recent Posts