Event device operation

Abstract

Described herein are devices, systems, and methods for event equipment operation. In some examples, one or more embodiments include a mobile device comprising a user interface, a memory, and a processor that executes instructions stored in the memory to: receive a signal from a control panel of a control system in response to the mobile device being connected to the control panel; generate an event equipment analysis of a plurality of event equipment included in the control system based on the signal; display the event equipment analysis via the user interface; display a diagnostic guide for correcting a fault in response to selecting the fault corresponding to an event equipment from a list of event equipment having a fault; and control at least one of an operation of the control panel and an operation of one of the plurality of event equipment in response to an input to the user interface.

Description

Technical Field

[0001] This disclosure relates to devices, systems, and methods for operating event devices. Background Technology

[0002] Large facilities (e.g., buildings), such as commercial facilities, office buildings, hospitals, etc., may have alarm systems that can be triggered during emergencies (e.g., fire) to warn occupants to evacuate. Such alarm systems may be part of a control system that controls the operation of devices included in the alarm system. For example, an alarm system may include control panels (e.g., fire control panels) and multiple event devices (e.g., hazard sensing devices, input devices, output devices, etc.) located throughout the facility (e.g., on different floors of the facility and / or in different rooms), which can act to notify occupants of the hazard event when it occurs in the facility, via alarms or other mechanisms.

[0003] Maintaining an alarm system may include periodic testing of the incident equipment. Such periodic testing may be mandated by practice standards in an attempt to ensure that the incident equipment is functioning properly. Attached Figure Description

[0004] Figure 1 This is an example of a system for operating an event device according to one or more embodiments of this disclosure.

[0005] Figure 2 The illustration is a display provided on a user interface that shows a description including fault and diagnostic guidance, generated according to one or more embodiments of this disclosure.

[0006] Figure 3 It is a display illustration provided on an event device analysis user interface that includes event device operation information, generated according to one or more embodiments of this disclosure.

[0007] Figure 4 It is an illustration provided on a user interface showing event device analysis, generated according to one or more embodiments of this disclosure.

[0008] Figure 5 Examples of mobile devices for operation of event devices according to one or more embodiments of this disclosure. Detailed Implementation

[0009] This document describes devices, systems, and methods for operating event devices. In some examples, one or more embodiments include a mobile device comprising a user interface, memory, and a processor that executes instructions stored in the memory to: receive a signal from a control panel in response to the mobile device being connected to a control panel of a control system; generate an event device analysis based on the signal for a plurality of event devices included in the control system; display the event device analysis via the user interface; display diagnostic guidance for correcting a fault in response to selecting a fault corresponding to an event device from a list of faulty event devices; and control at least one of the operation of the control panel and the operation of one of the plurality of event devices in response to input to the user interface.

[0010] Maintenance of incident devices may typically involve a first user (e.g., a technician, engineer, etc.) performing functional tests on the incident devices and other components of the alarm system while they walk around the facility and visually inspect the alarm system components. For example, smoke tests and visual inspections of fire sensors may be performed while inspectors are close enough to visually inspect each fire sensor. While the first user is performing functional tests and visual inspections of the incident devices, a second user may interpret signals received at the alarm system control panel. These signals may be the result of the first user's functional tests of the incident devices in the facility.

[0011] This manual testing process, conducted between a second user at the control panel and a first user in the facility testing the event equipment, can lead to costly maintenance because two users must perform the testing. Additionally, some users may be unfamiliar with the alarm system, resulting in them failing to identify problems, misdiagnosing problems, or identifying problems without understanding what they are. Consequently, such users may be unable to locate and / or diagnose certain problems in the alarm system (e.g., malfunctions), leading to calls to technical support or other skilled users spending additional time diagnosing such problems (e.g., remotely or by walking to the facility). Furthermore, in some examples, certain problems may cause the control panel's user interface to display errors, but these errors may not be clearly visible on the control panel.

[0012] The event device operation method disclosed herein allows users to utilize mobile devices to view event device analytics and control the operation of event devices in control panels and / or facilities. The mobile device may further display a copy of the control panel's user interface. This method allows users to perform tests on event devices, perform maintenance operations, view current event device operation information, and / or diagnose and correct faults associated with the event devices and / or control panels, as well as other uses, without requiring a second user to wait at the control panel or to travel back and forth between the control panel and the event devices within the facility. Therefore, compared to previous methods where one user monitors the event devices and another user monitors the control panel, this method allows for simpler and more convenient alarm system operation, maintenance activities, fault diagnosis, and / or product knowledge support, while also saving time and / or costs, as such activities can be performed by a single user using a mobile device.

[0013] In the following detailed description, reference is made to the accompanying drawings, which form a part thereof. The drawings illustrate by way of example how one or more embodiments of this disclosure can be practiced.

[0014] These embodiments are described in sufficient detail to enable one or more embodiments of this disclosure to be practiced by a person skilled in the art. It should be understood that other embodiments may be utilized and process, electrical and / or structural changes may be made without departing from the scope of this disclosure.

[0015] It should be understood that elements shown in the various embodiments herein may be added, exchanged, combined, and / or eliminated to provide multiple additional embodiments of this disclosure. The scale and relative dimensions of the elements provided in the accompanying drawings are intended to illustrate embodiments of this disclosure and should not be construed as limiting.

[0016] The figures in this document follow the following numbering convention: one or more first digits correspond to the figure number, while the remaining digits identify elements or parts in the figure. Similar elements or parts between different figures can be identified by using similar digits. For example, 102 can be referenced... Figure 1 The element "02" in the text, and Figure 2 Similar elements in this context can be referenced as 202.

[0017] As used in this article, "one" or "several" can refer to one or more such things, while "multiple" can refer to more than one such thing. For example, "numerous components" can refer to one or more components, while "multiple components" can refer to more than one component.

[0018] Figure 1This is an example of a system 100 for operating an event device according to one or more embodiments of the present disclosure. System 100 may include a mobile device 102, event devices 106-1, 106-2, 106-N (collectively referred to herein as event device 106), a remote computing device 108, a gateway device 110, and a control panel 112.

[0019] like Figure 1 As shown, system 100 may include control panel 112. As used herein, the term "control panel" refers to a device that is a component of a control system for controlling a facility. For example, control panel 112 may be a fire control panel capable of receiving information from event device 106 and determining whether a hazardous event is occurring or has occurred.

[0020] Control panel 112 may include user interface 114. As used herein, the term "user interface" refers to a device for providing (e.g., displaying and / or presenting) information to a user and / or receiving information from a user (e.g., input made by the user). For example, in some embodiments, user interface 114 may be a graphical user interface (GUI) that provides information to and / or receives information from a user of control panel 112. User interface 114 may be, for example, a touchscreen (e.g., the GUI may include touchscreen functionality). Alternatively, user interface 114 may be part of a television, computer monitor, mobile device screen, other type of display device, or any combination thereof, connected to control panel 112 and configured to receive video signals output from control panel 112.

[0021] Control panel 112 can be connected to event device 106. As used herein, the term "event device" refers to a device that can receive event-related input and / or generate event-related output. Such events can be, for example, hazardous events such as fire. For example, event device 106 can receive input related to a fire occurring in the facility. Such event device 106 can be part of the facility's control system and may include devices such as fire sensors, smoke detectors, heat detectors, carbon monoxide (CO) detectors, or combinations thereof; interfaces; pull-out fire alarm boxes; input / output modules; suction units; and / or audio / video equipment (e.g., speakers, sound generators, buzzers, microphones, cameras, video displays, video screens, etc.) and other types of event devices.

[0022] In some examples, event device 106 may be an automated self-test device, such as a smoke detector, heat detector, CO detector, and / or other devices. Such a self-test device may include mechanisms that generate aerosols, heat, carbon monoxide, etc., and sense these items depending on the type of device being tested within the device to test its performance. This may be used, for example, to test the thermal and / or light sensing capabilities of the event device. However, embodiments of this disclosure are not limited to this automated self-test device. For example, event device 106 may be a non-self-test device that must be manually tested by a user. Additionally, in some examples, event device 106 may include a combination of automated self-test devices and non-self-test devices.

[0023] System 100 may include mobile device 102. As used herein, the term “mobile device” means a device carried and / or worn (or that may be carried and / or worn by a user). For example, mobile device 102 may be a telephone (e.g., a smartphone), a tablet computer, a personal digital assistant (PDA), smart glasses and / or wrist-worn devices (e.g., a smartwatch), and other types of mobile devices.

[0024] Mobile device 102 may include user interface 104. For example, in some embodiments, user interface 104 may be a graphical user interface (GUI) that provides information to and / or receives information from a user of mobile device 102. User interface 104 may be, for example, a touchscreen (e.g., the GUI may include touchscreen functionality). Alternatively, user interface 104 may be a television, computer monitor, mobile device screen, other type of display device, or any combination thereof that is connected to mobile device 102 and configured to receive video signals output from mobile device 102.

[0025] like Figure 1 As shown, mobile device 102 can connect to remote computing device 108. Remote computing device 108 can be, for example, a remote server. Remote computing device 108 can be a cloud computing environment. In some examples, remote computing device 108 can run on control panel 112 or mobile device 102.

[0026] Mobile device 102 may connect to control panel 116 directly (e.g., via a wireless or wired network relationship) or via gateway device 110. As used herein, the term "gateway device" refers to a device used to provide an interface between control panel 112 and remote server 115. In some examples, remote server 115 may be a cloud computing environment (e.g., a cloud server).

[0027] Mobile device 102 can be connected to gateway device 110 via a network. For example, the network can provide a network relationship between mobile device 102 and gateway device 110 / control panel 112. This network relationship can be a wired or wireless network connection. Examples of such network relationships can include local area networks (LANs), wide area networks (WANs), personal area networks (PANs), distributed computing environments (e.g., cloud computing environments), storage area networks (SANs), metropolitan area networks (MANs), cellular communication networks, Long Term Evolution (LTE), Visible Light Communication (VLC), Bluetooth, WiMAX, Near Field Communication (NFC), Infrared (IR) communication, Public Switched Telephone Network (PSTN), radio waves and / or the Internet, as well as other types of network relationships.

[0028] In some implementations, mobile device 102 may be directly connected to control panel 112. For example, mobile device 102 may be connected directly and / or via a wired connection (e.g., a cable, such as a serial cable or Universal Serial Bus (USB) cable) and / or via a private wireless network (e.g., via a wireless transceiver device connected to control panel 112). Figure 1 (Not shown) Wirelessly connected to control panel 112. Such implementations may be used when the security and / or privacy of information included on control panel 112 are of concern.

[0029] In some implementations, mobile device 102 can connect to control panel 112 by scanning a code associated with control panel 112. For example, control panel 112 may have a code associated with it (e.g., a barcode, QR code, etc.) (e.g., as a sticker on control panel 112, displayed via user interface 114, etc.), and a user can scan the code via mobile device 102 to establish a connection between mobile device 102 and control panel 112.

[0030] In addition, such as Figure 1 As shown, system 100 may include a remote server 115. The remote server 115 may be a server accessed, for example, by a mobile device 102 via the Internet.

[0031] As previously mentioned above, mobile device 102 can be used to view event device analysis of event device 106. Additionally and / or alternatively, mobile device 102 can be used to control the operation of control panel 112 and / or event device 106. Such operations are further described herein.

[0032] As mentioned above, mobile device 102 may be connected to control panel 112 via gateway device 110 or directly. In response to mobile device 102 connecting to control panel 112 of the control system shown in system 100, mobile device 102 may receive signals from control panel 112. Signals may include, for example, information about the control system shown in system 100. For example, signals received by mobile device 102 may include information about event device 106, computational operations performed by control panel 112, data and / or other information stored by control panel 112, as further described herein.

[0033] Mobile device 102 may generate an event device analysis of a plurality of event devices 106 included in the control system shown in system 100 based on the received signals. The event device analysis may include a list of the plurality of event devices 106 of the control system and / or a list (e.g., a sublist) of event devices with malfunctions from the total number of event devices 106, as further described herein.

[0034] In some examples, event device analysis may include a list of multiple event devices 106 of the control system. For example, mobile device 102 may generate a list based on signals received from control panel 112, including... Figure 1 The control system shown is a list of event devices 106-1, 106-2, and 106-N. Therefore, the user of mobile device 102 can view different time devices among the multiple event devices 106 via the list, and perform other actions, as described herein. Figures 2 to 4 Further details are provided.

[0035] In some examples, an event device analysis may include a list of event devices 106 that are faulty. As used herein, the term "faulty" refers to a defect in a device that prevents it from functioning properly. For example, an event device analysis may include a sublist of event devices 106-1 and 106-2, where event devices 106-1 and 106-2 are faulty event devices.

[0036] The mobile device 102 can display event device analysis via the user interface 104 of the mobile device 102. For example, the mobile device 102 can display a list of multiple event devices 106 of the control system, and a list of multiple event devices 106 with malfunctions (e.g., event devices 106-1, 106-2).

[0037] In some examples, the user interface 114 of control panel 112 may display information about system 100. For example, user interface 114 may display a list of faulty event devices 106-1 and 106-2. Mobile device 102 may be configured to reproduce and display the user interface 114 of control panel 112 on user interface 104 of mobile device 102. Therefore, in instances where the user of mobile device 102 is not near control panel 112 or the user interface 114 of control panel 112 may be unclear, mobile device 102 may reproduce (e.g., copy) and display the user interface 114 of control panel 112 on user interface 104 of mobile device 102.

[0038] In some examples, system 100 may be deployed in various regions around the world. Therefore, different regions may include different languages, some of which include different alphanumeric characters. Thus, mobile device 102 may display event device analytics via user interface 104 in a language corresponding to the physical geographic location of mobile device 102. Mobile device 102 may determine its physical geographic location (e.g., via Global Positioning System (GPS), mobile device network (e.g., 3G, 4G, 5G, etc.), via user input, and other examples) and determine the language used to display event device analytics based on its physical geographic location. For example, in one example, mobile device 102 may be used in system 100 deployed in India, and mobile device 102 may display event device analytics in Hindi. In another example, mobile device 102 may be used in system 100 deployed in the United States, and mobile device 102 may display event device analytics in English. However, as mentioned above, embodiments of this disclosure are not limited to Hindi and / or English, and can be displayed in any language.

[0039] Mobile device 102 can control the operation of one of the event devices 106 in control panel 112 and / or event devices 106 in response to input to user interface 104. For example, mobile device 102 can receive input via user interface 104 to cause mobile device 102 to control the operation of control panel 112 in such a way that control panel 112 transmits information to mobile device 102, such that mobile device 102 can display a list of faulty event devices 106, view a description of the fault, display the location of the selected event device 106 in the facility, display a total count of faulty event devices, display diagnostic guidance for correcting the fault, and other examples. As another example, mobile device 102 can receive input via user interface 104 to cause mobile device 102 to control the operation of one of a plurality of event devices 106 in such a way that event device 106 performs maintenance activities, views event device operation information, performs tests, and other examples as further described herein.

[0040] In some instances, mobile device 102 may control certain operations of control panel 112 and / or event device 106 requiring further authentication. For example, some operations may not be possible for less skilled / less trained users. Therefore, the user may be prompted to enter user credentials via user interface 104 of mobile device 102. In response to the user credential being entered and the user profile of mobile device 102 being verified (e.g., the user corresponding to mobile device 102), mobile device 102 may control the operation of control panel 112 and event device 106. User credentials may include username and password, biometric information corresponding to the user of mobile device 102, and other types of user credentials.

[0041] In some examples, controlling event device 106 may include causing event device 106 to perform maintenance activities. For example, a user of mobile device 102 may expect to perform maintenance activities on event device 106-1. Mobile device 102 may cause event device 106-1 to perform a walk test, for example, by receiving user input via user interface 104. Mobile device 102 may transmit user input to control panel 112, and control panel 112 may cause event device 106-1 to perform a walk test.

[0042] To help users identify whether they are performing maintenance activities on the correct event device 106, mobile device 102 can cause control panel 112 to cause the event device 106 to blink a user-visible light fixture. For example, a user might want to test event device 106-1 during a walk-through test, but event devices 106-1 and 106-2 are positioned close to each other (e.g., on the ceiling of the same room). Mobile device 102 can transmit a signal to control panel 112, and control panel 112 can transmit a signal to event device 106-1 to cause the light fixture (e.g., a light-emitting diode (LED)) of event device 106-1 to blink to verify that the user is in communication with the event device 106 they wish to test. Thus, the event device 106 to be tested can be verified for the user by causing a specific event device 106 to blink its light fixture.

[0043] In some examples, a user can view an event device 106 that is faulty. For instance, a user can select event device 106-1 (e.g., faulty) via user interface 104 to diagnose the fault in event device 106-1. User interface 104 can display diagnostic guides to help the user diagnose the fault associated with event device 106-1. (See also...) Figure 2 Furthermore, the diagnostic guidance may include step-by-step instructions to the user of the mobile device 102, informing them of certain steps they can take to correct the fault.

[0044] After using the diagnostic guide, the user interface 104 may display a notification to allow the user of the mobile device 102 to receive feedback on the diagnostic guide. For example, the diagnostic guide may include step-by-step instructions on how to correct the configuration checksum failure of event device 106. The user can provide feedback on how helpful or useful the steps in the diagnostic guide are. For example, the user can provide feedback stating that the step-by-step instructions should include more photos to help the user visualize and / or show how and / or where to perform these steps. The mobile device 102 may transmit this feedback to the remote computing device 108.

[0045] In some examples, as mentioned above, remote computing device 108 may be a cloud computing environment running on control panel 112 or mobile device 102. Remote computing device 108 may run machine learning models to improve diagnostic guidance provided by mobile device 102. For example, remote computing device 108 may determine via a machine learning model that the amount of feedback received (e.g., exceeding some data threshold) should (e.g., with more photos) update the diagnostic guidance related to a specific issue (e.g., configuration checksum failure) of event device 106 and / or control panel 112 to better assist the user in diagnosing and troubleshooting the specific issue. The machine learning models executed on remote computing device 108 may include supervised learning, unsupervised learning, regression, instance-based, decision tree, Bayesian, clustering, artificial neural networks, deep learning, and other types of machine learning techniques.

[0046] Although the remote computing device 108 has been described above as modifying diagnostic guidance by adding more photos, the embodiments disclosed herein are not limited to this. For example, the remote computing device 108 may modify diagnostic guidance by adding more text information, rearranging steps and / or text information, suggesting the creation and addition of video tutorials, adding different questions to query the user, etc.

[0047] Diagnostic guidance provided by mobile device 102 can be generated and / or updated by receiving various inputs from remote computing device 108. Inputs can be user input, data from event device 106, data from remote server 115, and other inputs. For example, event device 106 may include electrical faults. Remote computing device 108 may receive inputs including: battery manufacturing date, battery installation date, previously performed battery maintenance (e.g., repair, maintenance logs, etc.), rated battery capacity, the last known battery health information from event device 106 or control panel 112 (e.g., battery internal resistance, charging voltage, battery voltage, thermistor readings, etc.), battery load / size, etc. Such inputs allow remote computing device 108 to generate and / or update diagnostic guidance and predict maintenance needs for viewing by the user via user interface 104 of mobile device 102. For example, diagnostic guidance is generated and / or updated to include and / or update prompts for possible causes (e.g., expired battery life, charger circuit failure, thermistor disconnected / damaged, insufficient battery size, etc.), suggestions for troubleshooting (e.g., check battery wiring, check blown fuses, check non-functional chargers, check thermistor section, recalculate battery size / load, etc.), and / or recommendations for troubleshooting (e.g., replace battery, rewire battery, replace potentially blown fuses, replace thermistor, replace panelboard, reset battery size, etc.), and other examples.

[0048] Figure 2 This is an illustration of a display provided on a user interface 204 of an event device analysis 201, which includes a description 220 of fault and diagnostic guidance 224, generated according to one or more embodiments of this disclosure. The user interface 204 may be included in a mobile device 202.

[0049] like Figure 2 As shown, event device analysis 201 may include a list 219 of event devices, wherein these event devices include faults 218-1, 218-2, and 218-M. Such event devices may be those previously combined... Figure 1 The device included in system 100. Additionally, although embodiments of this disclosure are not described in detail for clarity and to avoid confusion... Figure 2 As shown, but event device analysis 201 may include a list of event devices included in the facility, wherein the list may include a sublist of event devices including faults 218-1, 218-2, 218-M (e.g., list 219).

[0050] Event device analysis 201 may include a total count 228 of event devices with malfunctions. For example, such as... Figure 2As shown, the facility may include 35 faults associated with various event devices included in the facility.

[0051] Users can select event devices from list 219. For example, a user may want to diagnose a faulty event device and can select the faulty event device from list 219.

[0052] For example, in response to selecting an event device from a list 219 of event devices with fault 218 via user interface 204, mobile device 202 may display a description 220 corresponding to fault 218-1 of the selected event device. For example, the user may select an icon with a circled "i", and user interface 204 may display description 220. Fault 218-1 may be "Configuration checksum failure", and description 220 may further explain to the user of mobile device 202 what a configuration checksum failure is (e.g., when continuous internal checks of the configuration memory have found corruption in the configuration settings of the [event device]). This description may also include possible causes (e.g., corruption in the configuration settings).

[0053] Users may want to find further information about the event device with fault 218-1. For example, when fault 218-1 is selected, user interface 204 may display the location 222 of the event device within the area of ​​the facility that includes the control system. For example, the event device with fault 218-1 may be located in the reception area of ​​Zone 1 on the west wing of the first floor of the facility. This information can help guide the user to the location 222 of the event device.

[0054] When selecting fault 218-1, the user may expect fault diagnosis for fault 218-1. Therefore, the user can select diagnostic guidance 224 (e.g., by selecting an icon with a "wrench and screwdriver"). Upon selection of the icon, the mobile device 202 can generate and display diagnostic guidance 224 for correcting fault 218-1. Diagnostic guidance 224 can indicate to the user the possible causes of fault 218-1 and provide step-by-step instructions 226 for correcting fault 218-1, as further described herein.

[0055] like Figure 2 As shown, the user interface 204 can display step-by-step instructions 226 for correcting fault 218-1. For example, at step 226-1, the user interface 204 can display possible causes of fault 218-1, such as the memory possibly not being erased after a firmware upgrade, or the configuration from the PC application possibly being corrupted. Any of these possible causes may lead to a configuration checksum failure for the event device with fault 218-1. Therefore, the user can select "Start" to initiate the fault diagnosis guidance.

[0056] At 226-2, diagnostic guidance 224 may include instructions for the user to “perform a configuration backup and attempt to erase the memory.” The user can then perform such steps and press “Apply this step” or “Next.” In some instances, the user may know that step 226-2 will not correct fault 218-1 or may have already attempted this step, and therefore may press “Skip this step.”

[0057] At 226-3, diagnostic guidance 224 may include instructions to the user to “reconfigure from the PC application and then press Reset”. Similarly, the user may perform such steps and press “Apply this step” or “Next”, or in some instances, the user may know that step 226-3 will not correct fault 218-1 or has already tried this step and therefore may press “Skip this step”.

[0058] In some examples, the user may not be clear on how to perform the steps. For example, the user may not understand how to “reconfigure from the PC application and then press reset.” Therefore, the diagnostic guide 224 may include a link 230 to the event device product information. This event device product information may be external information that the user can view to obtain further information about the event device and / or the steps in the diagnostic guide 224, such as product manuals, videos, product information (e.g., technical details, voltage limits, etc.).

[0059] In response to selecting link 230, mobile device 202 can access the remote server (e.g., previously combined) Figure 1 The remote server 115 retrieves event device product information. For example, the event device product information could be a video tutorial on how to "reconfigure the event device from a PC application and then press reset". Alternatively, it could be a product manual on how to "reconfigure the event device from a PC application and then press reset". Additionally, the event device product information could be other information describing the event device, such as other technical details about the event device. Therefore, the mobile device 202 can retrieve the event device product information from the remote server and display it via the user interface 204. Access to the remote server can be made, for example, via wired or wireless network connections such as Wi-Fi, mobile communication networks, the Internet, etc. Therefore, the user can utilize the event device product information to "reconfigure the event device from a PC application and then press reset" for the event device with fault 218-1.

[0060] At 226-P, diagnostic guide 224 may include instructions to the user that if previous steps have not corrected fault 218-1, the user should return the PCB to the factory (because the PCB may be faulty). Therefore, the user can complete the step-by-step instructions 226 in diagnostic guide 224 to diagnose fault 218-1. Similar steps can be taken for the user to diagnose faults 218-2 and / or 218-M (e.g., selecting faults 218-2 and / or 218-M, viewing the descriptions 220 of faults 218-2 and 218-M, viewing diagnostic guide 224 for faults 218-2 and 218-M, etc.).

[0061] In some examples, mobile device 202 may be accessible via an audio output device of mobile device 202 (e.g., Figure 2 (Not shown) Step-by-step instructions 226 can be transmitted audibly. For example, mobile device 202 can use a speaker that can transmit step-by-step instructions 226 of diagnostic guidance 224 audibly to allow the user to hear such instructions 226. Thus, the user can use mobile device 202 hands-free to diagnose fault 218.

[0062] In addition, although in Figure 2 The event device analysis 201 is shown in English, but embodiments of this disclosure are not limited thereto. For example, the event device analysis 201 may be displayed on the user interface 204 in any other language.

[0063] Figure 3 This is an illustration of a display provided on a user interface 304 of an event device analysis 301, including event device operation information 332, generated according to one or more embodiments of this disclosure. The user interface 304 may be included in a mobile device.

[0064] As previously combined Figure 2 The event device analysis 301 may include a list of event devices included in the control system. The user can select one of these event devices (e.g., whether it has a fault or not).

[0065] In response to selecting an event device from a list of multiple event devices included in the control system, the mobile device can display event device operation information 332 of the selected event device via user interface 304. This event device operation information 332 is further described herein.

[0066] In some implementations, the event device operation information 332 may include event device voltage information 334. For example, the event device voltage information 334 may include information describing various electrical characteristics of the selected event device, such as DC voltage (e.g., 24 volts (V)), battery voltage (e.g., 19V), battery wiring (e.g., 427 milliohms (mOhm), charger (e.g., 28V), and other electrical characteristics of the selected event device.

[0067] Additionally, the event device operation information 332 may include the real-time status 336 of the event device. For example, the real-time status 336 may include monitoring counts associated with the event device. For example, the event device may be a smoke detector, and the real-time status 336 may be the count of smoke particles currently being detected by the smoke detector (e.g., 2023 counts).

[0068] Additionally, the event device operation information 332 may include the event device's event log 338. For example, a user can select the event log 338 icon to view previous information about the event device, including previous event device voltage information, previous smoke particle counts, and whether any events have been detected previously.

[0069] In addition, the event device operation information 332 may include maintenance notifications for the event device. For example, a user can select the maintenance 340 icon to view maintenance notifications for the event device, including when maintenance can be performed on the event device (e.g., whether the event device sensor has drifted beyond a predetermined calibration limit after a predetermined time has expired). The user can determine whether to perform maintenance on the event device based on the maintenance notification.

[0070] Figure 4 This is an illustration of a display provided on a user interface 404 illustrating event device analysis 401, generated according to one or more embodiments of this disclosure. The user interface 404 may be included in a mobile device 402.

[0071] like Figure 1 As previously mentioned, mobile device 402 can control certain operations of the control panel and / or event device. In some implementations, such control may be permitted after user authentication via user interface 404.

[0072] Mobile device 402 can control the event device by causing it to perform a walk test. As used herein, the term "walk test" refers to a test method in which the event device is intentionally activated to determine whether the control system recognizes the activated event device. For example, a user can locate the event device and initiate a walk test via user interface 404 of mobile device 402. In response to receiving a signal from the control panel (e.g., the event device notifies the control panel that it has detected an event (e.g., intentional activation), and the control panel transmits a signal indicating this to mobile device 402), the user can determine whether the walk test was successful via mobile device 402. Additionally, the user can stop and / or reset the walk test via mobile device 402.

[0073] Mobile device 402 can further control the control panel in the control system. For example, in response to an alarm generated by an event device (e.g., in response to a hazard detected by an event device), mobile device can acknowledge 442 the alarm (e.g., by the user selecting “ACK” via user interface 404), mute 444 the alarm (e.g., by the user selecting “mute” via user interface 404), mute 446 the alarm (e.g., by the user selecting “mute” via user interface 404), and / or re-enable the alarm 448 (e.g., by the user selecting “re-enable” via user interface 404).

[0074] In some examples, mobile device 402 can control the control panel by enabling / disabling event device groups. For example, a group of event devices may be included in the facility. Multiple groups can be divided into event device subgroups 450 (e.g., different event device zones, such as...). Figure 4 As shown in the diagram, different zones can be different subgroups 450 of the group of event devices. For example, zone 1 can be a subgroup 450 of event devices included on a specific floor of the facility. Zone 2 can be a subgroup 450 of event devices in a specific area on a different floor of the facility, and zone 3 can be a subgroup 450 of event devices in a different area on a different floor of the facility. Therefore, a user may wish to disable the subgroup 450 of event devices. The user can select "Disable" 454 via user interface 404 to disable the subgroup 450 of event devices included in the control system. Alternatively, the user may wish to enable the subgroup 450 of event devices, and similarly, can select "Enable" 452 via user interface 404 to enable the subgroup 450 of event devices included in the control system.

[0075] The event device operation method disclosed herein allows users to utilize mobile devices to view event device analytics and control the operation of event devices within control panels and / or facilities. This approach allows users to perform tests on event devices, perform maintenance operations, view current event device operation information and / or diagnose and correct faults associated with event devices and / or control panels, and other uses, without requiring a second user to wait at the control panel or to travel back and forth between the control panel and the event devices within the facility. Therefore, compared to previous methods, this method allows one user, rather than two, to perform activities using a mobile device.

[0076] Figure 5 This is an example of a mobile device 502 for operation of an event device according to one or more embodiments of this disclosure. Figure 5 As shown, the mobile device 502 may include a memory 558 and a processor 556 for operation of the event device according to the present disclosure.

[0077] Memory 558 can be any type of storage medium that can be accessed by processor 556 to execute various examples of the present disclosure. For example, memory 558 can be a non-transitory computer-readable medium on which computer-readable instructions (e.g., executable instructions / computer program instructions) are stored, which can be executed by processor 556 to perform event device operation according to the present disclosure.

[0078] Memory 558 can be volatile or non-volatile memory. Memory 558 can also be removable (e.g., portable) memory or non-removable (e.g., internal) memory. For example, memory 558 can be random access memory (RAM) (e.g., dynamic random access memory (DRAM) and / or phase-change random access memory (PCRAM)), read-only memory (ROM) (e.g., electrically erasable programmable read-only memory (EEPROM) and / or optical disc read-only memory (CD-ROM)), flash memory, laser discs, digital versatile optical discs (DVDs) or other optical storage devices and / or magnetic media (such as magnetic tape cassettes, magnetic tapes, or disks), and other types of memory.

[0079] Furthermore, although memory 558 is shown as residing within mobile device 502, embodiments of this disclosure are not limited thereto. For example, memory 558 may also be located within another computing resource (e.g., enabling computer-readable instructions to be downloaded via the Internet or another wired or wireless connection).

[0080] like Figure 5 As shown, the mobile device 502 includes a user interface 560. For example, the user interface 560 may be displayed in a single integrated display (e.g., as previously described). Figures 1 to 4The event device analysis described above. A user (e.g., an operator) of mobile device 502 can interact with mobile device 502 via user interface 560. For example, user interface 560 can provide (e.g., display and / or present) information to the user of mobile device 502 and / or receive (e.g., input) information from the user of mobile device 502. For example, in some embodiments, user interface 560 can be a graphical user interface (GUI) that provides information to and / or receives information from the user of mobile device 502. The display can be, for example, a touchscreen (e.g., the GUI may include touchscreen functionality). Alternatively, the display can include a television, computer monitor, mobile device screen, other types of display devices, or any combination thereof, connected to mobile device 502 and configured to receive video signals output from mobile device 502.

[0081] As another example, user interface 560 may include a keyboard and / or mouse that a user can use to input information into mobile device 502. However, embodiments of this disclosure are not limited to a particular type of user interface.

[0082] User interface 560 can be localized to any language. For example, user interface 430 can utilize any language, such as English, Spanish, German, French, Mandarin, Arabic, Japanese, Hindi, etc. Therefore, user interface 560 can correspond to the language of the physical geographic location of mobile device 502 for event device analysis.

[0083] Although specific embodiments have been illustrated and described herein, those skilled in the art will understand that any arrangement calculated to achieve the same technology may replace the specific embodiments shown. This disclosure is intended to cover any and all modifications or variations of the various embodiments of this disclosure.

[0084] It should be understood that the above description is given in an illustrative rather than restrictive manner. Combinations of the above embodiments, as well as other embodiments not specifically described herein, will be apparent to those skilled in the art upon reading the above description.

[0085] The scope of the various embodiments of this disclosure includes any other application using the structures and methods described above. Therefore, the scope of the various embodiments of this disclosure should be determined with reference to the appended claims and the full scope of their equivalents.

[0086] In the above specific embodiments, for the purpose of simplifying this disclosure, various features are combined in the example embodiments shown in the drawings. This disclosure method should not be construed as reflecting an intention to require more features than expressly recited in each claim.

[0087] Instead, as reflected in the following claims, the subject matter of the invention lies in fewer than all the features of a single disclosed embodiment. Therefore, the following claims are incorporated herein by reference, wherein each claim exists independently as a separate embodiment.

Claims

1. A mobile device (102, 202, 402) for operating an event device, said mobile device comprising: User interface (104, 204, 304, 404); Memory (558); and Processor (556), the processor being configured to execute executable instructions stored in the memory (558) to: The mobile device (102, 202, 402) receives a signal from the control panel (112) in response to the mobile device (102, 202, 402) being connected to the control panel (112) of the control system; Based on the signal, event device analysis (201, 301, 401) is generated for a plurality of event devices (106) included in the control system, wherein the event device analysis (201, 301, 401) includes: The list of the plurality of event devices (106) of the control system; as well as The list of event devices (106) of the control system that have faults (218); The event device analysis (201, 301, 401) is displayed via the user interface (104, 204, 304, 404). In response to selecting an event device (106) from the list of event devices (106) with a fault (218) via the user interface (104, 204, 304, 404), the location (222) of the event device (106) in the area of ​​the facility including the control system is displayed. In response to selecting a fault (218) corresponding to an event device (106) from the list of event devices (106) with a fault (218), a diagnostic guide (224) for correcting the fault (218) is displayed; and By means of a copy display of the control panel user interface on the user interface of the mobile device, in response to input to the user interface (104, 204, 304, 404), control is made to operate at least one of the control panel (112) and the operation of one of the plurality of event devices (106), wherein the at least one operation of the event device includes causing the event device to perform maintenance activities.

2. The mobile device (102, 202, 402) according to claim 1, wherein in response to selecting an event device (106) from the list of event devices (106) with fault (218) via the user interface (104, 204, 304, 404), the processor (556) is configured to execute the instructions to display a description (220) of the fault (218) corresponding to the selected event device (106).

3. The mobile device (102, 202, 402) according to claim 1, wherein the event device analysis (201, 301, 401) further includes a total count (228) of event devices (106) with faults (218).

4. The mobile device (102, 202, 402) according to claim 1, wherein the diagnostic guidance (224) includes step-by-step instructions (226) for correcting the fault (218).

5. The mobile device (102, 202, 402) according to claim 4, wherein the processor (556) is configured to execute the instructions to audibly transmit the step instructions (226) via an audio output device of the mobile device (102, 202, 402).

6. The mobile device (102, 202, 402) according to claim 4, wherein the diagnostic guidance (224) includes a link (230) to product information of the event device (106).

7. The mobile device (102, 202, 402) according to claim 6, wherein in response to selecting the link (230) via input to the user interface (104, 204, 304, 404), the processor (556) is configured to execute the instructions to retrieve product information of the event device (106) from a remote server (115).

8. The mobile device (102, 202, 402) according to claim 7, wherein the processor (556) is configured to execute the instructions to display product information of the event device (106) via the user interface (104, 204, 304, 404).

9. The mobile device (102, 202, 402) according to claim 1, wherein the processor (556) is configured to execute the instructions to control the event device (106) via the input to the user interface (104, 204, 304, 404) so ​​that the event device (106) performs maintenance activities.

Images