Derivative works — US Patent 11709037

Defensive Disclosure: Innovations in Automated Pyrotechnic and Actuation Systems

Publication Date: May 10, 2026
Reference: This document is submitted as a defensive publication to establish prior art against future patent applications related to the technologies described herein, which are derivative of, or improvements upon, the concepts disclosed in U.S. Patent No. 11,709,037.

Introduction

This document discloses a series of innovations and alternative embodiments that expand upon the core concepts of automated pyrotechnic control systems, as outlined in U.S. Patent No. 11,709,037 ("the '037 patent"). The purpose of this disclosure is to place into the public domain a variety of modifications, enhancements, and alternative applications of the described technology. By doing so, we aim to prevent the patenting of obvious and incremental variations by third parties, thereby fostering innovation and open competition in the fields of pyrotechnics, remote actuation, and synchronized event management.

The following sections detail derivative inventions across five axes of innovation: (1) Material and Component Substitution, (2) Operational Parameter Expansion, (3) Cross-Domain Application, (4) Integration with Emerging Technologies, and (5) "Inverse" or Failure Mode Operation.

1. Material & Component Substitutions

The '037 patent describes a detonation wire with a connector housing and one or more firework igniters. The following are variations on the materials and components used in this system.

1.1. High-Durability, All-Weather Housing Materials

Enabling Description: The housing (210) of the hybrid connection assembly (202), originally conceived as plastic, is re-engineered using a high-performance thermoplastic, such as Polyether ether ketone (PEEK). This substitution provides superior thermal resistance for repeated use with high-temperature pyrotechnics, enhanced chemical resistance to black powder and other corrosive residues, and superior mechanical strength for rugged field use. The cover (240) and latch (250) mechanisms are fabricated from a fiber-reinforced polymer composite (e.g., carbon-fiber-reinforced PEEK) to prevent warping and ensure a secure seal over thousands of thermal cycles. The internal electrical contacts (220) are gold-plated beryllium copper for improved conductivity and corrosion resistance.
```
graph TD
    A[Firing Module] -->|Detonation Wire| B(Hybrid Connector);
    B --> C{PEEK Housing};
    C --> D[Carbon-Fiber-Reinforced PEEK Lid];
    C --> E[Gold-Plated Be-Cu Contacts];
```

1.2. Solid-State Relay (SSR) Firing Module

Enabling Description: The detonation modules (30) within the firing module (4) are redesigned to use solid-state relays (SSRs) instead of traditional electromechanical relays. This modification eliminates moving parts, increasing the system's lifespan and reliability. The SSRs provide faster switching times, enabling more precise synchronization of pyrotechnic effects to audio, with a timing resolution of less than 1 millisecond. The control circuitry (28) is updated with a microcontroller (e.g., an ESP32) that can drive the SSRs directly using GPIO pins, reducing component count and power consumption.
```
sequenceDiagram
    participant MC as Mobile App
    participant FM as Firing Module (ESP32)
    participant SSR as Solid-State Relay
    participant Igniter
    MC->>FM: FIRE_CUE_1
    activate FM
    FM->>SSR: Set Gate High
    activate SSR
    SSR->>Igniter: Close Circuit (Current Flow)
    activate Igniter
    Igniter-->>FM: Fired Confirmation (Current Sense)
    deactivate Igniter
    FM-->>MC: CUE_1_FIRED
    deactivate FM
    deactivate SSR
```

1.3. Thermoelectric (Peltier) Igniter

Enabling Description: The resistive heating element (264) in the fuse igniter (214) is replaced with a miniature Peltier device. When a current is applied, one side of the Peltier element heats rapidly to a temperature sufficient to ignite a standard pyrotechnic fuse (6B), while the other side cools. After ignition, the current can be reversed, actively cooling the ignition point. This allows for a much faster reset time between uses and reduces the risk of accidental ignition from residual heat. The power controller (221) is modified to include an H-bridge circuit to control the polarity of the voltage supplied to the Peltier element.
```
stateDiagram-v2
    [*] --> Idle
    Idle --> Heating: FIRE command
    Heating --> Ignition: Temp > 200°C
    Ignition --> Cooling: REVERSE_CURRENT command
    Cooling --> Idle: Temp < 40°C
```

1.4. Universal Quick-Connect Ignition Port

Enabling Description: The connection assembly (52) is redesigned with a universal, hermaphroditic magnetic connector. This connector replaces the dedicated ports (220) and grooves (74, 235, 276) with a single, standardized interface. The connector uses a set of concentric, spring-loaded pogo pins for electrical connection and powerful neodymium magnets for secure physical attachment. This allows for rapid, blind mating of both e-match style igniters and reusable fuse igniters, which are housed in a standardized puck. The system uses a simple 1-Wire communication protocol over one of the pins to identify the type of igniter connected.
```
graph LR
    subgraph Firing Module
        A(Universal Magnetic Port)
    end
    subgraph Igniter Puck
        B(Magnetic Connector)
        C(1-Wire ID Chip)
        D{Ignition Element}
    end
    A -- Neodymium Magnets & Pogo Pins --> B
    B -- Electrical & Data --> D
    B -- 1-Wire Protocol --> C
```

1.5. Biodegradable Housing and Wire Insulation

Enabling Description: For single-use or environmentally sensitive applications, the housing (210) of the hybrid connector and the insulation of the detonation wires (32) are fabricated from a biodegradable polymer, such as polylactic acid (PLA) or polyhydroxyalkanoates (PHA), blended with flame-retardant additives. This ensures that any components left in the field after a display will naturally decompose over a period of months, reducing environmental impact, particularly in parks or conservation areas.
```
graph TD
    A[Biodegradable Components] --> B(PLA/PHA Housing);
    A --> C(PLA/PHA Wire Insulation);
    B --> D[Environmental Decomposition];
    C --> D;
```

2. Operational Parameter Expansion

2.1. Micro-Pyrotechnic System for Theatrical Effects

Enabling Description: The entire system is miniaturized for indoor or close-proximity theatrical applications. The firing module (4) is scaled down to the size of a credit card, powered by a LiPo battery. The detonation wires (32) are replaced with thin, flexible Kapton circuits. The igniters are designed to activate micro-smokes, sparks, or small non-projecting pyrotechnic effects. The control application includes features for precise, low-latency synchronization with stage lighting and sound cues, controlled via a DMX or Art-Net interface integrated into the server (8).
```
graph TD
    A[DMX/Art-Net Controller] --> B(Server);
    B --> C{Wi-Fi/BLE};
    C --> D[Micro Firing Module];
    D --> E(Kapton Flex Circuit);
    E --> F[Micro-Igniter];
    F --> G((Theatrical Effect));
```

2.2. High-Altitude Weather Rocket Deployment System

Enabling Description: The system is adapted for high-altitude scientific research. A ruggedized firing module is integrated into the payload of a weather balloon or sounding rocket. It is designed to operate in low-pressure (-90 kPa) and low-temperature (-70°C) environments. The control circuitry (28) is hardened against radiation, and the batteries (230) are replaced with a high-discharge, wide-temperature-range lithium-thionyl chloride battery pack. The system is used to sequentially deploy atmospheric sensors or chaff at programmed altitudes, triggered by an onboard barometric sensor or a command from the mobile device (6) via a long-range LoRaWAN radio link.
```
sequenceDiagram
    participant GroundControl as Ground Control (Mobile Device)
    participant Payload as High-Altitude Payload
    participant Altimeter
    participant FiringModule as Firing Module
    Payload->>Altimeter: Read Altitude
    Altimeter-->>Payload: 50,000 ft
    Payload->>FiringModule: Execute Sequence 1
    activate FiringModule
    FiringModule->>Igniter1: Fire
    deactivate FiringModule
    GroundControl->>Payload: LoRaWAN Command: Deploy_Payload_2
    Payload->>FiringModule: Execute Sequence 2
    activate FiringModule
    FiringModule->>Igniter2: Fire
    deactivate FiringModule
```

2.3. Submersible System for Underwater Demolition/Signaling

Enabling Description: The firing module housing (202) and hybrid connection assembly (202) are environmentally sealed to an IP68 rating, capable of submersion to 50 meters. All external connectors are replaced with wet-mateable connectors. The wireless communication (24) is replaced with a hydro-acoustic modem for communication with a submerged control unit or a surface-based mobile device via a buoyed RF gateway. The system can be used for precise, timed detonation of underwater explosive charges for civil engineering or for activating underwater signaling flares.
```
graph TD
    A[Surface Controller] -- RF --> B(Gateway Buoy);
    B -- Acoustic Modem --> C[Submersible Firing Module];
    C -- Sealed Cable --> D(Wet-Mate Connector);
    D --> E(Underwater Charge/Flare);
```

3. Cross-Domain Application

3.1. Agricultural Pest Deterrent System

Enabling Description: The automated detonation system is repurposed to control an array of non-lethal pest deterrent devices in a large agricultural field. The fireworks (2) are replaced with sonic emitters, strobe lights, and compressed air cannons. The mobile application (100) is adapted to allow a farmer to schedule deterrent patterns based on time of day, crop type, or data from wildlife-sensing IoT cameras. The system uses a mesh network (e.g., Zigbee or Wi-SUN) to connect multiple firing modules (4) across a wide area, ensuring coordinated activation to effectively drive pests from fields.
```
classDiagram
class MobileApp {
    +createDeterrentSchedule()
    +viewPestActivityMap()
    +manualActivate(deviceId)
}
class FiringModule {
    -deviceID
    -deviceType: enum {SONIC, STROBE, AIR_CANNON}
    +receiveCommand(command)
    +activate()
}
class IoT_Camera {
    +detectPest()
    +sendAlert()
}
class Server {
    +processPestAlert()
    +triggerDeterrentSequence()
}
MobileApp --|> Server
Server --> FiringModule : Zigbee/Wi-SUN Mesh
IoT_Camera --> Server
```

3.2. Aerospace: Micro-Satellite Thruster Array Ignition

Enabling Description: The core principle of a remote, timed, multi-channel ignition system is applied to the attitude control of a nano- or pico-satellite (e.g., a CubeSat). The "fireworks" are replaced by an array of solid-fuel micro-thrusters. The firing module (4) becomes an onboard flight computer with a highly reliable, radiation-hardened driver circuit. The "remote control" (6) is a ground station, which uplinks a sequence of thruster firings (a "show") to achieve a desired orbital maneuver or attitude adjustment. The system's ability to pre-program and simulate sequences on the ground before execution is critical for mission success.

sequenceDiagram
    autonumber
    GroundStation->>Satellite: Uplink Maneuver Sequence (JSON)
    Satellite->>FlightComputer: Store Sequence in Memory
    FlightComputer->>FlightComputer: Verify Sequence Integrity (CRC Check)
    FlightComputer-->>Satellite: Acknowledge Uplink
    Satellite-->>GroundStation: Telemetry: Sequence OK
    FlightComputer->>ThrusterDriver: Execute Command #1 (e.g., Fire Thruster Z+)
    ThrusterDriver->>MicroThruster: Activate Igniter
    FlightComputer->>InertialMeasurementUnit: Read Attitude Change
    InertialMeasurementUnit-->>FlightComputer: Gyro/Accel Data
    FlightComputer->>GroundStation: Telemetry: Maneuver Execution & New Attitude

3.3. Consumer Electronics: Immersive Haptic Feedback System

Enabling Description: The detonation system is re-imagined as a distributed haptic feedback system for virtual reality (VR) or home theater environments. The firing modules (4) are small, wearable units or are embedded in a vest or chair. The "fireworks" (2) are replaced with a variety of haptic actuators: high-force linear resonant actuators (LRAs), piezoelectric actuators for sharp taps, and thermal actuators (Peltier coolers/heaters) for temperature sensations. The mobile app (100) becomes a control hub that parses a "haptic track" (analogous to the song in the '037 patent) and dispatches timed commands to the haptic modules via a low-latency, real-time Bluetooth LE broadcast, creating synchronized physical sensations that correspond with on-screen action or VR events.
```
graph TD
    subgraph VR/Gaming System
        A[Game/Movie Engine] --> B(Haptic Track Parser);
    end
    B --"Timestamped Haptic Events"--> C[Control Hub App];
    C --"Bluetooth LE Broadcast"--> D1(Haptic Module 1 - Chest);
    C --"Bluetooth LE Broadcast"--> D2(Haptic Module 2 - Back);
    C --"Bluetooth LE Broadcast"--> D3(Haptic Module 3 - Arms);
    D1 --> E1(LRA Actuator);
    D2 --> E2(Piezo Actuator);
    D3 --> E3(Thermoelectric Actuator);
```

4. Integration with Emerging Tech

4.1. AI-Powered Choreography and Safety Monitoring

Enabling Description: The mobile application (100) is enhanced with a machine learning module. This module can analyze an audio track (e.g., music) and automatically generate a pyrotechnic show by identifying beats, crescendos, and key musical moments, then matching them with suitable fireworks from the user's available inventory (identified via QR codes). Furthermore, the firing module (4) is equipped with a microphone and an accelerometer. An onboard AI model (e.g., a TinyML model) continuously monitors the audio signature and vibration patterns during a show. It can detect anomalies, such as a dud (no explosion sound after a firing command) or a catastrophic malfunction (e.g., a cake tipping over, detected by the accelerometer), and automatically pause or terminate the show, sending an alert to the user's device (6).
```
graph TD
    A[Audio File] --> B{AI Choreography Engine};
    B -- Scans Inventory --> C(Fireworks Database);
    B --> D[Generated Show File .JSON];
    D --> E(Mobile App);
    E -- BLE --> F(Firing Module);

    subgraph "Real-time Safety"
        G(Firing Module) -- "Vibration/Sound" --> H{Onboard TinyML Model};
        H -- "Anomaly Detected" --> I[Emergency Stop];
        I --> G;
        H -- "Anomaly" --> J(Alert to Mobile App);
    end

    F --> G
```

4.2. IoT-Enabled Distributed Firing Network with Real-Time Environmental Sensing

Enabling Description: Each firing module (4) is equipped with an IoT communication module (e.g., LoRaWAN or NB-IoT) and sensors for wind speed, wind direction, temperature, and humidity. Multiple modules can be deployed over a large area, forming a network managed by a cloud-based server (8). Before and during a show, the server collects real-time environmental data from all modules. It can automatically adjust firing angles or timing to compensate for wind drift or cancel specific devices if conditions become unsafe (e.g., high winds). This allows for larger, safer, and more complex shows distributed across a landscape, all controlled from a single interface.

flowchart TD
    subgraph Cloud_Platform
        Server[Server 8]
        Analytics[Weather Analytics Engine]
    end

    subgraph Field_Nodes
        FM1[Firing Module 1 <br> Wind/Temp/Humidity Sensors]
        FM2[Firing Module 2 <br> Wind/Temp/Humidity Sensors]
        FMN[Firing Module N <br> Wind/Temp/Humidity Sensors]
    end

    MobileApp[Mobile App 6] -- "Control/Monitor" --> Server
    Server -- "Commands" --> FM1
    Server -- "Commands" --> FM2
    Server -- "Commands" --> FMN

    FM1 -- "Sensor Data" --> Server
    FM2 -- "Sensor Data" --> Server
    FMN -- "Sensor Data" --> Server
    Server -- "Data" --> Analytics
    Analytics -- "Safety Adjustments" --> Server

4.3. Blockchain for Pyrotechnic Lifecycle Tracking

Enabling Description: A private blockchain is established for tracking the lifecycle of commercial-grade pyrotechnics. Each firework (2) or case of fireworks is assigned a unique digital identity (a non-fungible token or NFT) at the point of manufacture. This token's metadata includes manufacturer, batch number, explosive content, and safety information. As the firework moves through the supply chain (distributor, retailer, technician), each transfer is recorded as a transaction on the blockchain, providing an immutable chain of custody. The firing module (4) acts as a node on the network. Before arming, it verifies the firework's authenticity and history by querying the blockchain. The final firing event is recorded, permanently "retiring" the firework's digital token. This system enhances safety, prevents counterfeiting, and provides a transparent audit trail for regulators.
```
erDiagram
    MANUFACTURER ||--o{ FIREWORK_TOKEN : creates
    FIREWORK_TOKEN {
        string tokenId PK
        string manufacturer
        string batchNumber
        string type
    }
    DISTRIBUTOR ||--|{ TRANSACTION : creates
    TECHNICIAN ||--|{ TRANSACTION : creates
    TRANSACTION {
        string txId PK
        string fromAddress
        string toAddress
        timestamp
    }
    FIREWORK_TOKEN ||--|{ TRANSACTION : has
    FIRING_MODULE ||--|{ FIRING_EVENT : records
    FIRING_EVENT {
        string eventId PK
        string tokenId FK
        timestamp
        gpsLocation
    }
```

5. The "Inverse" or Failure Mode Designs

5.1. Failsafe Dual-Processor Firing Module

Enabling Description: The firing module's control circuitry (28) is redesigned with a dual-processor architecture. A primary processor (e.g., ARM Cortex-M4) handles the wireless communication, show timing, and user interface commands. A secondary, much simpler safety co-processor (e.g., an ATTiny85) acts as a watchdog and safety interlock. The safety processor directly controls the power gate to the igniter circuits. It receives a constant "heartbeat" signal from the primary processor. If this heartbeat ceases, or if onboard sensors (e.g., accelerometer, temperature sensor) detect a fault condition (e.g., the unit is tipped over), the safety processor immediately and irrevocably cuts power to all detonator outputs, preventing any further firing, regardless of commands from the primary processor or the user.
```
graph TD
    subgraph Failsafe Firing Module
        A[Primary CPU<br>(ARM Cortex-M4)]
        B[Safety Co-Processor<br>(ATTiny85)]
        C[Wireless Module]
        D[Power Gate<br>(MOSFET)]
        E[Igniter Circuits]
        F[Sensors<br>(Accel, Temp)]

        C -- Commands --> A
        A -- "Heartbeat Signal" --> B
        A -- "Fire Command" --> E
        F -- "Fault Data" --> B
        B -- "Enable/Disable" --> D
        D -- "Power" --> E
    end
```

5.2. Limited-Functionality "Manual Only" Mode

Enabling Description: The system is designed with a physical "mode" switch on the housing (202) of the firing module (4). In "Auto" mode, it functions as described in the '037 patent. When switched to "Manual" mode, it enters a low-power, limited-functionality state. In this state, the Bluetooth radio is disabled, and the processor (29) will only accept firing commands from physical buttons located directly on the housing, one for each detonator port (220). This mode allows for safe, direct-control firing in environments with high RF interference or when the user's mobile device fails. It also serves as a safe mode for testing connections, where only one channel can be armed and fired at a time.
```
stateDiagram-v2
    state "Manual Mode (Low Power)" as Manual {
        [*] --> Idle
        Idle --> Armed: Press_Arm_Button_N
        Armed --> Firing: Press_Fire_Button_N
        Firing --> Idle: Fired
        note right of Armed
            Only one channel (N)
            can be armed at a time.
        end note
    }
    state "Auto Mode (Full Function)" as Auto {
        [*] --> Connected
        Connected --> ExecutingShow: Start_Show_Command
        ExecutingShow --> Connected: Show_Complete
        ExecutingShow --> Connected: Emergency_Stop
    }
    [*] --> Manual: Switch_Position_Manual
    Manual --> Auto: Switch_Position_Auto
    Auto --> Manual: Switch_Position_Manual
```

5.3. Capacitive Discharge Ignition with Pre-Flight Check

Enabling Description: The power delivery system for the igniters is redesigned to use a capacitive discharge system. Instead of directly connecting the battery to the heating element (64), a command from the controller (28) first charges a high-capacity capacitor for a specific igniter channel. A "Ready to Fire" signal is sent back to the mobile app only after the capacitor reaches its target voltage. The actual "Fire" command then triggers a high-current SCR (Silicon-Controlled Rectifier) to dump the capacitor's charge through the igniter, providing a rapid, powerful, and controlled energy pulse. This method provides a safety check (the pre-charge sequence) and ensures consistent energy delivery for reliable ignition, even with a low or aging battery. If the capacitor fails to charge within a specified time, the system flags that channel as faulty and will not allow an arming attempt.
```
sequenceDiagram
    MobileApp->>FiringModule: ARM Channel 3
    FiringModule->>Capacitor3: Begin Charging
    activate FiringModule
    loop Charge Monitoring
        FiringModule->>Capacitor3: Check Voltage
        Capacitor3-->>FiringModule: Voltage_Level
    end
    FiringModule->>MobileApp: Channel 3 ARMED
    MobileApp->>FiringModule: FIRE Channel 3
    FiringModule->>SCR3: Trigger Gate
    SCR3->>Igniter3: Discharge Capacitor
    deactivate FiringModule
```

6. Combination Prior Art Scenarios

6.1. Integration with MQTT for IoT-Based Firework Displays

Enabling Description: The firing module (4) is designed to act as an MQTT (Message Queuing Telemetry Transport) client. Instead of a direct Bluetooth connection, it connects to a local Wi-Fi network and subscribes to a specific MQTT topic on a broker (server). The mobile application (100) acts as an MQTT publisher. This allows a single user, or multiple authorized users, to control a vast network of firing modules from anywhere with internet access. The MQTT protocol, being a lightweight publish/subscribe standard, is ideal for sending low-latency firing commands to hundreds of devices simultaneously, enabling large-scale, geographically distributed, and collaborative pyrotechnic displays. The iot.eclipse.org or a self-hosted Mosquitto broker could be used.

6.2. Control via Robot Operating System (ROS)

Enabling Description: A ROS node is developed to interface with the firing module (4). The '037 patent's firing module is treated as a hardware peripheral. The ROS node exposes services such as /fire_channel, /get_status, and /arm_system. This allows the pyrotechnic system to be integrated into larger robotic systems. For instance, a mobile robot equipped with a firing module could be programmed to navigate to a specific GPS coordinate and then execute a pyrotechnic sequence, all orchestrated within the ROS framework. This enables applications in robotics research, automated film production special effects, and unmanned systems.

6.3. Standardized Pyrotechnic Show Description using an XML Schema (PyroML)

Enabling Description: The custom show design format within the mobile application (100) is replaced with an open, standardized XML-based format, "PyroML." This standard defines tags for firework types (<firework>), timing information relative to an audio track (<cue time="12.34s">), firing module addresses (<module id="A1">), and safety parameters. The mobile application becomes a graphical editor and player for PyroML files. This allows professional choreographers to use sophisticated third-party software to design shows and export them as a .pml file, which can then be loaded and executed by any '037-compliant system, promoting interoperability between different hardware manufacturers who adopt the open standard.