Method and apparatus for detecting pressure relief valve proximity activation

Abstract

Systems, apparatuses, articles, and methods for detecting pressure relief valve near activation are disclosed. An example computing device includes interface circuitry, machine-readable instructions, and programmable circuitry to at least one of instantiate or execute the machine-readable instructions to perform operations to obtain pressure data from a pressure sensor, the pressure data associated with a differential pressure between a first region of a pressure relief valve and a second region of the pressure relief valve, the first region different from the second region; obtain setpoint data corresponding to a threshold pressure and an activation pressure of the pressure relief valve; determine whether the differential pressure is between the threshold pressure and the activation pressure based on the pressure data and the setpoint data; and generate an indication corresponding to the differential pressure being between the threshold pressure and the activation pressure.

Description

Technical Field

[0001] This disclosure relates generally to fluid valves, and more specifically to methods and apparatus for detecting proximity activation of pressure relief valves. Background Technology

[0002] Pressure relief valves are typically used in pressurized fluid systems to maintain a safe level of fluid pressure. When the pressure within the system exceeds a threshold level, the pressure relief valve opens to release fluid, thereby reducing the pressure within the system. Pilot-operated pressure relief valves feed system pressure back to the valve seat to increase the sealing force, thus reducing leakage at system pressures close to the threshold level. Adjustable pilot-operated pressure relief valves are configured to open gradually in proportion to the difference between the system pressure and the threshold pressure. In this way, adjusting the pilot-operated pressure relief valve reduces the total volume of fluid released in response to the system pressure exceeding the threshold pressure. Summary of the Invention

[0003] The exemplary methods and apparatus disclosed herein include a computing device comprising interface circuitry, machine-readable instructions, and programmable circuitry, the programmable circuitry being configured to instantiate or execute at least one of the machine-readable instructions to perform the following operations: obtaining pressure data from a pressure sensor associated with a differential pressure between a first region and a second region of a pressure relief valve, the first region being different from the second region; obtaining setpoint data corresponding to a threshold pressure and an activation pressure of the pressure relief valve; determining, based on the pressure data and the setpoint data, whether the differential pressure is between the threshold pressure and the activation pressure; and generating an indication corresponding to the differential pressure being between the threshold pressure and the activation pressure.

[0004] The exemplary methods and apparatus disclosed herein include a non-transitory machine-readable storage medium comprising instructions that cause programmable circuitry to perform at least the following operations: obtaining sensor identification data corresponding to a sensor operatively coupled to a pressure relief valve within a fluid system, the pressure relief valve being coupled to a pressure vessel; obtaining setpoint data corresponding to the activation differential pressure of the pressure relief valve; obtaining pressure data from the sensor corresponding to a differential pressure across a flow control element within the pressure relief valve, the flow control element selectively fluidly coupling and selectively isolating the inlet of the pressure relief valve from its outlet based on the differential pressure rising above or falling below the activation differential pressure of the pressure relief valve; and determining the state of the pressure relief valve based on the sensor identification data, the setpoint data, and the pressure data.

[0005] The exemplary methods and apparatus disclosed herein include a method for detecting the proximity activation of a pressure relief valve, the method comprising: receiving sensor data corresponding to the identifier of a pressure sensor within a fluid system, the pressure sensor being used to measure pressure within the pressure relief valve, the pressure relief valve including an inlet and a dome; receiving setpoint data corresponding to the activation pressure of the pressure relief valve; receiving pressure data from the pressure sensor; and determining whether the pressure relief valve is close to activation based on the sensor data, the pressure data, and the setpoint data. Attached Figure Description

[0006] Figure 1 This is a block diagram of an exemplary environment, in which an exemplary controller operates to determine the operating state of an exemplary pressure relief valve in an exemplary fluid system.

[0007] Figure 2 yes Figure 1 A block diagram illustrating an exemplary implementation of the controller.

[0008] Figures 3A-3C This is an illustration of an exemplary pressure relief valve in an exemplary closed state, an exemplary proportional release state, and an exemplary maximum release state.

[0009] Figures 4A-4B It can be used to determine Figure 1 An exemplary operation diagram showing the operating state of an exemplary pressure relief valve.

[0010] Figures 5-6 This indicates that it can be implemented, instantiated, and / or run by an exemplary programmable circuit. Figure 2 A flowchart of exemplary machine-readable instructions and / or exemplary operations of the controller.

[0011] Figure 7 This is a block diagram of an exemplary processing platform including programmable circuitry configured to execute, instantiate, and / or run exemplary machine-readable instructions and / or perform... Figure 5 and / or Figure 6 Exemplary operations to achieve Figure 2 The controller.

[0012] Figure 8 yes Figure 7 A block diagram illustrating an exemplary implementation of a programmable circuit.

[0013] Figure 9 yes Figure 7 A block diagram of another exemplary implementation of a programmable circuit.

[0014] Typically, the same reference numerals will be used throughout the accompanying drawings and written description to refer to the same or similar parts. The drawings are not necessarily drawn to scale. Instead, the thickness of layers or areas may be enlarged in the drawings. Detailed Implementation

[0015] Complex fluid systems, such as industrial systems, often include pressure vessels that are monitored remotely. Control systems collect data from sensors within the fluid system to monitor and control the associated processes and pressure vessels. Pressure relief valves are typically monitored to determine whether they activate in response to pressure exceeding a threshold pressure within the pressure vessel.

[0016] In some applications, it is advantageous to detect when a pressure relief valve is about to activate and / or when the pressure in the fluid container approaches the valve's activation pressure. Known control systems do not provide notification that a pressure relief valve is about to activate. Monitoring a pressure relief valve approaching activation is challenging in large fluid systems with many pressure relief valves having different activation pressures.

[0017] The methods and apparatus disclosed herein monitor differential pressure measurements across valve components in a pressure relief valve to determine whether the pressure relief valve is approaching an activated state. In this way, the control system can notify the user or otherwise adjust the operation of the fluid system to anticipate activation of the pressure relief valve.

[0018] Figure 1 This is a block diagram of an exemplary environment 100, in which an exemplary controller 102 operates to determine the operational state of exemplary pressure relief valves (PRVs) 104, 106 in an exemplary fluid system 108. The exemplary fluid system 108 includes exemplary pressure vessels (e.g., fluid containers, fluid reservoirs, etc.) 110a, 110b. PRVs 104, 106 are fluidly coupled to pressure vessels 110a, 110b via exemplary inlets 112a, 112b. When the fluid pressure reaches a threshold, PRVs 104, 106 release fluid from pressure vessels 110a, 110b through exemplary outlets 114a, 114b, as referenced below. Figures 3A-3C A more detailed explanation.

[0019] PRV 104 includes an exemplary differential pressure sensor 116a for measuring the pressure difference (e.g., differential pressure) within PRV 104. PRV 106 includes an exemplary differential pressure sensor 116b for measuring the pressure difference within PRV 106 and an exemplary pressure sensor 118 for measuring the pressure (e.g., gauge pressure) within inlet 112b. Differential pressure sensors 116a, 116b, and 118 transmit pressure data to controller 102 via an exemplary network 120. In some examples, PRV 104 and PRV 106 include data transmitters for wireless communication with network 120. In some examples, differential pressure sensor 116b measures the pressure difference in PRV 106 and the pressure in inlet 112b without the need for pressure sensor 118. In other examples, PRV 106 includes two pressure sensors 118 for reading the pressure in the inlet and within PRV 106 (e.g., fluid pressure in the dome, fluid pressure relative to the main relief valve, etc.) to determine differential pressure and inlet pressure.

[0020] Figure 1 An exemplary fluid system 108 is shown having two containers 110, PRV 104, and PRV 106. Controller 102 receives pressure data from differential pressure sensor 116a of PRV 104, differential pressure sensor 116b of PRV 106, and pressure sensor 118 of PRV 106. In other examples, fluid system 108 may include any number of containers 110, each container 110 including either PRV 104 or PRV 106 that transmits pressure data to controller 102.

[0021] Figure 2 It is used to determine whether PRV is close to activation. Figure 1 A block diagram of an exemplary implementation of controller 102. Figure 2 The controller 102 can be instantiated by executing first instructions from programmable circuitry (such as a central processing unit (CPU)). (e.g., creating an instance of it, making it last for any duration, materializing, implementing, etc.) Additionally or alternatively, Figure 2 The controller 102 can be instantiated (e.g., instantiated, made to last for any length of time, materialized, implemented, etc.) by (i) an application-specific integrated circuit (ASIC) and / or (ii) a field-programmable gate array (FPGA), which is constructed and / or configured to perform an operation corresponding to the first instruction in response to the execution of the second instruction. It should be understood that Figure 2 Some or all of the circuits can therefore be instantiated at the same or different times. Figure 2Some or all of the circuitry can be instantiated, for example, in one or more threads that execute concurrently on hardware and / or serially on hardware. Furthermore, in some examples, Figure 2 Some or all of the circuitry can be implemented by microprocessor circuitry that executes instructions and / or FPGA circuitry that executes operations to implement one or more virtual machines and / or containers.

[0022] Figure 2 The exemplary controller 102 communicates with the exemplary control system 200 and the network 120. The network 120 receives data from one or more PRVs 106 and / or PRVs 104. In some examples, the PRVs 106 and / or PRVs 104 communicate directly with the controller 102 without using the network 120. PRV 106 includes a differential pressure sensor 116 and a pressure sensor 118. PRV 104 includes a differential pressure sensor 116. The controller 102 includes an exemplary sensor identification circuit 202, an exemplary setpoint determination circuit 204, an exemplary pressure data receiving circuit 206, an exemplary valve status determination circuit 208, and an exemplary indication generation circuit 210.

[0023] Sensor identification circuit 202 associates data received from pressure sensors (e.g., differential pressure sensor 116, pressure sensor 118, etc.) with specific pressure relief valves (e.g., PRV 106, PRV 104, etc.) within a fluid system (e.g., fluid system 108). In this way, valve states generated by valve state determination circuit 208 can be associated with corresponding pressure relief valves within the fluid system for presentation to the user and / or control system 200. In some examples, sensor identification circuit 202 generates sensor identification data corresponding to pressure sensors within the fluid system. In some examples, sensor identification circuit 202 is instantiated by programmable circuitry that executes sensor identification instructions and / or configured to perform actions such as those generated by… Figure 5 and Figure 6 The flowchart represents the operations performed.

[0024] In some examples, the controller includes a unit for identifying the sensor. For example, the identification unit may be implemented by a sensor identification circuit 202. In some examples, the sensor identification circuit 202 may be implemented by a programmable circuit (such as...) Figure 7 The exemplary programmable circuit 712 is instantiated. For example, the sensor identification circuit 202 can be instantiated via... Figure 8 An exemplary microprocessor 800 executes machine-executable instructions (such as those given by...). Figure 5 and Figure 6 The sensor identification circuit 202 can be instantiated by at least those instructions implemented in blocks 502 and 602. In some examples, the sensor identification circuit 202 can be instantiated by hardware logic circuitry, which can be instantiated by... Figure 9 The sensor identification circuit 202 is implemented by an ASIC, XPU, or FPGA circuit 900, which is configured and / or constructed to perform operations corresponding to machine-readable instructions. Additionally or alternatively, the sensor identification circuit 202 may be instantiated by any other combination of hardware, software, and / or firmware. For example, the sensor identification circuit 202 may be implemented by at least one or more hardware circuits (e.g., processor circuitry, discrete and / or integrated analog and / or digital circuitry, FPGA, ASIC, XPU, comparator, operational amplifier, logic circuitry, etc.) configured and / or constructed to execute some or all of the machine-readable instructions and / or perform some or all of the operations corresponding to the machine-readable instructions without executing software or firmware; however, other configurations are equally suitable.

[0025] Setpoint determination circuit 204 receives and / or determines the functional setpoint of the pressure relief valve associated with the pressure sensor. The pressure relief valve has an activation setpoint (e.g., threshold pressure value, set pressure, activation differential pressure, activation gauge pressure, etc.) that activates the pressure relief valve or otherwise allows fluid to flow from the inlet to the outlet. In other words, the activation setpoint is the maximum permissible pressure in the pressure vessel.

[0026] In some examples, the pressure relief valve includes additional functional setpoints describing other behaviors of the pressure relief valve, such as operating states. For example, setpoint data received by setpoint determination circuit 204 may include a lower threshold pressure (e.g., minimum threshold pressure, lower threshold differential pressure, etc.) corresponding to a pressure relief valve approaching an activation setpoint. In this way, the lower threshold pressure acts as an early indicator that the pressure relief valve will soon be activated. In some examples, the setpoint data received by setpoint determination circuit 204 includes an upper threshold pressure (e.g., maximum threshold pressure, upper threshold differential pressure) corresponding to the maximum opening of the pressure relief valve. See below for reference. Figures 3A-3C As described in further detail, some example pressure relief valves open proportionally to the pressure within the pressure relief valve. In this way, the activation setpoint and upper threshold pressure define the range of proportional fluid release from the pressure relief valve. In some examples, the setpoint data received by the setpoint determination circuit 204 includes differential pressure associated with the function of the pressure relief valve. In other examples, the setpoint data received by the setpoint determination circuit 204 includes gauge pressure activating the setpoint and the ratio (e.g., percentage of gauge pressure activating the setpoint) used by the setpoint determination circuit 204 to determine (e.g., calculate) other operating setpoints, as described below. Figure 4A and Figure 4BFurther details are provided. In some examples, the setpoint determination circuit 204 is instantiated by a programmable circuit that executes setpoint determination instructions and / or configured to perform actions such as those described by... Figure 5 and Figure 6 The flowchart represents the operations performed.

[0027] In some examples, the controller includes a unit for determining the setpoint of the pressure relief valve. For example, the unit for determination may be implemented by a setpoint determination circuit 204. In some examples, the setpoint determination circuit 204 may be implemented by a programmable circuit (such as...) Figure 7 The exemplary programmable circuit 712) is instantiated. For example, the setpoint determination circuit 204 can be instantiated via... Figure 8 An exemplary microprocessor 800 executes machine-executable instructions (such as those given by...). Figure 5 and Figure 6 The setpoint determination circuit 204 can be instantiated by at least those instructions implemented in blocks 504, 508, 604, 608, 612, and 620. In some examples, the setpoint determination circuit 204 can be instantiated by hardware logic circuitry, which can be instantiated by... Figure 9 The setpoint determination circuit 204 is implemented by an ASIC, XPU, or FPGA circuit 900 configured and / or constructed to perform operations corresponding to machine-readable instructions. Additionally or alternatively, the setpoint determination circuit 204 may be instantiated by any other combination of hardware, software, and / or firmware. For example, the setpoint determination circuit 204 may be implemented by at least one or more hardware circuits (e.g., processor circuitry, discrete and / or integrated analog and / or digital circuitry, FPGA, ASIC, XPU, comparator, operational amplifier, logic circuitry, etc.) configured and / or constructed to execute some or all of the machine-readable instructions and / or perform some or all of the operations corresponding to the machine-readable instructions without executing software or firmware; however, other configurations are equally suitable.

[0028] Pressure data receiving circuit 206 receives pressure data from pressure sensors in the system (e.g., differential pressure sensor 116, pressure sensor 118, etc.) for later use by valve state determination circuit 208. In some examples, pressure data receiving circuit 206 receives data from pressure sensors substantially in real time. In some examples, pressure data receiving circuit 206 receives raw signal data (e.g., voltage, current, etc.) from pressure sensors and converts the raw signal data into usable pressure measurements. In some examples, pressure data receiving circuit 206 determines whether the pressure data is a differential pressure measurement or a gauge pressure measurement. In some examples, pressure data receiving circuit 206 is instantiated by programmable circuitry that executes pressure data receiving instructions and / or configured to perform actions such as those by... Figure 5The flowchart represents the operations performed.

[0029] In some examples, the controller includes a unit for receiving pressure data. For example, the unit for receiving data can be implemented by a pressure data receiving circuit 206. In some examples, the pressure data receiving circuit 206 can be implemented by a programmable circuit (such as...) Figure 7 The exemplary programmable circuit 712) is instantiated. For example, the pressure data receiving circuit 206 can be instantiated via... Figure 8 An exemplary microprocessor 800 executes machine-executable instructions (such as those from at least...). Figure 5 The instruction implemented in block 506 is used to instantiate it. In some examples, the pressure data receiving circuit 206 can be instantiated by hardware logic circuitry, which can be instantiated by... Figure 9 The pressure data receiving circuit 206 is implemented by an ASIC, XPU, or FPGA circuit 900, which is configured and / or constructed to perform operations corresponding to machine-readable instructions. Additionally or alternatively, the pressure data receiving circuit 206 may be instantiated by any other combination of hardware, software, and / or firmware. For example, the pressure data receiving circuit 206 may be implemented by at least one or more hardware circuits (e.g., processor circuitry, discrete and / or integrated analog and / or digital circuitry, FPGA, ASIC, XPU, comparator, operational amplifier, logic circuitry, etc.) configured and / or constructed to execute some or all of the machine-readable instructions and / or perform some or all of the operations corresponding to the machine-readable instructions without executing software or firmware; however, other configurations are equally suitable.

[0030] Valve state determination circuit 208 compares pressure data received from pressure data receiving circuit 206 with setpoint data received from setpoint determination circuit 204 to determine the state of the pressure relief valve. For example, if valve state determination circuit 208 determines that the pressure measurement value from the pressure relief valve is less than a lower threshold, then valve state determination circuit 208 assigns a normal operating state to the pressure relief valve. The following is about... Figure 4A , Figure 4B and Figure 6 The following describes in detail other valve states (e.g., operating states) and their determination methods. In some examples, the valve state determination circuit 208 is instantiated by a programmable circuit that executes valve state determination instructions and / or configured to perform actions such as those by... Figure 5 and Figure 6 The flowchart represents the operations performed.

[0031] In some examples, the controller includes a unit for determining the state of the pressure relief valve. For example, the unit for determination may be implemented by valve state determination circuit 208. In some examples, valve state determination circuit 208 may be implemented by programmable circuitry (such as...) Figure 7 Example programmable circuit 712) instantiated. For example, valve state determination circuit 208 can be instantiated via... Figure 8 An exemplary microprocessor 800 executes machine-executable instructions (such as those given by...). Figure 5 and Figure 6 The valve state determination circuit 208 can be instantiated by at least those instructions implemented in blocks 508, 602, 604, 606, 608, 610, 612, 614, 616, 618, 620, 622, and 624. In some examples, the valve state determination circuit 208 can be instantiated by hardware logic circuitry, which can be instantiated by... Figure 9 The valve state determination circuit 208 is implemented by an ASIC, XPU, or FPGA circuit 900, which is configured and / or constructed to perform operations corresponding to machine-readable instructions. Additionally or alternatively, the valve state determination circuit 208 can be instantiated by any other combination of hardware, software, and / or firmware. For example, the valve state determination circuit 208 can be implemented by at least one or more hardware circuits (e.g., processor circuitry, discrete and / or integrated analog and / or digital circuitry, FPGA, ASIC, XPU, comparator, operational amplifier, logic circuitry, etc.) configured and / or constructed to execute some or all of the machine-readable instructions and / or perform some or all of the operations corresponding to the machine-readable instructions without executing software or firmware, but other configurations are equally suitable.

[0032] The report generation circuit 210 compiles sensor identification data received from sensor identification circuit 202 and valve status data received from valve status determination circuit 208 into indication data to be sent to control system 200. The indication data includes data about each pressure relief valve within the monitored fluid system, which includes a pressure sensor that sends data to controller 102. The indication data allows the user of the control system to determine the status of the pressure relief valve. In some examples, the indication data includes pressure data received from pressure data receiving circuit 206. In some examples, the report generation circuit 210 is instantiated by programmable circuitry that executes report instructions and / or configured to perform actions such as those by… Figure 5 The flowchart represents the operations performed.

[0033] In some examples, the controller includes a unit for generating reports. For example, the unit for generation can be implemented by report generation circuitry 210. In some examples, report generation circuitry 210 can be implemented by programmable circuitry (such as...) Figure 7The exemplary programmable circuit 712) is instantiated. For example, the report generation circuit 210 can be instantiated via... Figure 8 An exemplary microprocessor 800 executes machine-executable instructions (such as those from at least...). Figure 5 The instruction implemented in box 510 is used to instantiate it. In some examples, the report generation circuit 210 can be instantiated by hardware logic circuitry, which can be instantiated by... Figure 9 The report generation circuit 210 is implemented by an ASIC, XPU, or FPGA circuit 900, which is configured and / or constructed to perform operations corresponding to machine-readable instructions. Additionally or alternatively, the report generation circuit 210 may be instantiated by any other combination of hardware, software, and / or firmware. For example, the report generation circuit 210 may be implemented by at least one or more hardware circuits (e.g., processor circuitry, discrete and / or integrated analog and / or digital circuitry, FPGA, ASIC, XPU, comparator, operational amplifier, logic circuitry, etc.) configured and / or constructed to execute some or all of the machine-readable instructions and / or perform some or all of the operations corresponding to the machine-readable instructions without executing software or firmware, but other configurations are equally suitable.

[0034] Although Figure 2 The implementation is shown in the figure. Figure 1 The controller 102 is an example of such a method, but Figure 2 One or more of the components, processes, and / or devices shown may be combined, divided, rearranged, omitted, eliminated, and / or implemented in any other way. Furthermore, exemplary sensor identification circuit 202, exemplary setpoint determination circuit 204, exemplary pressure data receiving circuit 206, exemplary valve status determination circuit 208, exemplary indication generation circuit 210, and / or more generally... Figure 2 The exemplary controller 102 can be implemented solely by hardware or by hardware in combination with software and / or firmware. Therefore, for example, any of the exemplary sensor identification circuit 202, exemplary setpoint determination circuit 204, exemplary pressure data receiving circuit 206, exemplary valve state determination circuit 208, exemplary indication generation circuit 210, and / or more generally, the exemplary controller 102, can be implemented by programmable circuitry combined with machine-readable instructions (e.g., firmware or software), processor circuitry, analog circuitry, digital circuitry, logic circuitry, programmable processors, programmable microcontrollers, graphics processing units (GPUs), digital signal processors (DSPs), ASICs, programmable logic devices (PLDs), and / or field-programmable logic devices (FPLDs) (such as FPGAs). Furthermore, Figure 2 The exemplary controller 102 may include, in addition to Figure 2 Those other than or in place of those shown Figure 2 One or more of the elements, processes and / or devices shown, and / or may include more than one of any or all of the elements, processes and devices shown.

[0035] exist Figure 5 and / or Figure 6 The diagram illustrates how this can be implemented and / or instantiated by programmable circuitry. Figure 2 The exemplary machine-readable instructions and / or representations of the controller 102 can be executed by programmable circuitry to implement and / or instantiate it. Figure 2 A flowchart illustrating exemplary operation of controller 102. Machine-readable instructions may be used by programmable circuitry (such as those described below). Figure 7 The programmable circuit 712 shown in the exemplary processor platform 700 discussed herein executes one or more executable programs or one or more portions of one or more executable programs, and / or may be to be combined with the following Figure 8 and / or Figure 9 The exemplary programmable circuits discussed (e.g., FPGAs) perform one or more functions or portions of functions. In some examples, machine-readable instructions cause operations, tasks, etc., to be performed and / or carried out automatically in the real world. As used herein, “automation” means without human intervention.

[0036] The program may be embodied in instructions (e.g., software and / or firmware) stored on one or more non-transitory computer-readable and / or machine-readable storage media, such as cache memory, magnetic storage devices or disks (e.g., floppy disks, hard disk drives (HDDs), etc.), optical storage devices or disks (e.g., Blu-ray discs, optical discs (CDs), digital versatile discs (DVDs), etc.), redundant arrays of independent disks (RAID), registers, ROM, solid-state drives (SSDs), SSD memory, non-volatile memory (e.g., electrically erasable programmable read-only memory (EEPROM), flash memory, etc.), volatile memory (e.g., random access memory (RAM) of any type), and / or any other storage device or disk. The instructions on the non-transitory computer-readable and / or machine-readable media may be programmed and / or executed by programmable circuitry located in one or more hardware devices, but the entire program and / or portions thereof may alternatively be executed and / or instantiated and / or embodied in dedicated hardware by one or more hardware devices other than programmable circuitry. Machine-readable instructions can be distributed across multiple hardware devices and / or executed by two or more hardware devices (e.g., server and client hardware devices). For example, client hardware devices can be implemented by endpoint client hardware devices (e.g., hardware devices associated with human and / or machine users) or by intermediate client hardware device gateways (e.g., radio access networks (RANs)) that facilitate communication between the server and endpoint client hardware devices. Similarly, non-transitory computer-readable storage media can include one or more media. Furthermore, although references... Figure 5 and / or Figure 6 The flowchart shown describes an exemplary program, but many other methods for implementing the exemplary controller can be used alternatively. For example, the execution order of the flowchart's boxes can be changed, and / or some of the described boxes can be modified, eliminated, or combined. Additionally or alternatively, any or all of the flowchart's boxes can be implemented by one or more hardware circuits (e.g., processor circuitry, discrete and / or integrated analog and / or digital circuitry, FPGAs, ASICs, comparators, operational amplifiers (op-amps), logic circuitry, etc.) configured to perform the corresponding operations without executing software or firmware. Programmable circuitry can be distributed across different network locations and / or local to one or more hardware devices (e.g., a single-core processor (e.g., a single-core CPU), a multi-core processor (e.g., a multi-core CPU, XPU, etc.)). For example, programmable circuitry can be a CPU and / or FPGA located in the same package (e.g., the same integrated circuit (IC) package or two or more separate housings), one or more processors in a single machine, multiple processors distributed across multiple servers in a server rack, multiple processors distributed across one or more server racks, etc., and / or any combination thereof.

[0037] The machine-readable instructions described herein can be stored in one or more of the following formats: compressed format, encrypted format, segmented format, compiled format, executable format, packaged format, etc. As described herein, machine-readable instructions can be stored as data (e.g., computer-readable data, machine-readable data, one or more bits (e.g., one or more computer-readable bits, one or more machine-readable bits, etc.), bit streams (e.g., computer-readable bit streams, machine-readable bit streams, etc.)) or data structures (e.g., as part of instructions, code, code representations, etc.). For example, machine-readable instructions can be segmented and stored on one or more storage devices, disks, and / or computing devices (e.g., servers) located in the same or different locations (e.g., in the cloud, on edge devices, etc.) within a network or network set. Machine-readable instructions may require installation, modification, adaptation, updating, combination, supplementation, configuration, decryption, decompression, unpacking, distribution, redistribution, compilation, etc., to make them directly readable, interpretable, and / or executable by computing devices and / or other machines. For example, machine-readable instructions may be stored in multiple parts that are individually compressed, encrypted, and / or stored on separate computing devices, wherein these parts, when decrypted, decompressed, and / or combined, form a set of computer-executable and / or machine-executable instructions that, when implemented together, can form one or more functions and / or operations of a program such as those described herein.

[0038] In another example, machine-readable instructions may be stored in a state where they can be read by programmable circuitry, but libraries (e.g., dynamic link libraries (DLLs)), software development kits (SDKs), application programming interfaces (APIs), etc., need to be added to enable execution of the machine-readable instructions on a specific computing device or other device. In yet another example, the machine-readable instructions may need to be configured (e.g., stored settings, data input, recorded network addresses, etc.) before they can be fully or partially executed. Therefore, machine-readable, computer-readable, and / or machine-readable media as used herein can include instructions and / or programs, regardless of their specific format or state.

[0039] The machine-readable instructions described in this article can be represented by any past, present, or future instruction language, scripting language, programming language, etc. For example, machine-readable instructions can be represented using any of the following languages: C, C++, Java, C#, Perl, Python, JavaScript, Hypertext Markup Language (HTML), Structured Query Language (SQL), Swift, etc.

[0040] As mentioned above, Figure 5 and / or Figure 6 The exemplary operation can be implemented using executable instructions (e.g., computer-readable and / or machine-readable instructions) stored on one or more non-transitory computer-readable and / or machine-readable media. As used herein, the terms non-transitory computer-readable medium, non-transitory computer-readable storage medium, non-transitory machine-readable medium, and / or non-transitory machine-readable storage medium are explicitly defined to include any type of computer-readable storage device and / or storage disk, excluding propagation signals and transmission media. Examples of such non-transitory computer-readable medium, non-transitory computer-readable storage medium, non-transitory machine-readable medium, and / or non-transitory machine-readable storage medium include optical storage devices, magnetic storage devices, HDDs, flash memory, read-only memory (ROM), CDs, DVDs, caches, any type of RAM, registers, and / or any other storage device or storage disk in which information is stored for any duration (e.g., extended time period, permanent, transient, for temporary buffering, and / or for caching information). As used herein, the terms "non-transitory computer-readable storage device" and "non-transitory machine-readable storage device" are defined as including any physical (mechanical, magnetic, and / or electrical) hardware designed to retain information for a period of time, excluding the propagation of signals and the transmission medium. Examples of non-transitory computer-readable storage devices and / or non-transitory machine-readable storage devices include any type of random access memory, any type of read-only memory, solid-state memory, flash memory, optical disc, hard disk, disk drive, and / or redundant array of independent disks (RAID) system. As used herein, the term "device" refers to a physical structure, such as mechanical and / or electrical equipment, hardware, and / or circuitry, which may or may not be configured by computer-readable instructions, machine-readable instructions, etc., and / or manufactured to execute computer-readable instructions, machine-readable instructions, etc.

[0041] Figures 3A-3C yes Figure 1 The illustration shows an example pressure relief valve (PRV) 106 in an exemplary closed state 300, an exemplary proportional release state 302, and an exemplary maximum release state 304. The PRV 106 includes an example pilot device 306 that allows exemplary fluid 307 to flow from inlet 112 to an exemplary dome 308. The dome 308 is the region opposite inlet 112 to an exemplary piston 310 (e.g., a valve, flow control member, cylinder, etc.). By allowing fluid 307 to flow from inlet 112 to dome 308, the pilot device 306 allows piston 310 to remain sealed as the pressure of fluid 307 increases.

[0042] Pilot device 306 is configured to selectively fluidly isolate inlet 112 from dome 308 once the pressure of fluid 307 rises to a set point of PRV 106. Once dome 308 is fluidly isolated from inlet 112, the pressure of fluid 307 in inlet 112 causes pilot device 306 to release fluid from dome 308. The reduction of fluid 307 in dome 308 causes piston 310 to move away from inlet 112 to fluidly couple inlet 112 to outlet 114. In other words, when the pressure of fluid 307 rises to the set pressure of PRV 106, PRV 106 selectively fluidly couples inlet 112 to outlet 114. Conversely, when the pressure of fluid 307 in inlet 112 drops below the set pressure of PRV 106, pilot device 306 selectively fluidly couples inlet 112 to dome 308. Once the dome 308 and inlet 112 are fluidly coupled, fluid 307 returns to the dome 308 and pushes the piston 310 toward the inlet 112 to fluidly isolate the inlet 112 from the outlet 114.

[0043] Figure 3A A dome 308 is shown, fluidly coupled to a PRV 106 via a pilot device 306 at inlet 112. A differential pressure sensor 116 measures the pressure difference between inlet 112 and dome 308. Figure 3A In the example, differential pressure sensor 116 generates pressure data corresponding to a differential pressure of zero or near zero. In other words, Figure 3A The dome 308 and inlet 112 are fluidly coupled and experience the same pressure from fluid 307. Pressure sensor 118 measures the gauge pressure at inlet 112. Figure 3A In the example, pressure sensor 118 generates pressure data corresponding to a fluid pressure less than a set pressure of PRV 106.

[0044] Figure 3B A dome 308 of the PRV 106 is shown, fluidly isolated from inlet 112 via pilot device 306. Additionally, exemplary fluid 312 within the dome 308 is released by pilot device 306 to reduce the pressure of the fluid 312 within the dome. Figure 3B In the example, differential pressure sensor 116 generates pressure data corresponding to a positive differential pressure. In other words, Figure 3B The dome 308 and inlet 112 are fluidly isolated, and the pressure from fluid 307 is higher than the pressure from fluid 312. Figure 3B In the example, pressure sensor 118 generates pressure data corresponding to a set pressure of approximately equal to PRV 106 for the fluid pressure. Figure 3B PRV 106 shows that fluid 307 is released proportionally to the differential pressure between piston 310 and dome 308 and inlet 112. Figure 3BIn the middle, piston 310 has begun to move, and fluid 307 flows from inlet 112 to outlet 114 at a relatively low rate.

[0045] Figure 3C The dome 308 of the PRV 106 is shown, fluidly isolated from the inlet 112 via a pilot device 306. Additionally, most of the fluid 312 has been released by the pilot device 306. In this example, the differential pressure sensor 116 generates pressure data corresponding to a differential pressure close to a set pressure (e.g., the activation pressure of the PRV 106). In other words, Figure 3C The dome 308 and inlet 112 are fluidly isolated, and the gauge pressure in the dome 308 is close to zero (e.g., close to atmospheric pressure). Figure 3C In the example, pressure sensor 118 generates pressure data corresponding to a set pressure approximately equal to PRV 106. For example... Figure 3C As shown, piston 310 has moved away from inlet 112 and stopped (e.g., reached the maximum lift position, reached the maximum distance from inlet 112, etc.). In this way, PRV 106 is fully open and releases fluid 307 to outlet 114.

[0046] Figures 4A-4B It can be used to determine Figure 1 Exemplary operation diagrams 400 and 402 illustrate the operating states of exemplary pressure relief valves (PRVs) 104 and 106. Figure 4A An operation chart 400 corresponding to a PRV is shown, which includes a single differential pressure sensor to measure the differential pressure across the inlet and dome of the PRV (e.g., PRV 104). Operation chart 400 illustrates an exemplary operating threshold 404 for the differential pressure and an exemplary resulting valve state 406. The operating threshold 404 is described as a percentage of the set pressure (e.g., activation pressure, activation setpoint, etc.) of the described PRV.

[0047] Line 408 of Operation Chart 400 shows that if the differential pressure between the inlet and the dome is 5% or less of the set pressure, the PRV has a valve state corresponding to normal operation, where the valve is in the closed position. Line 410 of Operation Chart 400 shows that if the differential pressure between the inlet and the dome is greater than 5% but less than 30% of the set pressure, the PRV has a valve state corresponding to near the set pressure, where the valve is in the closed position. In some examples, the 5% threshold (e.g., a lower limit threshold) between the normal operating state and the near-setpoint pressure state can be changed by the user to different values ​​(e.g., between 0% and 30% of the set pressure) to accommodate different system characteristics, such as pulse pressure variations.

[0048] Line 412 of the operation diagram 400 shows that if the differential pressure between the inlet and the dome is 30% or greater than the set pressure, but 65% or less than the set pressure, the PRV has a valve state corresponding to the release, where the valve releases proportionally to the differential pressure (e.g., in the open position). In other words, when the differential pressure is 30% of the set pressure, the PRV begins to release and increases the release proportionally (e.g., Figure 3 A-). Figure 3C The distance between the inlet 112 and the piston 310), until the differential pressure reaches 65% of the set pressure. In some examples, the PRV 106 has different characteristics (e.g., different ratios of cylinder diameter to seat diameter), which makes the 30% threshold for PRV activation different (e.g., 25%, 35%, etc.).

[0049] Line 414 of the operation diagram 400 shows that if the differential pressure between the inlet and the dome is greater than 65% of the setpoint pressure, the PRV has a valve state corresponding to release, where the valve releases under maximum lift conditions (e.g., fully open conditions, etc.). In some examples, the PRV has different operating characteristics, and the 65% threshold (e.g., upper limit threshold) between a valve that releases proportionally to the differential pressure and a valve that releases at maximum lift can be a different value (e.g., 55% of the differential pressure) to reflect the different operating characteristics of the PRV.

[0050] Figure 4B Operation chart 402 includes the differential pressure operation threshold 404 and the resulting valve state 406 shown in operation chart 400. Operation chart 402 also includes an exemplary gauge pressure threshold 416. Gauge pressure threshold 416 serves as a reference pressure for valve state 406 and as an indicator of a malfunction in the PRV. Row 418 of operation chart 402 includes the values ​​in row 408 and gauge pressure measurements of 95% or less of the set pressure, which are associated with a normal operating valve state in which the PRV has the valve in the closed position. Row 420 of operation chart 402 includes the values ​​in row 410 and gauge pressure measurements greater than 95% and up to 100% of the set pressure, which are associated with a valve state in which the PRV has the valve in the closed position and close to the set pressure. Row 422 of operation chart 402 includes the values ​​in row 412 and gauge pressure measurements greater than 100% of the set pressure, which are associated with a valve release state in which the PRV releases proportionally to the differential pressure. Row 424 of the operation chart 402 includes the value in row 414 and the gauge pressure measurement value that is greater than 100% of the set pressure, which is related to the PRV having the valve released and the valve being in the maximum release position.

[0051] Line 426 of Operation Chart 402 shows that if the gauge pressure is greater than 103% of the set pressure and the differential pressure is less than 30% of the set pressure, the PRV has an malfunctioning state (e.g., an operational error state), where the system pressure is higher than the maximum permissible operating pressure without any indication of PRV release. Line 428 of Operation Chart 402 shows that if the gauge pressure is less than 97% of the set pressure and the differential pressure is at least 30% of the set pressure, the PRV has an operational error valve state, where the PRV releases below the set pressure. In this way, lines 426 and 428 show that the gauge pressure reading added at the PRV inlet allows for the detection of operational errors or other changes.

[0052] Operating diagrams 400 and 402 illustrate examples of how measured pressure can be correlated with valve status. In other examples, such as PRV valves designed to operate under vacuum, the differential pressure and / or gauge pressure setpoints can differ to suit the specific activation method of the PRV.

[0053] Figure 5 This is a flowchart illustrating exemplary machine-readable instructions and / or exemplary operations 500, which can be executed, instantiated, and / or run by programmable circuitry to determine the operating state of a pressure relief valve. Figure 5 The exemplary machine-readable instructions and / or example operations 500 begin at block 502, where sensor identification circuitry 202 receives (e.g., acquires) sensor data from a pressure sensor (e.g., differential pressure sensor 116, pressure sensor 118, etc.) that measures pressure within a pressure vessel (e.g., PRV 104, PRV 106) within a fluid system (e.g., fluid system 108). The sensor data includes identification data corresponding to the pressure sensor and the PRV. In some examples, sensor identification circuitry 202 receives the sensor data and generates identification data based on the sensor data.

[0054] Figure 5Operation 500 continues to block 504, where setpoint determination circuit 204 receives (e.g., acquires) setpoint data corresponding to the PRV. The setpoint data includes data corresponding to the set pressure (e.g., activation pressure) of the PRV within the fluid system. The setpoint data includes example thresholds describing the operating characteristics of the PRV within the fluid system (e.g., states near the set pressure, states of release proportional to differential pressure, states of release at maximum lift, states of malfunction, etc.). In this way, each PRV in the fluid system is identified by sensor identification circuit 202 and defined by the setpoint received by setpoint determination circuit 204. In some examples, the setpoint data includes gauge pressure measurements and / or differential pressure measurements corresponding to the set pressure and threshold. In other examples, the setpoint data includes a multiplier (e.g., ratio, percentage, etc.) of the set pressure corresponding to the threshold. For example, setpoint data may include a set pressure of 100 pounds per square inch and a threshold of 65% of the set pressure, which will be interpreted by setpoint determination circuit 204 and / or valve state determination circuit 208 as a threshold pressure of 65 pounds per square inch.

[0055] Figure 5 Operation 500 continues to block 506, where pressure data receiving circuit 206 receives (e.g., acquires) pressure data from sensors within the fluid system. In some examples, the pressure data includes differential pressure and / or gauge pressure from each PRV. In some examples, the pressure data includes signal data (e.g., voltage signal, current signal, etc.) from pressure sensors, which is converted into pressure data by pressure data receiving circuit 206.

[0056] Figure 5 Operation 500 continues to box 508, where the valve state determination circuit determines the valve state. The following is about... Figure 6 In further detail, the valve status determination circuit compares sensor identification data, setpoint data, and pressure data to determine the valve status within the PRV. Operation 500 continues to block 510, where report generation circuit 210 sends the pressure data and valve status data to the control system (e.g., control system 200). In this way, the valve status corresponding to the PRV in the fluid system is reported to the control system and the user of the control system. Operation 500 continues to block 512, where controller 102 determines whether monitoring of the PRV should continue. In some examples, controller 102 will continue monitoring until it receives user input to stop. If controller 102 continues monitoring, operation 500 moves to block 506, where pressure data is received. If the controller does not continue monitoring, operation 500 ends.

[0057] Figure 6This is a flowchart representing exemplary machine-readable instructions and / or exemplary operations 508 that can be executed, instantiated, and / or run by programmable circuitry to determine valve status. Figure 6 The exemplary machine-readable instructions and / or exemplary operation 508 begin at block 602, where valve state determination circuit 208 identifies the sensor to be analyzed. In some examples, valve state determination circuit 208 selects a sensor from sensor identification data generated by sensor identification circuit 202. Operation 508 continues to block 604, where valve state determination circuit 208 determines whether the differential pressure reading corresponding to the identified sensor is greater than 5% of the set pressure of the corresponding PRV. In other words, valve state determination circuit 208 compares pressure data from pressure data receiving circuit 206 with setpoint data received from setpoint determination circuit 204 to determine whether the pressure data is greater than a lower threshold pressure. If the differential pressure is not greater than 5% of the set pressure, operation continues to block 606, where valve state determination circuit 208 assigns a valve state of valve closure and normal operation. Operation 508 moves to block 624, where valve state determination circuit 208 determines whether all PRVs have been analyzed. If all PRVs have been analyzed, operation 508 returns to... Figure 5 Operation 500. If not all PRVs have been analyzed, operation 508 returns to box 602, where the valve status determination circuit 208 identifies the new pressure sensor to be analyzed.

[0058] Returning to box 604, if the differential pressure is greater than 5% of the set pressure, operation 508 moves to box 608, where valve state determination circuit 208 determines whether the differential pressure is less than 30% of the set pressure. In this example, 30% of the set pressure corresponds to the differential activation pressure of the PRV. If the differential pressure is less than 30% of the set pressure, operation 508 moves to box 610, where valve state determination circuit 208 determines whether the system pressure is greater than 103%. If the system pressure is not greater than 103%, or if there is no system pressure measurement associated with the PRV being analyzed, operation 508 moves to box 612, where valve state determination circuit 208 assigns a valve state of valve closure, close to the set pressure. Operation 508 moves to box 624, where valve state determination circuit 208 determines whether all PRVs have been analyzed. If all PRVs have been analyzed, operation 508 returns to... Figure 5 Operation 500. If not all PRVs have been analyzed, operation 508 returns to box 602, where the valve status determination circuit 208 identifies the new pressure sensor to be analyzed.

[0059] Returning to box 610, if valve status determination circuit 208 determines that the system pressure is greater than 103% of the set pressure, operation 508 moves to box 622, where valve status determination circuit 208 assigns an operational error to the valve. In this example, the operational error is that the system pressure exceeds the maximum permissible operating pressure of the PRV without any PRV activation. Operation 508 moves to box 624, where valve status determination circuit 208 determines whether all PRVs have been analyzed. If all PRVs have been analyzed, operation 508 returns to... Figure 5 Operation 500. If not all PRVs have been analyzed, operation 508 returns to box 602, where the valve status determination circuit 208 identifies the new pressure sensor to be analyzed.

[0060] Returning to box 608, if valve status determination circuit 208 determines that the differential pressure is not less than 30% of the set pressure, operation 508 moves to box 614, where valve status determination circuit 208 determines whether the system pressure is less than 97% of the set pressure. If the system pressure is less than 97% of the set pressure, operation 508 moves to box 622, where valve status determination circuit 208 assigns an operational error to the valve status. In this example, the operational error is that the PRV is activated when the system pressure is below the set pressure (e.g., the PRV is released prematurely). Operation 508 moves to box 624, where valve status determination circuit 208 determines whether all PRVs have been analyzed. If all PRVs have been analyzed, operation 508 returns to... Figure 5 Operation 500. If not all PRVs have been analyzed, operation 508 returns to box 602, where the valve status determination circuit 208 identifies the new pressure sensor to be analyzed.

[0061] Returning to box 614, if valve status determination circuit 208 determines that the system pressure is not less than 97% of the set pressure, operation 508 continues to box 616. At box 616, valve status determination circuit 208 determines whether the differential pressure is greater than 65% of the set pressure. In this example, 65% of the set pressure corresponds to the upper threshold setpoint of the PRV. If the differential pressure is not greater than 65% of the set pressure, operation 508 moves to box 620, where valve status determination circuit 208 sets the valve status with proportional release. In other words, valve status determination circuit 208 determines that the PRV has begun to open and release fluid, but has not yet reached its maximum lift. Operation 508 moves to box 624, where valve status determination circuit 208 determines whether all PRVs have been analyzed. If all PRVs have been analyzed, operation 508 returns to... Figure 5 Operation 500. If not all PRVs have been analyzed, operation 508 returns to box 602, where the valve status determination circuit 208 identifies the new pressure sensor to be analyzed.

[0062] Returning to box 616, if valve status determination circuit 208 determines that the differential pressure is greater than 65% of the set pressure, operation 508 continues to box 618. At box 618, valve status determination circuit 208 sets the valve status to have maximum release. In other words, valve status determination circuit 208 determines that the PRV has reached the valve's maximum lift and that the PRV is releasing fluid at its maximum rate. Operation 508 moves to box 624, where valve status determination circuit 208 determines whether all PRVs have been analyzed. If all PRVs have been analyzed, operation 508 returns to... Figure 5 Operation 500. If not all PRVs have been analyzed, operation 508 returns to box 602, where the valve status determination circuit 208 identifies the new pressure sensor to be analyzed.

[0063] Figure 7 It is configured to execute and / or instantiate exemplary machine-readable instructions and / or Figure 5 and / or Figure 6 Exemplary operations to achieve Figure 2 A block diagram of an exemplary programmable circuit platform 700 for controller 102. Programmable circuit platform 700 can be, for example, a server, personal computer, workstation, self-learning machine (e.g., neural network), mobile device (e.g., cellular phone, smartphone, such as iPad). TM Tablet computers, personal digital assistants (PDAs), internet devices, head-mounted devices (e.g., augmented reality (AR) headsets, virtual reality (VR) headsets, etc.) or other wearable devices, or any other type of computing and / or electronic device.

[0064] The programmable circuit platform 700 shown in the example includes a programmable circuit 712. The programmable circuit 712 shown in the example is hardware. For example, the programmable circuit 712 can be implemented by one or more integrated circuits, logic circuits, FPGAs, microprocessors, CPUs, GPUs, DSPs, and / or microcontrollers from any desired family or manufacturer. The programmable circuit 712 can be implemented by one or more semiconductor-based (e.g., silicon-based) devices. In this example, the programmable circuit 712 implements a sensor identification circuit 202, a setpoint determination circuit 204, a pressure data receiving circuit 206, a valve status determination circuit 208, and a report generation circuit 210.

[0065] The programmable circuit 712 of the illustrated example includes local memory 713 (e.g., cache, registers, etc.). The programmable circuit 712 of the illustrated example communicates via bus 718 with main memories 714, 716, including volatile memory 714 and non-volatile memory 716. The volatile memory 714 may be implemented using synchronous dynamic random access memory (SDRAM), dynamic random access memory (DRAM), RAMBUS® dynamic random access memory (RDRAM®), and / or any other type of RAM device. The non-volatile memory 716 may be implemented using flash memory, and / or any other desired type of memory device. Access to the main memories 714, 716 of the illustrated example is controlled by a memory controller 717. In some examples, the memory controller 717 may be implemented using one or more integrated circuits, logic circuitry, microcontrollers from any desired family or manufacturer, or any other type of circuitry to manage data flows to and from the main memories 714, 716.

[0066] The programmable circuit platform 700 shown in the example also includes interface circuitry 720. Interface circuitry 720 can be implemented in hardware according to any type of interface standard, such as an Ethernet interface, a Universal Serial Bus (USB) interface, a Bluetooth® interface, a Near Field Communication (NFC) interface, a Peripheral Component Interconnect (PCI) interface, and / or a Peripheral Component Interconnect Fast (PCIe) interface.

[0067] In the example shown, one or more input devices 722 are connected to interface circuitry 720. The input devices 722 allow users (e.g., human users, machine users, etc.) to input data and / or commands into programmable circuitry 712. Input devices 722 can be implemented as, for example, audio sensors, microphones, cameras (still or video), keyboards, buttons, mice, touchscreens, touchpads, trackballs, isotope devices, and / or voice recognition systems.

[0068] One or more output devices 724 are also connected to the interface circuitry 720 of the illustrated example. The output devices 724 may be implemented, for example, by display devices (e.g., light-emitting diode (LED), organic light-emitting diode (OLED), liquid crystal display (LCD), cathode ray tube (CRT) display, flat panel display (IPS), touchscreen, etc.), haptic output devices, printers, and / or speakers. Therefore, the interface circuitry 720 of the illustrated example typically includes a graphics driver card, a graphics driver chip, and / or graphics processor circuitry such as a GPU.

[0069] The interface circuitry 720 of the example shown also includes communication devices such as transmitters, receivers, transceivers, modems, residential gateways, wireless access points, and / or network interfaces to facilitate the exchange of data with external machines (e.g., any kind of computing device) via network 726. Communication can be achieved through, for example, Ethernet connections, digital subscriber line (DSL) connections, telephone line connections, coaxial cable systems, satellite systems, beyond-line-of-sight wireless systems, line-of-sight wireless systems, cellular telephone systems, optical connections, etc.

[0070] The programmable circuit platform 700 shown in the example also includes one or more mass storage disks or devices 728 for storing firmware, software, and / or data. Examples of such mass storage disks or devices 728 include magnetic storage devices (e.g., floppy disks, drives, HDDs, etc.), optical storage devices (e.g., Blu-ray discs, CDs, DVDs, etc.), RAID systems, and / or solid-state storage disks or devices (such as flash memory devices and / or SSDs).

[0071] It can be by Figure 5 and / or Figure 6 The machine-readable instructions 732 implemented by the machine-readable instructions can be stored in a mass storage device 728, a volatile memory 714, a non-volatile memory 716 and / or at least one non-transitory computer-readable storage medium (such as a removable CD or DVD).

[0072] Figure 8 yes Figure 7 A block diagram illustrating an exemplary implementation of the programmable circuit 712. In this example, Figure 7 The programmable circuit 712 is implemented by the microprocessor 800. For example, the microprocessor 800 can be a general-purpose microprocessor (e.g., a general-purpose microprocessor circuit). The microprocessor 800 executes... Figure 5 and / or Figure 6 The flowchart contains some or all of the machine-readable instructions to effectively translate... Figure 2 The circuit is instantiated as a logic circuit to perform operations corresponding to those machine-readable instructions. In some such examples, Figure 2The circuitry is instantiated by the hardware circuitry of the microprocessor 800 in conjunction with machine-readable instructions. For example, the microprocessor 800 can be implemented by multi-core hardware circuitry such as a CPU, DSP, GPU, XPU, etc. Although it can include any number of exemplary cores 802 (e.g., one core), this example microprocessor 800 is a multi-core semiconductor device including N cores. The cores 802 of the microprocessor 800 can operate independently or collaboratively to execute machine-readable instructions. For example, machine code corresponding to firmware, embedded software programs, or software programs can be executed by one core of core 802, or by multiple cores of core 802 at the same or different times. In some examples, the machine code corresponding to firmware, embedded software programs, or software programs is divided into threads and executed in parallel by two or more cores 802. The software program can correspond to... Figure 5 and / or Figure 6 The flowchart represents part or all of the machine-readable instructions and / or operations.

[0073] Core 802 can communicate via a first exemplary bus 804. In some examples, the first bus 804 can be implemented as a communication bus to enable communication associated with one or more cores of core 802. For example, the first bus 804 can be implemented as at least one of an inter-integrated circuit (I2C) bus, a serial peripheral interface (SPI) bus, a PCI bus, or a PCIe bus. Additionally or alternatively, the first bus 804 can be implemented as any other type of computing or electrical bus. Core 802 can obtain data, instructions, and / or signals from one or more external devices via exemplary interface circuitry 806. Core 802 can output data, instructions, and / or signals to one or more external devices via interface circuitry 806. Although the core 802 in this example includes exemplary local memory 820 (e.g., a Level 1 (L1) cache that can be divided into an L1 data cache and an L1 instruction cache), the microprocessor 800 also includes exemplary shared memory 810 (e.g., a Level 2 (L2) cache) that can be shared by the cores for high-speed access to data and / or instructions. Data and / or instructions can be transferred (e.g., shared) by writing to and / or reading from shared memory 810. The local memory 820 and shared memory 810 of each core in core 802 can include multi-level cache memory and main memory (e.g., ...). Figure 7 The cache is part of the storage device hierarchy (main memory 714, 716). Generally, higher-level memories in the hierarchy exhibit lower access times and have smaller storage capacities compared to lower-level memories. Changes to the various levels of the cache hierarchy are managed by cache coherence policies (e.g., reconciliation).

[0074] Each core 802 may be referred to as a CPU, DSP, GPU, or any other type of hardware circuitry. Each core 802 includes control unit circuitry 814, arithmetic and logic (AL) circuitry (sometimes called ALU) 816, multiple registers 818, local memory 820, and a second exemplary bus 822. Other structures may be present. For example, each core 802 may include vector unit circuitry, single instruction multiple data (SIMD) unit circuitry, load / store unit (LSU) circuitry, branch / jump unit circuitry, floating-point unit (FPU) circuitry, etc. Control unit circuitry 814 includes semiconductor-based circuitry configured to control (e.g., coordinate) the movement of data within the corresponding core 802. AL circuitry 816 includes semiconductor-based circuitry configured to perform one or more mathematical and / or logical operations on data within the corresponding core 802. Some examples of AL circuitry 816 perform integer-based operations. In other examples, AL circuitry 816 also performs floating-point operations. In other examples, AL circuitry 816 may include a first AL circuitry performing integer-based operations and a second AL circuitry performing floating-point operations. In some examples, the AL circuit 816 may be referred to as an arithmetic logic unit (ALU).

[0075] Register 818 is a semiconductor-based structure used to store data and / or instructions, such as the results of one or more operations performed by the AL circuit 816 corresponding to core 802. For example, register 818 may include vector registers, SIMD registers, general-purpose registers, flag registers, segment registers, machine-specific registers, instruction pointer registers, control registers, debug registers, memory management registers, machine check registers, etc. Register 818 may be arranged in a manner such as... Figure 8 In the bank shown. Alternatively, register 818 can be organized in any other arrangement, format, or structure, such as by distributing it throughout core 802 to reduce access time. The second bus 822 can be implemented by at least one of an I2C bus, an SPI bus, a PCI bus, or a PCIe bus.

[0076] Each core 802 and / or more generally, the microprocessor 800 may include additional and / or alternative structures to those shown and described above. For example, one or more clock circuits, one or more power supplies, one or more power gates, one or more cache home agents (CHAs), one or more converged / common mesh stops (CMSs), one or more shifters (e.g., barrel shifters), and / or other circuitry may be present. The microprocessor 800 is a semiconductor device fabricated to include a plurality of interconnected transistors to implement the above-described structures in one or more integrated circuits (ICs) contained in one or more packages.

[0077] Microprocessor 800 may include one or more accelerators (e.g., acceleration circuitry, hardware accelerators, etc.) and / or cooperate with one or more accelerators. In some examples, accelerators are implemented by logic circuitry to perform certain tasks faster and / or more efficiently than a general-purpose processor. Examples of accelerators include ASICs and FPGAs, such as those discussed herein. GPUs, DSPs, and / or other programmable devices may also be accelerators. Accelerators may be on the board of microprocessor 800, in the same chip package as microprocessor 800, and / or in one or more packages separate from microprocessor 800.

[0078] Figure 9 yes Figure 7 A block diagram illustrating another example implementation of the programmable circuit 712. In this example, the programmable circuit 712 is implemented by an FPGA circuit 900. For example, the FPGA circuit 900 can be implemented by an FPGA. The FPGA circuit 900 can be used, for example, to perform operations that would otherwise be implemented by... Figure 8 The example microprocessor 800 executes the corresponding machine-readable instructions. However, once configured, the FPGA circuitry 900 instantiates the operations and / or functions corresponding to the machine-readable instructions in hardware, and therefore can typically execute the operations / functions faster than if they were executed by a general-purpose microprocessor executing the corresponding software.

[0079] More specifically, with the above Figure 8 The microprocessor 800 (which can be programmed to execute by) Figure 5 and / or Figure 6 Compared to a general-purpose device (one or more flowcharts representing some or all of the machine-readable instructions, but whose interconnections and logic circuitry are fixed once manufactured), Figure 9 The example FPGA circuit 900 includes interconnects and logic circuitry, which can be configured, constructed, programmed, and / or interconnected in different ways after manufacturing to instantiate, for example, with... Figure 5 and / or Figure 6 The flowchart(s) represent some or all of the machine-readable instructions corresponding to the operations / functions. Specifically, the FPGA circuit 900 can be considered as an array of logic gates, interconnects, and switches. Switches can be programmed to change how the logic gates are interconnected, effectively forming one or more dedicated logic circuits (unless and until the FPGA circuit 900 is reprogrammed). The configured logic circuits enable the logic gates to cooperate in different ways to perform different operations on data received from the input circuits. These operations can correspond to... Figure 5 and / or Figure 6 The flowchart represents some or all of the instructions (e.g., software and / or firmware). Therefore, the FPGA circuit 900 can be configured and / or constructed to effectively connect with... Figure 5 and / or Figure 6 Some or all of the machine-readable instructions corresponding to the flowcharts (one or more) are instantiated as special-purpose logic circuits to perform the operations / functions corresponding to those software instructions in a specialized manner similar to that of an ASIC. Therefore, the FPGA circuit 900 can execute operations / functions that a general-purpose microprocessor can perform. Figure 5 and / or Figure 6 Some or all of the machine-readable instructions can be executed faster than Figure 5 and / or Figure 6 Operations / functions corresponding to some or all of the machine-readable instructions.

[0080] exist Figure 9 In some examples, the FPGA circuit 900 is configured and / or constructed in response to being programmed (and / or reprogrammed once or multiple times) based on a binary file. In some examples, the binary file can be compiled and / or generated based on instructions from a hardware description language (HDL) such as Lucid, VHSIC (Very High Speed ​​Integrated Circuit) Hardware Description Language (VHDL), or Verilog. For example, a user (e.g., a human user, a machine user, etc.) can write code or programs in the HDL corresponding to one or more operations / functions; the code / program can be translated into a low-level language as needed; and the code / program (e.g., low-level language code / program) can be converted (e.g., by a compiler, software application, etc.) into a binary file. In some examples, Figure 9 The FPGA circuit 900 can access and / or load binary files to enable Figure 9 The FPGA circuit 900 is configured and / or constructed to perform one or more operations / functions. For example, a binary file may consist of a bit stream (e.g., one or more computer-readable bits, one or more machine-readable bits, etc.), data (e.g., computer-readable data, machine-readable data, etc.), and / or Figure 9The FPGA circuitry is implemented using machine-readable instructions accessible to it, enabling configuration and / or construction. Figure 9 The FPGA circuit 900 or one or more of its components.

[0081] In some examples, the binary file is compiled, generated, transformed, and / or otherwise output from a unified software platform used to program the FPGA. For example, the unified software platform can translate a first instruction (e.g., code or program) corresponding to one or more operations / functions in a high-level language (e.g., C, C++, Python, etc.) into a second instruction corresponding to one or more operations / functions in an HDL. In some such examples, the binary file is compiled, generated, and / or otherwise output from the unified software platform based on the second instruction. In some examples, Figure 9 The FPGA circuit 900 can access and / or load binary files to enable Figure 9 The FPGA circuit 900 is configured and / or constructed to perform one or more operations / functions. For example, a binary file may consist of a bit stream (e.g., one or more computer-readable bits, one or more machine-readable bits, etc.), data (e.g., computer-readable data, machine-readable data, etc.), and / or Figure 9 The FPGA circuitry is implemented using machine-readable instructions accessible to it, enabling configuration and / or construction. Figure 9 The FPGA circuit 900 or one or more of its components.

[0082] Figure 9 The FPGA circuitry 900 includes exemplary input / output (I / O) circuitry 902 for obtaining and / or outputting data from / to exemplary configuration circuitry 904 and / or external hardware 906. For example, configuration circuitry 904 may be implemented by interface circuitry capable of obtaining a binary file, which may be implemented as a bitstream, data, and / or machine-readable instructions to configure FPGA circuitry 900 or portions thereof. In some such examples, configuration circuitry 904 may obtain the binary file from a user, a machine (e.g., hardware circuitry (e.g., programmable or dedicated circuitry) capable of implementing artificial intelligence / machine learning (AI / ML) models to generate binary files, and / or any combination thereof). In some examples, external hardware 906 may be implemented by external hardware circuitry. For example, external hardware 906 may be implemented by… Figure 8 The microprocessor 800 is implemented.

[0083] The FPGA circuit 900 also includes an array of exemplary logic gates 908, a plurality of exemplary configurable interconnects 910, and exemplary memory circuitry 912. The logic gates 908 and the configurable interconnects 910 are configurable to instantiate one or more operations / functions, which may correspond to... Figure 5 and / or Figure 6 At least some machine-readable instructions and / or other expected operations. Figure 9 The logic gate circuit 908 shown is manufactured in blocks or groups. Each block includes a semiconductor-based electrical structure that can be configured into a logic circuit. In some examples, the electrical structure includes logic gates (e.g., AND gates, OR gates, NOR gates, etc.) that provide basic building blocks for the logic circuit. Electrically controllable switches (e.g., transistors) are present within each logic gate circuit 908 to enable the configuration of the electrical structure and / or logic gates to form a circuit for performing a desired operation / function. The logic gate circuit 908 may include other electrical structures such as lookup tables (LUTs), registers (e.g., flip-flops or latches), multiplexers, etc.

[0084] The configurable interconnect 910 in the example shown is a conductive path, trace, via, etc., which may include electrically controllable switches (e.g., transistors) whose states can be changed by programming (e.g., using an HDL instruction language) to activate or deactivate one or more connections between one or more logic gates 908 to program the desired logic circuit.

[0085] The storage circuit 912 in the example shown is configured to store the results of one or more operations performed by the corresponding logic gates. The storage circuit 912 can be implemented using registers, etc. In the example shown, the storage circuit 912 is distributed among the logic gates 908 to facilitate access and improve execution speed.

[0086] Figure 9 The exemplary FPGA circuit 900 also includes exemplary dedicated operating circuitry 914. In this example, dedicated operating circuitry 914 includes dedicated circuitry 916, which can be invoked to implement common functions, thereby avoiding the need for on-site programming of these functions. Examples of such dedicated circuitry 916 include memory (e.g., DRAM) controller circuitry, PCIe controller circuitry, clock circuitry, transceiver circuitry, memory, and multiplier-accumulator circuitry. Other types of dedicated circuitry may be present. In some examples, FPGA circuitry 900 may also include exemplary general-purpose programmable circuitry 918, such as exemplary CPU 920 and / or exemplary DSP 922. Other general-purpose programmable circuitry 918, such as GPU, XPU, etc., may additionally or alternatively be present, which can be programmed to perform other operations.

[0087] although Figure 8 and Figure 9 It shows Figure 7 These are two exemplary implementations of the programmable circuit 712, but many other methods are conceivable. For example, the FPGA circuit may include an onboard CPU, such as... Figure 8One or more of the exemplary CPUs 920. Therefore, Figure 7 The programmable circuit 712 can be further combined with at least Figure 8 Exemplary microprocessor 800 and Figure 9 This is implemented using an exemplary FPGA circuit 900. In some such hybrid examples, Figure 8 One or more cores of the 802 can execute commands by Figure 5 and / or Figure 6 The flowchart(s) represent the first part of machine-readable instructions to perform one or more first operations / functions. Figure 9 The FPGA circuit 900 can be configured and / or constructed to perform operations related to... Figure 5 and / or Figure 6 The flowchart represents the second part of a machine-readable instruction corresponding to one or more second operations / functions, and / or the ASIC can be configured and / or constructed to perform operations corresponding to those specified by the second part of the instruction. Figure 5 and / or Figure 6 The flowchart represents the third part of a machine-readable instruction, corresponding to one or more third operations / functions.

[0088] It should be understood that Figure 2 Some or all of the circuitry can therefore be instantiated at the same or different times. For example, Figure 8 The same and / or different parts of the microprocessor 800 can be programmed to execute parts of machine-readable instructions at the same and / or different times. In some examples, Figure 9 The same and / or different parts of the FPGA circuit 900 can be configured and / or constructed to perform operations / functions corresponding to parts of machine-readable instructions at the same and / or different times.

[0089] In some examples, Figure 2 Some or all of the circuitry can be instantiated, for example, in one or more threads executing concurrently. For example, Figure 8 The microprocessor 800 can execute machine-readable instructions in one or more threads that execute concurrently and / or serially. In some examples, Figure 9 The FPGA circuit 900 can be configured and / or constructed to perform operations / functions concurrently and / or serially. Furthermore, in some examples, Figure 2 Some or all of the circuits can be Figure 8 One or more virtual machines and / or containers are implemented and executed on the microprocessor 800.

[0090] In some examples, Figure 7 The programmable circuit 712 can be housed in one or more packages. For example, Figure 8 microprocessors 800 and / or Figure 9 The FPGA circuitry 900 can be housed in one or more packages. In some examples, the XPU can be... Figure 7 The programmable circuit 712 is implemented and can be in one or more packages. For example, the XPU may include a CPU in a package (e.g., Figure 8 microprocessor 800, Figure 9 CPU 920, etc.), and DSP in another package (e.g., Figure 9 DSP 922), GPU in another package, and FPGA in yet another package (e.g., Figure 9 FPGA circuit 900).

[0091] "Comprising" and "including" (and all their forms and tenses) are used herein as open-ended terms. Therefore, whenever a claim uses any form of "comprising" or "including" (e.g., including, containing, comprising, having, etc.) as a preamble or within any kind of claim statement, it should be understood that additional elements, terms, etc., may be present without falling outside the scope of the corresponding claim or statement. As used herein, when the phrase "at least" is used as a transitional term, for example, in the preamble of a claim, it is open-ended in the same way that the terms "comprising" and "including" are open-ended. When used, for example, in the form of A, B, and / or C, the term "and / or" refers to any combination or subset of A, B, C, such as (1) only A, (2) only B, (3) only C, (4) A and B, (5) A and C, (6) B and C, or (7) A and B and C. As used herein in the context of describing structures, components, projects, objects, and / or things, the phrase “at least one of A and B” is intended to refer to an implementation that includes (1) at least one A, (2) at least one B, or (3) at least one A and at least one B. Similarly, as used herein in the context of describing structures, components, projects, objects, and / or things, the phrase “at least one of A or B” is intended to refer to an implementation that includes (1) at least one A, (2) at least one B, or (3) at least one A and at least one B. As used herein in the context of describing the operation or execution of processes, instructions, actions, activities, etc., the phrase “at least one of A and B” is intended to refer to an implementation that includes (1) at least one A, (2) at least one B, or (3) at least one A and at least one B. Similarly, as used herein in the context of describing the operation or execution of processes, instructions, actions, activities, etc., the phrase “at least one of A or B” is intended to refer to an implementation that includes (1) at least one A, (2) at least one B, or (3) at least one A and at least one B.

[0092] As used herein, singular references (e.g., "a," "an," "first," "second," etc.) do not exclude plural. As used herein, the term "a" or "an" refers to one or more of the same object. The terms "a" (or "an"), "one or more," and "at least one" are used interchangeably herein. Furthermore, although listed separately, multiple means, elements, or actions may be implemented by, for example, the same entity or object. Additionally, although individual features may be included in different examples or claims, these features may be combined, and inclusion in different examples or claims does not imply that the combination of features is infeasible and / or disadvantageous.

[0093] As used herein, unless otherwise stated, the term "above" describes the relationship of two parts relative to the Earth. The first part is above the second part if the second part has at least one portion between the Earth and the first part. Similarly, as used herein, the first part is "below" the second part when the first part is closer to the Earth than the second part. As stated above, the first part may be above or below the second part and may have one or more of the following: other portions between them, no other portions between them, the first and second parts in contact, or the first and second parts not in direct contact with each other.

[0094] As used in this patent, a statement that any part (e.g., layer, film, region, area, or plate) is on another part in any way (e.g., positioned on another part, located on another part, disposed on another part, or formed on another part, etc.) indicates that the referenced part is in contact with the other part or that the referenced part is above the other part, wherein one or more intermediate parts are located therebetween.

[0095] As used herein, unless otherwise stated, a connection reference (e.g., attachment, coupling, connection, and linkage) may include intermediate components between the elements referenced by the connection reference and / or relative movement between these elements. Therefore, a connection reference does not necessarily imply that two elements are directly connected and / or fixed to each other. As used herein, the statement that any part is in “contact” with another part is defined as meaning that there is no intermediate part between the two parts.

[0096] Unless otherwise specified, descriptors such as “first,” “second,” “third,” etc., are used herein without imposing or otherwise indicating any meaning of priority, physical order, arrangement in a list, and / or any sorting, but merely as labels and / or arbitrary names to distinguish elements for the purpose of understanding the disclosed examples. In some examples, the descriptor “first” may be used to refer to an element in a particular embodiment, while the same element may be referred to in the claims by different descriptors (such as “second” or “third”). In such cases, it should be understood that such descriptors are only used to clearly identify those elements in the context of the discussion (e.g., in the claims), where elements may otherwise share the same name, for example.

[0097] As used herein, “approximately” and “about” modify their subject / value to identify the potential for variation in real-world applications. For example, as those skilled in the art will understand, “approximately” and “about” can modify dimensions that may not be precise due to manufacturing tolerances and / or other real-world defects. For example, unless otherwise stated herein, “approximately” and “about” can indicate that such a dimension is within a tolerance of + / - 10%.

[0098] As used in this article, "substantially real-time" means occurring in a near-instantaneous manner, acknowledging the real-world delays that may exist in computation time, transmission, etc. Therefore, unless otherwise stated, "substantially real-time" means real-time plus 1 second.

[0099] As used herein, the phrase “communication” (including its variations) covers direct communication and / or indirect communication through one or more intermediate components, and does not require direct physical (e.g., wired) communication and / or continuous communication, but additionally includes selective communication at periodic intervals, predetermined intervals, non-periodic intervals and / or one-off events.

[0100] As used herein, “programmable circuit” is defined as including (i) one or more special-purpose circuits (e.g., special-purpose circuits (ASICs) configured to perform one or more specific operations and including one or more semiconductor-based logic devices (e.g., electrical hardware implemented by one or more transistors)), and / or (ii) one or more general-purpose semiconductor-based circuits that can be programmed with instructions to perform one or more specific functions and / or operations and include one or more semiconductor-based logic devices (e.g., electrical hardware implemented by one or more transistors). Examples of programmable circuits include programmable microprocessors, such as a central processing unit (CPU) capable of executing a first instruction to perform one or more operations and / or functions, a field-programmable gate array (FPGA) capable of being programmed with a second instruction to instantiate one or more operations and / or functions corresponding to the first instruction by the configuration and / or construction of an FPGA, a graphics processing unit (GPU) capable of executing a first instruction to perform one or more operations and / or functions, a digital signal processor (DSP) capable of executing a first instruction to perform one or more operations and / or functions, an XPU, a network processing unit (NPU) capable of executing a first instruction to perform one or more operations and / or functions, and / or an integrated circuit such as an application-specific integrated circuit (ASIC). For example, an XPU can be implemented by a heterogeneous computing system that includes multiple types of programmable circuits (e.g., one or more FPGAs, one or more CPUs, one or more GPUs, one or more NPUs, one or more DSPs, etc., and / or any combination thereof), and orchestration techniques (e.g., one or more application programming interfaces (APIs) that can assign one or more computing tasks to any of the multiple types of programmable circuits that is suitable and can be used to perform one or more computing tasks).

[0101] As used herein, an integrated circuit / circuit is defined as one or more semiconductor packages containing one or more circuit elements, such as transistors, capacitors, inductors, resistors, current paths, diodes, etc. For example, an integrated circuit can be implemented as one or more of an ASIC, FPGA, chip, microchip, programmable circuit, semiconductor substrate coupling multiple circuit elements, system-on-a-chip (SoC), etc.

[0102] Based on the foregoing, it should be understood that exemplary systems, apparatuses, articles, and methods have been disclosed that determine whether a pressure relief valve is close to activation based on differential pressure measurements and operating thresholds. In this way, the disclosed systems, apparatuses, articles, and methods allow monitoring and / or control systems of pressure systems to provide an indication to control systems and / or users managing the fluid system that the pressure within the fluid system is approaching the maximum permissible operating pressure. This indication allows for corrective actions or other preparations to be performed before the pressure relief valve discharges fluid. Therefore, the disclosed systems, apparatuses, articles, and methods relate to one or more improvements to the operation of machines such as computers or other electronic and / or mechanical equipment.

[0103] This document discloses exemplary methods, apparatus, systems, and articles of manufacture for determining whether a pressure relief valve is close to activation. Further examples and combinations thereof include the following:

[0104] Example 1 includes a computing device comprising interface circuitry, machine-readable instructions, and programmable circuitry for instantiating or executing at least one of the machine-readable instructions to perform the following operations: obtaining pressure data from a pressure sensor associated with a differential pressure between a first region and a second region of a pressure relief valve, the first region being different from the second region; obtaining setpoint data corresponding to a threshold pressure and an activation pressure of the pressure relief valve; determining, based on the pressure data and the setpoint data, whether the differential pressure lies between the threshold pressure and the activation pressure; and generating an indication corresponding to the differential pressure lying between the threshold pressure and the activation pressure.

[0105] Example 2 includes the computing device described in Example 1, wherein the indication corresponds to the pressure relief valve being activated upon proximity.

[0106] Example 3 includes the computing device of any one of Examples 1 or 2, wherein the first region is the inlet of the pressure relief valve and the second region is the dome of the pressure relief valve.

[0107] Example 4 includes the computing device described in Example 3, wherein the programmable circuitry is further configured to determine the state of the pressure relief valve based on pressure data and setpoint data, and generate a second indication corresponding to the state of the pressure relief valve.

[0108] Example 5 includes the computing device described in Example 4, wherein determining the state of the pressure relief valve includes determining whether the differential pressure is lower than the activation pressure based on pressure data and setpoint data, and generating a second indication includes generating an indication corresponding to the closed state of the pressure relief valve.

[0109] Example 6 includes the computing device of any one of Examples 4 or 5, wherein the setpoint data includes a second threshold pressure greater than the activation pressure, determining the state of the pressure relief valve includes determining whether the differential pressure is greater than the activation pressure and less than the second threshold pressure based on the pressure data and the setpoint data, and generating a second indication includes generating an indication corresponding to the proportional release state of the pressure relief valve.

[0110] Example 7 includes the computing device of any one of Examples 4-6, wherein the setpoint data includes a second threshold pressure greater than the activation pressure, determining the state of the pressure relief valve includes determining whether the differential pressure is greater than the second threshold pressure based on the pressure data and the setpoint data, and generating a second indication includes generating an indication corresponding to the maximum release state of the pressure relief valve.

[0111] Example 8 includes the computing device described in any one of Examples 4-7, wherein obtaining pressure data includes obtaining pressure data from a second pressure sensor for generating a gauge pressure measurement associated with a second region, setpoint data includes activating gauge pressure, determining the state of the pressure relief valve includes determining, based on the pressure data and setpoint data, whether the gauge pressure measurement is greater than the activating gauge pressure and whether the differential pressure is less than the activating pressure, and generating a second indication includes generating an indication corresponding to an operational error state of the pressure relief valve.

[0112] Example 9 includes the computing device described in any one of Examples 1-8, wherein setpoint data is received via user input.

[0113] Example 10 includes a non-transitory machine-readable storage medium comprising instructions for causing a programmable circuit to perform at least the following operations: obtaining sensor identification data corresponding to a sensor operatively coupled to a pressure relief valve within a fluid system, the pressure relief valve being coupled to a pressure vessel; obtaining setpoint data corresponding to an activation differential pressure of the pressure relief valve; obtaining pressure data from the sensor corresponding to a differential pressure across a flow control element within the pressure relief valve, the flow control element being configured to selectively fluidly couple and selectively isolate the inlet of the pressure relief valve from its outlet based on the differential pressure rising above or falling below the activation differential pressure of the pressure relief valve; and determining the state of the pressure relief valve based on the sensor identification data, the setpoint data, and the pressure data.

[0114] Example 11 includes the non-transitory machine-readable storage medium of Example 10, wherein the setpoint data includes a lower threshold differential pressure, which is greater than zero and less than the activation differential pressure, and wherein determining the state of the pressure relief valve includes determining whether the differential pressure is higher than the lower threshold differential pressure and lower than the activation differential pressure.

[0115] Example 12 includes the non-transitory machine-readable storage medium described in Example 11, wherein setpoint data is obtained via user input, and the lower threshold differential pressure is limited by user input.

[0116] Example 13 includes any one of Examples 10-12, a non-transitory machine-readable storage medium, wherein the setpoint data includes an upper threshold differential pressure corresponding to the flow control member being located at a maximum distance from the inlet, and wherein determining the state of the pressure relief valve includes determining whether the differential pressure is at or above the upper threshold differential pressure.

[0117] Example 14 includes the non-transitory machine-readable storage medium of Example 13, wherein determining the state of the pressure relief valve includes determining whether the differential pressure is higher than the activation differential pressure and lower than the upper limit threshold differential pressure.

[0118] Example 15 includes a non-transitory machine-readable storage medium as described in any one of Examples 10-14, wherein the instructions further cause the programmable circuitry to perform the following operations: obtain sensor identification data corresponding to a second sensor operatively coupled to the inlet of a pressure relief valve; obtain setpoint data corresponding to the activation gauge pressure of the pressure relief valve; and obtain pressure data from the second sensor corresponding to the pressure in the inlet.

[0119] Example 16 includes the non-transitory machine-readable storage medium of Example 15, wherein determining the state of the pressure relief valve includes determining whether the pressure in the inlet is greater than the active gauge pressure and whether the differential pressure is lower than the active differential pressure.

[0120] Example 17 includes a method for detecting the proximity activation of a pressure relief valve, the method comprising: receiving sensor data corresponding to an identifier of a pressure sensor within a fluid system, the pressure sensor being used to measure pressure within the pressure relief valve, the pressure relief valve including an inlet and a dome; receiving setpoint data corresponding to an activation pressure of the pressure relief valve; receiving pressure data from the pressure sensor; and determining, based on the sensor data, the pressure data, and the setpoint data, whether the pressure relief valve is close to activation.

[0121] Example 18 includes the method of Example 17, further comprising sending sensor data corresponding to an identifier of a pressure relief valve determined to be proximity activated to the control system.

[0122] Example 19 includes the method of any one of Examples 17 or 18, wherein the setpoint data includes a minimum threshold pressure of the pressure relief valve, and determining whether the pressure relief valve is close to activation includes determining whether the pressure data is between the minimum threshold pressure and the activation pressure.

[0123] Example 20 includes the method of any one of Examples 17-19, wherein the setpoint data includes the maximum threshold pressure of the pressure relief valve, and determining whether the pressure relief valve is close to activation includes determining whether the pressure data is between the activation pressure and the maximum threshold pressure.

[0124] The appended claims are hereby incorporated by reference into this specific embodiment. Although certain exemplary systems, apparatuses, articles of manufacture, and methods have been disclosed herein, the scope of this patent is not limited thereto. Rather, this patent covers all systems, apparatuses, articles of manufacture, and methods that fall fully within the scope of the claims of this patent.

Claims

1. A computing device, comprising: Interface circuit; Machine-readable instructions; as well as A programmable circuit for instantiating or executing at least one of the machine-readable instructions to perform the following operations: Pressure data is obtained from a pressure sensor and is associated with the differential pressure between a first region and a second region of the pressure relief valve, wherein the first region is different from the second region; Obtain setpoint data corresponding to the threshold pressure and activation pressure of the pressure relief valve; Based on the pressure data and the setpoint data, determine whether the differential pressure is between the threshold pressure and the activation pressure; as well as Generate an indication corresponding to the differential pressure being between the threshold pressure and the activation pressure.

2. The computing device according to claim 1, wherein, The indication corresponds to the pressure relief valve being close to activation.

3. The computing device according to claim 1, wherein, The first region is the inlet of the pressure relief valve, and the second region is the dome of the pressure relief valve.

4. The computing device according to claim 3, wherein, The programmable circuit is also used for: Based on the pressure data and the setpoint data, the state of the pressure relief valve is determined; and A second indication corresponding to the state of the pressure relief valve is generated.

5. The computing device according to claim 4, wherein, Determining the state of the pressure relief valve includes determining whether the differential pressure is lower than the activation pressure based on the pressure data and the setpoint data, and generating the second indication includes generating an indication corresponding to the closed state of the pressure relief valve.

6. The computing device according to claim 4, wherein: The setpoint data includes a second threshold pressure, which is greater than the activation pressure. Determining the state of the pressure relief valve includes determining, based on the pressure data and the setpoint data, whether the differential pressure is greater than the activation pressure and less than the second threshold pressure; and Generating the second indication includes generating an indication corresponding to the proportional release state of the pressure relief valve.

7. The computing device according to claim 4, wherein: The setpoint data includes a second threshold pressure, which is greater than the activation pressure. Determining the state of the pressure relief valve includes determining whether the differential pressure is greater than the second threshold pressure based on the pressure data and the setpoint data; and Generating the second indication includes generating an indication corresponding to the maximum release state of the pressure relief valve.

8. The computing device according to claim 4, wherein: Obtaining the pressure data includes obtaining pressure data from a second pressure sensor, which is used to generate a gauge pressure measurement associated with the second region; The setpoint data includes the activation gauge pressure; Determining the state of the pressure relief valve includes determining, based on the pressure data and the setpoint data, whether the gauge pressure measurement is greater than the activation gauge pressure and whether the differential pressure is less than the activation pressure; and Generating the second indication includes generating an indication corresponding to an operational error state of the pressure relief valve.

9. The computing device according to claim 1, wherein, The setpoint data is received via user input.

10. A non-transitory machine-readable storage medium, comprising instructions that cause a programmable circuit to perform at least the following operations: Obtain sensor identification data corresponding to a sensor of a pressure relief valve operatively coupled to a pressure vessel within a fluid system; Obtain setpoint data corresponding to the activation differential pressure of the pressure relief valve; Pressure data is obtained from the sensor, the pressure data corresponding to the differential pressure across a flow control component within the pressure relief valve, the flow control component selectively fluidly coupling and selectively isolating the inlet of the pressure relief valve from the outlet of the pressure relief valve based on the differential pressure rising above or falling below the activation differential pressure of the pressure relief valve. as well as The state of the pressure relief valve is determined based on the sensor identification data, the setpoint data, and the pressure data.

11. The non-transitory machine-readable storage medium according to claim 10, wherein, The setpoint data includes a lower threshold differential pressure, which is greater than zero and less than the activation differential pressure, and wherein determining the state of the pressure relief valve includes determining whether the differential pressure is higher than the lower threshold differential pressure and lower than the activation differential pressure.

12. The non-transitory machine-readable storage medium according to claim 11, wherein, The setpoint data is obtained via user input, and the lower limit threshold differential pressure is limited by user input.

13. The non-transitory machine-readable storage medium according to claim 10, wherein, The setpoint data includes an upper threshold differential pressure, which corresponds to the maximum distance of the flow control component from the inlet, and wherein determining the state of the pressure relief valve includes determining whether the differential pressure is at or above the upper threshold differential pressure.

14. The non-transitory machine-readable storage medium according to claim 13, wherein, Determining the state of the pressure relief valve includes determining whether the differential pressure is higher than the activation differential pressure and lower than the upper limit threshold differential pressure.

15. The non-transitory machine-readable storage medium according to claim 10, wherein, The instructions also cause the programmable circuit to perform the following operations: Obtain sensor identification data corresponding to the second sensor operatively coupled to the inlet of the pressure relief valve; Obtain setpoint data corresponding to the activation gauge pressure of the pressure relief valve; as well as Pressure data corresponding to the pressure in the inlet is obtained from the second sensor.

16. The non-transitory machine-readable storage medium according to claim 15, wherein, Determining the state of the pressure relief valve includes determining whether the pressure in the inlet is greater than the activation gauge pressure and whether the differential pressure is lower than the activation differential pressure.

17. A method for detecting the proximity activation of a pressure relief valve, the method comprising: Receive sensor data corresponding to the identifier of a pressure sensor within the fluid system, the pressure sensor being used to measure the pressure within the pressure relief valve, the pressure relief valve including an inlet and a dome; Receive setpoint data corresponding to the activation pressure of the pressure relief valve; Receive pressure data from the pressure sensor; as well as Based on the sensor data, the pressure data, and the setpoint data, it is determined whether the pressure relief valve is close to activation.

18. The method of claim 17, further comprising transmitting the sensor data corresponding to an identifier of the pressure relief valve determined to be near-activated to the control system.

19. The method of claim 17, wherein, The setpoint data includes the minimum threshold pressure of the pressure relief valve, and determining whether the pressure relief valve is close to activation includes determining whether the pressure data is between the minimum threshold pressure and the activation pressure.

20. The method of claim 17, wherein, The setpoint data includes the maximum threshold pressure of the pressure relief valve, and determining whether the pressure relief valve is close to activation includes determining whether the pressure data is between the activation pressure and the maximum threshold pressure.

Images