With the rapid development of computer technology, the instrument industry affected by it has also undergone tremendous changes, that is, the manual operation of instruments has been changed to computer-controlled automatic testing. With the development of automatic testing technology and program-controlled instruments, in addition to the standardization of physical hardware interfaces, software control standardization is also required. In terms of hardware, since the concept of automatic testing was established in the 1950s, after the initial dedicated interfaces and semi-dedicated interfaces, it was not until the mid-1980s that open standard interface buses were popularized, such as RS232 serial communication interface bus, GPIB general interface bus, PXI computer peripheral instrument system bus, VXI block instrument system bus, etc. In terms of software, the IEEE488.2 (Programmable Instrument Message Exchange Protocol) standard promulgated in June 1987 first solved the problem of data structure, but still left a large amount of device semantics to the designer to define freely. In April 1990, nine international instrument companies proposed SCPI (Standard Commands for Programmable Instruments) based on IEEE488.2, which standardized the device data and commands of programmable instruments. The overall goal of SCPI is to shorten the program development time of the automatic test system, protect the hardware and software investment of both instrument manufacturers and users, and provide a widely compatible coding environment for instrument control and data utilization. After receiving the SCPI message, the instrument responds: receiving string messages, lexical analysis, syntax analysis, intermediate code generation, optimization and target code generation. The performance of the syntax analysis module directly affects the efficiency of program control execution. In order to further simplify the syntax analysis module in the instrument and improve the efficiency of program control execution, this topic proposes the idea of adding a parsing module to the interface circuit, which can convert the SCPI message sent by the controller to the instrument, that is, the complex ASCII code string, into a simple binary code. The use of this parsing module will greatly simplify the software work of the instrument designer, which can not only realize the standardization of the instrument language but also improve the response speed of the instrument to remote control, which will be very useful when studying homemade instruments in the laboratory. There are many types of instrument interfaces. This topic mainly discusses the two interfaces of RS232 and GPIB. In this design, the instrument interface board is independent of the instrument and uses a separate microprocessor with the instrument. To connect to the instrument and realize communication, it is only necessary to communicate between the two microprocessors. The purpose of this is: on the one hand, it does not affect the design and operation of the instrument, and on the other hand, it can realize the versatility of the interface board and the interchangeability of the instrument. As the RS232 interface is a simple interface, I first focus on software design, mainly considering how to parse complex ASCII code strings into simple binary codes. As for the GPIB interface, the main part of the software design has been completed, and then the focus of work is placed on hardware design, using the more cost-effective CPID to implement the GPIB interface chip NAT9914. In order to observe the analysis results, an LCD display is also added. This design has made a beneficial attempt in the development of a universal and low-cost instrument interface board, laying the foundation for further research on automatic test systems. Keywords: instrument; SCPI; RS232 interface; GPIB interface; CPLD
You Might Like
Recommended ContentMore
Open source project More
Popular Components
Searched by Users
Just Take a LookMore
Trending Downloads
Trending ArticlesMore