Editing Automatic test equipment (section)

==Test equipment platforms==
Several modular electronic instrumentation platforms are currently in common use for configuring automated electronic test and measurement systems. These systems are widely employed for incoming inspection, quality assurance, and production testing of electronic devices and subassemblies. Industry-standard communication interfaces link signal sources with measurement instruments in "[[19-inch rack|rack-and-stack]]" or chassis-/mainframe-based systems, often under the control of a custom software application running on an external PC.

===GPIB/IEEE-488===
The General Purpose Interface Bus ([[GPIB]]) is an IEEE-488 (a standard created by the [[Institute of Electrical and Electronics Engineers]]) standard parallel interface used for attaching sensors and programmable instruments to a computer. GPIB is a digital 8-bit parallel communications interface capable of achieving data transfers of more than 8&nbsp;MB/s. It allows daisy-chaining up to 14 instruments to a system controller using a 24-pin connector. It is one of the most common I/O interfaces present in instruments and is designed specifically for instrument control applications. The IEEE-488 specifications standardized this bus and defined its electrical, mechanical, and functional specifications, while also defining its basic software communication rules. GPIB works best for applications in industrial settings that require a rugged connection for instrument control.

The original GPIB standard was developed in the late 1960s by Hewlett-Packard to connect and control the programmable instruments the company manufactured. The introduction of digital controllers and programmable test equipment created a need for a standard, high-speed interface for communication between instruments and controllers from various vendors. In 1975, the IEEE published ANSI/IEEE Standard 488-1975, IEEE Standard Digital Interface for Programmable Instrumentation, which contained the electrical, mechanical, and functional specifications of an interfacing system. This standard was subsequently revised in 1978 (IEEE-488.1) and 1990 (IEEE-488.2). The IEEE 488.2 specification includes the Standard Commands for Programmable Instrumentation (SCPI), which define specific commands that each instrument class must obey. SCPI ensures compatibility and configurability among these instruments.

The IEEE-488 bus has long been popular because it is simple to use and takes advantage of a large selection of programmable instruments and stimuli. Large systems, however, have the following limitations:

*'''Driver fanout''' capacity limits the system to 14 devices plus a controller.
*'''Cable length''' limits the controller-device distance to two meters per device or 20 meters total, whichever is less. This imposes transmission problems on systems spread out in a room or on systems that require remote measurements.
*'''Primary addresses''' limit the system to 30 devices with primary addresses. Modern instruments rarely use secondary addresses so this puts a 30 device limit on system size.<ref>ICS Electronics. [http://www.icselect.com/pdfs/ab48_12.pdf Extending the GPIB Bus] Retrieved December 29, 2009.</ref>

===LAN eXtensions for Instrumentation (LXI)===
The [[LAN eXtensions for Instrumentation|LXI]] Standard defines the communication protocols for instrumentation and data acquisition systems using Ethernet. These systems are based on small, modular instruments, using low-cost, open-standard LAN (Ethernet). LXI-compliant instruments offer the size and integration advantages of modular instruments without the cost and form factor constraints of card-cage architectures. Through the use of Ethernet communications, the LXI Standard allows for flexible packaging, high-speed I/O, and standardized use of LAN connectivity in a broad range of commercial, industrial, aerospace, and military applications. Every LXI-compliant instrument includes an Interchangeable Virtual Instrument (IVI) driver to simplify communication with non-LXI instruments, so LXI-compliant devices can communicate with devices that are not themselves LXI compliant (i.e., instruments that employ GPIB, VXI, PXI, etc.). This simplifies building and operating hybrid configurations of instruments.

LXI instruments sometimes employ scripting using embedded test script processors for configuring test and measurement applications. Script-based instruments provide architectural flexibility, improved performance, and lower cost for many applications. Scripting enhances the benefits of LXI instruments, and LXI offers features that both enable and enhance scripting. Although the current LXI standards for instrumentation do not require that instruments be programmable or implement scripting, several features in the LXI specification anticipate programmable instruments and provide useful functionality that enhances scripting's capabilities on LXI-compliant instruments.<ref>Franklin, Paul and Todd A. Hayes. LXI Connection.[https://web.archive.org/web/20110714005908/http://www.lxiconnexion.com/articles/0708/0708_scripting.pdf Benefits of LXI and Scripting.] July 2008. Retrieved January 5, 2010.</ref>

===VME eXtensions for Instrumentation (VXI)===
The [[VXI]] bus architecture is an open standard platform for automated test based on the [[VMEbus]]. Introduced in 1987, VXI uses all Eurocard form factors and adds trigger lines, a local bus, and other functions suited for measurement applications. VXI systems are based on a mainframe or chassis with up to 13 slots into which various VXI instrument modules can be installed.<ref>[http://www.interfacebus.com/Equipment_VXI_Chassis_Manufacturers.html Hardware Mechanical Components VXI Chassis and Case Manufacturers]. Retrieved December 30, 2009.</ref> The chassis also provides all the power supply and cooling requirements for the chassis and the instruments it contains. VXI bus modules are typically [[Rack unit|6U]] in height.

===PCI eXtensions for Instrumentation (PXI)===
[[PXI]] is a peripheral bus specialized for data acquisition and real-time control systems. Introduced in 1997, PXI uses the CompactPCI [[Rack unit|3U]] and [[Rack unit|6U]] form factors and adds trigger lines, a local bus, and other functions suited for measurement applications. PXI hardware and software specifications are developed and maintained by the PXI Systems Alliance.<ref>PXI Systems Alliance. [http://www.pxisa.org/Specifications/Default.aspx Specifications]. Retrieved December 30, 2009.</ref> More than 50 manufacturers around the world produce PXI hardware.<ref>PXI Systems Alliance. [http://www.pxisa.org/Member_Roster.html Member Roster] {{webarchive|url=https://web.archive.org/web/20100905170530/http://www.pxisa.org/Member_Roster.html |date=2010-09-05 }} Retrieved December 30, 2009.</ref>

===Universal Serial Bus (USB)===
[[USB]] connects peripheral devices, such as keyboards and mice, to PCs. USB is a [[Plug & Play|Plug and Play]] bus that can handle up to 127 devices on one port, and has a theoretical maximum throughput of 480&nbsp;Mbit/s (high-speed USB defined by the USB 2.0 specification). Because USB ports are standard features of PCs, they are a natural evolution of conventional serial port technology. However, it is not widely used in building industrial test and measurement systems for a number of reasons; for example, USB cables are not industrial grade, are noise sensitive, can accidentally become detached, and the maximum distance between the controller and the device is 30&nbsp;m. Like [[RS-232]], USB is useful for applications in a laboratory setting that do not require a rugged bus connection.

===RS-232===
RS-232 is a specification for serial communication that is popular in analytical and scientific instruments, as well for controlling peripherals such as printers. Unlike GPIB, with the RS-232 interface, it is possible to connect and control only one device at a time. RS-232 is also a relatively slow interface with typical data rates of less than 20&nbsp;KB/s. RS-232 is best suited for laboratory applications compatible with a slower, less rugged connection. It works on a ±24&nbsp;volt supply.

=== Boundary scan===
[[Boundary scan]] can be implemented as a PCB-level or system-level interface bus for the purpose of controlling the pins of an IC and facilitating continuity (interconnection) tests on a test target (UUT) and also functional cluster tests on logic devices or groups of devices. It can also be used as a controlling interface for other instrumentation that can be embedded into the ICs themselves (see IEEE 1687) or instruments that are part of an external controllable test system.

===Test script processors and a channel expansion bus===
One of the most recently developed test system platforms employs instrumentation equipped with onboard test script processors combined with a high-speed bus. In this approach, one "master" instrument runs a test script (a small program) that controls the operation of the various "slave" instruments in the test system, to which it is linked via a high-speed LAN-based trigger synchronization and inter-unit communication bus. Scripting is writing programs in a scripting language to coordinate a sequence of actions.

This approach is optimized for small message transfers that are characteristic of test and measurement applications. With very little network overhead and a 100&nbsp;Mbit/sec data rate, it is significantly faster than GPIB and 100BaseT Ethernet in real applications.

The advantage of this platform is that all connected instruments behave as one tightly integrated multi-channel system, so users can scale their test system to fit their required channel counts cost-effectively. A system configured on this type of platform can stand alone as a complete measurement and automation solution, with the master unit controlling sourcing, measuring, pass/fail decisions, test sequence flow control, binning, and the component handler or prober. Support for dedicated trigger lines means that synchronous operations between multiple instruments equipped with onboard Test Script Processors that are linked by this high speed bus can be achieved without the need for additional trigger connections.<ref>Cigoy, Dale. R&D Magazine.[http://www.rdmag.com/Featured-Articles/2007/02/Smart-Instruments-Keep-Up-with-Changing-R-D-Needs/ Smart Instruments Keep Up With Changing RD Needs] Retrieved January 4, 2009.</ref>