|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| home |
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| articles > | Overcoming obsolescence |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Replacement of legacy instruments with PXI modules without software changes
With new PXI modules introduced to the market in growing numbers, the replacement of the legacy instruments is available without the modification of the legacy TPSs or their software drivers. Legacy test and measurement instruments face end-of-life problems, lack of replacement parts, and require on going maintenance and calibration. In most cases, said instruments reside in three-bay Automatic Test Equipment (ATE) that occupies significant floor space. Their dimensions and technical conditions require valuable storage space and cause countless project delays.The replacement of these instruments with PXI based modules requires modifications and revalidation of old Test Programs Sets (TPS), which have been developed under old programming languages such as HP-Basic, Assembly, FORTRAN, and ATLAS. Changes to these software applications can be impractical due to the magnitude (budget and schedule) of such an effort. Until recently, said replacement was almost impossible from a technical aspect, due to the lack of modules with similar hardware capabilities, such as high density switching or high frequency RF modules.
Current status description
Technology description Since the technology does not affect the source code, it does not require its availability. This is a very important feature for classified military projects that cannot expose their source code. Figure 1 illustrates a traditional tester in which an old instrument is connected to a CPU through GPIB bus.
In Figure 2, the new instrument is a PXI chassis with modules that are able to perform and provide the same functions as the old instrument. The old CPU still sends and receives the same commands as it did in the past. The communication between the CPU controller and the instruments translator/emulator module is done via the existing GPIB bus and the communication between the translator/emulator and the PXI modules by utilizing a TCP/IP protocol. Each command and/or address sent by the CPU controller is analyzed and translated in real-time in to one or more commands of the new PXI modules that is connected to the bus. The new instrument’s reply is treated in the same way.
It is important to mention that TCP/IP is mentioned as one option among several. In other words, the communication can be USB, LXI, or any other communication type. The number of instruments supported by one instrument translator/emulator module is limited only by the number of PXI slots. If required, a second PXI chassis can be added to provide more modules. As more and more chassis are added, it is easy to convert a three-bay ATE to one- or half-bay ATE that can host the 1U instrument translator/emulator and several PXI chasses. Figure 3 shows 2 x PXI chassis with the following main modules:
The instrument translator/emulator is installed under the monitor (on top of the PXI chassis) and takes only 1U of space. A Virginia Panel interface serves as new interfaces for the UUT (Unit Under Test)
The original ATE is three-bay in size and is used for radio testing by the US Navy. As the presented technical solution deals with the communication level only (GPIB or others), it is not required to have the TPS source code available, and the programming language of the TPS does not affect this technical solution.
As mentioned before, the PXI based solution can be combined with rack-mounted instruments. In Figure 4, the instrument translator/emulator communicates with both PXI based instruments and GPIB rack-mounted instruments. The GPIB addresses of the old instruments are mapped in such a way that the instrument translator/emulator knows if it is a TCP/IP (PXI) instrument or GPIB (rack mount) instruments. As the instrument translator/emulator will need to load new emulators/translator along the life of the refurbished ATE, a web server was added for loading new instruments. This server is also used in cases that undocumented commands discovered during the execution of new TPS (which have not been run yet on the upgraded ATE).
Additionally, the instrument translator/emulator can support those cases in which instrument manufacturers released new instruments with a built in emulation module. While testing several instruments, we discovered the following problems:
The technology described herein has built in tools that handle these and other integration problems. Its tracing tool can collect and analyze the protocol low-level commands in both directions, and the web server capability enables remote support. An internal utility can provide the configuration of all the instruments that are attached to the instrument translator/emulator module, as this information is provided by the instrument manufacturer. This information is accessible via the internet. ITAs (Interface Test Adapters) and custom-made instruments have the most complex replacement objectives. The new device often needs to preserve the old signals and their characteristics. Again, in this situation, the instrument translator/emulator provides a replacement alternative. Figure 5 shows a one-bay PXI based ATE in its final configuration. The instrument translator/emulator is hidden and at least half of the rack is empty and ready for future expansion. New TPSs are written in LabVIEW and the old TPS remains untouched.
Figure 6 shows a mobile rack in which two rack-mount legacy instruments, DMM and counter from Racal-Dana, are being replaced with two PXI modules. Although the size of the PXI chassis is identical to these two instruments, most of the chassis is empty and may host 16 more PXI modules. The old DMM and counter were left in the rack for demonstration purpose only. In real life they are not required for the ATE functionality.
Conclusions
The cost associated with this technology is significantly lower than with existing methods by which the software or driver is rewritten and then revalidated. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||