The present disclosure is generally in the field of gas furnaces. For example, systems and methods are provided herein for gas furnaces including a gas furnace with a pressure transducer and/or a pressure switch.
Gas furnace systems have been developed to heat the interior of structures such as residential and commercial structures. Gas furnace systems typically burn a combustible fluid such as natural gas to generate heat that may then be distributed throughout an interior of a structure. For example,
Pressure switch 104 may activate electrical switch 112 when a certain air pressure is achieved at heat exchanger 106. Once electrical switch 112 is activated, the gas valve may be actuated (e.g., by controller 110) to permit gas flow to the ignitor for combustion at a desired air-to-gas ratio. The pressure switch may be designed such that a minimum operational pressure for ignition at the heat exchanger is the same pressure that causes electrical switch 112 to activate. In this manner, pressure switch 104 may prevent operation of the pump if the minimum operational pressure is not achieved.
While gas furnace 100 with pressure switch 104 may prevent the heat exchanger from operating below a minimum air pressure, such a system illustrated in
Accordingly, there is a need for improved methods and systems for safely and cost effectively operating a gas furnace at multiple operating modes having various fuel-to-air ratios or mixtures.
Furnace systems have been developed for heating residential and commercial structures using a combustible fluid (e.g., natural gas) and capable of efficiently achieving multiple operating modes and/or multiple fuel-to-air mixtures. For example, a gas furnace system may include a heat exchanger and an induction fan for causing airflow through the heat exchanger. The induction fan and/or heat exchanger may include a pressure transducer and optionally one or more pressure switches.
The pressure switches may be used to calibrate and/or confirm the accuracy of the pressure transducer. The pressure transducer may be in communication with a controller controlling a valve connecting to a gas line for adjusting gas flow into the ignition of the heat exchanger based on a pressure detected by the pressure transducer. As the pressure transducer is designed to detect a wide range or spectrum of pressures and the valve is designed to be incrementally opened or closed varying degrees, the pressure transducer together with the gas valve may achieve multiple different operational modes and/or fuel-to-air mixtures or ratios.
Referring now to
As shown in
Controller 210 may be any computing device with a processor and may include one or more displays (e.g., touch screen display), one or more user interfaces (e.g., buttons), and/or one or more speakers and/or microphones. Controller 210 may communicate with one or more or other computing devices (e.g., remote controllers, smart phones, tablets, servers, etc.) via any suitable wired or wireless system (e.g., Wi-Fi, cellular network, Bluetooth, Bluetooth Low Energy (BLE) network, near field communication protocol, or the like).
Pressure transducer 204 may be any suitable pressure transducer designed to translate a mechanical displacement due to a pressure force into an electrical signal, the electrical signal indicative of a detected pressure. As pressure varies so too may the electrical signal, such that pressure changes may be continuously detected. Pressure transducer 204 may communicate with controller 210 via any suitable wired or wireless system.
Controller 210 may also be in communication with (e.g., via any suitable wired or wireless system) and/or may otherwise control an adjustable gas valve, which may control gas flow from gas line 205 into ignition 224. The gas valve may be any suitable gas valve which may be actuated to open or close a certain degree or percentage such that the flow of gas may be adjusted between 0 and 100% open. The gas valve may be situated in controller 210, ignition 224, and/or along gas line 205, for example.
Ignition 224 may be any suitable ignition which may cause combustion of gas received from gas line 205. Heat exchanger 206 may receive hot exhaust from ignition 224 and may direct the exhaust through a plurality of tubing terminating at inductor fan 202. Inductor fan 202 may be any suitable blower or other fan for generating an airflow within the tubing of heat exchanger 206, such that air flows across ignition 224, causing hot exhaust from heat exchanger 224 to be directed into tubing 206.
A fuel-to-air ratio at ignition 224 may be adjusted based on the degree at which the gas valve is opened and/or the airflow at ignition 224, generated by inductor fan 202. To determine the pressure at ignition 224 and thus the airflow, pressure transducer 204 may be positioned in or near inductor fan 204. While pressure transducer 204 is illustrated incorporated into inductor fan 202 in
As heated air travels through heat exchanger 206, blower 214 may generate a flow across heat exchanger 206. Blower 214 may be any suitable blower or fan. For example, air may enter inlet 218, be directed through blower 214, and across heat exchanger 206, and ultimately exit housing 206 to enter ducting of the residential or commercial structure. By adjusting the gas valve permitting gas to enter ignition 224, the heat generated by heat exchanger 206 may be adjusted, resulting in different heat modes. A user may select a desired heat mode based on the heating needs for the residential or commercial structure.
Pressure transducer 204 may detect a range of pressures, which may be indicative or representative of a pressure and/or airflow at ignition 224. A minimum pressure corresponding to a minimum airflow at ignition 224 may be required to safely ignite gas supplied from gas line 205. Pressure transducer 204 may, for example, detect pressures from or near the minimum operational pressure and pressures between the minimum operational pressure or airflow at ignition 224 and a maximum operational pressure and/or airflow. For example, operational pressure for the gas furnace system may be between 0 and 5 inches of water, with a minimum operational pressure of 0.01 inches of water and a maximum operational pressure of 5 inches of water.
Pressure transducer 204 may send an electrical signal indicative of the pressure sensed at pressure transducer 204 and/or a wireless message indicative of the same to controller 210. Based on the pressure determined from the electrical and/or wireless signal or message, controller 210 may determine an amount to open the gas valve. For example, controller 210 may maintain a table, database, plot, data, or other information associating certain pressures with an amount or degree for opening the gas valve.
In one example, controller 210 may maintain a set of data points associating degrees of valve opening with detected pressures. For example, plot 220 may illustrate the amount the gas valve will be opened in response to pressures detected. As shown in plot 220, the gas valve may remain closed until a certain minimum pressure is detected. Once a minimum pressure is achieved the gas valve may be continuously opened as detected pressure increases. While plot 220 depicts a linear curve, it is understood that any plot shape may be achieved and/or desirable.
As shown in plot 220, each point along the plot representing a certain degree or percent valve open and pressure detected may also correspond to a fuel-to-air mixture ratio. Fuel-to-air mixture ratios may be calculated and/or determined for each point along the plot. For example, there may be certain points along the plot (e.g., certain pressure, valve setting combinations) for which the fuel-to-air ratio (e.g., air/fuel mixture 1, 2, or 3) is known to be optimal or otherwise desirable (e.g., generates least amount of undesirable byproducts) and therefore may be selected by the controller 210.
In one example, controller 210 may optionally also control inductor fan 202 and may generate an airflow using inductor fan 202 determined to generate a certain pressure corresponding to a desired fuel-to-air mixture. Once the identified pressure is detected using pressure transducer 204, controller 210 may adjust the gas valve to the prescribed percent or degree open, as set forth in plot 220, to achieve the desire fuel-to-air mixture. As pressure transducer 204 is not limited to only one pressure detection amount, the gas furnace system is capable of operating at various modes along plot 220.
Referring now to
Gas furnace 300 may be similar to gas furnace 200 of
Gas furnace 300 may include the same components of gas furnace 200, with the exception of pressure switch 325 and/or pressure switch 335. Pressure switch 325 and pressure switch 335 may be the same but pressure switch 325 may be set to actuate to close the electrical circuit at a pressure that may be lower than pressure switch 335. The gas valve that restricts flow of gas line 305 may communicate with controller 310 to actuate to restrict gas flow based on the pressure detected by pressure transducer 304.
Pressure switches 325 and/or 335 may be used to confirm the accuracy of pressure transducer 304. For example, as shown in plot 320, controller 310 may maintain data and/or a plot associating certain percent or degree open of the gas valve to the pressure detected by pressure transducer 304. A minimum operating pressure may be set at pressure value 340. A maximum operating pressure may be set at a maximum pressure value 342. In one example, pressure switch 325 may correspond to pressure value 340, which may correspond to a certain air-to-fuel mixture value, and pressure switch 335 may correspond to pressure value 342, which may correspond to a different air-to-fuel mixture value.
In one example, pressure switch 325 may be set to actuate or otherwise generate an electrical signal at first pressure value 340 and/or pressure switch 335 may be set to actuate or otherwise generate an electrical signal at pressure value 342. It is understood that controller 310 may only include one pressure switch or more than two pressure switches. It is further understood that the pressure switches may be associated or set at different pressure values than those illustrated in
To confirm the accuracy of pressure transducer 304, controller 310 may cause inductor fan 302 to operate at a first setting estimated or known to generate a first pressure or alternatively to incrementally increase in speed. When the pressure transducer achieves the known or estimated pressure, which may be the operating pressure, controller 310 may determine whether pressure switch 325, which may be designed to activate at the known or estimated pressure, is activated (e.g., with the electrical switch closed or activated). If the pressure switch is activated, then the pressure transducer may be deemed to be accurate. If it is not activated, then the pressure transducer may be faulty or not calibrated.
Gas furnace 300 may similarly cause inductor fan 302 to increase speed to generate an airflow resulting in a pressure at which pressure switch 335 is designed to activate (e.g., maximum operational temperature). When the pressure transducer achieves the known or estimated pressure, which may be the operating pressure, controller 310 may determine whether pressure switch 335 is activated (e.g., with the electrical switch closed or activated). If the pressure switch is activated, then the pressure transducer may be deemed to be accurate. If it is not activated, then the pressure transducer may be faulty or not calibrated.
Controller 310 may be designed to check the accuracy of pressure transducer 304 when gas furnace 300 is not operating (e.g., during down time). For example, a gas furnace may quickly achieve minimum and maximum operational pressures at set periods of time (e.g., every hour, every week, every month). In another example, only one pressure switch may be included and may be designed to activate at a pressure between minimum and maximum operational pressures.
Referring now to
Pressure transducer 404, pressure switch 425, pressure switch 435, and/or controller 410, may be the same as or similar to pressure transducer 304, pressure switch 325, pressure switch 335, and/or controller 310 of
Referring now to
At block 502, computer-executable instructions stored on a memory of a device, such as a controller, may be executed to determine to perform the calibration check (e.g., at a set time or elapsed time). At block 504, computer-executable instructions stored on a memory of a device, such as a controller, may be executed to cause the draft inducer to operate at a first setting which may, for example, correspond to a first pressure switch. At block 506, computer-executable instructions stored on a memory of a device, such as a controller, may be executed to determine a pressure transducer output (e.g., signal) at the first setting of the inductor fan (e.g., draft inducer).
At block 508, computer-executable instructions stored on a memory of a device, such as a controller, may be executed to determine the output of the first pressure switch at the first setting of the inductor fan (e.g., this may be a signal to indicate that the electric switch has closed). At decision 510 computer-executable instructions stored on a memory of a device, such as a controller, may be executed to determine whether the pressure transducer output corresponds to the pressure switch output (e.g., whether they indicate the same pressure value).
If the outputs don't indicate the same pressure value, then at block 512, computer-executable instructions stored on a memory of a device, such as a controller, may be executed to generate an error message for the pressure transducer at the first inductor fan setting. Alternatively, if the outputs do indicate the same pressure value, then at block 514, computer-executable instructions stored on a memory of a device, such as a controller, may be executed to cause the inductor fan to operate at a second setting corresponding to a second pressure switch. Optionally, step 514 may also be initiated after block 512.
At block 516, computer-executable instructions stored on a memory of a device, such as a controller, may be executed to determine the pressure transducer output amount at the second setting of the inductor fan. At block 518, computer-executable instructions stored on a memory of a device, such as a controller, may be executed to determine the second pressure switch output amount at the second setting of the inductor fan.
At decision 520 computer-executable instructions stored on a memory of a device, such as a controller, may be executed to determine whether the pressure transducer output corresponds to the pressure switch output (e.g., whether they indicate the same pressure value). If the outputs don't indicate the same pressure value, then at block 522, computer-executable instructions stored on a memory of a device, such as a controller, may be executed to generate an error message for the pressure transducer at the second draft inducer setting. Alternatively, if the outputs do indicate the same pressure value, then the pressure transducer may be calibrated and/or accurate and the process and block 502 may be reinitiated. Block 502 may optionally be reinitiated after block 522 as well.
Controller 600 may be designed to communicate with one or more gas valves, ignitors, gas valves, inductor fans, blower fans, pressure transducers, and/or pressure switches. Controller 600 may be designed to communicate via one or more networks. Such network(s) may include, but are not limited to, any one or more different types of communications networks such as, for example, cable networks, public networks (e.g., the Internet), private networks (e.g., frame-relay networks), wireless networks, cellular networks, telephone networks (e.g., a public switched telephone network), or any other suitable private or public packet-switched or circuit-switched networks.
In an illustrative configuration, controller 600 may include one or more processors 602, one or more memory devices 604 (also referred to herein as memory 604), one or more input/output (I/O) interface(s) 606, one or more network interface(s) 608, one or more transceiver(s) 610, one or more antenna(s) 634, and data storage 620. The controller 600 may further include one or more bus(es) 618 that functionally couple various components of the controller 600.
The bus(es) 618 may include at least one of a system bus, a memory bus, an address bus, or a message bus, and may permit exchange of information (e.g., data (including computer-executable code), signaling, etc.) between various components of the controller 600. The bus(es) 618 may include, without limitation, a memory bus or a memory controller, a peripheral bus, an accelerated graphics port, and so forth. The bus(es) 618 may be associated with any suitable bus architecture including.
The memory 604 may include volatile memory (memory that maintains its state when supplied with power) such as random access memory (RAM) and/or non-volatile memory (memory that maintains its state even when not supplied with power) such as read-only memory (ROM), flash memory, ferroelectric RAM (FRAM), and so forth. Persistent data storage, as that term is used herein, may include non-volatile memory. In various implementations, the memory 604 may include multiple different types of memory such as various types of static random access memory (SRAM), various types of dynamic random access memory (DRAM), various types of unalterable ROM, and/or writeable variants of ROM such as electrically erasable programmable read-only memory (EEPROM), flash memory, and so forth.
The data storage 620 may include removable storage and/or non-removable storage including, but not limited to, magnetic storage, optical disk storage, and/or tape storage. The data storage 620 may provide non-volatile storage of computer-executable instructions and other data. The memory 604 and the data storage 620, removable and/or non-removable, are examples of computer-readable storage media (CRSM) as that term is used herein. The data storage 620 may store computer-executable code, instructions, or the like that may be loadable into the memory 604 and executable by the processor(s) 602 to cause the processor(s) 602 to perform or initiate various operations. The data storage 620 may additionally store data that may be copied to memory 604 for use by the processor(s) 602 during the execution of the computer-executable instructions. Moreover, output data generated as a result of execution of the computer-executable instructions by the processor(s) 602 may be stored initially in memory 604, and may ultimately be copied to data storage 620 for non-volatile storage.
The data storage 620 may store one or more operating systems (O/S) 622; one or more optional database management systems (DBMS) 624; and one or more program module(s), applications, engines, computer-executable code, scripts, or the like such as, for example, one or more implementation modules 626, temperature control modules 627, gas control modules 629, and one or more communication modules 628. Some or all of these modules may be sub-modules. Any of the components depicted as being stored in data storage 620 may include any combination of software, firmware, and/or hardware. The software and/or firmware may include computer-executable code, instructions, or the like that may be loaded into the memory 604 for execution by one or more of the processor(s) 602. Any of the components depicted as being stored in data storage 620 may support functionality described in reference to correspondingly named components earlier in this disclosure.
Referring now to other illustrative components depicted as being stored in the data storage 620, the O/S 622 may be loaded from the data storage 620 into the memory 604 and may provide an interface between other application software executing on the controller 600 and hardware resources of the controller 600. More specifically, the O/S 622 may include a set of computer-executable instructions for managing hardware resources of the controller 600 and for providing common services to other application programs (e.g., managing memory allocation among various application programs). In certain example embodiments, the O/S 622 may control execution of the other program module(s) to for content rendering. The O/S 622 may include any operating system now known or which may be developed in the future including, but not limited to, any server operating system, any mainframe operating system, or any other proprietary or non-proprietary operating system.
The optional DBMS 624 may be loaded into the memory 604 and may support functionality for accessing, retrieving, storing, and/or manipulating data stored in the memory 604 and/or data stored in the data storage 620. The DBMS 624 may use any of a variety of database models (e.g., relational model, object model, etc.) and may support any of a variety of query languages. The DBMS 624 may access data represented in one or more data schemas and stored in any suitable data repository including, but not limited to, databases (e.g., relational, object-oriented, etc.), file systems, flat files, distributed datastores in which data is stored on more than one node of a computer network, peer-to-peer network datastores, or the like.
The optional I/O interface(s) 606 may facilitate the receipt of input information by the controller 600 from one or more I/O devices as well as the output of information from the controller 600 to the one or more I/O devices. The I/O devices may include any of a variety of components such as a display or display screen having a touch surface or touchscreen; an audio output device for producing sound, such as a speaker; an audio capture device, such as a microphone; an image and/or video capture device, such as a camera; and so forth. Any of these components may be integrated into the controller 600 or may be separate.
The controller 600 may further include one or more network interface(s) 608 via which the controller 600 may communicate with any of a variety of other systems, platforms, networks, devices, and so forth. The network interface(s) 608 may enable communication, for example, with one or more wireless routers, one or more host servers, one or more web servers, and the like via one or more of networks.
The antenna(s) 634 may include any suitable type of antenna depending, for example, on the communications protocols used to transmit or receive signals via the antenna(s) 634. Non-limiting examples of suitable antennas may include directional antennas, non-directional antennas, dipole antennas, folded dipole antennas, patch antennas, multiple-input multiple-output (MIMO) antennas, or the like. The antenna(s) 634 may be communicatively coupled to one or more transceivers 612 or radio components to which or from which signals may be transmitted or received. Antenna(s) 634 may include, without limitation, a cellular antenna for transmitting or receiving signals to/from a cellular network infrastructure, an antenna for transmitting or receiving Wi-Fi signals to/from an access point (AP), a Global Navigation Satellite System (GNSS) antenna for receiving GNSS signals from a GNSS satellite, a Bluetooth antenna for transmitting or receiving Bluetooth signals including BLE signals, a Near Field Communication (NFC) antenna for transmitting or receiving NFC signals, a 900 MHz antenna, and so forth.
The transceiver(s) 612 may include any suitable radio component(s) for, in cooperation with the antenna(s) 634, transmitting or receiving radio frequency (RF) signals in the bandwidth and/or channels corresponding to the communications protocols utilized by the controller 600 to communicate with other devices. The transceiver(s) 612 may include hardware, software, and/or firmware for modulating, transmitting, or receiving-potentially in cooperation with any of antenna(s) 634—communications signals according to any of the communications protocols discussed above including, but not limited to, one or more Wi-Fi and/or Wi-Fi direct protocols, as standardized by the IEEE 802.11 standards, one or more non-Wi-Fi protocols, or one or more cellular communications protocols or standards. The transceiver(s) 612 may further include hardware, firmware, or software for receiving GNSS signals. The transceiver(s) 612 may include any known receiver and baseband suitable for communicating via the communications protocols utilized by the controller 600. The transceiver(s) 612 may further include a low noise amplifier (LNA), additional signal amplifiers, an analog-to-digital (A/D) converter, one or more buffers, a digital baseband, or the like.
Referring now to functionality supported by the various program module(s) depicted in
The temperature control module(s) 627 may include computer-executable instructions, code, or the like that responsive to execution by one or more of the processor(s) 602 may perform functions including, but not limited to, receiving input such as user input or sensor input used to inform a temperature setting and/or operational setting and monitor operation of the gas furnace to achieve a certain temperature and/or operational setting.
The communication module(s) 628 may include computer-executable instructions, code, or the like that responsive to execution by one or more of the processor(s) 602 may perform functions including, but not limited to, communicating with one or more devices, for example, via wired or wireless communication, communicating with mobile devices, communicating with servers (e.g., remote servers), communicating with remote datastores and/or databases, sending or receiving notifications or commands/directives, communicating with cache memory data, communicating with user devices, and the like.
The gas control module(s) 629 may include computer-executable instructions, code, or the like that responsive to execution by one or more of the processor(s) 602 may perform functions including, but not limited to, operating the gas furnace to achieve a desired temperature and/or operational setting or mode. For example, pump operation module 629 may perform calibration checks on a pressure transducer and/or may adjust the gas valve.
Although specific embodiments of the disclosure have been described, one of ordinary skill in the art will recognize that numerous other modifications and alternative embodiments are within the scope of the disclosure. For example, any of the functionality and/or processing capabilities described with respect to a particular device or component may be performed by any other device or component. Further, while various illustrative implementations and architectures have been described in accordance with embodiments of the disclosure, one of ordinary skill in the art will appreciate that numerous other modifications to the illustrative implementations and architectures described herein are also within the scope of this disclosure.
Certain aspects of the disclosure are described above with reference to block and flow diagrams of systems, methods, apparatuses, and/or computer program products according to example embodiments. It will be understood that one or more blocks of the block diagrams and flow diagrams, and combinations of blocks in the block diagrams and the flow diagrams, respectively, may be implemented by execution of computer-executable program instructions. Likewise, some blocks of the block diagrams and flow diagrams may not necessarily need to be performed in the order presented, or may not necessarily need to be performed at all, according to some embodiments. Further, additional components and/or operations beyond those depicted in blocks of the block and/or flow diagrams may be present in certain embodiments.
Accordingly, blocks of the block diagrams and flow diagrams support combinations of means for performing the specified functions, combinations of elements or steps for performing the specified functions, and program instruction means for performing the specified functions. It will also be understood that each block of the block diagrams and flow diagrams, and combinations of blocks in the block diagrams and flow diagrams, may be implemented by special-purpose, hardware-based computer systems that perform the specified functions, elements or steps, or combinations of special-purpose hardware and computer instructions.
Program module(s), applications, or the like disclosed herein may include one or more software components, including, for example, software objects, methods, data structures, or the like. Each such software component may include computer-executable instructions that, responsive to execution, cause at least a portion of the functionality described herein (e.g., one or more operations of the illustrative methods described herein) to be performed.
A software component may be coded in any of a variety of programming languages. An illustrative programming language may be a lower-level programming language such as an assembly language associated with a particular hardware architecture and/or operating system platform. A software component comprising assembly language instructions may require conversion into executable machine code by an assembler prior to execution by the hardware architecture and/or platform.
Another example programming language may be a higher-level programming language that may be portable across multiple architectures. A software component comprising higher-level programming language instructions may require conversion to an intermediate representation by an interpreter or a compiler prior to execution.
Other examples of programming languages include, but are not limited to, a macro language, a shell or command language, a job control language, a script language, a database query or search language, or a report writing language. In one or more example embodiments, a software component comprising instructions in one of the foregoing examples of programming languages may be executed directly by an operating system or other software component without having to be first transformed into another form.
A software component may be stored as a file or other data storage construct. Software components of a similar type or functionally related may be stored together such as, for example, in a particular directory, folder, or library. Software components may be static (e.g., pre-established or fixed) or dynamic (e.g., created or modified at the time of execution).
Software components may invoke or be invoked by other software components through any of a wide variety of mechanisms. Invoked or invoking software components may comprise other custom-developed application software, operating system functionality (e.g., device drivers, data storage (e.g., file management) routines, other common routines, and services, etc.), or third-party software components (e.g., middleware, encryption, or other security software, database management software, file transfer or other network communication software, mathematical or statistical software, image processing software, and format translation software).
Software components associated with a particular solution or system may reside and be executed on a single platform or may be distributed across multiple platforms. The multiple platforms may be associated with more than one hardware vendor, underlying chip technology, or operating system. Furthermore, software components associated with a particular solution or system may be initially written in one or more programming languages, but may invoke software components written in another programming language.
Computer-executable program instructions may be loaded onto a special-purpose computer or other particular machine, a processor, or other programmable data processing apparatus to produce a particular machine, such that execution of the instructions on the computer, processor, or other programmable data processing apparatus causes one or more functions or operations specified in the flow diagrams to be performed. These computer program instructions may also be stored in a CRSM that upon execution may direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means that implement one or more functions or operations specified in the flow diagrams. The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational elements or steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process.
Additional types of CRSM that may be present in any of the devices described herein may include, but are not limited to, programmable random access memory (PRAM), SRAM, DRAM, RAM, ROM, electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the information and which can be accessed. Combinations of any of the above are also included within the scope of CRSM. Alternatively, computer-readable communication media (CRCM) may include computer-readable instructions, program module(s), or other data transmitted within a data signal, such as a carrier wave, or other transmission. However, as used herein, CRSM does not include CRCM.
Although embodiments have been described in language specific to structural features and/or methodological acts, it is to be understood that the disclosure is not necessarily limited to the specific features or acts described. Rather, the specific features and acts are disclosed as illustrative forms of implementing the embodiments. Conditional language, such as, among others, “can,” “could,” “might,” or “may,” unless specifically stated otherwise, or otherwise understood within the context as used, is generally intended to convey that certain embodiments could include, while other embodiments do not include, certain features, elements, and/or steps. Thus, such conditional language is not generally intended to imply that features, elements, and/or steps are in any way required for one or more embodiments or that one or more embodiments necessarily include logic for deciding, with or without user input or prompting, whether these features, elements, and/or steps are included or are to be performed in any particular embodiment.
This application claims the benefit of U.S. Application No. 63/534,008, filed Aug. 22, 2023, the entirety of which is incorporated herein by reference.
Number | Date | Country | |
---|---|---|---|
63534008 | Aug 2023 | US |