BACKGROUND

[0001] Exemplary embodiments pertain to the art of hazard detectors and more specifically to a hazard detector socket.

[0002] An industrial smoke detector unit may consist of a detector socket to be mounted on a surface such as a ceiling and a detector that plugs into this socket. In a redundancy loop of such smoke detectors all electronics may be inside the detector.

[0003] When installing a loop based fire alarm system, the electrician traditionally mounts cabling and detector sockets, then insert detectors, and at this time the technician may identify what detector sits where. A technician may not be able to verify the electrical integrity of the loop before all loop units are in place unless the loop includes certain no-break sockets. A no-break socket is one in which a detector loop may not be broken when removing a smoke detector (i.e., for replacing, cleaning etc.). No-break sockets may use a micro switch that closes the detector loop when removing the detector to prevent losing fire detection or introducing a break in redundancy electronics when removing a detector. For example such micro switches connect the inputs and output from the opened socket.

BRIEF DESCRIPTION

[0004] Disclosed is a socket for removably connecting a hazard detector to a networked alarm system, the system having a first controller which is a system controller, the socket comprising: a housing having a base, an electrical interface for removably receiving the detector, and a second controller which is a socket controller mounted to the base, the socket controller maintaining wireless and/or wired network communications with the system controller when the detector is connected and disconnected.

[0005] In addition to one or more of the above disclosed features or as an alternate the socket includes a first plurality of electrical connectors mounted to the base for electrically connecting to the system and receiving power and data from the system whether the detector is connected or disconnected

[0006] In addition to one or more of the above disclosed features or as an alternate the electrical interface is a communications port for connecting to a data transfer port in the detector.

[0007] In addition to one or more of the above disclosed features or as an alternate wherein the socket includes a second plurality of electrical connectors for connecting the socket within a daisy-chain of hazard detectors disposed on a common circuit the system.

[0008] In addition to one or more of the above disclosed features or as an alternate wherein the socket includes a third plurality of electrical connectors for powering an indicator which is a visual and/or audio indicator.

[0009] In addition to one or more of the above disclosed features or as an alternate the socket controller actuates the indicator when a connected detector is in an alarm state.

[0010] Further disclosed is a networked alarm system comprising: a system controller, a circuit and at least one detector mounted to the circuit with the socket having one or more of the above disclosed features.

[0011] In addition to one or more of the above disclosed features or as an alternate the socket receives power and data over the circuit.

[0012] In addition to one or more of the above disclosed features or as an alternate the circuit is a loop circuit.

[0013] In addition to one or more of the above disclosed features or as an alternate the socket controller determines when a detector is disconnected therefrom and communicates a status update to the system controller, wherein the system controller communicates the status update to a third controller over a telecommunications network, and wherein the third controller is a fire system controller.

[0014] Further disclosed is a method for removably connecting a hazard detector to a networked alarm system, the system having a first controller which is a system controller, the method comprising: removably connecting the hazard detector to a socket having one or more of the above disclosed features. Further disclosed is a method of configuring the networked alarm system, the system including one or more of the above disclosed features.

BRIEF DESCRIPTION OF THE DRAWINGS

[0015] The following descriptions should not be considered limiting in any way. With reference to the accompanying drawings, like elements are numbered alike:

[0016] FIG. 1 illustrates an alarm socket according to an embodiment;

[0017] FIG. 2 illustrates a networked alarm system according to an embodiment; and

[0018] FIG. 3 illustrates various electronic features utilized in electronic controllers according to an embodiment.

DETAILED DESCRIPTION

[0019] A detailed description of one or more embodiments of the disclosed apparatus and method are presented herein by way of exemplification and not limitation with reference to the Figures.

[0020] Turning to FIGS. 1 and 2, disclosed is a socket 100 for removably connecting a hazard detector 105 (which in this type of configuration may be referred to as a head unit) to a networked alarm system 110. The system 110 may be a looped circuit 111 with a plurality of daisy-chained detectors including the hazard detector 105. The hazard detector 105 may be a smoke detector, beacon, sounder, an input/output device, etc. In the illustrated embodiment the detector 105 is a smoke detector. The system 110 may be an intelligent alarm system which has a first controller 115 which is a system controller.

[0021] With further reference to FIG. 1, the socket 100 may comprise a housing 120 having a base 125. The housing may be generally cylindrical and the base may be attachable to a ceiling. A first plurality of electrical connectors 130 may be mounted to the base 125. The connectors 130 may be used for electrically connecting the socket to the system 110 to receive power. Within the scope of the disclosure are wireless and wired network connections for connecting the socket 100 to the system 110.

[0022] With the connectors 130, the socket 100 may continuously receive available power from the networked alarm system 110 when the detector 105 is connected and disconnected. By preventing a break in the system 110, the socket 100 secures the continued use of the redundant power lines in the loop.

[0023] An electrical interface 135 may be provided for removably receiving the detector 105. In addition a second controller 140 which may be a socket controller is mounted to the base 125. The socket controller 140 may maintain wired or wireless communications with the system controller 115 when the hazard detector 105 is connected and disconnected. As a result, intelligent communications with the socket 100 may occur in the absence of the detector.

[0024] The electrical interface 135 may be a communication port or more specifically a serial port for connecting to a data transfer port 137 in the detector 105. Such standardized port connections may enable relatively quick interchanging of detectors for example to update or to change the type of detector or communication electronics within the socket 100. It is within the scope of the disclosure to use a smoke detector, a heat detector, or other hazard detector with the socket 100.

[0025] A second plurality of electrical connectors 145 may be provided for connecting the socket 100 to the circuit 111 to provide power to additional detectors in the daisy-chain. A third plurality of electrical connectors 150 are included for powering an indicator 155 which is a visual and/or audio indicator 155. The socket controller 140 actuates the indicator 155 when a connected detector 105 is in an alarm state. The indicator 155 may be a light emitting diode (LED).

[0026] Other features of the disclosed embodiments may include that the housing 120 has one or more mechanical connectors 156 for fixedly receiving the detector 105. The mechanical connectors 156 may be flanges, protrusions, tabs or the like.

[0027] Turning to FIG. 2 the circuit 111 may, at one time or another be in a configuration where various sockets such as sockets 105, 157, etc., are not fitted with a head unit. At the same time, other head units may be installed in one or more sockets of the type disclosed herein such as with detector 158, sounder 159 and beacon 160. (As indicated head units including input/output devices, etc. are within the scope of the disclosure.) Yet additionally, a legacy style hazard detector 161 may also be in the circuit 1 11. Advantageously with the configuration of FIG. 2, uninterrupted power and data may be communicated throughout the circuit 111, to each socket of the type disclosed herein, each head unit attached to such socket, and each legacy type hazard detector.

[0028] As further illustrated in FIG. 2, other features of the disclosed system 110 may include a fire alarm panel 164 that includes the system controller 1 15. The socket controller 140 may determine when a detector 105 is disconnected therefrom and communicate a status update to the system controller 115. The system controller 115 may communicate the status update to a third controller 165 over a telecommunications network 170. The third controller 165 may be a fire system controller 165 such as at a remote monitoring station.

[0029] The above disclosed system 100 separates field communication from the detector/sounder/beacon connected to the socket. One advantage of this configuration may be implementing at a later stage a new field communication protocol, and reusing the detector/ sounder/beacon. The socket may be adapted for other existing field protocols, including wired and wireless protocols. Beneficially any detector/sounder/beacon, and regulatory certifications associated with the same, may be reused.

[0030] Turning now to FIG. 3, and as indicated above, the embodiments herein may include a plurality of controllers including the first controller 1 15, the second controller 140 and the third controller 165, wherein at least the first controller 115 and third controller 165 communicate over the network 170. The plurality of controllers may have substantially the same technology features. Accordingly, features of the plurality of controllers may be disclosed hereinafter with reference to the first controller 115, which may be generally referred to hereinafter as controller 115.

[0031] The controller 115 may be a computing device that includes processing circuitry that may further include an application specific integrated circuit (ASIC), an electronic circuit with one or more elemental circuit components such as resistors, an electronic processor (shared, dedicated, or group) 300 and memory 305 that executes one or more software algorithms or firmware algorithms and programs, contains relevant data which may be dynamically collected or disposed in one or more look-up tables, a combinational logic circuit that contains one or more operational amplifiers, and/or other suitable interfaces and components that provide the described functionality. For example, the processor 300 processes data stored in the memory 305 and employs the data in various control algorithms, diagnostics and the like.

[0032] The controller 115 may further include, in addition to a processor 300 and memory 305, one or more input and/or output (I/O) device interface(s) 310 that are communicatively coupled via an onboard (local) interface to communicate among the plurality of controllers. The onboard interface may include, for example but not limited to, an onboard system bus 315, including a control bus 320 (for inter-device communications), an address bus 325 (for physical addressing) and a data bus 330 (for transferring data). That is, the system bus 315 enables the electronic communications between the processor 300, memory 305 and I/O connections 310. The I/O connections 310 may also include wired connections and/or wireless connections. The onboard interface may have additional elements, which are omitted for simplicity, such as controllers, buffers (caches), drivers, repeaters, and receivers to enable electronic communications.

[0033] In operation, the processor 300 onboard the controller 115 may be configured to execute software algorithms stored within the memory 305, to communicate data to and from the memory 305, and to generally control computing operations pursuant to the software algorithms. The algorithms in the memory 305, in whole or in part, may be read by the processor 300, perhaps buffered within the processor 300, and then executed. The processor 300 may include hardware devices for executing the algorithms, particularly algorithms stored in memory 305. The processor 300 may be a custom made or a commercially available processor 300, a central processing units (CPU), an auxiliary processor among several processors associated with computing devices, semiconductor based microprocessors (in the form of microchips or chip sets), or generally any such devices for executing software algorithms.

[0034] The memory 305 onboard the controller 115 may include any one or combination of volatile memory elements (e.g., random access memory (RAM, such as DRAM, SRAM, SDRAM, VRAM, etc.)) and/or nonvolatile memory elements (e.g., ROM, hard drive, tape, CD-ROM, etc.). Moreover, the memory 305 may incorporate electronic, magnetic, optical, and/or other types of storage media. The memory 305 may also have a distributed architecture, where various components are situated remotely from one another, but may be accessed by the processor 300.

[0035] The software algorithms in the memory 305 onboard the controller 115 may include one or more separate programs, each of which includes an ordered listing of executable instructions for implementing logical functions. A system component embodied as software algorithms may be construed as a source program, executable program (object code), script, or any other entity comprising a set of instructions to be performed. When constructed as a source program, the software algorithms may be translated via a compiler, assembler, interpreter, or the like, which may or may not be included within the memory. [0036] Some of the input/output (I/O) devices that may be coupled to the controller 115 using the system I/O Interface(s) 310, the wired interfaces and/or the wireless interfaces will now be identified but the illustration of which shall be omitted for brevity. Such I/O devices include, but are not limited to (i) input devices such as a keyboard, mouse, scanner, microphone, camera, proximity device, etc., (ii) output devices such as a printer, display, etc., and (iii) devices that communicate both as inputs and outputs, such as a modulator/ demodulator (modem; for accessing another device, system, or network), a radio frequency (RF) or other transceiver, a telephonic interface, a bridge, a router, etc.

[0037] Further, using the wireless connection, the controller 115 may communicate over the network 170 by applying electronic short range communication (SRC) protocols. Such protocols may include local area network (LAN) protocols and/or a private area network (PAN) protocols. LAN protocols include Wi-Fi technology, which is a technology based on the Section 802.11 standards from the Institute of Electrical and Electronics Engineers, or IEEE. PAN protocols include, for example, Bluetooth Low Energy (BTLE), which is a wireless technology standard designed and marketed by the Bluetooth Special Interest Group (SIG) for exchanging data over short distances using short-wavelength radio waves. PAN protocols also include Zigbee, a technology based on Section 802.15.4 protocols from the Institute of Electrical and Electronics Engineers (IEEE). More specifically, Zigbee represents a suite of high-level communication protocols used to create personal area networks with small, low-power digital radios for low-power low-bandwidth needs, and is best suited for small scale projects using wireless connections. Such wireless connection 330 may include Radio-frequency identification (RFID) technology, which is another SRC technology used for communicating with an integrated chip (IC) on an RFID smartcard.

[0038] One should note that the above disclosed architecture, functionality, and/or hardware operations of the controller 115 may be implemented using software algorithms. In the software algorithms, such functionality may be represented as a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that such modules may not necessarily be executed in any particular order and/or executed at all.

[0039] One should also note that any of the functionality of the controller 115 described herein can be embodied in any non-transitory computer-readable medium for use by or in connection with an instruction execution system, apparatus, or device, such as a computer-based system, processor-containing system, or other system that can fetch the instructions from the instruction execution system, apparatus, or device and execute the instructions. In the context of this document, a“computer-readable medium” contains, stores, communicates, propagates and/or transports the program for use by or in connection with the instruction execution system, apparatus, or device.

[0040] Further, the computer readable medium in the controller 115 may include various forms of computer readable memory 305. For example the computer readable memory 305 may be integral to an apparatus or device, which may include one or more semiconductors, and in which the communication and/or storage technology may be one or more of electronic, magnetic, optical, electromagnetic or infrared. More specific examples (a non-exhaustive list) of a computer-readable medium the illustration of which being omitted for brevity include a portable computer diskette (magnetic), a random access memory (RAM) (electronic), a read only memory (ROM) (electronic), an erasable programmable read-only memory (EPROM or Flash memory) (electronic), and a portable compact disc read-only memory (CDROM) (optical).

[0041] In addition, the above distributed system of controllers is not intended to be limiting. In one embodiment, each of the controllers on the same side of the network may be the same device such that no network there between is required. In one embodiment a single on-site controller is provided instead of the distributed system of controllers. In one embodiment the controllers on the same side of the network are controlled by servers located over the World Wide Web, using a cloud computing configuration. In one embodiment, the distributed controller network is hard-wired for all telecommunication services so that no wireless network is necessary. In one embodiment redundant wireless and wired networks are utilized which automatically switch between such services to minimize network congestion.

[0042] The above configuration provides placing all loop communication electronics in the socket, including short circuit isolators, voltage regulators etc. A communication bus in the detector connects the detector to the socket via a connector interface in the socket. The communication bus in the detector may be standardized so that the detector may be used with many different socket versions and the socket may receive different types of detectors. The disclosed embodiments enable the use of remote service tools (IR, led flashing, RFID etc.) on the socket. Thus the disclosed embodiments enable a technician to electrically connect the socket to obtain to complete loop electronics before detector is mounted.

[0043] Changing communications technologies (new technology, improvements) may be more easily implemented with independent detectors. The disclosed sockets may enable advanced loop diagnostics without mounting detectors (that is, before commissioning the loop or individual detectors). The disclosed sockets may provide universal connections to other loop units, sounders, strobes, I/O- modules, etc. Changing detectors at the end of a useful life cycle may be more efficient due to reusing communication modules.

[0044] The term“about” is intended to include the degree of error associated with measurement of the particular quantity based upon the equipment available at the time of filing the application.

[0045] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the present disclosure. As used herein, the singular forms“a”,“an” and“the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises” and/or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, element components, and/or groups thereof.

[0046] While the present disclosure has been described with reference to an exemplary embodiment or embodiments, it will be understood by those skilled in the art that various changes may be made and equivalents may be substituted for elements thereof without departing from the scope of the present disclosure. In addition, many modifications may be made to adapt a particular situation or material to the teachings of the present disclosure without departing from the essential scope thereof. Therefore, it is intended that the present disclosure not be limited to the particular embodiment disclosed as the best mode contemplated for carrying out this present disclosure, but that the present disclosure will include all embodiments falling within the scope of the claims.