Notification of events in the meter and distribution of process data

Abstract

A meter electronic device (20) is provided that is configured to notify events and distribute process data. The meter electronic device (20) includes a memory (230) configured to continuously store process data (410) for a duration (412); and a processor (210) communicatively coupled to the memory (230). The processor (210) is configured to detect one or more events (430) in the process data (410) and to generate at least one of a notification (460) and distribute the process data (410) based on the detected one or more events (430).

Description

Technical Field

[0001] The embodiments described below relate to process data in a meter, and more particularly, to providing notification of events in a meter and distribution of process data. Background Art

[0002] Meters such as Coriolis mass flow meters, liquid density meters, gas density meters, liquid viscometers, gas / liquid specific gravity meters, gas / liquid relative density meters, and gas molecular weight meters are commonly known and used to measure the properties of fluids. Typically, the meter includes a sensor assembly and an electronics section. The material within the sensor assembly can be flowing or stationary. Each type of sensor can have unique characteristics that the meter must account for to achieve optimal performance. For example, some sensors may require a tube assembly to vibrate at a specific displacement level. Other sensor assembly types may require specific compensation algorithms. These requirements are similar to those in other meters based on other technologies such as magnetic flowmeters, ultrasonic, etc.

[0003] Regardless of the technology, meters typically include meter electronics that can store process data. This process data can include measurements of the material being measured by the meter, measurements of environmental conditions, values ​​related to the condition of the meter, and the like. Process data can be stored as a history file. This history file can store various types of data with varying write frequencies. History files can also store derived data such as moving averages, standard deviations, differences between parameters, and the like. Storing large amounts of data with a relatively long duration and / or a relatively high write frequency can be valuable to customers. For example, a customer may wish to perform post-event analysis on process data and may wish to access data before and after the event.

[0004] However, storing large amounts of data, for example due to frequent sampling and writing of process parameters, can be very expensive. Customers may also not want to analyze all events or all process data after an event. Customers may also desire to reduce the effort associated with accessing process data or monitoring events. Therefore, there is a need to provide event notification and process data distribution within the meter. Summary of the Invention

[0005] A meter electronics device configured to notify events and distribute process data is provided. According to an embodiment, the meter electronics device includes a memory configured to continuously store process data for a duration of time; and a processor communicatively coupled to the memory. The processor is configured to detect one or more events in the process data and at least one of generate a notification and distribute the process data based on the detected one or more events.

[0006] A meter configured to notify events and distribute process data is provided. According to an embodiment, the meter includes meter electronics configured to continuously store process data for a duration. The meter electronics is configured to detect one or more events in the process data and to at least one of generate a notification and distribute the process data based on the detected one or more events.

[0007] A method for notifying events and distributing process data is provided. According to an embodiment, the method includes: continuously storing process data for a duration; detecting one or more events in the process data; and generating at least one of a notification and distributing the process data based on the detected one or more events.

[0008] All aspects

[0009] According to one aspect, a meter electronic device (20) configured to notify events and distribute process data includes a memory (230) configured to continuously store process data (410) for a duration (412), a processor (210) communicatively coupled to the memory (230), and the processor (210) configured to detect one or more events (430) in the process data (410) and to generate at least one of a notification (460) and distribute the process data (410) based on the detected one or more events (430).

[0010] Preferably, the processor (210) is further configured to generate a notification (460) based on the previous context length (444).

[0011] Preferably, the processor (210) being configured to generate the notification (460) includes the processor (210) being configured to include information related to the detected one or more events (430) in the notification (460).

[0012] Preferably, the processor (210) is configured to generate the notification (460) including information related to the downloading process data (410) in the notification (460).

[0013] Preferably, the processor (210) is further configured to provide a notification (460) via at least one of the port (26) and the user interface (30).

[0014] Preferably, the processor (210) is further configured to distribute the process data (410) into distributed process data (450), the distributed process data (450) including event-related process data (410a).

[0015] Preferably, the allocated process data (450) further includes at least one of pre-context data (410b) and post-context data (410c).

[0016] Preferably, the processor (210) is further configured to provide the allocated process data (450) via at least one of the port (26) and the external storage device (236).

[0017] Preferably, the processor (210) being configured to detect the one or more events (430) includes the processor (210) being configured to determine whether a process parameter (340) exceeds a threshold value.

[0018] According to one aspect, a meter (5) configured to notify events and distribute process data includes meter electronics (20) configured to continuously store process data (410) for a duration (412). The meter electronics (20) is configured to detect one or more events (430) in the process data (410) and to at least one of generate a notification (460) and distribute the process data (410) based on the detected one or more events (430).

[0019] Preferably, the meter electronics (20) is further configured to generate a notification (460) based on the previous context length (444).

[0020] Preferably, the meter electronics (20) being configured to generate the notification (460) includes the meter electronics (20) being configured to include information related to the detected one or more events (430) in the notification (460).

[0021] Preferably, the meter electronics (20) being configured to generate the notification (460) includes the meter electronics (20) being configured to include information related to the downloading process data (410) in the notification (460).

[0022] Preferably, the meter electronics (20) is further configured to provide a notification (460) via at least one of the port (26) and the user interface (30).

[0023] Preferably, the meter electronics (20) is further configured to distribute the process data (410) into distributed process data (450), the distributed process data (450) including event-related process data (410a).

[0024] Preferably, the allocated process data (450) further includes at least one of pre-context data (410b) and post-context data (410c).

[0025] Preferably, the meter electronics (20) is further configured to provide the allocated process data (450) via at least one of the port (26) and the external storage device (236).

[0026] Preferably, the meter electronics (20) being configured to detect the one or more events (430) includes the meter electronics (20) being configured to determine whether a process parameter (340) exceeds a threshold value.

[0027] According to one aspect, a method for notifying events and distributing process data includes continuously storing process data for a duration; detecting one or more events in the process data; and generating at least one of a notification and distributing the process data based on the detected one or more events.

[0028] Preferably, the method further comprises generating a notification based on the previous context length.

[0029] Preferably, generating the notification comprises including information related to the detected one or more events in the notification.

[0030] Preferably, generating the notification includes including information related to the downloading process data in the notification.

[0031] Preferably, the method further comprises providing notification via at least one of a port and a user interface.

[0032] Preferably, the method further comprises: allocating the process data into allocated process data, the allocated process data comprising event-related process data.

[0033] Preferably, the allocated process data further includes at least one of pre-context data and post-context data.

[0034] Preferably, the method further comprises providing the allocated process data via at least one of a port and an external storage device.

[0035] Preferably, the method further comprises detecting one or more events if the process parameter exceeds a threshold value. BRIEF DESCRIPTION OF THE DRAWINGS

[0036] Like reference numerals represent like elements throughout the drawings.It should be understood that these drawings are not necessarily drawn to scale.

[0037] Figure 1 A meter 5 is shown which notifies of events and distributes process data.

[0038] Figure 2 A block diagram of the meter 5 is shown, including a block representation of the meter electronics 20 .

[0039] Figure 3 Meter electronics 20 are shown for notifying events and distributing process data in a meter.

[0040] Figure 4 An allocation 400 of process data 410 is shown.

[0041] Figure 5 A method 500 for notifying events and distributing process data is shown. DETAILED DESCRIPTION

[0042] Figures 1 to 5 The following description depicts specific examples to teach those skilled in the art how to create and use the best mode of implementation of notification events and distribution process data. For the purpose of teaching the inventive principles, some conventional aspects have been simplified or omitted. Those skilled in the art will appreciate variations of these examples that fall within the scope of this specification. Those skilled in the art will appreciate that the features described below can be combined in various ways to form multiple variations of notification events and distribution process data. Therefore, the embodiments described below are not limited to the specific examples described below, but are limited only by the claims and their equivalents.

[0043] Figure 1 A meter 5 is shown which notifies events and distributes process data. Figure 1 As shown, meter 5 is a vibrating meter including a sensor assembly 10 and meter electronics 20, but any suitable meter may be used. Sensor assembly 10 is responsive to the mass flow rate and density of the process material. Meter electronics 20 is connected to sensor assembly 10 via leads 100 to provide density, mass flow rate, and temperature information on path 26, as well as other information.

[0044] The sensor assembly 10 includes a pair of manifolds 150 and 150', flanges 103 and 103' having flanged necks 110 and 110', a pair of parallel conduits 130 and 130', a driver 180, a resistance temperature detector (RTD) 190, and a pair of inductive sensors 170l and 170r. The conduits 130 and 130' have two substantially straight inlet branches 131 and 131' and outlet branches 134 and 134' that converge toward each other at conduit mounting blocks 120 and 120'. The conduits 130 and 130' bend at two symmetrical locations along their lengths and are substantially parallel throughout their lengths. Struts 140 and 140' define axes W and W' about which each conduit 130 and 130' oscillates. Branches 131, 131' and 134, 134' of conduits 130, 130' are fixedly attached to conduit mounting blocks 120 and 120', which in turn are fixedly attached to manifolds 150 and 150'. This provides a continuous closed material path through sensor assembly 10.

[0045] When flanges 103 and 103' having holes 102 and 102' are connected via inlet and outlet ports 104 and 104' to a process line (not shown) carrying the process material being measured, the material enters the meter's inlet port 104 through orifice 101 in flange 103 and is directed through manifold 150 to conduit mounting block 120 having surface 121. Within manifold 150, the material is separated and conveyed through conduits 130, 130'. Upon exiting conduits 130, 130', the process material recombines into a single stream within block 120' having surface 121' and manifold 150' and is thereafter conveyed to outlet port 104' connected to a process line (not shown) via flange 103' having hole 102'.

[0046] The conduits 130, 130' are selected and appropriately mounted to the conduit mounting blocks 120, 120' so as to have substantially the same mass distribution, moment of inertia, and Young's modulus about the bending axes W--W and W'--W', respectively. These bending axes pass through the support rods 140, 140'. Since the Young's modulus of the conduit changes with temperature, and this change affects the calculation of flow and density, an RTD 190 is mounted to the conduit 130' to continuously measure the temperature of the conduit 130'. The temperature of the conduit 130' and therefore the voltage that appears across the RTD 190 for a given current passing through the RTD 190 is controlled by the temperature of the material passing through the conduit 130'. The temperature-dependent voltage that appears across the RTD 190 is used by the meter electronics 20 in a known manner to compensate for changes in the elastic modulus of the conduits 130, 130' caused by any changes in the conduit temperature. The RTD 190 is connected to the meter electronics 20 via a lead 195.

[0047] Both conduits 130, 130' are driven by a driver 180 in opposite directions about their respective bending axes W and W', and in what is referred to as the first out-of-phase bending mode of the flow meter. The driver 180 can include any of a number of well-known arrangements, such as a magnet mounted to conduit 130' and an opposing coil mounted to conduit 130, through which alternating current is passed to vibrate both conduits 130, 130'. A suitable drive signal 185 is applied to the driver 180 by the meter electronics 20 via leads.

[0048] Meter electronics 20 receives the RTD temperature signal on lead 195, as well as the left and right sensor signals present on conductor 100, carrying left and right sensor signals 1651, 165r, respectively. Meter electronics 20 generates a drive signal 185 that appears on leads to driver 180 and causes conduits 130, 130' to vibrate. Meter electronics 20 processes the left and right sensor signals, along with the RTD signal, to calculate the mass flow rate and density of the material passing through sensor assembly 10. This information, along with other information, is applied by meter electronics 20 as a signal on port 26.

[0049] Figure 2 A block diagram of the meter 5 is shown, including a block diagram representation of the meter electronics 20. Figure 2 As shown in FIG, the meter electronics 20 is communicatively coupled to the sensor assembly 10. As previously described with reference to FIG. Figure 1 As depicted, the sensor assembly 10 includes left and right pickoff sensors 1701 and 170 r , a driver 180 , and an RTD 190 , which are communicatively coupled to the meter electronics 20 via a set of leads 100 through a communication channel 112 and an I / O port 260 .

[0050] The meter electronics 20 provides a drive signal 185 via the leads 100. More specifically, the meter electronics 20 provides the drive signal 185 to the driver 180 in the sensor assembly 10. Furthermore, the sensor signal 165 is provided by the sensor assembly 10. More specifically, in the illustrated embodiment, the sensor signal 165 is provided by the left pickoff sensor 1701 and the right pickoff sensor 170r in the sensor assembly 10. It will be appreciated that the sensor signals 165 are provided to the meter electronics 20 separately via the communication channel 112.

[0051] The meter electronics 20 includes a processor 210 communicatively coupled to one or more signal processors 220 and one or more memories 230. The processor 210 is also communicatively coupled to the user interface 30. The processor 210 is communicatively coupled to the host computer via a communication port on path 26 and receives power via a power port 250. The processor 210 can be a microprocessor, but any suitable processor can be used. For example, the processor 210 can be composed of sub-processors such as a multi-core processor, serial communication ports, peripheral interfaces (e.g., a serial peripheral interface), on-chip memory, I / O ports, etc. In these and other embodiments, the processor 210 is configured to perform operations on received and processed signals, such as digitized signals.

[0052] The processor 210 can receive digitized sensor signals from one or more signal processors 220. The processor 210 is also configured to provide information such as phase difference, properties of the fluid in the sensor assembly 10, etc. The processor 210 can provide this information to a host computer via a communication port. The processor 210 can also be configured to communicate with one or more memories 230 to receive and / or store information in the one or more memories 230. For example, the processor 210 can receive calibration factors and / or a sensor assembly zero point (e.g., a phase difference when there is zero flow) from the one or more memories 230. Each of the calibration factors and / or sensor assembly zero points can be associated with the flow meter 5 and / or the sensor assembly 10, respectively. The processor 210 can use the calibration factors to process the digitized sensor signals received from the one or more signal processors 220.

[0053] The one or more signal processors 220 are shown as including a coder / decoder (CODEC) 222 and an analog-to-digital converter (ADC) 226. The one or more signal processors 220 can condition analog signals, digitize conditioned analog signals, and / or provide digitized signals. The CODEC 222 is configured to receive sensor signals 165 from the left pickup sensor 1701 and the right pickup sensor 170r. The CODEC 222 is also configured to provide a drive signal 185 to the driver 180. In alternative embodiments, more or fewer signal processors may be employed.

[0054] As shown, the sensor signal 165 is provided to the CODEC 222 via the signal conditioner 240. The drive signal 185 is provided to the driver 180 via the signal conditioner 240. Although the signal conditioner 240 is shown as a single block, the signal conditioner 240 may include signal conditioning components, such as two or more operational amplifiers, filters such as low-pass filters, voltage-to-current amplifiers, etc. For example, the sensor signal 165 may be amplified by a first amplifier, and the drive signal 185 may be amplified by a voltage-to-current amplifier. Amplification can ensure that the amplitude of the sensor signal 165 is close to the full scale range of the CODEC 222.

[0055] In the illustrated embodiment, the one or more memories 230 include a read-only memory (ROM) 232, a random access memory (RAM) 234, and an external storage device (ESD) 236. However, in alternative embodiments, the one or more memories 230 may include more or less memory. Additionally or alternatively, the one or more memories 230 may include different types of memory (e.g., volatile memory, non-volatile memory, etc.). For example, different types of non-volatile memory, such as erasable programmable read-only memory (EPROM), may be used in place of the external storage device 236. As shown, the external storage device 236 may be a flash memory card, a USB memory stick, etc. that can be removed by the user. The one or more memories 230 may be a storage device configured to store data, such as calibration values, meter verification values, etc. These values ​​may be used to calculate the mass flow rate.

[0056] The mass flow rate measurement can be generated according to the following formula

[0057]

[0058] The Δt term includes an operationally derived (i.e., measured) time delay value that includes the time delay that exists between pickup sensor signals, for example, where the time delay is due to the Coriolis effect related to the mass flow rate through the vibrating flow meter 5. As the flow material flows through the vibrating flow meter 5, the measured Δt term ultimately determines the mass flow rate of the flow material. The Δt0 term includes the time delay / phase difference at zero flow calibration constant. The Δt0 term is typically determined at the factory and programmed into the vibrating flow meter 5. The time delay / phase difference Δt0 term at zero flow will not change, even if flow conditions change. The flow calibration factor FCF is proportional to the physical stiffness of the flow meter. Calibration and meter check terms, mass flow rate, and other process parameters can have corresponding values ​​that can be stored and processed in the meter electronics 20.

[0059] Figure 3 The meter electronics 20 for notifying events and distributing process data in the meter is shown. The meter electronics 20 may include an interface 301 and a processing system 302. The meter electronics 20, for example, receives a vibration response from the meter assembly 10. The meter electronics 20 processes the vibration response to obtain flow characteristics of the flowing material flowing through the sensor assembly 10. Figure 3 As shown, meter electronics 20 includes a processing system 302 communicatively coupled to a memory system 304. Processing system 302 is also communicatively coupled to interface 301 and port 303.

[0060] Interface 301 via Figure 1 Lead 100 receives the vibration response from each of the pickup sensors 170l, 170r. Interface 301 can perform any necessary or desired signal conditioning, such as any form of formatting, amplification, buffering, etc. Alternatively, some or all of the signal conditioning can be performed in processing system 302. In addition, interface 301 can enable communication between meter electronics 20 and external devices. Interface 301 is capable of any form of electronic, optical, or wireless communication. Interface 301 can provide information based on the vibration response. In one embodiment, interface 301 is coupled to a digitizer (not shown), wherein the sensor signal includes an analog sensor signal. The digitizer can sample and digitize the analog vibration response and generate a digital vibration response.

[0061] Port 303 may be an input / output port, such as that previously described. Figure 1 and Figure 2 Port 26 is described in detail, but any suitable port can be used. Port 303 can communicate with, for example, a user's terminal or server to provide, receive and / or exchange data. For example, process data can be provided to the user's terminal or server by processing system 302. The user's terminal or server can also send commands or requests to processing system 302 via port 303. Port 303 can be of any suitable type and conform to any suitable protocol, such as RS-232, universal serial bus (USB), etc. Port 303 can also be configured to be connected to a network, such as a master-slave network, in which the user's computer or server acts as a host, but any suitable network configuration can be used.

[0062] The processing system 302 operates the meter electronics 20 and processes flow measurements from the meter assembly 10. The processing system 302 executes one or more processing routines to process the flow measurements to generate one or more flow characteristics. The processing system 302 is communicatively coupled to the interface 301 and is configured to receive information from the interface 201.

[0063] Processing system 302 may include a general purpose computer, a microprocessor system, a logic circuit, or some other general purpose or custom processing device. Additionally or alternatively, processing system 302 may be distributed among multiple processing devices. Processing system 302 may also include any manner of integrated or independent electronic storage media, such as storage system 304. Processing system 302 may include reference Figure 2 A processor 210 and one or more memories 230 are depicted, but any suitable processing system may be employed.

[0064] The storage system 304 may store flow meter parameters and data, software routines, constant values, and variable values. In one embodiment, the storage system 304 includes routines executed by the processing system 302, such as the meter 5 operation routine 310, notification routine 320, and / or allocation routine 330. The storage system 304 may also store statistical values, such as standard deviations, confidence intervals, etc. The storage system 304 may include reference Figure 2 One or more memories 230 are described.

[0065] like Figure 3 As shown, storage system 304 includes an operating routine 310, a notification routine 320, and a distribution routine 330. Operating routine 310 performs steps for measuring and determining values ​​of process parameters. For example, operating routine 310 may receive sensor signals from sensor assembly 10 and determine the density, mass flow rate, viscosity, etc. of the material in the sensor assembly. Operating routine 310 may also determine other values ​​of process parameters that are not properties of the material, such as drive gain, drive signal parameters (e.g., amplitude, frequency, phase), etc. Other process parameters may be derived from the measured material properties and / or other process parameters such as void fraction, total mass flow rate, material composition, etc. These and other values ​​may be continuously sampled and written to storage system 304 as process parameters 340.

[0066] like Figure 3 As shown, process parameters 340 include a drive signal 341, a left pickup signal 342, and a right pickup signal 343. Such signals can be measurements of the amplitude, frequency, and / or phase of the drive signal 341, the left pickup signal 342, and the right pickup signal 343, respectively. The drive signal 341, the left pickup signal 342, and the right pickup signal 343 can have one or more frequency components and any suitable shape, such as sinusoidal, square, triangular, etc. The drive signal 341, the left pickup signal 342, and the right pickup signal 343 can be used to determine a drive gain 344. The drive signal 341, the left pickup signal 342, the right pickup signal 343, and the drive gain 344 can be provided and / or measured by the operating routine 310.

[0067] The process parameters 340 also include measured properties of the material derived from the drive signal 341, the left pickoff signal 342, the right pickoff signal 343, and / or the drive gain 344. Figure 3 As shown, process parameters 340 include mass flow rate 345 and density 346. Mass flow rate 345 can be determined by operating routine 310 by determining a time delay or phase difference between left pickoff signal 342 and right pickoff signal 343. Operating routine 310 can also determine density 346 based on the frequency of drive signal 341. However, any suitable method can be used to determine the values ​​of mass flow rate 345 and density 346.

[0068] These and / or other process parameters can indicate that an event has occurred. For example, a relatively high value of drive gain 344 can indicate a void in the material. Thus, a threshold value can be used to determine the presence of a void in the material. That is, if the value of drive gain 344 is greater than a corresponding drive gain threshold value, then the operating routine 310 can determine that a void exists in the material. The operating routine 310 can store the values ​​of the process parameters 340 as event-related process data corresponding to each process parameter 340. The operating routine 310 can also store the presence of a void as an event in the storage system 304, as will be described in more detail below.

[0069] like Figure 3 As shown, storage system 304 includes event 350. Event 350 can include any suitable event indicator, such as a tag, code, description, etc., and, in some embodiments, information about relevant process parameters 340. For example, event 350 can include a "gap" tag with a timestamp and a relevant process parameter tag indicating which values ​​of relevant process parameters 340 indicate a gap. As an example, the "gap" tag in event 350 can be associated with values ​​of drive gain 344 that exceed a corresponding drive gain threshold. This association can be, for example, a timestamp indicating which values ​​of drive gain 344 exceed the corresponding drive gain threshold. However, any suitable format and / or information can be included in event 350.

[0070] Process parameters 340 may include history files in storage system 304 that contain process data with values ​​periodically written to the history files at fixed intervals and stored for a duration. That is, the process data may be continuously stored in storage system 304 as measurements are taken. The process data for process parameters 340 may be history data, such as a time-stamped list of values, a table with a value column and a timestamp column, a sequential list of values ​​with date / time related information, and the like. In this example, the most recent value may be the first value in the process data, and the oldest value may be the last value in the process data, but any suitable structure may be employed. Although the process data for process parameters 340 may be described as history data with a fixed sampling / writing interval, for example, stored for a fixed duration, the sampling / writing interval and / or duration may be dynamic and based on something other than time, such as the size of a file, database, list, or record.

[0071] Drive gain 344 may have a short duration but consume a large portion of storage system 304. More specifically, the process data for drive gain 344 may be relatively large in size and may also have a relatively short duration. For example, the value of drive gain 344 may be considered "fast data" that is written every 1 to 10 seconds. Due to the data density required to store information with relatively short sampling / writing intervals, fast data such as drive gain 344 may be short in duration. As an example, the duration of drive gain 344 may be one week, but any suitable duration may be used.

[0072] Other process parameters 340, such as the average value of the mass flow rate 345, can have a large duration. More specifically, for this example, the process data including the average value of the mass flow rate 345 can have a relatively long duration. By way of illustration, the average value of the mass flow rate 345 can be considered as "slow data" that is written every five minutes. The duration of the slow data can be long due to the lack of data density caused by the infrequent writing of the average value of the mass flow rate 345 (e.g., long sampling / writing intervals). The duration of the average value of the mass flow rate 345 can be 30 days, but any suitable duration can be used. The duration of the slow data is generally greater than the duration of the fast data, even though they can be equal in size.

[0073] Data that is not within the duration of the process data is not retained in the storage system 304 and, therefore, may not be available for analysis. Therefore, if a gap event occurs outside the duration of the drive gain 344, a user cannot obtain, for example, the value of the drive gain 344 associated with the gap event. More specifically, in this example, a user would not be able to download a value of the drive gain 344 that was written at a time earlier than the duration of the drive gain 344.

[0074] Processing system 302 may execute notification routine 320 to generate notification 360 based on one or more events, such as events in event 350. Notification 360 may include information related to event 350, such as Figure 3 For example, if the value of drive gain 344 exceeds the corresponding drive gain threshold, processing system 302 can generate notification 360 including event information 362 indicating the presence of a void in the material. Notification 360 may not include the value of drive gain 344 exceeding the corresponding drive gain threshold. Notification 360 may be generated simultaneously with event 350.

[0075] Because notification 360 is generated simultaneously with the event, the user may be able to download process data for drive gain 344 for the duration of the drive gain 344. For example, upon receiving the notification, the user may immediately download the process data for drive gain 344 to external storage device 236 and remove external storage device 236 for offline analysis. However, the user may not be able to download the data immediately and may need to set aside time in the future to download the process data, and may need information about the duration of the process data associated with the event.

[0076] Thus, the processing system 302 may also execute the notification routine 320 to generate a notification 360 based on the duration of the process data of the process parameter 340. For example, Figure 3 As shown, notification 360 may include availability information 364 indicating when process data associated with the event will be available for download. Availability information 364 may include a date and time, a duration (e.g., 7 days), etc. Thus, a user may be informed when process data associated with an event may no longer be available and may schedule downloads of the process data accordingly. However, a user may not know what process data is associated with the event and how the associated process data can be downloaded.

[0077] Thus, processing system 302 may also generate notification 360 based on the process data that can be downloaded. For example, notification 360 may include download information 366 indicating how the process data can be accessed, the process data associated with an event, and the like. For example, event information 362 may indicate the presence of a void in the material, but may not indicate which process parameter 340 indicates the presence of the void. Thus, download information 366 may also notify the user that process data for drive gain 344 is associated with an event, such as a void in the material. Download information 366 may also indicate that the process data is available via port 303 and / or external storage device 236.

[0078] Thus, a user can download process data associated with the event using notification 360. For example, notification 360 may include event information 362 indicating that the event is a void in the material, availability information 364 indicating that the process data is available, for example, within a week, and download information 366 indicating that the process data for drive gain 344 is associated with the event and can be downloaded via port 303. However, port 303 and external storage device 236 may have limited bandwidth and / or memory.

[0079] The processing system 302 may accordingly execute an allocation routine 330 to allocate process data for the process parameters 340. For example, the processing system 302 may execute an allocation routine 330 that reduces the size of the process data available for download by a user. The process data for the process parameters 340 may be allocated by selecting a portion of the process data associated with the event and saving the selected data as allocated process data 370. The allocated process data 370 may also include contextual data for the process data associated with the event. Figure 3 As shown, the allocated process data 370 includes pre-context data 372 and post-context data 374, which will be referred to below. Figure 4 Describe them in more detail.

[0080] Still refer to Figure 3 Various attributes of or related to the notifications 360 and / or the assigned process data 370 can be configured in the configuration 380. For example, a user can configure the meter electronics 20 to only notify the user of certain events. The meter electronics 20 can also be configured to repeat notifications within a notification period. More specifically, the meter electronics 20 can be configured to generate and provide notifications 360, 460 every hour for 12 hours, although other rates and / or periods may be used.

[0081] Additionally or alternatively, the meter electronics 20 may be configured by the configuration 380 to store the assigned process data 370 for an assigned data duration that is longer than the duration of the process data for the process parameter 340. For example, the configuration 380 may configure the meter electronics 20 to store the assigned process data 370 for two weeks, where the duration of the process data for the process parameter 340 is one week. In another example, the configuration 380 may include an association configuration that configures the meter electronics 20 to associate some of the process parameters 340 with some of the events 350. For example, the configuration 380 may indicate that for a given event of the events 350, such as a void, the assigned process data 370 should include the drive gain 344 and the mass flow rate 345.

[0082] The configuration 380 can be read, operated on, and / or written to by the operation routine 310, the notification routine 320, and / or the allocation routine 330. For example, the operation routine 310 can update the configuration 380 with additional process parameters that the user manually selected when downloading other process data associated with the event. In another example, because the user terminated notification during the notification period, the notification routine 320 can update the configuration 380 with a reduced notification period. When the user removes the association during the download, the allocation routine 330 can add or remove the associated configuration between the process parameter 340 and the event 350. For example, a user can read the assigned process data 370 for a given event and choose to delete the process data for the process parameter 340 in the assigned process data 370 before downloading the assigned process data. The allocation routine 330 can delete the corresponding associated configuration in the configuration 380. These and other operations can be performed on the configuration 380 to ensure that the assigned process data 370 efficiently utilizes the port 303 and / or ESD 236. Figure 4 Exemplary allocated process data are described in more detail.

[0083] Example of assigned process data

[0084] Figure 4 4 shows the distribution 400 of process data 410. Figure 4 As shown, process data 410 is in a process parameter file 420 divided by day. The process parameter file 420 may be associated with, for example, the drive gain 344 described above, but may employ any suitable process parameter. The process data 410 is shown as having a duration 412 that corresponds to the 7-day duration shown in the process parameter file 420. The first data in the process parameter file 420 may be a data item corresponding to Figure 4 The most recent data for the current day is shown, and the last data in the process parameter file 420 may be the earliest data corresponding to the end of the seven-day duration. Also shown is event-related process data 410a of the process parameter file 420. Pre-context data 410b and post-context data 410c are also part of the process parameter file 420 and precede and follow, respectively, the event-related process data 410a.

[0085] As shown, event-related process data 410a may be associated with event 430. Event 430 has event length 442, pre-context data 410b has pre-context length 444, and post-context data has post-context length 446. The sum of event length 442, pre-context length 444, and post-context length 446 is span 440. Span 440 may be the span of allocated process data 450. Thus, event-related process data 410a is part of allocated process data 450. While not necessarily part of the allocated process data, Figure 4 Notification 460 is shown as being generated concurrently with the start or anterior of event 430 , but may be generated at an alternative time, such as concurrently with the end or after event 430 .

[0086] As mentioned above Figure 3 As discussed above with respect to the process parameters 340 shown in FIG, process data 410 can be any suitable data in any suitable format. For example, process data 410 can be a list of process parameter values ​​associated with a header having a timestamp for the first data and a write period, such as 5 seconds, indicating that the process parameter values ​​are written every 5 seconds. Other formats can be used, such as a table including columns for corresponding process parameter values ​​and timestamps for process parameter file 420. In these and other process data, a duration, such as in seconds, can be determined from the process data; however, duration 412 can be in any suitable format, units (e.g., hh:mm:ss), non-units (e.g., number of rows in a table), etc.

[0087] Process parameter file 420 may be a file associated with a process parameter that indicates an event, such as a drive gain value exceeding a drive gain threshold. Alternative process parameter files may be used that do not indicate an event but may still be associated with an event. For example, a drive gain exceeding a drive gain threshold may indicate a void in the material, but density 346 may also be associated with a void. That is, even if only drive gain 344 indicates a void, it may be useful to analyze process data for both drive gain 344 and density 346. As can be appreciated, more than one process data file may be downloaded, for example, with reference to Figure 3 Process data for drive gain 344 and density 346 are described.

[0088] Event 430 can be anything that indicates a process condition in the meter 5. Event 430 can be a flag, error, diagnostic, etc. related to a process condition in the meter 5. The process condition in the meter 5 can be, for example, a material condition (e.g., slug, void, mixed phase flow, etc.), a process parameter (e.g., temperature, pressure, flow rate, density) exceeding a threshold, etc. Figure 4 As shown, event 430 occurs during day 4 and is continuous, but events can occur at other times and may not be continuous. For example, in an alternative embodiment, additional events can occur during day 2. Thus, the allocated process data 450 can include all of the process data from day 2 and day 4, but not day 3.

[0089] Span 440 may be quantified in any suitable form and may or may not have units. Figure 4As shown, span 440 has a length of approximately two days, extending from approximately the middle of day 5 to approximately the middle of day 3. As shown, the available time for downloading the allocated process data 450 is approximately 2.5 days. This is due to the fact that process data 410 was written after event 430 began. In other words, some time has passed since event 430 occurred and notification 460 was sent. If only the event-related process data 410a were allocated when event 430 began, the available time would be 7 days. Availability information, such as availability information 364 discussed above, can include this and other information.

[0090] like Figure 4 As shown, assigned process data 450 can be generated based on process data 410. For example, assigned process data 450 can be generated using configuration 380 discussed above, which configures an association between event 430 and event-related process data 410a. Thus, assigned process data 450 includes event-related process data 410a. For example, if event 430 is the detection of a void in the material, event-related process data 410a may include a drive gain value exceeding a threshold. However, assigned process data 450 may also include process data that does not indicate event 430. For example, assigned process data 450 may additionally include a density value that is concurrent with event 430 but does not indicate event 430. Thus, a user can analyze process data for drive gain and density measurements.

[0091] The notification 460 may be generated based on both the duration 412 and / or the previous context length 444. As shown, the notification 460 may also include availability information indicating that the allocated process data 450 can be downloaded 6.5 days from a date and time, such as the date and time when the notification 460 is generated. The notification 460 may not indicate that the available time is 7 days because the allocated process data 450 includes the previous context data 410b. Alternatively, the notification 460 may indicate that the allocated process data 450 includes the previous context data 410b and that the previous context data 410b has a previous context length 444 of approximately 0.5 days, but may include any suitable availability information.

[0092] Notification 460 may also be generated based on event 430. For example, notification 460 may include information related to event 430, such as the void event discussed above. For example, notification 460 may include a field with an event code associated with the void event, etc. Additionally or alternatively, notification 460 may simply state that a void was detected in the material. Information related to event 430 may also include how event 430 was indicated. For example, information related to event 430 may state that the drive gain exceeded a threshold.

[0093] A notification 460 may also be generated to include information related to downloading the process data 410. For example, the notification 460 may include information about the allocated process data 450 (e.g., associated process parameters), how to download the allocated process data 450, the size of the allocated process data 450, etc. The notification 460 may be in any suitable format, such as machine-readable, simple text, a code sequence, etc. Thus, a user may be able to read the notification 460 and / or automatically download the allocated process data 450 via, for example, ports 26, 303.

[0094] As discussed above, the notification routine 320 and / or the allocation routine 330 may generate notifications and allocate process data. Figure 5 Exemplary methods for generating notifications and assigned process data (eg, notification 360 and assigned process data 370 described above) are discussed.

[0095] Method for notifying events and distributing process data

[0096] Figure 5 A method 500 for notifying an event and distributing process data is shown. Figure 5 As shown, method 500 begins by continuously storing process data for a duration in step 510. In step 520, method 500 detects one or more events in the process data. The one or more events may be the events described above or other events. If one or more values ​​of a process parameter exceed a threshold value, one or more events may be detected. Method 500 also includes at least one of step 530a and step 530b. That is, method 500 may perform step 530a and / or step 530b. In step 530a, method 500 generates a notification based on the one or more detected events. In step 530b, method 500 distributes process data based on the one or more events. In steps 530a and 530b, method 500 may also generate a notification based on the duration.

[0097] Method 500 may include additional steps, such as steps related to notifications. For example, method 500 may generate a notification based on the previous context length, as described above. Method 500 may also generate a notification to include information related to one or more detected events. A notification may also be generated to include information related to downloading process data. Method 500 may also provide notifications via a port and / or user interface.

[0098] Additionally or alternatively, method 500 may include steps related to allocating process data. For example, method 500 may allocate process data into allocated process data, wherein the allocated process data includes event-related process data. The allocated process data may also include pre-context data and / or post-context data. The allocated process data may be provided via a port and / or an external storage device.

[0099] The meter 5, meter electronics 20, and method 500 for notifying an event and distributing process data are described above. Because the meter 5, meter electronics 20, and method 500 notify the event, the user can understand the event in real time and determine whether to download process data. Consequently, the user can more efficiently prioritize interactions with the meter 5 and / or meter electronics 20. For example, the user may not want to analyze process data related to some events, but may want to analyze process data related to other events.

[0100] Furthermore, because the data is distributed, memory in the meter 5 or meter electronics 20 can be utilized more efficiently. For example, process data 410 for process parameters 340 associated with an event can be distributed into distributed process data 450 and stored in the meter electronics 20 as distributed process data 370. Distributed process data 370, 450 can be provided via ports 26, 303 and / or ESD 236. Thus, for a given event, not all of process data 410 may be downloaded by the user. This allows for more efficient use of ports 26, 303, and any network communicatively coupled thereto, as well as ESD 236.

[0101] Thus, transaction time can be reduced between an event and a user, server, system, etc., communicatively coupled to the port 26, 303 that downloads the allocated process data 450. Transaction time can be reduced by allowing the user to automate the download, for example, based on a received notification 460 and / or because the size of the allocated process data 450 is less than the size of the process data 410.

[0102] The detailed description of the above embodiments is not an exhaustive description of all embodiments contemplated by the inventors to fall within the scope of this specification. Indeed, those skilled in the art will recognize that certain elements of the above embodiments may be variously combined or eliminated to create additional embodiments, and such additional embodiments fall within the scope and teachings of this specification. It will also be apparent to those skilled in the art that the above embodiments may be combined in whole or in part to create additional embodiments within the scope and teachings of this specification.

[0103] Therefore, although specific embodiments are described herein for illustrative purposes, various equivalent modifications are possible within the scope of this specification, as will be appreciated by those skilled in the relevant art. The teachings provided herein can be applied to other notifications of events and distribution of process data, and not just to the embodiments described above and shown in the accompanying drawings. Therefore, the scope of the embodiments described above should be determined by the appended claims.

Claims

1. A meter electronics device (20) configured to notify events and distribute process data, the meter electronics device (20) comprising: a memory (230) configured to continuously store the process data (410) for a duration (412); A processor (210) communicatively coupled to the memory (230), the processor (210) being configured to: detecting one or more events (430) in the process data (410); and assigning the process data (410) into assigned process data based on the detected one or more events (430); The allocated process data includes event-related process data and context data of the event-related process data.

2. The meter electronics (20) according to claim 1, wherein The processor (210) is further configured to generate a notification (460) based on the previous context length (444).

3. The meter electronics (20) of claim 2, wherein: The processor (210) being configured to generate the notification (460) includes the processor (210) being configured to include information related to the detected one or more events (430) in the notification (460).

4. Meter electronics (20) according to one of claims 2 and 3, wherein The processor (210) is configured to generate the notification (460) including information related to downloading the process data (410) in the notification (460).

5. The meter electronics (20) of claim 2, wherein: The processor (210) is further configured to provide the notification (460) via at least one of a port (26) and a user interface (30).

6. The meter electronics (20) of claim 1, wherein: The context data of the event-related process data includes at least one of pre-context data (410b) and post-context data (410c).

7. The meter electronics (20) of claim 1, wherein: The processor (210) is further configured to provide the allocated process data (450) via at least one of a port (26) and an external storage device (236).

8. The meter electronics (20) of claim 1, wherein: The processor (210) being configured to detect the one or more events (430) includes the processor (210) being configured to determine whether a process parameter (340) exceeds a threshold.

9. A meter (5) configured to notify events and distribute process data, the meter (5) comprising: Meter electronics (20) configured to continuously store the process data (410) for a duration (412), the meter electronics (20) configured to: detecting one or more events (430) in the process data (410); and assigning the process data (410) into assigned process data based on the detected one or more events (430); The allocated process data includes event-related process data and context data of the event-related process data.

10. The meter (5) according to claim 9, wherein The meter electronics (20) is also configured to generate a notification (460) based on the previous context length (444).

11. The meter (5) according to claim 10, wherein: The meter electronics (20) being configured to generate the notification (460) includes the meter electronics (20) being configured to include information related to the detected one or more events (430) in the notification (460).

12. The meter (5) according to claim 10 or 11, wherein: The meter electronics (20) being configured to generate the notification (460) includes the meter electronics (20) being configured to include information related to downloading the process data (410) in the notification (460).

13. The meter (5) according to claim 10, wherein: The meter electronics (20) is further configured to provide the notification (460) via at least one of the port (26) and the user interface (30).

14. The meter (5) according to claim 9, wherein The context data of the event-related process data includes at least one of pre-context data (410b) and post-context data (410c).

15. The meter (5) according to claim 9, wherein The meter electronics (20) is further configured to provide the allocated process data (450) via at least one of the port (26) and an external storage device (236).

16. The meter (5) according to claim 15, wherein The meter electronics (20) being configured to detect the one or more events (430) includes the meter electronics (20) being configured to determine whether a process parameter (340) exceeds a threshold value.

17. A method for notifying an event and distributing process data, the method comprising: Continuously store process data over a duration; detecting one or more events in the process data; as well as assigning the process data into assigned process data based on the detected one or more events; The allocated process data includes event-related process data and context data of the event-related process data.

18. The method according to claim 17, further comprising: Generate notifications based on the previous context length.

19. The method according to claim 18, wherein Generating the notification includes including information related to the detected one or more events in the notification.

20. The method according to one of claims 18 and 19, wherein Generating the notification includes including information related to downloading the process data in the notification.

21. The method of claim 19, further comprising: The notification is provided via at least one of a port and a user interface.

22. The method according to claim 17, wherein The context data includes at least one of pre-context data and post-context data.

23. The method of claim 17, further comprising: The allocated process data is provided via at least one of a port and an external storage device.

24. The method according to claim 23, further comprising: If the process parameter exceeds a threshold value, the one or more events are detected.

Images