Automated combined display of measurement data

Description

BACKGROUND

Measurement tools such as digital multimeter (DMM) devices, heat-sensing infrared cameras, vibration meters, and the like are used in a wide array of industrial, commercial, and residential settings to measure a variety of properties of equipment. In production facilities, plants, and factories, for example, it is critical to ensure that equipment remains operational. Interruptions in production for unexpected failure of equipment can be costly. Such facilities typically establish procedures for routine monitoring and maintenance of equipment that include using measurement tools.

For example, a technician using a handheld measurement tool may be tasked to periodically measure a property of equipment to assess the functional “health” of the equipment or to determine the presence of a fault. To perform such measurements, the technician travels to the site of the equipment, manually records data from the measurement tool, and returns to a central location to produce a report. Unfortunately, the technician may need to return multiple times to the site of the equipment to obtain the desired data. Further, analysis of measured data obtained from the equipment often requires the technician to manually enter the measured data into a computer.

In some instances, an equipment maintenance process includes obtaining readings of measurement data from multiple measurement tools at different locations, and sometimes includes obtaining measurements simultaneously or in close time proximity. Furthermore, complex calculations may be desired to be quickly performed on measured data obtained at the different locations, even when using measurement tools with limited or no functionality for storing or processing measurements over time. What is desired are systems and methods that allow guidance and coordination to be provided with respect to collecting measurements using measurement tools, and that allow measurement data to be efficiently collected and processed.

SUMMARY

The following summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This summary is not intended to identify key features of the claimed subject matter, nor is it intended to be used as an aid in determining the scope of the claimed subject matter.

In some embodiments, a computer-implemented method for automatically generating a combined display of measurement data is provided. A mobile computing device establishes communication connections with a plurality of measurement devices configured to generate measurement data. The mobile computing device receives measurement data generated by the plurality of measurement devices and, in response to information indicative of the measurement data representing related parts of a combined measurement, the mobile computing device automatically groups the measurement data received from the plurality of measurement devices and automatically displays the grouped measurement data in a combined display of the measurement data that shares at least one axis of measurement. For example, the combined measurement may be a multiphase parameter in which the related parts are the individual phases of the parameter. The measurement data received from each measurement device may represent a phase of the multiphase parameter.

According to further aspects, the multiphase parameter may be an electrical parameter having at least three component phases. The combined display may include three component phases of a three-phase voltage, current, or power parameter, and wherein the at least one axis of measurement represents time.

According to further aspects, the information indicative of the measurement data representing related parts of a combined measurement may include time information indicating a proximity of time when the measurement data was generated by the plurality of measurement devices. The time information may indicate that the measurement data was generated by the measurement devices during an overlapping time interval.

According to further aspects, the information indicative of the measurement data representing related parts of a combined measurement may include location information indicating a proximity of location where the measurement data was generated by the plurality of measurement devices. The location information may indicate that the measurement data was generated by the measurement devices at an equipment test point.

According to further aspects, the combined display of the measurement data may share at least two axes of measurement. The combined display may be a graph of the measurement data, and the measurement data received from the plurality of measurement devices may be superimposed in the graph using the at least two axes of measurement.

DESCRIPTION OF THE DRAWINGS

The foregoing aspects and many of the attendant advantages of this invention will become more readily appreciated as the same become better understood by reference to the following detailed description, when taken in conjunction with the accompanying drawings, wherein:

FIG. 1 is a schematic diagram that illustrates, at a high level, an exemplary embodiment of a system according to various aspects of the present disclosure;

FIG. 2 is a block diagram that illustrates an exemplary mobile computing device according to various aspects of the present disclosure;

FIG. 3 is a block diagram that illustrates an exemplary embodiment of a measurement device according to various aspects of the present disclosure;

FIG. 4 is a block diagram that illustrates an exemplary embodiment of a measurement processing server according to various aspects of the present disclosure;

FIG. 5 is a flowchart that illustrates an exemplary embodiment of a method of collecting and annotating test measurements using a mobile computing device according to various aspects of the present disclosure;

FIG. 6 is a flowchart that illustrates an exemplary method of processing measurement data for multiple units of equipment to generate a unified data collection and reporting interface according to various aspects of the present disclosure; and

FIG. 7 is a flowchart that illustrates an exemplary method for automatically generating a combined display of measurement data representing a combined measurement.

DETAILED DESCRIPTION

In various embodiments, disclosed herein are systems and methods for capturing, storing, analyzing, and reporting data obtained from measurement devices, such as handheld measurement tools and other sensors that perform measurements of equipment. Such systems and methods are useful, in part, for improving the speed, accuracy, and ease of use of measurement data collected from measurement devices, especially where the measurement data results from multiple simultaneous or near simultaneous measurements of different types of data.

As will be better understood from the following description, the term “measurement data” refers to data that is generated by a measurement device and directly or indirectly relates to or reflects a measured property of a device under test. In various embodiments, measurement devices may measure many types of properties, such as electrical and/or mechanical properties. Properties that may be measured by measurement devices include, for example and without limitation, electrical current, voltage, resistance, capacitance, inductance, vibration, humidity, pressure, light, time, temperature, sound, material composition, and the like.

FIG. 1 is a schematic diagram that illustrates, at a high level, an exemplary embodiment of a system according to various aspects of the present disclosure. In the illustrated embodiment, the system 100 includes a mobile computing device 104. The mobile computing device 104 is configured to interact with at least one measurement device 108 positioned with respect to equipment to be measured, such as the illustrated device under test (DUT) 92.

In some embodiments, the mobile computing device 104 may be a general purpose mobile computing device, such as a smart phone that provides cellular telephony, cellular data, Bluetooth, Wi-Fi, and/or other types of wireless connectivity, which is further programmed to provide functions as described herein. An application (or “app”) executing on the mobile computing device 104 may provide processes for data collection, storage, analysis, and communication as described herein. A user interface 106 is presented by the mobile computing device 104, which allows a user to view data that is collected and analyzed by the computing device 104, and to control the collection, processing, storage, and transmission thereof as discussed further below.

In various embodiments, the measurement device 108 may be, for example, a measurement tool such as a DMM, a Wi-Fi network tester, a vibration tester, an infrared or thermal imaging camera, and/or the like that is capable of measuring a property of a DUT 92 and providing measurement data based thereon. Generally, measurement devices 108 may be handheld or portable, and may include any type of testing or sensing device or multipurpose device capable of performing a measurement or a combination of types of measurements. Measurement devices 108 may also include single purpose or multi-purpose sensors that are capable of measuring properties of equipment.

In various embodiments, data communication between measurement devices 108 and the mobile computing device 104 may be wireless or wired, and may use any type of standardized or proprietary communication protocol. Current standardized protocols for wired communication include, for example, USB, Firewire, Ethernet, and the like, while wireless data communication may be performed using ZigBee, Bluetooth, Wi-Fi, cellular data transmission protocols, and the like. The communication may be a direct communication between the measurement device 108 and the mobile computing device 104, or may take place over a network with one or more intervening network devices providing a communication path. In some embodiments, at least some of the processing described herein as being performed by the mobile computing device 104 could be performed by the measurement processing server 102. In such embodiments, the measurement device 108 may be configurable to communicate directly with the measurement processing server 102 via a wireless or wired communication path, and may use any type of standardized or proprietary communication protocol, including but not limited to the illustrated network 90.

In an environment where multiple measurement devices 108 are used to measure different properties of equipment, the mobile computing device 104 may be configured to choose measurement devices 108 with which to communicatively interact to receive measurement data, as well as analyze, display, and further communicate the measurement data to one or more locations remote from the equipment and/or the mobile computing device 104.

In at least one implementation, a user may establish communication links between the mobile computing device 104 and one or more measurement devices 108 that are positioned with respect to one or more DUTs 92. As each communication link is established, measurement data generated by the respective measurement devices 108 may automatically be communicated to the mobile computing device 104. When measurement data is no longer received from a measurement device 108, e.g., the measurement device 108 drops out of range of the mobile computing device 104, the mobile computing device 104 discontinues or releases the communication link. As will be discussed in greater detail below, measurement data previously received from the measurement device 108 may be stored by the mobile computing device 104 in association with the measurement device 108 and/or the test point (or points) being measured on the equipment, but upon discontinuing or releasing the communication link, the mobile computing device 104 no longer displays live data measurements from the measurement device 108 nor indicates an active communication link with the measurement device 108.

When the user no longer desires to receive measurement data from a particular measurement device 108, the user may cause the mobile computing device 104 to disconnect or release the communication link with the measurement device 108. Subsequently, the measurement device 108 may return to a low power operational mode in which the measurement device 108 periodically communicates a presence detect signal, as previously described. If desired, the measurement device 108 may be configured to locally store measurement data in a data store present on the measurement device 108, which later may be read by a mobile computing device 104 upon establishing a new communication link with the measurement device 108.

In some wireless environments, the mobile computing device 104 may be paired with a measurement device 108 in order to receive measurement data from the measurement device 108. Pairing adds a layer of security over such communication between the measurement device 108 and the mobile computing device 104 in that establishing a communication link with the measurement device 108 may utilize additional data that is typically accessible only to persons or devices authorized to engage in such communication.

As measurement data is received, the mobile computing device 104 may display the measurement data to the user via the user interface 106. In some embodiments, the displayed measurement data represents instantaneous measurements received from the measurement devices 108. When storage of the measurement data is desired, the user may initiate collection of the measurement data, such as by pressing a “Capture” or “Record” button on the user interface 106. For example, in at least one implementation, pressing a “Capture” button on the user interface 106 may cause the mobile computing device 104 to save a single set of the measurement data obtained at an instance of time. On the other hand, by pressing a “Record” button, the user may initiate a recording of multiple sets of the measurement data in which the mobile computing device 104 saves a time series of the measurement data received from the measurement device 108. If desired, such recordings may be presented to the user as a data graph or an image video on the display of the mobile computing device 104.

In some embodiments, the data obtained by the mobile computing device 104 may further include status or safety information regarding the measurement device 108 (as opposed to the DUT 92). For instance, if the status of the measurement device 108 justifies display of a warning light on the measurement device 108, information regarding that status may be transmitted to the mobile computing device 104 and a corresponding icon may be displayed on the mobile computing device 104 noting the condition of the measurement device 108. Some nonlimiting examples of a status that would justify the display of a warning light include a low battery status, an out-of-range indicator, a lead indicator, and the like. This may be particularly helpful to a user whose mobile computing device 104 is connected to multiple measurement devices 108. Such icon display helps the user to recognize when one or more of the measurement devices 108 need attention to ensure that correct measurement data is being obtained.

In some embodiments, data may also be conveyed between a measurement device 108 and the mobile computing device 104 using techniques other than via a communication protocol as described above. As a nonlimiting example, in some embodiments, data may be exchanged between the measurement device 108 and the mobile computing device 104 through transfer of physical media, such as a memory card that is transferred between memory slots in the measurement device 108 and the mobile computing device 104. As another nonlimiting example, in some embodiments, data may be displayed by the measurement device 108 in a human-readable format (such as via an analog instrument meter with analog display, or via a LCD or other indicator that presents a digital value) and the mobile computing device 104 may obtain the measurement data by capturing and processing an image of the measurement device 108. In yet another nonlimiting example, in some embodiments, data may be displayed by the measurement device 108, and a user may manually enter the data into the mobile computing device 104 via the user interface 106.

While in some embodiments, the mobile computing device 104 is the device in the system 100 responsible for obtaining, processing, and storing measurement data from measurement devices 108, in other embodiments, the mobile computing device 104 may also or instead communicate the measurement data to one or more measurement processing servers 102, which may be located at one or more local or remote locations. Such communication may be performed through a network 90 such as a wired or wireless network, and may involve local, wide area, or global data communication links, such as the Internet. In some embodiments, such communication may be performed by syncing the mobile computing device 104 to another computing device (such as a desktop computing device, a laptop computing device, a tablet computing device, and/or the like) via a dock, a physical communication cable, a wireless communication technology, or a network, and the other computing device may then act as the measurement processing server 102. In some embodiments, the other computing device may receive the data from the mobile computing device 104 and then subsequently transmit the data to the measurement processing server 102 via the network 90. In some embodiments, the mobile computing device 104 may obtain, process, and store the measurement data locally while unable to access the network 90, such as when there is no access to a cellular data network due to a lack of wireless signal strength at a measurement location. The mobile computing device 104 may then transmit the measurement data to one or more measurement processing servers 102 as discussed above upon being reconnected to a network 90 or otherwise communicatively coupled to another computing device.

FIG. 2 is a block diagram that illustrates an exemplary mobile computing device 104 according to various aspects of the present disclosure. As illustrated, the mobile computing device 104 may include a processor 211, at least one communication interface 224, at least one data storage device 217, and at least one input/output (I/O) interface 222, among other elements. As used herein, the term processor is not limited to integrated circuitry otherwise referred to as a computer, but broadly refers to a microcontroller, a microcomputer, a microprocessor, a programmable logic controller, an application specific integrated circuit, other programmable circuits, combinations of the above, and/or the like. The processor 211 generally serves as a computational center of the mobile computing device 104 by supporting the execution of instructions that cause the device to receive, store, analyze, and communicate data using the communication interface 224, the storage device 217, and/or the input/output interface 222.

The communication interface 224 may include one or more components configured to communicate with external devices, such as another mobile computing device, a computer system at a remote location, a measurement device 108, and/or the like. All such communication may be wired or wireless. In some embodiments, the mobile computing device 104 may process measurement data into different forms and communicate the processed measurement data to such external devices. In some embodiments, the measurement data is organized and stored by the mobile computing device 104 in the storage device 217. The stored measurement data may later be retrieved, analyzed, and communicated.

The storage device 217 may comprise any form of computer-readable storage media, such as any currently available or later developed media suitable for storing computer-executable instructions and data that are accessible to one or more device components, such as the processor 211. Computer-readable storage media may be removable or nonremovable and may be volatile or nonvolatile. Examples of computer-readable storage media may include hard drives as well as RAM, ROM, EEPROM, flash types of memory, and/or the like.

The input/output interface 222 may include one or more input devices such as dials, switches, or buttons, and one or more output devices, such as a display or printer. Generally, the input/output interface 222 allows a user or an external system to interact with programs being executed by the mobile computing device 104. In at least one embodiment, the input/output interface 222 allows a user to control or configure the mobile computing device 104 to receive data from a measurement device 108 and to analyze, store, and/or communicate the measurement data to an external device. Information regarding the configuration of measurement devices and the equipment properties that they measure may be stored in the storage device 217 and used by the processor 212 when interacting with the measurement devices 108.

As an output device, a display may include, without limitation, a liquid crystal display (LCD), a light emitting diode (LED) device, an organic light emitting diode (OLED) device, and/or the like. The display may be capable of displaying color images, though embodiments disclosed herein also work with black and white displays. The display may include a touch screen that, in some embodiments, incorporates aspects of an input device into the display. The touch screen may be any type of touch screen currently known or later developed. For example, the touch screen may be a capacitive, infrared, resistive, or surface acoustic wave (SAW) device. In response to input received by the input device, the mobile computing device 104 may receive, analyze, store, and communicate data related to measurement of properties of equipment. In some measurement applications, the touch screen may be suitable for use in industrial settings, for example, where the touch screen is configured to receive inputs through gloved hands.

In addition to a touch screen or other display, the input/output interface 222 of the mobile computing device 104 may further include one or more input devices that communicate an input to the mobile computing device 104. As mentioned earlier, such input device may include, as examples, buttons, switches, trigger switches, selectors, rotary switches, or other input devices known to those of ordinary skill in the art. In at least one embodiment, measurement devices may be configured to perform measurements in response to user input or user selection of an input that is provided to the mobile computing device 104 via the one or more input devices.

As illustrated, the processor 211 may be configured to provide one or more engines. In general, the term “engine,” as used herein, refers to logic embodied in hardware or software instructions, which can be written in a programming language, such as C, C++, COBOL, JAVA™, PHP, Perl, HTML, CSS, JavaScript, VBScript, ASPX, Objective C, Ruby, Microsoft .NET™ languages such as C #, and/or the like. An engine may be compiled into executable programs or written in interpreted programming languages. Software engines or applications may be callable from other engines or from themselves. Generally, the engines described herein refer to logical modules that can be merged with other engines or applications, or can be divided into sub-engines. The engines can be stored in any type of computer-readable medium or computer storage device, such as the storage device 217, and be stored on and executed by one or more general purpose processors (such as processor 211), thus creating a special purpose computing device configured to provide the engine. In some embodiments, the engines described herein may be incorporated into one or more applications or “apps” installed on the mobile computing device 104. The illustrated engines may be provided by the processor 211 in response to execution by the processor of computer-executable instructions stored on a computer-readable medium, such as the storage device 217.

As illustrated, the engines provided by the processor 211 may include a user interface engine 212, a measurement collection engine 214, and a measurement processing engine 216. The measurement collection engine 214 is configured to interact with one or more measurement devices 108 via the communication interface 224. The measurement collection engine 214 may instruct the measurement devices 108 to obtain measurement data, and may receive measurement data from the measurement devices 108. The measurement collection engine 214 may also store the received measurement data in the measurement data store 220. Additionally, the measurement collection engine 214 may receive warning status information from the measurement devices 108, and may cause the user interface engine 212 to present corresponding icons and/or notifications. The measurement processing engine 216 may perform processing over measurements stored in the measurement data store 220, or may process measurements obtained by the measurement collection engine 214 before storage in the measurement data store 220. For example, the measurement processing engine 216 may group measurements with other related measurements, may assign metadata to a received measurement, and/or perform other processing on the measurements as described elsewhere herein. As will be described below, the metadata includes group identifying information that associates the stored measurement data with other data annotated with similar group identifying information.

The user interface engine 212 is configured to generate a user interface for presentation to a user via the input/output interface 222 of the mobile computing device 104. The user interface generated by the user interface engine 212 may allow the user to configure the measurement collection engine 214 to communicate with various measurement devices 108, and may allow the user to configure the measurement devices 108 to capture measurements per the user's input. The user interface generated by the user interface engine 212 may allow the user to instruct the measurement collection engine 214 to store a given measurement or a time series of measurements, may allow the user to observe currently obtained measurements, and may allow the user to browse and/or compare previously collected and stored measurements.

In some embodiments, the interface provided by the user interface engine 212 may also provide guidance to the user for assisting in collecting measurements. For example, in some embodiments, the user interface engine 212 may be configured to present a task list to the user representing a set of measurements to be obtained. In some embodiments, the user interface engine 212 may be configured to present a map to the user in order to guide the user to a location at which measurements are to be obtained, to assist the user in identifying equipment from which measurements have been obtained, and/or to assist the user in locating test points to be monitored on the equipment.

As illustrated, the storage device 217 may include a work order data store 215, a facility data store 218, a measurement data store 220, and an equipment data store 221. The measurement data store 220 may be configured to store measurements received by the mobile computing device 104, and also may be configured to store metadata associated with said measurements. The facility data store 218 may be configured to store information about a facility, such as floor plans, equipment locations, identifiers of installed equipment, test points on the equipment, and/or the like. The equipment data store 221 may be configured to store information about equipment that has been monitored (or is intended to be monitored in the future) using the system 100. For example, in some embodiments the equipment data store 221 may store information associated with units of equipment such as location information, model information, make information, equipment identifiers, photos, and test points. The work order data store 215 may be configured to store work order information that helps guide a user through a series of measurements to be completed. In some embodiments, the work order data store 215 may also be configured to store progress information along with a given work order to indicate which tasks within the work order have been completed and which are yet to be performed.

As understood by one of ordinary skill in the art, a “data store” as described herein may be any suitable device, or a data structure on a computer-readable medium, configured to store data for access by a computing device. One example of a data store is data stored in an organized manner on a storage medium such as storage device 217. Another example of a data store (which may be more relevant to the data stores provided by the measurement processing server 102 described further below) is a highly reliable, high-speed relational database management system (DBMS) executing on one or more computing devices and accessible over a high-speed packet switched network. Yet another example of a data store is a non-relational network-based storage system, such as the Amazon S3 store provided by Amazon.com, Inc., Google Cloud Storage provided by Google, Inc., a distributed hash table (DHT), and/or the like. However, any other suitable storage technique and/or device capable of quickly and reliably providing the stored data in response to queries may be used to provide a data store, and the computing device may be accessible locally instead of over a network, or may be accessible over some other type of suitable network or provided as a cloud-based service. For example, though the data stores in FIG. 2 are illustrated as being present on the storage device 217 of the mobile computing device 104, in some embodiments, the data stores may not be resident on the mobile computing device 104 but may instead be remotely accessible by the mobile computing device 104. One of ordinary skill in the art will recognize that separate data stores described herein may be combined into a single data store, and/or a single data store described herein may be separated into multiple data stores, without departing from the scope of the present disclosure.

FIG. 3 is a block diagram that illustrates an exemplary embodiment of a measurement device according to various aspects of the present disclosure. As illustrated, the measurement device 108 includes one or more sensors 330, and optionally includes a machine interface 324, a human-readable interface 326, and a measurement data store 328.

The sensors 330 are devices associated with the measurement device 108 that collect information regarding properties of a device under test, and convert the information to a useable form. For example, a voltage sensor may sense a voltage across two test leads applied to the device under test, and may output a value indicating the sensed voltage for use by other components of the measurement device 108. Likewise, a temperature sensor may detect a temperature of a portion of the device under test, and may output a value indicating the temperature. In some embodiments, the sensors 330 may be integrated into a single case along with the rest of the components of the measurement device 108. In some embodiments, one or more of the sensors 330 may be located external from a case containing other components of the measurement device 108, and may communicate to the measurement device 108 using any suitable technique.

In some embodiments, the measurement device 108 may include one or more sensors 330 that are placed on or near test points of the equipment to be measured. Such sensors 330 may be temporarily affixed to the equipment or to structures near the equipment. Alternatively or in addition, the sensors 330 may be incorporated into test devices that a user can relocate from one test point to another on the equipment as needed.

In some embodiments, the measurement device 108 may be a handheld measurement tool. A handheld measurement tool is generally configured to be held in a user's hand while measuring a property of equipment. However, it should be appreciated that a handheld measurement tool need not always be held in a user's hand and may be positioned by a user away from the user's hand, for example, by affixing or hanging the tool from a support or placing the tool on or near a test point on the equipment to be measured. In some embodiments, the measurement device 108 is a device other than a handheld measurement tool. For example, the measurement device 108 may be, for example, a portable measurement tool that is not necessarily intended to be used while held in the hand. While not permanently connected to the equipment being measured, such portable tools are useful for measuring properties of the equipment over days or weeks, as desired.

In some instances, the measurement device 108 may log measurements of equipment properties over time, and may store the measurements in the measurement data store 328. Later, the mobile computing device 104 may obtain the measurements stored in the measurement data store 328. In some embodiments, the stored measurements may be obtained by the mobile computing device 104 via the machine interface 324, if the machine interface 324 is available, or via the human-readable interface 326, if the human-readable interface 326 is available and provides access to the stored measurements.

In some embodiments, the measurement data store 328 may be omitted. In such embodiments, the mobile computing device 104 may collect measurements from the sensors 330 via the machine interface 324 or the human-readable interface 326 as they are obtained by the sensors 330. The mobile computing device 104 may then provide storage functionality by storing the measurements in the measurement data store 220, thus allowing historical measurements to be collected, analyzed, and presented even when the measurement device 108 does not itself include a measurement data store 328. When desired, the mobile computing device 104 may display one or more graphs showing the measurement data as received over time, even from the measurement devices 108 that do not include the measurement data store 328.

The machine interface 324 may be any suitable machine-readable interface, such as a wireless communication interface or a wired communication interface as discussed above. In some embodiments, the machine interface 324 may be used to obtain measurements from the sensors 330 in real time or substantially in real time as measurements are obtained by the sensors 330, with or without the measurements being stored in the measurement data store 328. In some instances, the measurement device 108 may also include a human-readable interface 326. The human-readable interface 326 may display values obtained by the sensors 330 to the user in real time or substantially real time, and may provide access to stored past measurements in the measurement data store 328. The human-readable interface 326 may include a video display, a LCD display, an analog display, an indicator light, or any other suitable display. In some embodiments, similar information may be obtained via the machine interface 324 and the human-readable interface 326, while in some embodiments, different information may be obtained via the two interfaces.

FIG. 4 is a block diagram that illustrates an exemplary embodiment of a measurement processing server 102 according to various aspects of the present disclosure. As illustrated, the measurement processing server 102 may be configured to provide a facility data store 404, a measurement data store 406, an equipment data store 408, and a work order data store 409. The facility data store 404, the measurement data store 406, and the work order data store 409 may be configured to store information similar to that stored by the facility data store 218, the measurement data store 220, and the work order data store 215, respectively, discussed above with respect to FIG. 2. However, in some embodiments, the data stores present on the measurement processing server 102 may receive and store data collected by more than one mobile computing device 104, or provided by multiple management computing devices for distribution to mobile computing devices 104. This may be useful for many purposes, including but not limited to comparing measurements taken of similar equipment at different locations and different times, centralized distribution of task lists and equipment information, and the like.

The equipment data store 408 may be configured to store information about equipment of particular makes, models, and/or the like. For example, for a given piece of equipment, the equipment data store 408 may store maintenance guidelines, user manuals, standard specifications, normal operating parameters, testing instructions, and/or the like. This information may be provided to a mobile computing device 104 to assist in performing measurements. The facility data store 404 may include unique identifiers used to identify particular installations of equipment at a facility, and may refer to information stored in the equipment data store 408 to provide further description of the equipment.

One of ordinary skill in the art will recognize that the illustration of components as being present on the measurement processing server 102 is exemplary only, and that in some embodiments, components of measurement processing server 102 may instead be located on the mobile computing device 104, or split between the measurement processing server 102 and the mobile computing device 104.

FIG. 5 is a flowchart that illustrates an exemplary embodiment of a method 500 of collecting and annotating test measurements using a mobile computing device 104, according to various aspects of the present disclosure. From a start block, the method 500 proceeds to a continuation terminal (“terminal A”), and from terminal A to block 502, where a mobile computing device 104 guides a technician to a measurement location. Generally, a measurement location is a location at which a mobile computing device 104 can communicate with a measurement device 108 configured to measure properties of a device under test. In some embodiments, the measurement location may be in close proximity to the device under test, such that a handheld or other portable measurement device 108 may be placed in contact with the device under test or otherwise obtain measurement data from the device under test. In some embodiments, the measurement location may be in proximity to a network via which the mobile computing device 104 may communicate with a measurement device 108 configured to measure properties of a device under test at a different location. In some embodiments, the mobile computing device 104 may guide the technician to the measurement location by presenting a map, floor plan, or travel directions to the technician. In some embodiments, it may be assumed that the technician knows the location of the device under test, and the mobile computing device 104 may guide the technician to the measurement location by presenting a task list and an indication of the device to be tested.

Next, at block 504, one or more measurement devices 108 are positioned with respect to a device under test (DUT) 92, as illustrated in FIG. 1. For example, a sensor of the measurement device 108 may be placed in physical or electrical contact with the DUT 92 to detect a property such as vibration, voltage, resistance, and/or the like. As another example, a sensor of the measurement device 108 capable of sensing properties without being in physical contact with the DUT 92, such as a clamp meter, an infrared camera, and/or the like, may be positioned to sense a property of the DUT 92. One of ordinary skill in the art will recognize that, in some embodiments, the actions described in blocks 502 and 504 may be swapped in order, such as in embodiments where the measurement devices are left in position for monitoring the DUT 92 even between collections of measurements using a mobile computing device 104.

At block 506, the mobile computing device 104 establishes communication links with one or more selected measurement devices 108. The communication links may include transmission of data via a communication protocol or by any other technique discussed above or otherwise known to one of ordinary skill in the art. In some cases, the measurement devices 108 may initially operate in a mode in which the measurement devices 108 periodically communicate a signal indicating their presence, which the mobile computing device 104 can detect. The user may be required to initiate an input, such as press a button, on the measurement devices 108 or otherwise cause the measurement devices 108 to commence communicating such a presence detect signal. In any event, upon detection of the presence of one or more measurement devices 108, the mobile computing device 104 may display the availability of the measurement devices 108 to the user via the user interface 106.

The user may indicate to the mobile computing device 104 the particular measurement device 108 or devices that should be linked to the mobile computing device 104 for communication of measurement data. For example, in at least one implementation, the user may press particular buttons on the mobile computing device 104 that are associated with the available measurement devices 108. As another example, the user may touch particular text or icons on the user interface 106 presented on a touchscreen of the mobile computing device 104 to indicate a desire to link the mobile computing device 104 with the measurement devices 108. In response to such user indication, the mobile computing device 104 establishes communication links with the indicated measurement devices 108, e.g., by responding to the presence detect signal that is periodically sent by the measurement devices 108. The measurement devices 108 and the mobile computing device 104 may exchange configuration information that allows for exclusive or nonexclusive communication of measurement data from the measurement devices 108. In yet other embodiments, the mobile computing device 104 may automatically establish communication links with all measurement devices 108 that it detects.

Next, at block 508, a measurement collection engine 214 of the mobile computing device 104 receives measurement data from the one or more selected measurement devices 108. In some embodiments, the measurement data may be received via a network or wireless protocol of the communication link. In some embodiments, the measurement data may be received via other means. As nonlimiting examples, in some embodiments, the measurement data may be received by exchanging a tangible computer-readable medium between the mobile computing device 104 and a measurement device 108, by manual entry of the measurement data into the mobile computing device 104 by the technician, by capturing an image of the measurement device 108 using a camera of the mobile computing device 104, and/or using any other suitable technique. The measurement data may include a single value representing a property of the DUT 92 at a given time, or may include multiple values representing a time series of values representing a property of the DUT 92 over a period of time. At block 510, the measurement collection engine 214 records a set of received measurement data in a measurement data store 220. The set of received measurement data may include a single reading from a single sensor 330, multiple readings from a single sensor 330, or one or more readings from multiple sensors 330.

The method 500 then proceeds to block 512, where a measurement processing engine 216 of the mobile computing device 104 annotates the recorded set of measurement data in the measurement data store 220 with metadata. In some embodiments, the metadata used to annotate the recorded set of measurement data may include information describing when, where, and how the information was collected including, but not limited to: a timestamp; a GPS location (or a location obtained using other positioning technology) of the mobile computing device 104 and/or the measurement device 108; an equipment identifier that either uniquely identifies the DUT 92 or identifies a type or model of the DUT 92; an identifier of the measurement device 108; a record of settings of the measurement device 108; the particular test point or points on the DUT 92; a work order, task list, or job instruction that directed the collection of the measurement data; an identity of the technician collecting the measurement data; a text note; a voice note; an image; a video; an image annotation; and/or the like. In some instances, the DUT 92 may be labeled with human perceptible data, such as on a sticker, hang tag, or the like, that identifies the particular equipment. The technician may enter the equipment identity into the mobile computing device 104 based on the labeled data. In other instances, the DUT 92 may be labeled with a machine readable code, such as a barcode, a QR code, or a radio frequency identification (RFID) tag, that the technician can scan using the mobile computing device 104. Alternatively or in addition, the equipment identity and other information may be provided by a barcode or QR code printed on a work order delivered to the technician conducting the equipment measurements. The equipment identity corresponding to the scanned code can then be automatically stored in the metadata of the measurement data that is automatically being associated in a particular data group.

In some embodiments, the metadata used to annotate the recorded set of measurement data may include group identifying information. The group identifying information may associate the recorded set of measurement data with other recorded sets of measurement data, and this association may then be used to display or otherwise process the grouped sets measurement data together. In some embodiments, the group identifying information may include one or more group identifiers that may be automatically associated with the recorded set of measurement data. In at least one implementation, the mobile computing device 104 may associate measurement data into a group based on an element that is common to the metadata of each received data measurement, such as time information that reflects when the data was measured. For example, measurement data that is captured simultaneously or near in time to each other, such as within a predetermined amount of time of each other, from various measurement devices 108 may automatically be grouped into a single data group, and the data group may be associated with a particular test point or group of test points of the DUT 92. The identity of the test point or group of test points may be supplied by the user, either before, during, or after receipt of the measurement data. In other implementations, the identity of the test point or group of test points may automatically be obtained from the DUT 92, from the measurement devices 108, or from the mobile computing device 104 or other devices. For example, a GPS circuit in a measurement device 108 may provide location data that can be included with or otherwise associated with the measurement data being transmitted to the mobile computing device 104. In some cases, the location data may be associated in a memory or other storage device with one or more test points. The location data may be used (e.g., as an index or keyword for look up in a table) to identify particular test points associated with the location, either in the measurement devices 108 or in the mobile computing device 104.

For example, multiple sets of measurement data taken with different measurement devices 108 of the same DUT 92 (such as visual images, infrared images, and/or thermal images captured by a camera or thermal imager, electrical measurements such as voltage, current, or impedance measurements captured by a DMM, and measurement of mechanical parameters such as vibration or pressure captured by portable sensors, and/or the like) obtained at substantially the same time (such as, for example, within a few seconds or minutes of each other) may be grouped together to be displayed and/or analyzed as part of a single test. Said grouping may also be based on group identifying information specified by the technician or on some other piece of common metadata other than the timestamp. For example, measurement data captured within a predetermined distance of each other as determined by a positioning system may be grouped together.

As another example, sets of measurement data taken of different DUTs 92 that are the same type of equipment (such as, for example, two different units of the same model of a motor) may be grouped together to provide comparisons between multiple separate units. The mobile computing device 104 may also be configured to receive text, capture an image, or record audio or video initiated by the technician, such as a voice comment or text annotation of measurement data or as a recording of equipment appearance or sound, and associate such text, image, or audio/video recordings with the measurement data in a particular group. As yet another example, a technician may provide commentary on observations of the DUT 92 at the time the measurement data is obtained. Such commentary may be received from the technician before, during, or after the data measurements occur. By saving the user-initiated text or audio/video recordings with metadata that is held in common with the measurement data, the text or audio/video recordings may likewise be associated in the same group with the measurement data.

A feature of the present disclosure is that group identifying information may be generated either before, during, or after the measurement data is obtained. In instances where measurement data is captured before the group identifying information is generated, the measurement data may automatically be associated in a group according to parameters such as the time or location when the data is measured or transmitted.

Automatically generated groups may be presented to the technician with a prompt for the technician to confirm the automatically generated information or to supply further group identifying information. The technician can input information pertaining to the group and have the information stored in the metadata. For example, the technician may enter information regarding the measured equipment and have the identity of the equipment stored with the measurement data in the group. In some embodiments, the technician manually inputs the identity of the measured equipment. In other embodiments, the mobile computing device 104 may display a list of previously identified equipment and allow the technician to select the equipment being measured. If the equipment being measured is not included in the displayed list, the technician may initiate a prompt on the mobile computing device 104 that allows the technician to create a new equipment identity and store the equipment identity in the list for later retrieval when the equipment is again being measured. In yet other embodiments, the mobile computing device 104 may receive or sense location data (e.g., through a GPS reading or other positioning technology) and automatically provide a list of known equipment associated with the location data, from which the technician can select the equipment record matching the DUT 92. In still other embodiments, the mobile computing device 104 may automatically generate a group based on work order data, either by grouping all measurements gathered while processing a work order, by obtaining equipment identifiers using the work order data, and/or using any other suitable technique.

Next, the method 500 proceeds to a decision block 514, where a determination is made regarding whether more devices remain to be tested. If the result of the determination at decision block 514 is YES, the method 500 proceeds to terminal A, and the actions discussed with respect to blocks 502 through 514 are repeated for the next device to be tested. Otherwise, if the result of the determination at decision block 514 is NO, the method 500 proceeds to an end block and terminates.

In various embodiments, data groups that have been generated by the mobile computing device 104 may be presented to the user in a variety of formats for viewing, analyzing, and reporting. For example, a textual description of a data group or a visual graph of measurement data in the data group may be shown to the user. In instances where a data group includes a large amount of measurement data, the user may be presented with a small portion or short description of the measurement data with a prompt that the user may select to receive additional detail regarding the data measurements in the group. If desired, the user may divide the measurement data in a data group into two or more smaller data groups. Information that distinguishes the two or more smaller groups is stored in the metadata of the data measurements pertaining to the smaller groups.

By automatically associating data into data groups, an improved process is provided for easily organizing and presenting the measurement data to the user in a clear, straightforward, and visual manner. The measurement data is packaged and/or formatted in a way that makes it easy for the user and others to analyze the data in the different data groups and evaluate the status of the equipment being measured.

In some embodiments, the system 100 disclosed herein may be particularly useful for large organizations that have a desire to monitor or otherwise measure a large number of units of equipment, or to monitor or otherwise measure a large number of properties of a given unit of equipment. Accordingly, some embodiments of the present disclosure further provide a unified data collection and reporting interface for equipment being measured. These embodiments include processes for collecting data from disparate measurement devices positioned to obtain measurements of equipment in one or more locations, storing the measurement data in one or more associated data structures, and reporting the measurement data in a unified display.

One example of a unified display is a single, scrollable “equipment page” presented by the user interface engine 212 that is associated with particular equipment and provides a view of the measurement data captured and/or processed with regard to the equipment. By storing and displaying disparate data collected with regard to a given unit or type of equipment on a single page, a user is able to evaluate both historical data and presently measured data, observe trends in the data, determine the status of the equipment, and predict future maintenance needs of the equipment. Such analysis may be conducted by a technician on site with the equipment or by management personnel and/or experts at remote locations that have access to the unified data collection and reporting interface for the equipment.

In some cases, it may be helpful to a user to compare the measurement data of particular equipment to the measurement data of similar equipment in other locations, particularly if the health status of the other equipment has already been established. Equipment pages for installations of similar equipment may be displayed in a manner (e.g., side-by side or picture-in-picture) that facilitates comparison of the measurement data obtained from a DUT 92 to overall trends shown in other installations of similar equipment. Comparing the DUT 92 with similar equipment in other locations may facilitate evaluation of a health status of the DUT 92.

FIG. 6 is a flowchart that illustrates an exemplary method 600 of processing measurement data for multiple units of equipment to generate a unified data collection and reporting interface according to various aspects of the present disclosure. From a start block, the method 600 proceeds to block 602, where measurement data is transmitted to and stored by a measurement data store 406 of a measurement processing server 102. The measurement data stored in block 602 represents measurements collected from one or more units of equipment. In some embodiments, the measurement data may have been collected using a method similar to the method illustrated in FIG. 5 and discussed above, though in other embodiments, any other suitable method may be used to obtain the measurement data. Next, at block 604, the measurement processing server 102 stores annotations for the measurement data to link the measurement data to one or more equipment records in an equipment data store 408. In some embodiments, the annotation that links the measurement data to one or more equipment records may be an equipment identifier that uniquely identifies an equipment record in the equipment data store 408, and may be added along with the rest of the metadata stored with the measurement data. One of ordinary skill in the art may consider the actions described above in blocks 602-604 as providing the system 100 with historical measurement data for use in creating the unified data collection and reporting interface as described below.

Once the system 100 has obtained some historical measurement data for equipment to be compared to the DUT 92, a unified data collection and reporting interface may be generated by the system 100. Accordingly, the method 600 proceeds to block 606, where a mobile computing device 104 is connected to one or more measurement devices 108 configured to collect measurement data from one or more DUT 92, as described above. Next, at block 608, a user interface engine 212 of the mobile computing device 104 receives an indication of an equipment identifier associated with the DUT 92. The equipment identifier may be provided in a human-perceptible form on a name plate, hang tag, sticker, label, and/or the like attached to the DUT 92. In some embodiments, the equipment identifier may be entered into the mobile computing device 104 by manual entry, by scanning of text on the DUT 92, by scanning a bar code or QR code label, and/or by any other suitable technique, similar to the techniques discussed above. Meanwhile, in other embodiments, the equipment identifier may be determined by the technician selecting equipment matching the DUT 92 from the unified data collection and reporting interface presented by the user interface engine 212.

Production plants, factories, facilities, etc., typically have multiple installations of equipment of a given type at different locations. The unified data collection and reporting interfaces for different equipment installations may be organized in the mobile device and in remote data processing centers to enable a technician to quickly identify and select particular equipment for viewing of the corresponding interface. In various embodiments, attributes such as equipment name, type, location, and status may be used to distinguish different installations of equipment. The unified data collection and reporting interfaces for the different equipment installations may include such equipment attributes. The equipment attributes may be displayed to facilitate user identification and selection of a desired installation of equipment.

For example, the location of equipment may be identified by a textual description of the equipment's surroundings. Alternatively or in addition, graphical depictions illustrating the location of the equipment relative to its surroundings may be provided. For example, a map showing a floor plan of a factory or facility having multiple equipment installations may be shown with icons representing particular equipment installations within the factory or facility. The icons may be positioned within an image of the floor plan to illustrate the respective locations of the equipment. In instances where the map is larger than the available area on the display, the depiction of the map may be scrollable in one or more dimensions to enable easy access to the complete floor plan map.

In some embodiments, the map may be a formal illustration of a floor plan. In other embodiments, the map may be a hand drawn sketch generated by a technician and saved in the unified data collection and reporting interface for the equipment. The image of the floor plan may be, for example, a photograph of a sketch or formal illustration on paper, or it may be a sketch drawn directly onto the screen of the display. Images of the equipment stored in the unified data collection and reporting interface for the equipment may further facilitate identification of the particular equipment. Depicting a floor plan map or other graphical image of equipment surroundings may help a technician to physically find particular equipment. Accordingly, a technician sent to measure data with regard to particular equipment may be guided when attempting to locate the equipment on site.

In some embodiments, the map data may include GPS or other positioning information. In such embodiments, a mobile computing device 104 capable of receiving or generating GPS data may superimpose an icon onto a depiction of the map indicating the position of the mobile computing device 104 relative to equipment and other surroundings in the map. Such depictions may further guide a technician sent to measure data with regard to particular equipment.

A technician may also use map data to identify particular equipment that the technician is seeking to evaluate. For example, in at least one embodiment, a graphical map may be displayed to the technician showing various equipment installations. The technician can then touch or click a mapped location on the display to select particular equipment at that location. Selection of the particular equipment causes the equipment identifier for that equipment to be selected.

Alternatively or in addition to graphically depicting a map showing equipment installations, a mobile computing device 104 may display a listing of building areas or room types (potentially organized in a hierarchy) that enables a technician to identify and select particular equipment for evaluation. An exemplary embodiment may provide a list of building areas, such as basement, floor, wall, or roof, that are associated with the locations of different equipment. Upon selection of a building area, the mobile computing device 104 may further display a more detailed list of rooms or locations within the selected building area. Upon selection of a room or location within the building area, the technician may then be provided a listing of equipment in the selected room or location. Eventually, the technician is able to identify and select particular equipment based on its relative location in the building, and thereby select the equipment identifier to be used.

Another exemplary embodiment may provide a listing of room types, such as boiler room, machine room, assembly floor, laboratory, office, and/or the like, where equipment is located. Upon selection of a room type, the mobile computing device 104 may further display a more detailed list of rooms that match the selected room type. Thereafter, upon selection of a particular room, the technician may be provided a listing of equipment in the selected room. The technician may then identify and select particular equipment from the list. Selection of particular equipment from the list causes the equipment identifier for that equipment to be used. In some embodiments, the map information, the locations of equipment, and/or the like may be stored in the facility data store 404 and obtained therefrom by the mobile computing device 104.

Once the equipment identifier is obtained, the method 600 proceeds to block 610, where the user interface engine 212 submits a request for equipment information associated with the equipment identifier to the measurement processing server 102. At block 612, the measurement processing server 102 transmits an equipment record associated with the equipment identifier to the mobile computing device 104.

At block 614, the measurement processing server 102 transmits stored measurement data associated with the equipment record to the mobile computing device 104. Once the mobile computing device 104 has received the stored measurement data and/or the equipment record, the method 600 proceeds to block 616, where the user interface engine 212 presents a unified data collection and reporting interface for the DUT 92 using the equipment record and the stored measurement data.

In various embodiments, the unified data collection and reporting interface for particular equipment may be configured to present reference documents stored in the equipment record that are helpful to the technician and others. For example, the equipment record may hold safety manuals or maintenance guidelines that the technician and others can access while operating the equipment, making measurements, or evaluating measurement data. In addition, work orders pertaining to the equipment and subsequent reports may be stored in the equipment record for later access.

In various embodiments, the unified data collection and reporting interface for particular equipment may also be configured to present the stored measurement data, either by itself or side-by-side with a current measurement value. For example, the interface may present a graph that shows trends in a measurement value over time for a given DUT 92, or for all similar measurement values collected from equipment of the same equipment type, and may also present the current measurement value for comparison. In various embodiments, the interface for particular equipment may also include features such as a status bar that quickly illustrates the current status of the equipment. For example, a green status bar may indicate equipment in good maintenance condition, while a yellow or red status bar may indicate equipment needing further attention. The status may be updated by a technician, or may be automatically determined by comparing a current measurement value or values to the stored measurement data or to acceptable values stored in the equipment record. The interface may include images of the equipment taken before, during, or after measurement data is obtained. Images of the equipment obtained over time may be compared to identify changes indicative of future maintenance needs. If desired, a tool may be provided in which a previously obtained image of the equipment is superimposed on an image to be taken or presented side-by-side with an image to be taken, allowing the technician to align the two images, which facilitates later comparison of the images. In some embodiments, the tool may also provide the ability to compare two previously obtained images for comparison to each other, either in a side-by-side presentation or superimposed on one another. In some embodiments, the tool may provide the ability to provide a side-by-side or superimposed comparison of images of different units of equipment. The interface may include collections of measurement data organized into groups as described above. A technician viewing the equipment page for particular equipment may select one or more of the data groups for further viewing and analysis.

When providing measurement data for viewing and analysis, the unified data collection and reporting interface may automatically provide graphs of the measurement data collected over time. Alternatively or in addition, data captured at a particular instance of time may be displayed as a static numerical value. Image data stored in the measurement data store 406 or equipment data store 408 may be displayed as images in the interface. Such images may be shown along with graphs and/or static numerical values of other measurement data to enable a broader, holistic view of the equipment. As will be understood by one of ordinary skill in the art, when image data is discussed herein, said image data may include visible light image data, infrared image data, or any other suitable type of image data whether in a visible light spectrum or not.

Once the user has finished interacting with the unified data collection and reporting interface, the method 600 proceeds to an end block and terminates.

In some embodiments, the system 100 may be configurable to automatically generate reports in formats other than the unified data collection and reporting interface as well. For example, in some embodiments the mobile computing device 104, the measurement processing server 102, or some other computing device associated with the system 100 may include a report definition. The report definition may include measurements to be reported in a particular format, such as a regulatory form and/or the like. Upon collection of measurements to be entered in the form, the system 100 may automatically generate a report in the format indicated in the report definition, and may provide the report for submission to a regulatory agency, for storage in a record associated with the DUT, and/or the like.

The present disclosure further provides automated processes for providing a combined display of measurement data that represents related parts of a combined measurement. In some cases, the combined measurement may be a multiphase parameter and the related parts of the combined measurement are the component phases of the multiphase parameter. A multiphase parameter may comprise multiple components that differ from one another according to a phase of the respective component. One example of a multiphase parameter is three-phase power in a three-phase power system.

As discussed above, in one example the mobile computing device 104 may receive measurement data from a plurality of current-sensing and/or voltage-sensing measurement devices 108 and establish communication connections with each of the measurement devices 108. The mobile computing device 104 may receive the measurement data from the measurement devices 108 during an overlapping time interval, as recognized by a timestamp or other time information associated with the measurement data indicating when the measurement data was generated by the measurement devices 108 and/or received by the mobile computing device 104. Such time information may indicate a time proximity when the measurement data was generated by the measurement devices 108. In view of this time information, the mobile computing device 104 may automatically associate, or group together, such measurement data as discussed above in greater detail.

In accordance with the present disclosure, the mobile computing device 104 may further consider such time information indicative of the measurement data representing related parts of a combined measurement and automatically display the grouped measurement data in a combined display of the measurement data that shares at least one axis of measurement. In at least one embodiment, the combined display may be a graph depicting the measurement data sharing at least one axis of measurement. Typical axes of measurement are time and magnitude.

For example, the mobile computing device 104 may establish communication connections with three current-sensing or three voltage-sensing measurement devices 108 and simultaneously receive measurement data from the measurement devices. Based on time information associated with the measurement data, the mobile computing device 104 may not only group the measurement data together but interpret the measurement data as representing component parts of a three-phase power signal, where the measurement data from each measurement device 108 represents a particular phase of the power signal.

Instead of displaying three separate graphs of the measurement data (i.e., a separate graph with separate axes of measurement for the measurement data from each of the three measurement devices), as may be done with conventional systems, the mobile computing device 104 of the present disclosure is configured to automatically generate and present a single graph displaying the current or voltage measurements of the three phases together, without requiring user input to cause preparation of such a graph. In some cases, the combined display of the measurement data may share at least two axes of measurement. In cases where the combined display provides a graph of the measurement data, the display of each set of measurement data may be superimposed on one another in the graph using, for example, magnitude and time as the shared axes of measurement. By superimposing the measurement data in a combined graph with at least two shared axes of measurement, the magnitude and phase relationships between the different components of the multiphase parameter are more easily observed.

As another example of a combined measurement, the mobile computing device 104 may receive multiple temperature measurements from measurement devices 108 placed in an HVAC system. The measurement devices 108 may be configured to measure the temperature of different parts of the HVAC system, such as the burner, flue, or air duct, etc. By receiving and evaluating the measurement data from the measurement devices 108 in a combined display as discussed above, a user of the mobile computing device 104 may assess the health of the HVAC system by looking at relationships between the multiple temperature measurements. For example, one may expect the flue temperature of the HVAC system to track with changes in the boiler temperature. A too-rapid rise in the air duct temperature after a rise in the burner temperature may indicate a crack in the heat exchanger, while a too-slow rise in the air duct temperature might indicate a blockage. By automatically grouping the multiple temperature measurements together as a combined measurement for the HVAC system, the health of the HVAC system may be more easily assessed. Similar considerations may be given to other systems in which multiple measurements of equipment in the systems may be considered related parts of a combined measurement and the measurement data may be automatically grouped together for a combined display, in accordance with the present disclosure.

FIG. 7 is a flowchart that illustrates an exemplary method 700 for automatically generating a combined display of measurement data representing a combined measurement. As a first step at block 702, the communication interface 224 of a mobile computing device 104 establishes communication connections with a plurality of measurement devices 108. Next, at block 704, a measurement collection engine 214 of the mobile computing device 104 receives measurement data from the plurality of measurement devices. At this point, the mobile computing device 104 is configured to evaluate available information that may indicate that the measurement data represents related parts of a combined measurement, as indicated at decision block 706.

As one example described above, information indicative of the measurement data representing related parts of a combined measurement may include time information indicating proximity of time when the measurement data was generated by the plurality of measurement devices. In particular, the time information may indicate that the measurement data was generated by the measurement devices during an overlapping time interval. Simultaneous generation of measurement data by multiple measurement devices, particularly when measuring the same parameter, may be interpreted as indicating a combined measurement, such as a measurement of a multiphase parameter.

As another example, information indicative of the measurement data representing related parts of a combined measurement may include location information indicating proximity of location where the measurement data was generated by the plurality of measurement devices. In particular, the location information may indicate that the measurement data was generated by the measurement devices at an equipment test point. The mobile computing device may automatically interpret the proximity of location of the measurement devices as measuring the same test point of the equipment, wherein each measurement device is sensing a related part of the combined measurement, such as a particular phase of a multiphase parameter.

In contrast to conventional systems that display different sets of measurement data in separate graphs and require careful manipulation of the data by a user in order to join the different sets of measurement data into a single graph, the present disclosure provides a method, system, and computer-readable medium in which a combined display of measurement data representing a combined measurement is automatically presented in a combined display. In some embodiments, the combined display may be a graph that graphically depicts the measurement data. In other embodiments, the combined display may be a numerical or other non-graphical display. In any event, a combined display advantageously facilitates faster evaluation of the measurement data when the measurement data represents a combined measurement, such as a multiphase parameter.

For example, in a three-phase power system as described above, the mobile computing device 104 of the present disclosure can detect receipt of multiple current or voltage measurements and interpret the current or voltage measurements as representing measurements of the same test point of a three-phase power system. Accordingly, the mobile computing device 104, or other computing device in the system, can automatically produce a combined display of the three-phase measurement data as discussed above.

A user desiring to measure and evaluate the different phases of a three-phase power system need only position the three current or voltage measurement devices 108 with regard to the component parts of the three-phase power system being measured and establish communication connections between the mobile computing device 104 and the measurement devices 108. The mobile computing device 104 receives the measurement data from the measurement devices 108 and, as described above, automatically generates and presents a combined display, such as a graph providing a graphical depiction of the three different phases. This is particularly useful, for example, when the user desires to quickly evaluate whether a load placed on a three-phase power system is balanced.

Returning to FIG. 7, if the mobile computing device 104 determines that the measurement data represents related parts of a combined measurement, the measurement processing engine 216 of the mobile computing device 104 automatically groups the measurement data, as indicated at block 708. The grouped measurement data is then processed and provided to the input/output interface 222 as indicated at block 710, for automatically displaying the grouped measurement data in a combined display that shares at least one axis of measurement, as described above.

While embodiments of systems and methods have been illustrated and described in the foregoing description, it will be appreciated that various changes can be made therein without departing from the spirit and scope of the present disclosure. For example, while embodiments of the mobile computing device have been described in the context of a smart phone executing one or more programmed applications, other embodiments of the mobile computing device may include a handheld measurement tool that is additionally capable of measuring properties of equipment. The measurement devices, as indicated earlier, may include handheld measurement tools as well as multipurpose and single use sensors that are positioned relative to equipment to be measured. Computer-executable instructions that cause one or more computing devices to perform processes as described herein may be stored in a nontransitory computer readable medium accessible to the one or more computing devices. Moreover, it should be understood that rearrangement of structure or steps in the devices or processes described herein that yield similar results are considered within the scope of the present disclosure. Accordingly, the scope of the present disclosure is not constrained by the precise forms that are illustrated for purposes of exemplifying embodiments of the disclosed subject matter.

Claims

1. A computer-implemented method for automatically generating a combined display of measurement data, the method comprising: establishing, by a mobile computing device, communication connections with a plurality of measurement devices configured to measure electrical or mechanical properties of equipment and generate measurement data based on the electrical or mechanical properties of the equipment;receiving, by the mobile computing device, the measurement data generated by the plurality of measurement devices;after receiving the measurement data, determining whether the measurement data represents related parts of a combined measurement, wherein said determining whether the measurement data represents related parts of a combined measurement is based on location information indicating a proximity of respective physical locations of the plurality of measurement devices; andin response to determining that the measurement data represents related parts of a combined measurement: automatically grouping the measurement data that was determined to represent related parts of a combined measurement to produce grouped measurement data; andautomatically displaying the grouped measurement data in a combined display of in which the grouped measurement data, as displayed, shares at least one axis of measurement.
2. The method of claim 1, wherein the combined measurement is a multiphase parameter, and the measurement data received from each measurement device represents a phase of the multiphase parameter.
3. The method of claim 2, wherein the multiphase parameter is an electrical parameter having at least three component phases.
4. The method of claim 3, wherein the combined display includes three component phases of a three-phase voltage, current, or power parameter, and wherein the at least one axis of measurement represents time.
5. The method of claim 1, wherein determining whether the measurement data represents related parts of a combined measurement is further based on time information indicating a proximity of time when the measurement data was generated by the plurality of measurement devices.
6. The method of claim 5, wherein the time information indicates that the measurement data was generated by the plurality of measurement devices during an overlapping time interval.
7. The method of claim 1, wherein the location information indicates a proximity of location where the measurement data was generated by the plurality of measurement devices.
8. The method of claim 7, wherein the location information indicates that the measurement data was generated by the plurality of measurement devices at an equipment test point.
9. The method of claim 1, wherein the grouped measurement data, as displayed in the combined display, shares at least two axes of measurement.
10. The method of claim 9, wherein the combined display is a graph of the grouped measurement data, and wherein the grouped measurement data is superimposed in the graph using the at least two axes of measurement.
11. A system for automatically generating a combined display of measurement data, the system comprising: a mobile computing device configured to: establish communication connections with a plurality of measurement devices configured to measure electrical or mechanical properties of equipment and generate measurement data based on the electrical or mechanical properties of the equipment;receive the measurement data generated by the plurality of measurement devices;after receiving the measurement data, determine whether the measurement data represents related parts of a combined measurement, wherein the measurement data is determined to represent related parts of a combined measurement based on location information indicating a proximity of respective physical locations of the plurality of measurement devices; and in response to determining that the measurement data represents related parts of a combined measurement: automatically group the measurement data that was determined to represent related parts of a combined measurement to produce grouped measurement data; andautomatically display the grouped measurement data in a combined display in which the grouped measurement data, as displayed, shares at least one axis of measurement.
12. The system of claim 11, wherein the combined measurement is a multiphase parameter, and the measurement data received from each measurement device represents a phase of the multiphase parameter.
13. The system of claim 12, wherein the multiphase parameter is an electrical parameter having at least three component phases.
14. The system of claim 13, wherein the combined display includes three component phases of a three-phase voltage, current, or power parameter, and wherein the at least one axis of measurement represents time.
15. The system of claim 11, wherein the mobile computing device is further configured to determine whether the measurement data represents related parts of a combined measurement based on time information indicating a proximity of time when the measurement data was generated by the plurality of measurement devices.
16. The system of claim 15, wherein the time information indicates that the measurement data was generated by the plurality of measurement devices during an overlapping time interval.
17. The system of claim 11, wherein the location information indicates a proximity of location where the measurement data was generated by the plurality of measurement devices.
18. The system of claim 17, wherein the location information indicates that the measurement data was generated by the plurality of measurement devices at an equipment test point.
19. The system of claim 11, wherein the grouped measurement data, as displayed in the combined display, shares at least two axes of measurement.
20. The system of claim 19, wherein the combined display is a graph of the grouped measurement data, and wherein the grouped measurement data is superimposed in the graph using the at least two axes of measurement.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No. 14/214,662, filed Mar. 15, 2014, which claims the benefit of U.S. Provisional Application No. 61/801,380, filed Mar. 15, 2013, and U.S. Provisional Application No. 61/876,719, filed Sep. 11, 2013, the disclosures of which are incorporated by reference herein in their entirety.

US Referenced Citations (732)

Number	Name	Date	Kind
4644320	Carr et al.	Feb 1987	A
4717872	Wagner et al.	Jan 1988	A
4754218	Wagner et al.	Jun 1988	A
5146371	Hamada	Sep 1992	A
5172052	Wells	Dec 1992	A
5371842	Easton	Dec 1994	A
5386117	Piety et al.	Jan 1995	A
5428342	Enoki et al.	Jun 1995	A
5493287	Bane	Feb 1996	A
5594332	Harman et al.	Jan 1997	A
5637871	Piety et al.	Jun 1997	A
5650771	Lee	Jul 1997	A
5664207	Crumpler et al.	Sep 1997	A
5748104	Argyroudis et al.	May 1998	A
5767667	Shafie	Jun 1998	A
5992237	McCarty et al.	Nov 1999	A
6122603	Budike, Jr.	Sep 2000	A
6184798	Egri	Feb 2001	B1
6195018	Ragle	Feb 2001	B1
6202491	McCarty et al.	Mar 2001	B1
6219340	Cutler	Apr 2001	B1
6229526	Berstis	May 2001	B1
6243105	Hoyer	Jun 2001	B1
6261230	Bardy	Jul 2001	B1
6280380	Bardy	Aug 2001	B1
6298308	Reid et al.	Oct 2001	B1
6336900	Alleckson et al.	Jan 2002	B1
6363057	Ardalan et al.	Mar 2002	B1
6363488	Ginter et al.	Mar 2002	B1
6437692	Petite et al.	Aug 2002	B1
6441723	Mansfield, Jr. et al.	Aug 2002	B1
6489884	Lamberson et al.	Dec 2002	B1
6496705	Ng	Dec 2002	B1
6501983	Natarajan et al.	Dec 2002	B1
6502063	Eriksson	Dec 2002	B1
6538577	Ehrke	Mar 2003	B1
6571140	Wewalaarachchi et al.	May 2003	B1
6684245	Shuey et al.	Jan 2004	B1
6826514	Antico	Nov 2004	B1
6862540	Welch	Mar 2005	B1
6885309	Van Heteren	Apr 2005	B1
6891478	Gardner	May 2005	B2
6934862	Sharood et al.	Aug 2005	B2
6956500	Ducharme et al.	Oct 2005	B1
6985819	Lipscomb et al.	Jan 2006	B2
6993417	Osann, Jr.	Jan 2006	B2
7076239	Kirkup et al.	Jul 2006	B2
7130844	Elder	Oct 2006	B2
7149285	Kennedy	Dec 2006	B2
7191184	Laborde et al.	Mar 2007	B2
7236900	Hagen	Jun 2007	B2
7289887	Rodgers	Oct 2007	B2
7304618	Plathe	Dec 2007	B2
7310583	De La Quintana	Dec 2007	B2
7312603	Luo et al.	Dec 2007	B2
7317404	Cumeralto et al.	Jan 2008	B2
7327228	Min	Feb 2008	B2
7338443	Tucker	Mar 2008	B1
7382247	Welch et al.	Jun 2008	B2
7385524	Orlosky	Jun 2008	B1
7423985	Hill	Sep 2008	B1
7424527	Petite	Sep 2008	B2
7454050	Garvey	Nov 2008	B2
7478305	Betawar et al.	Jan 2009	B2
7480501	Petite	Jan 2009	B2
7528372	Garvey, III et al.	May 2009	B2
7535378	Cornwall	May 2009	B2
7541941	Bogolea et al.	Jun 2009	B2
7561200	Garvey, III et al.	Jul 2009	B2
7561867	Frye, Jr.	Jul 2009	B2
7616110	Crump et al.	Nov 2009	B2
7703032	Wells	Apr 2010	B2
7706596	Garvey	Apr 2010	B2
7728275	Blanchard	Jun 2010	B2
7746092	Li	Jun 2010	B2
7791351	Raber	Sep 2010	B2
7813822	Hoffberg	Oct 2010	B1
7848905	Troxler et al.	Dec 2010	B2
7902507	Garvey, III et al.	Mar 2011	B1
7907995	Nagata	Mar 2011	B2
7917382	Cereghini et al.	Mar 2011	B2
7960965	Lund	Jun 2011	B2
7995830	Garvey	Aug 2011	B2
8003942	Garvey, III et al.	Aug 2011	B2
8005576	Rodgers	Aug 2011	B2
8024724	Garrison Stuber et al.	Sep 2011	B2
8036597	Rahman et al.	Oct 2011	B2
8085143	Hollander et al.	Dec 2011	B2
8090480	Brumfield et al.	Jan 2012	B2
8094034	Patel et al.	Jan 2012	B2
8119986	Garvey, III et al.	Feb 2012	B1
8124923	Blanchard	Feb 2012	B2
8131489	Heuser	Mar 2012	B2
8148687	Praly	Apr 2012	B1
8170722	Elberbaum	May 2012	B1
8233486	Phuah et al.	Jul 2012	B2
8269650	Cornwall et al.	Sep 2012	B2
8300922	Garvey, III	Oct 2012	B1
8319658	Conant	Nov 2012	B2
8334513	Garvey, III et al.	Dec 2012	B1
8339093	Lu	Dec 2012	B2
8358903	Meads et al.	Jan 2013	B1
8368001	Blanchard	Feb 2013	B2
8410931	Petite et al.	Apr 2013	B2
8427006	Gilbert	Apr 2013	B2
8432154	Lund	Apr 2013	B2
8447541	Rada	May 2013	B2
8450995	Wagner	May 2013	B2
8456278	Bergman et al.	Jun 2013	B1
8489063	Petite	Jul 2013	B2
8502821	Louise	Aug 2013	B2
8576231	Woodings	Nov 2013	B2
8581743	Chan et al.	Nov 2013	B2
8618930	Papadopoulos et al.	Dec 2013	B2
8639465	Elberbaum	Jan 2014	B1
8643539	Pauly et al.	Feb 2014	B2
8665082	Glenn et al.	Mar 2014	B2
8707193	Khazanov et al.	Apr 2014	B2
8712732	Patel	Apr 2014	B2
8738925	Park	May 2014	B1
8754779	Ruther	Jun 2014	B2
8836318	Cheng et al.	Sep 2014	B2
8870086	Tessier et al.	Oct 2014	B2
8880092	Cooley	Nov 2014	B1
8884553	Hai	Nov 2014	B2
8902249	Wilson et al.	Dec 2014	B1
8976039	O'Hara et al.	Mar 2015	B2
8983785	Panko	Mar 2015	B2
9076275	Chinnadurai et al.	Jul 2015	B2
9081829	Bhave	Jul 2015	B2
9117251	Schmidt et al.	Aug 2015	B2
9151818	Danesh et al.	Oct 2015	B2
9172275	Bhakta	Oct 2015	B2
9191286	Lachapelle	Nov 2015	B2
9197949	Indovina et al.	Nov 2015	B2
9250275	Patel et al.	Feb 2016	B2
9319288	Somaiya et al.	Apr 2016	B2
9347796	Rapadas	May 2016	B1
9363148	Somaiya et al.	Jun 2016	B2
9384116	Rider et al.	Jul 2016	B2
9408250	Yi et al.	Aug 2016	B2
9430353	Shafi	Aug 2016	B2
9430558	Bhat et al.	Aug 2016	B2
9438300	Oliaei	Sep 2016	B1
9449408	Benson et al.	Sep 2016	B2
9454820	Kirmani et al.	Sep 2016	B1
9467745	Hotchkiss	Oct 2016	B1
9477784	Bhave et al.	Oct 2016	B1
9489745	Heitz, III et al.	Nov 2016	B1
9495187	Bingham et al.	Nov 2016	B2
9501555	Zhou et al.	Nov 2016	B2
9501849	Wong et al.	Nov 2016	B2
9541472	Neeley et al.	Jan 2017	B2
9557720	Woods	Jan 2017	B1
9563218	Hall	Feb 2017	B2
9564945	Goyal	Feb 2017	B1
9704369	Richardson et al.	Jul 2017	B2
9733974	Bingham et al.	Aug 2017	B2
9753935	Tobin	Sep 2017	B1
9766270	Heydron	Sep 2017	B2
9773330	Douglas et al.	Sep 2017	B1
9778285	Fox	Oct 2017	B2
9792020	Kelley	Oct 2017	B1
9864383	Reider et al.	Jan 2018	B2
9866026	Nomura	Jan 2018	B2
9887541	Hall	Feb 2018	B2
9900560	Kirmani et al.	Feb 2018	B1
9946288	Sato et al.	Apr 2018	B2
9955527	Uchida	Apr 2018	B2
9995655	Dagnino et al.	Jun 2018	B2
10019890	Tanaka	Jul 2018	B2
10054464	Quady	Aug 2018	B2
10067038	Hou	Sep 2018	B2
10088389	Neeley et al.	Oct 2018	B2
10095659	Katz et al.	Oct 2018	B2
10120021	Silva	Nov 2018	B1
10128937	Yamazaki	Nov 2018	B2
10129611	Primm	Nov 2018	B2
10209271	Epperson	Feb 2019	B2
10216695	Shankar et al.	Feb 2019	B1
10312681	Aiello	Jun 2019	B2
10337946	Tan	Jul 2019	B1
10417224	Duffield	Sep 2019	B2
10453573	Greene et al.	Oct 2019	B2
10509061	Brown	Dec 2019	B2
10530666	Venkitapathi	Jan 2020	B2
10540053	Gasperi	Jan 2020	B2
10555057	Koezuka	Feb 2020	B2
10571493	Sonderegger	Feb 2020	B2
10614132	Bingham	Apr 2020	B2
10628442	Naskar	Apr 2020	B1
10666048	Hall	May 2020	B2
10734838	Roytelman	Aug 2020	B2
10748406	Boerhout	Aug 2020	B2
10812957	Wallington	Oct 2020	B2
10908188	Laurino	Feb 2021	B2
10998709	Wulfekuhle	May 2021	B1
11190017	Rothschild	Nov 2021	B1
20010001850	Miller	May 2001	A1
20010025138	Bardy	Sep 2001	A1
20010038343	Meyer	Nov 2001	A1
20010051764	Bardy	Dec 2001	A1
20020190208	Wood	Dec 2002	A1
20020193144	Belski et al.	Dec 2002	A1
20030020759	Cancilla	Jan 2003	A1
20030050737	Osann, Jr.	Mar 2003	A1
20030058243	Faust	Mar 2003	A1
20030128212	Pitkow	Jul 2003	A1
20030135338	Knaus	Jul 2003	A1
20030158677	Swarztrauber et al.	Aug 2003	A1
20030216971	Sick et al.	Nov 2003	A1
20040028023	Mandhyan et al.	Feb 2004	A1
20040032433	Kodosky	Feb 2004	A1
20040034496	Correll	Feb 2004	A1
20040061623	Tootoonian Mashhad	Apr 2004	A1
20040066309	Jang	Apr 2004	A1
20040113810	Mason, Jr.	Jun 2004	A1
20040140908	Gladwin et al.	Jul 2004	A1
20040197040	Walker et al.	Oct 2004	A1
20040227501	Wobben	Nov 2004	A1
20040249605	Komatsu	Dec 2004	A1
20040253997	Kochie	Dec 2004	A1
20050060107	Rodenberg, III et al.	Mar 2005	A1
20050065743	Cumming	Mar 2005	A1
20050125512	Fuller, III et al.	Jun 2005	A1
20050132241	Curt et al.	Jun 2005	A1
20050171411	KenKnight	Aug 2005	A1
20050184882	Angelis	Aug 2005	A1
20050194962	Briese et al.	Sep 2005	A1
20050195757	Kidder et al.	Sep 2005	A1
20050212526	Blades	Sep 2005	A1
20050225347	Khandros et al.	Oct 2005	A1
20050237221	Brian	Oct 2005	A1
20050240540	Borleske	Oct 2005	A1
20050270151	Winick	Dec 2005	A1
20050278007	Godara	Dec 2005	A1
20050289264	Illowsky et al.	Dec 2005	A1
20060022663	Chen	Feb 2006	A1
20060062190	Suga	Mar 2006	A1
20060071812	Mason	Apr 2006	A1
20060097713	Brandt	May 2006	A1
20060101311	Lipscomb	May 2006	A1
20060136825	Cory et al.	Jun 2006	A1
20060145890	Junker et al.	Jul 2006	A1
20060167638	Murphy et al.	Jul 2006	A1
20060189871	Al-Ali et al.	Aug 2006	A1
20060202816	Crump et al.	Sep 2006	A1
20060217936	Mason	Sep 2006	A1
20060256786	Bibr et al.	Nov 2006	A1
20070001868	Boaz	Jan 2007	A1
20070007968	Mauney, Jr. et al.	Jan 2007	A1
20070013547	Boaz	Jan 2007	A1
20070038591	Haub et al.	Feb 2007	A1
20070057814	Goldberg et al.	Mar 2007	A1
20070067360	Engel	Mar 2007	A1
20070083307	Pasztor	Apr 2007	A1
20070100520	Shah	May 2007	A1
20070100666	Stivoric et al.	May 2007	A1
20070118310	Kindseth	May 2007	A1
20070118323	Ishizuka	May 2007	A1
20070126731	Sabram	Jun 2007	A1
20070127833	Singh	Jun 2007	A1
20070156313	Fudali	Jul 2007	A1
20070156373	Yamashita et al.	Jul 2007	A1
20070176933	Culpi et al.	Aug 2007	A1
20070179754	Sper	Aug 2007	A1
20070182584	Ogino	Aug 2007	A1
20070198222	Schuster et al.	Aug 2007	A1
20070244668	Huck	Oct 2007	A1
20070297112	Gilbert	Dec 2007	A1
20080012701	Kass	Jan 2008	A1
20080036466	Raber	Feb 2008	A1
20080042641	Stockman	Feb 2008	A1
20080046387	Gopal et al.	Feb 2008	A1
20080046414	Haub et al.	Feb 2008	A1
20080046457	Haub et al.	Feb 2008	A1
20080046838	Haub et al.	Feb 2008	A1
20080052017	Smith et al.	Feb 2008	A1
20080068217	Van Wyk et al.	Mar 2008	A1
20080068994	Garrison Stuber et al.	Mar 2008	A1
20080077336	Fernandes	Mar 2008	A1
20080082278	Tan	Apr 2008	A1
20080091345	Patel et al.	Apr 2008	A1
20080148877	Sim	Jun 2008	A1
20080161957	Rice et al.	Jul 2008	A1
20080224892	Bogolea et al.	Sep 2008	A1
20080231719	Benson et al.	Sep 2008	A1
20080269932	Chardon et al.	Oct 2008	A1
20090017816	Chainer	Jan 2009	A1
20090031042	Phatak	Jan 2009	A1
20090045804	Durling et al.	Feb 2009	A1
20090054743	Stewart	Feb 2009	A1
20090072985	Patel et al.	Mar 2009	A1
20090088991	Brzezowski et al.	Apr 2009	A1
20090109021	Paoletti	Apr 2009	A1
20090128124	Garland	May 2009	A1
20090128127	Garland	May 2009	A1
20090128128	Garland	May 2009	A1
20090135836	Veillette	May 2009	A1
20090141593	Taha	Jun 2009	A1
20090150509	Chang et al.	Jun 2009	A1
20090174603	Scalisi	Jul 2009	A1
20090210814	Agrusa et al.	Aug 2009	A1
20090225229	Kobota	Sep 2009	A1
20090228448	Ivanov	Sep 2009	A1
20090237404	Cannon, III	Sep 2009	A1
20090262138	Bradbury et al.	Oct 2009	A1
20090275805	Lane et al.	Nov 2009	A1
20090281679	Taft	Nov 2009	A1
20090292486	Van Gorp	Nov 2009	A1
20090299940	Hayes	Dec 2009	A1
20090315725	Hollander et al.	Dec 2009	A1
20090326410	James	Dec 2009	A1
20090326731	Bowdry	Dec 2009	A1
20100005331	Somasundaram et al.	Jan 2010	A1
20100014746	Warnke	Jan 2010	A1
20100030289	Casavant et al.	Feb 2010	A1
20100058222	Bergstrom	Mar 2010	A1
20100063785	Pich et al.	Mar 2010	A1
20100102926	Grieve et al.	Apr 2010	A1
20100109842	Patel et al.	May 2010	A1
20100167659	Wagner	Jul 2010	A1
20100174419	Brumfield	Jul 2010	A1
20100179438	Heneghan et al.	Jul 2010	A1
20100214299	Robertson et al.	Aug 2010	A1
20100217099	LeBoeuf et al.	Aug 2010	A1
20100217418	Fontanot	Aug 2010	A1
20100218305	Weston et al.	Sep 2010	A1
20100244868	Cantave et al.	Sep 2010	A1
20100256456	Natarajan	Oct 2010	A1
20100286840	Powell	Nov 2010	A1
20100299284	Gristina et al.	Nov 2010	A1
20100305889	Tomlinson, Jr.	Dec 2010	A1
20100323555	Geiger	Dec 2010	A1
20100329174	Shuey	Dec 2010	A1
20100331651	Groll	Dec 2010	A1
20110012587	Greenberg	Jan 2011	A1
20110012743	Van Gorp	Jan 2011	A1
20110016120	Haughay, Jr.	Jan 2011	A1
20110016517	Kasahara	Jan 2011	A1
20110039571	Bodine	Feb 2011	A1
20110074598	Cornwall	Mar 2011	A1
20110085461	Liu	Apr 2011	A1
20110087461	Hollander et al.	Apr 2011	A1
20110099424	Rivera Trevino et al.	Apr 2011	A1
20110101956	Thorn	May 2011	A1
20110106589	Blomberg	May 2011	A1
20110115640	Jiang et al.	May 2011	A1
20110126142	Zhou	May 2011	A1
20110137678	Williams	Jun 2011	A1
20110153236	Montreuil et al.	Jun 2011	A1
20110184267	Duke	Jul 2011	A1
20110199916	Garrett	Aug 2011	A1
20110200045	Baehre	Aug 2011	A1
20110212700	Petite	Sep 2011	A1
20110243005	Sun	Oct 2011	A1
20110248857	Rutherford et al.	Oct 2011	A1
20110251807	Rada et al.	Oct 2011	A1
20110270797	Adams	Nov 2011	A1
20110285546	Vadali	Nov 2011	A1
20110288810	Ishikawa et al.	Nov 2011	A1
20110288900	McQueen et al.	Nov 2011	A1
20110298301	Wong et al.	Dec 2011	A1
20110307418	Bouzaglo	Dec 2011	A1
20110309820	Khanke et al.	Dec 2011	A1
20110316717	Young et al.	Dec 2011	A1
20120001768	Radosavljevic et al.	Jan 2012	A1
20120004872	Oh	Jan 2012	A1
20120004886	Jordil et al.	Jan 2012	A1
20120007588	Tan	Jan 2012	A1
20120009918	Wu	Jan 2012	A1
20120022815	Murakami et al.	Jan 2012	A1
20120026005	Myoung et al.	Feb 2012	A1
20120029718	Davis	Feb 2012	A1
20120045988	Blanton et al.	Feb 2012	A1
20120046897	Panko	Feb 2012	A1
20120047424	Rothschild	Feb 2012	A1
20120051242	Rigomier et al.	Mar 2012	A1
20120056755	Hanft	Mar 2012	A1
20120062390	Solomon	Mar 2012	A1
20120083682	Klodell	Apr 2012	A1
20120102078	Flick et al.	Apr 2012	A1
20120112701	Ito	May 2012	A1
20120119791	Hsiao	May 2012	A1
20120122480	Scalisi	May 2012	A1
20120130223	Reicher	May 2012	A1
20120138388	Finschi et al.	Jun 2012	A1
20120139952	Imai	Jun 2012	A1
20120143387	Indovina et al.	Jun 2012	A1
20120146788	Wilson	Jun 2012	A1
20120154172	O'Hara et al.	Jun 2012	A1
20120154404	Clement et al.	Jun 2012	A1
20120157009	Hollander et al.	Jun 2012	A1
20120166233	Wengrovitz	Jun 2012	A1
20120172023	Griff	Jul 2012	A1
20120173032	Pamulaparthy et al.	Jul 2012	A1
20120178438	Vashi	Jul 2012	A1
20120181974	Kuniyosi et al.	Jul 2012	A1
20120187883	Valdez et al.	Jul 2012	A1
20120224067	Stuart	Sep 2012	A1
20120229270	Morley et al.	Sep 2012	A1
20120245751	Gow et al.	Sep 2012	A1
20120245878	Kane	Sep 2012	A1
20120265586	Mammone	Oct 2012	A1
20120270505	Prakash et al.	Oct 2012	A1
20120271557	Sekimoto	Oct 2012	A1
20120275651	Brown	Nov 2012	A1
20120278014	Davies	Nov 2012	A1
20120293337	Carlsson	Nov 2012	A1
20120296799	Playfair	Nov 2012	A1
20120296899	Adams	Nov 2012	A1
20120300089	Sbaiz	Nov 2012	A1
20120306882	Kashiwagi et al.	Dec 2012	A1
20120310558	Taft	Dec 2012	A1
20120320189	Stuart	Dec 2012	A1
20120330615	Cornwall	Dec 2012	A1
20130009788	Langenberg	Jan 2013	A1
20130023295	Kasslin	Jan 2013	A1
20130024149	Nayar	Jan 2013	A1
20130027219	Myoung	Jan 2013	A1
20130027220	Marwah	Jan 2013	A1
20130029683	Kim	Jan 2013	A1
20130035871	Mayou et al.	Feb 2013	A1
20130040664	Zhang et al.	Feb 2013	A1
20130041852	Ellis et al.	Feb 2013	A1
20130050246	Barry et al.	Feb 2013	A1
20130051498	Taft	Feb 2013	A1
20130064178	Cs	Mar 2013	A1
20130065633	Sridhara et al.	Mar 2013	A1
20130066576	Cs	Mar 2013	A1
20130069627	Cs	Mar 2013	A1
20130083193	Okuyama et al.	Apr 2013	A1
20130106616	Gustafsson	May 2013	A1
20130106906	Roche et al.	May 2013	A1
20130124136	Neeley	May 2013	A1
20130127904	Dove et al.	May 2013	A1
20130128022	Bose	May 2013	A1
20130137940	Schafer	May 2013	A1
20130147464	Tan	Jun 2013	A1
20130150744	Brattain et al.	Jun 2013	A1
20130158911	Young	Jun 2013	A1
20130162442	Honda	Jun 2013	A1
20130176141	LaFrance	Jul 2013	A1
20130181845	Johnson	Jul 2013	A1
20130197835	Jonsson et al.	Aug 2013	A1
20130204439	Scelzi	Aug 2013	A1
20130204448	Lee et al.	Aug 2013	A1
20130204554	Tuckey et al.	Aug 2013	A1
20130211214	Olsen	Aug 2013	A1
20130211557	O'Brien	Aug 2013	A1
20130211731	Woltman	Aug 2013	A1
20130215154	Ponomarev et al.	Aug 2013	A1
20130215903	Kotlicki et al.	Aug 2013	A1
20130231790	Shao	Sep 2013	A1
20130241743	Loic	Sep 2013	A1
20130241746	McKinley	Sep 2013	A1
20130245965	Kane et al.	Sep 2013	A1
20130249917	Fanning et al.	Sep 2013	A1
20130253882	Park	Sep 2013	A1
20130261821	Lu	Oct 2013	A1
20130262197	Kaulgud	Oct 2013	A1
20130268620	Osminer	Oct 2013	A1
20130271467	Misumi	Oct 2013	A1
20130291060	Moore	Oct 2013	A1
20130297259	Tsao et al.	Nov 2013	A1
20130300747	Wong et al.	Nov 2013	A1
20130307992	Erlandsson et al.	Nov 2013	A1
20130321425	Greene et al.	Dec 2013	A1
20130338958	Shanishchara	Dec 2013	A1
20130342359	Miyaji	Dec 2013	A1
20130344888	Dousse	Dec 2013	A1
20140018111	Farley	Jan 2014	A1
20140028854	Heinke et al.	Jan 2014	A1
20140035607	Heydron et al.	Feb 2014	A1
20140039838	Katz et al.	Feb 2014	A1
20140039842	Yuen et al.	Feb 2014	A1
20140051941	Messerschmidt	Feb 2014	A1
20140052503	Zaloom	Feb 2014	A1
20140067325	McKee	Mar 2014	A1
20140071136	Lang	Mar 2014	A1
20140074257	Bhargava	Mar 2014	A1
20140078151	Garr et al.	Mar 2014	A1
20140095577	Root et al.	Apr 2014	A1
20140142724	Park et al.	May 2014	A1
20140152667	Li et al.	Jun 2014	A1
20140163746	Drew et al.	Jun 2014	A1
20140163927	Molettiere	Jun 2014	A1
20140164611	Molettiere	Jun 2014	A1
20140172772	Sanchez Loureda	Jun 2014	A1
20140180968	Song et al.	Jun 2014	A1
20140184604	Bak et al.	Jul 2014	A1
20140187254	Wang et al.	Jul 2014	A1
20140191573	Chen et al.	Jul 2014	A1
20140210845	Zazueta-Hall	Jul 2014	A1
20140212978	Sharpe, Jr. et al.	Jul 2014	A1
20140215073	Dow et al.	Jul 2014	A1
20140218383	Srivastava	Aug 2014	A1
20140232549	Shin et al.	Aug 2014	A1
20140232553	Venkatraman	Aug 2014	A1
20140236371	Ishihara	Aug 2014	A1
20140259133	Alonso Diaz et al.	Sep 2014	A1
20140266669	Fadell	Sep 2014	A1
20140266765	Neeley et al.	Sep 2014	A1
20140267294	Ma et al.	Sep 2014	A1
20140267296	Neeley	Sep 2014	A1
20140267765	Stuart et al.	Sep 2014	A1
20140270546	Neeley et al.	Sep 2014	A1
20140274114	Rowitch	Sep 2014	A1
20140277792	Kaufman	Sep 2014	A1
20140277814	Hall	Sep 2014	A1
20140277827	Chinnadurai et al.	Sep 2014	A1
20140278255	Anderson	Sep 2014	A1
20140278259	Neeley et al.	Sep 2014	A1
20140279443	Neeley	Sep 2014	A1
20140282145	Dewan	Sep 2014	A1
20140282241	Epperson et al.	Sep 2014	A1
20140289250	Nojima	Sep 2014	A1
20140289251	Nojima	Sep 2014	A1
20140297229	Izumo et al.	Oct 2014	A1
20140300486	Hummel	Oct 2014	A1
20140313205	Huempel et al.	Oct 2014	A1
20140324388	Kriss	Oct 2014	A1
20140336837	Kiuchi et al.	Nov 2014	A1
20140340236	Rhoads	Nov 2014	A1
20140375428	Park	Dec 2014	A1
20140375472	Sankey	Dec 2014	A1
20140376377	Mikoda et al.	Dec 2014	A1
20150012147	Haghighat-Kashani	Jan 2015	A1
20150019280	Mejegard	Jan 2015	A1
20150022181	Anderson	Jan 2015	A1
20150022529	Johnston	Jan 2015	A1
20150025701	Huomo	Jan 2015	A1
20150035833	Hao et al.	Feb 2015	A1
20150035834	Axness	Feb 2015	A1
20150039269	Mejegard	Feb 2015	A1
20150050902	Umeki	Feb 2015	A1
20150054830	Inuzuka	Feb 2015	A1
20150061859	Matsuoka	Mar 2015	A1
20150077269	Hua	Mar 2015	A1
20150085136	Bernal	Mar 2015	A1
20150088442	Farrar et al.	Mar 2015	A1
20150090585	Nosti	Apr 2015	A1
20150094874	Hall	Apr 2015	A1
20150095414	Turbin	Apr 2015	A1
20150112617	Suen et al.	Apr 2015	A1
20150120222	Roytelman	Apr 2015	A1
20150123814	Wada	May 2015	A1
20150133167	Edge	May 2015	A1
20150149119	Fansler	May 2015	A1
20150149122	Cipri	May 2015	A1
20150160284	Cern	Jun 2015	A1
20150185251	Heydron et al.	Jul 2015	A1
20150185718	Tappan et al.	Jul 2015	A1
20150190099	Aratani	Jul 2015	A1
20150228097	Matange et al.	Aug 2015	A1
20150242783	Sasaki	Aug 2015	A1
20150271575	Asao	Sep 2015	A1
20150276816	Yoshida et al.	Oct 2015	A1
20150276830	Airaksinen et al.	Oct 2015	A1
20150308856	Srinivasan et al.	Oct 2015	A1
20150309089	Katsukura et al.	Oct 2015	A1
20150323611	Kise et al.	Nov 2015	A1
20150324439	Bhave	Nov 2015	A1
20150355036	Giorgi	Dec 2015	A1
20160028475	Zhang et al.	Jan 2016	A1
20160041002	Alzate Perez	Feb 2016	A1
20160048740	Winter	Feb 2016	A1
20160049790	Wordsworth	Feb 2016	A1
20160078127	Bhat et al.	Mar 2016	A1
20160080666	Stuart	Mar 2016	A1
20160080667	Stuart	Mar 2016	A1
20160109491	Kann	Apr 2016	A1
20160117070	Rose	Apr 2016	A1
20160119592	Stuart	Apr 2016	A1
20160124022	Tadano	May 2016	A1
20160140870	Connor	May 2016	A1
20160149717	Wada	May 2016	A1
20160149721	Wakeyama	May 2016	A1
20160169577	Watanabe et al.	Jun 2016	A1
20160171728	Klein	Jun 2016	A1
20160180578	Vegesna	Jun 2016	A1
20160188185	Bous	Jun 2016	A1
20160190981	Hong et al.	Jun 2016	A1
20160212506	Norwood et al.	Jul 2016	A1
20160231372	Wootton et al.	Aug 2016	A1
20160232457	Gray et al.	Aug 2016	A1
20160238639	Tadano	Aug 2016	A1
20160249831	Eastman et al.	Sep 2016	A1
20160291608	Reider et al.	Oct 2016	A1
20160294019	Yamauchi	Oct 2016	A1
20160320432	Nagai	Nov 2016	A1
20160321224	Duncker et al.	Nov 2016	A1
20160322078	Bose	Nov 2016	A1
20160327294	Svendsen	Nov 2016	A1
20160335377	Yamashina et al.	Nov 2016	A1
20160349954	Thompson et al.	Dec 2016	A1
20160359325	Kawata et al.	Dec 2016	A1
20160360464	Han et al.	Dec 2016	A1
20160363956	Moore	Dec 2016	A1
20160370001	Sim	Dec 2016	A1
20160371412	Marie	Dec 2016	A1
20160371662	Fine	Dec 2016	A1
20170004358	Bose et al.	Jan 2017	A1
20170005515	Sanders et al.	Jan 2017	A1
20170006435	Yamamoto	Jan 2017	A1
20170017214	O'Keeffe	Jan 2017	A1
20170019248	Mustafa et al.	Jan 2017	A1
20170019809	Saikusa	Jan 2017	A1
20170026800	Kim et al.	Jan 2017	A1
20170030951	Shon	Feb 2017	A1
20170041960	Quan et al.	Feb 2017	A1
20170045868	Cavarec et al.	Feb 2017	A1
20170048482	Drako et al.	Feb 2017	A1
20170108351	Shimizu	Apr 2017	A1
20170108456	Alizadeh et al.	Apr 2017	A1
20170108904	Choi et al.	Apr 2017	A1
20170109653	Agarwal	Apr 2017	A1
20170122774	Quady	May 2017	A1
20170123397	Billi et al.	May 2017	A1
20170124350	Reihman et al.	May 2017	A1
20170126843	Pantea et al.	May 2017	A1
20170146429	Suzuki	May 2017	A1
20170150069	Parrish et al.	May 2017	A1
20170150239	Davis	May 2017	A1
20170154445	Maruhashi	Jun 2017	A1
20170155279	Eckhardt et al.	Jun 2017	A1
20170171359	Ando	Jun 2017	A1
20170177546	Heinz et al.	Jun 2017	A1
20170189751	Knickerbocker et al.	Jul 2017	A1
20170193788	Kim et al.	Jul 2017	A1
20170200294	Hirano	Jul 2017	A1
20170205451	Moinuddin	Jul 2017	A1
20170212668	Shah	Jul 2017	A1
20170215191	Martin	Jul 2017	A1
20170219379	Rapadas	Aug 2017	A1
20170223433	Busslinger	Aug 2017	A1
20170229863	Hall	Aug 2017	A1
20170249648	Garvey	Aug 2017	A1
20170265053	Diebold et al.	Sep 2017	A1
20170271877	Stewart et al.	Sep 2017	A1
20170285591	Menzel	Oct 2017	A1
20170307245	Itaya	Oct 2017	A1
20170307665	Shinozaki	Oct 2017	A1
20170309094	Farahat	Oct 2017	A1
20170336930	Tappan	Nov 2017	A1
20170363666	Alkuran	Dec 2017	A1
20180003573	Giorgi	Jan 2018	A1
20180011626	Kelley et al.	Jan 2018	A1
20180031618	Friedlander et al.	Feb 2018	A1
20180040317	Mochizuki et al.	Feb 2018	A1
20180042174	Li	Feb 2018	A1
20180049039	Chandrasekaran	Feb 2018	A1
20180060741	Sakai	Mar 2018	A1
20180066945	Meier et al.	Mar 2018	A1
20180074099	Takata	Mar 2018	A1
20180090932	Main et al.	Mar 2018	A1
20180090933	Main et al.	Mar 2018	A1
20180138704	Hall	May 2018	A1
20180140241	Hamalainen et al.	May 2018	A1
20180143237	Beaudet	May 2018	A1
20180165385	Cillis et al.	Jun 2018	A1
20180165554	Zhang	Jun 2018	A1
20180165842	Kumar	Jun 2018	A1
20180165844	Kirichenko et al.	Jun 2018	A1
20180174337	Menard et al.	Jun 2018	A1
20180180648	Carson	Jun 2018	A1
20180189989	Douglas	Jul 2018	A1
20180197135	Moyer et al.	Jul 2018	A1
20180197188	Halstead et al.	Jul 2018	A1
20180199250	Vare et al.	Jul 2018	A1
20180209922	Yamakawa et al.	Jul 2018	A1
20180225600	Govindugari	Aug 2018	A1
20180228432	Woo et al.	Aug 2018	A1
20180242058	Hayakawa	Aug 2018	A1
20180248352	Herazo	Aug 2018	A1
20180248403	Takashita et al.	Aug 2018	A1
20180254661	Toizumi	Sep 2018	A1
20180255372	Toizumi	Sep 2018	A1
20180268581	Demuth	Sep 2018	A1
20180278091	Fukasawa	Sep 2018	A1
20180294647	Borean et al.	Oct 2018	A1
20180320915	Nagasaka	Nov 2018	A1
20180320967	Kaloudis	Nov 2018	A1
20180321836	Tappan et al.	Nov 2018	A1
20180322255	Connell, II et al.	Nov 2018	A1
20180343506	Busslinger	Nov 2018	A1
20180349365	McRaven et al.	Dec 2018	A1
20180349563	Bastide et al.	Dec 2018	A1
20180364689	O'Brien	Dec 2018	A1
20190041439	Brown	Feb 2019	A1
20190054347	Saigh	Feb 2019	A1
20190082241	Schmidt et al.	Mar 2019	A1
20190087990	Hournbuckle, Jr. et al.	Mar 2019	A1
20190098377	Kallus	Mar 2019	A1
20190162762	Beck	May 2019	A1
20190213100	Tayeb et al.	Jul 2019	A1
20190214954	Coover	Jul 2019	A1
20190254629	Li	Aug 2019	A1
20190271566	Childers	Sep 2019	A1
20190277898	Beaudet	Sep 2019	A1
20190279498	Honda	Sep 2019	A1
20190281371	Klicpera	Sep 2019	A1
20190292013	Ginsberg	Sep 2019	A1
20190293698	Ventola	Sep 2019	A1
20190310167	Kriss	Oct 2019	A1
20190325642	Martinet	Oct 2019	A1
20190342639	Christiansen	Nov 2019	A1
20190372345	Bain	Dec 2019	A1
20190380046	Johnson	Dec 2019	A1
20200007962	Kuesel	Jan 2020	A1
20200008214	Jeong	Jan 2020	A1
20200036635	Ohuchi	Jan 2020	A1
20200191607	Sosna	Jun 2020	A1
20200309828	Ahn	Oct 2020	A1
20200367821	Redshaw	Nov 2020	A1
20200374605	Snook	Nov 2020	A1
20210011071	Adachi	Jan 2021	A1
20210080514	Beaudet	Mar 2021	A1
20210088390	Kriss	Mar 2021	A1
20210116517	Snook, II	Apr 2021	A1
20210117961	Deshmukh	Apr 2021	A1
20210135890	Arduini	May 2021	A1
20210176541	Okada	Jun 2021	A1
20210288520	Cardozo	Sep 2021	A1
20210329451	Jun	Oct 2021	A1
20220038930	Fujisaki	Feb 2022	A1
20220101456	Schönfeld	Mar 2022	A1
20220128388	Raduchel	Apr 2022	A1
20220137600	Ramos Peñuela	May 2022	A1
20220173767	Barois	Jun 2022	A1
20220205890	Chen	Jun 2022	A1
20220252485	Strudwicke	Aug 2022	A1

Foreign Referenced Citations (27)

Number	Date	Country
2152024	Dec 1995	CA
1237302	Dec 1999	CN
1443404	Sep 2003	CN
101061523	Oct 2007	CN
101326479	Dec 2008	CN
101498744	Aug 2009	CN
101782600	Jul 2010	CN
102188263	Sep 2011	CN
102568170	Jul 2012	CN
202351298	Jul 2012	CN
1 560 121	Aug 2005	EP
1710593	Oct 2006	EP
2 026 080	Feb 2009	EP
2 254 253	Nov 2010	EP
2 889 630	Jul 2015	EP
2-294204	Dec 1990	JP
8-68668	Mar 1996	JP
2003-110749	Apr 2003	JP
2003-302260	Oct 2003	JP
2004-69641	Mar 2004	JP
2010-9477	Jan 2010	JP
2010-272118	Dec 2010	JP
2011-258109	Dec 2011	JP
10-2008-0112692	Dec 2008	KR
10-2012-0065540	Jun 2012	KR
10-2012-0077332	Jul 2012	KR
2013020110	Feb 2013	WO

Non-Patent Literature Citations (28)

Entry
Bicelli et al., “From the Traditional Multimeter to the Wireless Multimeter Networking”, IMTC 2006—Instrumentation and Measurement Technology Conference, Sorrento, Italy, Apr. 24-27, 2006, pp. 1581-1586.
Extech Instruments, “Extech EX540 Wireless Datalogging selected as 2010 EC&M Product of the Year Category Winner,” Press Release, Mar. 18, 2009, 2 pages.
Extech Instruments, “Extech EX845 METERLiNK™ Clamp Meter Transmit Readings to FLIR IR Cameras,” Press Release, Apr. 1, 2010, 3 pages.
Extech Instruments, “MultiMeter/Datalogger with Wireless PC Interface,” Product Datasheet, Jul. 14, 2011, 1 page.
Extech Instruments, “Wireless TRMS Multimeter—Model EX540,” User's Guide, Apr. 1, 2010, 17 pages.
Extended European Search Report, dated Jun. 1, 2015, for European Application No. 14200521.4-1560, 9 pages.
Extended European Search Report, dated Nov. 11, 2013, for European Application No. 13178568.5-1560, 8 pages.
Extended European Search Report, dated Oct. 20, 2016, for European Application No. 14762404.3-1568 / 2973108, 7 pages.
Extended European Search Report, dated Sep. 10, 2013, for European Application No. 13178211.2-1853, 8 pages.
“Fluke 3000 FC Fluke Connect Series Wireless Digital Multimeter,” retrieved from http://www.testequity.com/products/5220, retrieved on Sep. 1, 2015, 2 pages.
Fluke, “1652C/1653B/1654B Electrical Installation Tester,” User's Manual, Sep. 2010, 66 pages.
Fluke, “Basic electrical installation testing,” Application Note, 2014, 4 pages.
Fluke, “Performing Live-Circuit Installation Tests with a Fluke 1650 series Tester on an IT-system,” Application Note, 2004, 8 pages.
Fluke, “Testing RCDs with the Fluke 1650B Series,” Application Note, 2014, 2 pages.
Fluke, “The importance of loop impedance testing,” Application Note, 2003, 2 pages.
Hoh et al., Wireless Remote Connectivity with Handheld Digital Multimeters, 2012, retrieved from, http://www.wirelessdesignmag.com/blog/2012/03/wireless-remote-connectivity-handheld-digital-multimeters, retrieved on Sep. 1, 2015, 6 pages.
International Search Report dated Jul. 10, 2014, for International Application No. PCT/US2014/029561, 3 pages.
International Search Report and Written Opinion dated Sep. 12, 2014, for International Application No. PCT/US2014/029867, 12 pages.
International Search Report and Written Opinion dated Jul. 17, 2014, for International Application No. PCT/US2014/029889, 11 pages.
International Search Report and Written Opinion dated Jul. 18, 2014, for International Application No. PCT/US2014/029885, 13 pages.
International Search Report and Written Opinion dated Jul. 22, 2014, for International Application No. PCT/US2014/029883, 11 pages.
International Search Report and Written Opinion dated Jul. 24, 2014, for International Application No. PCT/US2014/029879, 10 pages.
Japanese Office Action, dated Jan. 23, 2018, for Japanese Application No. 2016-503271, 10 pages (with English translation).
Office Action for JP Application No. 2016-503271 dated Dec. 4, 2018, 8 pages.
Office Action, for Chinese Application No. 201480027748.9, dated Nov. 2, 2016, 22 pages. (with English Translation).
Office Action, dated Oct. 31, 2016, for Chinese Application No. 201310334993.1, 30 pages. (with English Translation).
Redfish Instruments, “iDVM v1.0 User's Guide,” 2013, 21 pages.
Redfish Instruments, “iDVM,” Screenshot, retrieved from http://appshopper.com/utilities/idvm, retrieved 2013, 2 pages.

Related Publications (1)

	Number	Date	Country
	20210033497 A1	Feb 2021	US

Provisional Applications (2)

	Number	Date	Country
	61876719	Sep 2013	US
	61801380	Mar 2013	US

Continuations (1)

	Number	Date	Country
Parent	14214662	Mar 2014	US
Child	17074470		US

Automated combined display of measurement data

Information

Patent Number

Date Filed

Date Issued

Inventors

Original Assignees

Examiners

Agents

CPC

Field of Search

CPC

International Classifications

Abstract