Measurement module interface protocol database and registration system Number:7,165,005 from the United States Patent and Trademark Office (PTO) owispatent System and method for providing a measurement module (MM) interface for configuring a measurement system. The method includes creating a MM and one or more MM interface programs implementing respective MM interface protocols (MMIP) for the measurement module. An MMIP server is accessed and the MM registered with the MMIP server. The MM interface programs are stored on the MMIP server, where they are each downloadable from the MMIP server and usable to program a functional unit on a carrier unit, enabling the carrier unit to communicate with the MM in accordance with the respective MMIP. A MM is installed in the measurement system and provides ID to a carrier unit of the system. The MMIP server is accessed and, based on the ID, payment information, etc., a MM interface program is downloaded and used to configure the carrier unit to enable communication with the MM in performing a task.<H registration, Measurement, Measurement, mod, 7165005.html, Patent, pto, 7165005

Title: Measurement module interface protocol database and registration system

Abstract: System and method for providing a measurement module (MM) interface for configuring a measurement system. The method includes creating a MM and one or more MM interface programs implementing respective MM interface protocols (MMIP) for the measurement module. An MMIP server is accessed and the MM registered with the MMIP server. The MM interface programs are stored on the MMIP server, where they are each downloadable from the MMIP server and usable to program a functional unit on a carrier unit, enabling the carrier unit to communicate with the MM in accordance with the respective MMIP. A MM is installed in the measurement system and provides ID to a carrier unit of the system. The MMIP server is accessed and, based on the ID, payment information, etc., a MM interface program is downloaded and used to configure the carrier unit to enable communication with the MM in performing a task.

Patent Number: 7,165,005 Issued on 01/16/2007 to Steger, et al.

Inventors: Steger; Perry (Georgetown, TX), Foote; Garritt W. (Austin, TX), Potter; David (Austin, TX), Truchard; James J. (Austin, TX)
Assignee: National Instruments Corporation (Austin, TX)

Appl. No.: 10/194,927

Filed: July 12, 2002

Current U.S. Class: 702/120 ; 702/127; 702/188; 710/100; 717/124; 717/149

Current International Class: G06F 3/00 (20060101)

Field of Search: 702/127,188,120 709/223,224,204,200 710/100 370/254 717/124,149 714/39

References Cited [Referenced By]

U.S. Patent Documents


6073160	June 2000	Grantham et al.
6081533	June 2000	Laubach et al.
6219153	April 2001	Kawanabe et al.
2005/0137653	June 2005	Friedman et al.
2006/0010199	January 2006	Brailean et al.

Primary Examiner: Barlow; John
Assistant Examiner: Vo; Hien
Attorney, Agent or Firm: Meyertons Hood Kivlin Kowert & Goetzel, P.C. Hood; Jeffrey C. Williams; Mark S.

Parent Case Text

PRIORITY CLAIM

This application claims benefit of priority of U.S. provisional application Ser. No. 60/312,254 titled "Measurement System with Modular Measurement Modules That Convey Interface Information" filed on Aug. 14, 2001, whose inventors are Perry Steger, Garritt W. Foote, David Potter and James J. Truchard.

Claims

We claim:

1. A system for registering measurement module interfaces, comprising: a server computer system, comprising: a processor; and a memory medium coupled to the processor, wherein the memory medium stores measurement module registration software; wherein the server computer system is accessible by a client computer over a network; wherein the measurement module registration software is executable by the processor to perform: receiving registration information for a measurement module from the client computer; receiving one or more measurement module interface programs from the client computer implementing a respective one or more measurement module interface protocols, wherein each of the one or more measurement module interface protocols describes an interface for communicating with the measurement module; and storing the one or more measurement module interface programs, wherein the one or more measurement module interface programs are downloadable from the server computer system; wherein each of the one or more measurement module interface programs is usable to program one or more functional units of a carrier unit, thereby enabling the carrier unit to communicate with the measurement module in accordance with the respective measurement module interface protocol.

2. The system of claim 1, wherein said registration information comprises one or more of: identification information for the measurement module; version information for the one or more measurement module interface programs; and time and date information.

3. The system of claim 2, wherein said identification information for the measurement module comprises one or more of: a model number for the measurement module; version information for the measurement module; a functional description of the measurement module; identification information for the manufacturer of the measurement module; a help file describing the use and operation of the measurement module; platform information for the measurement module; and ordering information for the measurement module.

4. The system of claim 3, wherein said ordering information for the measurement module comprises one or more of: pricing information for the measurement module; and availability information for the measurement module.

5. The system of claim 1, wherein said registration information further comprises payment information.

6. The system of claim 1, wherein the measurement module registration software is executable by the processor to register a plurality of measurement modules from a plurality of manufacturers; wherein the memory medium is operable to store a plurality of measurement module interface programs implementing a respective plurality of measurement module interfaces for the plurality of measurement modules; and wherein the plurality of measurement module interface programs are downloadable from the server computer system.

7. The system of claim 1, wherein the server computer system is further accessible by the client computer to provide updates for one or more of: the registration information for the measurement module; and the one or more measurement module interface programs.

8. The system of claim 7, wherein the memory medium further stores software which is executable by the processor to notify one or more clients of said updates.

9. The system of claim 1, wherein at least one of the one or more measurement module interface programs comprises a hardware configuration program which is deployable on a programmable hardware element on the carrier unit.

10. The system of claim 1, wherein at least one of the one or more measurement module interface programs comprises a bitstream which is deployable on a Field Programmable Gate Array (FPGA) on the carrier unit.

11. The system of claim 1, wherein at least one of the one or more measurement module interface programs is executable by a processor on the carrier unit.

12. The system of claim 1, wherein at least one of the one or more measurement module interface programs comprises a text-based program; and wherein the memory medium of the server computer system stores one or more programs executable to compile the text-based program to one or more of: a hardware configuration program which is deployable on a programmable hardware element of the carrier unit; and an executable program executable by a processor on the carrier unit.

13. The system of claim 12, wherein the hardware configuration program comprises a bitstream which is deployable on a Field Programmable Gate Array (FPGA) on the carrier unit.

14. The system of claim 1, wherein at least one of the one or more measurement module interface programs comprises a graphical program; and wherein the memory medium of the server computer system stores one or more programs executable to compile the graphical program to one or more of: a hardware configuration program which is deployable on a programmable hardware element of the carrier unit; and an executable program executable by a processor on the carrier unit.

15. The system of claim 14, wherein the hardware configuration program comprises a bitstream which is deployable on a Field Programmable Gate Array (FPGA) on the carrier unit.

16. A method for registering measurement module interfaces, comprising: creating a measurement module; creating one or more measurement module interface programs that implement respective measurement module interface protocols (MMIP) for the measurement module; accessing an MMIP server computer system; registering the measurement module with the MMIP server computer system; and providing the one or more measurement module interface programs for storage on the MMIP server computer system; wherein the one or more measurement module interface programs are downloadable from the MMIP server computer system; and wherein the one or more measurement module interface programs are usable to program one or more functional units on a carrier unit, thereby enabling the carrier unit to communicate with the measurement module in accordance with the respective measurement module interface protocols.

17. The method of claim 16, wherein said registering the measurement module with the MMIP server computer system comprises one or more of: providing identification (ID) information for the measurement module to the MMIP sewer computer system; providing version information for the one or more measurement module interface programs; providing pricing information for the one or more measurement module interface programs; and providing time and date information.

18. The method of claim 17, wherein said identification information for the measurement module comprises one or more of: a model number for the measurement module; version information for the measurement module; a functional description of the measurement module; identification information for the manufacturer of the measurement module; a help file describing the use and operation of the measurement module; platform information for the measurement module; and ordering information for the measurement module.

19. The method of claim 18, wherein said ordering information for the measurement module comprises one or more of: pricing information for the measurement module; and availability information for the measurement module.

20. The method of claim 16, wherein said registering the measurement module with the MMIP server computer system further comprises: providing payment information to the MMIP server computer system.

21. The method of claim 16, wherein said accessing the MMIP server computer comprises accessing the MMIP server computer over a network.

22. The method of claim 16, further comprising: accessing the MMIP server computer to provide updates for one or more of: the registration information for the measurement module; and the one or more measurement module interface programs.

23. The method of claim 22, further comprising: receiving notification of said updates.

24. The method of claim 16, wherein at least one of the one or more measurement module interface programs comprises a hardware configuration program which is deployable on a programmable hardware element on the carrier unit.

25. The method of claim 16, wherein at least one of the one or more measurement module interface programs comprises a bitstream which is deployable on a Field Programmable Gate Array (FPGA) on the carrier unit.

26. The method of claim 16, wherein at least one of the one or more measurement module interface programs is executable by a processor on the carrier unit.

27. The method of claim 16, wherein at least one of the one or more measurement module interface programs comprises a text-based program; and wherein the memory medium of the server computer system stores one or more programs executable to compile the text-based program to one or more of: a hardware configuration program which is deployable on a programmable hardware element of the carrier unit; and an executable program executable by a processor on the carrier unit.

28. The method of claim 27, wherein the hardware configuration program comprises a bitstream which is deployable on a Field Programmable Gate Array (FPGA) on the carrier unit.

29. The method of claim 16, wherein at least one of the one or more measurement module interface programs comprises a graphical program; and wherein the memory medium of the server computer system stores one or more programs executable to compile the graphical program to one or more of: a hardware configuration program which is deployable on a programmable hardware element of the carrier unit; and an executable program executable by a processor on the carrier unit.

30. The method of claim 29, wherein the hardware configuration program comprises a bitstream which is deployable on a Field Programmable Gate Array (FPGA) on the carrier unit.

31. A method for registering measurement module interfaces, comprising: receiving a request to register a measurement module; registering the measurement module; receiving one or more measurement module interface programs that implement respective measurement module interface protocols for the measurement module; and storing the one or more measurement module interface programs; wherein the one or more measurement module interface programs are downloadable to client computer systems; and wherein the one or more measurement module interface programs are usable to program one or more functional units on a carrier unit, thereby enabling the carrier unit to communicate with the measurement module in accordance with the respective measurement module interface protocols.

32. The method of claim 31, wherein said registering the measurement module comprises one or more of: receiving identification (ID) information for the measurement module; receiving version information for the one or more measurement module interface programs; receiving pricing information for the one or more measurement module interface programs; and receiving time and date information.

33. The method of claim 32, wherein said identification information for the measurement module comprises one or more of: a model number for the measurement module; version information for the measurement module; a functional description of the measurement module; identification information for the manufacturer of the measurement module; a help file describing the use and operation of the measurement module; platform information for the measurement module; and ordering information for the measurement module.

34. The method of claim 33, wherein said ordering information for the measurement module comprises one or more of: pricing information for the measurement module; and availability information for the measurement module.

35. The method of claim 31, wherein said registering the measurement module farther comprises: receiving payment information.

36. The method of claim 31, wherein said receiving the request and said receiving the program comprises: receiving the request, and receiving the program from a client computer system over a network.

37. The method of claim 31, further comprising: receiving updates for one or more of: the registration information for the measurement module; and the one or more measurement module interface programs.

38. The method of claim 37, further comprising: providing notification of said updates to one or more clients.

39. The method of claim 31, wherein at least one of the one or more measurement module interface programs comprises a hardware configuration program which is deployable on a programmable hardware element on the carrier unit.

40. The method of claim 31, wherein at least one of the one or more measurement module interface programs comprises a bitstream which is deployable on a Field Programmable Gate Array (FPGA) on the carrier unit.

41. The method of claim 31, wherein at least one of the one or more measurement module interface programs is executable by a processor on the carrier unit.

42. The method of claim 31, wherein at least one of the one or more measurement module interface programs comprises a text-based program, the method further comprising: compiling the text-based program to one or more of: a hardware configuration program which is deployable on a programmable hardware element of the carrier unit; and an executable program executable by a processor on the carrier unit.

43. The method of claim 42, wherein the hardware configuration program comprises a bitstream which is deployable on a Field Programmable Gate Array (FPGA) on the carrier unit.

44. The method of claim 31, wherein at least one of the one or more measurement module interface programs comprises a graphical program, the method further comprising: compiling the graphical program to one or more of: a hardware configuration program which is deployable on a programmable hardware element of the carrier unit; and an executable program executable by a processor on the carrier unit.

45. The method of claim 44, wherein the hardware configuration program comprises a bitstream which is deployable on a Field Programmable Gate Array (FPGA) on the carrier unit.

46. A system for registering measurement module interfaces, comprising: means for creating a measurement module; means for creating one or more measurement module interface programs that implement respective measurement module interface protocols (MMIP) for the measurement module; means for accessing an MMIP server computer system; means for registering the measurement module with the MMIP server computer system; and means for providing the one or more measurement module interface programs for storage on the MMIP server computer system; wherein the one or more measurement module interface programs are downloadable from the MMIP server computer system; and wherein the one or more measurement module interface programs are usable to program one or more functional units on a carrier unit, thereby enabling the carrier unit to communicate with the measurement module in accordance with the respective measurement module interface protocols.

47. A system for registering measurement module interfaces, comprising: means for receiving a request to register a measurement module; means for registering the measurement module; means for receiving one or more measurement module interface programs that implement respective measurement module interface protocols for the measurement module; and means for storing the one or more measurement module interface programs; wherein the one or more measurement module interface programs are downloadable to client computer systems; and wherein the one or more measurement module interface programs are usable to program one or more functional units on a carrier unit, thereby enabling the carrier unit to communicate with the measurement module in accordance with the respective measurement module interface protocols.

48. A computer-accessible medium which stores program instructions for registering measurement module interfaces, wherein the program instructions are executable to perform: receiving a request to register a measurement module; registering the measurement module; receiving one or more measurement module interface programs that implement respective measurement module interface protocols for the measurement module; and storing the one or more measurement module interface programs; wherein the one or more measurement module interface programs are downloadable to client computer systems; and wherein the one or more measurement module interface programs are usable to program one or more functional units on a carrier unit, thereby enabling the carrier unit to communicate with the measurement module in accordance with the respective measurement module interface protocols.

49. A method for configuring a measurement system, comprising: installing a measurement module in the measurement system, wherein said installing comprises coupling the measurement module to a carrier unit of the measurement system the measurement module providing identification information to the carrier unit; accessing a measurement module interface protocol (MMIP) sewer computer system over a network based on the provided identification information; downloading a measurement module interface program from the MMIP server computer system, wherein the measurement module interface program implements a measurement module interface protocol for operating with the measurement module; and configuring the carrier unit with the measurement module interface program, thereby enabling the carrier unit to communicate with the measurement module in accordance with the measurement module interface protocol; wherein after said configuring, the carrier unit and the measurement module are together operable to perform one or more of a data acquisition, measurement, and control task.

50. The method of claim 49, further comprising: providing payment information to the MMIP server computer system prior to said downloading.

51. The method of claim 49, wherein said identification information comprises one or more of: a model number for the measurement module; version information for the measurement module; a functional description of the measurement module; identification information for the manufacturer of the measurement module; and platform information for the measurement module.

52. The method of claim 49, wherein said accessing the measurement module interface protocol (MMIP) sewer computer system is performed by the carrier unit.

53. The method of claim 49, further comprising: the carrier unit providing the identification information to a computer system coupled to the carrier unit; wherein said accessing the measurement module interface protocol (MMIP) server computer system is performed by the computer system.

54. The method of claim 49, wherein said configuring the carrier unit with the measurement module interface program comprises: programming one or more functional units on the carrier unit with the measurement module interface program.

55. The method of claim 49, further comprising: the carrier unit and the measurement module together performing one or more of a data acquisition, measurement, and control task.

56. A method for configuring a measurement system, comprising: receiving identification information for a measurement module; storing the identification information on a memory medium; and providing a measurement module interface program based on the received identification information, wherein the measurement module interface program implements a measurement module interface protocol for operating with the measurement module; wherein the measurement module interface program is usable to configure a carrier unit in the measurement system, thereby enabling the carrier unit to communicate with the measurement module in accordance with the measurement module interface protocol.

57. The method of claim 56, further comprising: receiving payment information prior to said providing.

58. The method of claim 56, wherein said identification information comprises one or more of: a model number for the measurement module; version information for the measurement module; a functional description of the measurement module; identification information for the manufacturer of the measurement module; and platform information for the measurement module.

59. The method of claim 56, further comprising: configuring the carrier unit with the measurement module interface program, thereby enabling the carrier unit to communicate with the measurement module in accordance with the measurement module interface protocol; wherein after said configuring, the carrier unit and the measurement module are together operable to perform one or more of a data acquisition, measurement, and control task.

60. The method of claim 56, wherein said providing the measurement module interface program comprises downloading the measurement module interface program to the carrier unit.

61. The method of claim 56, wherein said providing the measurement module interface program comprises downloading the measurement module interface program to a computer system coupled to the carrier unit.

62. The method of claim 56, wherein being usable to configure a carrier unit in the measurement system comprises: being usable to program one or more functional units on the carrier unit with the measurement module interface program.

63. The method of claim 56, wherein being usable to configure a carrier unit in the measurement system comprises: being deployable on one or more programmable hardware elements on the carrier unit.

Description

FIELD OF THE INVENTION

The present invention relates to measurement, data acquisition, and control, and particularly to measurement devices with adaptive interfaces and modular signal conditioning and conversion devices which convey interface information. More specifically, systems and methods are described for registering and using interface protocols for modular measurement modules.

DESCRIPTION OF THE RELATED ART

Scientists and engineers often use measurement or instrumentation systems to perform a variety of functions, including laboratory research, process monitoring and control, data logging, analytical chemistry, test and analysis of physical phenomena, and control of mechanical or electrical machinery, to name a few examples. An instrumentation system typically includes transducers and other detecting means for providing "field" electrical signals representing a process, physical phenomena, equipment being monitored or measured, etc. For example, detectors and/or sensors are used to sense the on/off state of power circuits, proximity switches, pushbutton switches, thermostats, relays or even the presence of positive or negative digital logic-level signals. The instrumentation system typically also includes interface hardware for receiving the measured field signals and providing them to a processing system, such as a personal computer. The processing system typically performs data analysis and presentation for appropriately analyzing and displaying the measured data.

Often, the field signals may be coupled to high common-mode voltages, ground loops, or voltage spikes that often occur in industrial or research environments which could damage the computer system. In that case, the instrumentation system typically includes isolation circuitry such as opto-couplers for eliminating ground-loop problems and isolating the computer from potentially damaging voltages. Input modules are typically provided for conditioning the raw field voltage signals by amplifying, isolating, filtering or otherwise converting the signals to the appropriate digital signals for the computer system. As one example, the digital signals are then provided to a plug-in data acquisition (DAQ) input/output (I/O) board, or a computer-based instrument which is plugged into one of the I/O slots of a computer system. Generally, the computer system has an I/O bus and connectors or slots for receiving I/O boards. Various computer systems and I/O buses may be used to implement a processing system.

Typical DAQ, measurement, and control modules include circuitry or components to provide a standard interface to external systems, such as PCI or PXI boards. The inclusion of these standard interface components on each module may be expensive, and may also substantially increase the size of a given module. Additionally, when multiple modules are used in a single system, such as a PXI based system fielding multiple sensors, the inclusion of PXI interface circuitry on each sensor is redundant and inefficient. Finally, if multiple communication interfaces are desired for the modules, the expense and size of the modules may increase dramatically with the inclusion of each additional interface card.

Therefore, improved measurement systems are desired which reduce cost and enhance efficiency and flexibility.

SUMMARY

Various embodiments of a system and method for registering and using measurement module interface protocols are described. The system may include a measurement module interface protocol (MMIP) server computer system which is accessible by client computer systems over a network or other communication medium. The MMIP server may be operable to register and store measurement module interface protocols for various modular measurement modules and to make these protocols available for download to clients for configuring measurement systems.

In one embodiment, a measurement module may be created, and one or more measurement module interface programs implementing respective measurement module interface protocols for the measurement module. The measurement module interface protocol server computer system may be accessed, e.g., over a network, such as the Internet, and the measurement module registered with the measurement module interface protocol server. The one or more measurement module interface programs may be provided for storage on the MMIP server computer system, where they may be downloadable from the MMIP server computer system by client computer systems. The one or more measurement module interface programs may be usable to program one or more functional units on a carrier unit, thereby enabling the carrier unit to communicate with the measurement module in accordance with the respective measurement module interface protocols.

Registering the measurement module with the MMIP server computer system may include providing one or more of: identification (ID) information for the measurement module to the MMIP server computer system, version information for the one or more measurement module interface programs, pricing information for the one or more measurement module interface programs, and time and date information, among others. In one embodiment, the identification information for the measurement module may include one or more of: a model number for the measurement module, version information for the measurement module, a functional description of the measurement module, identification information for the manufacturer of the measurement module, a help file describing the use and operation of the measurement module, platform information for the measurement module, and ordering information for the measurement module, such as, for example, pricing and/or availability information for the measurement module. In one embodiment, registering the measurement module with the MMIP server computer system may further include providing payment information, e.g., a credit account or credit card information, to the MMIP server computer system.

In one embodiment, the MMIP server computer may be accessed subsequently by the client to provide updates for the registration information for the measurement module, and/or the one or more measurement module interface programs. The MMIP server may send notification of the updates to clients, which may then access the MMIP server to receive the updates as desired.

In one embodiment, at least one of the one or more measurement module interface programs includes a hardware configuration program which is deployable on a programmable hardware element on the carrier unit. For example, at least one of the measurement module interface programs may include a bitstream which is deployable on a Field Programmable Gate Array (FPGA) on the carrier unit. In another embodiment, at least one of the one or more measurement module interface programs may be executable by a processor on the carrier unit. In other embodiments, at least one of the measurement module interface programs may be a text-based program or a graphical program, where the MMIP server computer system may store one or more programs executable to compile the program to one or more of: a hardware configuration program which is deployable on a programmable hardware element of the carrier unit, and an executable program executable by a processor on the carrier unit.

Once one or more measurement module interface programs have been registered and stored on the MMIP server, other computer systems may access the server to download the programs to configure measurement systems. For example, in one embodiment, a measurement module may be installed in the measurement system, e.g., the measurement module may be coupled to a carrier unit of the measurement system. The measurement module may provide ID information to the carrier unit of the system. In one embodiment, the ID information may include one or more of: a model number for the measurement module, version information for the measurement module, a functional description of the measurement module, identification information for the manufacturer of the measurement module, and platform information for the measurement module, among others.

The MMIP server computer system may then be accessed over a network based on the provided ID information. For example, in one embodiment, the MMIP server computer system may be accessed by the carrier unit, which may provide the ID information to the MMIP server. In another embodiment, the carrier unit may provide the identification information to the computer system coupled to the carrier unit, and the computer system may access the MMIP server computer system.

A measurement module interface program from the MMIP server computer system may then be downloaded, where the measurement module interface program implements a measurement module interface protocol for operating with the measurement module. The carrier unit may then be configured with the measurement module interface program, thereby enabling the carrier unit to communicate with the measurement module in accordance with the measurement module interface protocol. After being configured with the measurement module interface program, the carrier unit and the measurement module may together be operable to perform one or more of a data acquisition, measurement, and control task, among others. In one embodiment, payment information may be provided to the MMIP server computer system prior to said downloading. In other words, a fee may be required to download the program.

In one embodiment, configuring the carrier unit with the measurement module interface program may include programming one or more functional units e.g., a processor (or microprocessor) and memory, or a programmable hardware element (e.g., an FPGA), on the carrier unit with the measurement module interface program. After being configured, the carrier unit and the measurement module together may perform one or more of a data acquisition, measurement, and control task.

Thus, in one embodiment, the measurement module may be operable to communicate interface information to the carrier, which in turn informs the computer system how to program the carrier to implement the communicated interface, i.e., how to "talk" to the measurement module. In another embodiment, the carrier itself may include a processor and memory which receives the interface information from the module and programs reconfigurable hardware on the carrier to implement the interface.

This "adaptive interface" approach allows the measurement module to include only components necessary for providing the required functionality, i.e., the measurement module does not have to include hardware and software implementing standard interfaces for communication with external systems. Said another way, much of the interface responsibilities of the measurement module are assumed by the carrier, which itself is programmed by the computer system, thus the measurement module may be smaller and cheaper than typical functional modules.

BRIEF DESCRIPTION OF THE DRAWINGS

A better understanding of the present invention can be obtained when the following detailed description of the preferred embodiment is considered in conjunction with the following drawings, in which:

FIG. 1A illustrates a measurement system, according to one embodiment of the invention;

FIG. 1B illustrates a networked measurement system including a server computer system, according to one embodiment of the invention;

FIG. 2 is a block diagram of a networked measurement system computer system, according to one embodiment of the invention;

FIGS. 3A and 3B are block diagrams of two embodiments of a computer system;

FIGS. 4A and 4B are block diagrams of embodiments of a measurement module;

FIGS. 5A and 5B illustrate a measurement module, according to one embodiment;

FIG. 5C illustrates a hardware layout of a measurement module, according to one embodiment of the invention;

FIG. 6 is a block diagram of a carrier with multiple measurement modules, according to one embodiment of the invention;

FIG. 7A illustrates a cartridge carrier with measurement cartridges, according to one embodiment of the invention;

FIG. 7B illustrates a cartridge carrier with measurement cartridges, according to another embodiment of the invention;

FIGS. 7C and 7D illustrate embodiments of measurement cartridges used in RIO systems;

FIG. 8A is a block diagram of a cartridge carrier in a RIO system with separate cartridge channels, according to one embodiment;

FIG. 8B is a block diagram of a cartridge carrier in a RIO system with a shared cartridge bus, according to one embodiment;

FIG. 9 is a block diagram of a cartridge carrier, according to one embodiment;

FIG. 10A is a block diagram of a cartridge controller, according to one embodiment;

FIGS. 10B and 10C illustrate SPI signal timing, according to one embodiment;

FIG. 11A is a block diagram of a measurement system using re-configurable I/O (RIO), according to one embodiment of the invention;

FIG. 11B is a block diagram illustrating functional partitions of a RIO measurement system with measurement modules, according to one embodiment;

FIG. 12A illustrates a PXI carrier card, according to one embodiment of the invention;

FIG. 12B illustrates a PDA based measurement system, according to one embodiment of the invention;

FIG. 12C illustrates various embodiments of a RIO based system with I/O expansion;

FIG. 12D illustrates various sensor/measurement systems according to the present invention;

FIG. 13 illustrates the use of measurement modules in the context of current measurement systems;

FIG. 14 is a flowchart of a method for configuring a measurement system, according to one embodiment;

FIG. 15 is a flowchart of another method for configuring a measurement system, according to one embodiment;

FIG. 16 is a flowchart of a method for performing a measurement function, according to one embodiment;

FIG. 17 is a flowchart of a method for registering a measurement cartridge bitstream with a measurement module interface protocol (MMIP) server;

FIG. 18 is a flowchart of a method for configuring a measurement cartridge;

FIG. 19 illustrates communication layers and interfaces in the measurement system, according to one embodiment;

FIG. 20 illustrates a high-level architecture of a standard measurement system interface, according to one embodiment;

FIGS. 21 30 are timing diagrams for defined methods supported by the measurement system, according to one embodiment;

FIG. 31 illustrates one embodiment of a measurement module pinout specification, according to one embodiment;

FIGS. 32A and 32B illustrate SPI signal timing, according to one embodiment;

FIGS. 33A 33C are example circuit diagrams for various measurement modules, according to one embodiment;

FIGS. 33D 33G are example circuit diagrams for various measurement module/RIO FPGA configurations, according to one embodiment;

FIGS. 34A 34E illustrate representations of setup information for various measurement modules, according to one embodiment;

FIG. 35 is a block diagram for a serial communication block, according to one embodiment;

FIG. 36 illustrates a sequence list configuration, according to one embodiment;

FIG. 37 illustrates an SPI rate description format, according to one embodiment;

FIG. 38 illustrates a sequence command list file format, according to one embodiment; and

FIG. 39 illustrates one embodiment of a carrier logic configuration for synchronizing multiple delta-sigma converters.

While the invention is susceptible to various modifications and alternative forms specific embodiments are shown by way of example in the drawings and may herein be described in detail. It should be understood however, that drawings and detailed description thereto are not intended to limit the invention to the particular form disclosed. But on the contrary the invention is to cover all modifications, equivalents and alternative following within the spirit and scope of the present invention as defined by the appended claims.

DETAILED DESCRIPTION OF THE EMBODIMENTS

Incorporation by Reference

The following U.S. Patents and patent applications are hereby incorporated by reference in their entirety as though fully and completely set forth herein.

U.S. Pat. No. 4,914,568 titled "Graphical System for Modeling a Process and Associated Method," issued on Apr. 3, 1990.

U.S. Pat. No. 6,219,628 titled "System and Method for Configuring an Instrument to Perform Measurement Functions Utilizing Conversion of Graphical Programs into Hardware Implementations".

U.S. Pat. No. 6,173,438 titled "Embedded Graphical Programming System" filed Aug. 18, 1997, whose inventors are Jeffrey L. Kodosky, Darshan Shah, Samson DeKey, and Steve Rogers.

U.S. Provisional Patent Application Ser. No. 60/312,254 titled "Measurement System with Modular Measurement Modules That Convey Interface Information" filed on Aug. 14, 2001, whose inventors are Perry Steger, Garritt W. Foote, David Potter and James J. Truchard.

U.S. patent application Ser. No. 10/195,051 titled "Measurement System with Modular Measurement Modules That Convey Interface Information" filed on Jul. 12, 2002, whose inventors are Perry Steger, Garritt W. Foote, David Potter and James J. Truchard.

U.S. patent application Ser. No. 10/194,952 titled "Measurement System Including a Programmable Hardware Element and Measurement Modules that Convey Interface Information" filed on Jul. 12, 2002, whose inventors are Perry Steger, Garritt W. Foote, David Potter and James J. Truchard.

U.S. patent application Ser. No. 09/891,571 titled "System and Method for Configuring an Instrument to Perform Measurement Functions Utilizing Conversion of Graphical Programs into Hardware Implementations" filed on Jun. 25, 2001, whose inventors are Jeffrey L. Kodosky, Hugo Andrade, Brian Keith Odom, Cary Paul Butler, and Kevin L. Schultz.

U.S. patent application Ser. No. 09/745,023 titled "System and Method for Programmatically Generating a Graphical Program in Response to Program Information," filed Dec. 20, 2000, whose inventors are Ram Kudukoli, Robert Dye, Paul F. Austin, Lothar Wenzel and Jeffrey L. Kodosky.

U.S. patent application Ser. No. 09/595,003 titled "System and Method for Automatically Generating a Graphical Program to Implement a Prototype", filed Jun. 13, 2000, whose inventors are Nicolas Vazquez, Jeffrey L. Kodosky, Ram Kudukoli, Kevin L. Schultz, Dinesh Nair, and Christophe Caltagirone.

FIGS. 1A and 1B--A Measurement System

FIGS. 1A and 1B illustrate embodiments of a computer system 102 coupled to a measurement or data acquisition (DAQ) device 107. As used herein, the term "measurement device" is intended to include instruments, smart sensors, data acquisition devices or boards, and any of various types of devices that are operable to acquire and/or store data. A measurement device may also optionally be further operable to analyze or process the acquired or stored data. Examples of a measurement device include an instrument, such as a computer-based instrument (instrument on a card) an external instrument a data acquisition card, a device external to a computer that operates similarly to a data acquisition card, a smart sensor, one or more DAQ or measurement modules in a chassis, an image acquisition device such as an image acquisition board or smart camera, a motion control device and other similar types of devices. Exemplary instruments include oscilloscopes, multi-meters, and GPIB, PCI, PXI, and VXI instruments, among others.

In the embodiment of FIG. 1A, the computer system 102 may couple to the measurement device through a transmission medium, e.g., a serial bus, such as a USB 109. It should be noted that although a USB 109 is shown in this example, any other transmission medium may be used, including Ethernet, wireless media such as IEEE 802.11 (Wireless Ethernet) or (Bluetooth, a network, such as a fieldbus, a Control Area Network (CAN) or the Internet, serial or parallel buses, or other transmission means. For example, in the embodiment of FIG. 1B, the measurement device 107 is coupled to a server computer system 102 over a network 104, such as the Internet. In one embodiment, the server computer 102 may comprise a measurement module interface protocol (MMIP) server 102A which is operable to store a plurality of MMIPs for use by the measurement device. The MMIP server may be accessed by the measurement device 107 to retrieve the MMIP, as described in more detail below. In another embodiment, the MMIP server may be separate from the computer system 102, and the measurement device 107 (or the computer system 102) may retrieve the MMIP from the server 102A.

Thus, FIGS. 1A and 1B illustrate an exemplary data acquisition or measurement system. As FIGS. 1A and 1B show, the measurement device 107 may in turn couple to or comprise a sensor or actuator 112, such as a pressure or temperature gauge, a thermocouple, an imaging device, (e.g. a camera), or any other type of sensor or actuator. As shown in FIG. 1C, the measurement device 107 may include a measurement module (or multiple measurement modules) comprised in a chassis for performing one or more measurement (including) or processing functions as described below.

The host computer 102 may comprise a CPU, a display screen, memory, and one or more input devices such as a mouse or keyboard as shown. The computer 102 may operate with the measurement device 107 to analyze or measure data from the sensor 112 and/or measurement device 107 or to control the sensor 112 and/or measurement device 107. Alternatively, the computer 102 may be used only to configure or program the measurement device 107, as described below.

FIG. 2--Block Diagram of a Measurement System

FIG. 2 is a block diagram of a measurement system, according to another embodiment of the invention. As FIG. 2 shows, the measurement device 107 may comprise a carrier 110 and a measurement module 108. The sensor 112 may be coupled to the measurement module 108 which may in turn be coupled to the carrier unit 110, also referred to as carrier 110. The carrier 110 may be coupled to computer system 102 via a network (e.g., the Internet) 104 as shown, or, as mentioned above, may be coupled to the computer system 102 by other transmission means, including serial or parallel bus, wireless, and CAN, among others. In an embodiment where the carrier 110 includes a processor and memory, the carrier may operate independent of the computer 102, as describe in more detail below.

The measurement module 108 and the carrier 110 together may provide the functionality of the measurement device 107 of FIG. 1A. For example, in one embodiment, the measurement module 108 may be operable to perform signal conditioning and/or signal conversion on the signals sent by the sensor 112, and to transmit results of such processing on to the carrier 110. In one embodiment, the carrier 110 may be operable to receive data from the measurement module 108 and communicate the data (possibly in a different format or form) to the computer system 102, e.g., over the transmission medium 104. For example, the carrier 110 may receive signal data in a proprietary format from the measurement module 108 and format the data for transmission over wireless Ethernet to the computer system 102.

In the preferred embodiment, the carrier 110 includes a functional unit 106, which may be programmed, for example, by computer system 102 or by a processor/memory comprised in the carrier itself. As used herein, the term "functional unit" may include a processor and memory and/or a programmable hardware element. As used herein, the term "processor" is intended to include any of types of processors, CPUs, microcontrollers, or other devices capable of executing software instructions. As used herein, the term "programmable hardware element" is intended to include various types of programmable hardware, reconfigurable hardware, programmable logic, or field-programmable devices (FPDs), such as one or more FPGAs (Field Programmable Gate Arrays), or one or more PLDs (Programmable Logic Devices), such as one or more Simple PLDs (SPLDs) or one or more Complex PLDs (CPLDs), or other types of programmable hardware. Thus, the carrier unit 110 may be re-configurable, i.e., programmable by an external computer system, such as computer system 102.

More specifically, in the preferred embodiment, the carrier unit 110 may be operable to receive interface protocol information from the measurement module 108 specifying how to operate or interface with the measurement module 108. In one embodiment, the carrier unit 110 may then communicate the interface protocol information to the computer system 102. Alternatively, measurement module may communicate the interface information directly to the computer system. Based on the interface protocol information, the computer system 102 may program or configure the functional unit 106 on the carrier unit 110 to implement the interface as specified by the measurement module 108. In other words, the measurement module 108 may tell the carrier 110 how to "talk" with it, and the carrier 110 may then tell the computer system 102 how to program the carrier 110 to communicate with the measurement module 108 accordingly (or the measurement module may tell the computer system directly how to program the camera. The computer system 102 may then program the carrier 110 (i.e., the carrier's functional unit 106), thereby implementing the interface specified in the interface protocol information communicated by the measurement module 108.

In another embodiment, the carrier unit 110 may be operable to receive the interface protocol information from the measurement module 108, and a processor and memory on the carrier unit 110 may then program or configure the functional unit on the carrier unit 110 to implement the interface as specified by the measurement module. In other words, the measurement module may communicate its interface protocol to the carrier, and the carrier may program itself (i.e., the processor/memory on the carrier 110 may program a programmable hardware element on the carrier 110) to communicate with the measurement module accordingly, thereby implementing the interface specified in the interface protocol information communicated by the measurement module.

This process may be referred to as initialization of the measurement module/carrier. Further details of this process are described below.

Referring again to FIG. 2, the computer 102 may include a memory medium on which computer programs according to the present invention may be stored. As used herein, the term "memory medium" includes a non-volatile medium, e.g., a magnetic media or hard disk, or optical storage; a volatile medium, such as computer system memory, e.g., random access memory (RAM) such as DRAM, SRAM, EDO RAM, RAMBUS RAM, DR DRAM, etc.; or an installation medium, such as a CD-ROM or floppy disks, on which the computer programs according to the present invention may be stored for loading into the computer system. The term "memory medium" may also include other types of memory or combinations thereof.

The memory medium may be comprised in the computer 102 where the programs are executed or may be located on a second computer which is coupled to the computer 102 through a network, such as a local area network (LAN), a wide area network (WAN), or the Internet. In this instance, the second computer operates to provide the program instructions through the network to the computer 102 for execution. Also, the computer system 102 may take various forms, including a personal computer system, mainframe computer system, workstation, network appliance, Internet appliance, personal digital assistant (PDA), television set-top box, instrument, or other device. In general, the term "computer system" can be broadly defined to encompass any device having at least one processor which executes instructions from a memory medium.

Thus, in various embodiments, software programs of the present invention may be stored in a memory medium of the respective computer 102, or in a memory medium of another computer, and executed by the CPU. The CPU executing code and data from the memory medium thus comprises a means for receiving interface protocol information and programming or configuring the carrier 110 to implement the specified interface, as described in more detail below.

In one embodiment, the computer system 102 may also store a program implementing one or more measurement functions, i.e., a measurement program, e.g., a software program, such as a graphical program, implementing the one or more measurement functions. The term "measurement function" may include measurement, data acquisition, and/or control functions, such as displaying received data, analyzing and/or processing received data to generate a result, performing signal processing on received data, or otherwise analyzing and/or processing received data to perform a measurement. Examples of measurement functions include various instrumentation functions or control functions.

In the present application, the term "graphical program" or "block diagram" is intended to include a program comprising graphical code, e.g., two or more nodes or icons interconnected in one or more of a data flow, control flow, or execution flow format, where the interconnected nodes or icons may visually indicates the functionality of the program. Thus the terms "graphical program" or "block diagram" are each intended to include a program comprising a plurality of interconnected nodes or icons which visually indicates the functionality of the program. A graphical program may comprise a block diagram and may also include a user interface portion or front panel portion. The user interface portion may be contained in the block diagram or may be contained in one or more separate panels or windows. A graphical program may be created using any of various types of systems which are used to develop or create graphical code or graphical programs, including LabVIEW, DASYLab, and DiaDem from National Instruments, Visual Designer from Intelligent Instrumentation, Agilent VEE (Visual Engineering Environment), Snap-Master by HEM Data Corporation, SoftWIRE from Measurement Computing, ObjectBench by SES (Scientific and Engineering Software), Simulink from the MathWorks, WiT from Coreco, Vision Program Manager from PPT Vision, Hypersignal, VisiDAQ, VisSim, and Khoros, among others. In the preferred embodiment, the system uses the LabVIEW graphical programming system available from National Instruments.

The computer system 102 may be operable to execute the measurement program to perform the one or more measurement functions, preferably in conjunction with operation of the carrier 110 and/or measurement module 108. For example, the measurement program may be executable to perform one or more of measurement or control functions, including analysis of data or signals received from the carrier, control of carrier and/or measurement module operations, user interface functions, image processing or machine vision functions, and motion control functions, among others.

In another embodiment, the computer system may be operable to deploy the measurement program onto the functional unit 106 of the carrier unit 110. In other words, in addition to, or instead of, programming the carrier unit 110 to implement the interface, the computer system may download the measurement program onto the functional unit of the carrier. After deploying a software program on the functional unit 106 the carrier 110 may be operable to execute the measurement program to perform the one or more measurement functions, preferably in conjunction with operation of the measurement module 108, and possibly the computer system 102.

The configured carrier 110 and the measurement module 108 may then be operable to perform measurement operations using the sensor 112 and/or the computer system 102.

FIGS. 3A and 3B--Computer Block Diagrams

FIGS. 3A and 3B are exemplary block diagrams of the computer 102 of FIGS. 1A and 1B, respectively. The elements of a computer not necessary to understand the operation of the present invention have been omitted for simplicity. The computer 102 may include at least one central processing unit (CPU) or processor 160 which is coupled to a processor or host bus 162. The CPU 160 may be any of various types, including an x86 processor, a PowerPC processor, a CPU from the Motorola family of processors, a CPU from the SPARC family of RISC processors, as well as others. Main memory 166 may be coupled to the host bus 162 by means of memory controller 164. The main memory 166 is operable to store one or more programs according to the present invention. For example, the memory medium 164 may store a program which is executable to use interface protocol information received from the carrier 110 to program or configure the functional unit 106 comprised in the carrier 110. The main memory 166 may also store operating system software, i.e., software for operation of the computer system, as well as one or more application programs, as is well known to those skilled in the art. In addition, the main memory 166 may store one or more measurement programs which are executable to perform DAQ, measurement, and/or control tasks.

The host bus 162 is coupled to an expansion or input/output bus 170 by means of a bus controller 168 or bus bridge logic. The expansion bus 170 is preferably the PCI (Peripheral Component Interconnect) expansion bus, although other bus types may be used. The expansion bus 170 may include slots for various devices, the examples shown including a controller 186, e.g., a USB controller 186, shown in FIG. 3A coupled to the carrier 110 (as also shown in FIG. 1A), and a network controller 184 shown in FIG. 3B coupling to the carrier 110 over a network, as described above with reference to FIG. 1B. In both embodiments shown, the carrier 110 is coupled to a measurement module 108 (or multiple measurement modules), which may itself be coupled to a sensor 112 as shown.

The computer 102 may further comprise a video display subsystem 180 and hard drive 182 coupled to the expansion bus 170, also shown. It should be noted that the network controller 184 may be any type of network controller, including Ethernet, wireless Ethernet, Bluetooth, and CAN, among others. Furthermore, the USB controller shown is meant to be illustrative only, i.e., any other type of controller may be used as desired to communicate with the carrier 110. In other embodiments, the controller 186 may be comprised in the bus controller 168, or may be implemented in any other forms customary and known in the art. Of course, the embodiments shown in FIGS. 3A and 3B may be combined in various ways, such as, for example, coupling to a first carrier through a controller, and coupling to a second carrier via a network.

FIGS. 4A and 4B--Measurement Modules with a Functional Unit

FIGS. 4A and 4B are block diagrams of embodiments of a measurement module 108 where the measurement module 108 includes one or more functional units 106. As mentioned above, a functional unit refers to either a processor 306 and memory (or multiple processors and/or memories) or one or more programmable hardware elements 308, such as an FPGA, or various combinations thereof.

FIG. 4A--A Measurement Module with Processor

FIG. 4A is a block diagram of a measurement module 108A including a processor 306, e.g., a micro-controller. As FIG. 4A shows, the measurement module 108A may include measurement circuitry which is operable to perform one or more of signal conditioning and signal conversion. For example, in one embodiment, the measurement circuitry may include a signal conditioner 302 and/or a signal converter 304, such as an analog to digital converter (ADC) 304, as shown. In other embodiments, the signal converter 304 may comprise a digital to analog converter, or other types of signal converter, as desired.

The measurement module 108A may also include interface circuitry which is operable to provide an interface for the measurement circuitry. In one embodiment, the interface circuitry may be operable to couple to a carrier unit 110, and may also be operable to communicate an interface protocol to the carrier unit 110 describing the interface.

In the embodiment shown in FIG. 4A, the interface circuitry includes micro-controller 306 and memory 307, such as an EEPROM 307, containing a DAQ Electronic Data Sheet (EDS), defined by IEEE 1451.2, and an optional calibration history.

IEEE 1451.2 defines an interface between tra