General purpose interface bus (GPIB) sniffer system and method

A sniffer bus-based network General Purpose Interface Bus (GPIB) module includes two functional units. One is Data Acquisition Unit (DAU) module, and the other one is Data Processing Unit (DPU) module. The DPU is configured to receive data from the (DAU) module and converting the data by time-stamping and a host server configured to receive JSON format data via a communication network. Further, captured data is transferred to the cloud for big data analysis to obtain the specifics of equipment utilization and evaluate the overall efficiency of the test system.

CROSS-REFERENCE TO RELATED APPLICATION

This application claims priority to and the benefit of Malaysian Patent Application No. PI 2017704741 filed Dec. 8, 2017, the entire disclosure of which is hereby incorporated by reference.

TECHNICAL FIELD

Embodiments of the present invention pertains to system and method relates to General Purpose Interface Bus (GPIB) which captures and displays captures traffic on the GPIB bus. The present invention relates to software diagnostic tools for monitoring and displaying events made to driver software by two of its main units Data Acquiring Unit and Data Processing Unit.

BACKGROUND

Traditionally, various methods for measuring instruments connected onto a GPIB bus. For integrating and designing a system of test instruments for performing a number of tests and measurements on a device under test (DUT), it is important to insure that operations of the test instruments are properly timed and coordinated to insure that the test operations perform as expected.

The GPIB, otherwise referred to as the Institute of Electrical and Electronic Engineers IEEE-488 interface bus, is designed for remote control of programmable instruments. The IEEE 488 bus, also referred to as the General Purpose Interface Bus (GPIB), is used for connecting instruments and controllers to a common bus to perform various test and measurement functions. A typical GPIB system comprises one or more GPIB instruments up to 14 instruments, and a controller, typically a GPIB interface board installed in a general purpose computer, connected by standard GPIB cables. A GPIB software application executes on the computer to control the instruments. The GPIB application interfaces through GPIB driver level software to the GPIB controller. In response to the GPIB application, the controller provides program commands to the instruments, and the instruments return formatted data and response messages to the controller. GPIB instruments are message-based devices which are programmed with high-level ASCII character strings. A respective GPIB device includes a local processor that parses the command strings and sets the appropriate register bits to perform the indicated functions.

Big data analytics is a relatively new approach to managing large amounts of data. As used herein, the term “big data” is used to describe unstructured and semi-structured data in such large volumes (for example, petabytes or exabytes of data) as to be immensely cumbersome to load into a relational database for analysis. The GPIB devices can be listeners, talkers and/or controllers. A talker sends data messages to one or more listeners, which receive the data. The controller manages the flow of information on the GPIB by sending commands to all devices. Some devices may perform several functions, such as a digital volt meter which acts as a talker by sending voltage information on the GPIB and as a listener when receiving configuration and control information. Usually, there is only one controller for a given GPIB where multiple GPIB devices are further coupled to the GPIB for receiving command information from the controller for interfacing the other GPIB devices.

Conventionally, it is noted that some GPIB configurations do not require a controller if only one device would be considered a talker and the remaining devices are listen-only devices. A controller is necessary when the active or addressed talker or listener must be changed or reconfigured where such control functions are usually handled by a computer device. Also, there may be multiple controllers on a given GPIB, although only one controller is the controller-in-charge (CIC) at any given time.

Moreover, for a test system managed via the GPIB bus, various test and measurement instruments are connected to the bus as GPIB devices. A computer with the corresponding test application software is also connected to the bus which acts as the GPIB bus controller. However, there remains a need in the art to provide a system and method to connect to the GPIB bus which is able to capture events on the bus without interrupting existing operation of the test system.

In the current era PCI or PCI Express boards are available. However, PC with PCI slot or PCI Express slot is required to plug in those boards. The cost of the PC plus the board is quite high and the PC plus the board take up a large space during deployment. Generally, the GPIB traffic captured by the board is shown locally on the PC monitor to the user and there is no easy way to transfer the data to the cloud. The main use of the board is to troubleshoot and solve GPIB hardware and software problems, and the PC plus the board is not used for collecting data for big data analysis.

U.S. patent application Ser. No. 08/473,110, filed on Jun. 7, 1995, entitled “GPIB System for Capturing GPIB Signals at a Predetermined Rate and Upon Transitions of the Data Valid Signal”; U.S. patent application Ser. No. 08/473,200, filed on Jun. 7, 1995, entitled “GPIB System Including Real Time Time-stamp”; U.S. patent application Ser. No. 08/472,967 filed on Jun. 7, 1995, entitled “GPIB System Including Deglitch Method and Apparatus to Assure Valid Data Sampling”; and U.S. patent application Ser. No. 08/472,626, filed on Jun. 7, 1995, entitled “GPIB System with Improved Parallel Poll Response Detection”. All of the applications are assigned to the same assignee.

Accordingly, there remains a need in the prior art to develop a General Purpose Interface Bus (GPIB) sniffer system and method. The present invention provides a system where the data captured by the system is communicated to the cloud for big data analysis to obtain the specifics of equipment utilization and evaluate the overall efficiency of one or more test systems.

SUMMARY

The present invention is a GPIB Sniffer which is connected to the test system and captures events from the test system without interrupting existing operation of the test system. Particularly, the test system consist of GPIB Controller and different types of GPIB devices. For example, GPIB devices may be any one of test and measurement equipments, and instruments like power supplies, multimeters, oscilloscopes and the like.

Embodiments of the present disclosure relates to system and methods connected in a bus-based network, a General Purpose Interface Bus (GPIB) sniffer consisting of Data Acquisition Unit (DAU) module, a Data Processing Unit (DPU) module. Particularly, the General Purpose Interface Bus (GPIB) module is configured to transmit and receive data in a General Purpose Interface Bus (GPIB) format. The Data Acquisition Unit (DAU) module is configured to capture data traffic on a General Purpose Interface Bus (GPIB) bus, and the Data Processing Unit (DPU) module is configured to receive data from the Data Acquisition Unit (DAU) module and convert the data by time-stamping in a JavaScript Object Notation (JSON) format. Further, the host server is configured to receive JSON format data via a communication network.

In one and more embodiments of present invention, the Data Acquisition Unit (DAU) module is configured to capture traffic without participating in General Purpose Interface Bus (GPIB) handshake mechanism and appearing “transparent” to all other GPIB devices on the bus.

In particular DPU receives data from DAU and data is processed and formatted before being transmitted to the server on the network via LAN cable. Moreover, DPU establishes a secure communication channel with the server for transmission of data. Furthermore, the server is listening on certain port number(s).

Embodiments of the present disclosure relates to a method for analyzing data in a test system by one or more communication connections. Particularly, the method includes the steps of transmitting and receiving data in a General Purpose Interface Bus (GPIB) format, capturing data traffic on a General Purpose Interface Bus (GPIB) bus, receiving data and converting the data to generate time-stamped data executed by the Data Processing Unit (DPU) module, and communicating the time-stamped data to a host server, and processing the time-stamped data to output information about timing of the data stored.

The Data Acquisition Unit (DAU) module of General Purpose Interface Bus (GPIB) system includes a General Purpose Interface Bus (GPIB) transceiver providing the electrical compatibility between DAU and GPIB Bus. The GPIB Transceiver is designed to meet the requirements of IEEE Standard 488.1.

Particularly, the data acquisition Unit (DAU) module is configured to capture traffic without participating in General Purpose Interface Bus (GPIB) handshake mechanism.

The Data Processing Unit (DPU) module of General Purpose Interface Bus (GPIB) sniffer includes a Central Computing Unit which extracts information and constructing messages in the JSON format timestamping the messages and delivering them to the JSON server on the network. In particular, a Real-time Clock (RTC) for timestamping the JSON messages and keeping track record, and battery backup protecting the Central Computing Unit (CCU) from system and data corruption during unplanned power outage.

Moreover, Data DPU has a visual display for displaying status information of the DPU to the users, a keypad enabling the users to control the DPU locally and a interconnect board providing means for connecting the RTC, the backup battery, the visual display, the keypad and the power supply to the central computing module.

The data captured by the GPIB Sniffer is then transferred to the cloud for big data analysis to obtain the specifics of equipment utilization and evaluate the overall efficiency of the test system.

DETAILED DESCRIPTION

Various embodiments of the present invention provide systems, and methods to connect to the General Purpose Interface Bus (GPIB) test system and captures events on the bus without interrupting existing operation of a test system. The data captured by the present system are transferred to the cloud for big data analysis to obtain the specifics of equipment utilization and evaluate the overall efficiency of the test system. The present invention provide systems to connect to the GPIB Bus and captures events on the bus without interrupting existing operation of the test system. Moreover, the principles of the present invention and their advantages are best understood by referring toFIG. 1toFIG. 7.

In the following detailed description of illustrative or exemplary embodiments of the disclosure, specific embodiments in which the disclosure may be practiced are described in sufficient detail to enable those skilled in the art to practice the disclosed embodiments. For example, specific details such as specific method steps, structures, elements, and connections are presented herein. However, it is to be understood that the specific details presented need not be utilized to practice the embodiments of the present disclosure.

The following detailed description is, therefore, not to be taken in a limiting sense, and the scope of the present disclosure is defined by the appended claims and equivalents thereof.

FIG. 1illustrates a block diagram of schematic configuration of General Purpose Interface Bus (GPIB) sniffer in accordance with an embodiment of the present invention. A General Purpose Interface Bus (GPIB) sniffer system100which is a bus-based network including a Data Acquisition Unit (DAU) module115configured to capture data traffic on a General Purpose Interface Bus (GPIB) bus. Particularly, Data Processing Unit (DPU) module120is configured to receive data from the Data Acquisition Unit (DAU) module115and convert the data by time-stamping in a prescribed format. Moreover, it has a host server125configured to receive the prescribed format data via a communication network130.

In some implementations, the host server125can communicate wirelessly through a communication interface (not shown), which may include digital signal processing circuitry where necessary. The communication interface can provide for status information of the firmware developed for the sniffer system under various modes or protocols, AM signal, an FM signal, a phase modulated signal, CDMA, TDMA, spread spectrum, the Internet, a WiFi connection, a Bluetooth connection, a Zigbee connection, a network, a wireless network, a 3G network, a 4G network, a USB connection, or any combination thereof.

In another embodiment the communication interface can provide for status information of the firmware developed for the sniffer system under various modes or protocols using the wireless device via the Internet, a WiFi connection, a network, a wireless network, a USB connection, or any combination thereof.

In another embodiment the communication interface can provide status information of the firmware developed for the sniffer system under various modes or protocols based on FM signal, a phase modulated signal, CDMA, TDMA, spread spectrum, the Internet, a WiFi connection, a Bluetooth connection, a Zigbee connection, a network, a wireless network, a 3G network, a 4G network, a USB connection, or any combination thereof. In addition, short-range communication may occur, such as using a Bluetooth, WiFi, or other such transceiver. In some implementations, the system100can be a distributed client/server system that spans one or more networks such as the network130. The network130can be a large computer network, such as a local area network (LAN), wide area network (WAN), the Internet, a cellular network, or a combination thereof connecting any number of mobile clients, fixed clients, and servers.

In some implementations, each client (e.g., computing devices not shown) can communicate with server125via a virtual private network (VPN), Secure Shell (SSH) tunnel, or other secure network connection. In some implementations, the network130can further include a corporate network (e.g., internet) and one or more wireless access points.

FIG. 2illustrates a block diagram200of schematic configuration of two main functional units of the General Purpose Interface Bus sniffer Data Acquisition Unit (DAU) module and Data Processing Unit (DPU) module, in accordance with an embodiment of the present invention. Particularly, the two main functional units of the sniffer system100are the Data Acquisition Unit (DAU) module115and Data Processing Unit (DPU) module120. Particularly, the General Purpose Interface Bus (GPIB) module105is configured to transmit and receive data in a General Purpose Interface Bus (GPIB) format. The Data Acquisition Unit (DAU) module115is configured to capture data traffic on a General Purpose Interface Bus (GPIB) bus105.

Particularly, the Data Processing Unit (DPU) module120is configured to receive data from the Data Acquisition Unit (DAU) module115and convert the data by time-stamping in a JSON format. In operation, the host server125is configured to receive JSON format data via a communication network130. Moreover, the Data Acquisition Unit (DAU) module115is configured to capture traffic without participating in General Purpose Interface Bus (GPIB) handshake mechanism. To capture traffic on the GPIB bus the DAU appears to be “transparent” to other GPIB devices on the bus.

FIG. 3illustrates a block diagram of schematic configuration of Data Acquisition Unit (DAU) module115. module120in accordance with an embodiment of the present invention. The Data Acquisition Unit (DAU) module115of General Purpose Interface Bus (GPIB) sniffer system100includes a General Purpose Interface Bus (GPIB) transceiver340, operably configured to provide an electrical compatibility between Data Acquisition Unit (DAU) module115and General Purpose Interface Bus (GPIB). Particularly, the Data Acquisition Unit (DAU) module115also has latching circuitry345configured to latch a data signal.

Moreover, a data input receives the data signal by Microcontroller (MCU)350retrieving the data signal state captured by the latching circuitry345. Furthermore, a universal serial bus (USB) interface355is configured to be coupled to the Microcontroller (MCU)350for transferring the data signal to the Data Processing Unit (DPU) module120. Particularly, the Data Acquisition Unit (DAU) module115is configured to capture data traffic without participating in General Purpose Interface Bus (GPIB) handshake mechanism.

FIG. 4illustrates a block diagram of schematic configuration of Data Processing Unit (DPU) module115. The Data Processing Unit (DPU) module120of General Purpose Interface Bus (GPIB) sniffer system100includes a central computing module405having an instruction for constructing messages. Particularly, the Data Processing Unit (DPU) module120establish a secure communication channel with the host server125for data transmission. The host server125is configured on certain port numbers.

Moreover, the Data Processing Unit (DPU) module120has a Real-time Clock (RTC)420configured to provide time-stamping of the prescribed format data and provide system time for keeping track record of prescribed format data. Furthermore, battery backup module425is configured to protect the central computing module405from data corruption during unplanned power outage. The central computing module405of DPU120extracts data captured by Data Acquisition Unit (DAU) module115such as Talker and Listeners and timestamp the data and convert the data into JSON message format and deliver the data to a JSON server125. Subsequently, a visual display interface is configured to display status information of the Data Processing Unit (DPU)120to one or more users and a keypad input configured to enable multiple users to control the Data Processing Unit (DPU) module120. Further, to develop a firmware for displaying status information from the DPU120, the present system enables users to remotely control the DPU120through a network130tighten the security of DPU120, including encrypting the data sent via network130.

FIG. 5illustrates a flow diagram illustrating method for analyzing data in a General Purpose Interface Bus (GPIB) sniffer system100by one or more communication connections for in accordance with one or more embodiment of the present invention. The method500for analyzing data analyzing data in a General Purpose Interface Bus (GPIB) sniffer system100by one or more communication connections starts at step505. At step505, the method500includes the step of transmitting and receiving data in the General Purpose Interface Bus (GPIB) format. The method500proceeds to step510. At step510, data traffic on the General Purpose Interface Bus (GPIB) bus105is captured for processing to data units.

The method500proceeds to step515. At step515, the data received is converted to generate time-stamped data executed by the Data Processing Unit (DPU) module115. The method500proceeds to step520. At step520, the time-stamped data is communicated to the host server125. The method500proceeds to step525. At step525, the time-stamped data is processed to output information about timing of the data stored.

In one or more embodiment in accordance with the present generation, the time-stamping of the data is in JSON format.

In another embodiment, the method500further include the step of developing a firmware for displaying status information of the sniffer system100.

In yet another embodiment, of the present invention, the method500further includes the steps of remotely controlling the sniffer system100by at least one client device (not shown).

In yet another embodiment, the data are events on at least one of the GPIB bus. In operation to tighten the security of data transmitted by DAU115, the data is encrypted by DPU module120. Particularly, the data encrypted is communicated via the computer network130. Accordingly, the data captured by the present invention is transferred to the cloud for big data analysis to obtain the specifics of equipment utilization and evaluate the overall efficiency of the test system. Moreover, the present invention is developed as a standalone equipment, and a personal computer is not needed for its operation. Further, the events captured from the GPIB bus are timestamped and sent to the cloud automatically. Further, the present invention provides a low cost solution and the present invention is small in size.

FIG. 6illustrates a flow diagram illustrating steps for analyzing data by the Data Acquisition Unit (DAU) module115of General Purpose Interface Bus (GPIB) sniffer system100. The method600for analyzing data by the Data Acquisition Unit (DAU) module115of General Purpose Interface Bus (GPIB) sniffer system100is configured to execute a set of instructions. At step605, the method600includes the step of transmitting and receiving data in the General Purpose Interface Bus (GPIB) format. At step605, electrical compatibility is provided between the Data Acquisition Unit (DAU) module115and the General Purpose Interface Bus (GPIB).

The method600proceeds to step610. At step610, the data signal is latched and received by data input. The method600then proceeds to step615. At step615, the data signals are retrieved and captured by the latching circuitry345.

The method600then proceeds to step620. At step620, data signal are transferred to the Data Processing Unit (DPU) module120via the universal serial bus (USB) interface355. Particularly, the universal serial bus (USB) interface355is configured to be coupled to the Microcontroller (MCU)350for transferring the data signal to the Data Processing Unit (DPU) module120.

FIG. 7illustrates a flow diagram illustrating steps for analyzing data by the Data Processing Unit (DPU) module120of General Purpose Interface Bus (GPIB) sniffer system100. The method700for analyzing data by the Data Processing Unit (DPU) module120of the General Purpose Interface Bus (GPIB) sniffer system100is configured to execute a set of instructions. The method700starts at step705. At step705, the Data Processing Unit (DPU) module120constructs one or more messages based on data signal received from the Data Acquisition Unit (DAU) module115.

The method700proceeds to step710. At step710, the data is time stamped in a prescribed format and method700also provides the system100the time for keeping track record of the prescribed format data.

In one embodiment, the prescribed format data is a JSON format data structure.

The method700then proceeds to step715. At step715, status information is displayed by the Data Processing Unit (DPU) module120to one or more users. The method700then proceeds to step720. At step720, one or more users are enabled to control the Data Processing Unit (DPU) module120.

Therefore, as may be seen, various embodiments of the present invention, as herein described above, provide need for developing the method and system of capturing the events without disturbing the ongoing events. The present technology of capturing events on the General Purpose Interface Bus (GPIB) sniffer system without interrupting existing operation of the system of the GPIB Bus. The present invention illustrates a new and complete way for capturing and processing data by the General Purpose Interface Bus (GPIB) sniffer without participating in handshake mechanism then transferring to cloud for big data analysis. The present invention of General Purpose Interface Bus (GPIB) sniffer provides a system and method to efficiently utilize equipment and evaluate the overall efficiency of the test system as a standalone equipment.