Fire activation module for an automatic fire extinguishing system

ES 2 633 962 T3

DESCRIPTION

Cable harness for an automatic fire suppression system

This description refers to a fire extinguishing system.

Fire suppression systems often have multiple zones, spanning numerous suppression areas. Each zone typically includes one or more detectors, suppressors, and triggering devices.

Typically, fire suppression systems are centralized and use a common controller to activate suppressors in the various zones, making operation in each zone dependent on the controller. That is, a detector sends a detection signal to the controller, which determines whether or not to activate the suppressors in a given area. Controllers are specific to the number and configuration of zones and can be quite large.

The number and size of cables in the system affect the packaging and weight of the system. Assuming at least three to four wires per detector and / or suppressor are desired, a system using a combination of fifteen detectors and suppressors, for example, might require up to sixty cables connected directly to the same controller, not including the cables that would be desirable. for any auxiliary component. A fully redundant system would require twice as many cables. Also, two wires to each suppressor, for example, are typically power wires that are sized to provide sufficient current to a drive device. These power cables can be stretched over long distances, contributing significantly to the weight of the system, which is especially undesirable for mobile applications, such as an aircraft.

SUMMARY

According to the invention, there is provided a fire extinguishing system comprising: a wire harness for a fire extinguishing system comprising: a connector having a pair of power cables and a pair of control cables; and at least one zone identification element incorporated in the harness in communication with the connector and configured to provide a zone location assignment to the connector; a component connected to the connector, wherein the component comprises a microprocessor configured to interpret the zone location assignment and establish a zone location in response thereto; and a controller connected to the wire harness and configured to receive the zone location from the component.

BRIEF DESCRIPTION OF THE DRAWINGS

The description may be further understood with reference to the following detailed description, taken in connection with the accompanying drawings, in which:

Figure 1A is a schematic view of an exemplary automatic fire suppression system with an integrated data bus.

Figure 1B is a schematic view of a suppressor and a suppressor source.

Figure 2 is a schematic view of an exemplary fire activation module.

Figure 3 is a schematic view of a connector and a microprocessor.

Figure 4 is a schematic view of a controller with a removable network configuration device.

DETAILED DESCRIPTION

An automatic fire suppression system 10 with a highly integrated data bus (HIDB (Highly Integrated Data Bus) system or system) (see Figure 1A) is configured to automatically perform fire detection and fire suppression functions as well as blast detection and blast suppression for fixed structures (buildings, warehouses, etc.), in asphalt, off-road, military, commercial, and rail-guided vehicles, as well as air and marine vehicles. The HIDB system 10 includes a single zone, or multiple separate zones (eg, zones 14, 16, 18, 20) in a data bus network. A zone is defined as a specific suppression zone 29 (see Figure 1B) to be protected. For example, an engine compartment, an auxiliary power unit compartment, a passenger compartment, cargo or storage areas, spare wheel and tire areas, areas outside the vehicle, crew or passenger exit doors , warehouse or manufacturing areas, etc. There is no practical limit to the number of zones or the number of components connected to the 10 HIDB system.

ES 2 633 962 T3

Referring to Figure 1A, the 10 HIDB system allows for rapid detection of explosion events with short reaction times in order to suppress the explosion before it has a chance to mature (typically, response times are within the range). interval between 6 and 10 ms for detection and initiation of suppressor activation), and / or detection and extinguishing of fires, which can have response times measured in seconds. Information is transmitted to a first data bus 22 to and from a controller 12 and components within zones 14, 16, 18, 20, for example. A second data bus 24 can be used to provide redundancy. Each data bus 22, 24 includes command cables 42 and power cables 44, best seen in Figure 2.

In the example, each zone includes at least a detector 26, a suppressor 28, and a Fire Extinguishing Activation Module (FAM) 30, which may be separate or integrated in a variety of configurations. The FAMs 30 activate the suppressors 28, which are connected to a suppression source 27, to selectively disperse suppressor in the suppression zone, as illustrated in Figure 1B. The data buses 22, 24 are directly connected and are common to the detectors 26, the suppressors 28 and the FAMs 30 of the zones 14, 16, 18, 20.

Controller 12 may contain a single processor or multiple processors, as well as Non-Volatile Random Access Memory (NVRAM) used to store a history of events, faults, and other activities of devices on the bus network. of data. This NVRAM can be used as the source for reports, maintenance actions and other activities.

Controller 12 has the ability to communicate with any device (eg, detectors 26, suppressors 28, FAMs 30) over the data bus network, which is illustrated in Figure 1A. Such communication would be to order a device or devices to perform specific functions and to receive their response information, as well as to receive unsolicited information from any device on the network. Controller 12 monitors all network devices to ensure they are operational, or to disable or reactivate specific devices on the network. The 10 HIDB system is designed to be autonomous with respect to the detection and suppression of fires and explosions. To this end, each detector 26 and FAM 30 includes at least one microprocessor configured to operate independently of the controller 12. The exemplary HIDB system 10, however, provides manual overrides of the system within network zones.

An optional computer data bus communication link 38 coordinates all communications with controller 12, responds to requests, and also transmits unsolicited information to controller 12.

Controller 12 may be programmed to handle a specific network configuration, i.e., for example, a specified number of detectors 26 and suppressors 28 in an engine compartment, a specified number in a crew compartment, cargo compartment, etc. During controller 12 startup, controller 12 would verify that each detector 26, suppressor 28, FAM 30, and auxiliary components (if used), are all in place and functioning properly for each zone. Any malfunctioning or missing component will be reported accordingly.

The controller 12 may have its own control panel built into it (buttons, lights, switches, for example), or it may be a hidden black box somewhere with a remote control panel or optional remote control panels to provide control , or it can have both its own built-in control panel and a remote control panel or remote control panels. Sometimes more than one control panel is desired, as certain crew members may be isolated from the vehicle operators or, in the case of a building, may require multiple control panels for checks or to access the controls. network components.

Data buses 22, 24 minimize the number of cables that are used to directly connect detectors 26, suppressors 28, FAMs 30, and other auxiliary devices or components. The use of a single control area network (CAN, Controller Area Network) or a similar data bus, for example, only requires four cables, which are a pair of control cables (CAN Hi, CAN Low) and a pair of power cables, which manage all the detectors 26, suppressors 28, FAMs 30 and auxiliary components connected to the network. A dual data bus system with a second data bus 24, providing complete redundancy, would only require eight cables in such a configuration.

Control of the data bus is provided by controller 12. In the example, controller 12 is designed to manage two independent and redundant data buses 22, 24. Both data buses 22, 24 send the same information to the network components (detectors 26, suppressors 28 and FAMs 30) and those components send their data to the controller 12 through both data buses 22, 24. A redundant data bus is used when communication to and from network devices is critical. For example, in a combat vehicle redundant routes may be desired if the vehicle suffers damage due to combat. Typically, the data bus wiring would be run through different well-separated paths throughout the vehicle, joining only at

ES 2 633 962 T3 the connector of the particular component. In this way, if a data bus communication link has been disabled, communication is still available through the second data bus. When applications only require one communication path, then a single data bus can be used.

The HIDB system 10 provides detectors 26 for the detection of a suppression event, including fires and explosions, using a number of different detection logic schemes, such as, but not limited to:

1) OR logic (any detector 26 in a zone can initiate a discharge from a fire extinguisher or explosion suppressor, both of which are called a suppressor 28),

2) AND logic that requires that more than one detector 26 in a zone must detect the event before activating a suppressor 28,

3) discrimination between different types of fire and non-fire events.

The HIDB system 10 can use multiple types of detectors 26, such as, but not limited to, optical detectors (typically fire and explosion detection), thermal (thermistor, eutectic, for example, typically used in fire detection), pressure (typically, explosion detection) and other types.

The detector 26 contains a microprocessor 25, which interfaces with the electronic circuit or device that actually determines whether there is a fire or explosion event. This microprocessor 25 can also be the interface to the data buses 22, 24. In addition, the microprocessor 25 can determine if there is a fire or explosion event. Typically, this would be determined by microprocessor 25 calculating the speed, and / or complexity of performing the detection methodology. If detector 26 determines that a suppression event has occurred (fire or explosion, for example), then detector 26 sends a command to the desired suppressors 28 in the area where the event has been detected (and could include contiguous zones depending on the desired system logic) via data buses 22, 24 via a FAM 30, for example.

In one example, each detector 26 has the ability to perform a Built In Test (BIT) of itself to determine if it is working properly. It can perform a BIT periodically, or on a command from controller 12, and report the status to controller 12. A faulty detector 26 can be self-deactivated, or deactivated by controller 12. Deactivation helps to make dynamic changes in AND logic, described below.

If OR logic is being used, upon detection of an event, detector 26 would transmit a message over the data bus ordering all FAMs 30 in the same zone as detector 26 to activate their suppressor 28. However, by design , it could also instruct other suppressors 28 in adjoining areas to activate their suppressors 28 depending on the logic provided by the client.

If AND or discrimination logic is used, the desired number of detectors 26 in each zone will detect the event before a command can be transmitted for the FAMs 30 to activate suppressors 28 in the desired zone or zones. During startup, each detector 26 determines whether it should use AND logic across the data bus, or use discrete 32 wiring, which provides faster AND logic capability. If AND logic is used across the data bus, then each detector 26 in the zone would transmit messages to each of the other detectors 26 in the zone when an event is detected. When the desired number of detectors 26 are detecting the event, then any or all of the detectors 26 in the zone that are detecting the event can command the FAMs 30 to activate the desired suppressors 28. Furthermore, for example, detectors 26 in an area could transmit through that data bus that they have detected an event and the FAM or FAMs 30 located in an area could count the number of detectors 26 within that area that they have detected the fire, and when the required number has been reached, the FAM or FAMs 30 could activate suppressors 28 in that zone and, if necessary, in contiguous zones. This logic could be communicated to the FAM (s) 30 during startup by a Network Configuration Device (NCD) 34, described in more detail below.

Inherent in the logic described above is the ability to dynamically reduce the number of detectors 26 that detect an event so that the FAMs 30 are ordered to activate the suppressors 28. For example, if you want two of the four detectors in a zone detect an event before transmitting a command to the FAMs 30, it can be determined via the single or dual data buses whether, in fact, the other detectors 26 are operational. Some of the detectors 26 could have been disabled by the event and thus logic can be incorporated to order the FAMs 30 to activate the suppressors 28 if all the detectors 26 are not operational within a given zone. Regardless of the dynamically changing logic desired, it can be achieved by having the detectors 26 determine the state of the other detectors 26 within a zone via the single or dual data bus.

ES 2 633 962 T3

Controller 12 will also see any of the above command messages and store this event traffic in its NVRAM. You can also verify that each FAM 30 has performed the commanded action, and that, in fact, each suppressor 28 has been successfully activated by communicating with each FAM 30 in the area. You can also determine which detectors 26 are not working properly.

Because detector 26 contains a microprocessor 25, another option that can be used in detector 26 is to download into its NVRAM the CAGE code, part number, and serial number (for that particular unit) provided at the time of the scan. manufacturing. When a unit is faulty, the controller 12 may issue a message regarding the zone, part number, and serial number of the faulty unit. Because there is typically also a physical nameplate on the detector 26, the part number and serial number on the nameplate will help system maintenance personnel identify the component to be replaced.

If AND logic is used on dedicated discrete cables connecting all the detectors in a zone together (for example, via 32 cables), then the same dynamic changing logic as described above in relation to detectors 26 can be introduced. For example, a tri-voltage signaling scheme is used, but other schemes could also be used. For example, if a detector 26 is operational, it outputs a voltage signal within a given average range (eg, 6-10 volts) on discrete line 32 indicating that it is operational. If the detector 26 detects an event, it would increase the voltage to a higher level, for example 12-16 volts. If the voltage drops below 5 volts (0-5 volts) this is an indication that the detector 26 is not working properly. Therefore, by having each detector 26 discretely observe the output voltages of the other detectors 26 within a zone, you can determine if all detectors 26 are operational, how many detectors 26 may be in alarm, and how many are not operating properly. Therefore, the correct decision can be made using AND logic, and if one or more of the detectors 26 are not working properly, the logic can be dynamically adjusted to command the FAMs 30 to activate their suppressors 28.

With reference to Figure 2, the FAM 30 is a module, which may be an integral part of a suppressor 28, or a separate module, which is located in close proximity to the suppressor 28. The FAM 30 contains a microprocessor 54, interconnected with the electronic circuitry or device, which actually activates the suppressor 28 upon a command from the detectors 26 or a manual discharge command from the controller 12. This microprocessor 54 can also monitor the status of the activation device (such as the continuity of the cables), and / or pressure switches / pressure transducers that inform / indicate about the pressure inside the suppressor 28. This microprocessor 54 it can also be the interface to the data buses 22, 24. The FAM 30 would report any failure associated with the suppressor 28 via the data bus (or buses).

The HIDB system 10 incorporates the use of one or more capacitors 48 in the FAM 30, which, upon command from the microprocessor 54, provide the necessary power to activate a suppressor 28. As a result, smaller power cables 44 can be used with a current capacity that would not be able to satisfy the current draw of the instantaneous actuation of the actuator 46. The power requirements for an actuation device 46, such as a valve or other mechanism, in each suppressor 28 determines the size of the capacitor within the FAM 30. The FAM 30 may be integrated with the suppressor 28 or it may be remote from the same. If suppressor 28 is remote from FAM 30, capacitor 48 can be packaged with suppressor 28 if desired. The capacitors would remain charged through trickle or hold charging with energy transmitted through the power cables 44, thus requiring only a low level power requirement.

During a suppression event, the FAM 30 receives the command from the detector 26. The microprocessor 54, in turn, operates the actuator 46 by applying a voltage from the capacitor 48 through a switching device 49, for example. A sensing element 58 associated with actuator 46 may be monitored by microprocessor 54 to ensure that actuator 46 has been successfully actuated. The sensing element 58 may be a pressure transducer, for example, that detects a drop in suppression pressure as a result of a desired dispensing of the suppressor into the suppression zone 29 (Figure 1B).

Because the FAM 30 is an integral part of the suppressor 28, or is located in the vicinity of the suppressor 28, there is an opportunity to use as little energy as possible to activate the suppressor 28. For example, only 1.0 A could be used to activate a suppressor 28. In this way, due to the close proximity, a robust protection against electromagnetic interference (EMI, Electromagnetic Interference) can be incorporated to eliminate accidental discharges, due to potential causes related to EMI.

Upon command from detectors 26 or controller 12, FAM 30 would release the energy in the capacitors to activate suppressor 28. FAM 30 would also be able to verify that suppressor 28 has been activated by the

ES 2 633 962 T3 resulting low pressure in the suppressor 28 via the pressure switch / transducer, and would be able to report this status to the controller 12. The FAM 30 could also report that the suppressor 28 is faulty as it had been activated and no longer has internal pressure, thus causing a maintenance action by system maintenance personnel.

The FAM 30 has the ability to perform an integrated check (BIT) of itself to determine if it is working properly. It can perform a BIT periodically, or by a command from controller 12, and can report status to controller 12. Faulty FAMs 30 can be self-deactivated, or they can be deactivated by controller 12 to avoid accidental discharges due to that the unit is not working properly.

Because the exemplary FAM 30 contains the 54 microprocessor, another option that can be used in the FAM 30 is to download the CAGE code, part number, and serial number (for that particular unit) provided at the time of delivery to your NVRAM. manufacturing. When a unit is defective, the controller 12 may issue a message indicating the zone, part number, and serial number of the defective unit. Since there will also be a physical nameplate on the FAM 30, the part number and serial number on the nameplate will help system maintenance personnel identify the component to be replaced.

Controller 12 does not command FAMs 30 to activate a suppressor 28 when it is operating in its normal, automatic, and autonomous mode of operation. However, it can initiate a suppressor 28 discharge within a specified zone or zones from the control panel when a person enters the correct command through the controller 12 and / or remote control panel 36. As described above, each detector 26, suppressor 28, FAM 30, and auxiliary component has a defined zone. In this way, for example, if a fire or explosion event is detected in Zone 3, and meets the requirements of the AND / OR logic, the detector or detectors can transmit a message indicating that each FAM 30 in Zone 3 it should activate its suppressor 28. In this way, communication with controller 12 is not necessary to activate suppressor 28. Controller 12 will also see the same broadcast message, and will store this event in its NVRAM. You can also verify that each FAM 30 has performed the commanded action, and that, in fact, each suppressor 28 has been successfully activated by communication with each FAM 30 in the area.

The HIDB system 10 wants each detector 26 and suppressor 28 to operate in a zonal fashion. It is also desirable that all other components also operate in a zonal manner rather than being wired to controller 12. The microprocessor 54 of an exemplary FAM 30 is shown in Figure 3. In this way, the most flexibility and functionality is obtained in the 10 HIDB system. The zone identification is programmed into the network wiring harness mating connectors 50, which includes one or more zone identification elements 52. The zone number programming or zone assignment procedure on the mating connector can take several forms, such as using multiple grounded connector pins that indicate a zone number by a binary counting procedure, or by the use of single or multiple pins with embedded resistors where each resistance value represents a zone. Other zone identification elements can also be used, but are integrated into the mating harness to retain the independence of component configuration. There is no limit to the number of zones or components that can be used in the 10 HIDB system. The microprocessor inside the detector, FAM 30, or auxiliary equipment will interpret the zone number and thus establish its own zone location, and will also transmit it to the controller 12 during startup to verify that it is present on the network and also if it is working properly or is faulty.

Integration of zone identification into the mating harness connector allows all detectors 26, suppressors 28, FAMs 30, and ancillary components to be manufactured and / or programmed to be independent of their end-use location on a network, and allows them to be interchangeable with other vehicles, buildings, networks or areas. There can be multiple connectors within a zone, all with the same zone location assignment.

Returning to Figure 1A, the optional Network Configuration Device (NCD 34) enables the fabrication of a universal controller 12 that is independent of a network configuration. This allows the controller 12 to be used in multiple applications without modification. During controller startup, the controller reads the NCD 34 and determines what the network configuration should be, then verifies that it is correct and working correctly, zone by zone, and component by component. This is easily accomplished as each device has determined its zone during startup, as described above, and can report its device type (detector 26, suppressor 28, FAM 30) and zone identification.

The purpose and function of the NCD 34 is to provide the desired network configuration to the controller 12, thereby allowing the controller 12 to be manufactured independently of the network on which it will be used.

ES 2 633 962 T3

The NCD 34 provides a network map, which is loaded into the NVRAM of the controller 12 during startup, that identifies the configuration of devices on the network, zone by zone, component by component.

The NCD 34 can support dual or single data bus interfaces and would typically be located separate from the controller 12 as a component. However, the NCD 34 can be connected directly to the controller 12, as illustrated in Figure 4. In this way, if it is necessary to add, remove or change components in a network, the only change desired would be to change the network map. of NCD 34 instead of reprogramming controller 12. Therefore, once the physical changes to the components on the network have been made, and the NCD 34 updated, the controller 12 is ready for full operation at the next boot.

Typical items loaded into the NVRAM of the NCD 34 would be, but not limited to:

1. Use of dual or single data bus

two. Detector part numbers and quantities for each zone

3. FAM part numbers and quantities for each zone

Four. AND logic, OR logic or discrimination logic for each zone

5. Whether discrete fast response wiring is used for AND logic or discrimination logic for each zone (ideal for fast response times), or whether AND or data bus discrimination logic will be performed via bus communication of data for each zone

6. The FAM in specific zones counts the number of detectors in alarm and activates the suppressors

7. Remote control panels, and type for each zone

8. Battery Back-Up Units (BBUs) per zone

9. Manual discharge zones

10. Vehicle data bus interface

eleven. Activation of suppressors adjacent to the zone in which a fire event has been detected

A backup power source or BBU 40 (Figure 1A) can be provided when main power 11 is lost. Such examples are combat vehicles whose main battery may have been disabled during an event, or a manufacturing plant that needs to protect critical areas during a power outage. BBUs 40 are generally sized to provide power for detection and activation of the suppressors for a specified period of time. These times depend on the application. If desired, multiple smaller BBU 40s could be used to avoid the use of a single larger BBU 40. In one example, the BBU 40 contains a microprocessor that interfaces with the electronic charging and voltage monitoring circuitry within the BBU 40. This microprocessor may also be the interface for the dual or single data bus.

The BBU 40 has the ability to perform a built-in check (BIT) of itself to determine if it is working properly or if the batteries are in a degraded or discharged mode. It can perform a BIT periodically, or on a command from controller 12, and it can report status to controller 12. The faulty BBU 40 can be self-deactivated, or it can be deactivated by controller 12.

In some cases, there may not be space to house a controller 12 in a vehicle instrument panel or other types of panels, so the controller 12 is located away from the panel and a small, interacting control panel 36 is used. with controller 12. Controller 12 may have its own control panel built into the housing, and other control panels on the network may also control the system.

The control panel 36 can take many forms, with pushbuttons, switches, touch screen controls, and / or many types of visual indicators, etc. Multiple control panels may be desired, depending on vehicle configurations, or facility layouts. Some panels may be restricted to perform only testing functions, while others may have full control of the system.

Regardless of its configuration, style, or functionality, the control panel contains a microprocessor that interacts with the electronic circuitry within the panel. This microprocessor can also be the interface to the dual or individual data buses. All control panel communications would be via the dual or single data bus interface.

ES 2 633 962 T3

The control panel would have the ability to perform a built-in check (BIT) of itself to determine if it is working properly. You can perform a BIT periodically, or on command from controller 12, and report status to controller 12. Faulty control panels can be auto-disabled, or they can be disabled by controller 12.

Primary power 11 and return would be provided to controller 12, and if used, the BBU or BBUs 40. Controller 12 provides power to all components on the network except for the BBU 40, if used. In this manner, controller 12 can provide all boot sequencing for verification of network and zone configurations. If a BBU 40 is used, communication would first be done with the BBU 40 before doing other network configuration checks.

In many applications, vehicles and buildings use centralized computers to monitor the overall condition of a facility or vehicle. Controller 12 can support this interface, providing operational status, event or fault status, accepting requests from, and providing responses to, the central computer. This interface can be implemented through multiple different database protocols, and it can differ from the database format used to control network components.

Although an exemplary embodiment has been described, one of ordinary skill in this art would recognize that certain modifications would be included within the scope of the claims.