Patent Application
20250166490
This application claims priority to GB Application Serial No. 2317663.9, filed Nov. 17, 2023, and entitled “DATA LOGGING IN A FIRE ALARM SYSTEM,” the contents of which are hereby incorporated herein in the entirety.
The present disclosure relates to the logging of data in a fire alarm system.
Fire alarm systems, such as the fire alarm system 1 shown in
Multiple loops are generally installed from the fire alarm control panel 3, with each loop typically carrying the devices 4 to a different part of the premises. The loops typically provide power to the devices 4 on the loop, and convey instructions and data from the fire alarm control panel 3 to the individual devices 4, such as configuration data to all devices 4 or an alarm signal to the notification appliances 4b, and convey data from the devices 4 to the fire alarm control panel 3. Where the device 4 is a detector 4a, it generates a detector value corresponding to what the detector 4a is sensing, and the loop conveys the detector value to the fire alarm control panel 3. Other devices might generate values too.
The looped arrangement provides resilience to a break in an individual loop occurring during operation, and the voltage level between the wires in the loop are maintained sufficiently high to sustain all of the devices 4 around the complete loop. A single fire alarm control panel 3 can support multiple loops of addressable devices 4.
Faults can arise in the fire alarm system 1 which must be identified and resolved, which involves testing the integrity of the loops, and the correct operation of the devices 4 and the fire alarm control panel 3.
A fire alarm condition is indicated when the fire alarm control panel 3 determines that certain conditions are met by the values sent to it by the devices 4. A false alarm is raised when there is not a fire condition but the fire alarm control panel 3 processing the values indicates there is one. This false alarm could be raised for many reasons including poor detector type choice (smoke, heat, etc.) or by poor selection of an algorithm within the fire alarm control panel 3 which assesses the values against the criteria for a fire alarm condition. If the fire alarm system 1 reports unwanted alarm events, an engineer needs to investigate. Once the cause is explained, a technician can take the appropriate action.
The event log contains a record of events such as fire alarm conditions or faults which arise, and identifies when such conditions arose and which device was involved. Fire alarm systems do not have data storage sufficient to collect all available data over a long period of time, because, in fault-free operation, an enormous amount of data would be collected which would require costly large-scale storage.
Fire alarm technicians are known to connect laptop computers to control panels to collect the contents of logs and detector values over a short period of time, but this is generally limited in duration to one to two hours, by the fact that the laptop must generally be supervised by a person to prevent its theft.
An aim of the present disclosure is to permit detector values to be securely collected from the fire alarm control panel 3 over an extended period of time of more than a few hours, preferably extending to more than one day (a 24 hour period).
A data logging method in a fire alarm system comprising a data logger device that fits within the casing of a fire alarm control panel of the fire alarm system, the data logging method comprising communicating, via a data interface of the data logger device that is connected to a data connection of the fire alarm control panel, with one or more processors of the fire alarm control panel, to obtain detector values stored in one or more data stores of the fire alarm control panel, wherein the fire alarm system comprises one or more detectors communicatively coupled with the fire alarm control panel via a wired or wireless connection; and logging the detector values into one or more data stores of the data logger device.
The present disclosure permits detector values to be stored in the data logger device to be logged securely over an extended period of time.
In one aspect, a portable data memory device is connectable to the data logger device once it has logged detector values from the fire alarm control panel.
In one aspect, the data logger device comprises logger control software installed thereon before logging data.
Preferably, the data logger device is configured to obtain the detector values by requesting, from the fire alarm control panel, one or more most recently returned values from each of the one or more detectors.
Advantageously, the data logger device may learn addresses of the detectors without needing pre-configuration. For example, the data logger device may learn the addresses by requesting a detector value for each address that is configurable on each addressable loop that is connectable to the fire alarm control panel; and recording only the addresses which correspond to a detector being present on a connected addressable loop. In this way, pre-configuration of the data logger device is not required.
According to a second aspect, a fire alarm control panel of a fire alarm system includes: a casing; one or more processors; one or more data stores; a data connection; wherein the fire alarm system comprises one or more detectors communicatively coupled with the fire alarm control panel via a wired or wireless connection; and a data logger device within the casing of the fire alarm control panel, the data logger device having one or more data stores and a data interface that is connected to the data connection of the fire alarm control panel, wherein the data logger device is configured to: communicate, via the data interface of the data logger device that is connected to the data connection of the fire alarm control panel, with the one or more processors of the fire alarm control panel, to obtain detector values stored in the one or more data stores of the fire alarm control panel; and log the detector values into the one or more data stores of the data logger device.
Advantageously, the data logger device comprises logger control software installed thereon for managing communication with the fire alarm control panel, and for managing the operation of the data logger device.
Preferably, the data logger device is a single board computer.
In this disclosure, references to a single-board computer (SBC) are to a complete, functioning computer in which its microprocessor, input/output functions, memory, and other features are all built on a single circuit board, with RAM built in and with no expansion slots for peripherals. Examples of SBCs are the Raspberry Pi®, the Arduino® and the ASUS® Tinker Board.
The present disclosure will now be described by way of example only with reference to the accompanying drawings in which:
The one or more processors 7 control the operation of the fire alarm control panel 3. The one or more processors 7 communicate with each of the devices 4 by instructing communications to be sent to the devices 4 via the loop controller 10 (for those devices 4 that are communicatively coupled with the fire alarm control panel 3 via the wiring 2) or via the wireless transceiver 14 (for those devices 4 that are communicatively coupled with the fire alarm control panel 3 via the wireless network 15).
The loop controller 10 includes a plurality of ports for connection to the wiring 2. Communication received from the devices 4 by an applicable one of the loop controller 10 or the wireless transceiver 14 are communicated via the data bus 14 to the one or more data stores 8 and the one or more processors 7 which act according to their programming to determine any consequent actions. For example, if a detector 4a sends a communication giving a detector value which exceeds a threshold corresponding to a fire condition, the one or more processors 7 will instruct the loop controller 10 or the wireless transceiver 14, whichever applicable, to send an alarm signal to the notification appliances 4b, so as to alert people to the detection of a fire, and will instruct the one or more data stores 8 to record an alarm condition in the event log.
Communication with devices 4, whether on the wiring 2 or on the wireless network 15, takes place using a Command/Response protocol where the one or more processors 7 direct the loop controller 10 or the wireless transceiver 14, whichever applicable, to poll each of the devices 4 with an addressed command, and when a device 4 receives a command addressed for it, the device 4 carries out the instruction and sends a response on the wiring 2 or the wireless network 15, whichever applicable, for the fire alarm control panel 3 to receive. The command from the loop controller 10 or the wireless transceiver 14, whichever applicable, to a device 4 could, for example, instruct the device 4 to enter data into its memory, such as configuration data, or the command could instruct the device 4 to send some data to the fire alarm control panel 3 over the loop, or the command could request an alarm status if the device 4 is a detector 4a, or the command could request a value from the device 4 if the device 4 is a detector 4a, or the command could instruct the device 4 to sound an alarm if the device 4 is a notification appliance 4b. Every device 4 is polled about every 5 seconds.
The one or more data stores 8 include the event log which stores a record of significant events, such as an alarm condition or when a fault is identified. The log also records the time and date of the event, and the source of the event.
The one or more data stores 8 also store other data, including the values returned by the devices 4 when they are polled by the fire alarm control panel 3, and it is this data which the one or more processors 7 are described above as comparing with a threshold value to determine whether a fire condition exists. Since every device 4 is polled about every 5 seconds, to avoid collection of a very large amount of information, the value returned by a device 4 replaces or overwrites the value returned on the previous polling event so that only the most recent value is stored.
When faults arise in communication between the fire alarm control panel 3 and the devices 4 on the wiring 2 or on the wireless network 14, whichever applicable, for example, by errors in installation, or by noise, the cause can be difficult to diagnose because they are often intermittent, and because there is insufficient data. In this scenario, technicians typically rely on the event log in the one or more data stores 8 of the fire alarm control panel 3, but event logs contain a limited amount of information, and don't give the exact cause for communication failure. It has been determined that diagnosis of the cause can be aided by analysing the values returned to the fire alarm control panel 3 by the devices 4 over a longer period of time, for example for a day or a week.
The user interface 9 allows for a technician or other authorised person to enter data into the fire alarm control panel 3, and to view information about the status of the fire alarm system 1. For example, the user interface 9 will typically include a keypad and a display which is a combination of status lights and an LED screen.
A data connection 11 is present on the data bus 14 to allow other devices, such as diagnostic tools, to be plugged into the fire alarm system 1 with access to the data bus 14.
Since the one or more data stores 8 only retain the most recent values returned to the fire alarm control panel 3 by the devices 4, diagnosis of problems is constrained by the fact that values returned over a longer period are not available to a technician. To overcome this problem, and to ensure security of any data logging equipment, in the present aspects a data logger device 20 is used which is a single board computer, as defined above. The single board computer comprises one or more processors 21 (e.g., one or more CPUs), one or more data stores 22, a data interface 23, and a second data interface 24, all of which are connected to a data bus 25. The data logger device 20 also includes a power input 26 which supplies power to at least the one or more processors 21 and the one or more data stores 22. In some non-limiting aspects, the data logger device 20 is a Raspberry Pi loaded with control software stored on the one or more data stores 22 to control its operation. An essential characteristic of the data logger device 20 is that it is very compact and small enough to fit within the casing 6 of the fire alarm control panel 3.
The data logger device 20 is shown in
Step one 31 is to open the casing 6 of the fire alarm control panel 3.
Step two 32 is to place the data logger device 20 within the casing 6 of the fire alarm control panel 3. It might be appropriate to secure the data logger device 20 within the casing 6, for example, with zip ties.
Step three 33 is to connect the data interface 23 of the data logger device 20 to the data connection 11 of the fire alarm control panel 3 with a cable so that data can be passed from the data connection 11 to the data interface 23.
Step four 34 is to connect the power input 26 of the data logger device 20 to the power supply 12 within the casing 6 of the fire alarm control panel 3. However, the data logger device 20 could be battery powered, in which case, this step would not be required.
Step five 35 is to close the casing 6 of the fire alarm control panel 3 with the data logger device 20 located securely inside.
Step six 36 is the learning of what detectors 4a are in the fire alarm system 1 and the addresses of those detectors 4a. This is done by the one or more processors 21 of the data logger device 20 sending a request to the one or more processors 7 of the fire alarm control panel 3 for the value of a device having a first address, say Loop 1, address 001, via the data bus 25 of the data logger device 20, the data interface 23, the data connection 11, and the data bus 14 of the fire alarm control panel 3 for the current value held in the one or more data stores 8 for that device. If there is a detector at this address, the one or more data stores 8 return the detector value back to the data logger device 20 where that value is stored in the one or more data stores 22 together with the time and date of collection, and the identity of the device 4 that the value came from. If there is no detector with that address, the one or more data stores 8 report this to the data logger device 20, which ensures that no future requests are made corresponding to that address. The one or more processors 21 repeat this process with Loop 1, address 002 and all the other possible addresses, and log both the values of all the sensor devices 4a, and learn which addresses to request future values about, and which to exclude.
Step seven 37 of logging the values can then take place. It will be realised that, once steps one to four have been completed, the logging of data might be expected to start before the casing 6 is actually closed. Logging is done by the one or more processors 21 of the data logger device 20 sending a request to the one or more processors 7 of the fire alarm control panel 3 via the data bus 25 of the data logger device 20, the data interface 23, the data connection 11, and the data bus 14 of the fire alarm control panel 3 for the current value held in the one or more data stores 8 for a particular detector. The one or more data stores 8 return that value back to the data logger device 20 where that value is stored in the one or more data stores 22 together with the time and date of collection, and the identity of the detector 4 that the value came from. Some detectors have more than one sensing element, such as smoke and heat sensing elements, so more than one value might be available, in which case all of the values are stored by the data logger device 20. Once a value has been stored, the data logger device 20 requests the value of the next detector 4, and this is repeated until the values originating from all of the detectors 4 have been collected and stored.
It is important that the data logger device 20 doesn't put the fire alarm control panel 3 under too great a load as the fire alarm control panel 3 must remain fully operational during the logging. For this reason, the data logger device 20 throttles its requests. One way to do this is to request values at a frequency, for example, of X requests per second, at which it is known that the fire alarm control panel 3 is capable of remaining fully operational. An alternative is to have a timed pause following the receipt of a value before requesting the next one, say 0.2 s. The reason this is advantageous is that this functionality introduces a dynamic component to the requests because, if the fire alarm control panel 3 is under greater than average load, it will take longer to return a value, and this causes a reduction in the frequency of requests made to the fire alarm control panel 3 for values.
It will be appreciated that not all of the values will be stored in the data logger device 20 because the frequency of value logging will generally be less than the frequency at which they are acquired by the fire alarm control panel 3. However, enough data will be logged to make diagnosis of problems much easier, and the safe operation of the fire alarm control panel 3 will not be compromised by the logging process.
The data stored will include the time/date, device type, device address, monitored values, etc.
Step eight 38 is carried out once the data logger device 20 has been operating for a long enough time that the data logger device 20 will have collected sufficient amount of data, and includes reopening the casing 6.
Step ten 39 is to disconnect the data logger device 20 from the fire alarm control panel 3 and to remove it from the casing 6.
Step eleven 40 is to close the casing 6.
Step nine 41 is to download the data from the data logger device 20. This might be done in a number of ways. A portable data memory device can be plugged into the second data interface 24 in order to download the data onto the portable data memory device so that the data can then be analysed, for example, by being plugged into a laptop computer.
Alternatively, a laptop computer could be plugged directly into the second data interface 24 of the data logger 20 and download the data directly.
Once the data has been analysed, if a situation can be identified (e.g., a fault or cause of false alarms) based on the data which has been analysed, appropriate action can be taken.
Various further modifications to the above-described examples, whether by way of addition, deletion or substitution, will be apparent to the skilled person to provide additional examples, any and all of which are intended to be encompassed by the appended claims.
Referring to
As used herein, a processor, at least one processor, and/or one or more processors, individually, as a subgroup, or in combination, configured to perform or operable for performing a plurality of actions is meant to include at least two different processors able to perform different, overlapping or non-overlapping subsets of the plurality actions, or a single processor able to perform all of the plurality of actions. In one non-limiting example of multiple processors being able to perform different ones of the plurality of actions in combination, a description of a processor, at least one processor, and/or one or more processors configured or operable to perform actions X, Y, and Z may include at least a first processor configured or operable to perform a first subset of X, Y, and Z (e.g., to perform X) and at least a second processor configured or operable to perform a second subset of X, Y, and Z (e.g., to perform Y and Z). Alternatively, a first processor, a second processor, and a third processor may be respectively configured or operable to perform a respective one of actions X, Y, and Z. It should be understood that any combination of one or more processors each may be configured or operable to perform any one or any combination of a plurality of actions.
The one or more processors 402 may be a micro-controller and/or may include a single or multiple set of processors or multi-core processors. Moreover, the one or more processors 402 may be implemented as an integrated processing system and/or a distributed processing system.
The computing device 400 may further include one or more memories 404, such as for storing local versions of applications being executed by the one or more processors 402, related instructions, parameters, etc. The one or more memories 404 may include a type of memory usable by a computer, such as random access memory (RAM), read only memory (ROM), tapes, magnetic discs, optical discs, volatile memory, non-volatile memory, and any combination thereof. Additionally, the one or more processors 402 and the one or more memories 404 may include and execute an operating system executing on the one or more processors 402, individually, as a subgroup, or in combination, one or more applications, display drivers, etc., and/or other components of the computing device 400.
As used herein, a memory, at least one memory, and/or one or more memories, individually, as a subgroup, or in combination, configured to store or having stored thereon instructions executable by one or more processors for performing a plurality of actions is meant to include at least two different memories able to store different, overlapping or non-overlapping subsets of the instructions for performing different, overlapping or non-overlapping subsets of the plurality actions, or a single memory able to store the instructions for performing all of the plurality of actions. In one non-limiting example of one or more memories, individually, as a subgroup, or in combination, being able to store different subsets of the instructions for performing different ones of the plurality of actions, a description of a memory, at least one memory, and/or one or more memories configured or operable to store or having stored thereon instructions for performing actions X, Y, and Z may include at least a first memory configured or operable to store or having stored thereon a first subset of instructions for performing a first subset of X, Y, and Z (e.g., instructions to perform X) and at least a second memory configured or operable to store or having stored thereon a second subset of instructions for performing a second subset of X, Y, and Z (e.g., instructions to perform Y and Z). Alternatively, a first memory, and second memory, and a third memory may be respectively configured to store or have stored thereon a respective one of a first subset of instructions for performing X, a second subset of instruction for performing Y, and a third subset of instructions for performing Z.
It should be understood that any combination of one or more memories each may be configured or operable to store or have stored thereon any one or any combination of instructions executable by one or more processors to perform any one or any combination of a plurality of actions. Moreover, one or more processors may each be coupled to at least one of the one or more memories and configured or operable to execute the instructions to perform the plurality of actions. For instance, in the above non-limiting example of the different subset of instructions for performing actions X, Y, and Z, a first processor may be coupled to a first memory storing instructions for performing action X, and at least a second processor may be coupled to at least a second memory storing instructions for performing actions Y and Z, and the first processor and the second processor may, In combination, execute the respective subset of instructions to accomplish performing actions X, Y, and Z. Alternatively, three processors may access one of three different memories each storing one of instructions for performing X, Y, or Z, and the three processor may in combination execute the respective subset of instruction to accomplish performing actions X, Y, and Z. Alternatively, a single processor may execute the instructions stored on a single memory, or distributed across multiple memories, to accomplish performing actions X, Y, and Z.
Further, the computing device 400 may include a communications component 406 that provides for establishing and maintaining communications with one or more other devices, parties, entities, etc., utilizing hardware, software, and services. The communications component 406 may carry communications between components on the computing device 400, as well as between the computing device 400 and external devices, such as devices located across a communications network and/or devices serially or locally connected to the computing device 400. For example, the communications component 406 may include one or more buses, and may further include transmit chain components and receive chain components associated with a wireless or wired transmitter and receiver, respectively, operable for interfacing with external devices.
Additionally, the computing device 400 may include a data store 408, which can be any suitable combination of hardware and/or software, that provides for mass storage of information, databases, and programs. For example, the data store 408 may be or may include a data repository for applications and/or related parameters not currently being executed by the one or more processors 402, individually, as a subgroup, or in combination. In addition, the data store 408 may be a data repository for an operating system, application, display driver, etc., executing on the one or more processors 402, individually, as a subgroup, or in combination, and/or one or more other components of the computing device 400.
The computing device 400 may also include a user interface component 410 operable to receive inputs from a user of the computing device 400 and further operable to generate outputs for presentation to the user (e.g., via a display interface to a display device). The user interface component 410 may include one or more input devices, including but not limited to a keyboard, a number pad, a mouse, a touch-sensitive display, a navigation key, a function key, a microphone, a voice recognition component, or any other mechanism capable of receiving an input from a user, or any combination thereof. Further, the user interface component 410 may include one or more output devices, including but not limited to a display interface, a speaker, a haptic feedback mechanism, a printer, any other mechanism capable of presenting an output to a user, or any combination thereof.
Referring to
Referring to
At block 502 the method 500 includes communicating, via a data interface of the data logger device that is connected to a data connection of the fire alarm control panel, with one or more processors of the fire alarm control panel, to obtain detector values stored in one or more data stores of the fire alarm control panel, wherein the fire alarm system comprises one or more detectors communicatively coupled with the fire alarm control panel via a wired or wireless connection. For example, in an aspect, computing device 400, one or more processors 402 individually, as a subgroup, or in combination, one or more memories 404 individually, as a subgroup, or in combination, and/or data logging component 412 may be configured to or may comprise means for communicating, via a data interface of the data logger device that is connected to a data connection of the fire alarm control panel, with one or more processors of the fire alarm control panel, to obtain detector values stored in one or more data stores of the fire alarm control panel, wherein the fire alarm system comprises one or more detectors communicatively coupled with the fire alarm control panel via a wired or wireless connection.
For example, the one or more processors 21 of the data logger device 20 may communicate with the one or more processors 7 of the fire alarm control panel 3 via the data interface 23 of the data logger device 20 that is connected to the data connection 11 of the fire alarm control panel 3, to obtain detector values stored in the one or more data stores 8 of the fire alarm control panel 3, wherein the fire alarm system 1 comprises one or more detectors 4 communicatively coupled with the fire alarm control panel 3 via a wired or wireless connection.
In some optional implementations, the data logger device 20 comprises logger control software installed thereon before logging data, wherein the logger control software is executable by the one or more processors 21 of the data logger device 20 to perform any data logging functionality described herein.
In some optional implementations, at optional block 504 the method 500 includes requesting, from the fire alarm control panel, one or more most recently returned values from each of the one or more detectors. For example, in an aspect, computing device 400, one or more processors 402 individually, as a subgroup, or in combination, one or more memories 404 individually, as a subgroup, or in combination, and/or data logging component 412 may be configured to or may comprise means for requesting, from the fire alarm control panel, one or more most recently returned values from each of the one or more detectors.
For example, the one or more processors 21 of the data logger device 20 may request, from the fire alarm control panel 3, one or more most recently returned values from each of the one or more detectors 4a.
At block 506 the method 500 includes logging the detector values into the one or more data stores of the data logger device. For example, in an aspect, computing device 400, one or more processors 402 individually, as a subgroup, or in combination, one or more memories 404 individually, as a subgroup, or in combination, and/or data logging component 412 may be configured to or may comprise means for logging the detector values into the one or more data stores of the data logger device.
For example, the one or more processors 21 of the data logger device 20 may log the detector values into the one or more data stores 22 of the data logger device 20.
In some optional implementations, a portable data memory device (e.g., a universal serial bus (USB) device) is connectable to the data logger device 20. In these implementations, the data logger device 20 is further configured to download the detector values from the one or more data stores 22 of the data logger device 20 into the portable data memory device.
In some optional implementations, the data logger device 20 is a single board computer.
In some optional implementations, the fire alarm control panel 3 further comprises the power supply 12, wherein the data logger device 20 is powered by the power supply 12 of the fire alarm control panel 3.
In some optional implementations, the fire alarm control panel 3 is configured to reset responsive to the power supply 12 being turned off and turned back on.
In some optional implementations, at optional block 508 the method 500 includes resetting responsive to the power supply being turned off and turned back on. For example, in an aspect, computing device 400, one or more processors 402 individually, as a subgroup, or in combination, one or more memories 404 individually, as a subgroup, or in combination, and/or data logging component 412 may be configured to or may comprise means for resetting responsive to the power supply being turned off and turned back on.
For example, the data logger device 20 may reset responsive to the power supply being turned off and turned back on.
In some optional implementations, the resetting at optional block 508 includes optional blocks 510 and 512 described below.
In some optional implementations, at optional block 510 the method 500 includes starting a timer subsequent to the power supply being turned back on. For example, in an aspect, computing device 400, one or more processors 402 individually, as a subgroup, or in combination, one or more memories 404 individually, as a subgroup, or in combination, and/or data logging component 412 may be configured to or may comprise means for starting a timer subsequent to the power supply being turned back on.
For example, the data logger device 20 may start a timer subsequent to the power supply 12 being turned back on.
In some optional implementations, at optional block 512 the method 500 includes beginning learning addresses of the one or more detectors after expiry of the timer. For example, in an aspect, computing device 400, one or more processors 402 individually, as a subgroup, or in combination, one or more memories 404 individually, as a subgroup, or in combination, and/or data logging component 412 may be configured to or may comprise means for beginning learning addresses of the one or more detectors after expiry of the timer.
For example, the data logger device 20 may begin learning addresses of the detectors 4a after expiry of the timer.
In some optional implementations, the timer is configured to allow the fire alarm control panel 3 to learn a configuration of the fire alarm system 1 and log new detector values stored in the one or more data stores 8 of the fire alarm control panel 3 after being reset.
In some optional implementations, the timer is configured to expire in 2 minutes.
Referring to
For example, the data logger device 20 may learn addresses of the detectors 4a.
In some optional implementations, the learning at optional block 602 includes optional blocks 604, 606, 608, and 610 described below.
In some optional implementations, at optional block 604 the method 600 includes requesting a detector value for each address that is configurable on each addressable loop that is connectable to the fire alarm control panel. For example, in an aspect, computing device 400, one or more processors 402 individually, as a subgroup, or in combination, one or more memories 404 individually, as a subgroup, or in combination, and/or data logging component 412 may be configured to or may comprise means for requesting a detector value for each address that is configurable on each addressable loop that is connectable to the fire alarm control panel.
For example, the data logger device 20 may request a detector value for each address that is configurable on each addressable loop (e.g., wiring 2) that is connectable to the fire alarm control panel 3.
In some optional implementations, a maximum number of loops are connectable to the fire alarm control panel 3, and a maximum number of addresses are configurable on each loop that is connectable to the fire alarm control panel 3.
In some optional implementations, the maximum number of loops connectable to the fire alarm control panel 3 is 32 and the maximum number of addresses configurable on each loop is 250.
In some optional implementations, the requesting at optional block 604 includes optional blocks 606 at which the method 600 includes requesting the detector value for each one of configurable addresses 1 through 250 on each one of connectable addressable loops 1 through 3. For example, in an aspect, computing device 400, one or more processors 402 individually, as a subgroup, or in combination, one or more memories 404 individually, as a subgroup, or in combination, and/or data logging component 412 may be configured to or may comprise means for requesting the detector value for each one of configurable addresses 1 through 250 on each one of connectable addressable loops 1 through 3.
For example, the data logger device 20 may request a detector value for all addresses 1 through 250 on all addressable loops 1 through 3.
In some optional implementations, at optional block 608 the method 600 includes recording only the addresses which correspond to a detector being present on a connected addressable loop. For example, in an aspect, computing device 400, one or more processors 402 individually, as a subgroup, or in combination, one or more memories 404 individually, as a subgroup, or in combination, and/or data logging component 412 may be configured to or may comprise means for recording only the addresses which correspond to a detector being present on a connected addressable loop.
For example, the data logger device 20 may record only the addresses which correspond to a detector 4a being present on a connected addressable loop (e.g., wiring 2).
In some optional implementations, the recording at optional block 608 includes optional block 610 at which the method 600 includes determining that the detector is present at an address that is configurable on a connectable addressable loop responsive to a corresponding detector value being received for the address. For example, in an aspect, computing device 400, one or more processors 402 individually, as a subgroup, or in combination, one or more memories 404 individually, as a subgroup, or in combination, and/or data logging component 412 may be configured to or may comprise means for determining that the detector is present at an address that is configurable on a connectable addressable loop responsive to a corresponding detector value being received for the address.
For example, the data logger device 20 may determine that the detector 4a is present at an address that is configurable on a connectable addressable loop (wiring 2) responsive to a corresponding detector value being received for the address.
Referring to
In some optional implementations, at optional block 702 the method 700 includes throttling obtaining detector values. For example, in an aspect, computing device 400, one or more processors 402 individually, as a subgroup, or in combination, one or more memories 404 individually, as a subgroup, or in combination, and/or data logging component 412 may be configured to or may comprise means for throttling obtaining detector values.
For example, the data logger device 20 may throttle obtaining detector values from the fire alarm control panel 3.
In some optional implementations, the throttling at optional block 702 includes optional block 704 at which the method 700 includes obtaining a threshold number of detector values per second. For example, in an aspect, computing device 400, one or more processors 402 individually, as a subgroup, or in combination, one or more memories 404 individually, as a subgroup, or in combination, and/or data logging component 412 may be configured to or may comprise means for obtaining a threshold number of detector values per second.
For example, the data logger device 20 may throttle obtaining detector values from the fire alarm control panel 3 by obtaining a threshold number of detector values per second.
In some optional implementations, the throttling at optional block 702 includes optional blocks 706, 708, 710, and 712 described below.
In some optional implementations, at optional block 706 the method 700 includes obtaining a detector value from the one or more processors of the fire alarm control panel.
For example, in an aspect, computing device 400, one or more processors 402 individually, as a subgroup, or in combination, one or more memories 404 individually, as a subgroup, or in combination, and/or data logging component 412 may be configured to or may comprise means for obtaining a detector value from the one or more processors of the fire alarm control panel.
For example, the data logger device 20 may obtain a detector value from the one or more processors 7 of the fire alarm control panel 3.
In some optional implementations, at optional block 708 the method 700 includes logging the detector value into the one or more data stores of the data logger device. For example, in an aspect, computing device 400, one or more processors 402 individually, as a subgroup, or in combination, one or more memories 404 individually, as a subgroup, or in combination, and/or data logging component 412 may be configured to or may comprise means for logging the detector value into the one or more data stores of the data logger device.
For example, the data logger device 20 may log the detector value into the one or more data stores 22 of the data logger device 20.
In some optional implementations, at optional block 710 the method 700 includes starting a timer upon obtaining the detector value. For example, in an aspect, computing device 400, one or more processors 402 individually, as a subgroup, or in combination, one or more memories 404 individually, as a subgroup, or in combination, and/or data logging component 412 may be configured to or may comprise means for starting a timer upon obtaining the detector value.
For example, the data logger device 20 may start a timer upon obtaining the detector value.
In some optional implementations, at optional block 712 the method 700 includes obtaining a subsequent detector value from the one or more processors of the fire alarm control panel, upon expiry of the timer. For example, in an aspect, computing device 400, one or more processors 402 individually, as a subgroup, or in combination, one or more memories 404 individually, as a subgroup, or in combination, and/or data logging component 412 may be configured to or may comprise means for obtaining a subsequent detector value from the one or more processors of the fire alarm control panel, upon expiry of the timer.
For example, the data logger device 20 may obtain a subsequent detector value from the one or more processors 7 of the fire alarm control panel 3, upon expiry of the timer.
In some optional implementations, at optional block 714 the method 700 includes logging the subsequent detector value into the one or more data stores of the data logger device.
For example, in an aspect, computing device 400, one or more processors 402 individually, as a subgroup, or in combination, one or more memories 404 individually, as a subgroup, or in combination, and/or data logging component 412 may be configured to or may comprise means for logging the subsequent detector value into the one or more data stores of the data logger device.
For example, the data logger device 20 may log the subsequent detector value into the one or more data stores 22 of the data logger device 20.
Some further aspects are described in the below clauses.
The previous description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other aspects. Thus, the claims are not intended to be limited to the aspects shown herein, but is to be accorded the full scope consistent with the language claims, wherein reference to an element in the singular is not intended to mean “one and only one” unless specifically so stated, but rather “one or more.” The word “exemplary” is used herein to mean “serving as an example, instance, or illustration.” Any aspect described herein as “exemplary” is not necessarily to be construed as preferred or advantageous over other aspects. Unless specifically stated otherwise, the term “some” refers to one or more. Combinations such as “at least one of A, B, or C,” “one or more of A, B, or C,” “at least one of A, B, and C,” “one or more of A, B, and C,” and “A, B, C, or any combination thereof” include any combination of A, B, and/or C, and may include multiples of A, multiples of B, or multiples of C. Specifically, combinations such as “at least one of A, B, or C,” “one or more of A, B, or C,” “at least one of A, B, and C,” “one or more of A, B, and C,” and “A, B, C, or any combination thereof” may be A only, B only, C only, A and B, A and C, B and C, or A and B and C, where any such combinations may contain one or more member or members of A, B, or C. All structural and functional equivalents to the elements of the various aspects described throughout this disclosure that are known or later come to be known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be encompassed by the claims. Moreover, nothing disclosed herein is intended to be dedicated to the public regardless of whether such disclosure is explicitly recited in the claims. The words “module,” “mechanism,” “element,” “device,” and the like may not be a substitute for the word “means.” As such, no claim element is to be construed as a means plus function unless the element is expressly recited using the phrase “means for.”
| Number | Date | Country | Kind |
|---|---|---|---|
| 2317663.9 | Nov 2023 | GB | national |
