Exemplary embodiments pertain to the art of detector loops and more specifically to a system and method for startup of a detector loop.
A traditional detector loop with many loop units (for example, more than one hundred loop units) may take many minutes to start. The process may involve consecutively starting each loop unit and having each loop unit test for a short circuit in the loop. Each unit, one at a time, may power up, identify itself, and test for a short circuit by closing an on-board short circuit isolator switch. Due to a relatively low loop communication speeds, this may be a time-consuming procedure.
Disclosed is a hazard detector electrically connected to a circuit, wherein the circuit includes: a plurality of circuit ends including a first end and a second end, and a plurality of detectors including the detector, wherein the detector is connected intermediate the plurality of circuit ends, a circuit driver connected to the plurality of circuit ends so that the circuit forms a loop circuit, the circuit driver including a first controller controlling one or more power sources to selectively provide power to the first end and the second end, and the detector comprising a second controller and a switch which is a short isolator switch that, when opened, breaks electrical continuity downstream of the detector, wherein the detector scans for a short at startup by receiving power, closing the switch, measuring one or more circuit parameters, and determining whether there is a short based on the one or more parameters, when there is a short, the detector transmits a first circuit communication that identifies the short.
In addition to one or more of the above features or as an alternate the detector when powered provides status by receiving a second circuit communication requesting an amount of elapsed time since receiving power and a unique detector identifier, and transmitting a third circuit communication responsive to the second circuit communication, including the amount of elapsed time and the unique detector identifier.
Further disclosed is a circuit comprising: a plurality of circuit ends including a first end and a second end, and a plurality of detectors including the above disclosed detector connected intermediate the plurality of circuit ends, a circuit driver connected to the plurality of circuit ends so that the circuit forms a loop circuit, the circuit driver including a first controller controlling one or more power sources to selectively provide power to the first end and the second end, and wherein the circuit driver scans circuit continuity during startup by: transmitting power to the first end, monitoring the second end, and when the circuit driver senses power at the second end, the circuit driver determines continuity exists.
In addition to one or more of the above features or as an alternate when the circuit driver determines continuity exists, the circuit driver maps circuit topology by: transmitting the second circuit communication from the first end, requesting from the plurality of detectors the amount of elapsed time since receiving power and the unique identifier for the detector, receiving, from each of the plurality of detectors, the third circuit communication responsive to the second circuit communication, including the amount of elapsed time and the unique detector identifier, and maps circuit topology based the unique detector identifiers and the elapsed time since receiving power.
In addition to one or more of the above features or as an alternate the circuit driver detects circuit discontinuity at startup by receiving the first circuit communication at the first end from the detector, thereby determining there is a circuit short, or failing to receive a circuit communication or sense power at the second end within a predetermined period of time, thereby determining there is a circuit break.
In addition to one or more of the above features or as an alternate when there is a circuit discontinuity, the circuit driver maps a first segment topology of the circuit from the first end to the circuit discontinuity by transmitting the second circuit communication, requesting the amount of elapsed time since receiving power and the unique detector identifier, receiving the third circuit communication responsive to the second circuit communication, including the amount of elapsed time and the unique detector identifier and mapping the first segment topology of the circuit between the first end and the discontinuity based the unique detector identifiers and the elapsed time since receiving power from the first end.
In addition to one or more of the above features or as an alternate when there is a circuit discontinuity, the circuit driver maps a second segment topology of the circuit from the second end to the circuit discontinuity, transmitting power to the second power end, detecting circuit discontinuity through the second end by receiving the first circuit communication at the second end from a second detector, thereby confirming there is a circuit short, and failing to receive a circuit communication within a predetermined period of time, thereby confirming there is a circuit break, transmitting the second circuit communication, requesting the amount of elapsed time since receiving power and the unique detector identifier, receiving the third circuit communication responsive to the second circuit communication, including the amount of elapsed time and the unique detector identifier, and mapping the second segment topology of the circuit between the second end and the discontinuity based the unique detector identifiers and the elapsed time since receiving power from the second end.
In addition to one or more of the above features or as an alternate the circuit driver determines a location of the circuit discontinuity combining the mapped first segment topology and mapped second segment topology of the circuit.
In addition to one or more of the above features or as an alternate the detector acknowledges receiving power at startup by issuing an acknowledgment pulse to the circuit.
In addition to one or more of the above features or as an alternate the detector scans for a circuit break at startup by failing to receive an acknowledgement pulse within a predetermined period of time.
Further disclosed is a method of scanning for a short at startup by a hazard detector electrically connected to a circuit, the circuit including one or more of the above disclosed features. Yet further disclosed is method of scanning circuit continuity at startup by a circuit driver electrically connected to a circuit, the circuit including one or more of the above disclosed features. Further disclosed is a method of acknowledging receiving power at startup by hazard detector electrically connected to a circuit, the circuit including one or more of the above disclosed features. Yet further disclosed is a method of detecting continuity by a circuit driver electrically connected to a circuit, the circuit including one or more of the above disclosed features.
The following descriptions should not be considered limiting in any way. With reference to the accompanying drawings, like elements are numbered alike:
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.
Turning to
The circuit 20 may include a circuit driver 45 connected to the plurality of circuit ends so that the circuit forms a loop circuit. The circuit 20 may further include a first controller 50 that may control, for example, a plurality of power sources including a first power source 55 and a second power source 60. The first power source 55 may selectively provide power to the first end 25 and the second power source 60 may selectively provide power to the second end 30. In an alternative embodiment power sources 55 and 60 may be the same power source, wherein the circuit driver 45 transmits the power from the single power source to the first and second outputs independently, and if desired simultaneously, using switches.
The detector 10, in contrast, may comprise a second controller 65 and a switch 70 which is a short isolator switch. When opened, the switch 70 may break electrical continuity downstream of the detector 10.
Turning to
Turning to
Step S300 may include step S305 of receiving a second circuit communication of requesting an amount of elapsed time since receiving power, for example as may be recorded on a counter. The request may also seek a unique detector identifier, such as a hardware address. The detector 10 at step S310 may transmit a third circuit communication responsive to the second circuit communication, which may include the amount of elapsed time and the unique detector identifier.
Turning to
Turning to
Turning to
Turning to
Turning to
With power at the second end 30, the circuit driver 45 may perform step S815 of detecting circuit discontinuity. Similar to the above step S600, step S815 may include step S820 of receiving the first circuit communication at the second end 30 from a second detector 85 (
After confirming the discontinuity on the second end 30, the circuit driver 45 may perform step S840 of transmitting the second circuit communication, requesting the amount of elapsed time since receiving power and the unique detector identifier. The circuit driver 45 may then perform step S845 of receiving the third circuit communication responsive to the second circuit communication. As before such communication may include the amount of elapsed time and the unique detector identifier.
The circuit driver 45 may then perform step S850 of the second segment topology 80 of the circuit 20 between the second end 30 and the discontinuity. As before the mapping may be based the unique detector identifiers and the elapsed time since receiving power from the second end 30. With the mapped topologies the circuit driver 45 may determine a location of the circuit discontinuity by combining the mapped first segment topology 75 and mapped second segment topology 80 of the circuit 20.
Turning to
In contrast in
By adding the features of
It is to be appreciated that combining the above disclosed embodiments can be accomplished by changing step S205 to “receiving power and emitting a pulse”. Similarly step S615 would recite “failing to receive a circuit communication, failing to receive a pulse within a predetermined period of time, or failing to sense power.” Such modifications would subsume
Turning now to
The controller 50 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) 1100 and memory 1105 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 1100 processes data stored in the memory 1105 and employs the data in various control algorithms, diagnostics and the like.
The controller 50 may further include, in addition to a processor 1100 and memory 1105, one or more input and/or output (I/O) device interface(s) 1110 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 1115, including a control bus 1120 (for inter-device communications), an address bus 1125 (for physical addressing) and a data bus 1130 (for transferring data). That is, the system bus 1115 enables the electronic communications between the processor 1100, memory 1105 and I/O connections 1110. The I/O connections 1110 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.
In operation, the processor 1100 onboard the controller 50 may be configured to execute software algorithms stored within the memory 1105, to communicate data to and from the memory 1105, and to generally control computing operations pursuant to the software algorithms. The algorithms in the memory 1105, in whole or in part, may be read by the processor 1100, perhaps buffered within the processor 1100, and then executed. The processor 1100 may include hardware devices for executing the algorithms, particularly algorithms stored in memory 1105. The processor 1100 may be a custom made or a commercially available processor 1100, 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.
The memory 1105 onboard the controller 50 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 1105 may incorporate electronic, magnetic, optical, and/or other types of storage media. The memory 1105 may also have a distributed architecture, where various components are situated remotely from one another, but may be accessed by the processor 1100.
The software algorithms in the memory 1105 onboard the controller 50 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.
Some of the input/output (I/O) devices that may be coupled to the controller 50 using the system I/O Interface(s) 1110, 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.
Further, using the wireless connection, the controller 50 may communicate over the network 54 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 1130 may include Radio-frequency identification (RFID) technology, which is another SRC technology used for communicating with an integrated chip (IC) on an RFID smartcard.
One should note that the above disclosed architecture, functionality, and/or hardware operations of the controller 50 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.
One should also note that any of the functionality of the controller 50 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.
Further, the computer readable medium in the controller 50 may include various forms of computer readable memory 1105. For example the computer readable memory 1105 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).
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 therebetween 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.
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.
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.
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.
Filing Document | Filing Date | Country | Kind |
---|---|---|---|
PCT/EP2018/066678 | 6/21/2018 | WO | 00 |