• 专利附录
  • 专利说明
  • 权利要求
  • 类似技术
  • 同族专利
  • 引用文献
  • 法律状态
  • 优先权
    • 专利摘要:
    SYSTEMS AND METHODS TO START A VERIFICATION TEST WITHIN A FLOW METER VIA A FLOW COMPUTER. Systems and methods for initiating a verification test within a flow meter via a flow computer are disclosed. An example method includes communicating, via a flow computer, a request for a flow meter to initiate a flow meter verification test. The sample method also includes retrieving diagnostic data from the flow meter. The example method also includes recording a verification test result in a flow computer record, the result based on the diagnostic data.
    公开号:BR112014028361B1
    申请号:R112014028361-3
    申请日:2013-05-13
    公开日:2020-10-20
    发明作者:Justin Mickael Berndt；Mary Barbara Abens
    申请人:Bristol, Inc., D/B/A Remote Automated Solutions；
    IPC主号:
    专利说明:

    FIELD OF DISSEMINATION
    [0001] This disclosure generally refers to supervisory control systems and data acquisition and, more particularly, to systems and methods for initiating a verification test within a flow meter via a flow computer. FUNDAMENTALS
    [0002] Supervisory control and data acquisition systems (SCADA), such as those used in the oil and gas production industry, often include flow computers as central pieces of equipment in a production process system (for example, in a wellhead production lease). Flow computers are used to perform flow calculations, control the system, optimize the system, create historical files and / or communicate with the SCADA network. The monitoring and / or control of a process system via a flow computer is achieved by interfacing the flow computer with field devices (for example, valves, valve positioners, switches, sensors, transmitters, etc.) configured to perform functions control systems, such as opening or closing valves and measuring process parameters. Such interface of field devices with the flow computer via any of analog, digital or combined analog / digital buses via any desired means of communication (eg, wired, wireless, etc.) and protocols (eg, Fieldbus , Profibus®, HART®, Modbus®, etc.). BRIEF DESCRIPTION OF THE DRAWINGS
    [0003] FIG. 1 illustrates an example system comprising an example stream computer implemented in accordance with the teachings disclosed in this document.
    [0004] FIG. 2 is a flow chart representative of an example process that can be performed to implement the example flow computer and / or, more generally, the example system of FIG. 1.
    [0005] FIGS. 3A and 3B are respective first and second portions of a flowchart representative of another sample process that can be performed to implement the sample flow computer and / or, more generally, the sample system of FIG. 1.
    [0006] FIGS. 4A and 4B are respective first and second portions of a flowchart representative of another example process that can be performed to implement the example flow computer and / or, more generally, the example system of FIG. 1. SUMMARY
    [0007] Systems and methods for initiating a verification test within a flow meter via a flow computer are disclosed. An example method is revealed that includes communicating, via a flow computer, a request for a flow meter to initiate a flow meter verification test. The sample method also includes retrieving diagnostic data from the flow meter. The example method also includes recording a verification test result in a flow computer record, the result based on the diagnostic data.
    [0008] An example flow computer built in accordance with the teachings disclosed in this document includes a flow meter interface for communicatively coupling the flow computer to a flow meter. The flow meter interface is for communicating a request to the flow meter to initiate a flow meter verification test and retrieve diagnostic data from the flow meter. The sample stream computer also includes a memory for recording the verification test result, the result based on the diagnostic data.
    [0009] An example tangible machine-readable storage medium is disclosed that includes instructions which, when executed, make a machine at least communicate a request to a flow meter to initiate a flow meter verification test, retrieve data flow meter diagnostics and record a verification test result in a flow computer record. The result is based on the diagnostic data. DETAILED DESCRIPTION
    [0010] FIG. 1 illustrates an example system 100 comprising an example flow computer 102 implemented in accordance with the teachings disclosed in this document. In the illustrated example, flow computer 102 is in communication with a flow meter 104. In some examples, flow computer 102 can also be in communication with at least one of a host supervisory control and data acquisition system ( SCADA) 106, one or more external devices 108 (for example, other components in a SCADA system, a portable computer, a portable field communicator, etc.), or one or more flow meters 110.
    [0011] The flow meter 104 illustrated in FIG. 1 can be any suitable flow meter that contains internal functionality to run diagnostics to verify the performance and integrity of flow meter 104. For example, flow meter 104 can be a flow meter that uses the Coriolis Effect with the tool diagnostic tool Smart Meter Verification developed by Micro Motion, a division of Emerson Process Management. Therefore, in example system 100, flow meter 104 includes one or more of diagnostic applications 112 to perform tests and / or diagnostics on flow meter 104. In the illustrated example, flow meter 104 includes a diagnostic application 112 to perform a verification test on the flow meter components 104. The diagnostic application 112 produces diagnostic data associated with the verification test that can be stored in an internal memory 114. In some known flow meters 104, the internal memory 114 where diagnostic data is stored comprises registers. Diagnostic data can include an indication of the test's operational status (for example, whether the test is running or not), the progress and / or completion of the verification test (for example, initialization, measurement, analysis, complete and / or complete percentage), the value of secondary parameters measured and / or calculated during the verification test, the result of the verification test (for example, the success or failure of the flow meter 104 to pass the verification test) and / or any errors associated with a failed verification test. The success or failure of the flow meter 104 can be determined based on whether the secondary parameters measured are within boundary limits defined in the factory specifications.
    [0012] For example, a typical flow meter can be used to measure the mass flow rate of fluid in a tube. The flow meter can be connected in line with the tube and includes one or more tubes or conduits defining inlet and outlet openings through which the fluid in the tube can flow. The flow meter can determine flow rate by vibrating the tube (s) by vibrating while material is flowing through the tube. The inertial forces of the material flowing in the tube can combine with the vibrating tube (s) to cause the Coriolis Effect, so there is a phase shift in the vibration of the tube (s) at different points along the tube (s), as well as at points adjacent to the inlet and outlet openings. Using such a flow meter and the Coriolis Effect, the mass flow rate of the fluid in the tube is proportional to the time delay or phase difference at the separate points along the tube (s). As such, the mass flow rate can be determined by multiplying the time delay by a calibration constant based on the material properties and the shape of the tube (s), which may be related to a stiffness parameter of the flow meter tube (s). Thus, in such examples, the secondary parameters include the phase difference of the vibrations of the tubes at the separate points and the calculated stiffness of the phase difference. From such secondary parameters, the integrity and performance of a flow meter that uses the Coriolis Effect can be determined, allowing the flow meter to implement a verification test that excites the tube (s) via a controlled vibration, while material is flowing through a corresponding tube, measure the vibrational response of the tube (s) at multiple points, determine a stiffness parameter at each of the points along the tube (s) with based on the phase shift measured at each point and compare the stiffness parameters with pre-configured limits for the flow meter specified at the time of manufacture. A stiffness parameter falling outside of factory specifications is an indication that the flow meter is unable to measure accurately
    [0013] After the flow meter 104 has passed a verification test, the resulting diagnostic data can be accessed by an operator to initiate any appropriate response based on the results (for example, replacing the flow meter 104 if the meter flow test has not passed the verification test). However, data from many known flow meters implementing such diagnostic tools is typically only accessible via proprietary applications developed in connection with flow meters. As a result, the diagnostic results of the flow meter cannot be directly included in a global process system, such as a SCADA system, to allow operators to acquire a more complete picture of the system, to interact remotely with the flow meter through of a system host application, to schedule and / or remotely start a verification test via the system host application, to time mark and archive when the verification test is performed (for example, when started and / or aborted) at an event record of an audit trail associated with the SCADA system for further analysis, review and / or training in connection with other events and / or alarms in the system.
    [0014] Such obstacles are overcome by the sample flow computer 102 illustrated in FIG. 1 which interfaces with flow meter 104 in accordance with the teachings disclosed in this document. Sample flow computer 102 in the illustrated example includes a sample processor 116. Processor 116 in the illustrated example is hardware. For example, processor 116 can be implemented by one or more integrated circuits, logic circuits, microprocessors or controllers from any desired family or manufacturer.
    [0015] Processor 116 in the illustrated example includes a local memory 118 (e.g., a cache). The processor 116 in the illustrated example is in communication with a main memory 120, including volatile memory and non-volatile memory, via a bus 122. The volatile memory of main memory 120 can be implemented by Synchronous Dynamic Random Access Memory (SDRAM), Dynamic Random Access Memory (DRAM), RAMBUS Dynamic Random Access Memory (RDRAM) and / or any other type of random access memory device. The non-volatile memory of main memory 120 can be implemented by flash memory and / or any other desired type of memory device. Access to main memory 120 is controlled by a memory controller.
    [0016] The flow computer 102 of the illustrated example also includes one or more interfaces 124. The interface (s) 124 can be implemented by any type of interface standard, such as an Ethernet interface , a universal serial bus (USB), a PCI express interface, a serial peripheral interface bus (SPI) and / or interfaces used in SCADA and other process control systems (eg Fieldbus, Profibus®, HART®, Modbus ®, etc.) to communicate with internal and / or external component (s) to allow operators to enter input data, commands and / or other information into the flow computer 102 and / or receive data and / or other information from the flow computer 102. The internal component (s) in the illustrated example include components integral to the flow computer 102 such as, for example, an operator display (for example, operator display 126) that may include a display screen, a keyboard, buttons, indicator lights, etc. The external component (s) in the illustrated example include, for example, the SCADA host system 106 and / or other external device (s) 108 such as, for example, a portable computer, a portable field communicator, a printer, etc. In addition, the sample flow computer 102 can interface with field devices and / or other components in the SCADA system 100, such as flow meter 104 and / or other flow meters 110.
    [0017] More particularly, the internal component (s) and / or external (s) can be implemented to insert data by, for example, an audio sensor, a microphone, a camera (still or video), a keyboard, a button, a mouse, a touch screen, a track-pad, a trackball, isopoint and / or a voice recognition system. In addition, the internal and / or external component (s) can be implemented to send data by, for example, display devices (for example, a light emitting diode). light (LED), an organic light-emitting diode (OLED), a liquid crystal display, a cathode ray tube (CRT) display, a touch screen, a tactile output device, a light-emitting diode (LED) ), a printer and / or speakers). The interface (s) 124, in some examples may include a graphics driver card, a graphics driver chip or a graphics driver processor.
    [0018] The interface (s) 124 of the illustrated example also includes a communication device, such as a transmitter, receiver, transceiver, modem and / or network interface card to facilitate exchange data with the external component (s) (for example, computing devices of any kind) via a network (for example, an Ethernet connection, an RS-485 connection, a digital subscriber line (DSL ), a phone line, coaxial cable, a cell phone system, etc.) using any means of communication (for example, wireless, hard-wired, etc.) and protocols (for example, HTTP, SOAP, etc.) desired.
    [0019] The flow computer 102 of the illustrated example also includes one or more mass storage devices 128 for storing software and data. Examples of such mass storage devices 128 include flash drives or memory chips, floppy disk drives, hard disk drives, compact disk drives, Blu-ray disk drives, RAID systems and digital versatile (DVD) drives. Among other things, the mass storage devices 128 of the sample stream computer 102 can store encrypted instructions 130 implemented to execute all or any part of the functionality of the stream computer 102. Additionally or alternatively, the encrypted instructions 130 can be stored in local memory 118, in the volatile or non-volatile memory of main memory 120 and / or in a removable tangible computer-readable storage medium, such as a CD or DVD. The coded instructions 130 of the illustrated example include instructions for implementing the example processes of FIGS. 2, 3A-B and 4A-B described below to interface with flow meter 104 and / or SCADA host system 106, or external device (s) 108 to initiate a verification test flow meter and file its timing and results in an event log and / or alarm log associated with the SCADA system.
    [0020] Although an exemplary way of implementing flow computer 102 is illustrated in FIG. 1, one or more of the elements, processes and / or devices illustrated in FIG. 1 can be combined, divided, rearranged, omitted, eliminated and / or implemented in any other way. In addition, sample processor 116, sample main memory 120, sample interface (s) 124, sample mass storage 128 and / or, more generally, sample stream computer 102 of FIG. 1 can be implemented by hardware, software, firmware and / or any combination of hardware, software and / or firmware. Thus, for example, any of the example processor 116, example main memory 120, the example interface (s) 124, the mass storage of example 128 and / or more generally, the flow computer 102 could be implemented by one or more circuit (s), programmable processor (s), application-specific integrated circuits (ASIC (s)), programmable logic devices (PLD (s)) and / or field programmable logic devices ( FPLD (s)). When reading any of the device or system claims of this patent to cover a purely software and / or firmware implementation, at least one of the sample processor 116, the sample main memory 120, the sample interface (s) 124 and / or example mass storage 128 is / are expressly defined (s) to include a tangible computer-readable storage device or storage disc, such as a memory, a digital versatile disc (DVD), a compact disc (CD), a Blu-ray disc, etc., storing the software and / or firmware. In addition, the sample flow computer 102 of FIG. 1 may include one or more elements, processes and / or devices in addition to, or instead of, those illustrated in FIG. 1 and / or may include more than one of any or all of the elements, processes and devices illustrated.
    [0021] Flowcharts representative of example processes for implementing flow computer 102 and / or, more generally, example system 100 of FIG. 1 are shown in FIGS. 2, 3A-B and 4A-B. In these examples, the processes can be implemented as a program for execution by a processor, such as processor 116 shown in the sample flow computer 102 discussed above in connection with FIG. 1. The program can be incorporated into software stored on a tangible computer-readable storage medium, such as a CD-ROM, a floppy disk, a hard disk drive, a digital versatile disk (DVD), a Blu-ray disc or a memory associated with processor 116, but the entire program and / or its parts, alternatively, could be run by a device other than processor 116 and / or incorporated into firmware or dedicated hardware. In addition, although the example program is described with reference to the flowchart illustrated in FIGS. 2, 3A-B and 4A-B, many other methods of implementing sample flow computer 102 and / or, more generally, sample system 100 may alternatively be used. For example, the execution order of the blocks can be changed and / or some of the described blocks can be changed, eliminated, or combined.
    [0022] As mentioned above, the example processes of FIGS. 2, 3A-B and 4A-B, can be implemented using coded instructions (for example, computer and / or machine-readable instructions) stored in a tangible computer-readable medium, such as a hard disk drive, a flash memory, a read-only memory (ROM), a compact disc (CD), a versatile digital disc (DVD), a cache, a random access memory (RAM) and / or any other storage device or storage disc on which the information is stored for any duration (for example, for prolonged periods of time, permanently, briefly, to temporarily store and / or to cache information). As used in this document, the term tangible computer-readable medium is expressly defined to include any type of computer-readable storage device and / or storage disk and to exclude propagating signals. As used herein, "tangible computer-readable storage medium" and "machine-readable tangible storage medium" are used interchangeably. Additionally or alternatively, the example processes of FIGS. 2, 3A-B and 4A-B can be implemented using coded instructions (for example, computer and / or machine-readable instructions) stored on a non-transitory computer and / or machine-readable medium, such as a hard disk drive, a flash memory, a read-only memory, a compact disk, a digital versatile disk, a cache, a random access memory and / or any other storage medium in which information is stored for any duration (for example, for periods of time, permanently, briefly, to temporarily store and / or to cache information). As used herein, the term non-transitory computer-readable device or disk is expressly defined to include any type of computer-readable medium and to exclude signal propagation. As used in this document, when the phrase "at least" is used as the transitional term in a preamble to a claim it is open-ended in the same way that the term "comprising" is open-ended.
    [0023] The example process of FIG. 2 begins at block 200 receiving (for example, via flow computer 102) a request to initiate a verification test on a flow meter (for example, sample flow meter 104). The sample process includes communicating the request to the flow meter (for example, 104) (block 202). For example, the flow computer (for example, 102) can record a start code and send it to the flow meter (for example, 104) via the interface (for example, 124) of the flow computer (for example , 102). The sample process also records a start event (block 204) (for example, within an audit trail or other file in the mass storage 128 of the flow computer 102).
    [0024] The example process of FIG. 2 also includes retrieving diagnostic data (block 206). Diagnostic data can, for example, be retrieved from a flow meter (for example, the sample flow meter 104) containing a diagnostic application (for example, 112) to perform a verification test. Diagnostic data can include any relevant information, such as the operational status of the verification test (for example, running / not running), the progress and / or completion of the verification test (for example, initialization, measurement, analysis, complete and / or complete percentage), the value of secondary parameters measured and / or calculated during the verification test, the results of the verification test (for example, success or failure of the flow meter (for example, 104) in passing the verification test), any errors associated with a failure of the flow meter 104 and / or any other information relevant to the verification test, as described above. In addition, when retrieving diagnostic data, diagnostic data is also stored in the flow meter memory (for example, the flow meter memory 114). In some instances, diagnostic data can be stored in recorders associated with the flow meter (eg 104) to which the flow computer (eg 102) has access via communication with the flow meter (eg 104) via a corresponding interface (for example, 124). The example process also determines whether a request to abort the verification test has been received (block 208). If a request to abort the verification test is received, the request is communicated to the flow meter (for example, 104) (block 210). The request can be communicated by the flow computer (eg 102) by recording an abort code to be sent to the flow meter (eg 104) via the interface (eg 124). In addition, the example process of FIG. 2 includes registering an abortion event (block 212).
    [0025] If no request to abort the verification test is received, the sample process continues to block 214 where the sample process determines whether the verification test is complete or complete. If it is determined that the verification test is not finished, the sample process searches for other meters (block 216) before returning to block 206 to retrieve updated diagnostic data. In some instances, if the check is not completed, the flow computer will search the other meters and then wait to cycle back to block 206 on a programmed basis (for example, every second, every 4 seconds, etc.). ). Once the verification test is determined to be complete (in block 214) the sample process retrieves results of the verification test (block 218). If the results indicate that the flow meter (for example, 104) has passed the verification test or not, the sample process stores the results in an event log and / or an alarm log associated with an audit trail or other file (block 220). Once the results have been recorded (in block 220) or the verification test aborted with a corresponding registry entry (blocks 210 and 212) the example process of FIG. 2 ends.
    [0026] FIGS. 3A and 3B are respective first and second portions of a flowchart representative of an example process that can be performed to implement the example flow computer 102 and / or, more generally, the example system 100 of FIG. 1. The example process begins in FIG. 3A by a flow computer (for example, the sample flow computer 102) retrieving diagnostic data (block 300) (for example, from a flow meter (for example, 104) while implementing a diagnostic application (for example , 112) associated with a verification test). Diagnostic data can include any relevant information, such as the operational status of the verification test (for example, running / not running), the progress and / or completion of the verification test (for example, initialization, measurement, analysis, complete and / or complete percentage), the value of secondary parameters measured and / or calculated during the verification test, the results of the verification test (for example, success or failure of the flow meter (for example, 104) in passing the verification test) and / or any errors associated with a failure of the flow meter 104. In the illustrated examples, the diagnostic data is stored in the flow meter memory (for example, the flow meter memory 104). In some instances, diagnostic data can be stored in recorders associated with the flow meter (eg 104) to which the flow computer (eg 102) has access via communication with the flow meter (eg 104) via a corresponding interface (for example, 124).
    [0027] During the example process of FIGS. 3A and 3B, the process determines whether a start / stop parameter has been triggered (block 302). In the illustrated example, the start / stop parameter is a single parameter stored within the flow computer (for example, 102) that is adjusted by an operator to request the flow meter (for example, 104) or start (for example, the verification test or abort (for example, stop) a verification test currently in progress. For example, the start / stop parameter can have a default value of 0 which if triggered (for example, set to 1) indicates that the verification test will either start or abort. Whether the triggered parameter starts or stops the verification test is determined based on whether or not the test is already running, as will be described in more detail below. In some examples, the start / stop parameter is triggered by an operator via any one of a SCADA host system (for example, 106), an external device (for example, 108) and / or an operator display (for example, 126) of the flow computer (for example, 102). In some examples, the start / stop parameter is triggered to run the verification test once. In other examples, the start / stop parameter is set to periodically trigger the verification test based on a schedule defined by the operator. If the example process determines that the start / stop parameter has not been triggered, the example process proceeds to block 318 (FIG. 3B) where the example process determines whether the verification test is running, as will be described in more details below. If the example process determines that the start / stop parameter has been triggered (for example, set to 1), the example process determines whether the verification test is enabled on the flow meter (for example, 104) (block 304). For example, many known flow meters do not include the built-in functionality (for example, the diagnostic application (s) 112) to perform the verification test. In these examples, where it is determined that the verification test is not enabled, the example process moves to block 316 where the start / stop parameter is reset (for example, set to 0), before continuing, as described below.
    [0028] If the verification test is enabled within the flow meter (for example, the diagnostic application (s) 112 includes (in) the functionality to perform the verification test), the sample process includes determining whether the verification test is currently running or is currently inactive (block 306). For example, as mentioned earlier, included within the diagnostic data retrieved from the flow meter (for example, 104), at block 300 is an indication of the operational status of the verification test that indicates whether or not the test is being performed. If the sample process determines that the verification test is not running, the sample process records a start event on the flow computer (for example, on an audit trail and / or another file within the mass storage device 128 of flow computer 102) (block 308). In addition to recording a start event (block 308), the sample process also includes generating and sending a start code to the flow meter (for example, 104) (block 310). In this way, the verification test is actually initiated by the flow meter (for example, 104) as instructed by the code received via the flow computer (for example, 102).
    [0029] If the example process determines in block 306 that the verification test is running (after determining that the start / stop parameter was triggered in block 302), the example process records an abort event on the flow (for example, 102) (block 312) and generates and sends an abort code to the flow meter (for example, 104) (block 314). In other words, when the start / stop parameter is triggered (for example, set to 1), while the verification test is in progress, the example process determines that the verification test currently running is about to be aborted, the The sample process creates the appropriate event record (for example, on an audit trail) and then provides the code to instruct the flow meter (for example, 104) to actually stop the verification test. After the appropriate event is logged (for example, a start event in block 308 or an abort event in block 312) and the corresponding code is sent (for example, the start code in block 310 or the abort code in block 314), the example process resets the start / stop parameter (for example, set to 0) (block 316). In this way, the start / stop parameter is configured to be triggered again or to start or stop the verification test, depending on the current operational state (for example, running / not running) of the verification test.
    [0030] The example process also includes determining if the verification test is running (block 318) (FIG. 3B). This determination is made in the same way as described above (in block 306), but takes into account any changes as a result of starting (block 310) or aborting (block 314) the verification test. If it is determined that the verification test is running, meaning that the verification test has just started or is not yet completed, the sample process searches for data from other meters (for example, the other flow meters 110) (block 320). After searching other meters (for example, 110), the example process goes back to block 300 (FIG. 3A) to retrieve any updated diagnostic data and repeat the process. In some examples, each iteration of the example process of FIGS. 3A and 3B, including searching the other meters (in block 320), is performed once per second. In this way, the sample process is always using updated or current diagnostic data retrieved during each pass of block 300. In some examples, the sample process starts through the process to retrieve diagnostic data (block 300) (FIG. 3A) approximately once every second, regardless of whether an associated flow meter (for example, 104) is performing a verification test. In other examples, the example process starts once every four seconds. In this way, even when the flow computer loses communication with a flow meter (for example, 104) undergoing the verification test, if communications are restored before the verification test is complete, the flow computer will be able to recognize the operational status of the verification test and continue monitoring the flow meter (for example, 104) until the verification test is complete or otherwise stops running. Other examples may cycle through the example process at different frequencies more or less than the examples outlined above.
    [0031] If it is determined that the verification test is not running (in block 318), the example process determines whether the verification test is ended or completed (block 322). In addition to diagnostic data indicating whether or not the verification test is running (for example, based on an operational status parameter), data retrieved from the flow meter (for example, 104) may also include information indicating progress and / or the completion of the verification test. If it is determined that the verification test is not finished (for example, if the verification test was started and then aborted before completion), the example process moves back to block 320 to search for other meters (for example, example, 110). If, on the other hand, it is determined that the verification test is finished (for example, the verification test has stopped running (as determined in block 318) because the flow meter (for example, 104) has completed the verification test) , the sample process determines whether the flow meter (for example, 104) has passed the verification test (block 324). A flow meter (for example, 104) that passes the verification test indicates the reliability of the performance and / or integrity of the flow meter (for example, 104).
    [0032] For example, as described above, the reliability of flow meters that use the Coriolis Effect can be determined by determining the rigidity factors or parameters of the tube (s) at various locations (for example, at the inlet and at the flow meter output) and comparing these stiffness parameters with factory specification limits for stiffness parameters via the verification test. Diagnostic tools for other types of flow meters may not base a verification test on stiffness parameters. However, such flow meters can still measure and / or calculate any other suitable metric to compare with factory specifications to similarly determine whether the flow meter has passed the verification test or not. Thus, in some examples, when the verification test is completed within the flow meter (for example, 104), one of the outputs included within the diagnostic data retrieved in block 300 (FIG. 3A) of the example process indicates whether the flow meter in question (for example, flow meter 104) passed or failed the verification test. If it is determined that the flow meter (for example, 104) has passed the verification test (in block 324), the sample process adjusts a result (for example, a result parameter within the flow computer (for example, 102 )) to a success value (block 326). The sample process also records a successful event on the flow computer (for example, 102) (block 328). In some examples, the success event is recorded within an audit trail or other file to be accessed and / or reviewed via other components (for example, the SCADA host system 106) associated with the flow computer (for example, 102 ).
    [0033] If it is determined that the flow meter (for example, 104) has not passed the verification test, the sample process sets the result to an error value (block 330). The error value can be indicative of one or more reasons for failure. For example, the error value for a flow meter that uses the Coriolis Effect can indicate whether one or more locations (for example, inlet and / or outlet) in the flow meter tube (s) have (have ) a stiffness parameter measured outside the tolerance level or boundary limit defined by the manufacturer. In some examples, the error value can indicate how much the measured stiffness parameters have exceeded or fallen below pre-configured limits or thresholds. In addition, any other flow meter that can perform a verification test can provide an error value for a corresponding result parameter indicating similar problems relevant to the basis on which the flow meter was tested. In addition, in other examples, for any type of flow meter, the error value may indicate that, although the verification test was complete, the data is not reliable.
    [0034] In addition to setting the result to an error value, the example process also records an error event on the flow computer (for example, 102) (block 332). In some instances, the error event is logged within an audit trail or other file to be accessed and / or reviewed via other components (eg, the SCADA host system 106) associated with the flow computer (eg, 102 ).
    [0035] Additionally, the illustrated example process sends feedback data associated with the verification test (block 334) which can include the result of the verification test. For example, the success or failure of the flow meter (eg 104) to pass the verification test can be displayed to an operator by viewing a display associated with any of a SCADA host system (eg 106), a external device (for example, 108) and / or an operator display (for example, 126) of the flow computer (for example, 102). In some examples, feedback data includes additional information based on the verification test, such as the progress and / or completion of the verification test and / or the value of secondary parameters associated with the verification test. In addition, in some instances, if the flow meter (for example, 104) failed the verification test, the output feedback data may also include information pertaining to the point during the verification test where the flow meter (for example , 104) failed (for example, the progress of the test at the time of failure), the reasons for the failure (for example, based on the error value of the result) and / or an alarm to attract the attention of an operator.
    [0036] The example process of FIGS. 3A and 3B, further includes determining whether to continue to monitor the flow meter (for example, 104) (block 336). If the sample process is to continue monitoring the flow meter (for example, 104), the sample process returns to block 320 to search for other meters (for example, 110) before retrieving the latest diagnostic data again ( in block 300 (FIG. 3A)) to repeat the example process, as described above. If the sample process determines not to continue monitoring the flow meter (for example, 104) the sample process ends.
    [0037] FIGS. 4A and 4B are respective first and second portions of a flowchart representative of another sample process that can be performed to implement the sample flow computer 102 and / or, more generally, the sample system 100 of FIG. 1. The example process begins in FIG. 4A determining whether a request to initiate a verification test on a flow meter (for example, 104) has been received (block 400). The request can be received from an operator either at that time or based on a previously entered schedule via, for example, any of a SCADA host system (for example, 106), an external device (for example, 108) and / or an operator display (for example, 126) of the flow computer (for example, 102). If no request was received, the sample process proceeds to block 424 (FIG. 4B) to determine whether a verification test is running within the flow meter (for example, 104) in the same manner as determined in block 318 described above in connection with FIG. 3B. If a request to initiate a verification test has been received (at block 400), the example process sets a start parameter to a value (for example, start = 1) indicating that a request has been received to initiate a verification test ( block 402). The sample process continues to retrieve diagnostic data (block 404). The diagnostic data is retrieved in the same way and contains the same information as described above in connection with block 300 of FIG. 3B.
    [0038] The example process includes determining whether the verification test is running (block 406) (based, for example, on the diagnostic data retrieved in block 404). If the verification test is determined to be running, the sample process determines whether a request to abort the verification test has been received (block 408). If a request to abort the verification test is received, the example process records an abort event (block 410) and writes an abort code instructing the flow meter (for example, 104) to abort the verification test (block 412). The example process then sets the start parameter to a value indicating that the verification test will no longer be completed (for example, start = 0) (block 414). At this point, the example process proceeds to block 424 (FIG. 4B) to proceed in the same manner as described above in block 318 of FIG. 3B. In contrast, if it is determined that a request to abort the verification test has not been received, the example process proceeds directly to block 424.
    [0039] If the sample process determines (in block 406) that the verification test is not running, the example process determines whether the verification test is enabled within the flow meter (for example, 104) (block 416 ). If the verification test is not enabled, the example process proceeds to block 414, where the start parameter is set to a value indicating that the verification test is no longer to be continued (for example, start = 0). If the verification test is enabled on the flow meter (for example, 104), the sample process records a start event (block 418) and sends a start code to the flow meter (for example, 104) instructing the flow meter (eg 104) starting the verification test (block 420). The sample process then sets the start parameter to a value indicating which instructions were sent to the flow meter (eg 104) to begin the verification test (eg start = 2) (block 422). The example process then proceeds to block 424 to determine whether the verification test is running in the same manner as described above for block 318 of FIG. 3B.
    [0040] Blocks 424, 426, 428, 430, 432, 434, 436, 438 and 440 of the example process in FIGS. 4A and 4B are implemented in a manner similar to those described above as blocks 318, 320, 322, 324, 326, 328, 330, 332 and 334 of FIGS. 3A and 3B, respectively. However, after sending the results of the verification test (at block 440), the example process of FIGS. 4A and 4B sets the start parameter to a value indicating that the verification test is complete and / or no longer needs to be completed (for example, start = 0) (block 442). After doing so, the example process then returns to block 426 to search for other meters before determining whether the start parameter indicates that the verification test no longer needs to be completed (for example, start = 0) (block 444 ). If the check does not need to continue (for example, start> 0) the sample process returns to block 404 (FIG. 4A) to retrieve updated diagnostic data before repeating the rest of the sample process. If the start parameter indicates that the verification test does not need to be completed (in block 444), the example process determines whether to continue monitoring the flow meter (for example, 104) (block 446). If the flow meter (for example, 104) is to continue to be monitored, the example process goes back to block 400 (FIG. A) to continue through the entire example process of FIGS. 4A and 4B. If determined not to continue monitoring the sample process ends.
    [0041] Although certain example methods, apparatus and articles of manufacture have been described in this document, the scope of coverage of this present patent is not limited to them. On the contrary, this patent covers all methods, devices and articles of manufacture, falling completely within the scope of the claims of this patent.
    权利要求:
    Claims (21)
    [0001]
    1. Method for initiating a verification test within a flow meter, characterized by the fact that it comprises: providing a flow meter, connected in line with a tube, which includes one or more tubes that define an inlet opening and a outlet opening through which the fluid in the tube flows; communicate, via a flow computer, a request for a flow meter to initiate a flow meter verification test, in which the verification test includes vibrating the tubes to cause vibrations in the tubes while material flows through the tubes; retrieve diagnostic data from the flow meter, where diagnostic data is based on tube vibrations; and recording a verification test result in a flow computer record, the result based on the diagnostic data.
    [0002]
    2. Method, according to claim 1, characterized by the fact that it also comprises registering a start event in the register corresponding to the request to start the verification test.
    [0003]
    3. Method, according to claim 1, characterized by the fact that it additionally comprises: receiving a request to abort the verification test; and record an abort event corresponding to the request to abort the verification test.
    [0004]
    4. Method according to claim 1, characterized by the fact that the diagnostic data comprises an indication of at least one of an operational state of the verification test, a value of a secondary parameter associated with the flow meter, a verification test progress, or verification test completion, where the secondary parameter value is measured during the verification test or calculated during the verification test.
    [0005]
    5. Method, according to claim 4, characterized by the fact that the result is based on a comparison of the value of the secondary parameter and a boundary limit associated with the secondary parameter, the value of the secondary parameter determined based on the verification test , the boundary limit defined by a factory specification.
    [0006]
    6. Method, according to claim 1, characterized by the fact that it further comprises sending feedback data associated with the verification test via at least one of a host supervisory control and data acquisition system associated with the flow meter, a flow computer operator display, or an external device, the feedback data comprising the verification test result.
    [0007]
    7. Method, according to claim 6, characterized by the fact that if the result corresponds to a failure of the flow meter when passing the verification test, the feedback data comprises at least one of an alarm associated with the failure, one verification test progress corresponding to when the failure was determined, or a reason for the failure
    [0008]
    8. Method, according to claim 1, characterized by the fact that the result corresponds to one of a success event or a failure event, the success event corresponding to the flow meter passing the verification test, the failure event corresponding to the flow meter failing the verification test.
    [0009]
    9. Method, according to claim 1, characterized by the fact that the record corresponds to at least one of an event record, an alarm record or an audit trail.
    [0010]
    10. Method according to claim 1, characterized by the fact that the flow meter is a coriolis flow meter.
    [0011]
    11. Method, according to claim 1, characterized by the fact that the request to start the verification test is triggered based on a schedule defined by an operator.
    [0012]
    12. Flow computer, characterized by the fact that it comprises: a flow meter interface to communicatively couple the flow computer to a flow meter, the flow meter interface to communicate a request to the flow meter to initiate a flow test checking the flow meter and retrieving diagnostic data from the flow meter, in which the flow meter is connected in line with a tube, which includes one or more tubes that define an inlet and an outlet opening through which the fluid in the tube flows, where the verification test includes vibrating the tubes to cause vibrations in the tubes while material flows through the tubes and where the diagnostic data is based on the vibrations of the tubes; and a memory to record a verification test result, the result based on the diagnostic data.
    [0013]
    13. Flow computer, according to claim 12, characterized by the fact that the memory is for recording a start event in the register corresponding to the request to start the verification test.
    [0014]
    14. Flow computer, according to claim 12, characterized by the fact that the flow meter interface is to receive a request to abort the verification test, the memory is to record an abort event corresponding to the request to abort the verification test.
    [0015]
    15. Flow computer, according to claim 12, characterized by the fact that it also comprises an external interface to connect the flow computer communicatively to at least one of a host control and data acquisition system associated with the meter flow, a flow computer operator display, or an external device, the external interface to send the verification test result.
    [0016]
    16. Flow computer, according to claim 15, characterized by the fact that if the result corresponds to a failure of the flow meter to pass the verification test, the external interface is to send at least one of an alarm associated with the failure, a verification test progress corresponding to when the failure was determined, or a reason for the failure.
    [0017]
    17. Tangible machine-readable storage medium, characterized by the fact that it comprises instructions that, when executed, make at least one machine: communicate a request for a flow meter to initiate a verification test of a flow meter, in which the flow meter is connected in line with a tube, which includes one or more tubes that define an inlet and an outlet opening through which the fluid in the tube flows, in which the verification test includes vibrating the tubes to cause vibrations in the tubes as material flows through the tubes; retrieve diagnostic data from the flow meter, where diagnostic data is based on tube vibrations; and recording a verification test result in a flow computer record, the result based on the diagnostic data.
    [0018]
    18. Storage medium according to claim 17, characterized by the fact that the instructions, when executed, cause the machine to register a start event in the register corresponding to the request to start the verification test.
    [0019]
    19. Storage medium, according to claim 17, characterized by the fact that the instructions, when executed, make the machine: receive a request to abort the verification test; and record an abort event corresponding to the request to abort the verification test.
    [0020]
    20. Storage medium according to claim 17, characterized by the fact that the instructions, when executed, still cause the machine to send feedback data associated with the verification test via at least one of a host supervisory control system and data acquisition associated with the flow meter, a flow computer operator display, or an external device, the feedback data comprising the verification test result.
    [0021]
    21. Storage medium according to claim 18, characterized by the fact that if the result corresponds to a failure of the flow meter when passing the verification test, the feedback data comprises at least one of an alarm associated with the failure , a verification test progress corresponding to when the failure was determined, or a reason for the failure.
    类似技术:
    公开号 | 公开日 | 专利标题
    BR112014028361B1|2020-10-20|method for initiating a verification test within a flow meter, flow computer, and machine-readable, tangible storage medium
    RU2601207C1|2016-10-27|Ultrasonic measurement of flow rate using calculated temperature with introduced correction
    BRPI0318620B1|2019-12-31|flow meter type identification
    BR112016010314B1|2020-12-08|method for measuring wellheads from at least one well using a coriolis flow meter, meter electronics, and wellhead measuring device by coriolis effect
    BR102017003152A2|2018-03-06|FAILURE DIAGNOSTIC METHOD AND SYSTEM AND HEALTH AND USE MANAGEMENT SYSTEM
    CN103718122A|2014-04-09|Field apparatus
    TW201423385A|2014-06-16|Test system and method for computer
    TW201423349A|2014-06-16|System and method for monitoring hot test of server
    JP5981029B2|2016-08-31|Method for evaluating the rotational speed of a tool mounted on a rotating spindle of a machine tool and such a machine tool
    BR112017017804B1|2021-04-27|METHOD FOR OPERATING A VIBRATORY FLOW METER, AND, METER ELECTRONICS
    US9368012B2|2016-06-14|Detector with integrated sensor platform
    JP2010517167A|2010-05-20|Process variable transmitter validation
    JP2009133227A|2009-06-18|Pump measuring equipment inspection device and method
    KR101969046B1|2019-04-15|Automated test system for water meter
    KR20150082565A|2015-07-15|A method for operating a compressor in case of failure of one or more measure signal
    BR112020000390A2|2020-07-14|monitoring apparatus and method of monitoring a system
    WO2016174958A1|2016-11-03|Water leak occurence position estimation device, system, and method
    TWI679532B|2019-12-11|Monitoring system and method
    CN107543595B|2021-04-09|Method for operating a flow meter and flow meter
    US20180157249A1|2018-06-07|Abnormality Detecting Apparatus
    CN108345471A|2018-07-31|Detection device handles the method and detection device of asynchronous event
    US7877240B2|2011-01-25|Method for detecting the sources of faults or defective measuring sensors by working case modeling and partial suppression of equations
    JP2015078555A|2015-04-23|Bridge pier soundness evaluation device and bridge pier soundness evaluation method
    KR101135747B1|2012-04-16|Method and computer-readable recording medium for controlling a measuring instrument based on ipc communications
    RU2323418C1|2008-04-27|Identification of type of flowmeter
    同族专利:
    公开号 | 公开日
    JP2015521284A|2015-07-27|
    CN205228596U|2016-05-11|
    MX2014013748A|2015-08-20|
    JP6404210B2|2018-10-10|
    CN111595420A|2020-08-28|
    RU2014148734A|2016-07-10|
    WO2013170247A1|2013-11-14|
    BR112014028361A2|2017-06-27|
    EP2847550B1|2021-04-28|
    RU2634794C2|2017-11-03|
    AR091026A1|2014-12-30|
    CA2873220A1|2013-11-14|
    US20130304411A1|2013-11-14|
    MX353611B|2018-01-18|
    EP2847550A1|2015-03-18|
    CN103424163A|2013-12-04|
    US9658097B2|2017-05-23|
    引用文献:
    公开号 | 申请日 | 公开日 | 申请人 | 专利标题
    US6536469B2|1999-06-29|2003-03-25|Fisher Controls International, Inc.|Self-centering magnet assembly for use in a linear travel measurement device|
    US6978210B1|2000-10-26|2005-12-20|Conocophillips Company|Method for automated management of hydrocarbon gathering systems|
    WO2006073388A1|2004-12-30|2006-07-13|Micro Motion, Inc.|A method and apparatus for directing the use of a coriolis flow meter|
    US7337084B2|2005-06-21|2008-02-26|Invensys Systems, Inc.|Switch-activated zero checking feature for a Coriolis flowmeter|
    CA2622976C|2005-09-19|2013-05-07|Micro Motion, Inc.|Meter electronics and methods for verification diagnostics for a flow meter|
    US7774150B2|2005-10-03|2010-08-10|Micro Motion, Inc.|Meter electronics and methods for determining one or more of a stiffness coefficient or a mass coefficient|
    US8027793B2|2006-07-10|2011-09-27|Daniel Measurement And Control, Inc.|Method and system of validating data regarding measured hydrocarbon flow|
    JP4822066B2|2006-12-20|2011-11-24|横河電機株式会社|Field device diagnostic equipment|
    US7768530B2|2007-01-25|2010-08-03|Fisher-Rosemount Systems, Inc.|Verification of process variable transmitter|
    US8046519B2|2008-10-20|2011-10-25|Daniel Measurement And Control, Inc.|Coupling a specialty system, such as a metering system, to multiple control systems|
    JP4952820B2|2010-05-13|2012-06-13|横河電機株式会社|Coriolis flow meter|
    CN102081370B|2010-11-26|2012-08-29|华中农业大学|Control method of water-fertilizer integrated intelligent accurate control system|
    JP2011137834A|2011-03-08|2011-07-14|Micro Motion Inc|Method and device for giving guidance on use of coriolis flowmeter|US20190101426A1|2013-06-14|2019-04-04|Dresser, Llc|Maintaining redundant data on a gas meter|
    US20190324005A1|2013-06-14|2019-10-24|Natural Gas Solutions North America, Llc|Modular metering system|
    EP3008428B1|2013-06-14|2021-02-24|Micro Motion, Inc.|Vibratory flowmeter and method for meter verification|
    SG11201605838RA|2014-01-24|2016-08-30|Micro Motion Inc|Vibratory flowmeter and methods and diagnostics for meter verification|
    US9689736B2|2014-10-31|2017-06-27|Invensys Systems, Inc.|Method to provide a quality measure for meter verification results|
    US9664659B2|2014-11-05|2017-05-30|Dresser, Inc.|Apparatus and method for testing gas meters|
    JP6293644B2|2014-11-10|2018-03-14|アズビル株式会社|Electromagnetic flowmeter test method and test system|
    JP6339927B2|2014-12-08|2018-06-06|アズビル株式会社|Electromagnetic flowmeter test method and test system|
    JP6361641B2|2015-12-03|2018-07-25|横河電機株式会社|Field equipment|
    US10908012B2|2017-04-02|2021-02-02|Natural Gas Solutions North America, Llc|Initializing a test apparatus for proving operation of gas meters|
    MX2019013471A|2017-06-14|2020-02-12|Micro Motion Inc|Frequency spacings to prevent intermodulation distortion signal interference.|
    CN109951348A|2017-12-21|2019-06-28|北京奇虎科技有限公司|A kind of method, apparatus and electronic equipment of quality that verifying application traffic|
    KR20210047299A|2018-08-02|2021-04-29|파나메트릭스 엘엘씨|Flow meter as an asset|
    DE102018133316B4|2018-12-21|2021-03-11|Endress+Hauser Flowtec Ag|Method for operating a field device in automation technology and a field device in automation technology|
    法律状态:
    2018-12-04| B06F| Objections, documents and/or translations needed after an examination request according [chapter 6.6 patent gazette]|
    2020-02-04| B06U| Preliminary requirement: requests with searches performed by other patent offices: procedure suspended [chapter 6.21 patent gazette]|
    2020-05-26| B09A| Decision: intention to grant [chapter 9.1 patent gazette]|
    2020-10-20| B16A| Patent or certificate of addition of invention granted [chapter 16.1 patent gazette]|Free format text: PRAZO DE VALIDADE: 20 (VINTE) ANOS CONTADOS A PARTIR DE 13/05/2013, OBSERVADAS AS CONDICOES LEGAIS. |
    优先权:
    申请号 | 申请日 | 专利标题
    US201261645865P| true| 2012-05-11|2012-05-11|
    US61/645,865|2012-05-11|
    PCT/US2013/040726|WO2013170247A1|2012-05-11|2013-05-13|Systems and methods to initiate a verification test within a flow meter via a flow computer|
    [返回顶部]