Pyrotechnic failure detection technique

Abstract

A pyrotechnic misfire detection system includes one or more sensors (20) that can acquire sensor data indicative of a pyrotechnic ignition event at one or more launch devices (16) and a controller that can receive the sensor data from the one or more sensors (20), determine whether the sensor data corresponds to a pyrotechnic launch command (18) based on the sensor data, and determine that the one or more launch devices (16) have misfired in response to the sensor data not corresponding to the pyrotechnic launch command (18).

Description

[0001] Cross-reference to related applications This application claims priority and benefit to U.S. Provisional Application No. 63 / 559423, filed February 29, 2024, entitled “PYROTECHNIC MISFIRE DETECTIONTECHNIQUES”, which is incorporated herein by reference in its entirety for all purposes. Background Technology

[0002] This section aims to introduce the reader to various aspects of the technology that may be related to the various aspects of this disclosure. This discussion is intended to help provide the reader with background information to facilitate a better understanding of the various aspects of this disclosure. Therefore, it should be noted that these statements should be read from this perspective and not as an admission of prior art.

[0003] Amusement parks or theme parks may include a variety of entertainment attractions designed to provide enjoyment for the park's customers. For example, attractions may include rides (e.g., closed-loop tracks, dark rides, thrill rides, or other similar rides), and attractions may be part of a themed environment, which may be traditionally established using equipment, furniture, architectural layouts, props, decorations, display media, etc. These themed environments may also include pyrotechnics for aesthetic and / or entertainment purposes. Summary of the Invention

[0004] Certain embodiments commensurate with the scope of the original claimed subject matter are outlined below. These embodiments are not intended to limit the scope of this disclosure; rather, they are merely intended to provide a brief overview of some of the disclosed embodiments. In fact, this disclosure may cover a variety of forms that may be similar to or different from the embodiments set forth below.

[0005] In one embodiment, a pyrotechnic misfire detection system includes one or more sensors and a controller. The sensors acquire sensor data indicating a pyrotechnic ignition event at one or more launching devices. The controller receives the sensor data from the one or more sensors, determines based on the sensor data whether the sensor data corresponds to a pyrotechnic launch command, and determines that the one or more launching devices have misfired in response to the sensor data not corresponding to the pyrotechnic launch command.

[0006] In one embodiment, a method for detecting a fireworks misfire includes receiving a fireworks launch command. The method further includes initiating a fireworks display based on the fireworks launch command. Additionally, the method includes receiving sensor data indicating a fireworks misfire and a notification that a misfire has occurred.

[0007] In one embodiment, a pyrotechnic misfire detection system includes one or more launching devices, each including at least one launching tube and an ignition circuit system capable of launching pyrotechnics from the at least one launching tube based on a pyrotechnic launch command. The pyrotechnic misfire detection system may also include one or more sensors capable of acquiring sensor data at the one or more launching devices. Additionally, the pyrotechnic misfire detection system may include a controller capable of transmitting the pyrotechnic launch command to the one or more launching devices, receiving the sensor data from the one or more sensors, and determining, based on the sensor data, that the one or more launching devices have misfired. Attached Figure Description

[0008] These and other features, aspects, and advantages of the invention will become better understood when the following detailed description is read with reference to the accompanying drawings, in which the same characters throughout the drawings denote the same parts, wherein: Figure 1 This is a schematic diagram of an embodiment of a smoke misfire detection system according to the present technology; Figure 2 This is a schematic diagram illustrating an embodiment of a fireworks misfire detection system based on sensor data from a fireworks display launcher, according to the present technology. Figure 3 This is a block diagram of a pyrotechnic misfire detection system, including a pyrotechnic controller and a firing device, based on the present technology. Figure 4 The diagram is based on a pyrotechnics controller according to the present technology, which includes a display for presenting status information of the launching device for a pyrotechnics display. Figure 5 This is a flowchart of the real-time smoke misfire detection method based on this technology; Figure 6 This is a flowchart of a method according to the present technology for performing a mitigation task in response to detecting a misfire in a fireworks display launcher; and Figure 7 This is a flowchart of a method for detecting misfires in a fireworks display launcher according to the present technology. Detailed Implementation

[0009] One or more specific embodiments will be described below. In an effort to provide a concise description of these embodiments, not all features of the actual implementation are described in the specification. It should be understood that, as in any engineering or design project, the development of any such actual implementation requires numerous implementation-specific decisions to achieve the developer's specific goals, such as compliance with system-related and business-related constraints, which may vary from one implementation to another. Furthermore, it should be understood that such development work may be complex and time-consuming, but will be nothing more than routine tasks of design, fabrication, and manufacturing for those skilled in the art who benefit from this disclosure.

[0010] When describing elements of various embodiments of this disclosure, the articles “a” and “the” are intended to mean the presence of one or more of the elements. The terms “comprising” and “including” are intended to be inclusive and mean that additional elements may be present in addition to the listed elements.

[0011] Fireworks displays may include multiple (e.g., thousands) launchers that fire fireworks in a specific ignition sequence to achieve a desired aesthetic result. In some cases, a single launcher or a group of launchers may be handled individually to allow for more complex ignition sequences. For example, certain fireworks may be designed to be launched in combination to create specific shapes, colors, or other pyrotechnic effects. Therefore, fireworks launch instructions may include instructions to launch specific fireworks at specific times. However, coordinating large-scale fireworks displays can be complex. For example, fireworks displays may complement, or be synchronized with, audio performances, countdowns, or other elements. The coordinator of a fireworks display may need to select appropriate launchers and projectiles, the location of the launchers, the timing of each fireworks ignition, etc., to achieve the desired aesthetic. Furthermore, launch conditions may be constrained by safety concerns.

[0012] In some cases, individual launchers in a fireworks display may misfire due to ignition failure, controller malfunction, firework quality issues, or other malfunctions. Undetected misfires can lead to further technical problems, potentially compromising the aesthetic quality of subsequent displays. In some situations, misfires can be manually detected by technicians before or after a new fireworks display by inspecting each launcher. However, manual inspection of each launcher can result in delays, increased complexity, or other costs, especially for large fireworks displays with numerous launchers.

[0013] Therefore, as will be described in more detail below, this disclosure provides a technique for efficiently detecting misfires of launching devices in a fireworks display. A misfire detection system for a fireworks display can detect misfires based on sensor data indicating whether a launching device has ignited or misfired, and its correlation with a fireworks command sent to the launching device. Specifically, the fireworks misfire detection system can compare sensor data for each launching device with a corresponding fireworks command for that launching device to determine whether the sensor data reflects (e.g., is aligned with or not aligned with) the corresponding fireworks command. For example, the sensor data may include vibration data acquired by a vibration sensor at a particular launching device, and the vibration data may be time-aligned with and compared to a launching command for the launching device (e.g., a launching command simultaneous with the vibration data) to detect a successful launch of the launching device, or alternatively, to detect a misfire of the launching device.

[0014] Alternatively or concurrently, sensor data can be compared with test data to determine the status of the launching device. For example, a misfire detection system can operate in a test mode in which sensor data from a successful launch (e.g., verified by a technician) is acquired. Thus, the sensor data from a successful launch can form a baseline, and the pyrotechnic controller can compare subsequently acquired sensor data to this baseline to determine a misfire and / or a successful launch. For example, sensor data from a misfire may deviate from reference sensor data from a successful launch.

[0015] Upon detection of a successful launch from a launching device, a successful launch indication can be displayed by a misfire detection system. Alternatively, if a misfire is detected, a corresponding misfire indication can be displayed. Therefore, the launch status of each launching device can be determined by the system in real time and / or remotely, eliminating the need for manual inspection of each launching device. Additionally, in some embodiments, the pyrotechnic controller can instruct an alternative (e.g., a backup) launching device to ignite in response to the detection of a misfire, thus maintaining the intended aesthetics of the pyrotechnics. Therefore, the challenges associated with misfires of one or more launching devices can be mitigated. Furthermore, it should be noted that while pyrotechnic displays, pyrotechnic misfires, and pyrotechnic ignition events are described herein, the disclosed techniques can be applied to other launching mechanisms, such as compressed air or gas launching systems. For example, sensor data can indicate electromechanical failures (e.g., valve failures) in compressed gas launching systems.

[0016] Considering the foregoing, Figure 1The illustration shows a system 10 including an array 14 of pyrotechnic controller 12 and launching devices 16. Launching devices 16 may include one or more types of launching devices suitable for launching pyrotechnics during a pyrotechnic display. Pyrotechnics may include fireworks, mortars, rockets, Roman candles, fountains, firecrackers, etc. In some cases, one or more launching devices in launching devices 16 may be loaded with projectile pyrotechnics, and each pyrotechnic may have a shape (e.g., a shell, a mine), chemical composition, or other characteristics that contribute visual elements to the pyrotechnic display. For example, based on the launch time of launching devices 16 and the pyrotechnics loaded in launching devices 16, a pyrotechnic display may include bright flashes (e.g., glints), light trails from the launching devices to a point in the sky, palm trees, spherical flower shapes, or other visual effects. Launching devices 16 and associated pyrotechnics may also be selected to produce audio elements (such as loud explosions (e.g., "report" or "salute")), or a combination of audio and visual elements. Furthermore, launching devices 16 may include one or more electric matches or other ignition starters that ignite the pyrotechnics loaded in launching devices 16. Each electric match may include, for example, a combustible material that ignites when an electric current passes through it. In the illustrated embodiment, the launching devices 16 are grouped such that they form an array 14 of launching devices 16. Each launching device 16 in the array 14 may be positioned, for example, on or associated with a base 17 (such as a structural frame (e.g., a mortar mount) or a sand-filled structural support (e.g., a mortar trough)) to support the launching device 16 in an upright or inclined orientation. As illustrated, a single launching device 16 may include one or more launching tubes 19. The launching tubes 19 may form a channel into which a single pyrotechnic 21 can be loaded and subsequently launched from the channel.

[0017] The pyrotechnic controller 12 can provide a pyrotechnic launch command 18 to the array 14 of launchers 16. The pyrotechnic launch command 18 may include current or other electrical characteristics that can ignite one or more launchers 16 of the array 14 via, for example, an electric match of the launcher 16. The pyrotechnic controller 12 can send the pyrotechnic launch command 18 to the array 14 to establish a launch schedule or launch timing, such that each launcher of the array 14 ignites its pyrotechnic 21 at a specific point in time or within a specific time range during the pyrotechnic display. Individual launchers 16 can be processed independently to launch different pyrotechnics at different times and / or in series or parallel with each other. In some cases, the launch command 18 and the pyrotechnic loading can be configured such that adjacent launch tubes 19 do not launch pyrotechnics simultaneously to avoid interference. In one example, the pyrotechnic launch command 18 can cause the launchers 16 to ignite their pyrotechnic 21 at the chorus of a musical performance, at the end of a pyrotechnic display, etc. For example, in response to the pyrotechnic launch command 18, the launchers 16 of the array 14 can be rapidly and continuously ignited to produce a series of aerial fireworks.

[0018] Array 14 may also include one or more sensors 20 capable of acquiring pyrotechnic sensor data 22 of the launching devices 16. The one or more sensors 20 may include microphones, pressure sensors, temperature sensors, vibration sensors, accelerometers, or other sensors suitable for acquiring sensor data to determine whether the launching devices 16 have successfully launched or misfired. In the illustrated embodiment, the one or more sensors 20 include sensors coupled to each launching device 16 in the launching devices 16. The launching device 16 may include, for example, a launching tube 19, and the sensors 20 may be positioned on the exterior of each launching tube 19. As mentioned, in some embodiments, each launching device 16 of array 14 may be supported by a base 17. In these embodiments, the one or more sensors 20 may include sensors 20 arranged on the base 17 or support structure of array 14, and thus, the sensors 20 may acquire pyrotechnic sensor data 22 of the plurality of launching devices 16 supported by the base 17. In another example, the one or more sensors 20 may include optical sensors positioned to capture infrared sensor data of each launching device 16. In another example, one or more sensors 20 may include cameras positioned to capture image data (e.g., video) of each emitting device 16. In any case, the pyrotechnic sensor data 22 acquired by one or more sensors 20 may be sent to the pyrotechnic controller 12 for analysis.

[0019] Although Figure 1 System 10 is illustrated as an array 14 including transmitting devices 16, but in some embodiments, system 10 may include multiple arrays 14 having a plurality of transmitting devices 16. Figure 2 The illustration depicts a system 10 in which a pyrotechnic controller 12 receives pyrotechnic sensor data from a first array 30 (e.g., an array of emitters 19), a second array 32, a third array 34, and a fourth array 36 during a pyrotechnic display. The illustrated arrangement is merely an example, and it should be understood that additional or fewer emitters 16 or arrays 14 may be used. Figure 2 The system 10 is illustrated for a specific time interval (such as a one-second snapshot) during a fireworks display. Furthermore, while the illustrated arrangement shows a separate sensor 20 associated with each array, in one embodiment, the sensor 20 may be coupled to each individual launcher or alternating launchers 16.

[0020] In the illustrated embodiment, the second array 32 and the third array 34 each successfully launch calibrated pyrotechnics, and therefore, the second pyrotechnic sensor data 38 of the second array 32 and the third pyrotechnic sensor data 40 of the third array 34 each include sensor data indicating a successful launch. For example, the second pyrotechnic sensor data 38 indicating a successful launch may include pressure data indicating rapid changes in pressure (e.g., within a pyrotechnic or gas compression launch tube), vibration data indicating rapid vibrations of the second array 32, infrared signatures indicating ignition flashes in one or more tubes of the second array 32, other sensor data indicating a successful launch, or combinations thereof. In some cases, the sensor data indicating a successful launch may include data at or above a set threshold. In one example, vibration amplitude from a vibration sensor associated with a single array 14 and / or a single launcher 16 at or above a threshold associated with a successful launch may indicate a successful ignition event. In another example, light intensity from an optical sensor associated with a single array 14 and / or a single launcher 16 may be at or above a threshold associated with a successful launch. Optical sensors can be configured to capture or select optical data from or just outside the firing tube opening to track firing or misfire.

[0021] On the other hand, neither the first array 30 nor the fourth array 36 successfully launched within the illustrated time interval. As a result, the first pyrotechnic sensor data 42 of the first array 30 and the fourth pyrotechnic sensor data 44 of the fourth array 36 each include sensor data that does not indicate a launch. In some cases, sensor data indicating a failure to launch may include data below a set threshold. In one example, vibration amplitude from a vibration sensor associated with a single array 14 and / or a single launching device 16 below a threshold associated with a successful launch may indicate a misfire. In another example, light intensity from an optical sensor associated with a single array 14 and / or a single launching device 16 may be below a threshold associated with a successful launch.

[0022] As will be understood, the first pyrotechnic sensor data 42 and the fourth pyrotechnic sensor data 44 may each include pressure data that does not indicate rapid changes in pressure, vibration data that does not indicate rapid vibrations, etc. Alternatively, the pressure data may indicate rapid changes in pressure, but such rapid changes in pressure may be inconsistent with a successful launch, or may include rapid vibrations inconsistent with a successful launch, etc. In some cases, the pyrotechnic controller 12 may determine that a misfire has occurred in array 14 (e.g., a misfire launch status for array 14 or one or more tubes 19 of array 14 may be determined) based on pyrotechnic sensor data from array 14 (e.g., during a time interval) and pyrotechnic commands sent to the array (e.g., for that time interval). However, it should be noted that in other cases, sensor data that does not indicate launch may not indicate a misfire (e.g., a misfire in the first array 30 and / or the fourth array 36) because the pyrotechnic commands (e.g., commands sent to the first array 30 and the fourth array 36) may not yet include commands for launch during the illustrated time interval. Therefore, as generally discussed herein, misfire detection may include determining whether the firing state of the firing device 16 is aligned with pyrotechnic firing commands for one or more time points.

[0023] Figure 3 The illustration shows a block diagram of the example launching device 16 and pyrotechnic controller 12 from the preceding figures. The launching device 16 may include an ignition circuit system 52 (such as an electric match) that facilitates the launching of a pyrotechnic device in response to a received electrical signal. The launching device 16 may also include one or more sensors 20, such as launching device coupled sensors 54, including microphones, pressure sensors, temperature sensors, vibration sensors, accelerometers, or other sensors suitable for acquiring sensor data to determine whether the launching device 16 has successfully launched or misfired, as described herein. Additionally, the launching device 16 may include an ignition indicator 56, which may display an indication of a misfire or successful launch in response to the detection of a misfire or successful launch by the launching device 16. For example, one or more sensors 54 may generate sensor data, the pyrotechnic controller 12 may determine that the sensor data indicates a successful launch, and the pyrotechnic controller 12 may send a signal to the ignition indicator 56 of the launching device 16 indicating an instruction for displaying an indication of a successful launch. The ignition indicator 56 may include a light-emitting diode (LED), a display, etc., and may display, for example, a green indicator indicating successful ignition, or alternatively, a red indicator indicating a misfire. This allows technicians to efficiently determine the status of the ignition device 16 without having to closely inspect it.

[0024] The pyrotechnics controller 12 may include, for example, a processing circuitry system 58, a memory 60, an ignition unit 62, a display 64, and a communication circuitry system 66. The processing circuitry system 58 may include one or more suitable processors capable of executing instructions for implementing the techniques disclosed herein, such as a general-purpose processor, a system-on-a-chip (SoC) device, an application-specific integrated circuit (ASIC), a programmable logic controller (PLC), an industrial PC (IPC), or some other similar processor configuration. These instructions are encoded in program or processor-executable code stored in a tangible, non-transitory computer-readable medium. The memory 60 may include one or more storage devices and may store machine-readable and / or processor-executable instructions (e.g., firmware or software) for execution by the processing circuitry system 58, such as instructions related to generating pyrotechnics commands, instructions related to determining the launch status, or instructions for generating alternative launch commands. In some cases, instructions may be generated using one or more machine learning (ML) models, computer vision functions, etc., to determine the launch status based on sensor data and launch commands. For example, instructions may be related to determining the launch status using computer vision based on sensor data from one or more cameras. Therefore, memory 60 can store, for example, control software, lookup tables, configuration data, ML models, etc. Memory 60 may include tangible, non-transitory machine-readable media, such as volatile memory (e.g., random access memory (RAM)) and / or non-volatile memory (e.g., read-only memory (ROM), flash memory, hard disk drive, and / or any other suitable optical, magnetic, or solid-state storage media). Memory 60 can store fireworks display configurations, launch schedules, launch status, etc. Memory 60 may also store instructions for determining the launch status based on sensor data and launch commands, and the processing circuitry system 58 can execute these instructions.

[0025] Ignition unit 62 may include a current source, power supply, etc., which facilitates the generation and / or transmission of an electrical signal as a launch command to launch device 16. For example, ignition unit 62 may generate and send one or more currents or other electrical characteristics to launch device 16 when instructed by processing circuitry system 58, which ignites ignition circuitry system 52 and actuates launch device 16. Although the illustrated example shows ignition unit 62 as part of controller 12, in embodiments, ignition unit 62 may be coupled to launch device 16 and / or array 14. In some cases, ignition unit 62 may allow manual control by a technician via a panel, electrical box, or other interface. For example, a technician may instruct ignition unit 62 to generate and send commands to actuate a corresponding backup launcher in response to a misfire in launch device 16. Additionally or alternatively, pyrotechnic controller 12 may include communication circuitry system 66, and communication circuitry system 66 may facilitate the transmission of launch commands, sensor data, display commands, etc., to launch device 16 or other devices via wireless communication with a corresponding communication circuitry system 67 of launch device 16.

[0026] The pyrotechnic controller 12 may also be communicatively coupled to one or more additional sensors 68, such as cameras or optical sensors positioned to acquire sensor data from the launcher 16. In one embodiment, the additional sensor 68 may generate data on the connections between the pyrotechnic controller 12 and the launcher 16, multiple launchers (e.g., an array 14 of launchers), an array 14 of multiple launchers, or each launcher 16 in a pyrotechnic display. The additional sensor 68 may also serve as an alternative to one or more sensors 54 of the launcher 16 in the event of a technical malfunction or other failure of one or more sensors 54. In some embodiments, the additional sensor 68 may generate sensor data from the ignition unit 62, such that the pyrotechnic controller 12 can determine whether a misfire is due to a malfunction in the ignition unit 62 (e.g., the ignition unit 62 fails to generate an electrical signal in response to an instruction from the processing circuitry system 58).

[0027] Display 64 may show an indication of successful launch or misfire of launcher 16. Display 64 may include a graphical user interface (GUI) (such as a touchscreen GUI) and may display information about the current or planned fireworks display, such as launcher location, launcher type, launch command schedule, etc. In particular, the GUI displayed by display 64 may include an indication of the launch status of launcher 16 as determined by fireworks controller 12.

[0028] In some embodiments, the display 64 may display transmission status indications for multiple transmitting devices. Figure 4An embodiment of system 10 is illustrated. In the illustrated embodiment, the display 64 of the pyrotechnic controller 12 displays status indicators for the first, second, third, fourth, fifth, and sixth arrays of the pyrotechnic display 70. In the illustrated embodiment, each array of the pyrotechnic display 70 includes a sensor that generates corresponding sensor data for that array, and the corresponding sensor data is sent to the pyrotechnic controller 12 as described herein. Then, for each corresponding array, the pyrotechnic controller 12 can determine whether a successful launch or a misfire has occurred for that corresponding array based on whether the corresponding sensor data corresponds to a launch command for that corresponding array. For example, the sensor data for the second array may indicate rapid vibrations within a 20-second time interval after the start of the pyrotechnic display. The pyrotechnic controller 12 can determine that the sensor data aligns with a launch command for the second array (e.g., a command for T-20 seconds), and thus can determine a successful launch for the second array. This determination can be displayed as part of the second array indicator 72 (illustrated here as a checkmark after the list of second arrays).

[0029] Alternatively, the pyrotechnic controller 12 can determine that a misfire has occurred in one or more launching devices based on sensor data and launch commands. For example, sensor data for the fourth array may indicate a lack of rapid vibrations for a certain time interval or for the duration of a pyrotechnic display. The pyrotechnic controller 12 can determine that the sensor data for the fourth array is not aligned with a launch command for the fourth array (e.g., launch at T-25 seconds), and thus determine a misfire for the fourth array. In another example, the sensor data for the fourth array may indicate rapid vibrations in a time interval not aligned with a launch time interval included in the launch command (e.g., rapid vibrations at T-5 seconds, launch command at T-20 seconds), and the pyrotechnic controller 12 can accordingly determine a misfire for the fourth array. In any case, the determination of a misfire for the fourth array can be displayed as a fourth array indicator 74, illustrated here as an "X" mark after the list of fourth arrays.

[0030] In some embodiments, the pyrotechnic controller 12 may not determine whether a misfire or successful launch has occurred in one or more launchers. For example, sensor data from the launchers may only partially indicate a successful launch, or may not indicate overlap or alignment with a threshold for the launch command. In such cases, the pyrotechnic controller 12 may instead determine a confidence interval associated with the launcher based on sensor data and the launch command for the launcher. Such determination may arise from a failed but still evident launch, sensor data for the launcher being affected by the ignition of neighboring launchers, etc. For example, sensor data for the sixth array may indicate some vibrations (e.g., less than threshold launch vibrations) in a time interval nearly aligned with the launch command for the sixth array (e.g., some vibrations at T-21 seconds for a command to launch at T-20 seconds). Thus, the determination of the confidence interval (e.g., neither a misfire nor a successful launch) may be shown as the sixth array indicator 76, illustrated here as a question mark following the list of the sixth arrays. In some embodiments, the numerical confidence interval (e.g., 50%, 75%) may be determined by the pyrotechnic controller 12 based on launch commands, sensor data, threshold times input via a graphical user interface, or sensor values, and may be indicated accordingly via the display 64. In any case, the displayed indication may indicate to a technician, for example, that the launcher may require a manual check for misfires at the end of a pyrotechnic display.

[0031] In some embodiments, the determination of misfires, successful launches, and / or confidence intervals, and the corresponding indications, can be dynamically updated throughout the duration of the fireworks display. This can be advantageous for fireworks displays that include launching devices or arrays that may ignite over multiple time intervals throughout the display, as the launching devices may successfully ignite and subsequently misfire, or misfire and later successfully ignite, etc. For example, the fireworks controller 12 may determine a successful launch of a second array in a first time interval (e.g., T-10 seconds), but may determine a misfire of the second array in a second time interval (e.g., T-20 seconds). Thus, the second array indicator 72 may display a checkmark after the first successful launch and may update to display an "X" after a misfire is determined. Alternatively or additionally, the display 64 may display a matrix, table, or similar mapping from launching devices to commanded launches, and may display an indication of whether each commanded launch was determined to be a successful launch or a misfire. For example, the display 64 may display separate column entries for each commanded launch.

[0032] In some cases, certain components and functions may be included and performed by a device or system separate from the pyrotechnic controller 12. For example, the pyrotechnic controller 12 may include an ignition unit 62 for communicating launch commands, a communication circuitry 66, a processor 58, and / or a memory 60, but may not receive sensor data, determine launch status, instruct backup tubes to launch, etc. Instead, such functions may be performed by a separate misfire detection system having one or more of the processor 58, memory 60, ignition unit 62, display 64, and communication circuitry 66. In such an example, the pyrotechnic controller 12 may use launch commands to launch pyrotechnics, while the separate misfire detection system may, for example, use launch commands to determine misfires.

[0033] Considering the foregoing, Figure 5 This is a flowchart of method 100 for detecting misfires in fireworks displays, and references... Figure 1-4 This will be discussed. Although described as being performed by pyrotechnic controller 12, one or more steps in method 100 may be performed by a separate misfire detection system. The process begins with initiating a pyrotechnic display (box 102). Initiating a pyrotechnic display may include, for example, loading launch commands for each launcher and / or an array of launchers into the memory of the pyrotechnic controller (e.g., memory 60 of pyrotechnic controller 12), loading projectiles or other pyrotechnics into each launcher, initializing audio output synchronized with the pyrotechnic display, activating timers for determining the correspondence between sensor data and launch commands, etc. Initiating a pyrotechnic display may also include sending a first launch command (e.g., a first current) to one or more launchers to begin the pyrotechnic display.

[0034] After the fireworks display is initiated (box 102), sensor data from one or more sensors 20 can be received at the fireworks controller 12 (box 104). As described herein, the sensor data may include audio values, pressure values, temperature, vibration data, acceleration data, etc., from one or more launchers or an array of launchers. The received sensor data may be aligned with the corresponding launch command (box 106). Aligning the received sensor data with the corresponding launch command may include mapping the received sensor data to the launch command. For example, sensor data received from a sensor attached to a first launcher may be aligned with a launch command for the first launcher stored in the memory 60 of the fireworks controller 12, and sensor data received from a sensor on a mortar mount attached to a first array of launchers may be aligned with a launch command for the first array stored in the memory 60 of the fireworks controller 12, etc. Additionally, aligning the received sensor data with the corresponding launch command may include time alignment. For example, the fireworks controller 12 may assign timestamps to the received sensor data (e.g., based on a timer started during initiation), and the received sensor data may be compared with the launch command at the timestamp. Furthermore, a delay can be determined during the testing process of a fireworks display, representing the time delay between the transmission of a launch command and the reception of sensor data indicating a successful launch. This delay can be subtracted from the timestamp to account for delays in the transmission of commands to the launching device and / or delays in receiving sensor data from the sensors of the launching device.

[0035] In some embodiments, sensor data can be received in real time during a fireworks display and compared with thresholds to determine whether each launcher has successfully launched or misfired. For example, during a testing phase of a fireworks display, a vibration threshold (e.g., 100 Hz) can be set as a minimum threshold indicating launch. Therefore, if sensor data indicating vibration above the threshold is received and mapped to a time interval including a launch command for the purpose of launching, the fireworks controller 12 determines a successful launch (box 110). However, if sensor data indicating vibration below the threshold is received and mapped to a time interval including a launch command for the purpose of launching, the fireworks controller 12 can determine a misfire (box 108). Additionally, if received sensor data indicating vibration above the threshold is mapped to a time interval excluding a launch command for the purpose of launching, the fireworks controller can determine a misfire (box 108). In any case, the fireworks controller 12 can continue to receive sensor data from the launchers (box 104).

[0036] Figure 6 This is a flowchart of a method 120 for performing a mitigation task in response to determining a misfire in one or more launchers of a fireworks display, and can be used as... Figure 5The method 100 may be performed in part or in combination with it. The process may begin by determining a misfire, as generally described above (box 122). In response to determining a misfire for one or more launching devices, an indication of a misfire may be displayed, for example via the display 64 of the pyrotechnic controller 12 or other suitable means (box 124). The determination of a misfire for one or more launching devices may be displayed as an "X" following a list of misfire launching devices, or as part of a matrix of indicated launching devices and launching devices. In another example, the graphical user interface presented by the display 64 may include a map of the launching areas of the pyrotechnic display (e.g., the area from which the pyrotechnics are launched), and misfires may be indicated on the map by appropriate indicators.

[0037] The pyrotechnic controller 12 can also instruct a backup launcher to ignite in response to a misfire, for example, by enhancing the launch command to include instructions for igniting a backup launcher (box 126). Backup launchers can be identified, for example, through a mapping from launchers (e.g., the main launcher) to corresponding backup launchers. Backup launchers may be located near one or more launchers and may have similar characteristics (e.g., projectile type, chemical composition) such that igniting a backup launcher in the event of a misfire maintains the intended aesthetics of the pyrotechnic performance. Furthermore, backup launchers may include sensors to acquire sensor data of the backup launcher, which can be sent to the pyrotechnic controller 12, and the pyrotechnic controller 12 can determine whether the backup launcher has successfully launched or misfired. Thus, if a misfire is detected in a backup launcher, method 120 can restart from determining a misfire (box 122). Additionally, the backup launcher itself may have an additional backup device that can be instructed to launch if the backup launcher misfires.

[0038] Figure 7 This is a flowchart of method 130 for detecting misfires in fireworks displays, and references... Figure 1-4 Let's discuss this further. The process may begin with initiating a fireworks display (box 132). As mentioned herein, initiating a fireworks display may include, for example, loading launch commands for each launcher and / or an array of launchers into the memory of the fireworks controller, loading projectiles or other fireworks into each launcher, initializing audio output synchronized with the fireworks display, starting a timer to determine when the fireworks display has ended, etc. Initiating a fireworks display may also include sending a first launch command (e.g., a first current) to one or more launchers to begin the fireworks display.

[0039] After the fireworks display is initiated (box 132), sensor data generated at the launching devices can be received at the fireworks controller 12 (box 134). As described herein, the sensor data may include audio values, pressure values, temperature, vibration data, acceleration data, etc., from one or more launching devices or an array of launching devices over a time interval. The sensor data can be used to determine a successful launch of a launching device (in which sensor data of the launching device was acquired during the time interval) by, for example, comparing the sensor data with a threshold (box 136). The threshold may include a minimum volume, minimum pressure, minimum vibration, etc., characterizing a successful launch. If the sensor data indicates a successful launch within the time interval, a successful launch is determined for the launching device (box 138).

[0040] If no successful launch is detected within the time interval (e.g., sensor data does not exceed a threshold for the time interval), a determination is made as to whether the fireworks display has ended (box 138). The determination can be based on the expiration of a timer started during the initiation of the fireworks display (e.g., a timer stored in the memory 60 of the fireworks controller 12). Alternatively, the determination can be based on input by a technician via, for example, a graphical user interface of the display 64 or other suitable input means. If the display has not yet ended, the fireworks controller 12 may continue to receive sensor data (box 134).

[0041] If the fireworks display has ended, a misfire can be identified (box 140). In some embodiments, this may include identifying a misfire for each launcher that was not determined to have successfully launched (e.g., in box 138). In response, mitigation tasks may be performed by the fireworks controller 12. Specifically, the fireworks controller may provide notification of the location of each misfired launcher (box 142) and / or the identity of each misfired launcher. For example, the display 64 may present a text notification including the grid location of each launcher identified as having misfired, or may present a map indicating the location of each misfired launcher. Alternatively or additionally, the notification may include an active indicator light on or near the launcher associated with the misfire.

[0042] While only certain features of the invention have been illustrated and described herein, many modifications and alterations will occur to those skilled in the art. Therefore, it is to be understood that the appended claims are intended to cover all such modifications and alterations that fall within the true spirit of this disclosure.

[0043] The techniques presented and claimed herein are referenced and applied to concrete examples and substantial objects that can arguably improve the practical nature of the art, and are therefore not abstract, abstract, or purely theoretical. Furthermore, if any claim appended to this specification contains one or more elements designated as “component for (performing)...(function)” or “step for (performing)...(function)”, such elements are intended to be interpreted in accordance with 35 USC 112(f). However, for any claim containing elements designated in any other manner, such elements are not intended to be interpreted in accordance with 35 U.SC 112(f).

Claims

1. A smoke and fire misfire detection system, comprising: One or more sensors configured to acquire sensor data indicating a pyrotechnic ignition event at one or more transmitting devices; as well as The controller is configured as follows: Receive sensor data from the one or more sensors; Determine whether the sensor data corresponds to a fireworks launch command; as well as Based on the absence of a corresponding pyrotechnic launch command in the sensor data, it is determined that one or more launching devices have misfired.

2. The system according to claim 1, wherein, The one or more launching devices are coupled to a plurality of launching tubes, each of the plurality of launching tubes including one of a plurality of pyrotechnics.

3. The system according to claim 2, wherein, Determining whether the sensor data corresponds to the fireworks launch command includes identifying the launch status of each corresponding firework.

4. The system according to claim 3, wherein, Determining that one or more of the transmitting devices have misfired includes identifying a single transmitting tube among the plurality of transmitting tubes that has a misfired firing state.

5. The system according to claim 2, wherein, The one or more sensors include a vibration sensor coupled to each of the plurality of transmitting tubes.

6. The system according to claim 1, wherein, The one or more sensors include at least one vibration sensor of the transmitting device coupled to the one or more transmitting devices.

7. The system according to claim 6, wherein, The sensor data indicates the vibration of the launching device at the same time as the execution of the fireworks launch command.

8. The system according to claim 7, wherein, A first vibration amplitude above a threshold indicates a successful ignition event, and a second vibration amplitude below the threshold indicates a misfire.

9. The system of claim 1, further comprising generating a notification indicating the misfire.

10. The system according to claim 9, wherein, The notification includes the location or identity of one or more of the transmitters associated with the misfire.

11. The system according to claim 1, wherein, The one or more sensors include a camera.

12. A method for detecting misfires in fireworks, comprising: Receive fireworks launch commands at the fireworks launch controller; The fireworks display is initiated via the fireworks launch controller based on the fireworks launch command. The sensor data indicating a misfire is received via the pyrotechnics launch controller; as well as The notification of the misfire is generated via the pyrotechnic launch controller.

13. The method according to claim 12, wherein, The sensor data is pressure sensor data, optical sensor data, or a combination thereof from the transmitting device.

14. The method according to claim 12, wherein, The sensor data indicating a misfire includes vibration signals indicating a misfire in one or more firing tubes of the firing device.

15. The method according to claim 12, wherein, The notification includes the location or identity of the launching device associated with the misfire.

16. The method according to claim 12, wherein, The notification includes an activated indicator light on or near the transmitter associated with the misfire.

17. A smoke and fire misfire detection system, comprising: One or more transmitting devices, including: At least one firing tube; and An ignition circuit system configured to emit fireworks from the at least one firing tube based on a fireworks emission command; One or more sensors configured to acquire sensor data at the one or more transmitting devices; and The controller is configured as follows: The fireworks launch command is transmitted to the one or more launching devices; Receive sensor data from the one or more sensors; and Based on the sensor data, it is determined that one or more of the transmitting devices have misfired.

18. The system according to claim 17, wherein, The controller is configured to determine that the one or more launching devices have misfired based on the sensor data indicating that no fireworks were launched within a time range corresponding to the indicated fireworks launch from the launching tube.

19. The system according to claim 18, wherein, The sensor data includes deviations from a reference associated with the pyrotechnic emission.

20. The system according to claim 17, wherein, The controller is configured to: The pyrotechnic launch command is enhanced to include a command to launch one or more backup launchers in response to the determination that one or more launchers have misfired; as well as The enhanced pyrotechnic launch command is transmitted to the one or more backup launchers.

Images