CENTRAL ALARM (CA) UNIT IN A GAS MONITORING SYSTEM INCLUDING GAS SENSORS AND GAS SENSOR CONTROLLERS

A central alarm unit in a gas monitoring system includes a gas sensor controller monitoring module that receives from each gas sensor controller aggregated status information of gas sensors connected to the gas sensor controller and that causes display of gas sensor controller graphical indicators. Each gas sensor controller graphical indicator corresponds to the aggregated status information of gas sensors connected to the respective gas sensor controller. The gas sensor controller monitoring module also receives a command requesting disaggregated status information of the gas sensors connected to the respective gas sensor controller. The unit further includes a gas sensor monitoring module that receives from each gas sensor controller disaggregated status information of the gas sensors connected to the respective gas sensor controller and that causes display of gas sensor graphical indicators. Gas sensor graphical indicators correspond to the disaggregated status information of respective gas sensors.

DETAILED DESCRIPTION

FIG. 1illustrates a schematic drawing of an exemplary gas monitoring system10. The system10includes gas monitoring stations20, each of which includes one or more gas sensors22. The system10also includes multiple gas sensor controllers14. Each gas sensor controller14may control multiple gas sensors22. Communication between gas sensor controllers14and corresponding gas sensors22is provided by a communication link15, such as a cable or wireless network link, between the gas sensor controller14and the gas sensors22.

In the embodiment ofFIG. 1, each of the gas monitoring stations20includes one or two gas sensors22. In other embodiments, the system10may include other combinations of gas sensors per monitoring station20, including one, two, three, or more gas sensors per monitoring station20.

The gas sensor controllers14convert output signals from the gas sensors22into signals representative of gas concentration thereby enabling detection of hazardous gas concentrations. The gas sensor controllers14may also issue local alarms to workers in the area where the sensor controller14resides. The gas sensor controllers14may also control a local alarm device17that may be activated if one or more gas sensors22detect a dangerous gas condition. The gas sensor controller14may further include a display18that may locally give additional information regarding the status of the respective gas sensor controller14and the gas sensors22connected to the particular gas sensor controller14.

Gas sensor controllers14may organize or map gas sensors22connected to the respective gas sensor controllers14in gas monitoring zones, which are discussed below in more detail. These gas monitoring zones may corresponding to and may mimic the layout of physical or geographical locations being monitored. The gas monitoring zones may assist users in better perceiving or understanding gas conditions at the facility or facilities where the gas sensors22reside.

In the illustrated embodiment, the system10includes an optional calibration and testing unit16. The calibration and testing unit16may include, among other elements, a supply of testing span gas (also referred to as calibration gas) and a supply of testing zero gas (also referred to as clearance gas). Embodiments where the calibration and testing unit16is supplied such as that illustrated inFIG. 1include a gas distribution network connecting the gas sensors22to the calibration and testing unit16through conduits34and36to deliver the testing span and zero gases from the calibration and testing unit16to the one or more sensors22.

The system10further includes a central alarm (CA) unit that is located at a location remote from the gas sensor controllers14and the gas sensors22. The CA unit40connects to the gas sensor controllers14. Communication between the CA unit40and the gas sensor controllers14is provided by communication links35such as cable or wireless network links. The CA unit40may communicate with multiple gas sensor controllers14and, via the gas sensor controllers14, to multiple gas sensors22.

The CA unit40receives output signals that are representative of gas alarms from the gas sensor controllers14thereby enabling remote monitoring of hazardous gas conditions. Based on the received signals, the CA unit40may issue or display alarms at the remote location. The CA unit40may control devices (not shown) remotely that may be activated if a gas sensor22detects a dangerous gas condition and thus the corresponding gas sensor controller14issues an alarm. The CA unit may include a display48that remotely present information regarding the status of the system10including respective gas sensor controllers14connected to the CA unit40and gas sensors22connected to the gas sensors controllers14.

In one embodiment, the CA unit40also includes the capability of communicating electronic messages (e.g., email, text messages, and so on) to remote computers. The electronic messages may include information representative of gas alarms received from the gas sensor controllers14, thereby enabling monitoring of hazardous gas conditions at any location at which an electronic message may be received. The electronic messages may include information representative of gas alarms in text form or in graphical or pictorial form to give recipients of the electronic messages a better understanding of the gas conditions at the facility or facilities where the gas sensors22reside. In one embodiment, the electronic messages include information representative of gas alarms in graphical form arranged by gas monitoring zones as disclosed in more detail below.

FIG. 2illustrates a block diagram of the exemplary gas monitoring system10. As discussed above, the system10includes gas sensors22, gas sensor controllers14, and the CA unit40.

In the illustrated embodiment, the CA unit40includes a communications module41that communicates with the gas sensor controllers14, which in turn, as discussed above, communicate with respective gas sensors22. In one embodiment, the communications module41also communicates with remote computers through a network (e.g., intranet, Internet, etc.).

The exemplary CA unit40further includes a gas sensor controller monitoring module42that receives from each gas sensor controller14aggregated status information of the gas sensors22operatively connected to the respective gas sensor controller14. The gas sensor controller monitoring module42may also cause graphical display of information relating to the aggregated status information. In one embodiment, the CA unit40includes the display48(seeFIG. 1) and the sensor controller monitoring module42causes graphical display of information relating to the aggregated status information on the display48. In other embodiments, the sensor controller monitoring module42causes graphical display of information relating to the aggregated status information on a display or displays other than the display48.

For example,FIG. 3illustrates an exemplary screen display50that the gas sensor controller monitoring module42may cause to be displayed on the display48. In the illustrated embodiment, a gas sensor controller graphical indicator52corresponding to the aggregated status information of gas sensors22operatively connected to the respective gas sensor controller14is displayed. In the illustrated embodiment, the gas sensor controller graphical indicator52corresponds to a gas sensor controller14labeled BAT_C. The gas sensor controller graphical indicator52aggregates the status information of the respective gas sensors22in the sense that the gas sensor controller graphical indicator52is displayed in, for example, a particular color that indicates the aggregated alarm status of gas sensors22operatively connected to the gas sensor controller14labeled BAT_C.

In the illustrated example, a Gas Services section54corresponding to the respective gas sensor controller14(in the illustrated embodiment the gas sensor controller labeled BAT_C) is also displayed in the screen display50. The Gas Services section54indicates that the gas sensor controller labeled BAT_C is operatively connected to at least two gas sensors corresponding to channels 1 and 16 of the gas sensor controller labeled BAT_C.

In the illustrated embodiment, the Gas Services section54lists channel 16 of the gas sensor controller14labeled BAT_C as an LEL type gas sensor and being on a High alarm state. The Gas Services section54further lists the Date & Time at which the alarm status of the channel 16 was updated. Similarly, the Gas Services section54lists channel 1 of the gas sensor controller14labeled BAT_C as a CO type gas sensor and being on a Low alarm state. The Gas Services section54further lists the Date & Time at which the alarm status of the channel 1 was updated.

In the illustrated embodiment, the gas sensor controller monitoring module42aggregates the alarm status information of the gas sensors channels 1 and 16 operatively connected to the gas sensor controller labeled BAT_C by displaying the gas sensor controller graphical indicator52in a particular color (e.g., red) to indicate that at least one gas sensor (i.e., channel 16) operatively connected to the gas sensor controller labeled BAT_C is in a High alarm state. In other examples (not shown), if the highest alarm level of the gas sensors operatively connected to the gas sensor controller labeled BAT_C is Low, the gas sensor controller graphical indicator52may be displayed in yellow. Similarly, if no alarm was present among the gas sensors operatively connected to the gas sensor controller labeled BAT_C, the gas sensor controller graphical indicator52may be displayed in green. Other gas sensor controller graphical indicators may include, for example, black for loss of communication, blue for a faulty gas sensor, and so on.

In other embodiments, the gas sensor controller monitoring module42may aggregate the alarm status information of the gas sensors operatively connected to the gas sensor controller labeled BAT_C by displaying the gas sensor controller graphical indicator52in a particular pattern or a particular shape, and so on.

The gas sensor controller monitoring module42may further receive a command requesting disaggregated status information of the gas sensors22operatively connected to the respective gas sensor controller14. In the example ofFIG. 3, a user may select the gas sensor controller graphical indicator52to request disaggregated status information of the gas sensors operatively connected to the gas sensor controller labeled BAT_C.

With continued reference toFIG. 2, the CA unit40further includes a gas sensor monitoring module43that receives from each gas sensor controller14disaggregated status information of the gas sensors22operatively connected to the respective gas sensor controller14. Upon the gas sensor controller monitoring module42receiving, as discussed above, the command requesting disaggregated status information of the gas sensors22operatively connected to the respective gas sensor controller14, the gas sensor monitoring module43causes display of gas sensor graphical indicators corresponding to the disaggregated status information of the gas sensors22.

For example,FIG. 4illustrates an exemplary screen display60that the gas sensor monitoring module43may cause to be displayed on the display48of the CA unit40. In the illustrated embodiment, gas sensor graphical indicators62, an example of which are indicators62aand62b, are displayed. The gas sensor graphical indicators62correspond to the disaggregated status information of each of the gas sensors22operatively connected to the respective gas sensor controller14(in this case the gas sensor controller labeled BAT_C).

The gas sensor graphical indicators62disaggregate the status information of the respective gas sensors22because each of the gas sensor graphical indicators62includes information regarding a specific gas sensor. In the illustrated embodiment, the gas sensor graphical indicator62acorresponds to the disaggregated status information of the gas sensor22associated with channel 1 of the gas sensor controller labeled BAT_C, while the gas sensor graphical indicator62bcorresponds to the disaggregated status information of the gas sensor22associated with channel 16 of the gas sensor controller labeled BAT_C. Moreover, each of the gas sensor graphical indicators62is displayed in, for example, a particular color that indicates the alarm status of the specific gas sensor22.

In the illustrated example, the screen display60illustrates that the gas sensor controller labeled BAT_C is operatively connected to forty two gas sensors corresponding to channels 1-42 of the gas sensor controller labeled BAT_C. A gas sensor graphical indicator62indicates a gas reading associated with the respective corresponding gas sensor22. For example, the gas sensor graphical indicator62aindicates a gas reading of 76.0 for the gas sensor corresponding to channel 1 of the gas sensor controller labeled BAT_C. Similarly, the gas sensor graphical indicator62bindicates a gas reading of 11.0 for the gas sensor corresponding to channel 16 of the gas sensor controller labeled BAT_C. A gas sensor graphical indicator62further indicates a type of gas sensor (e.g., LEL or CO) of the gas sensors22.

In the illustrated embodiment, the gas sensor monitoring module43disaggregates the alarm status information of the gas sensors22corresponding to channels 1-42 of the gas sensor controller labeled BAT_C by displaying a gas sensor graphical indicator62in a particular color. This is similar to the discussion above regarding gas sensor controller graphical indicators52(i.e., red for High alarm, yellow for Low alarm, green for no alarm, black for loss of communication, blue for a faulty gas sensor, etc.) In other embodiments, the gas sensor graphical indicators62may be displayed in a particular pattern or a particular shape, and so on to indicate alarm status of the specific gas sensor22.

In one embodiment, the CA unit40or the gas sensor controller14organizes or maps gas sensors22operatively connected to the gas sensor controller14in monitoring zones that each includes one or more gas sensors22.

With continued reference toFIG. 2, the CA unit40further includes a monitoring zone mapping module44that receives from each gas sensor controller14disaggregated status information of the gas sensors22operatively connected to the gas sensor controller14. The monitoring zone mapping module44, upon the gas sensor controller monitoring module42receiving the command requesting disaggregated status information of the gas sensors22operatively connected to the gas sensor controller14, causes display of gas sensor graphical indicators62arranged as groups corresponding to the monitoring zones.

Back to the example ofFIG. 4, notice that the gas sensor graphical indicators62are arranged as groups labeled CONTROL ROOM, STACK, GAS ANALYZER, MAIN, AREA A, BASEMENT, and AREA B. These groups of gas sensors correspond to monitoring zones that have been so arranged for user ease and convenience as well as to improve efficiency and efficacy of gas monitoring throughout the monitored facility and remotely to the monitored facility.

With continued reference toFIG. 2, the CA unit40further includes a remote gas monitoring module45that generates gas monitoring information messages. The gas monitoring information messages may be generated upon the aggregated status information or the disaggregated status information indicating that at least one gas sensor22is in alarm status. The remote gas monitoring module45further causes the communications module41to transmit the gas monitoring information messages to remote locations.

FIG. 5illustrates an exemplary simplified gas monitoring information message70that includes aggregated or disaggregated alarm status information of the alarm sensors22to thereby provide central level status information to remote locations.

In the illustrated embodiment, the gas monitoring information message70lists the gas sensor controller14associated with the gas sensor22(in the illustrated case the gas sensor controller labeled BAT_C), the channel of the gas sensor controller14to which the gas sensor22corresponds (in the illustrated case channel 16), the type of gas sensor22(in the illustrated case LEL), the date and time at which the alarm status of the alarm sensor22in channel 16 was updated, and the type of alarm (in this case High).

In one embodiment (not shown), the gas monitoring information message70includes data corresponding to the aggregated or disaggregated status information arranged in groups corresponding to monitoring zones to thereby provide central level status information to remote locations organized by monitoring zones. In another embodiment (not shown), the gas monitoring information message70includes data corresponding to the aggregated or disaggregated status information including gas sensor graphical indicators similar to those described above in reference to the screen display60ofFIG. 4. The gas sensor graphical indicators may be arranged in groups corresponding to monitoring zones to thereby provide central level status information to remote locations in graphical form and organized by monitoring zones.

Example methods may be better appreciated with reference to the flow diagram ofFIG. 6. While for purposes of simplicity of explanation, the illustrated methodologies are shown and described as a series of blocks, it is to be appreciated that the methodologies are not limited by the order of the blocks, as some blocks can occur in different orders or concurrently with other blocks from that shown or described. Moreover, less than all the illustrated blocks may be required to implement an example methodology. Furthermore, additional or alternative methodologies can employ additional, not illustrated blocks.

In the flow diagrams, blocks denote “processing blocks” that may be implemented with logic. The processing blocks may represent a method step or an apparatus element for performing the method step. A flow diagram does not depict syntax for any particular programming language, methodology, or style (e.g., procedural, object-oriented). Rather, a flow diagram illustrates functional information one skilled in the art may employ to develop logic to perform the illustrated processing. It will be appreciated that in some examples, program elements like temporary variables, routine loops, and so on, are not shown. It will be further appreciated that electronic and software applications may involve dynamic and flexible processes so that the illustrated blocks can be performed in other sequences that are different from those shown or that blocks may be combined or separated into multiple components. It will be appreciated that the processes may be implemented using various programming approaches like machine language, procedural, object oriented or artificial intelligence techniques.

In one example, methodologies are implemented as processor executable instructions or operations provided on a computer-readable medium. Thus, in one example, a computer-readable medium may store processor executable instructions operable to perform the method ofFIG. 6.

WhileFIG. 6illustrates various actions occurring in serial, it is to be appreciated that various actions illustrated could occur substantially in parallel. While a number of processes are described, it is to be appreciated that a greater or lesser number of processes could be employed and that lightweight processes, regular processes, threads, and other approaches could be employed. It is to be appreciated that other example methods may, in some cases, also include actions that occur substantially in parallel.

FIG. 6illustrates an exemplary method600for a central alarm (CA) unit in a gas monitoring system including gas sensors and gas sensor controllers operatively connected to respective gas sensors. At610, the method600includes receiving from a gas sensor controller a signal including aggregated status information of gas sensors operatively connected to the gas sensor controller. At620, the method600includes causing display of gas sensor controller graphical indicators. Each gas sensor controller graphical indicator corresponds to the aggregated status information of gas sensors operatively connected to the respective gas sensor controller. At630, the method600includes receiving a command requesting disaggregated status information of the gas sensors operatively connected to the respective gas sensor controller. If the command requesting disaggregated status information of the gas sensors is received, at640, the method600includes causing display of gas sensor graphical indicators. Each gas sensor graphical indicator corresponds to the disaggregated status information of the gas sensors operatively connected to the respective gas sensor controller.

At650, if at least one of the aggregated status information and the disaggregated status information indicates that at least one gas sensor is in alarm status, the method600includes, at660, generating a gas monitoring information message and transmitting the gas monitoring information message to a remote computer. Each gas monitoring information message includes data corresponding to the aggregated status information or the disaggregated status information to thereby provide central level status information to remote locations. In one embodiment, the gas monitoring information message includes gas sensor graphical indicators.

In one embodiment, the gas sensors operatively connected to the gas sensor controller are organized in monitoring zones that each includes one or more gas sensors and the gas sensor graphical indicators are displayed as groups corresponding to a monitoring zone. In one embodiment, the gas monitoring information messages include the gas sensor graphical indicators arranged in groups corresponding to the monitoring zones to thereby provide central level status information to remote locations organized by monitoring zones.

FIG. 7illustrates a schematic drawing of an exemplary central alarm (CA) unit40that includes a processor702, a memory704, and I/O Ports710operably connected by a bus708.

The processor702can be a variety of various processors including dual microprocessor and other multi-processor architectures. The memory704can include volatile memory or non-volatile memory. The non-volatile memory can include, but is not limited to, ROM, PROM, EPROM, EEPROM, and the like. Volatile memory can include, for example, RAM, synchronous RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), and direct RAM bus RAM (DRRAM).

The memory704can store processes714or data716, for example. The memory704can also store an operating system that controls and allocates resources of the CA unit40.

The bus708can be a single internal bus interconnect architecture or other bus or mesh architectures. While a single bus is illustrated, it is to be appreciated that CA unit40may communicate with various devices, logics, and peripherals using other busses that are not illustrated (e.g., PCIE, SATA, Infiniband, 1394, USB, Ethernet). The bus708can be of a variety of types including, but not limited to, a memory bus or memory controller, a peripheral bus or external bus, a crossbar switch, or a local bus. The local bus can be of varieties including, but not limited to, an industrial standard architecture (ISA) bus, a microchannel architecture (MCA) bus, an extended ISA (EISA) bus, a peripheral component interconnect (PCI) bus, a universal serial (USB) bus, and a small computer systems interface (SCSI) bus.

The CA unit40may interact with input/output devices via I/O Interfaces718and I/O Ports710. Input/output devices can include, but are not limited to, a keyboard, a microphone, a pointing and selection device, cameras, video cards, displays, gas sensor controllers14, network devices720, and the like. The I/O Ports710can include but are not limited to, serial ports, parallel ports, and USB ports.

The CA unit40can operate in a network environment and thus may be connected to network devices720via the I/O Interfaces718, or the I/O Ports710. Through the network devices720, the CA unit40may interact with a network. Through the network, the CA unit40may be logically connected to remote computers. The networks with which the CA unit40may interact include, but are not limited to, a local area network (LAN), a wide area network (WAN), and other networks. The network devices720can connect to LAN technologies including, but not limited to, fiber distributed data interface (FDDI), copper distributed data interface (CDDI), Ethernet (IEEE 802.3), token ring (IEEE 802.5), wireless computer communication (IEEE 802.11), Bluetooth (IEEE 802.15.1), Zigbee (IEEE 802.15.4) and the like. Similarly, the network devices720can connect to WAN technologies including, but not limited to, point to point links, circuit switching networks like integrated services digital networks (ISDN), packet switching networks, and digital subscriber lines (DSL). While individual network types are described, it is to be appreciated that communications via, over, or through a network may include combinations and mixtures of communications.

DEFINITIONS

The following includes definitions of selected terms employed herein. The definitions include various examples, forms, or both of components that fall within the scope of a term and that may be used for implementation. The examples are not intended to be limiting. Both singular and plural forms of terms may be within the definitions.

“Computer-readable medium,” as used herein, refers to a medium that participates in directly or indirectly providing signals, instructions or data. A computer-readable medium may take forms, including, but not limited to, non-volatile media, volatile media, and transmission media. Non-volatile media may include, for example, optical or magnetic disks, and so on. Volatile media may include, for example, optical or magnetic disks, dynamic memory and the like. Transmission media may include coaxial cables, copper wire, fiber optic cables, and the like. Transmission media can also take the form of electromagnetic radiation, like that generated during radio-wave and infra-red data communications, or take the form of one or more groups of signals. Common forms of a computer-readable medium include, but are not limited to, a floppy disk, a flexible disk, a hard disk, a magnetic tape, other magnetic media, a CD-ROM, other optical media, punch cards, paper tape, other physical media with patterns of holes, a RAM, a ROM, an EPROM, a FLASH-EPROM, or other memory chip or card, a memory stick, a carrier wave/pulse, and other media from which a computer, a processor or other electronic device can read. Signals used to propagate instructions or other software over a network, like the Internet, can be considered a “computer-readable medium.”

An “operable connection,” or a connection by which entities are “operably connected,” is one in which signals, physical communications, or logical communications may be sent or received. Typically, an operable connection includes a physical interface, an electrical interface, or a data interface, but it is to be noted that an operable connection may include differing combinations of these or other types of connections sufficient to allow operable control. For example, two entities can be operably connected by being able to communicate signals to each other directly or through one or more intermediate entities like a processor, operating system, a logic, software, or other entity. Logical or physical communication channels can be used to create an operable connection.

“Signal,” as used herein, includes but is not limited to one or more electrical or optical signals, analog or digital signals, data, one or more computer or processor instructions, messages, a bit or bit stream, or other means that can be received, transmitted or detected.

“Software,” as used herein, includes but is not limited to, one or more computer or processor instructions that can be read, interpreted, compiled, or executed and that cause a computer, processor, or other electronic device to perform functions, actions or behave in a desired manner. The instructions may be embodied in various forms like routines, algorithms, modules, methods, threads, or programs including separate applications or code from dynamically or statically linked libraries. Software may also be implemented in a variety of executable or loadable forms including, but not limited to, a stand-alone program, a function call (local or remote), a servelet, an applet, instructions stored in a memory, part of an operating system or other types of executable instructions. It will be appreciated by one of ordinary skill in the art that the form of software may depend, for example, on requirements of a desired application, the environment in which it runs, or the desires of a designer/programmer or the like. It will also be appreciated that computer-readable or executable instructions can be located in one logic or distributed between two or more communicating, co-operating, or parallel processing logics and thus can be loaded or executed in serial, parallel, massively parallel and other manners.

Suitable software for implementing the various components of the example systems and methods described herein may be produced using programming languages and tools like Java, Java Script, Java.NET, ASP.NET, VB.NET, Cocoa, Pascal, C#, C++, C, CGI, Perl, SQL, APIs, SDKs, assembly, firmware, microcode, or other languages and tools. Software, whether an entire system or a component of a system, may be embodied as an article of manufacture and maintained or provided as part of a computer-readable medium as defined previously. Another form of the software may include signals that transmit program code of the software to a recipient over a network or other communication medium. Thus, in one example, a computer-readable medium has a form of signals that represent the software/firmware as it is downloaded from a web server to a user. In another example, the computer-readable medium has a form of the software/firmware as it is maintained on the web server. Other forms may also be used.

“User,” as used herein, includes but is not limited to one or more persons, software, computers or other devices, or combinations of these.

Some portions of the foregoing detailed descriptions are presented in terms of algorithms and symbolic representations of operations on data bits within a memory. These algorithmic descriptions and representations are the means used by those skilled in the art to convey the substance of their work to others. An algorithm is here, and generally, conceived to be a sequence of operations that produce a result. The operations may include physical manipulations of physical quantities. Usually, though not necessarily, the physical quantities take the form of electrical or magnetic signals capable of being stored, transferred, combined, compared, and otherwise manipulated in a logic and the like.