Pressure management system

Abstract

Aspects of the disclosed technology provide a pressure management system in which pressure release is controlled by one or more programmable and updatable electronic controller / s. A pressure management system can include an electronic controller, a pressure sensor coupled to the electronic controller and to a pipe, wherein the pressure sensor is configured to relay pressure information about the pipe to the electronic controller, and a primary valve coupled between a vent and the electronic controller. The pressure management system can further include a cylinder coupled to the pipe via a secondary valve, and wherein the electronic controller is configured to actuate the primary valve and / or the secondary based on pressure information received from the pressure sensor. Processes and machine-readable media are also provided.

Description

BACKGROUND1. Technical Field

[0001] The present disclosure relates generally to control systems for a gas delivery infrastructure and, in particular, to the use of programmable valve controllers for managing fluid exchange in a gas piping infrastructure.2. Introduction

[0002] Gas-powered vehicles have become an important or even integral part of transportation systems and economies around the world. The widespread use of gas-powered vehicles and other power-generation systems has created increasing demands for refueling systems, stations, and technologies used to fuel / refuel the gas-powered vehicles and other power-generation systems. Moreover, the increasing demands for refueling systems, stations, and technologies have fueled efforts to deploy better, safer, and more efficient refueling systems and stations, such as gas filling stations. However, the combustibility, volatility, flammability and other properties of typical gas fuel sources, such as hydrogen, create safety issues for refueling systems, stations, and procedures. Consequently, safety regulations, standards, and practices have emerged to address the various safety issues associated with refueling systems, stations, and procedures. Nevertheless, the safety regulations, standards, and practices, as well as the demands for better safer, and more efficient refueling systems and stations have created difficult challenges in deploying or updating refueling systems and stations, managing refueling systems and stations, and dispensing gas to gas-powered systems and vehicles.BRIEF DESCRIPTION OF THE DRAWINGS

[0003] The various advantages and features of the present technology will become apparent by reference to specific implementations illustrated in the appended drawings. A person of ordinary skill in the art will understand that these drawings only show some examples of the present technology and would not limit the scope of the present technology. Furthermore, the skilled artisan will appreciate the principles of the present technology as described and explained with additional specificity and detail through the use of the accompanying drawings in which: FIG. 1A illustrates an example gas filling station for a vehicle, according to some examples of the present disclosure; FIG. 1B illustrates an example of transportable gas filling station, according to some examples of the present disclosure; FIG. 2 illustrates an example of a mechanical release valve that can be used to reduce pressure in a gas pipeline infrastructure; FIG. 3A illustrates an example pressure management system, including an electronic controller for managing pressure release from piping infrastructure, according to some examples of the present disclosure; FIG. 3B illustrates an example pressure management system, including an electronic controller for managing pressure release and cylinder (tank) filling operations, according to some aspects of the present disclosure; FIG. 4A is a flowchart illustrating an example process for managing pressure release in which pressure is kept below a predetermined threshold, according to some examples of the present disclosure; FIG. 4B is a flowchart illustrating an example process for managing pressure release in which pressure is kept above a predetermined threshold, according to some examples of the present disclosure; FIG. 4C conceptually illustrates a multitude of pressure threshold levels for operating a pressure management system, according to some examples of the present disclosure; FIG. 5 illustrates a method for managing pressure using an electronically controlled PRV, according to some examples of the present disclosure; and FIG. 6 illustrates an example processor-based system architecture for implementing certain aspects of the present disclosure. DETAILED DESCRIPTION

[0004] The detailed description set forth below is intended as a description of various configurations of the subject technology and is not intended to represent the only configurations in which the subject technology can be practiced. The appended drawings are incorporated herein and constitute a part of the detailed description. The detailed description includes specific details for the purpose of providing a more thorough understanding of the subject technology. However, it will be clear and apparent that the subject technology is not limited to the specific details set forth herein and may be practiced without these details. In some instances, structures and components are shown in block diagram form to avoid obscuring the concepts of the subject technology.

[0005] Pressure reducing valves (or pressure release valves) (PRVs) can be used in fluid dispensation systems to limit the maximum pressure at various locations in a network of piping, such as at critical junctions used for fluid transfer or dispensation. PRVs are sometimes used in gas dispensation infrastructure, such as in the piping of gas transportation modules for refueling vehicles using pressurized fuel tanks (or "cylinders"). In such cases, PRVs can utilize mechanical release mechanisms that release pressure to the atmosphere when the pressure in the pipe exceeds a maximum set-point, which can depend on equipment parameters, safety protocols, and / or regulation, etc. However, mechanical release valves, such as springs, are limited in functionality because they are triggered at a static pressure set point that cannot be easily adjusted for operation at different pressure set-point levels. As such, mechanical PRVs are not well adapted for different use cases, such as for use with different vehicle or cylinder types, and / or use in different temperature environments. Additionally, mechanical PRVs are prone to wear with repeated use; however, malfunctions can be difficult to identify without physical inspection. For example, mechanical PRVs can suffer from so-called "dead bands" whereby the PRV gradually opens as the pressure increases against its spring, causing a leak of gases and / or fluid, which can continue to increase in severity, until the threshold pressure is reached. Mechanical PRVs are also prone to malfunction due to hysteresis, e.g., wherein the valve closes at a lower pressure than it opens, causing the valve to remain open (leaking) if the pressure does not drop below the required closing pressure, even when the pressure is below the opening / threshold pressure.

[0006] Aspects of the disclosed technology address the limitations of mechanical PRVs by providing a pressure management system in which pressure release is controlled by one or more programmable and updatable electronic controller / s. For example, a pressure management system can include an electronic controller, such as a programmable logic controller (PLC), that is coupled to a valve (e.g., a primary valve) that regulates pressure release from a network of pipes. In some configurations, the controller can actuate the primary valve using a pneumatic coupling. However, other types of communication between the controller and the primary valve, such as electrical, electromagnetic, or other types of couplings may be used, without departing from the scope of the disclosed technology. Pressure information can be received by (or retrieved by) the controller from one or more pressure sensors in the pipes. Received pressure information can be used by logic of the electronic controller to make decisions about when to actuate the primary valve. In some implementations, the primary valve may be configured to be normally open, such that if power to the controller is lost, or of the compressed air supply for the valve control fails, the primary valve automatically opens to reduce pressure to, or approximate to, an ambient atmospheric pressure.

[0007] Using a pressure management system that includes an electronic controller to manage valve operation provides several advantages, including the ability to dynamically update pressure management system thresholds based on equipment specifications, improving safety across a variety of vehicles, cylinders, and in a variety of operating conditions such as different temperature and ambient pressure conditions. The disclosed pressure management system also enables more intelligent operation through the collection and use of various types of sensor data that can be received from one or more wired or wireless sensors in the surrounding environment, including but not limited to Internet-of-Thing (IoT) sensors, temperature sensors, ambient temperature sensors, pressure sensors, ambient pressure sensors, actuation counters, state of charge sensors, and / or density sensors, etc. As used herein, IoT sensors can refer to sensors configured for wireless communication with one or more controllers and / or with one or more other sensors, without the need for connection to a public computer network, such as the Internet. Additionally, actuation counters can include sensors or other devices that are configured to count a number of times a valve has been actuated. Further details regarding the operation of the disclosed pressure management system are provided below.

[0008] FIG. 1A depicts an example gas filling station 100 for a vehicle 120, according to some examples of the present disclosure. Gas filling station 100 can be configured similar to, or substantially as, a gas station. For example, vehicle 120 can use gas filling station 100 to refuel, as shown in FIG. 1A. In this example, the gas filling station 100 includes gas dispenser 110 configured to dispense gas, such as hydrogen gas, to vehicles such as vehicle 120. Gas dispenser 110 can include a re-fueling hose 114 with a nozzle 112 configured to detachably connect to filling port 122 of vehicle 120. Filling port 122 can be connected to an internal fuel tank (not shown in FIG. 1A) of the vehicle 120. Thus, the gas from the gas filling station 100 can flow from the gas dispenser 110 to the re-fueling hose 114 and the nozzle 112 connected to the filling port 122 of the vehicle 120. Gas can travel from the nozzle 112 and the filling port 122 of the vehicle 120 to the internal fuel tank of vehicle 120 to refill the internal fuel tank of vehicle 120.

[0009] While the example gas filling station 100 is described with respect to vehicle 120 (e.g., a car), gas filling station 100 can be deployed for refueling any applicable vehicle or gas-fueled system / device such as, for example and without limitation, a movable platform, a truck, a commercial vehicle, an industrial vehicle, a passenger vehicle, an aircraft, an aerial vehicle, a train, a boat or ship, a lawnmower, a motorcycle, a motorized tool or device, a subway vehicle, a watercraft, a locomotive, farm equipment, a construction vehicle, and / or a warehouse vehicle, among others.

[0010] In some examples, the source of gas dispensed by the gas filling station 100 can be or include one or more tanks storing the gas. For example, in some cases involving hydrogen gas, the source of the hydrogen dispensed by gas filling station 100 can be or include one or more tanks holding the hydrogen at a lower pressure (e.g., around 100 bar) relative to a desired delivery pressure (e.g., 600-900 bar). In some examples, the source of the hydrogen can be or include a hydrogen generator providing hydrogen gas at near ambient pressure.

[0011] Depending on the desired implementation, gas filling station 125 can be configured as a mobile refueling station for hydrogen, (e.g., a Mobile Hydrogen Refueling Station (MHRS)), or for gas, (e.g., a multi-element gas container (MEGC)) or a mobile refueling unit, such as mobile gas filling station 125 illustrated in FIG. 1B. For example, the gas filling station can be configured as a transportable self-contained module or system suitable for re-fueling gas-powered systems (e.g., vehicles, etc.) at remote locations or as part of a temporary installation (e.g., a construction site, a port, an airport, etc.). In other examples, the gas filling station can be configured as a module of a larger installation, such as a re-fueling station for air vehicles installed on a ship.

[0012] FIG. 1B illustrates an example mobile gas filling station 125 (also referred to as multi-element gas containers (MEGCs) or mobile refueling units) for refueling vehicles (e.g., a truck, a bus, a rail-bound vehicle, etc.). In this example, mobile gas filling station 125 can include a detachable tank container 130 and a mobile refueler 140. In some cases, tank container 130 can be mounted on a chassis of a vehicle (not shown) used to transport tank container 130, such as a truck, which allows tank container 130 to be transportable, disconnected from the mobile refueler 140, and / or filled separately.

[0013] Tank container 130 (also referred to as a gas storage unit) can be configured to store any gas, such as hydrogen gas. The size of the tank container 130 can vary depending on the storage capacity desired. In some examples, tank container 130 can include a control unit 132 for monitoring and / or controlling the status of tank container 130.

[0014] In some aspects, the mobile refueler 140 (also referred to as a buffer tank or a buffer unit) can include a control panel 142 with a nozzle 144, a buffer storage unit (e.g., a pressure tank) (not shown), a hydrogen compressor (not shown), and / or any applicable control unit. In some examples, the mobile refueler 140 can include a hydrogen pre-cooling unit to facilitate rapid refueling.

[0015] Gas stored in the tanks of the mobile gas filling station 125 (e.g., the tank container 130, the mobile refueler 140) can be dispensed to vehicles (and / or any other systems or devices) from a nozzle, such as nozzle 144. Mobile gas filling station 125 can include a network of pipes between the nozzle and any of the tanks of the mobile gas filling station 125. In some examples, the mobile gas filling station 125 can include one or more process elements (e.g., operation and / or safety elements) along one or more pipe paths. For example, the mobile gas filling station 125 can include one or more pressure relief valves (PRVs) along a pipe path to allow gas to vent (e.g., to release gas to the atmosphere) as needed.

[0016] Moreover, the mobile gas filling station 125 (and the gas filling station 100 shown in FIG. 1A) can include operations elements (not shown) used to manage the gas in the tanks, control refueling operations, provide safety / failsafe mechanisms for safe containment and dispensing of fuel (e.g., hydrogen etc.), etc. For example, the mobile gas filling station 125 (and the gas filling station 100 shown in FIG. 1A) can include one or more PRVs, one or more actuators, one or more switches, one or more tamper detection devices, one or more transmitters and / or transceivers, one or more sensors, one or more cooling components, one or more safety devices (e.g., valves, etc.), one or more flow metering and / or control devices, one or more leak detection devices, one or more gas (e.g., hydrogen) flow measurement devices, one or more emergency shutdown systems, one or more gauges, one or more fire-suppression mechanisms, one or more gas distribution and pressure management systems, one or more computing components (e.g., controllers, processors, computers, etc.), one or more compressors, etc. Non-limiting examples of a sensor that can be included or implemented by a gas filling station can include a temperature sensor, a pressure sensor, a fire sensor, a gas sensor, a flame detector, a leakage sensor, a flow sensor, a valve position sensor (e.g., sensor to detect if a valve is open or closed), an impedance sensor, an accelerometer, a gyroscope, an inertial measurement unit (IMU), a motion sensor, a position sensor, an image / camera sensor, a nuclear magnetic resonance (NMR) detector / spectrometer, a location sensor, and / or any other sensor device.

[0017] FIG. 2 illustrates an example of a mechanical release valve 202 that can be used to reduce pressure in a gas pipeline infrastructure 204. Mechanical release valve 202 is located at a juncture of pipe infrastructure 204, e.g., at a juncture of pipe section 204A and pipe section 204B. Mechanical release valve 202 can include a spring-loaded release mechanism configured to release gas or fluids from pipe infrastructure 204 at a specifically determined pressure level. As discussed above, mechanical release valves, such release valve 202, are limited in functionality because they are triggered at static pressure set points and are therefore not easily adjustable. Mechanical PRVs are also prone to wear with repeated use; however, malfunctions can be difficult to identify without physical inspection, making them difficult to maintain. Also, mechanical PRVs can suffer from so-called "dead bands" whereby the PRV gradually opens as the pressure increases against its spring, causing a leak of gases and / or fluid, which can continue to increase in severity, until the threshold pressure is reached. Mechanical PRVs are also prone to malfunction due to hysteresis, e.g., wherein the valve closes at a lower pressure than it opens, causing the valve to remain open (leaking) if the pressure does not drop below the required closing pressure, even when the pressure is below the opening / threshold pressure. As such, mechanical PRVs are not well adapted for different use cases, such as for use with different vehicle or cylinder types, and / or use in different temperature environments.

[0018] Aspects of the disclosed technology address the limitations of mechanical PRVs by providing a pressure management system in which pressure release is controlled by programmable electronic controller / s, as discussed in further detail with respect to FIG. 3A.

[0019] FIG. 3A illustrates an example pressure management system 300 that includes a pipe infrastructure 301 for which pressure is monitored and controlled by electronic controller 302, which can be configured to store one or more setpoints (predetermined pressure thresholds) in a failsafe memory. In pressure management system 300, controller 302 is configured to actuate primary valve 304, e.g., in response to pressure information received from pressure sensor 306 and / or information received from one or more other sensors, such as Internet of Things (IoT) sensor 310. As used herein, actuation can refer to the changing of a valve state, e.g., from open to close, or from closed to open, irrespective of whether the valve state change is caused by the affirmative application of force or power. For example, a normally open valve may be actuated via the removal of power or pressure, and a closed valve may be opened through the application of pneumatic force, electrical power, or another means of physical interaction (e.g., electromagnetic). Communication between controller 302, valve 304, control valve 305, or check valve 308, and one or more of pressure sensor 306 and / or IoT sensor 310 may be performed to monitor, regulate, and test pressure management system 300, as discussed in further detail below. Depending on the desired implementation, communication between controllers (e.g., controller 302), valves (304, 305, 308), and sensors (306, 310) may be facilitated using a wired, wireless and / or pneumatic communication path, such as communication path 303.

[0020] For pressure regulation in pipe 301, actuation of primary valve 304 can be performed using valve control 305, which can include a pneumatic control system. However, controller 302 may be configured to actuate primary valve 304 using other means, such as by using an electrical or electromagnetic actuator. In the illustrated configuration, primary valve 304 separates pipe 301 from vent 307, which enables release of fluids (such as gas) thereby reducing the internal pressure of pipe 301. As such, actuation of primary valve 304 by controller 302 can be used to reduce (or increase) pressure in pipe 301. In some approaches, primary valve 304 may be normally open, such that primary valve 304 is closed through active control by controller 302, and automatically opened in the event of power loss, or the loss of compressed air, to controller 302. In other approaches, primary valve 304 may be normally closed, such that primary valve 304 is opened through active control by controller 302, and automatically closed in the event of power loss, or the loss of compressed air.

[0021] To prevent backflow into pipe 301 when primary valve 304 is opened (e.g., either due to a detected high-pressure condition or power loss to controller 302), a check valve 308 is disposed between primary valve 304 and pipe 301. Depending on the desired implementation, check valve 308 may be optional, and may not be needed in some configurations. Check valve 308 can be configured to maintain a low-pressure seal (e.g., 1 - 5 bar above atmospheric pressure) in order to prevent ingress and contamination into pipe 301 via vent 307. It is understood that other default values for the low-pressure seal may be used, without departing from the scope of the disclosed technology.

[0022] More generally, controller 302 can be programmed to actuate primary valve 304 upon the detection of one or more pre-conditions, such as a detected pressure in pipe 301 exceeding a predetermined threshold value (also: predetermined pressure threshold). For example, controller 302 may be programmed to open primary valve 304 if a pressure in pipe 301 reaches, or exceeds, 500 bar, 800 bar, or 1000 bar, etc. It is understood that virtually any predetermined pressure threshold may be used, without departing from the scope of the disclosed technology. Additionally, controller 302 may be programmed to perform valve management operations based on multiple pressure set points or thresholds, including but not limited to a low-low (LL) setpoint (or Threshold 1), a low (L) setpoint (or Threshold 2), a high (H) setpoint (or Threshold 3), and a high-high (HH) setpoint (or Threshold 4), etc., as discussed in further detail with respect to FIG. 3B, below.

[0023] Pressure information collected by pressure sensor 306 may be provided to controller 302 and if the measured pressure meets or exceeds the predetermined pressure threshold value (or predetermined threshold), then controller 302 can open primary valve 304 to release pressure from pipe 301 via vent 307. In some implementations, one or more valves (e.g., primary valve 304) may include a standalone pressure sensor (or pressure switch) that is configured to automatically control valve actuation in response to the detection of a predetermined pressure condition.

[0024] Depending on the desired setup, pressure sensor 306 may be configured to transmit pressure information to controller 302 on a periodic basis, or at a time when certain pressure changes are detected. For example, pressure sensor 306 may be configured to transmit pressure information to controller 302 at a regular cadence (e.g., 1 / min, 1 / second, or 10 / second), or only at times when pressure changes are detected at pressure sensor 306. In some aspects, a communication cadence of pressure sensor 306 and / or other sensors configured to communicate with controller 302 (e.g., IoT sensor 310) may be updated by a remote management system (not illustrated). In some instances, received sensor data may be filtered to eliminate noisy measurements, or short-term outliers in the measured values. For example, debouncing techniques, or moving window averages may be used to temporally smooth received sensor data values.

[0025] Sensor data may also be used to make inferences about future states of pressure management system 300 or to infer the occurrence of future events. For example, rapidly rising pressure values may be used to estimate that pressure in pipe 301 is likely to overshoot acceptable pressure levels (e.g., the predetermined threshold). In such instances, anticipatory responses may be implemented, for example, to lower rapidly rising pressure in pipe 301 by opening valve 304. In other aspects, notifications may be automatically transmitted to an operator to indicate a need for system intervention.

[0026] Controller 302 may be capable of being deactivated during testing of system (e.g., filling station 100, 125). In doing so, controller 302 may receive a signal based on an indication from a user via an input device that the system is undergoing testing. In some embodiments, controller 302 may automatically deactivate itself, e.g., based on a testing schedule, resulting in the normally open primary valve 304 being opened during testing. In other embodiments, when controller 302 receives the signal indicating that the system is undergoing testing, primary valve 304 can be set to a closed state, with a threshold for venting that is associated with testing.

[0027] The actuation of primary valve 304 can be based on other types of information received by controller 302, such as various types of sensor information received from one or more IoT sensors, such as IoT sensor 310. Operationally, IoT sensor 310 may include any of a variety of sensor types and may be configured to identify any of a variety of conditions. For example, IoT sensor 310 may include a temperature sensor, an ambient pressure sensor, a fire sensor, and / or a density meter etc. As such, IoT sensor 310, alone or in conjunction with other sensors, can be configured to measure ambient pressure information, detect fires, and / or measure density of fluid inside pipe 301.

[0028] Additionally, one or more of the valves (304, 308) may have one or more sensors that detect the corresponding valve state. For example, primary valve 304 may have one or more sensors that detect the valve state (e.g., open or closed). This open / close information may be provided to, or retrieved by, controller 302, for example help determine when state changes are needed and / or to track duty-cycles of primary valve 304 for predictive maintenance purposes. The predictive maintenance may also be based on monitoring of system runtime. In some instances, primary valve 304 may have a thermal pressure relief device (TPRD), or another safety device, that is configured to open (vent) pipe 301 upon the detection of an emergency event, such as a fire. The logic for how controller 302 actuates primary valve 304 in response to combinations of received sensor information, including but not limited to pipe pressure, ambient pressure, temperature, and / of fluid density, etc., can be stored in a memory of controller 302, which may be remotely updated, such as by a filling or distribution system, depending on the desired implementation. For example, various sensor values or parameters may be stored in a lookup table of a local memory device of controller 302 and referenced to determine if (or when) primary valve 304 is to be actuated. In some instances, the various sensor values and / or parameters may be stored in a lookup table located in a failsafe memory, for example, that is access controlled for regulatory review or audit.

[0029] A record of venting events and / or collected sensor information may be stored in memory (e.g., local memory or cloud memory), for later review and analysis. The record of venting events may include the detected sensor data (e.g., pressure data, temperature data, valve position data), event timestamps, and the relevant triggering thresholds used to initiate venting. Stored event information and timestamps can be used to identify the cause of various malfunctions, or to predict the need for further maintenance. For example, based on the number of venting events, the system may provide a notification to a user regarding preventative maintenance of associated parts, such as the primary valve 304, the valve control 305, and relevant sensors. In some approaches, detected events (e.g., valve actuation events, or detected changes in sensor data, etc.) may be communicated to a human operator in real time (or near real time), for immediate action. For example, service technicians may be dispatched upon the detection of a venting event, a detected high-pressure event, and / or any of a variety of other pre-conditions identifiable from collected sensor data.

[0030] Remote control over valves, using one or more network connected controllers, can be used for testing various aspects of valve operation and performance, such as valve responsiveness. For example, valves may be opened / closed according to a schedule, or in response to remote commands, for the purpose of testing valve functionality, e.g., to see if they "stick" after periods inactivity, or to test responsiveness under certain conditions, e.g., to see if actuation lags. In some aspects, valve actuation may be used to corroborate the functions of various other sensors or components in pressure management system 300. For example, the functionality of one or more pressure sensors (306, 310) may be validated by opening or closing various valves to ensure that pressure levels decrease or increase accordingly. Further details regarding a process for controlling a pressure release valve are discussed with respect to FIGs. 4A and 4B.

[0031] FIG. 3B illustrates an example pressure management system 350, similar to pressure management system 300, discussed above, but that additionally includes a secondary valve 312, for facilitating management and filling operations for cylinder 314. Additionally, in pressure management system 350, check valve 308 is optional, and in some aspects, may not be used. As illustrated, cylinder 314 can be coupled to pipe 301 via secondary valve 312. Similar to primary valve 304, secondary valve 312 can be actuated by controller 302, for example to control the ingress / egress of fluids (e.g., gas) from cylinder 314. In some implementations, secondary valve 312 can be closed to prevent pressure loss in cylinder 314, as discussed in further detail below.

[0032] In operation, the open / close status of secondary valve 312 and / or primary valve 304 can depend on one or more thresholds, and / or can be based on sensor information received by one or more of IoT sensor 310, pressure sensor 306 and / or one or more valve-integrated open / close sensors, etc. For example, electronic controller 302 can be configured to store multiple threshold pressure values that can be used to determine open / close conditions for primary valve 304 and / or secondary valve 312, including but not limited to a first threshold value (e.g., Threshold 1), a second threshold value (e.g., Threshold 2), a third threshold value (e.g., Threshold 3) and / or a fourth threshold value (e.g., Threshold 4).

[0033] In some implementations, the first threshold value can define a low pressure setpoint, below which, secondary valve 312 can be closed, for example to protect cylinder 314 from depressurizing, which can result in damage to various components, such as the liner and / or composite reinforcement layer. The second threshold value can be greater (or higher) than the first threshold value. If a detected pressure in pipe 301 is less than the second threshold value, but greater than the first threshold value, then low-pressure warnings (or notifications) may be generated. For example, notifications may be generated directly by controller 302, and / or the pressure information may be communicated to one or more remote systems, and the notifications may be remotely generated.

[0034] A third threshold value may be used to define a pressure greater than the second threshold value. If the pressure measured in pipe 301 is greater than the second threshold value, but less than the third threshold value, system 350 may be in a normal or optimal operating mode, and no action is taken.

[0035] A fourth threshold value may be used to define a high-pressure threshold that is greater than the third threshold value, and above which primary valve 304 can be opened, e.g., to reduce the pressure in pipe 301, as discussed above. In some implementations, secondary valve 312 may also be closed, for example, to prevent backflow into the cylinder in instances where a check valve (e.g., check valve 308) is not used. For pressure measurements above the fourth threshold value, notifications / warnings may also be generated, e.g., to alert of the high-pressure condition of management system 350. Further details regarding embodiments in which multiple pressure threshold levels are used to determine actuation for two or more valves are provided in further detail with respect to FIG. 4C, below.

[0036] FIG. 4A is a flowchart illustrating an example process 400 for managing pressure release using an electronically controlled pressure release valve, such as a primary valve 304 managed by electronic controller 302, discussed above. Process 400 begins at step 402 when pressure measurements (e.g., pressure measurement information) are received or retrieved by a controller, such as an electronic controller (or PLC) configured to control a pressure release valve, such as primary valve 302 discussed above with respect to FIGs. 3A and 3B. Received pressure information may indicate a pressure in a pipe of a gas delivery infrastructure (e.g., pipe 301), as discussed above. Additionally, pressure information may be received by the controller via a wired or wireless communication path.

[0037] Depending on the desired implementation, different (or additional) types of sensor information may be received by the controller. For example, pressure information indicating pressure readings at different locations in the pipe infrastructure and / or indicating ambient pressure readings may be received. In other approaches, various other types of sensor information may be received, including but not limited to one or more of: temperature information (indicating internal and / or ambient temperatures), density measurement information (indicating a density of a fluid or gas in a pipe infrastructure), and / or valve state information (indicating the open / close status of one or more valves), etc.

[0038] At step 404, it is determined, at the controller, whether the received pressure information indicates that the measured pressure is below (or equal to) the valve threshold (setpoint). The pressure threshold (or setpoint) can be used to specify a pressure threshold above which pressure release is initiated. In some aspects, measured pressures above a predetermined setpoint value can trigger pressure release, as discussed in further detail with respect to FIG. 4B, below. In some instances, the controller setpoint (predetermined threshold) may correspond with a pressure value that is based on a safety regulation and / or based on operational parameters of equipment, such as cylinders or vehicles, involved in a gas filling or distribution process.

[0039] To determine whether the requisite pre-conditions have been met, electronic controller 302 may access a lookup table of threshold values for reference / comparison. In some approaches, the pressure threshold may be referenced based on an identification of the fluid contained within system (e.g., filling station 100, 125) and traveling through pipe 301. In some embodiments, the identification of the fluid is provided to electronic controller 302 via an input device by a user. Alternatively, fluid identification may be performed automatically e.g., using one or more sensors in the system (e.g., filling station 100, 125) that are communicatively coupled to electronic controller 302. In some embodiments, the identification of the fluid is automatically communicated to the system (e.g., filling station 100, 125) by a communications device or a filling device used to fill the system with fluid.

[0040] For example, a mobile filling station 125 may dispense a first fluid having a first associated pressure threshold. Upon emptying of the first fluid after dispensing to other storage containers, the mobile filling station 125 may be filled with a second fluid having a second associated pressure threshold. As described herein, an identification of the second fluid may be communicated to the electronic controller 302 by a user via an input device, automatically detected by a sensor of the mobile filling station 125 as the mobile filling station 125 is filled with the second fluid or communicated to the mobile filling station 125 by the filling device used to fill the mobile filling station 125 with the second fluid. In this way, the mobile filling station 125 can dynamically accommodate the safety requirements of multiple different fluids without having to change hardware components (e.g., mechanical release valve 202).

[0041] If at step 404 it is determined that the setpoint has not been triggered, e.g., that the received pressure measurement is below the threshold, then process 400 reverts to step 402. However, if at step 404 it is determined that the setpoint has been triggered, e.g., that the measured pressure is greater than the predetermined pressure threshold / setpoint, sufficient to meet the triggering criterion, then process 400 proceeds to step 406 in which a valve is opened, e.g., to release pressure from within the pipe, thereby reducing the pressure. As discussed above, opening the valve can release gas / fluids from inside of a pipe into the atmosphere e.g., via a vent coupled to the valve. The valve may be a normally open valve such that valve closure must be actively maintained by a controller, in which case, power loss to the controller, or loss of compressed air, can cause the valve to automatically open. In other configurations, the valve may be normally closed, in which case, power loss to the controller can cause the valve to automatically open.

[0042] At step 408, the controller can continue to receive (or retrieve) subsequent pressure measurement information from one or more pressure sensors (e.g., a second pressure measurement, or a third pressure measurement, etc.). For example, the controller may receive a subsequent pressure measurement that represents a pressure inside of a pipe at some time after the PRV has been opened (406). As discussed above, additional pressure measurements and / or other types of sensor data may be also (or alternatively) be received, without departing from the scope of the disclosed technology.

[0043] At step 410, it is determined whether the subsequently received pressure information (408) indicates that the pressure setpoint is still triggered, i.e., if the measured pressure is still above the setpoint, or of the pressure has been lowered to acceptable levels. Depending on the desired implementation, a pressure measurement that is below the setpoint / threshold can indicate that a pressure in the pipe has been reduced to an acceptable level, i.e., that the setpoint is no longer triggered. If at step 410 it is determined that the setpoint is still triggered, then process 400 can revert to step 410, the valve can remain open, and pressure monitoring can continue. Alternatively, if it is determined that the pressure has been adequately reduced below the predetermined threshold (e.g., that the setpoint is no longer triggered), process 400 can advance to step 412 and the valve can be closed.

[0044] FIG. 4B is a flowchart illustrating an example process for managing pressure in which pressure is kept above a predetermined threshold. Process 450 begins at step 452 when pressure measurements (e.g., pressure measurement information) are received by a controller, such as an electronic controller (or PLC) configured to control a PRV, such as primary valve 302 discussed above with respect to FIGs. 3A and 3B. Received pressure information may indicate a pressure in a pipe of a gas delivery infrastructure (e.g., pipe 301). As discussed above, pressure information may be received by the controller via a wired or wireless communication path.

[0045] Depending on the desired implementation, different (or additional) types of sensor information may be received by the controller. For example, pressure information indicating pressure readings at different locations in the pipe infrastructure and / or indicating ambient pressure readings may be received. In other approaches, various other types of sensor information may be received, including but not limited to one or more of: temperature information (indicating internal and / or ambient temperatures), density measurement information (indicating a density or viscosity of a fluid or gas in a pipe infrastructure), and / or valve state information (indicating the open / close status of one or more valves), etc.

[0046] At step 454, it is determined whether the received pressure information indicates that the measured pressure is below (or equal to) the valve threshold (setpoint). The pressure threshold (or setpoint) can be used to specify a pressure threshold below which valve closure is initiated. The controller setpoint (predetermined threshold) may correspond with a pressure value that is based on a safety regulation and / or based on operational parameters of equipment, such as cylinders or vehicles, involved in a gas filling process.

[0047] To determine whether the requisite pre-conditions have been met, electronic controller 302 may access a lookup table of threshold values for reference / comparison. In some approaches, the pressure threshold may be referenced based on an identification of the fluid contained within system (e.g., filling station 100, 125) and traveling through pipe 301. In some embodiments, the identification of the fluid is provided to electronic controller 302 via an input device by a user. Alternatively, fluid identification may be performed automatically e.g., using one or more sensors in the system (e.g., filling station 100, 125) that are communicatively coupled to electronic controller 302. In some embodiments, the identification of the fluid is automatically communicated to the system (e.g., filling station 100, 125) by a communications device or a filling device used to fill the system with fluid.

[0048] For example, a mobile filling station 125 may dispense a first fluid having a first associated pressure threshold. Upon emptying of the first fluid after dispensing it to other storage containers, the mobile filling station 125 may be filled with a second fluid having a second associated pressure threshold. As described herein, an identification of the second fluid may be communicated to the electronic controller 302 by a user via an input device, automatically detected by a sensor of the mobile filling station 125 as the mobile filling station 125 is filled with the second fluid or communicated to the mobile filling station 125 by the filling device used to fill the mobile filling station 125 with the second fluid. In this way, the mobile filling station 125 can dynamically accommodate the safety requirements of multiple different fluids without having to change hardware components (e.g., mechanical release valve 202).

[0049] If at step 454 it is determined that the setpoint has not been triggered, e.g., that the received pressure measurement remains above the threshold, then process 450 reverts to step 452. However, if at step 454 it is determined that the setpoint has been triggered, e.g., that the measured pressure is below than the predetermined pressure threshold / setpoint, sufficient to meet the triggering criterion, then process 450 proceeds to step 456 in which a valve is closed, e.g., to prevent the release of pressure from within the pipe, thereby increasing the pressure. Closing the valve can prevent the release of gas / fluids from inside of a pipe. In such setups, the valve may be a normally closed valve such that valve opening must be actively performed by a controller, in which case, power loss to the controller can cause the valve to automatically close.

[0050] At step 458, the controller can continue to receive (or retrieve) subsequent pressure measurement information from one or more pressure sensors (e.g., a second pressure measurement, or a third pressure measurement, etc.). For example, the controller may receive a subsequent pressure measurement that represents a pressure inside of a pipe at some time after the PRV has been closed (456). Additional pressure measurements and / or other types of sensor data may be also (or alternatively) be received, without departing from the scope of the disclosed technology.

[0051] At step 460, it is determined whether the subsequently received pressure information (408) indicates that the pressure setpoint is still triggered. Depending on the desired implementation, a pressure measurement that is below the setpoint can indicate that a pressure in the pipe has not yet returned to an acceptably high level. Thus, if at step 460 it is determined that the setpoint is still triggered, then process 450 can revert to step 456, and the valve can remain closed, for example, to continue the buildup of pressure in the pipe. Alternatively, if it is determined that the pressure has been adequately raised above the predetermined threshold (e.g., that the setpoint is not still triggered), process 450 can advance to step 452 and the valve can be opened.

[0052] It is understood that valve actuation can be controlled based on other types of sensor information, including but not limited to information regarding: temperature, ambient temperature, ambient pressure, fluid density, fluid viscosity, valve state, etc. As such, the setpoint triggering determinations (404, 410) can additionally (or alternatively) be based on other types of sensor information, without departing from the scope of the disclosed technology.

[0053] FIG. 4C conceptually illustrates a multitude of pressure threshold levels 480 e.g., Threshold 1 (LL), Threshold 2 (L), Threshold 3 (H), and Threshold 4 (HH), for operating a pressure management system. Threshold levels 480 define various operational conditions of a pressure management system, such as management system 350, discussed above. It is understood that a greater (or fewer) number of threshold levels may be used, without departing from the scope of the disclosed technology.

[0054] As discussed above with respect to FIG. 3B, if a measured pressure in the management system is below a first threshold (e.g., Threshold 1), then the system may be considered to be in an extreme low pressure state (LL), and the management system can respond by generating one or more notifications or warnings regarding the low-pressure condition, and / or closing a secondary valve (e.g., valve 312) to avoid depressurization of a connected cylinder or tank (482). Closing of cylinder valves in low pressure scenarios can help to protect various cylinder components, such as liners and / or reinforcement layers, etc.

[0055] If the measured pressure is greater than Threshold 1, but less than Threshold 2, then the system can be considered to be in a low pressure state (L). In this state, warnings / notifications may be generated, e.g., to warn of the low-pressure condition (484). As discussed above, warnings or alerts may be communicated off-device, for example, to communicate state information about the management system to specific devices and / or individuals.

[0056] If the measured pressure is greater than Threshold 2, but less than Threshold 3, the management system may be considered to be in an optimal or steady-state operating region (486), in which case no action is needed. In this state, the pressure management system can continue with normal operations, and no alerts / warnings are generated, and no actions are taken to alter valve states.

[0057] If the measured pressure is greater than Threshold 3, but less than Threshold 4, the management system may be considered to be in a high-pressure state (H). In such cases, warnings / notifications may be generated, e.g., to warn of the high pressure condition (488).

[0058] If the measured pressure is greater than Threshold 4, the management system may be considered to be in a very-high pressure (HH) state. In such cases, a primary valve (e.g., primary valve 304) may be opened to reduce pressure in one or more pipes of the management system, as discussed above (490). In some instances, cylinder-valves (e.g., secondary valve 312) may also be closed, for example, to prevent backflow into the cylinder in implementations where a check valve (e.g., check valve 308) is not used.

[0059] FIG. 5 illustrates a method 500 for managing pressure using an electronically controlled and monitored PRV. At step 502, the method 500 includes storing a pressure threshold value on an electronic controller, wherein the electronic controller is configured to actuate a primary valve, and wherein the primary valve controls fluidic communication between a pipe and a vent. The pressure threshold value can be used to indicate a maximum amount of pressure that can be observed / measured before pressure release should be initiated, as such the pressure threshold value can function as a predetermined threshold (or predetermined pressure threshold) for triggering pressure release. The pressure threshold value may be, or may be based on, regulation and / or equipment specifications. Additionally, the pressure threshold value may be based on or determined from other types of information, including but not limited to sensor information received from one or more network connected sensors (e.g., IoT sensors) in a vicinity of a pressure management system. By way of example, the pressure threshold value may be set based on an ambient temperature, a pipe pressure, and / or a temperature around a pressure management system that includes an electronic controller coupled to a pressure release valve (e.g., a primary valve) to release pressure from a piping infrastructure.

[0060] At step 504, method 500 includes receiving pressure information from a pressure sensor, the pressure information representing a pressure in the pipe. In some aspects, the pressure sensor may be collocated or integrated with the controller receiving the pressure information. In other aspects, the controller and pressure sensor may be disparate, in which case communication may occur via a wired or wireless communication means. As discussed above, the transmission of pressure information to the controller may also be based on certain programmable pre-conditions of the pressure sensor. For example, pressure reading information may be communicated at regular intervals, or may be communicated in response to detected pressure changes, etc.

[0061] Additional or other types of sensor information may also be communicated to the controller. For example, pressure measurement information from one or more additional pressure sensors may be provided, for example, to provide additional information about pressure conditions at various location in a pipe infrastructure and / or to provide ambient pressure data. As discussed above, sensor information of other types may also be used. For example, the controller may be configured to make valve actuation decisions using temperature information received from one or more temperature sensors and / or density information received from one or more density sensors, and the like. In some configurations, the controller may also receive state information directly from one or more valves (such as the primary valve) that indicate open / close states of the respective valve. Valve state information may be used to validate operational states of the pressure management system and in some instances may be used for predictive maintenance, e.g., to predict when the primary valve needs maintenance or replacement.

[0062] At step 506, method 500 includes actuating the primary valve via the electronic controller, if the pressure in the pipe is greater than or equal to a predetermined threshold. As discussed above, the valve may be configured to be normally open such that closed-valve states are actively maintained. In such configurations, power loss to the controller can cause the valve to automatically open helping to prevent over-pressure conditions in power-limited or emergency scenarios.

[0063] At step 508, method 500 includes maintaining a closure of the primary valve, if the pressure in the pipe is lower than a predetermined threshold.

[0064] FIG. 6 illustrates an example processor-based system 600 that can be used to implement some or all aspects of the subject technology. For example, processor-based system 600 can be used to implement a controller (PLC), such as electronic controller 302, and / or any component thereof.

[0065] The processor-based system 600 can include a connection 605 used by components of the system to communicate with each other. The connection 605 can be or include a physical connection via a bus, or a direct connection into processor 610, such as in a chipset architecture. Connection 605 can also be a virtual connection, networked connection, or logical connection.

[0066] The example system 600 includes at least one processing unit (CPU or processor) 610 and connection 605 that couples various system components including system memory 615, such as read-only memory (ROM) 520 and random-access memory (RAM) 625 to processor 610. Computing system 600 can include a cache of high-speed memory 612 connected directly with, in close proximity to, and / or integrated as part of processor 610.

[0067] Processor 610 can include any general-purpose processor and a hardware service or software service, such as services 632, 634, and 636 stored in storage device 630, configured to control processor 610 as well as a special-purpose processor where software instructions are incorporated into the actual processor design. Processor 610 may essentially be a completely self-contained computing system, containing multiple cores or processors, a bus, memory controller, cache, etc. A multi-core processor may be symmetric or asymmetric.

[0068] To enable user interaction, computing system 600 can include an input device 645, which can represent any number of input mechanisms, such as a microphone for speech, a touch-sensitive screen for gesture or graphical input, keyboard, mouse, motion input, speech, etc. Computing system 600 can also include output device 635, which can be one or more of a number of output mechanisms known to those of skill in the art. In some instances, multimodal systems can enable a user to provide multiple types of input / output to communicate with computing system 600. Computing system 600 can include communications interface 640, which can generally govern and manage the user input and system output.

[0069] The communication interface may perform or facilitate receipt and / or transmission wired or wireless communications via wired and / or wireless transceivers, including those making use of an audio jack / plug, a microphone jack / plug, a universal serial bus (USB) port / plug, an Apple ®< Lightning ®< port / plug, an Ethernet port / plug, a fiber optic port / plug, a proprietary wired port / plug, a BLUETOOTH ®< wireless signal transfer, a BLUETOOTH ®< low energy (BLE) wireless signal transfer, an IBEACON ®< wireless signal transfer, a radio-frequency identification (RFID) wireless signal transfer, near-field communications (NFC) wireless signal transfer, dedicated short range communication (DSRC) wireless signal transfer, 502.11 Wi-Fi wireless signal transfer, wireless local area network (WLAN) signal transfer, Visible Light Communication (VLC), Worldwide Interoperability for Microwave Access (WiMAX), Infrared (IR) communication wireless signal transfer, Public Switched Telephone Network (PSTN) signal transfer, Integrated Services Digital Network (ISDN) signal transfer, 3G / 4G / 5G / LTE cellular data network wireless signal transfer, ad-hoc network signal transfer, radio wave signal transfer, microwave signal transfer, infrared signal transfer, visible light signal transfer, ultraviolet light signal transfer, wireless signal transfer along the electromagnetic spectrum, or some combination thereof.

[0070] Communications interface 640 may also include one or more Global Navigation Satellite System (GNSS) receivers or transceivers that are used to determine a location of the computing system 600 based on receipt of one or more signals from one or more satellites associated with one or more GNSS systems. GNSS systems include, but are not limited to, the US-based Global Positioning System (GPS), the Russia-based Global Navigation Satellite System (GLONASS), the China-based BeiDou Navigation Satellite System (BDS), and the Europe-based Galileo GNSS. There is no restriction on operating on any particular hardware arrangement, and therefore the basic features here may easily be substituted for improved hardware or firmware arrangements as they are developed.

[0071] Storage device 630 can be a non-volatile and / or non-transitory computer-readable memory device and can be a hard disk or other types of computer readable media which can store data that are accessible by a computer, such as magnetic cassettes, flash memory cards, solid state memory devices, digital versatile disks, cartridges, a floppy disk, a flexible disk, a hard disk, magnetic tape, a magnetic strip / stripe, any other magnetic storage medium, flash memory, memristor memory, any other solid-state memory, a compact disc read only memory (CD-ROM) optical disc, a rewritable compact disc (CD) optical disc, digital video disk (DVD) optical disc, a blu-ray disc (BD) optical disc, a holographic optical disk, another optical medium, a secure digital (SD) card, a micro secure digital (microSD) card, a Memory Stick ®< card, a smartcard chip, a EMV chip, a subscriber identity module (SIM) card, a mini / micro / nano / pico SIM card, another integrated circuit (IC) chip / card, random access memory (RAM), static RAM (SRAM), dynamic RAM (DRAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash EPROM (FLASHEPROM), cache memory (L1 / L2 / L3 / L4 / L9 / L#), resistive random-access memory (RRAM / ReRAM), phase change memory (PCM), spin transfer torque RAM (STT-RAM), another memory chip or cartridge, and / or a combination thereof.

[0072] Storage device 630 can include software services, servers, services, etc., that when the code that defines such software is executed by the processor 610, causes the system to perform a function. In some examples, a hardware service that performs a particular function can include the software component stored in a computer-readable medium in connection with the necessary hardware components, such as processor 610, connection 605, output device 635, etc., to carry out the function.

[0073] Aspects within the scope of the present disclosure may also include tangible and / or non-transitory computer-readable storage media or devices for carrying or having computer-executable instructions or data structures stored thereon. Such tangible computer-readable storage devices can be any available device that can be accessed by a general purpose or special purpose computer, including the functional design of any special purpose processor as described above. By way of example, and not limitation, such tangible computer-readable devices can include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other device which can be used to carry or store desired program code in the form of computer-executable instructions, data structures, or processor chip design. When information or instructions are provided via a network or another communications connection (either hardwired, wireless, or combination thereof) to a computer, the computer properly views the connection as a computer-readable medium. Thus, any such connection is properly termed a computer-readable medium. Combinations of the above should also be included within the scope of the computer-readable storage devices.

[0074] Computer-executable instructions include, for example, instructions and data which cause a general-purpose computer, special-purpose computer, or special-purpose processing device to perform a certain function or group of functions. By way of example, computer-executable instructions can be used to implement perception system functionality for determining when sensor cleaning operations are needed or should begin. Computer-executable instructions can also include program modules that are executed by computers in stand-alone or network environments. Generally, program modules include routines, programs, components, data structures, objects, and the functions inherent in the design of special-purpose processors, etc. that perform tasks or implement abstract data types. Computer-executable instructions, associated data structures, and program modules represent examples of the program code means for executing steps of the methods disclosed herein. The particular sequence of such executable instructions or associated data structures represents examples of corresponding acts for implementing the functions described in such steps.

[0075] Other examples of the disclosure may be practiced in network computing environments with many types of computer system configurations, including personal computers, hand-held devices, multi-processor systems, microprocessor-based or programmable consumer electronics, network PCs, minicomputers, mainframe computers, and the like. Aspects of the disclosure may also be practiced in distributed computing environments where tasks are performed by local and remote processing devices that are linked (either by hardwired links, wireless links, or by a combination thereof) through a communications network. In a distributed computing environment, program modules can be located in both local and remote memory storage devices.

[0076] The various examples described above are provided by way of illustration only and should not be construed to limit the scope of the disclosure. For example, the principles herein apply equally to optimization as well as general improvements. Various modifications and changes may be made to the principles described herein without following the example aspects and applications illustrated and described herein, and without departing from the spirit and scope of the disclosure.

[0077] Claim language or other language in the disclosure reciting "at least one of" a set and / or "one or more" of a set indicates that one member of the set or multiple members of the set (in any combination) satisfy the claim. For example, claim language reciting "at least one of A and B" or "at least one of A or B" means A, B, or A and B. In another example, claim language reciting "at least one of A, B, and C" or "at least one of A, B, or C" means A, B, C, or A and B, or A and C, or B and C, or A and B and C. The language "at least one of" a set and / or "one or more" of a set does not limit the set to the items listed in the set. For example, claim language reciting "at least one of A and B" or "at least one of A or B" can mean A, B, or A and B, and can additionally include items not listed in the set of A and B.

[0078] Illustrative examples of the disclosure include: Aspect 1. A pressure management system, comprising: an electronic controller; a pressure sensor coupled to the electronic controller and to a pipe, wherein the pressure sensor is configured to relay pressure information about the pipe to the electronic controller; and a primary valve coupled between a vent and the electronic controller; and a cylinder coupled to the pipe via a secondary valve, and wherein the electronic controller is configured to actuate the primary valve and / or the secondary based on pressure information received from the pressure sensor. Aspect 2. The pressure management system of Aspect 1, wherein the electronic controller is configured to receive open / close information from the primary valve and / or the secondary valve. Aspect 3. The pressure management system of any of Aspects 1 to 2, wherein the electronic controller is configured to actuate the primary valve and / or the secondary valve using a pneumatic actuator, an electric actuator, an electromagnetic actuator, or a combination thereof. Aspect 4. The pressure management system of any of Aspects 1 to 3, wherein the electronic controller is configured to: close the secondary valve, if the pressure information received from the pressure sensor indicates that a pressure in the pipe is below a first threshold value. Aspect 5. The pressure management system of any of Aspects 1 to 4, wherein the electronic controller is configured to: generate an alert, if the pressure information received from the pressure sensor indicates that a pressure in the pipe is above a first threshold value and below a second threshold value. Aspect 6. The pressure management system of any of Aspects 1 to 5, wherein the electronic controller is configured to: generate an alert, if the pressure information received from the pressure sensor indicates that a pressure in the pipe is above a third threshold value and below a fourth threshold value. Aspect 7. The pressure management system of any of Aspects 1 to 6, wherein the electronic controller is configured to: open the primary valve, if the pressure information received from the pressure sensor indicates that a pressure in the pipe is above a fourth threshold value. Aspect 8. The pressure management system of any of Aspects 1 to 7, further comprising: a density sensor communicatively coupled to the electronic controller, wherein the density sensor is configured to measure a density of fluid in the pipe. Aspect 9. The pressure management system of any of Aspects 1 to 8, further comprising: a check valve coupled between the primary valve and the pipe, wherein the check valve is configured to prevent a backflow from the vent into the pipe. Aspect 10. A method for managing pressure, comprising: storing a plurality of predetermined threshold values on an electronic controller, wherein the electronic controller is configured to actuate a primary valve and / or a secondary valve, and wherein the primary valve controls fluidic communication between a pipe and a vent, and the secondary valve controls fluidic communication between the pipe and a cylinder; receiving pressure information from a pressure sensor, the pressure information representing a pressure in the pipe; and actuating the primary valve and / or the secondary valve via the electronic controller, based on pressure information received from the pressure sensor. Aspect 11. The method of Aspect 10, wherein the primary valve and / or the secondary valve are actuated using a pneumatic actuator, an electric actuator, an electromagnetic actuator, or a combination thereof. Aspect 12. The method of any of Aspects 10 to 11, further comprising: closing the secondary valve, if the pressure information received from the pressure sensor indicates that a pressure in the pipe is below a first threshold value; and generating an alert if the pressure information indicates that the pressure in the pipe is above the first threshold value and below a second threshold value. Aspect 13. The method of any of Aspects 10 to 12, further comprising: generating an alert, if the pressure information received from the pressure sensor indicates that a pressure in the pipe is above a third threshold value and below a fourth threshold value. Aspect 14. The method of any of Aspects 10 to 13, further comprising: opening the primary valve, if the pressure information received from the pressure sensor indicates that a pressure in the pipe is above a fourth threshold value. Aspect 15. The method of any of Aspects 10 to 14, further comprising: communicatively coupling a density sensor to the electronic controller, wherein the density sensor is configured to measure a density of fluid in the pipe. Aspect 16. The method of any of Aspects 10 to 15, further comprising: disposing a check valve between the primary valve and the pipe, wherein the check valve is configured to prevent a backflow from the vent into the pipe. Aspect 17. The method of any of Aspects 10 to 16, further comprising: storing the plurality of predetermined thresholds in a lookup table on a local memory of the electronic controller. Aspect 18. The method of any of Aspects 10 to 17, further comprising: updating one or more of the plurality of predetermined thresholds using a wired or wireless network connection. Aspect 19. A non-transitory computer-readable medium having stored thereon instructions which, when executed by a controller, cause the controller to: store a plurality of predetermined threshold values on an electronic controller, wherein the electronic controller is configured to actuate a primary valve and / or a secondary valve, and wherein the primary valve controls fluidic communication between a pipe and a vent, and the secondary valve controls fluidic communication between the pipe and a cylinder; receive pressure information from a pressure sensor, the pressure information representing a pressure in the pipe; and actuate the primary valve and / or the secondary valve via the electronic controller, based on pressure information received from the pressure sensor. Aspect 20. The non-transitory computer-readable medium of Aspect 19, wherein the instructions are further configured to cause the controller to: receive open / close information from the primary valve and / or the secondary valve.

[0079] In particular, the invention relates to the following combinations of features, as are expressly defined in accordance with the sections

[00110] to

[00128] below:

[0080] A pressure management system, comprising: an electronic controller; a pressure sensor coupled to the electronic controller and to a pipe, wherein the pressure sensor is configured to relay pressure information about the pipe to the electronic controller; and a primary valve coupled between a vent and the electronic controller; and a cylinder coupled to the pipe via a secondary valve, and wherein the electronic controller is configured to actuate the primary valve and / or the secondary valve based on pressure information received from the pressure sensor.

[0081] The pressure management system of section

[00110] , wherein the electronic controller is configured to receive open / close information from the primary valve and / or the secondary valve.

[0082] The pressure management system of section

[00110] or

[00111] , wherein the electronic controller is configured to actuate the primary valve and / or the secondary valve using a pneumatic actuator, an electric actuator, an electromagnetic actuator, or a combination thereof.

[0083] The pressure management system of any of sections

[00110] to

[00112] , wherein the electronic controller is configured to: close the secondary valve, if the pressure information received from the pressure sensor indicates that a pressure in the pipe is below a first threshold value.

[0084] The pressure management system of any of sections

[00110] to

[00113] , wherein the electronic controller is configured to: generate an alert, if the pressure information received from the pressure sensor indicates that a pressure in the pipe is above a first threshold value and below a second threshold value.

[0085] The pressure management system of any of sections

[00110] to

[00114] , wherein the electronic controller is configured to: generate an alert, if the pressure information received from the pressure sensor indicates that a pressure in the pipe is above a third threshold value and below a fourth threshold value.

[0086] The pressure management system of any of sections

[00110] to

[00115] , wherein the electronic controller is configured to: open the primary valve, if the pressure information received from the pressure sensor indicates that a pressure in the pipe is above a fourth threshold value.

[0087] The pressure management system of any of sections

[00110] to

[00116] , further comprising: a density sensor communicatively coupled to the electronic controller, wherein the density sensor is configured to measure a density of fluid in the pipe.

[0088] The pressure management system of any of sections

[00110] to

[00117] , further comprising: a check valve coupled between the primary valve and the pipe, wherein the check valve is configured to prevent a backflow from the vent into the pipe.

[0089] A method for managing pressure, comprising: storing a plurality of predetermined threshold values on an electronic controller, wherein the electronic controller is configured to actuate a primary valve and / or a secondary valve, and wherein the primary valve controls fluidic communication between a pipe and a vent, and the secondary valve controls fluidic communication between the pipe and a cylinder; receiving pressure information from a pressure sensor, the pressure information representing a pressure in the pipe; and actuating the primary valve and / or the secondary valve via the electronic controller, based on pressure information received from the pressure sensor.

[0090] The method of section

[00119] , wherein the primary valve and / or the secondary valve are actuated using a pneumatic actuator, an electric actuator, an electromagnetic actuator, or a combination thereof.

[0091] The method of section

[00119] or

[00120] , further comprising: closing the secondary valve, if the pressure information received from the pressure sensor indicates that a pressure in the pipe is below a first threshold value; and generating an alert if the pressure information indicates that the pressure in the pipe is above the first threshold value and below a second threshold value.

[0092] The method of any of sections

[00119] to

[00121] , further comprising: generating an alert, if the pressure information received from the pressure sensor indicates that a pressure in the pipe is above a third threshold value and below a fourth threshold value.

[0093] The method of any of sections

[00119] to

[00122] , further comprising: opening the primary valve, if the pressure information received from the pressure sensor indicates that a pressure in the pipe is above a fourth threshold value.

[0094] The method of any of sections

[00119] to

[00123] , further comprising: communicatively coupling a density sensor to the electronic controller, wherein the density sensor is configured to measure a density of fluid in the pipe.

[0095] The method of any of sections

[00119] to

[00124] , further comprising: disposing a check valve between the primary valve and the pipe, wherein the check valve is configured to prevent a backflow from the vent into the pipe.

[0096] The method of any of sections

[00119] to

[00125] , further comprising: storing the plurality of predetermined thresholds in a lookup table on a local memory of the electronic controller.

[0097] The method of any of sections

[00119] to

[00126] , further comprising: updating one or more of the plurality of predetermined thresholds using a wired or wireless network connection.

[0098] A non-transitory computer-readable medium having stored thereon instructions which, when executed by a controller, cause the controller to: store a plurality of predetermined threshold values on an electronic controller, wherein the electronic controller is configured to actuate a primary valve and / or a secondary valve, and wherein the primary valve controls fluidic communication between a pipe and a vent, and the secondary valve controls fluidic communication between the pipe and a cylinder; receive pressure information from a pressure sensor, the pressure information representing a pressure in the pipe; and actuate the primary valve and / or the secondary valve via the electronic controller, based on pressure information received from the pressure sensor.

[0099] The non-transitory computer-readable medium of section

[00128] , wherein the instructions are further configured to cause the controller to: receive open / close information from the primary valve and / or the secondary valve.

Examples

Embodiment Construction

[0004]The detailed description set forth below is intended as a description of various configurations of the subject technology and is not intended to represent the only configurations in which the subject technology can be practiced. The appended drawings are incorporated herein and constitute a part of the detailed description. The detailed description includes specific details for the purpose of providing a more thorough understanding of the subject technology. However, it will be clear and apparent that the subject technology is not limited to the specific details set forth herein and may be practiced without these details. In some instances, structures and components are shown in block diagram form to avoid obscuring the concepts of the subject technology.

[0005]Pressure reducing valves (or pressure release valves) (PRVs) can be used in fluid dispensation systems to limit the maximum pressure at various locations in a network of piping, such as at critical junctions used for flu...

BACKGROUND1. Technical Field

[0001] The present disclosure relates generally to control systems for a gas delivery infrastructure and, in particular, to the use of programmable valve controllers for managing fluid exchange in a gas piping infrastructure.2. Introduction

[0002] Gas-powered vehicles have become an important or even integral part of transportation systems and economies around the world. The widespread use of gas-powered vehicles and other power-generation systems has created increasing demands for refueling systems, stations, and technologies used to fuel / refuel the gas-powered vehicles and other power-generation systems. Moreover, the increasing demands for refueling systems, stations, and technologies have fueled efforts to deploy better, safer, and more efficient refueling systems and stations, such as gas filling stations. However, the combustibility, volatility, flammability and other properties of typical gas fuel sources, such as hydrogen, create safety issues for refueling systems, stations, and procedures. Consequently, safety regulations, standards, and practices have emerged to address the various safety issues associated with refueling systems, stations, and procedures. Nevertheless, the safety regulations, standards, and practices, as well as the demands for better safer, and more efficient refueling systems and stations have created difficult challenges in deploying or updating refueling systems and stations, managing refueling systems and stations, and dispensing gas to gas-powered systems and vehicles.BRIEF DESCRIPTION OF THE DRAWINGS

[0003] The various advantages and features of the present technology will become apparent by reference to specific implementations illustrated in the appended drawings. A person of ordinary skill in the art will understand that these drawings only show some examples of the present technology and would not limit the scope of the present technology. Furthermore, the skilled artisan will appreciate the principles of the present technology as described and explained with additional specificity and detail through the use of the accompanying drawings in which: FIG. 1A illustrates an example gas filling station for a vehicle, according to some examples of the present disclosure; FIG. 1B illustrates an example of transportable gas filling station, according to some examples of the present disclosure; FIG. 2 illustrates an example of a mechanical release valve that can be used to reduce pressure in a gas pipeline infrastructure; FIG. 3A illustrates an example pressure management system, including an electronic controller for managing pressure release from piping infrastructure, according to some examples of the present disclosure; FIG. 3B illustrates an example pressure management system, including an electronic controller for managing pressure release and cylinder (tank) filling operations, according to some aspects of the present disclosure; FIG. 4A is a flowchart illustrating an example process for managing pressure release in which pressure is kept below a predetermined threshold, according to some examples of the present disclosure; FIG. 4B is a flowchart illustrating an example process for managing pressure release in which pressure is kept above a predetermined threshold, according to some examples of the present disclosure; FIG. 4C conceptually illustrates a multitude of pressure threshold levels for operating a pressure management system, according to some examples of the present disclosure; FIG. 5 illustrates a method for managing pressure using an electronically controlled PRV, according to some examples of the present disclosure; and FIG. 6 illustrates an example processor-based system architecture for implementing certain aspects of the present disclosure. DETAILED DESCRIPTION

[0004] The detailed description set forth below is intended as a description of various configurations of the subject technology and is not intended to represent the only configurations in which the subject technology can be practiced. The appended drawings are incorporated herein and constitute a part of the detailed description. The detailed description includes specific details for the purpose of providing a more thorough understanding of the subject technology. However, it will be clear and apparent that the subject technology is not limited to the specific details set forth herein and may be practiced without these details. In some instances, structures and components are shown in block diagram form to avoid obscuring the concepts of the subject technology.

[0005] Pressure reducing valves (or pressure release valves) (PRVs) can be used in fluid dispensation systems to limit the maximum pressure at various locations in a network of piping, such as at critical junctions used for fluid transfer or dispensation. PRVs are sometimes used in gas dispensation infrastructure, such as in the piping of gas transportation modules for refueling vehicles using pressurized fuel tanks (or "cylinders"). In such cases, PRVs can utilize mechanical release mechanisms that release pressure to the atmosphere when the pressure in the pipe exceeds a maximum set-point, which can depend on equipment parameters, safety protocols, and / or regulation, etc. However, mechanical release valves, such as springs, are limited in functionality because they are triggered at a static pressure set point that cannot be easily adjusted for operation at different pressure set-point levels. As such, mechanical PRVs are not well adapted for different use cases, such as for use with different vehicle or cylinder types, and / or use in different temperature environments. Additionally, mechanical PRVs are prone to wear with repeated use; however, malfunctions can be difficult to identify without physical inspection. For example, mechanical PRVs can suffer from so-called "dead bands" whereby the PRV gradually opens as the pressure increases against its spring, causing a leak of gases and / or fluid, which can continue to increase in severity, until the threshold pressure is reached. Mechanical PRVs are also prone to malfunction due to hysteresis, e.g., wherein the valve closes at a lower pressure than it opens, causing the valve to remain open (leaking) if the pressure does not drop below the required closing pressure, even when the pressure is below the opening / threshold pressure.

[0006] Aspects of the disclosed technology address the limitations of mechanical PRVs by providing a pressure management system in which pressure release is controlled by one or more programmable and updatable electronic controller / s. For example, a pressure management system can include an electronic controller, such as a programmable logic controller (PLC), that is coupled to a valve (e.g., a primary valve) that regulates pressure release from a network of pipes. In some configurations, the controller can actuate the primary valve using a pneumatic coupling. However, other types of communication between the controller and the primary valve, such as electrical, electromagnetic, or other types of couplings may be used, without departing from the scope of the disclosed technology. Pressure information can be received by (or retrieved by) the controller from one or more pressure sensors in the pipes. Received pressure information can be used by logic of the electronic controller to make decisions about when to actuate the primary valve. In some implementations, the primary valve may be configured to be normally open, such that if power to the controller is lost, or of the compressed air supply for the valve control fails, the primary valve automatically opens to reduce pressure to, or approximate to, an ambient atmospheric pressure.

[0007] Using a pressure management system that includes an electronic controller to manage valve operation provides several advantages, including the ability to dynamically update pressure management system thresholds based on equipment specifications, improving safety across a variety of vehicles, cylinders, and in a variety of operating conditions such as different temperature and ambient pressure conditions. The disclosed pressure management system also enables more intelligent operation through the collection and use of various types of sensor data that can be received from one or more wired or wireless sensors in the surrounding environment, including but not limited to Internet-of-Thing (IoT) sensors, temperature sensors, ambient temperature sensors, pressure sensors, ambient pressure sensors, actuation counters, state of charge sensors, and / or density sensors, etc. As used herein, IoT sensors can refer to sensors configured for wireless communication with one or more controllers and / or with one or more other sensors, without the need for connection to a public computer network, such as the Internet. Additionally, actuation counters can include sensors or other devices that are configured to count a number of times a valve has been actuated. Further details regarding the operation of the disclosed pressure management system are provided below.

[0008] FIG. 1A depicts an example gas filling station 100 for a vehicle 120, according to some examples of the present disclosure. Gas filling station 100 can be configured similar to, or substantially as, a gas station. For example, vehicle 120 can use gas filling station 100 to refuel, as shown in FIG. 1A. In this example, the gas filling station 100 includes gas dispenser 110 configured to dispense gas, such as hydrogen gas, to vehicles such as vehicle 120. Gas dispenser 110 can include a re-fueling hose 114 with a nozzle 112 configured to detachably connect to filling port 122 of vehicle 120. Filling port 122 can be connected to an internal fuel tank (not shown in FIG. 1A) of the vehicle 120. Thus, the gas from the gas filling station 100 can flow from the gas dispenser 110 to the re-fueling hose 114 and the nozzle 112 connected to the filling port 122 of the vehicle 120. Gas can travel from the nozzle 112 and the filling port 122 of the vehicle 120 to the internal fuel tank of vehicle 120 to refill the internal fuel tank of vehicle 120.

[0009] While the example gas filling station 100 is described with respect to vehicle 120 (e.g., a car), gas filling station 100 can be deployed for refueling any applicable vehicle or gas-fueled system / device such as, for example and without limitation, a movable platform, a truck, a commercial vehicle, an industrial vehicle, a passenger vehicle, an aircraft, an aerial vehicle, a train, a boat or ship, a lawnmower, a motorcycle, a motorized tool or device, a subway vehicle, a watercraft, a locomotive, farm equipment, a construction vehicle, and / or a warehouse vehicle, among others.

[0010] In some examples, the source of gas dispensed by the gas filling station 100 can be or include one or more tanks storing the gas. For example, in some cases involving hydrogen gas, the source of the hydrogen dispensed by gas filling station 100 can be or include one or more tanks holding the hydrogen at a lower pressure (e.g., around 100 bar) relative to a desired delivery pressure (e.g., 600-900 bar). In some examples, the source of the hydrogen can be or include a hydrogen generator providing hydrogen gas at near ambient pressure.

[0011] Depending on the desired implementation, gas filling station 125 can be configured as a mobile refueling station for hydrogen, (e.g., a Mobile Hydrogen Refueling Station (MHRS)), or for gas, (e.g., a multi-element gas container (MEGC)) or a mobile refueling unit, such as mobile gas filling station 125 illustrated in FIG. 1B. For example, the gas filling station can be configured as a transportable self-contained module or system suitable for re-fueling gas-powered systems (e.g., vehicles, etc.) at remote locations or as part of a temporary installation (e.g., a construction site, a port, an airport, etc.). In other examples, the gas filling station can be configured as a module of a larger installation, such as a re-fueling station for air vehicles installed on a ship.

[0012] FIG. 1B illustrates an example mobile gas filling station 125 (also referred to as multi-element gas containers (MEGCs) or mobile refueling units) for refueling vehicles (e.g., a truck, a bus, a rail-bound vehicle, etc.). In this example, mobile gas filling station 125 can include a detachable tank container 130 and a mobile refueler 140. In some cases, tank container 130 can be mounted on a chassis of a vehicle (not shown) used to transport tank container 130, such as a truck, which allows tank container 130 to be transportable, disconnected from the mobile refueler 140, and / or filled separately.

[0013] Tank container 130 (also referred to as a gas storage unit) can be configured to store any gas, such as hydrogen gas. The size of the tank container 130 can vary depending on the storage capacity desired. In some examples, tank container 130 can include a control unit 132 for monitoring and / or controlling the status of tank container 130.

[0014] In some aspects, the mobile refueler 140 (also referred to as a buffer tank or a buffer unit) can include a control panel 142 with a nozzle 144, a buffer storage unit (e.g., a pressure tank) (not shown), a hydrogen compressor (not shown), and / or any applicable control unit. In some examples, the mobile refueler 140 can include a hydrogen pre-cooling unit to facilitate rapid refueling.

[0015] Gas stored in the tanks of the mobile gas filling station 125 (e.g., the tank container 130, the mobile refueler 140) can be dispensed to vehicles (and / or any other systems or devices) from a nozzle, such as nozzle 144. Mobile gas filling station 125 can include a network of pipes between the nozzle and any of the tanks of the mobile gas filling station 125. In some examples, the mobile gas filling station 125 can include one or more process elements (e.g., operation and / or safety elements) along one or more pipe paths. For example, the mobile gas filling station 125 can include one or more pressure relief valves (PRVs) along a pipe path to allow gas to vent (e.g., to release gas to the atmosphere) as needed.

[0016] Moreover, the mobile gas filling station 125 (and the gas filling station 100 shown in FIG. 1A) can include operations elements (not shown) used to manage the gas in the tanks, control refueling operations, provide safety / failsafe mechanisms for safe containment and dispensing of fuel (e.g., hydrogen etc.), etc. For example, the mobile gas filling station 125 (and the gas filling station 100 shown in FIG. 1A) can include one or more PRVs, one or more actuators, one or more switches, one or more tamper detection devices, one or more transmitters and / or transceivers, one or more sensors, one or more cooling components, one or more safety devices (e.g., valves, etc.), one or more flow metering and / or control devices, one or more leak detection devices, one or more gas (e.g., hydrogen) flow measurement devices, one or more emergency shutdown systems, one or more gauges, one or more fire-suppression mechanisms, one or more gas distribution and pressure management systems, one or more computing components (e.g., controllers, processors, computers, etc.), one or more compressors, etc. Non-limiting examples of a sensor that can be included or implemented by a gas filling station can include a temperature sensor, a pressure sensor, a fire sensor, a gas sensor, a flame detector, a leakage sensor, a flow sensor, a valve position sensor (e.g., sensor to detect if a valve is open or closed), an impedance sensor, an accelerometer, a gyroscope, an inertial measurement unit (IMU), a motion sensor, a position sensor, an image / camera sensor, a nuclear magnetic resonance (NMR) detector / spectrometer, a location sensor, and / or any other sensor device.

[0017] FIG. 2 illustrates an example of a mechanical release valve 202 that can be used to reduce pressure in a gas pipeline infrastructure 204. Mechanical release valve 202 is located at a juncture of pipe infrastructure 204, e.g., at a juncture of pipe section 204A and pipe section 204B. Mechanical release valve 202 can include a spring-loaded release mechanism configured to release gas or fluids from pipe infrastructure 204 at a specifically determined pressure level. As discussed above, mechanical release valves, such release valve 202, are limited in functionality because they are triggered at static pressure set points and are therefore not easily adjustable. Mechanical PRVs are also prone to wear with repeated use; however, malfunctions can be difficult to identify without physical inspection, making them difficult to maintain. Also, mechanical PRVs can suffer from so-called "dead bands" whereby the PRV gradually opens as the pressure increases against its spring, causing a leak of gases and / or fluid, which can continue to increase in severity, until the threshold pressure is reached. Mechanical PRVs are also prone to malfunction due to hysteresis, e.g., wherein the valve closes at a lower pressure than it opens, causing the valve to remain open (leaking) if the pressure does not drop below the required closing pressure, even when the pressure is below the opening / threshold pressure. As such, mechanical PRVs are not well adapted for different use cases, such as for use with different vehicle or cylinder types, and / or use in different temperature environments.

[0018] Aspects of the disclosed technology address the limitations of mechanical PRVs by providing a pressure management system in which pressure release is controlled by programmable electronic controller / s, as discussed in further detail with respect to FIG. 3A.

[0019] FIG. 3A illustrates an example pressure management system 300 that includes a pipe infrastructure 301 for which pressure is monitored and controlled by electronic controller 302, which can be configured to store one or more setpoints (predetermined pressure thresholds) in a failsafe memory. In pressure management system 300, controller 302 is configured to actuate primary valve 304, e.g., in response to pressure information received from pressure sensor 306 and / or information received from one or more other sensors, such as Internet of Things (IoT) sensor 310. As used herein, actuation can refer to the changing of a valve state, e.g., from open to close, or from closed to open, irrespective of whether the valve state change is caused by the affirmative application of force or power. For example, a normally open valve may be actuated via the removal of power or pressure, and a closed valve may be opened through the application of pneumatic force, electrical power, or another means of physical interaction (e.g., electromagnetic). Communication between controller 302, valve 304, control valve 305, or check valve 308, and one or more of pressure sensor 306 and / or IoT sensor 310 may be performed to monitor, regulate, and test pressure management system 300, as discussed in further detail below. Depending on the desired implementation, communication between controllers (e.g., controller 302), valves (304, 305, 308), and sensors (306, 310) may be facilitated using a wired, wireless and / or pneumatic communication path, such as communication path 303.

[0020] For pressure regulation in pipe 301, actuation of primary valve 304 can be performed using valve control 305, which can include a pneumatic control system. However, controller 302 may be configured to actuate primary valve 304 using other means, such as by using an electrical or electromagnetic actuator. In the illustrated configuration, primary valve 304 separates pipe 301 from vent 307, which enables release of fluids (such as gas) thereby reducing the internal pressure of pipe 301. As such, actuation of primary valve 304 by controller 302 can be used to reduce (or increase) pressure in pipe 301. In some approaches, primary valve 304 may be normally open, such that primary valve 304 is closed through active control by controller 302, and automatically opened in the event of power loss, or the loss of compressed air, to controller 302. In other approaches, primary valve 304 may be normally closed, such that primary valve 304 is opened through active control by controller 302, and automatically closed in the event of power loss, or the loss of compressed air.

[0021] To prevent backflow into pipe 301 when primary valve 304 is opened (e.g., either due to a detected high-pressure condition or power loss to controller 302), a check valve 308 is disposed between primary valve 304 and pipe 301. Depending on the desired implementation, check valve 308 may be optional, and may not be needed in some configurations. Check valve 308 can be configured to maintain a low-pressure seal (e.g., 1 - 5 bar above atmospheric pressure) in order to prevent ingress and contamination into pipe 301 via vent 307. It is understood that other default values for the low-pressure seal may be used, without departing from the scope of the disclosed technology.

[0022] More generally, controller 302 can be programmed to actuate primary valve 304 upon the detection of one or more pre-conditions, such as a detected pressure in pipe 301 exceeding a predetermined threshold value (also: predetermined pressure threshold). For example, controller 302 may be programmed to open primary valve 304 if a pressure in pipe 301 reaches, or exceeds, 500 bar, 800 bar, or 1000 bar, etc. It is understood that virtually any predetermined pressure threshold may be used, without departing from the scope of the disclosed technology. Additionally, controller 302 may be programmed to perform valve management operations based on multiple pressure set points or thresholds, including but not limited to a low-low (LL) setpoint (or Threshold 1), a low (L) setpoint (or Threshold 2), a high (H) setpoint (or Threshold 3), and a high-high (HH) setpoint (or Threshold 4), etc., as discussed in further detail with respect to FIG. 3B, below.

[0023] Pressure information collected by pressure sensor 306 may be provided to controller 302 and if the measured pressure meets or exceeds the predetermined pressure threshold value (or predetermined threshold), then controller 302 can open primary valve 304 to release pressure from pipe 301 via vent 307. In some implementations, one or more valves (e.g., primary valve 304) may include a standalone pressure sensor (or pressure switch) that is configured to automatically control valve actuation in response to the detection of a predetermined pressure condition.

[0024] Depending on the desired setup, pressure sensor 306 may be configured to transmit pressure information to controller 302 on a periodic basis, or at a time when certain pressure changes are detected. For example, pressure sensor 306 may be configured to transmit pressure information to controller 302 at a regular cadence (e.g., 1 / min, 1 / second, or 10 / second), or only at times when pressure changes are detected at pressure sensor 306. In some aspects, a communication cadence of pressure sensor 306 and / or other sensors configured to communicate with controller 302 (e.g., IoT sensor 310) may be updated by a remote management system (not illustrated). In some instances, received sensor data may be filtered to eliminate noisy measurements, or short-term outliers in the measured values. For example, debouncing techniques, or moving window averages may be used to temporally smooth received sensor data values.

[0025] Sensor data may also be used to make inferences about future states of pressure management system 300 or to infer the occurrence of future events. For example, rapidly rising pressure values may be used to estimate that pressure in pipe 301 is likely to overshoot acceptable pressure levels (e.g., the predetermined threshold). In such instances, anticipatory responses may be implemented, for example, to lower rapidly rising pressure in pipe 301 by opening valve 304. In other aspects, notifications may be automatically transmitted to an operator to indicate a need for system intervention.

[0026] Controller 302 may be capable of being deactivated during testing of system (e.g., filling station 100, 125). In doing so, controller 302 may receive a signal based on an indication from a user via an input device that the system is undergoing testing. In some embodiments, controller 302 may automatically deactivate itself, e.g., based on a testing schedule, resulting in the normally open primary valve 304 being opened during testing. In other embodiments, when controller 302 receives the signal indicating that the system is undergoing testing, primary valve 304 can be set to a closed state, with a threshold for venting that is associated with testing.

[0027] The actuation of primary valve 304 can be based on other types of information received by controller 302, such as various types of sensor information received from one or more IoT sensors, such as IoT sensor 310. Operationally, IoT sensor 310 may include any of a variety of sensor types and may be configured to identify any of a variety of conditions. For example, IoT sensor 310 may include a temperature sensor, an ambient pressure sensor, a fire sensor, and / or a density meter etc. As such, IoT sensor 310, alone or in conjunction with other sensors, can be configured to measure ambient pressure information, detect fires, and / or measure density of fluid inside pipe 301.

[0028] Additionally, one or more of the valves (304, 308) may have one or more sensors that detect the corresponding valve state. For example, primary valve 304 may have one or more sensors that detect the valve state (e.g., open or closed). This open / close information may be provided to, or retrieved by, controller 302, for example help determine when state changes are needed and / or to track duty-cycles of primary valve 304 for predictive maintenance purposes. The predictive maintenance may also be based on monitoring of system runtime. In some instances, primary valve 304 may have a thermal pressure relief device (TPRD), or another safety device, that is configured to open (vent) pipe 301 upon the detection of an emergency event, such as a fire. The logic for how controller 302 actuates primary valve 304 in response to combinations of received sensor information, including but not limited to pipe pressure, ambient pressure, temperature, and / of fluid density, etc., can be stored in a memory of controller 302, which may be remotely updated, such as by a filling or distribution system, depending on the desired implementation. For example, various sensor values or parameters may be stored in a lookup table of a local memory device of controller 302 and referenced to determine if (or when) primary valve 304 is to be actuated. In some instances, the various sensor values and / or parameters may be stored in a lookup table located in a failsafe memory, for example, that is access controlled for regulatory review or audit.

[0029] A record of venting events and / or collected sensor information may be stored in memory (e.g., local memory or cloud memory), for later review and analysis. The record of venting events may include the detected sensor data (e.g., pressure data, temperature data, valve position data), event timestamps, and the relevant triggering thresholds used to initiate venting. Stored event information and timestamps can be used to identify the cause of various malfunctions, or to predict the need for further maintenance. For example, based on the number of venting events, the system may provide a notification to a user regarding preventative maintenance of associated parts, such as the primary valve 304, the valve control 305, and relevant sensors. In some approaches, detected events (e.g., valve actuation events, or detected changes in sensor data, etc.) may be communicated to a human operator in real time (or near real time), for immediate action. For example, service technicians may be dispatched upon the detection of a venting event, a detected high-pressure event, and / or any of a variety of other pre-conditions identifiable from collected sensor data.

[0030] Remote control over valves, using one or more network connected controllers, can be used for testing various aspects of valve operation and performance, such as valve responsiveness. For example, valves may be opened / closed according to a schedule, or in response to remote commands, for the purpose of testing valve functionality, e.g., to see if they "stick" after periods inactivity, or to test responsiveness under certain conditions, e.g., to see if actuation lags. In some aspects, valve actuation may be used to corroborate the functions of various other sensors or components in pressure management system 300. For example, the functionality of one or more pressure sensors (306, 310) may be validated by opening or closing various valves to ensure that pressure levels decrease or increase accordingly. Further details regarding a process for controlling a pressure release valve are discussed with respect to FIGs. 4A and 4B.

[0031] FIG. 3B illustrates an example pressure management system 350, similar to pressure management system 300, discussed above, but that additionally includes a secondary valve 312, for facilitating management and filling operations for cylinder 314. Additionally, in pressure management system 350, check valve 308 is optional, and in some aspects, may not be used. As illustrated, cylinder 314 can be coupled to pipe 301 via secondary valve 312. Similar to primary valve 304, secondary valve 312 can be actuated by controller 302, for example to control the ingress / egress of fluids (e.g., gas) from cylinder 314. In some implementations, secondary valve 312 can be closed to prevent pressure loss in cylinder 314, as discussed in further detail below.

[0032] In operation, the open / close status of secondary valve 312 and / or primary valve 304 can depend on one or more thresholds, and / or can be based on sensor information received by one or more of IoT sensor 310, pressure sensor 306 and / or one or more valve-integrated open / close sensors, etc. For example, electronic controller 302 can be configured to store multiple threshold pressure values that can be used to determine open / close conditions for primary valve 304 and / or secondary valve 312, including but not limited to a first threshold value (e.g., Threshold 1), a second threshold value (e.g., Threshold 2), a third threshold value (e.g., Threshold 3) and / or a fourth threshold value (e.g., Threshold 4).

[0033] In some implementations, the first threshold value can define a low pressure setpoint, below which, secondary valve 312 can be closed, for example to protect cylinder 314 from depressurizing, which can result in damage to various components, such as the liner and / or composite reinforcement layer. The second threshold value can be greater (or higher) than the first threshold value. If a detected pressure in pipe 301 is less than the second threshold value, but greater than the first threshold value, then low-pressure warnings (or notifications) may be generated. For example, notifications may be generated directly by controller 302, and / or the pressure information may be communicated to one or more remote systems, and the notifications may be remotely generated.

[0034] A third threshold value may be used to define a pressure greater than the second threshold value. If the pressure measured in pipe 301 is greater than the second threshold value, but less than the third threshold value, system 350 may be in a normal or optimal operating mode, and no action is taken.

[0035] A fourth threshold value may be used to define a high-pressure threshold that is greater than the third threshold value, and above which primary valve 304 can be opened, e.g., to reduce the pressure in pipe 301, as discussed above. In some implementations, secondary valve 312 may also be closed, for example, to prevent backflow into the cylinder in instances where a check valve (e.g., check valve 308) is not used. For pressure measurements above the fourth threshold value, notifications / warnings may also be generated, e.g., to alert of the high-pressure condition of management system 350. Further details regarding embodiments in which multiple pressure threshold levels are used to determine actuation for two or more valves are provided in further detail with respect to FIG. 4C, below.

[0036] FIG. 4A is a flowchart illustrating an example process 400 for managing pressure release using an electronically controlled pressure release valve, such as a primary valve 304 managed by electronic controller 302, discussed above. Process 400 begins at step 402 when pressure measurements (e.g., pressure measurement information) are received or retrieved by a controller, such as an electronic controller (or PLC) configured to control a pressure release valve, such as primary valve 302 discussed above with respect to FIGs. 3A and 3B. Received pressure information may indicate a pressure in a pipe of a gas delivery infrastructure (e.g., pipe 301), as discussed above. Additionally, pressure information may be received by the controller via a wired or wireless communication path.

[0037] Depending on the desired implementation, different (or additional) types of sensor information may be received by the controller. For example, pressure information indicating pressure readings at different locations in the pipe infrastructure and / or indicating ambient pressure readings may be received. In other approaches, various other types of sensor information may be received, including but not limited to one or more of: temperature information (indicating internal and / or ambient temperatures), density measurement information (indicating a density of a fluid or gas in a pipe infrastructure), and / or valve state information (indicating the open / close status of one or more valves), etc.

[0038] At step 404, it is determined, at the controller, whether the received pressure information indicates that the measured pressure is below (or equal to) the valve threshold (setpoint). The pressure threshold (or setpoint) can be used to specify a pressure threshold above which pressure release is initiated. In some aspects, measured pressures above a predetermined setpoint value can trigger pressure release, as discussed in further detail with respect to FIG. 4B, below. In some instances, the controller setpoint (predetermined threshold) may correspond with a pressure value that is based on a safety regulation and / or based on operational parameters of equipment, such as cylinders or vehicles, involved in a gas filling or distribution process.

[0039] To determine whether the requisite pre-conditions have been met, electronic controller 302 may access a lookup table of threshold values for reference / comparison. In some approaches, the pressure threshold may be referenced based on an identification of the fluid contained within system (e.g., filling station 100, 125) and traveling through pipe 301. In some embodiments, the identification of the fluid is provided to electronic controller 302 via an input device by a user. Alternatively, fluid identification may be performed automatically e.g., using one or more sensors in the system (e.g., filling station 100, 125) that are communicatively coupled to electronic controller 302. In some embodiments, the identification of the fluid is automatically communicated to the system (e.g., filling station 100, 125) by a communications device or a filling device used to fill the system with fluid.

[0040] For example, a mobile filling station 125 may dispense a first fluid having a first associated pressure threshold. Upon emptying of the first fluid after dispensing to other storage containers, the mobile filling station 125 may be filled with a second fluid having a second associated pressure threshold. As described herein, an identification of the second fluid may be communicated to the electronic controller 302 by a user via an input device, automatically detected by a sensor of the mobile filling station 125 as the mobile filling station 125 is filled with the second fluid or communicated to the mobile filling station 125 by the filling device used to fill the mobile filling station 125 with the second fluid. In this way, the mobile filling station 125 can dynamically accommodate the safety requirements of multiple different fluids without having to change hardware components (e.g., mechanical release valve 202).

[0041] If at step 404 it is determined that the setpoint has not been triggered, e.g., that the received pressure measurement is below the threshold, then process 400 reverts to step 402. However, if at step 404 it is determined that the setpoint has been triggered, e.g., that the measured pressure is greater than the predetermined pressure threshold / setpoint, sufficient to meet the triggering criterion, then process 400 proceeds to step 406 in which a valve is opened, e.g., to release pressure from within the pipe, thereby reducing the pressure. As discussed above, opening the valve can release gas / fluids from inside of a pipe into the atmosphere e.g., via a vent coupled to the valve. The valve may be a normally open valve such that valve closure must be actively maintained by a controller, in which case, power loss to the controller, or loss of compressed air, can cause the valve to automatically open. In other configurations, the valve may be normally closed, in which case, power loss to the controller can cause the valve to automatically open.

[0042] At step 408, the controller can continue to receive (or retrieve) subsequent pressure measurement information from one or more pressure sensors (e.g., a second pressure measurement, or a third pressure measurement, etc.). For example, the controller may receive a subsequent pressure measurement that represents a pressure inside of a pipe at some time after the PRV has been opened (406). As discussed above, additional pressure measurements and / or other types of sensor data may be also (or alternatively) be received, without departing from the scope of the disclosed technology.

[0043] At step 410, it is determined whether the subsequently received pressure information (408) indicates that the pressure setpoint is still triggered, i.e., if the measured pressure is still above the setpoint, or of the pressure has been lowered to acceptable levels. Depending on the desired implementation, a pressure measurement that is below the setpoint / threshold can indicate that a pressure in the pipe has been reduced to an acceptable level, i.e., that the setpoint is no longer triggered. If at step 410 it is determined that the setpoint is still triggered, then process 400 can revert to step 410, the valve can remain open, and pressure monitoring can continue. Alternatively, if it is determined that the pressure has been adequately reduced below the predetermined threshold (e.g., that the setpoint is no longer triggered), process 400 can advance to step 412 and the valve can be closed.

[0044] FIG. 4B is a flowchart illustrating an example process for managing pressure in which pressure is kept above a predetermined threshold. Process 450 begins at step 452 when pressure measurements (e.g., pressure measurement information) are received by a controller, such as an electronic controller (or PLC) configured to control a PRV, such as primary valve 302 discussed above with respect to FIGs. 3A and 3B. Received pressure information may indicate a pressure in a pipe of a gas delivery infrastructure (e.g., pipe 301). As discussed above, pressure information may be received by the controller via a wired or wireless communication path.

[0045] Depending on the desired implementation, different (or additional) types of sensor information may be received by the controller. For example, pressure information indicating pressure readings at different locations in the pipe infrastructure and / or indicating ambient pressure readings may be received. In other approaches, various other types of sensor information may be received, including but not limited to one or more of: temperature information (indicating internal and / or ambient temperatures), density measurement information (indicating a density or viscosity of a fluid or gas in a pipe infrastructure), and / or valve state information (indicating the open / close status of one or more valves), etc.

[0046] At step 454, it is determined whether the received pressure information indicates that the measured pressure is below (or equal to) the valve threshold (setpoint). The pressure threshold (or setpoint) can be used to specify a pressure threshold below which valve closure is initiated. The controller setpoint (predetermined threshold) may correspond with a pressure value that is based on a safety regulation and / or based on operational parameters of equipment, such as cylinders or vehicles, involved in a gas filling process.

[0047] To determine whether the requisite pre-conditions have been met, electronic controller 302 may access a lookup table of threshold values for reference / comparison. In some approaches, the pressure threshold may be referenced based on an identification of the fluid contained within system (e.g., filling station 100, 125) and traveling through pipe 301. In some embodiments, the identification of the fluid is provided to electronic controller 302 via an input device by a user. Alternatively, fluid identification may be performed automatically e.g., using one or more sensors in the system (e.g., filling station 100, 125) that are communicatively coupled to electronic controller 302. In some embodiments, the identification of the fluid is automatically communicated to the system (e.g., filling station 100, 125) by a communications device or a filling device used to fill the system with fluid.

[0048] For example, a mobile filling station 125 may dispense a first fluid having a first associated pressure threshold. Upon emptying of the first fluid after dispensing it to other storage containers, the mobile filling station 125 may be filled with a second fluid having a second associated pressure threshold. As described herein, an identification of the second fluid may be communicated to the electronic controller 302 by a user via an input device, automatically detected by a sensor of the mobile filling station 125 as the mobile filling station 125 is filled with the second fluid or communicated to the mobile filling station 125 by the filling device used to fill the mobile filling station 125 with the second fluid. In this way, the mobile filling station 125 can dynamically accommodate the safety requirements of multiple different fluids without having to change hardware components (e.g., mechanical release valve 202).

[0049] If at step 454 it is determined that the setpoint has not been triggered, e.g., that the received pressure measurement remains above the threshold, then process 450 reverts to step 452. However, if at step 454 it is determined that the setpoint has been triggered, e.g., that the measured pressure is below than the predetermined pressure threshold / setpoint, sufficient to meet the triggering criterion, then process 450 proceeds to step 456 in which a valve is closed, e.g., to prevent the release of pressure from within the pipe, thereby increasing the pressure. Closing the valve can prevent the release of gas / fluids from inside of a pipe. In such setups, the valve may be a normally closed valve such that valve opening must be actively performed by a controller, in which case, power loss to the controller can cause the valve to automatically close.

[0050] At step 458, the controller can continue to receive (or retrieve) subsequent pressure measurement information from one or more pressure sensors (e.g., a second pressure measurement, or a third pressure measurement, etc.). For example, the controller may receive a subsequent pressure measurement that represents a pressure inside of a pipe at some time after the PRV has been closed (456). Additional pressure measurements and / or other types of sensor data may be also (or alternatively) be received, without departing from the scope of the disclosed technology.

[0051] At step 460, it is determined whether the subsequently received pressure information (408) indicates that the pressure setpoint is still triggered. Depending on the desired implementation, a pressure measurement that is below the setpoint can indicate that a pressure in the pipe has not yet returned to an acceptably high level. Thus, if at step 460 it is determined that the setpoint is still triggered, then process 450 can revert to step 456, and the valve can remain closed, for example, to continue the buildup of pressure in the pipe. Alternatively, if it is determined that the pressure has been adequately raised above the predetermined threshold (e.g., that the setpoint is not still triggered), process 450 can advance to step 452 and the valve can be opened.

[0052] It is understood that valve actuation can be controlled based on other types of sensor information, including but not limited to information regarding: temperature, ambient temperature, ambient pressure, fluid density, fluid viscosity, valve state, etc. As such, the setpoint triggering determinations (404, 410) can additionally (or alternatively) be based on other types of sensor information, without departing from the scope of the disclosed technology.

[0053] FIG. 4C conceptually illustrates a multitude of pressure threshold levels 480 e.g., Threshold 1 (LL), Threshold 2 (L), Threshold 3 (H), and Threshold 4 (HH), for operating a pressure management system. Threshold levels 480 define various operational conditions of a pressure management system, such as management system 350, discussed above. It is understood that a greater (or fewer) number of threshold levels may be used, without departing from the scope of the disclosed technology.

[0054] As discussed above with respect to FIG. 3B, if a measured pressure in the management system is below a first threshold (e.g., Threshold 1), then the system may be considered to be in an extreme low pressure state (LL), and the management system can respond by generating one or more notifications or warnings regarding the low-pressure condition, and / or closing a secondary valve (e.g., valve 312) to avoid depressurization of a connected cylinder or tank (482). Closing of cylinder valves in low pressure scenarios can help to protect various cylinder components, such as liners and / or reinforcement layers, etc.

[0055] If the measured pressure is greater than Threshold 1, but less than Threshold 2, then the system can be considered to be in a low pressure state (L). In this state, warnings / notifications may be generated, e.g., to warn of the low-pressure condition (484). As discussed above, warnings or alerts may be communicated off-device, for example, to communicate state information about the management system to specific devices and / or individuals.

[0056] If the measured pressure is greater than Threshold 2, but less than Threshold 3, the management system may be considered to be in an optimal or steady-state operating region (486), in which case no action is needed. In this state, the pressure management system can continue with normal operations, and no alerts / warnings are generated, and no actions are taken to alter valve states.

[0057] If the measured pressure is greater than Threshold 3, but less than Threshold 4, the management system may be considered to be in a high-pressure state (H). In such cases, warnings / notifications may be generated, e.g., to warn of the high pressure condition (488).

[0058] If the measured pressure is greater than Threshold 4, the management system may be considered to be in a very-high pressure (HH) state. In such cases, a primary valve (e.g., primary valve 304) may be opened to reduce pressure in one or more pipes of the management system, as discussed above (490). In some instances, cylinder-valves (e.g., secondary valve 312) may also be closed, for example, to prevent backflow into the cylinder in implementations where a check valve (e.g., check valve 308) is not used.

[0059] FIG. 5 illustrates a method 500 for managing pressure using an electronically controlled and monitored PRV. At step 502, the method 500 includes storing a pressure threshold value on an electronic controller, wherein the electronic controller is configured to actuate a primary valve, and wherein the primary valve controls fluidic communication between a pipe and a vent. The pressure threshold value can be used to indicate a maximum amount of pressure that can be observed / measured before pressure release should be initiated, as such the pressure threshold value can function as a predetermined threshold (or predetermined pressure threshold) for triggering pressure release. The pressure threshold value may be, or may be based on, regulation and / or equipment specifications. Additionally, the pressure threshold value may be based on or determined from other types of information, including but not limited to sensor information received from one or more network connected sensors (e.g., IoT sensors) in a vicinity of a pressure management system. By way of example, the pressure threshold value may be set based on an ambient temperature, a pipe pressure, and / or a temperature around a pressure management system that includes an electronic controller coupled to a pressure release valve (e.g., a primary valve) to release pressure from a piping infrastructure.

[0060] At step 504, method 500 includes receiving pressure information from a pressure sensor, the pressure information representing a pressure in the pipe. In some aspects, the pressure sensor may be collocated or integrated with the controller receiving the pressure information. In other aspects, the controller and pressure sensor may be disparate, in which case communication may occur via a wired or wireless communication means. As discussed above, the transmission of pressure information to the controller may also be based on certain programmable pre-conditions of the pressure sensor. For example, pressure reading information may be communicated at regular intervals, or may be communicated in response to detected pressure changes, etc.

[0061] Additional or other types of sensor information may also be communicated to the controller. For example, pressure measurement information from one or more additional pressure sensors may be provided, for example, to provide additional information about pressure conditions at various location in a pipe infrastructure and / or to provide ambient pressure data. As discussed above, sensor information of other types may also be used. For example, the controller may be configured to make valve actuation decisions using temperature information received from one or more temperature sensors and / or density information received from one or more density sensors, and the like. In some configurations, the controller may also receive state information directly from one or more valves (such as the primary valve) that indicate open / close states of the respective valve. Valve state information may be used to validate operational states of the pressure management system and in some instances may be used for predictive maintenance, e.g., to predict when the primary valve needs maintenance or replacement.

[0062] At step 506, method 500 includes actuating the primary valve via the electronic controller, if the pressure in the pipe is greater than or equal to a predetermined threshold. As discussed above, the valve may be configured to be normally open such that closed-valve states are actively maintained. In such configurations, power loss to the controller can cause the valve to automatically open helping to prevent over-pressure conditions in power-limited or emergency scenarios.

[0063] At step 508, method 500 includes maintaining a closure of the primary valve, if the pressure in the pipe is lower than a predetermined threshold.

[0064] FIG. 6 illustrates an example processor-based system 600 that can be used to implement some or all aspects of the subject technology. For example, processor-based system 600 can be used to implement a controller (PLC), such as electronic controller 302, and / or any component thereof.

[0065] The processor-based system 600 can include a connection 605 used by components of the system to communicate with each other. The connection 605 can be or include a physical connection via a bus, or a direct connection into processor 610, such as in a chipset architecture. Connection 605 can also be a virtual connection, networked connection, or logical connection.

[0066] The example system 600 includes at least one processing unit (CPU or processor) 610 and connection 605 that couples various system components including system memory 615, such as read-only memory (ROM) 520 and random-access memory (RAM) 625 to processor 610. Computing system 600 can include a cache of high-speed memory 612 connected directly with, in close proximity to, and / or integrated as part of processor 610.

[0067] Processor 610 can include any general-purpose processor and a hardware service or software service, such as services 632, 634, and 636 stored in storage device 630, configured to control processor 610 as well as a special-purpose processor where software instructions are incorporated into the actual processor design. Processor 610 may essentially be a completely self-contained computing system, containing multiple cores or processors, a bus, memory controller, cache, etc. A multi-core processor may be symmetric or asymmetric.

[0068] To enable user interaction, computing system 600 can include an input device 645, which can represent any number of input mechanisms, such as a microphone for speech, a touch-sensitive screen for gesture or graphical input, keyboard, mouse, motion input, speech, etc. Computing system 600 can also include output device 635, which can be one or more of a number of output mechanisms known to those of skill in the art. In some instances, multimodal systems can enable a user to provide multiple types of input / output to communicate with computing system 600. Computing system 600 can include communications interface 640, which can generally govern and manage the user input and system output.

[0069] The communication interface may perform or facilitate receipt and / or transmission wired or wireless communications via wired and / or wireless transceivers, including those making use of an audio jack / plug, a microphone jack / plug, a universal serial bus (USB) port / plug, an Apple ®< Lightning ®< port / plug, an Ethernet port / plug, a fiber optic port / plug, a proprietary wired port / plug, a BLUETOOTH ®< wireless signal transfer, a BLUETOOTH ®< low energy (BLE) wireless signal transfer, an IBEACON ®< wireless signal transfer, a radio-frequency identification (RFID) wireless signal transfer, near-field communications (NFC) wireless signal transfer, dedicated short range communication (DSRC) wireless signal transfer, 502.11 Wi-Fi wireless signal transfer, wireless local area network (WLAN) signal transfer, Visible Light Communication (VLC), Worldwide Interoperability for Microwave Access (WiMAX), Infrared (IR) communication wireless signal transfer, Public Switched Telephone Network (PSTN) signal transfer, Integrated Services Digital Network (ISDN) signal transfer, 3G / 4G / 5G / LTE cellular data network wireless signal transfer, ad-hoc network signal transfer, radio wave signal transfer, microwave signal transfer, infrared signal transfer, visible light signal transfer, ultraviolet light signal transfer, wireless signal transfer along the electromagnetic spectrum, or some combination thereof.

[0070] Communications interface 640 may also include one or more Global Navigation Satellite System (GNSS) receivers or transceivers that are used to determine a location of the computing system 600 based on receipt of one or more signals from one or more satellites associated with one or more GNSS systems. GNSS systems include, but are not limited to, the US-based Global Positioning System (GPS), the Russia-based Global Navigation Satellite System (GLONASS), the China-based BeiDou Navigation Satellite System (BDS), and the Europe-based Galileo GNSS. There is no restriction on operating on any particular hardware arrangement, and therefore the basic features here may easily be substituted for improved hardware or firmware arrangements as they are developed.

[0071] Storage device 630 can be a non-volatile and / or non-transitory computer-readable memory device and can be a hard disk or other types of computer readable media which can store data that are accessible by a computer, such as magnetic cassettes, flash memory cards, solid state memory devices, digital versatile disks, cartridges, a floppy disk, a flexible disk, a hard disk, magnetic tape, a magnetic strip / stripe, any other magnetic storage medium, flash memory, memristor memory, any other solid-state memory, a compact disc read only memory (CD-ROM) optical disc, a rewritable compact disc (CD) optical disc, digital video disk (DVD) optical disc, a blu-ray disc (BD) optical disc, a holographic optical disk, another optical medium, a secure digital (SD) card, a micro secure digital (microSD) card, a Memory Stick ®< card, a smartcard chip, a EMV chip, a subscriber identity module (SIM) card, a mini / micro / nano / pico SIM card, another integrated circuit (IC) chip / card, random access memory (RAM), static RAM (SRAM), dynamic RAM (DRAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash EPROM (FLASHEPROM), cache memory (L1 / L2 / L3 / L4 / L9 / L#), resistive random-access memory (RRAM / ReRAM), phase change memory (PCM), spin transfer torque RAM (STT-RAM), another memory chip or cartridge, and / or a combination thereof.

[0072] Storage device 630 can include software services, servers, services, etc., that when the code that defines such software is executed by the processor 610, causes the system to perform a function. In some examples, a hardware service that performs a particular function can include the software component stored in a computer-readable medium in connection with the necessary hardware components, such as processor 610, connection 605, output device 635, etc., to carry out the function.

[0073] Aspects within the scope of the present disclosure may also include tangible and / or non-transitory computer-readable storage media or devices for carrying or having computer-executable instructions or data structures stored thereon. Such tangible computer-readable storage devices can be any available device that can be accessed by a general purpose or special purpose computer, including the functional design of any special purpose processor as described above. By way of example, and not limitation, such tangible computer-readable devices can include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other device which can be used to carry or store desired program code in the form of computer-executable instructions, data structures, or processor chip design. When information or instructions are provided via a network or another communications connection (either hardwired, wireless, or combination thereof) to a computer, the computer properly views the connection as a computer-readable medium. Thus, any such connection is properly termed a computer-readable medium. Combinations of the above should also be included within the scope of the computer-readable storage devices.

[0074] Computer-executable instructions include, for example, instructions and data which cause a general-purpose computer, special-purpose computer, or special-purpose processing device to perform a certain function or group of functions. By way of example, computer-executable instructions can be used to implement perception system functionality for determining when sensor cleaning operations are needed or should begin. Computer-executable instructions can also include program modules that are executed by computers in stand-alone or network environments. Generally, program modules include routines, programs, components, data structures, objects, and the functions inherent in the design of special-purpose processors, etc. that perform tasks or implement abstract data types. Computer-executable instructions, associated data structures, and program modules represent examples of the program code means for executing steps of the methods disclosed herein. The particular sequence of such executable instructions or associated data structures represents examples of corresponding acts for implementing the functions described in such steps.

[0075] Other examples of the disclosure may be practiced in network computing environments with many types of computer system configurations, including personal computers, hand-held devices, multi-processor systems, microprocessor-based or programmable consumer electronics, network PCs, minicomputers, mainframe computers, and the like. Aspects of the disclosure may also be practiced in distributed computing environments where tasks are performed by local and remote processing devices that are linked (either by hardwired links, wireless links, or by a combination thereof) through a communications network. In a distributed computing environment, program modules can be located in both local and remote memory storage devices.

[0076] The various examples described above are provided by way of illustration only and should not be construed to limit the scope of the disclosure. For example, the principles herein apply equally to optimization as well as general improvements. Various modifications and changes may be made to the principles described herein without following the example aspects and applications illustrated and described herein, and without departing from the spirit and scope of the disclosure.

[0077] Claim language or other language in the disclosure reciting "at least one of" a set and / or "one or more" of a set indicates that one member of the set or multiple members of the set (in any combination) satisfy the claim. For example, claim language reciting "at least one of A and B" or "at least one of A or B" means A, B, or A and B. In another example, claim language reciting "at least one of A, B, and C" or "at least one of A, B, or C" means A, B, C, or A and B, or A and C, or B and C, or A and B and C. The language "at least one of" a set and / or "one or more" of a set does not limit the set to the items listed in the set. For example, claim language reciting "at least one of A and B" or "at least one of A or B" can mean A, B, or A and B, and can additionally include items not listed in the set of A and B.

[0078] Illustrative examples of the disclosure include: Aspect 1. A pressure management system, comprising: an electronic controller; a pressure sensor coupled to the electronic controller and to a pipe, wherein the pressure sensor is configured to relay pressure information about the pipe to the electronic controller; and a primary valve coupled between a vent and the electronic controller; and a cylinder coupled to the pipe via a secondary valve, and wherein the electronic controller is configured to actuate the primary valve and / or the secondary based on pressure information received from the pressure sensor. Aspect 2. The pressure management system of Aspect 1, wherein the electronic controller is configured to receive open / close information from the primary valve and / or the secondary valve. Aspect 3. The pressure management system of any of Aspects 1 to 2, wherein the electronic controller is configured to actuate the primary valve and / or the secondary valve using a pneumatic actuator, an electric actuator, an electromagnetic actuator, or a combination thereof. Aspect 4. The pressure management system of any of Aspects 1 to 3, wherein the electronic controller is configured to: close the secondary valve, if the pressure information received from the pressure sensor indicates that a pressure in the pipe is below a first threshold value. Aspect 5. The pressure management system of any of Aspects 1 to 4, wherein the electronic controller is configured to: generate an alert, if the pressure information received from the pressure sensor indicates that a pressure in the pipe is above a first threshold value and below a second threshold value. Aspect 6. The pressure management system of any of Aspects 1 to 5, wherein the electronic controller is configured to: generate an alert, if the pressure information received from the pressure sensor indicates that a pressure in the pipe is above a third threshold value and below a fourth threshold value. Aspect 7. The pressure management system of any of Aspects 1 to 6, wherein the electronic controller is configured to: open the primary valve, if the pressure information received from the pressure sensor indicates that a pressure in the pipe is above a fourth threshold value. Aspect 8. The pressure management system of any of Aspects 1 to 7, further comprising: a density sensor communicatively coupled to the electronic controller, wherein the density sensor is configured to measure a density of fluid in the pipe. Aspect 9. The pressure management system of any of Aspects 1 to 8, further comprising: a check valve coupled between the primary valve and the pipe, wherein the check valve is configured to prevent a backflow from the vent into the pipe. Aspect 10. A method for managing pressure, comprising: storing a plurality of predetermined threshold values on an electronic controller, wherein the electronic controller is configured to actuate a primary valve and / or a secondary valve, and wherein the primary valve controls fluidic communication between a pipe and a vent, and the secondary valve controls fluidic communication between the pipe and a cylinder; receiving pressure information from a pressure sensor, the pressure information representing a pressure in the pipe; and actuating the primary valve and / or the secondary valve via the electronic controller, based on pressure information received from the pressure sensor. Aspect 11. The method of Aspect 10, wherein the primary valve and / or the secondary valve are actuated using a pneumatic actuator, an electric actuator, an electromagnetic actuator, or a combination thereof. Aspect 12. The method of any of Aspects 10 to 11, further comprising: closing the secondary valve, if the pressure information received from the pressure sensor indicates that a pressure in the pipe is below a first threshold value; and generating an alert if the pressure information indicates that the pressure in the pipe is above the first threshold value and below a second threshold value. Aspect 13. The method of any of Aspects 10 to 12, further comprising: generating an alert, if the pressure information received from the pressure sensor indicates that a pressure in the pipe is above a third threshold value and below a fourth threshold value. Aspect 14. The method of any of Aspects 10 to 13, further comprising: opening the primary valve, if the pressure information received from the pressure sensor indicates that a pressure in the pipe is above a fourth threshold value. Aspect 15. The method of any of Aspects 10 to 14, further comprising: communicatively coupling a density sensor to the electronic controller, wherein the density sensor is configured to measure a density of fluid in the pipe. Aspect 16. The method of any of Aspects 10 to 15, further comprising: disposing a check valve between the primary valve and the pipe, wherein the check valve is configured to prevent a backflow from the vent into the pipe. Aspect 17. The method of any of Aspects 10 to 16, further comprising: storing the plurality of predetermined thresholds in a lookup table on a local memory of the electronic controller. Aspect 18. The method of any of Aspects 10 to 17, further comprising: updating one or more of the plurality of predetermined thresholds using a wired or wireless network connection. Aspect 19. A non-transitory computer-readable medium having stored thereon instructions which, when executed by a controller, cause the controller to: store a plurality of predetermined threshold values on an electronic controller, wherein the electronic controller is configured to actuate a primary valve and / or a secondary valve, and wherein the primary valve controls fluidic communication between a pipe and a vent, and the secondary valve controls fluidic communication between the pipe and a cylinder; receive pressure information from a pressure sensor, the pressure information representing a pressure in the pipe; and actuate the primary valve and / or the secondary valve via the electronic controller, based on pressure information received from the pressure sensor. Aspect 20. The non-transitory computer-readable medium of Aspect 19, wherein the instructions are further configured to cause the controller to: receive open / close information from the primary valve and / or the secondary valve.

[0079] In particular, the invention relates to the following combinations of features, as are expressly defined in accordance with the sections

[00110] to

[00128] below:

[0080] A pressure management system, comprising: an electronic controller; a pressure sensor coupled to the electronic controller and to a pipe, wherein the pressure sensor is configured to relay pressure information about the pipe to the electronic controller; and a primary valve coupled between a vent and the electronic controller; and a cylinder coupled to the pipe via a secondary valve, and wherein the electronic controller is configured to actuate the primary valve and / or the secondary valve based on pressure information received from the pressure sensor.

[0081] The pressure management system of section

[00110] , wherein the electronic controller is configured to receive open / close information from the primary valve and / or the secondary valve.

[0082] The pressure management system of section

[00110] or

[00111] , wherein the electronic controller is configured to actuate the primary valve and / or the secondary valve using a pneumatic actuator, an electric actuator, an electromagnetic actuator, or a combination thereof.

[0083] The pressure management system of any of sections

[00110] to

[00112] , wherein the electronic controller is configured to: close the secondary valve, if the pressure information received from the pressure sensor indicates that a pressure in the pipe is below a first threshold value.

[0084] The pressure management system of any of sections

[00110] to

[00113] , wherein the electronic controller is configured to: generate an alert, if the pressure information received from the pressure sensor indicates that a pressure in the pipe is above a first threshold value and below a second threshold value.

[0085] The pressure management system of any of sections

[00110] to

[00114] , wherein the electronic controller is configured to: generate an alert, if the pressure information received from the pressure sensor indicates that a pressure in the pipe is above a third threshold value and below a fourth threshold value.

[0086] The pressure management system of any of sections

[00110] to

[00115] , wherein the electronic controller is configured to: open the primary valve, if the pressure information received from the pressure sensor indicates that a pressure in the pipe is above a fourth threshold value.

[0087] The pressure management system of any of sections

[00110] to

[00116] , further comprising: a density sensor communicatively coupled to the electronic controller, wherein the density sensor is configured to measure a density of fluid in the pipe.

[0088] The pressure management system of any of sections

[00110] to

[00117] , further comprising: a check valve coupled between the primary valve and the pipe, wherein the check valve is configured to prevent a backflow from the vent into the pipe.

[0089] A method for managing pressure, comprising: storing a plurality of predetermined threshold values on an electronic controller, wherein the electronic controller is configured to actuate a primary valve and / or a secondary valve, and wherein the primary valve controls fluidic communication between a pipe and a vent, and the secondary valve controls fluidic communication between the pipe and a cylinder; receiving pressure information from a pressure sensor, the pressure information representing a pressure in the pipe; and actuating the primary valve and / or the secondary valve via the electronic controller, based on pressure information received from the pressure sensor.

[0090] The method of section

[00119] , wherein the primary valve and / or the secondary valve are actuated using a pneumatic actuator, an electric actuator, an electromagnetic actuator, or a combination thereof.

[0091] The method of section

[00119] or

[00120] , further comprising: closing the secondary valve, if the pressure information received from the pressure sensor indicates that a pressure in the pipe is below a first threshold value; and generating an alert if the pressure information indicates that the pressure in the pipe is above the first threshold value and below a second threshold value.

[0092] The method of any of sections

[00119] to

[00121] , further comprising: generating an alert, if the pressure information received from the pressure sensor indicates that a pressure in the pipe is above a third threshold value and below a fourth threshold value.

[0093] The method of any of sections

[00119] to

[00122] , further comprising: opening the primary valve, if the pressure information received from the pressure sensor indicates that a pressure in the pipe is above a fourth threshold value.

[0094] The method of any of sections

[00119] to

[00123] , further comprising: communicatively coupling a density sensor to the electronic controller, wherein the density sensor is configured to measure a density of fluid in the pipe.

[0095] The method of any of sections

[00119] to

[00124] , further comprising: disposing a check valve between the primary valve and the pipe, wherein the check valve is configured to prevent a backflow from the vent into the pipe.

[0096] The method of any of sections

[00119] to

[00125] , further comprising: storing the plurality of predetermined thresholds in a lookup table on a local memory of the electronic controller.

[0097] The method of any of sections

[00119] to

[00126] , further comprising: updating one or more of the plurality of predetermined thresholds using a wired or wireless network connection.

[0098] A non-transitory computer-readable medium having stored thereon instructions which, when executed by a controller, cause the controller to: store a plurality of predetermined threshold values on an electronic controller, wherein the electronic controller is configured to actuate a primary valve and / or a secondary valve, and wherein the primary valve controls fluidic communication between a pipe and a vent, and the secondary valve controls fluidic communication between the pipe and a cylinder; receive pressure information from a pressure sensor, the pressure information representing a pressure in the pipe; and actuate the primary valve and / or the secondary valve via the electronic controller, based on pressure information received from the pressure sensor.

[0099] The non-transitory computer-readable medium of section

[00128] , wherein the instructions are further configured to cause the controller to: receive open / close information from the primary valve and / or the secondary valve.

Examples

Embodiment Construction

[0004]The detailed description set forth below is intended as a description of various configurations of the subject technology and is not intended to represent the only configurations in which the subject technology can be practiced. The appended drawings are incorporated herein and constitute a part of the detailed description. The detailed description includes specific details for the purpose of providing a more thorough understanding of the subject technology. However, it will be clear and apparent that the subject technology is not limited to the specific details set forth herein and may be practiced without these details. In some instances, structures and components are shown in block diagram form to avoid obscuring the concepts of the subject technology.

[0005]Pressure reducing valves (or pressure release valves) (PRVs) can be used in fluid dispensation systems to limit the maximum pressure at various locations in a network of piping, such as at critical junctions used for flu...

Claims

1. A pressure management system, comprising: an electronic controller; a pressure sensor coupled to the electronic controller and to a pipe, wherein the pressure sensor is configured to relay pressure information about the pipe to the electronic controller; and a primary valve coupled between a vent and the electronic controller; and a cylinder coupled to the pipe via a secondary valve, and wherein the electronic controller is configured to actuate the primary valve and / or the secondary valve based on pressure information received from the pressure sensor.

2. The pressure management system of claim 1, wherein the electronic controller is configured to receive open / close information from the primary valve and / or the secondary valve.

3. The pressure management system of claim 1, wherein the electronic controller is configured to actuate the primary valve and / or the secondary valve using a pneumatic actuator, an electric actuator, an electromagnetic actuator, or a combination thereof.

4. The pressure management system of claim 1, wherein the electronic controller is configured to: close the secondary valve, if the pressure information received from the pressure sensor indicates that a pressure in the pipe is below a first threshold value.

5. The pressure management system of claim 1, wherein the electronic controller is configured to: generate an alert, if the pressure information received from the pressure sensor indicates that a pressure in the pipe is above a first threshold value and below a second threshold value.

6. The pressure management system of claim 1, wherein the electronic controller is configured to: generate an alert, if the pressure information received from the pressure sensor indicates that a pressure in the pipe is above a third threshold value and below a fourth threshold value.

7. The pressure management system of claim 1, wherein the electronic controller is configured to: open the primary valve, if the pressure information received from the pressure sensor indicates that a pressure in the pipe is above a fourth threshold value.

8. The pressure management system of claim 1, further comprising: a check valve coupled between the primary valve and the pipe, wherein the check valve is configured to prevent a backflow from the vent into the pipe.

9. A method for managing pressure, comprising: storing a plurality of predetermined threshold values on an electronic controller, wherein the electronic controller is configured to actuate a primary valve and / or a secondary valve, and wherein the primary valve controls fluidic communication between a pipe and a vent, and the secondary valve controls fluidic communication between the pipe and a cylinder; receiving pressure information from a pressure sensor, the pressure information representing a pressure in the pipe; and actuating the primary valve and / or the secondary valve via the electronic controller, based on pressure information received from the pressure sensor.

10. The method of claim 9, wherein the primary valve and / or the secondary valve are actuated using a pneumatic actuator, an electric actuator, an electromagnetic actuator, or a combination thereof.

11. The method of claim 9, further comprising: closing the secondary valve, if the pressure information received from the pressure sensor indicates that a pressure in the pipe is below a first threshold value; and generating an alert if the pressure information indicates that the pressure in the pipe is above the first threshold value and below a second threshold value.

12. The method of claim 9, further comprising: generating an alert, if the pressure information received from the pressure sensor indicates that a pressure in the pipe is above a third threshold value and below a fourth threshold value.

13. The method of claim 9, further comprising: opening the primary valve, if the pressure information received from the pressure sensor indicates that a pressure in the pipe is above a fourth threshold value.

14. The method of claim 9, further comprising: disposing a check valve between the primary valve and the pipe, wherein the check valve is configured to prevent a backflow from the vent into the pipe.

15. A non-transitory computer-readable medium having stored thereon instructions which, when executed by a controller, cause the controller to: store a plurality of predetermined threshold values on an electronic controller, wherein the electronic controller is configured to actuate a primary valve and / or a secondary valve, and wherein the primary valve controls fluidic communication between a pipe and a vent, and the secondary valve controls fluidic communication between the pipe and a cylinder; receive pressure information from a pressure sensor, the pressure information representing a pressure in the pipe; and actuate the primary valve and / or the secondary valve via the electronic controller, based on pressure information received from the pressure sensor.

16. The non-transitory computer-readable medium of claim 15, wherein the instructions are further configured to cause the controller to: receive open / close information from the primary valve and / or the secondary valve.

Images