WO2011041001A1 - Procédé et système pour corréler des évènements de tir d'arme à des évènements de marquage de points - Google Patents

Procédé et système pour corréler des évènements de tir d'arme à des évènements de marquage de points Download PDF

Info

Publication number
WO2011041001A1
WO2011041001A1 PCT/US2010/039044 US2010039044W WO2011041001A1 WO 2011041001 A1 WO2011041001 A1 WO 2011041001A1 US 2010039044 W US2010039044 W US 2010039044W WO 2011041001 A1 WO2011041001 A1 WO 2011041001A1
Authority
WO
WIPO (PCT)
Prior art keywords
scoring
event
weapon
time
weapon firing
Prior art date
Application number
PCT/US2010/039044
Other languages
English (en)
Inventor
Niall B. Mcnelis
Original Assignee
Aai Corporation
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from US12/487,539 external-priority patent/US8706440B2/en
Priority claimed from US12/487,545 external-priority patent/US8275571B2/en
Priority claimed from US12/487,542 external-priority patent/US8234070B2/en
Application filed by Aai Corporation filed Critical Aai Corporation
Publication of WO2011041001A1 publication Critical patent/WO2011041001A1/fr

Links

Classifications

    • F—MECHANICAL ENGINEERING; LIGHTING; HEATING; WEAPONS; BLASTING
    • F41—WEAPONS
    • F41A—FUNCTIONAL FEATURES OR DETAILS COMMON TO BOTH SMALLARMS AND ORDNANCE, e.g. CANNONS; MOUNTINGS FOR SMALLARMS OR ORDNANCE
    • F41A33/00—Adaptations for training; Gun simulators
    • G—PHYSICS
    • G09—EDUCATION; CRYPTOGRAPHY; DISPLAY; ADVERTISING; SEALS
    • G09B—EDUCATIONAL OR DEMONSTRATION APPLIANCES; APPLIANCES FOR TEACHING, OR COMMUNICATING WITH, THE BLIND, DEAF OR MUTE; MODELS; PLANETARIA; GLOBES; MAPS; DIAGRAMS
    • G09B9/00—Simulators for teaching or training purposes
    • G09B9/003—Simulators for teaching or training purposes for military purposes and tactics

Definitions

  • each bullet fired must be correlated with the impact point of that bullet. This requires that each bullet fired be linked to the weapon that fired it, and that the time and location of the firing be known. Marking bullets, for example, through coloration, may allow bullets to be linked back to the respective weapons of the bullets, but provides no information as to where and when the bullet was fired. Bullets may also be lost, especially if the bullets miss the bullets' target, or if the bullets are destroyed, if the bullets hit a target.
  • An exemplary embodiment of the present invention sets forth an apparatus for registering a scoring event.
  • the apparatus includes a scoring area; a sensor, positioned in proximity to said scoring area, adapted to detect the occurrence of a scoring event caused by the presence of a projectile in said scoring area and to determine a trajectory of the projectile; a time tracking device adapted to keep track of time; a location detection device adapted to identify a location of the apparatus; a reference detection device adapted to identify a reference direction; and a controller, coupled to said sensor, said time tracking device, said location detection device, and said reference direction detection device, adapted to determine, based on said
  • the senor is adapted to transmit the occurrence of the scoring event caused by a projectile and the trajectory of the projectile to the controller; the time tracking device transmits the time to the controller; the location detection device transmits the location to the controller; and the reference direction detection device transmits the reference direction to the controller.
  • the apparatus may further include a lifter coupled to the target and adapted to move the target between a scoring and non-scoring position.
  • the time tracking device, the location detection device, and the true north device are placed within a single housing.
  • the time tracking device, the location detection device, and the reference direction detection device comprise a global positioning system (GPS) receiver.
  • GPS global positioning system
  • the location detection device comprises a global positioning system (GPS) receiver and the time tracking device comprises an internal clock synchronized by the GPS receiver.
  • GPS global positioning system
  • the apparatus may further include a velocity sensing device adapted to record a velocity of the projectile upon impact with the target.
  • An exemplary embodiment of the present invention sets forth a method for registering a scoring event.
  • the method includes determining that a scoring event, caused by a projectile, has occurred in the vicinity of a target; determining a position of said target when said scoring event occurred; determining a time at which said scoring event occurred; determining an orientation of the scoring area, with respect to a reference direction when said scoring event occurred; determining an angle of incidence of the projectile when the scoring event occurred based on said orientation of said scoring area; and recording said time at which said scoring event occurred and said angle of incidence of the projectile in a memory.
  • the method may further include determining a velocity of the projectile.
  • An exemplary embodiment of the present invention sets forth an apparatus for registering time and location of a weapon firing of a weapon.
  • the apparatus includes a microcontroller, a pressure sensor located in proximately to the weapon and adapted to determine pressure data based on air pressure in proximity to the weapon and provide the pressure data to a microcontroller, an accelerometer located in proximity to the weapon and adapted to determine acceleration data based on movement of the weapon and provide the acceleration data to the microcontroller; a time device adapted to keep time and provide the time to the microcontroller; a location sensor located in proximity to the weapon and adapted to determine a location of the weapon and provide the location of the weapon to the microcontroller; and a memory coupled to the microcontroller.
  • the microcontroller is adapted to determine if a weapon firing has occurred based on the acceleration data and the pressure data.
  • the microcontroller is adapted to retrieve and then transmit the acceleration data, the pressure data, the time, and the location of the weapon when the weapon firing occurred for storage in the memory.
  • the time device and the location device are combined into a combined device.
  • the apparatus may further include a momentary switch coupled to the microcontroller and adapted allow a user to communicate at least one of the pressure sensor, the accelerometer, the time device, the location device, and the microcontroller.
  • the apparatus may further include a momentary switch coupled to at least one of the pressure sensor, the accelerometer, the time device, and the location device and adapted to turn at least one of the pressure sensor, the accelerometer, the time device, the location device, and the microcontroller on and off.
  • the apparatus may further include an input/output (I/O) data port.
  • the data port is coupled to the microcontroller.
  • the I/O data port comprises at least one of a wireless interface or a wired interface.
  • the microcontroller comprises digital signal processing (DSP) capabilities.
  • DSP digital signal processing
  • the apparatus may further include a power
  • the power supply comprises at least of: a battery; a rechargeable battery; a non-rechargeable battery; a fuel cell; or a hydrogen fuel cell.
  • the apparatus may further include a signal conditioning unit coupled to at least one of the pressure sensor or the accelerometer and adapted to condition the pressure data and the acceleration data before the pressure data and the acceleration data is provided to the microcontroller.
  • a signal conditioning unit coupled to at least one of the pressure sensor or the accelerometer and adapted to condition the pressure data and the acceleration data before the pressure data and the acceleration data is provided to the microcontroller.
  • the apparatus stores a weapon firing signature.
  • the microcontroller determines if a weapon firing has occurred by comparing the acceleration data and the pressure data to the weapon firing signature.
  • the apparatus may further include a transceiver for transmitting the acceleration data, the pressure data, the time, and the location of the weapon when the weapon firing occurred for storage in the memory.
  • the transceiver comprises at least one of a wired interface, a wireless interface, RS-232 interface, a wired USB port, a firewire port, an eSATA port, and/or a proprietary port, or a wireless USB device, Bluetooth device, or IEEE 802.1 lx standard wi-fi connection, and IEEE 802.16x wimax connection.
  • the present invention sets forth a method for registering time and location of weapon firings of a weapon.
  • the method includes determining pressure data based on air pressure in proximity to the weapon; determining acceleration data based on movement of the weapon; analyzing the pressure data and the acceleration data to determine if a weapon firing has occurred; and if the weapon firing has occurred: determining a time of the weapon firing; determining a location of the weapon firing; and storing the pressure data, the acceleration data, the time, and the location in a memory.
  • the method may further include transmitting the pressure data, the acceleration data, the time, and the location to a device for storage.
  • the analyzing step further comprises comparing the acceleration data and the pressure data to a weapon firing signature to determine if a weapon firing has occurred.
  • the present invention sets forth a method for registering time and location of weapon firings of a weapon.
  • the method includes receiving
  • the method may further include transmitting the pressure data, the acceleration data, the time, and the location to a device for storage.
  • the analyzing step further comprises comparing the acceleration data and the pressure data to a weapon firing signature to determine if a weapon firing has occurred.
  • the present invention sets forth a method for correlating at least one weapon firing event to at least one scoring event.
  • the method comprising: (a) receiving, for a first scoring event, a time at which the first scoring event occurred, a location where the scoring event occurred, a direction of a reference direction, and an angle of incidence for a projectile associated with the scoring event with respect to the reference direction at a first computing device; (b) receiving, for a first weapon firing event, a time at which the first weapon firing event occurred, and a location where the first weapon firing event occurred at the first computing device; (c) calculating an angle between a reference line, extending from location of the first weapon event to the location of the first scoring event, and the reference direction at the first computing device; (d) comparing the time of the first scoring event to the time of the weapon firing event at the first computing device; (e) comparing the angle of incidence for the projectile to the calculated angle at the first computing device; and (f) identifying, based on the (d.) and
  • the method may further include calculating a time-of-flight window for a projectile associated with the first weapon firing event; adding the calculated time-of-flight window to the time of the first weapon firing; and step (d) may further include comparing the time of the first scoring event to the time of the weapon firing event at the first computing device.
  • the time at which each scoring event occurred and the time at which each weapon firing event occurred are determined in relation to a
  • the present invention sets forth a method for correlating weapon firing events to target scoring events.
  • the method includes (a) receiving, for a plurality of scoring events, a time at which each scoring event occurred, a location of each scoring area when each scoring event occurred, a direction of a reference direction, and an angle of incidence for each projectile associate with each scoring event with respect to the reference direction at a first computing device; (b) receiving, for a plurality of weapon firing events, a time at which the each weapon firing event occurred, and a location where each weapon firing events occurred at the first computing device; (c) creating a plurality of reference lines for each scoring event and each weapon firing event combination, wherein each reference line extends from the location of each weapon firing event to the location of each scoring event; (d) calculating a plurality of angles between the plurality of reference lines and the reference direction at the first computing device; (e) comparing the time of each scoring event to the time of each weapon firing event at the first computing device; (f) comparing the angle of
  • the method may further comprise (i) removing each unambiguous, one-to-one pairing identified in (g) from further consideration; (j) comparing the time of each remaining scoring event to the time of each remaining weapon firing event at the first computing device; (k) comparing the angle of incidence of the projectile of each remaining scoring event to each of the calculated angles at the first computing device; and (1) identifying, based on the (j.) and (k.), unambiguous, one-to-one pairings between scoring events and weapon firing events, at the first computing device.
  • (c) may further comprise calculating a time-of- flight window for a projectile associated with each weapon firing event; adding each calculated time-of-flight window to the time of each weapon firing.
  • (d) further comprises: comparing the time of each scoring event to the time of each weapon firing event at the first computing device.
  • An exemplary embodiment of the present invention sets forth a system for correlating weapon firing events to target scoring events comprising: a computing device; a target device for detecting a plurality of scoring events and, for each detected scoring event, determining a time at which each scoring event occurred, a location of each scoring area when each scoring event occurred, a direction of a reference direction, an angle of incidence for each projectile associate with each scoring event with respect to the reference direction, and outputting said determinations to a computing device; and a weapon device for detecting a plurality of weapon firing events and, for each detected weapon firing events, determining a time at which the each weapon firing event occurred, a location where each weapon firing events occurred at the first computing device, and outputting said determinations to the computing device, wherein said computing device: creates a plurality of reference lines for each scoring event and each weapon firing event combination, wherein each reference line extends from the location of each weapon firing event to the location of each scoring event; calculates a plurality of angles between the plurality of reference lines and the reference
  • FIG. 1 depicts a block diagram for an exemplary target scoring apparatus (TSA).
  • TSA target scoring apparatus
  • FIG. 2 depicts a block diagram for an exemplary scoring area, lifter, and sensor.
  • FIGS. 3A and 3B depict an exemplary front view and top view of an exemplary target scoring apparatus, respectively.
  • FIG. 4 depicts an exemplary flowchart for the operation of an exemplary TSA to determine the trajectory of a projectile which caused a scoring event.
  • FIG. 5 depicts a block diagram for an exemplary target interface unit (TIU).
  • TIU target interface unit
  • FIG. 6 depicts diagram 600 illustrating an exemplary computer system.
  • FIG. 7 depicts a block diagram for an exemplary TSA.
  • FIG. 8 depicts an exemplary flowchart for an exemplary operation of an exemplary TSA.
  • FIGS. 9 A and 9B depict an exemplary front view and top view of an exemplary target scoring apparatus, respectively.
  • FIG. 10 depicts an exemplary flowchart for the operation of an exemplary TSA.
  • FIG. 1 1 depicts an exemplary block diagram for an apparatus for registering the time and location of weapon firings.
  • FIGS. 12A-B depict an exemplary apparatus for registering the time and location of weapon firings.
  • FIGS. 13A-C depict an exemplary apparatus for registering the time and location of weapon firings mounted on an exemplary weapon.
  • FIGS. 14A and 4B depict exemplary graphs for sensor output during a single exemplary weapon firing of an exemplary weapon.
  • FIGS. 15A and 5B depict exemplary graphs for sensor output during a two round burst from an exemplary weapon firing of an exemplary weapon.
  • FIG. 16 depicts an exemplary flowchart for the operation of an apparatus for registering the time and location of weapon firings.
  • FIG. 17 depicts diagram 1700 illustrating an exemplary computer system.
  • FIG. 18 depicts an exemplary system for use with an exemplary method of correlating weapon firing events, from multiple weapons, with scoring events.
  • FIG. 19 depicts an exemplary flowchart for an exemplary method of correlating weapon firing events, from multiple weapons, with scoring events.
  • FIG. 20 depicts an exemplary method for correlating unambiguous one-to-one pairings among scoring events and weapon firing events.
  • FIGS. 21 A and 2 IB depict an exemplary process by which a position-calculated angle may be determined.
  • FIG. 22 depicts an exemplary method for correlating unambiguous, one-to-one pairings among remaining scoring events and weapon firing events from individual weapons.
  • FIG. 23 illustrates an exemplary method for correlating weapon firing events, from multiple weapons, with scoring events.
  • FIG. 24 depicts diagram 2400 illustrating an exemplary computer system.
  • FIG. 1 depicts a block diagram for an exemplary target scoring apparatus (TSA) 100.
  • TSA target scoring apparatus
  • the exemplary TSA 100 may include, for example, but is not limited to, a scoring area 101, a lifter 104, a sensor 106, a target interface unit (TIU) 108, and a computer 110. While the scoring area 101, lifter 104, sensor 106, (TIU) 108, and computer 110 are described separately below, they may be combined into one or more combined devices according to an exemplary embodiment. Furthermore, in an exemplary embodiment, the components of the TSA 100 may include hardware, firmware, software, or any combination of hardware, firmware and software.
  • the scoring area 101 may include, for example, but not limited to, a target 102 and suppression zone 103. According to an exemplary embodiment, the scoring area 101 may include at least two dimensions. An exemplary target 102 and an exemplary suppression zone 103 are described further below with reference to FIGS. 3A, 3B, 9A, and 9B. In an exemplary embodiment, the scoring area 101 may be coupled to lifter 104.
  • the target 102 may be, for example, an object within the scoring area 101 at which a projectile may be fired.
  • the target 102 may include one or more hit areas and/or miss areas.
  • the target 102 may be a two dimensional target (such as, e.g., but not limited to a circular target or a silhouette target), and/or a three dimensional target (such as, e.g., but not limited to a replica of a person or animal).
  • the scoring area 101 may also include more than one target 102.
  • the suppression zone 103 may refer to a zone surrounding the target 102 when the target 102 is in an exposed position and/or an area adjacent to the target 102 when the target 102 is in an unexposed position.
  • the suppression zone 103 may represent an area in which projectiles may be intended to suppress the target 102, and may not necessarily be intended to impact the target 102.
  • the lifter 104 may be coupled electrically, wired, wirelessly, physically and/or mechanically, including via a communications link (directly, or indirectly) to the scoring area 101, the target 102, the sensor 106, the TIU 108, and/or the computer 110.
  • the lifter 104 may be coupled to a target 102 in order to position the scoring target 102 in an exposed position (in which, for example, the target 102 may be exposed to incoming projectiles) (not shown) and/or move the target 102 between an exposed position and a non-exposed position (in which, for example, incoming projectiles are unable to impact the surface of the target 102) (not shown).
  • the lifter 104 may move the target 102 between an exposed and an unexposed position by, for example, but not limited to, moving the target 102 to/from a raised position, by moving the target 102 vertically, moving the target 102 horizontally, and/or rotating the target 102.
  • the lifter 104 may be combined with one or more of the scoring area 101, target 102, the sensor 106, the TIU 108, and/or the computer 110.
  • one or more sensors 106 may be electrically, wirelessly, mechanically and/or physically (directly or indirectly) coupled to the scoring area 101, the target 102, lifter 104, the TIU 108, and/or the computer 110.
  • the sensor 106 may also be electrically, wirelessly, mechanically, and/or physically coupled to the TIU 108, and/or the computer 110 and located within a proximity to the scoring area 101, the target 102, and/or the lifter 104.
  • the sensor 106 may be located within several inches to several feet from the scoring area 101, the target 102, and lifter 104.
  • the senor 106 may be located within a proximity to the scoring area 101, the target 102, and/or the lifter 104 but may not necessarily be electrically, wirelessly, mechanically, and/or physically coupled to the TIU 108, and/or the computer 110.
  • the sensor 106 may be located within several inches to several feet from the scoring area 101, the target 102, and lifter 104.
  • An exemplary sensor 106 which may be physically coupled to the scoring area 101, the target 102 and/or the lifter 104 may include a contact sensor.
  • a contact sensor may detect scoring events by sensing vibrations of the target 102 and suppression zone 103 caused by the impact of projectiles.
  • An exemplary sensor 106 which may be located within a proximity to the scoring area 101, the target 102 and/or the lifter 104 may include a non-contact hit sensor.
  • a non-contact hit sensor may detect the presence of projectiles in the scoring area 101 by, for example, recording and interpreting acoustical information.
  • the non-contact hit sensor may also be electrically, wirelessly, and/or physically coupled two the scoring area 101, the target 102 and/or the lifter 104
  • the sensor 106 may communicate with (via, e.g., but not limited, a wired and/or wireless communication link) and/or monitor the lifter 104 and/or the target 102, for a scoring event alone or in combination with the TIU108 and/or computer 110.
  • the sensor 106 may be able to detect a scoring event.
  • a scoring event may occur when a projectile passes through the scoring area 101.
  • the sensor 106 may also be able to detect the ambient temperature of the air in proximity to the sensor 106.
  • the sensor 106 may transmit data related to the scoring event to the TIU 108, which may store the data related to the event within the sensor 106, and/or may transmit the data related to the event
  • the sensor 106 may be combined with one or more of the scoring area 101, target 102, lifter 104, the TIU 108, and/or the computer 110.
  • the TIU 108 may be electrically, via a wired link, wirelessly, mechanically and/or physically (directly or indirectly) coupled to the target 102, the lifter 104, the sensor 106, and/or the computer 110.
  • the TIU 108 may monitor and/or communicate with the sensor 106 for data related to scoring events. Once the sensor 106 has determined that a scoring event has occurred, the TIU 108 may request and/or receive data related to the scoring event from the sensor 106 and/or the lifter 104. The TIU 108 may then store the data related to the event internally and/or may transmit the data related to the event to the computer 110.
  • the TIU 108 may be combined with one or more of the scoring area 101, the target 102, lifter 104, the sensor 106, and/or the computer 110.
  • the computer 110 may be electrically or wirelessly coupled to the TIU 108 and/or sensor 106.
  • the computer may be an external computing device capable of sending and/or receiving information with the target 102, the lifter 104, the sensor 106, and/or the TIU 108.
  • An exemplary computer 110 is described further below with reference to FIG. 6.
  • FIG. 2 depicts an exemplary detailed block 200 diagram for an exemplary scoring area
  • Lifter 104 may, for example, include a target port 202, an input power supply port 204, an output power supply port 208, a data input/output port 210, and/or internal power source 212.
  • an exemplary embodiment depicts an internal power source 212, as will be apparent to those skilled in the art, an external power supply 216 may also be used.
  • the target port 202 of the lifter 104 may be connected, coupled, mechanically, physically, electrically (wired or wirelessly), and/or wirelessly, to the target 102.
  • the lifter 104 may be electrically, wirelessly, and/or mechanically coupled to a target 102 in order to position the target 102 in an exposed position (in which, for example, the target 102 is exposed to incoming projectiles) and/or move the target 102 between an exposed position and a non-exposed position (in which, for example, incoming projectiles are unable to impact the surface of the target 102).
  • the lifter 104 may move the target 102 between an exposed and an unexposed position by, for example, but not limited to, moving the target 102
  • Lifter 104 may include one or more electro-mechanical devices such as, e.g., but not limited to, a servo-motor, a lever, an electrical motor, etc. for lifting and/or lowering target 102.
  • Lifter 104 in an exemplary embodiment, include a controller 209, which may include a processor and/or memory (not shown).
  • the input power supply port 204 may be electrically coupled to the internal power source 212, and may enable the internal power source 212 to receive power from an external power supply 216.
  • Power supply 216 may be any suitable power source for providing power to the lifter 104 and/or the TIU 108 and/or TSA 100 as a whole.
  • the power supply 216 may include, e.g., but is not limited to, a power source (such as, e.g., but not limited to a battery, a generator, a fuel cell, or a solar power array) and/or a power management system.
  • the internal power source 212 may be a power source
  • a power management system (such as, e.g., but not limited to, a battery, a generator, a fuel cell, and/or a solar power array) and/or a power management system.
  • the internal power source 212 and/or the external power source 216 may include a battery 262 (not shown), which may be a rechargeable battery, such as, e.g., but not limited to, a lithium-ion battery, nickel metal hydride, and/or nickel cadmium, etc. or a non-rechargeable battery, such as, e.g., but not limited to, lead acid, and/or zinc air, etc., and may be removable or non-removable.
  • the battery may be designed specifically for the apparatus, or may be a more common battery cell type such as an AA battery.
  • the power source 212 may be designed to accept multiple battery types. Power from the battery may be used to run some or all of the electronic elements of the apparatus.
  • the internal power source 212 and/or the external power source 216 may include a power management system.
  • the power management system may include any suitable electronic circuit for managing the use of power by the lifter 104, the sensor 106, and/or the TIU 108.
  • the power management unit may manage the power used from the battery, the recharging of the battery, and/or facilitating the power usage of the lifter 104.
  • the power management system may control the distribution of power to the lifter 104, the sensor 106 and/or the TIU 108 to ensure that the lifter 104, the sensor 106 and
  • the power management system may be disposed within, or may be external to, the lifter 104.
  • the lifter 104 may be physically, mechanically and/or electrically (wired or wirelessly) coupled to the target 102 via target port 202 and/or input/output data port 210.
  • the lifter 104 may be physically, mechanically, electrically, and/or wirelessly coupled to the sensor 106 via input/output data port 210.
  • the lifter 104 may be physically, mechanically, electrically (wired or wirelessly), and/or wirelessly coupled to the TIU 108 via the input/output data port 210.
  • the output power supply port 208 of the lifter 104 may be coupled to the power source 212 and may supply power to the sensor 106 via a power port 226, and/or the TIU 108.
  • the lifter 104 may include one or more output power supply ports 208 such that sensor 106 and the TIU 108 may be powered by the same or separate output power supply ports 208.
  • the data input/output port 210 may, e.g., but not limited to, send/receive data to/from the sensor 106 and/or the TIU 108.
  • the lifter 104 may include one or more data input/output ports 210 such that the sensor 106 and the TIU 108 may send/receive data via the same or separate data input/output ports 210.
  • the one or more input/output power supply ports 208, 210, and 202 may be combined to form one or more combined ports.
  • sensor 106 may, for example, include a controller 220, a target port 222, a data input/output port 224, an input power supply port 226 and/or a memory 228.
  • controller 220 may be any suitable microprocessor, digital signal processor, etc. capable of processing the data received from the scoring area 101, the lifter 104, the TIU 108, and/or the computer 110.
  • the sensor 106 may be physically, electrically, or wirelessly coupled to the scoring area 101 via target port 222 and/or input/output data port 224.
  • the sensor 106 may be physically, electrically, or wirelessly coupled to the lifter 104 via the lifter port 224 and/or input/output data port 224.
  • the sensor 106 may be physically, electrically, or wirelessly coupled to the TIU 108 via the input/output data port 224.
  • the sensor 106 may also be located within a proximity to the scoring area 101 and/or the lifter 104.
  • the sensor 106 may be physically, electrically, or wirelessly coupled to the scoring area 101 via target port 222 and/or input/output data port 224.
  • the sensor 106 may be physically, electrically, or wirelessly coupled to the lifter 104 via the lifter port 224 and/or input/output data port 224.
  • the sensor 106 may be physically, electrically, or wirelessly coupled to the TIU 108 via the input/output data port
  • the sensor 106 may include a controller 220 and a sensor subsystem 232.
  • the sensor 106 may receive power from the internal power source 212 and/or the external power source 216 via the input power supply port 226.
  • the sensor 106 may sense and/or receive data from the scoring area 101 and/or the lifter 104 relating to scoring events which occurred within the scoring area 101.
  • Data may refer to, e.g., but not limited to, electrical/wireless signals and/or vibrations from scoring area 101 as well as acoustical information from scoring area 101 or an area in proximity to the scoring area 101.
  • the sensor 106 may then interpret the sensed and/or received data to record information related to the scoring events.
  • An example of a scoring event which may occur in the scoring area 101 may be the presence of a projectile in an area of the target 102 (which may represent a hit), the presence of a projectile in a non-scoring area of the target 102 (which may represent a miss), and/or the presence of a bullet in the suppression zone 103 (which may represent a suppression shot).
  • the sensor 106 and/or controller 220 may use the gathered information to determine the trajectory of the projectile. The sensor 106 and/or controller 220 may then compare the trajectory of the projectile to several known characteristics of the scoring area 101 to determine whether the projectile caused an exemplary scoring event by striking the target 102 or the suppression zone 103.
  • Known characteristics of the scoring area 101 may refer to, for example, but not limited to, the size and/or shape of the target 102 and/or suppression zone 103, the distance of the scoring area 101 from the sensor 106, and/or the orientation of the scoring area 101 to the sensor 106.
  • the known characteristics of the scoring area 101 may be supplied to sensor 106 by a user, the computer 110, the scoring area 101, and/or the TIU 108.
  • the known characteristics may be stored in memory 228.
  • the orientation of the scoring area 101 may refer to a direction the scoring area 101 faces.
  • the direction the scoring area 101 faces may be dictated by the type of target 102 (for example, a traditional silhouette target may be oriented towards a single direction) or arbitrarily assigned (for example, a three dimensional target may be oriented in more than one direction).
  • the sensor 106 may determine information about the scoring event.
  • the sensor 106 may, e.g., but not limited to, determine, for example, the trajectory of the projectile (i.e. the path of the projectile before, during, and after the projectile passes through the scoring area 101), one or more locations of the projectile while in the scoring area (e.g. accuracy), whether the projectile missed the target 102, and/or the velocity of the projectile upon impact with the target 102.
  • the trajectory of the projectile may be calculated by the TSA 100 in relation to a reference plane perpendicular to the direction of the orientation of the scoring area 101.
  • the reference plane may be defined by the position of the sensor 106 or may be independent of the position of sensor 106. In an exemplary embodiment, the reference plane may also be determined by a user survey. The user may then store the reference plane in memory 228, memory 228, and/or computer 110 for later reference.
  • FIGS. 3A and 3B depicts an exemplary target scoring apparatus 300.
  • FIG. 3A depicts the exemplary target scoring apparatus 300 including scoring area 301, target 302, suppression zone 303 coupled to an exemplary lifter 304, a sensor 306, and a TIU 308, when viewed from the front.
  • sensor 306 may be position in front of the scoring area 301.
  • FIG. 3B depicts the exemplary scoring area 301, the lifter 304, the sensor 306, a path
  • This angle may be referred to as an angle of incidence.
  • FIG. 4 depicts an exemplary flowchart 400 for the operation of an exemplary TSA 300 to determine the trajectory of a projectile which caused a scoring event.
  • Flowchart 400 is described with reference to FIGS. 3A and 3B.
  • Flow diagram 400 may begin with block 410 and proceed directly to block 420.
  • the TSA 300 may identify and/or receive the reference plane 314.
  • the reference plane 3114 In FIG.
  • the reference plane 314 may be perpendicular to the orientation of the scoring area 301.
  • the orientation of the scoring area 301 may refer to the direction the scoring area 301 is facing.
  • the orientation of the scoring area 301 may be parallel to directional arrow A.
  • the process 400 may then proceed to block 430.
  • the TSA 300 may identify and/or receive the path 310 of the projectile as it passed through the scoring area 301.
  • the path 310 may be determined by the sensor 306 and/or the scoring area 301. The process may then proceed to block 440.
  • the TSA 300 may determine the angle 312 created between the path 310 of the projectile and the reference plane 314 by comparing the reference plane 314 to the path 310.
  • the angle 312 may be determined to be 120 degrees from the reference plane 314.
  • the process 400 may then proceed to block 450.
  • the process 400 may end.
  • sensor 106 may include a non-contact acoustic sensor subsystem 232.
  • An exemplary acoustic sensor subsystem 232 may include the models 2F2S or the 2F3S Enhanced TDCue Non Contract Hit Sensor manufactured by AAI Corporation of Hunt Valley, MD USA.
  • FIG. 5 depicts a block diagram 500 for an exemplary TIU 108 of an exemplary TSA
  • the TIU 108 may, for example, include, but is not limited to, a housing 500, one or more momentary switches 502, one or more status indicators 504, a computer input/output data port 506, a compass 508, an input/output data port 510, a power port 512, global positioning system (GPS) receiver 516, a GPS antenna 518, a controller 520, and/or memory 522.
  • Controller 520 may include any of various well known microcontrollers.
  • the housing 500 may be a housing or case made of any suitable materials, such as, for example, but not limited to, plastic, metal, rubber, and/or composites, in any suitable design.
  • the other elements of the TSA 100 may be disposed on or within the housing 500.
  • the housing 500 may be designed to withstand the stress of repeated use.
  • An exemplary embodiment of the TIU 108 may include a momentary switch 502.
  • the momentary switch 502 may include one or more suitable electro-mechanical switch(s), button(s), and/or other input device(s) disposed on the outside of the housing 500.
  • the momentary switch 502 may be positioned on the housing 500 such that the user of the apparatus may be able to access the momentary switch 500.
  • the momentary switch 502 may be used, e.g., to input data to the controller 520, to allow a user to control the operation of the TIU 108, including, e.g., but not limited to, to allow a user to turn the TIU 108 on/off, and/or to indicate
  • Attorney Docket No.: 13346-286631 various conditions to the controller 520.
  • the user may press the momentary switch 502 to begin recording and/or may transmitting information related to a scoring event.
  • holding the momentary switch 502 down for a specified period of time may signal the TIU 108 to enter a low-power consumption mode, and/or to shut down, etc.
  • An exemplary embodiment of the TIU 108 may include status indicators 504.
  • Status indicators 504 may include one or more lights, light emitting diode (LED) indicators of one or more varying colors, a liquid crystal display (LCD) screen, or any other suitable visual display audio or output device.
  • the status indicators 504 may be a pair of LED indicators disposed on the outside of the housing 500, which may be disposed next to the momentary switch 502.
  • the status indicators 504 may be used to convey information about the status of the TIU 108, and the various elements thereof, to a user of the TIU 108.
  • the status indicators 504 may indicate the condition of a battery (not shown) within the internal power source 212 and/or the external power source 216 such as, e.g., but not limited to, low battery, battery charging, and/or battery charged, attainment, or loss of the GPS signal by the GPS receiver 516, and/or data transfer activity through the data port 512, whether the TIU 108 is on or off, etc.
  • a battery not shown
  • the external power source 216 such as, e.g., but not limited to, low battery, battery charging, and/or battery charged, attainment, or loss of the GPS signal by the GPS receiver 516, and/or data transfer activity through the data port 512, whether the TIU 108 is on or off, etc.
  • the input/output data port 506 may be any, bus, port, suitable port or combination of ports for connecting the TIU 108 to a device, such as, for example, a computing device, to allow the device to access the elements of the apparatus.
  • the data port 506 may be a wired port which may include a physical connection via a cable, wired, or wireless port implemented as wireless device.
  • the data port 506 may be, e.g., but not limited to, a wired universal serial bus (USB) port, a serial port, a parallel port, a bus interface, a universal serial bus (USB), a card bus interface, firewire, a personal computer memory card international association (PCMCIA) interface, an ISA, a PCI, etc., firewire port, eSATA port, or proprietary port, or a wireless USB device, Bluetooth device, or 802.1 lx standard wi-fi device.
  • the data port 506 may allow a connected device access to the status indicators 504, the compass 508, the input/output data port 510, the power port 512, the global positioning system (GPS) receiver 516, the GPS antenna 518, the controller 520, and/or the memory 522 to, for example, allow for the test, repair, and/or calibration of the components of the TIU 108.
  • a connected device such as, for example, but not limited to, computer 110, may, e.g., use the data port 506 to read stored data from the memory 522, and/or write program code
  • the data port 506 is a wired port, the data port 506 may be disposed on the outside or within the housing 500, as depicted in FIG. 5. If the data port 506 is a wireless port, the wireless device used to implement the data port 506 may be disposed within or outside the housing, on or connected to, or coupled to a control board.
  • the compass 508 may be any device for determining a reference direction (such as, but not limited to, true north) relative to the magnetic poles of the earth.
  • the compass 508 may be a digital compass or a magnetic needle compass which has been compensated to identify the reference direction.
  • the compass 508 may also be combined with the GPS receiver 516.
  • the reference direction may be determined by a user survey. The user may then store the reference direction in memory 228, memory 522, and/or computer 1 10 for later reference.
  • the input/output data port 510 may be any suitable port or combination of ports for connecting the apparatus to a device, such as, for example, a lifter 104 via input/output data port 210, to allow the device to access the elements of the TIU 108 and to allow the TIU 108 to access elements of the device.
  • the data port 510 may be a wired port requiring a physical connection via, e.g., but not limited to, a cable, or wireless port implemented as wireless device.
  • the data port 510 may be a wired USB port, firewire port, eSATA port, or proprietary port, and/or a wireless USB device, Bluetooth device, or 802.1 lx standard wi-fi device.
  • the data port 510 may, e.g., allow a connected or coupled device access to the status indicators 504, the compass 508, the input/output data port 510, the power port 512, the Global Positioning System (GPS) receiver 516, the GPS antenna 518, the controller 520, and/or the memory 522 to, for example, allow for the test, repair, and/or calibration of the components of the coupled apparatus.
  • a connected or coupled device may use the data port 506 to read stored data from the memory 522, and to write program code for use by the controller 520 to the memory 522. If the data port 506 is a wired port, the data port 506 may be disposed on the outside of, or within the housing 500, as illustrated in FIG. 5.
  • the wireless device used to implement the data port 506 may be disposed within the housing, on or connected to a control board.
  • the data port 510 when coupled to input/output port 210 of the lifter 104, may also allow the TIU 108 access to the
  • the data input/output port 510 may be coupled to and/or send/receive data from the data input/output port 224 of the sensor 106 and/or the data input/output port 210 of the lifter 104.
  • the power port 512 may be coupled to and receive power from the output power supply port 208 of the lifter 104.
  • the one or more input/output power supply ports 208, 226, 512 may be combined with one or more of the data input/output ports 210, 224, 510 to form one or more combined ports.
  • the GPS receiver 516 may be any suitable device for receiving and interpreting GPS signals to determine the location of the GPS receiver at any particular time.
  • the GPS receiver 516 may be disposed within the housing 500, on a control board or otherwise connected thereto, or attached to the outside of the housing 500.
  • the controller 520 may request time and/or location data from the GPS receiver 516, according to an exemplary embodiment.
  • the GPS receiver 516 may be able to determine a reference direction.
  • the GPS receiver 516 may be positioned in close proximity to the target 102 in order to allow for a precise determination of the location of the target 102. Additionally, the GPS receiver 516 may be sensitive enough to determine location precisely and may be accurate enough to allow for the determination of the positions of two GPS receivers, which may be in close proximity to one another, to be distinguishable.
  • the GPS receiver 516 may be able to determine the location of the target 102 through, e.g., interpolation, extrapolation, etc.
  • the controller 520 may assist the GPS receiver 516 with calculations for performing the interpolation or extrapolation, if necessary. Interpolation may be based on previously determined location determination.
  • the positional accuracy of the GPS receiver 516 may be increased by survey with a differential GPS and/or averaging two or more discrete location determinations over a period of time to arrive at an averaged target 102 location.
  • Attorney Docket No.: 13346-286631 520 may work in conjunction with the GPS receiver 516 to conduct the survey and/or calculate the averaged location.
  • the precise target 102 location may be stored in memory 522.
  • the GPS receiver 516 may be able to determine the location of the target 102 through interpolation.
  • the controller 520 may assist the GPS receiver 516 with the calculation necessary to perform the interpolation, if necessary. Interpolation may be based on previously determined location determination.
  • the GPS receiver 516 may be used to set an internal clock (not shown) of TIU 108.
  • the controller 520 may retrieve time information from a clock when a scoring event occurs.
  • the GPS antenna 518 may be any antenna suitable for use with the GPS receiver 516.
  • the GPS antenna 518 may be disposed on the outside or the inside of the housing 500.
  • the GPS antenna 518 may pick up GPS signals and relay them to the GPS receiver 516.
  • Controller 520 may be any suitable microcontroller, processor, or microprocessor, digital signal processor, etc. capable of processing the data received from the scoring area 101, the sensor 106, the lifter 104, the controller 220, the digital compass 508, the computer 110, and the GPS receiver 516. Data from the scoring area 101, the sensor 106, the lifter 104, the controller 220, the digital compass 508, the computer 110, and/or the GPS receiver 105 may be sent to the controller 520, which may use the data to determine whether a scoring event has occurred.
  • the controller 520 may determine information about the scoring event in cooperation with scoring area 101, the sensor 106, the lifter 104, the controller 220, the digital compass 508, the computer 110, and/or the GPS receiver 105. The controller 520 may then store information about the scoring event in memory 228 and/or memory 522 and/or may transmit the information to computer 1 10.
  • the controller 104 may also receive input from the momentary switch 502, control the status indicators 504, and, if necessary, facilitate the transfer of data from the memory 522 through input/output data port 510.
  • the controller may be disposed within housing 500.
  • Memory 522 may include any computer readable medium, and/or storage device suitable for usage inside the housing 500.
  • the memory 522 may include, random access memory (RAM), read only memory (ROM), volatile or nonvolatile memory, a write once read
  • the controller 520 may read from and write to the memory 522.
  • Program code used by the controller 520 for example, program code for analyzing data from the sensor 106 and the lifter 104 that the controller 520 may use in determining if a scoring event has occurred, may be prewritten to the memory 522.
  • data from the GPS receiver 516 may be written to the memory 522 by the controller 520 on the occurrence of certain events, such as, for example, a scoring event as determined by the controller 520.
  • the memory 522 may be directly accessible by any suitable device connected to, or coupled to, the data port 506, or the controller 520 may be used as an intermediary by such a device.
  • the memory 522 may be disposed within the housing 500, and may be directly disposed on a control board (not shown), or may be disposed elsewhere within the housing 500 and connected to, or coupled to the control board.
  • the memory 522 may be fixed and/or removable. For example, if the memory 522 is, e.g., but not limited to, a Secure Digital flash memory card, the memory 522 may be inserted into the housing 500 through a slot in the housing 500, and may be removable.
  • TIU 108 may, for example, receive and/or detect information relating to a scoring event from the scoring area 101, lifter 104, and/or sensor 106, process the information relating to a scoring event, store information relating to a scoring event and/or may transmit the information to computer 110.
  • the TIU 108 may determine the time of each scoring event, the location of the target 102, the orientation of the target 102, the trajectory of a projectile, which caused a scoring event, with respect to the reference direction, and/or whether the target 102 was in an exposed or non-exposed position at the time of scoring.
  • the TIU 108 may make these determinations by receiving info from the lifter 104, the sensor 106, and/or scoring area 101.
  • the TIU 108 may, e.g., store the information relating to a target 102, locally and/or may transmit the information relating to a scoring event to another computing device (such as, but not limited to, computer 110).
  • FIG. 6 depicts diagram illustrating an exemplary computer system 600 such as may be used in, or in combination with devices 104, 106, 108, 110, 220, 520, etc. and that may be used in implementing an exemplary embodiment of the present invention.
  • FIG. 6 depicts an exemplary embodiment of a computer system 600 that may be used in computing devices such as, e.g., but not limited to, a client and/or a server, etc., according to an exemplary
  • FIG. 6 An example of a computer system 600 is shown in FIG. 6, depicting an exemplary embodiment of a block diagram of an exemplary computer system 600 useful for implementing the present invention. Specifically, FIG.
  • FIG. 6 illustrates an example computer 600, which in an exemplary embodiment may be, e.g., but not limited to, a personal computer (PC) system running an operating system such as, e.g., (but not limited to) MICROSOFT® WINDOWS® NT/98/2000/XP/CE/ME/VISTA/etc. available from MICROSOFT® Corporation of Redmond, WA, U.S.A.
  • an operating system such as, e.g., (but not limited to) MICROSOFT® WINDOWS® NT/98/2000/XP/CE/ME/VISTA/etc.
  • the invention may not be limited to these platforms.
  • the invention may be implemented on any appropriate computer system running any appropriate operating system such as, e.g., but not limited to, an Apple computer executing MAC OS.
  • the present invention may be implemented on a computer system operating as discussed herein.
  • FIG. 6 An exemplary computer system, computer 600 is shown in FIG. 6.
  • Other exemplary computer systems may include additional components, such as, e.g., but not limited to, a computing device, a communications device, mobile phone, a telephony device, an iPhone (available from Apple of Cupertine, CA USA), a 3G wireless device, a wireless device, a telephone, a personal digital assistant (PDA), a personal computer (PC), a handheld device, a portable device, an interactive television device (iTV), a digital video recorder (DVD), client workstations, thin clients, thick clients, fat clients, proxy servers, network communication servers, remote access devices, client computers, server computers, peer-to-peer devices, routers, gateways, web servers, data, media, audio, video, telephony or streaming technology servers, game consoles, content delivery systems, etc., may also be implemented using a computer such as that shown in FIG.
  • services may be provided on demand using, e.g., but not limited to, an interactive television device (iTV), a video on demand system (VOD), via a digital video recorder (DVR), and/or other on demand viewing system.
  • iTV interactive television device
  • VOD video on demand system
  • DVR digital video recorder
  • the computer system 600 may include one or more processors, such as, e.g., but not limited to, processor(s) 604.
  • the processor(s) 604 may be coupled to and/or connected to a
  • Attorney Docket No.: 13346-286631 communication infrastructure 606 (e.g., but not limited to, a communications bus, cross-over bar, or network, etc.).
  • Various exemplary embodiments may be described in terms of this exemplary computer system 600. After reading this description, it may become apparent to a person skilled in the relevant art(s) how to implement the invention using other computer systems and/or architectures.
  • Computer system 600 may include a display interface 631 that may forward, e.g., but not limited to, graphics, text, and other data, etc., from the communication infrastructure 606 (or from a frame buffer, etc., not shown) for display on the display unit 630.
  • a display interface 631 may forward, e.g., but not limited to, graphics, text, and other data, etc., from the communication infrastructure 606 (or from a frame buffer, etc., not shown) for display on the display unit 630.
  • the computer system 600 may also include, e.g., but may not be limited to, a main memory 608, random access memory (RAM), and a secondary memory 610, etc.
  • the secondary memory 610 may include a computer readable medium such as, for example, (but not limited to) a hard disk drive 612 and/or a removable storage drive 614, representing a floppy diskette drive, a magnetic tape drive, an optical disk drive, magneto-optical, a compact disk drive CD-ROM, etc.
  • the removable storage drive 614 may, e.g., but not limited to, read from and/or write to a removable storage unit 618 in a well known manner.
  • Removable storage unit 618 also called a program storage device or a computer program product, may represent, e.g., but not limited to, a floppy disk, magnetic tape, optical disk, compact disk, etc. which may be read from and written to by removable storage drive 614.
  • the removable storage unit 618 may include a computer usable storage medium having stored therein computer software and/or data.
  • a "machine-accessible medium" may refer to any storage device used for storing data accessible by a computer.
  • Examples of a machine-accessible medium may include, e.g., but not limited to: a magnetic hard disk; a floppy disk; an optical disk, like a compact disk read-only memory (CD-ROM), flash memory, nonvolatile memory, or a digital versatile disk (DVD); digital video recorder disk (DVR); a magnetic tape; and a memory chip, etc.
  • a magnetic hard disk e.g., but not limited to: a magnetic hard disk; a floppy disk; an optical disk, like a compact disk read-only memory (CD-ROM), flash memory, nonvolatile memory, or a digital versatile disk (DVD); digital video recorder disk (DVR); a magnetic tape; and a memory chip, etc.
  • secondary memory 610 may include other similar devices for allowing computer programs or other instructions to be loaded into computer system 600.
  • Such devices may include, for example, a removable storage unit 622 and an interface 620. Examples of such may include a program cartridge and cartridge interface (such as, e.g., but not limited to, those found in video game devices), a removable memory chip (such as, e.g., but not limited to, an erasable programmable read only memory (EPROM), or
  • EPROM erasable programmable read only memory
  • Computer 600 may also include an input device such as, e.g., (but not limited to) a mouse 606 or other pointing device such as a digitizer, an audio capture device 628 (such as, e.g., but not limited to, a microphone), an image video/visual capture device 632 (such as, e.g., but not limited to, a camera), and a keyboard 605 and/or other data entry device (not shown), etc.
  • an input device such as, e.g., (but not limited to) a mouse 606 or other pointing device such as a digitizer
  • an audio capture device 628 such as, e.g., but not limited to, a microphone
  • an image video/visual capture device 632 such as, e.g., but not limited to, a camera
  • keyboard 605 and/or other data entry device not shown
  • Computer 600 may also include output devices, such as, e.g., (but not limited to) display
  • Computer 600 may include input/output (I/O) devices such as, e.g., (but not limited to) communications interface 624 and communications path 626, etc. These devices may include, e.g., but not limited to, a network interface card 602, and modem(s) 603. Communications interface 674 may allow software and data to be transferred between computer system 600 and external devices.
  • I/O input/output
  • Communications interface 674 may allow software and data to be transferred between computer system 600 and external devices.
  • computer program medium and “computer readable medium” may be used to generally refer to media such as, e.g., but not limited to removable storage drive 614, a hard disk installed in hard disk drive 612, a storage area network (SAN), database, etc.
  • These computer program products may provide software to computer system 600.
  • the invention may be directed to such computer program products.
  • a computer program product may include software which may be distributed via a communication system and then may be stored on a storage device.
  • FIG. 7 depicts an exemplary TSA 700 comprising the scoring area 101, lifter 104, sensor 106, and/or TIU 108, where sensor 106 and TIU 108 are assembled in an exemplary housing 705, according to one exemplary embodiment.
  • FIG. 8 depicts an exemplary flowchart 800 for the operation of an exemplary TSA 100 and is described with reference to FIGS. 1-3 and 7.
  • Flow diagram 800 may begin with 810.
  • the TIU 108 may begin sending/receiving data to/from the target 102, lifter 104 and/or the sensor 106.
  • the process 800 may then proceed immediately to block 815.
  • the TSA 100 may determine or retrieve, or receive the location of the target 102.
  • the TSA 100 may determine the location of the target 102 via the lifter 104, the
  • the controller 520 may receive the target 102 location from, and/or determine the location of the target 102 in cooperation with, the GPS receiver 516. Once received and/or determined, the controller 520 may store the location information in memory 522 and/or may transmit the information to computer 110 in real-time, or on a delay. In an exemplary embodiment, the controller 520 may average target 102 location information and may determine an averaged target 102 location for a stationary target 102 over a period of time. Once the location is determined in 815, the process 800 may then continue to block 820.
  • the TSA 100 may determine if a scoring event has occurred.
  • the TSA 100 may determine if a scoring event has occurred via the lifter 104, the sensor 106, and/or the TIU 108. Once determined, the scoring event may be stored in memory 522 and/or may be transmitted to computer 110 in real-time and/or on a delay. If a scoring event has occurred, the process may continue to block 825.
  • the senor 106 may receive and/or determine the occurrence of a scoring event via the lifter 104 and relay the scoring event to the controller 520 in, e.g., real-time. Once received and/or determined, the controller 520 may store the scoring event in memory 522 and/or may transmit the occurrence of a scoring event to computer 110 in real-time, or on a delay.
  • the flow 800 may proceed back to block 810 (FIG shows 810).
  • the TSA 100 may determine the time at which the scoring event occurred.
  • the TSA 100 may determine the time at which the scoring event occurred via the lifter 104, the sensor 106, and/or the TIU 108. Once determined, time at which the scoring event occurred may be stored in memory 522 and/or may transmitted the time of the scoring event to computer 1 10 in real-time, or on a delay. The process may then continue to block 830.
  • the controller 520 may receive and/or determine the time at which the scoring event occurred from in cooperation with the GPS receiver 516. Once received and/or determined, the controller 520 may store the time at which the scoring event occurred in memory 522 and/or may transmit the information to computer 110 in real-time or on a delay.
  • the TIU 108 may determine the time via an internal, or other, clock.
  • the internal clock may be synchronized with the GPS receiver 516 at regular or irregular intervals to ensure accuracy.
  • the TSA 100 may determine the position of the target 102 when the scoring event occurred.
  • the TSA 100 may determine whether the target 102 was in an exposed or non-exposed position via target 102, the lifter 104, the sensor 106, and/or the TIU 108. Once determined, the position of the target 102 may be stored in memory 522 and/or may be transmitted to computer 110 in real-time or on a delay. The process may then continue to block 835.
  • the senor 106 may receive and/or determine the position of the target 102 via the lifter 104 and may relay the target 102 position to the controller 520 in real-time, or otherwise. Once received and/or determined, the controller 520 may store the occurrence of a scoring event in memory 522 and/or may transmit information to computer 110 in real-time, or on a delay.
  • the TSA 100 may determine the orientation of the target 102 with respect to a reference direction (for example, true north).
  • the TSA 100 may determine the orientation of the target 102 with respect to the reference direction via the lifter 104, the sensor 106, and/or the TIU 108. Once determined, the orientation of the target 102 with respect to the reference direction may be stored in memory 522 and/or may be transmitted to computer 110 in real-time, or on a delay.
  • the orientation of the target 102 with respect to the reference direction may be determined by comparing the reference direction to the orientation of the target 102.
  • the controller 520 may receive and/or determine the orientation of the target 102 in cooperation with the target 102, the lifter 104, the sensor 106, and/or the GPS receiver 516. Once received and/or determined, the controller 520 may store the orientation of target 102 in memory 522 and/or may transmit the information to computer 110 in real-time or on a delay.
  • the reference direction of true north may be determined by the controller 520, the compass 508 and/or the GPS receiver 516.
  • the compass 508 and/or the GPS receiver 516 may be positioned on, or in close proximity to, the target 102 in order to facilitate such a determination.
  • the controller 520 may store the direction of
  • the orientation of target 102 may also be determined by inputting the results of a survey to controller 520 of TIU 108 and/or the processor 220 of sensor 106.
  • a survey may refer to a measurement of the orientation of a target 102 taken by a user.
  • the TSA 100 may determine the angle between the trajectory of the projectile which caused the scoring event, as is passed through the scoring area 101, and a reference direction.
  • the angle may be determined and/or received by the lifter 104, the sensor 106, and/or the TIU 108. Once determined, the angle may be stored in memory 522 and/or transmitted to computer 110 in real-time or on a delay.
  • the angle between the trajectory of the projectile which caused the scoring event, as is passed through the scoring area 101, with respect to a reference direction may be determined by comparing the a trajectory of the projectile, with respect to the orientation of the scoring area 101, to the reference direction.
  • the controller 520 may receive and/or determine the trajectory of the projectile, with respect to the orientation of the scoring area 101, in addition to the reference direction in cooperation with the target 102, the lifter 104, the sensor 106, and/or the GPS receiver 516.
  • the controller 520 may store the angle between the trajectory of the projectile which caused the scoring event, as is passed through the scoring area 101, with respect to a reference direction in memory 522 and/or may transmit the information to computer 110 in real-time or on a delay.
  • the angle between the trajectory of the projectile which caused the scoring event, as is passed through the scoring area 101, with respect to a reference direction may be determined by the controller 520, the compass 508 and/or the GPS receiver 516.
  • the compass 508 and/or the GPS receiver 516 may be positioned on, or in close proximity to, the target 102 in order to facilitate such a determination.
  • the controller 520 may store the angle between the trajectory of the projectile which caused the scoring event, as is passed through the scoring area 101, with respect to a reference direction in memory 522 and/or may transmit the information to computer 110 in real-time or on a delay. From 840, 800 may continue with 845.
  • TSA 100 may determine the velocity and/or accuracy of the projectile which caused the scoring event may be determined. Once determined, velocity and/or accuracy of the projectile which caused the scoring event may be stored in memory 522 and/or may be transmitted to computer 110 in real-time or on a delay.
  • the velocity and/or accuracy may be determined by the lifter 104, the sensor 106, and/or the TIU 108. Once determined, velocity and/or accuracy of the projectile which caused the scoring event may be stored in memory 522 and/or may be transmitted to computer 110 in real-time or on a delay. From 845, flow diagram 800 may continue with 850.
  • the TSA 100 may save the information determined in blocks 815-845 to memory 522 and/or may transmit the information to computer 110. The process may then continue onto block 855.
  • the TSA 100 may determine whether to continue sending/receiving data to/from the target 102, lifter 104 and/or the sensor 106. If the TSA 100 continues sending/receiving data to/from the target 102, lifter 104 and/or the sensor 106, the process may proceed to block 810. If the TSA 100 discontinues sending/receiving data to/from the target 102, lifter 104 and/or the sensor 106, the process may proceed to block 860.
  • the TSA 100 may wait a short period of time before proceeding back to block 810. Waiting a short period of time may prevent the TSA 100 from erroneously detecting scoring events. Erroneous detections of scoring events may be caused by, for example, reflections of acoustical waves and/or mechanical vibrations.
  • FIGS. 9A and 9B depict an exemplary front view and top view of an exemplary target scoring apparatus 900, respectively.
  • FIG. 9A depicts an exemplary front view of an exemplary scoring area 901, a target 902, a suppression zone 903 attached, connected, and/or coupled, directly or indirectly, to an exemplary lifter 904, a sensor 906, and a TIU 908.
  • sensor 906 may be positioned in front of the scoring area 901.
  • FIG. 9B depicts the exemplary top view of an exemplary scoring area 901, lifter 904, and sensor 906, along with the path 910 of an exemplary projectile as it passes through scoring area 902, a reference plane 914, and a compass rose 916.
  • FIG. 10 depicts an exemplary flowchart 1000 for the operation of an exemplary TSA
  • the trajectory of the projectile may refer to the angle 912 created between the path 910 of the projectile and the reference plane 914 (e.g., the angle of incidence).
  • Flowchart 1000 is described with references to FIGS. 9A and 9B. Flow diagram 1000 may begin with block 1010 and proceed directly to block 1020.
  • the TSA 900 may identify and/or receive the reference plane 914.
  • the reference plane 914 may be perpendicular to the orientation of the scoring area 901.
  • the orientation of the scoring area 901 may refer to the direction the scoring area 901 is facing.
  • the orientation of the scoring, area 901 may be facing West, as indicated by compass rose 916.
  • the process 1000 may then proceed to block 1030.
  • the TSA 900 may identify and/or receive the path 910 of the projectile as it passed through the scoring area 901.
  • the path 910 may be determined by the sensor 906 and/or the scoring area 901. The process may then proceed to block 1040.
  • the TSA 900 may determine the angle 912 created between the path 610 of the projectile and the reference plane 914 by comparing the reference plane 914 to the path 910. In an exemplary embodiment, the angle 912 may be determined to be 120 degrees from the reference plane 614. The process 900 may then proceed to block 1050.
  • the TSA 900 may identify and/or receive the reference direction.
  • the reference direction may be true north.
  • the process 1000 may then proceed to block 1060.
  • the TSA 900 may determine the orientation of the scoring area 901 with respect to the reference direction (i.e. true north).
  • the orientation of the scoring area 901 may be determined by comparing the reference direction (i.e. true north) to the orientation of the target 902.
  • True north denoted by compass rose 916, may be determined the TSA 900 with the assistance of a controller (not shown), a GPS receiver (not shown), and/or a compass 508 (not shown).
  • the orientation of the target 902 with respect to true north may be determined by the TSA 900 with the assistance of a controller (not shown), the target 902, the lifter 904 and/or the sensor 906.
  • the controller (not shown) may
  • Attorney Docket No.: 13346-286631 then compare the two and determine the orientation of the target 902 and/or the scoring area 901 to true north (i.e., the direction the front surface 908 of the target 902 faces with respect to true north).
  • the exemplary target 902 is oriented to the West, or 240 degrees from true north.
  • the process 1000 may then proceed to block 1070.
  • the TSA 900 may determine the angle of incidence, (e.g. between the trajectory of the projectile which caused the scoring event, as is passed through the scoring area 901, with respect to the reference direction).
  • the angle may be determined by comparing the orientation of the target 902 (which may have been previously computed as 240 degrees from true north) to the trajectory of the projectile 912.
  • the trajectory of the projectile 912 when it passed through the scoring area 901 may be determined by the sensor 106 to be 135 degrees.
  • the angle between the trajectory of the projectile which caused the scoring event, as is passed through the scoring area 901, with respect to a reference direction may be computed to be 225 degrees from true north.
  • the process 1000 may then proceed to block 1080.
  • FIG. 11 depicts an exemplary block diagram for an exemplary embodiment of an apparatus 1100 for registering the time and location of a weapon's firings.
  • the exemplary apparatus may include, e.g., but is not necessarily limited to, a pressure sensor 1101, an accelerometer 1102, a signal conditioning unit 1 103, a global positioning system (GPS) a receiver 1105, a GPS antenna 1112, a momentary switch 1110, status indicators 1111, an input/output data port 1109, a memory 1106, a battery 1107, a power management system 1108, and a microcontroller 1104.
  • GPS global positioning system
  • the pressure sensor 1101 and the accelerometer 1102 may each transmit signals to the signal conditioning unit 1103.
  • the signal conditioning unit 1103 may process the signals and transmit the signals to the microcontroller 1104. Signals received by the microcontroller 1104 from the pressure sensor 1101 and the accelerometer 1102 may be used to determine whether a weapon firing has occurred.
  • the GPS antenna 1 112 may be coupled/connected to the GPS receiver 1 105.
  • the GPS receiver 1105 may transmit data to the microcontroller 1104.
  • data pertaining to the weapon firing from the GPS receiver 1105 may be stored in the memory 1106.
  • the GPS receiver 1105 and the GPS antenna 1112 may be replaced by any other device capable of determining the weapon's location.
  • the power management system 1108 may be coupled/connected to, e.g., but not limited to, the battery 1107, and may control the distribution of power to each component of the apparatus 1100 and/or the recharging of the battery 1107.
  • the microcontroller 1104 may store data relating to the weapon firing in memory 1 106 and/or may transmit data relating to the weapon firing via the input/output data port 1109.
  • the data may comprise, e.g., but not limited to, the time of each weapon firing event, the location of each weapon firing event (as determined by the GPS receiver 1105), the waveforms from the pressure sensor 1101, and/or the waveforms from the accelerometer 1102.
  • the microcontroller 1104 may continuously, or at set intervals, store data relating to the location of the weapon (as determined by the GPS receiver 1105) and/or transmit data relating to the location of the weapon firing via input/output data port 1109.
  • the input/output data port 1109 may be used to input data to and/or retrieve data from the apparatus 1100 for registering the time and location of weapon's firings 1100.
  • the input/output data port 1109 may be used to send information relating to the weapon firing from the pressure sensor 1101 and/or the accelerometer 1102 to an external interface.
  • the input/output data port 1109 may also be used to calibrate, program, repair, and/or communicate with the pressure sensor 1101, the accelerometer 1102, the signal conditioning unit 1103, the GPS receiver 1 105, the GPS antenna 1112, the momentary switch 1110, the status indicators 111 1, the memory 1106, the battery 1 107, the power management system 1108, and/or the microcontroller 1104.
  • the microcontroller 1104 may be a processor such as, but not limited to, a digital signal processor.
  • the apparatus 1100 for registering the time and location of weapon's firings may transmit information relating to the weapon firing in real-time, via the input/output data port 1109, to an external device and/or may store information relating to the weapon firing in memory 1106. Stored information relating to the weapon firing may in an exemplary embodiment be transmitted to an external device, via the input/output data port 1109, at a later time.
  • An exemplary embodiment of an apparatus 1100 for registering the time and location of weapon's firings may be used to, e.g., but not limited to, to register the time and location of a weapon's firing; to evaluate/monitor a weapon's performance in a real or simulated combat situation; to evaluate/monitor a soldier's actions in a real or simulated combat situation where the soldier's weapon contains an apparatus; and/or to program/fix other apparatuses for use on the same or similar weapon.
  • the soldier's actions may include, e.g., but are not limited to, weapon firings, battlefield movements, coordination with other soldiers, and weapon reloads.
  • FIGS. 12A-B depict an exemplary apparatus 1100 for registering the time and location of weapon firings.
  • Housing 1201 may include, e.g., but is not limited to, the pressure sensor 1101, the accelerometer 1102 (not shown), the signal conditioning unit 1103 (not shown), the GPS receiver 1105 (not shown), the GPS antenna 1112, the momentary switch 1110, the status indicators 1111, the input/output data port 1109, the memory 1 106 (not shown), the battery 1107, the power management system 1108 (not shown), and the microcontroller 1104 (not shown), each of which are depicted in FIG. 11.
  • the housing 1201 may be attached or coupled to a weapon via, e.g., but not limited to, rail mounts 1202 a, b (collectively 1202) on housing 1201.
  • the housing 1201 may be case made of any suitable materials, such as, for example, but not limited to, plastic, metal, rubber, and/or composites, in any suitable design.
  • the other elements of the apparatus 1100 may be disposed on or within the housing 1201.
  • the housing 1201 may be designed of materials appropriate to withstand the stress (e.g., vibration, etc.) of being attached to a weapon that will be fired repeatedly.
  • the rail mount 1202 may be disposed on the outside of the housing 1201 as shown in orthogonal view diagram 1220.
  • the rail mount 1202 may be made of any suitable material in any suitable design for allowing the secure attachment of the housing 1201 to a weapon (not shown). More than one rail mount 1202 may be disposed on the housing 1201.
  • FIGS. 13A-C depict exemplary orthogonal view diagram 1300, exemplary side view diagram 1304, and exemplary rearview diagram 1305 of an exemplary apparatus 1100 for registering the time and location of weapon firings mounted on an exemplary weapon.
  • An apparatus 1301 may be attached to an exemplary weapon 1302 by attaching the rail mounts 1202 of the apparatus to the exemplary weapon 1302.
  • the exemplary weapon 1302 may be any firearm, such as, for example, but not limited to, the depicted M16, or any other projectile based weapon whose firing may be detected via an accelerometer 1102 and/or a pressure sensor 1101.
  • the exemplary weapon 1302 may include one or more mounting points, for example the top mounting point of FIG. 13A and 13B depicted in side view 1304 of FIG.
  • the mounting point may include, for example, a mounting rail, such as, but not limited to, a Picatinny rail, manufactured by and available from Picatinny Arsenal, of Picatinny Rail, NJ USA.
  • the apparatus 1301 may be side mounted as depicted by 1305 of FIG. 13C.
  • the apparatus 1301 may be located in proximity to the exemplary weapon 1302 but not attached thereto.
  • a control board 1201 may be any suitable circuit board disposed within the housing 1201.
  • the components of the apparatus 1100, 1200 including, for example, the pressure sensor 1101, the accelerometer 1102, the signal conditioning unit 1103, the microcontroller 1104, the GPS receiver 1105, the memory 1106, the battery 1107, the power management system 1108, the input/output data port 1109, the antenna 1112, the momentary switch 11 10, the status indicators 1 1 11, and/or the GPS antenna 1112 may be disposed on, or coupled/connected to, the control board 1201. Elements not disposed directly on the control board 1201 may be coupled/connected to other elements directly disposed on the control board 1201.
  • the pressure sensor 1101 may be any sensor capable of detecting changes in pressure in the vicinity of the pressure sensor 1101.
  • the pressure sensor 1101 may be a TDCue Sensor manufactured by and available from the AAI Corporation
  • the pressure sensor 1101 may be disposed on the outside of housing 1201, for example, as depicted in FIGS. 12A-B, as the pressure sensor 1101 may require exposure to air outside of the housing 1201 to function properly.
  • pressure data from the pressure sensor 1101 may be constantly transmitted to the microcontroller 1104 through signal conditioning unit 1103.
  • the microcontroller 1104 may poll the pressure sensor 1101 at set intervals or event-based intervals.
  • the pressure sensor 1101 may be sensitive enough to detect changes in pressure, i.e., air pressure, to allow the microcontroller 1104 to distinguish between non-weapon firing events of the exemplary weapon 1302 to which the pressure sensor 1101 may be attached and the weapon firing events of the exemplary weapon 1302 to which the pressure sensor 1101 may be attached.
  • the accelerometer 1102 may be any sensor capable of detecting changes in the magnitude and/or direction of the acceleration of the accelerometer 1102 itself.
  • the accelerometer 1102 may be a piezoelectric sensor.
  • acceleration data from the accelerometer 1102 may be constantly transmitted to the microcontroller 1104, or the microcontroller 1104 may poll the accelerometer 1102 according to exemplary embodiments.
  • the accelerometer 1102 may be disposed on or within the housing 1201, and may be disposed on the control board 1201 in an exemplary embodiment.
  • the accelerometer 1102 may be sensitive enough to detect changes in the magnitude and/or direction of the acceleration of the accelerometer 1102 itself in order to distinguish between non- weapon firing events of the exemplary weapon 1302 to which the accelerometer 1102 may be attached and the weapon firing events of the exemplary weapon 1302 to which the accelerometer 1102 may be attached.
  • the signal conditioning unit 1103 may be any suitable electronics for conditioning the signals containing the data from the pressure sensor 1101 and the accelerometer 1102 so that the signals may be processed by the microcontroller 1104. For example, if the signals from the pressure sensor 1101 are too weak for the microcontroller 1104 to process correctly, the signal conditioning unit 1103 may amplify the signals from the pressure sensor 1 101 to levels suitable for processing by the microcontroller 1104. The signal conditioning unit 1103 may convert or filter signals from the pressure sensor 1101 and the accelerometer 1102, for example, to change the signals into a format recognizable by the microcontroller 1 104, or, e.g., to remove noise
  • the signal conditioning unit 1103 may be disposed within the housing 1201, on the control board 1201 in an exemplary embodiment.
  • the microcontroller 1104 may be any suitable microprocessor capable of processing the data received from the pressure sensor 1101, the accelerometer 1102, and the GPS receiver 1 105. Data from the pressure sensor 1101 and the accelerometer 1102 may be sent to the microcontroller 1104, which may use the data to determine whether the weapon has been fired. If the weapon has been fired, the microcontroller 1 104 may send the data from the pressure sensor 1101, the accelerometer 1102, and the GPS receiver 1 105 to the memory 1106. The microcontroller 1104 may also receive input from the momentary switch 1 110, control the status indicators 1111, and, if necessary, facilitate the transfer of data from the memory 1106 through the input/output data port 1109. The microcontroller 1104 may be disposed within the housing 1201, on the control board 1201 in an exemplary embodiment.
  • the GPS receiver 1105 may be any suitable device for receiving and interpreting GPS signals to determine the location of the GPS receiver 1105 at any particular time.
  • the GPS receiver 1105 may be disposed within the housing 1201, on the control board 1201 or otherwise coupled/connected thereto, or attached to the outside of the housing 1201, according to exemplary embodiments.
  • the microcontroller 1104 may request time and location data from the GPS receiver 1105.
  • the GPS receiver 1105 may need to be sensitive enough to determine location precisely and accurately enough to allow for the positions of two GPS receivers 1105 of one or more of the apparatus 1100 attached to one or more weapons located in close proximity to be distinguishable.
  • the GPS receiver 1105 may be able to determine the location of the weapon through interpolation.
  • the microcontroller 1104 may assist the GPS receiver 1105 with the calculation necessary to perform the interpolation, if necessary.
  • the memory 1106 may be any computer readable medium suitable for usage inside the housing 1201.
  • the memory 1106 may be removable or non-removable memory, storage, etc., such as, but not limited to, flash memory, a magnetic drive, an optical drive capable of fitting within the housing 1201, etc.
  • the microcontroller 1104 may read from and write to the memory 1106. Program code used by the microcontroller 1 104, for example,
  • Attorney Docket No.: 13346-286631 program code for analyzing data from the pressure sensor 1101 and the accelerometer 1 102, including data and/or parameters, such as, for example, but not limited to, a weapon firing signature, that the microcontroller 1104 may use in determining if the weapon has been fired, may be pre-written to the memory 1106.
  • Data from the pressure sensor 1101, the accelerometer 1102, and the GPS receiver 1105 may be written to the memory 1106 by the microcontroller 1104 on the occurrence of certain events, such as, for example, but not limited to, a firing of the weapon as determined by the microcontroller 1104.
  • the memory 1 106 may be directly accessible by any suitable device coupled/connected to the input/output data port 1109, or the microcontroller 1104 may be used as an intermediary by such a device.
  • the memory 1106 may be disposed within the housing 1201, and may be directly disposed on the control board 1201, or may be disposed elsewhere within the housing 1201 and coupled/connected to the control board 1201.
  • the memory 1106 may be fixed or removable. For example, if the memory 1106 is a Secure Digital flash memory card, the memory 1 106 may be inserted into the housing 1201 through a slot in the housing 1201, and may be removable.
  • the battery 1107 may be any suitable power source for providing power to the apparatus.
  • the battery 1107 may be a rechargeable battery, such as, e.g., but not limited to, nickel cadmium, nickel metal hydride, zinc, or a lithium-ion battery, or a non- rechargeable battery such as, e.g., but not limited to, lead acid, and may removable from the housing 1201, or non-removable.
  • the battery 1107 may be designed specifically for the apparatus, or may be a more common battery cell type such as, but not limited to, a hearing aid battery, a 9V, an AAA, or an AA battery.
  • the housing 1201 may be designed to accept multiple battery types. Power from the battery 1107 may be used to run all of the electronic elements of the apparatus. Battery 1107 may be replaced by another power device such as, e.g., but not limited to, a hydrogen fuel cell, or the like.
  • the power management system 1108 may be any suitable electronic circuit for managing the apparatus's use of power from the battery 1107 and/or the recharging of the battery 1107. For example, the power management system 1108 may control the distribution of power to the microcontroller 1104 to ensure that the microcontroller 1104 doesn't unnecessarily drain the battery 1107.
  • the power management system 1108 may be disposed within the housing 1201, on or coupled/connected to the control board 1201, and connected/coupled to the battery 1107.
  • the input/output data port 1 109 may be any suitable port or combination of ports for connecting the apparatus to another device, such as, for example, but not limited to, a computing device, to allow the other device to access the elements of the apparatus.
  • the input/output data port 1109 may be a wired port requiring a physical connection via a cable, or may include a wireless port implemented as e.g., a wireless transceiver device.
  • the input/output data port 1109 may be a RS-232 interface, a wired USB port, a firewire port, an eSATA port, and/or a proprietary port, or a wireless USB device, Bluetooth device, or IEEE 802.1 lx standard wi-fi , IEEE 802.16x wimax, or other wireless device.
  • the input/output data port 1109 may allow a coupled/connected device access to the pressure sensor 1101, the accelerometer 1102, the microcontroller 1104, the GPS receiver 1105, the memory 1106, and the battery 1107, for example, to allow for, e.g., the testing and calibration of the components of the apparatus.
  • a coupled/connected device may use the input/output data port 1109 to read stored data from the memory 1106, and to write program code for use by the microcontroller 1104 to the memory 1 106.
  • the input/output data port 1109 may also be used, e.g., to draw power to recharge the battery 1107.
  • the input/output data port 1109 is a wired port
  • the input/output data port 1 109 may be disposed on the outside of the housing 1201, as illustrated in diagram 1200 in FIG. 12A.
  • the wireless device used to implement the input/output data port 1109 may be disposed within or outside the housing, on or coupled/connected to the control board 1201.
  • the momentary switch 1 1 10 may include one or more suitable switch(es), button(s), or other input device(s) disposed on the outside of the housing 1201.
  • the momentary switch 1110 may be positioned on the housing 1201 such that the user of the apparatus may be able to access the momentary switch 1110 when the apparatus is attached to a weapon.
  • the momentary switch 1110 may be used, e.g., but not limited to, to input data to the microcontroller 1104, to allow a user to control the operation of the apparatus, to allow a user to turn the apparatus on/off, and indicate various conditions to the microcontroller 1 104.
  • the user may press the momentary switch 1110 while the apparatus is attached to a weapon to signal that the weapon has jammed.
  • the user may press the momentary switch when the jam is cleared.
  • the microcontroller 1104 may write the occurrence of the weapon jam and the time the jam occurred, along with the time the jam was cleared, to the memory 1106.
  • the memory 1106 may be used, e.
  • Attorney Docket No.: 13346-286631 holding the momentary switch 1110 down for a specified period of time may signal the apparatus to enter a low-power consumption mode, or to shut down.
  • the status indicators 1111 may be one or more lights or light emitting diode (LED) indicators of varying colors, a LED screen, a liquid crystal display (LCD) device or any other suitable visual display device.
  • LED light emitting diode
  • the status indicators 1111 may be a pair of LED indicators disposed on the outside of the housing 1201, next to the momentary switch 1110.
  • the status indicators 111 1 may be used to convey information about the status of the apparatus, and the various elements thereof, to a user of the apparatus.
  • the status indicators 1111 may indicate the condition of the battery 1107 such as, e.g., but not limited to, low battery, battery charging, and/or battery charged, attainment or loss of the GPS signal by the GPS receiver 1105, data transfer activity through the input/output data port 1109, whether the device is on or off, etc.
  • the GPS antenna 1112 may be any antenna suitable for use with the GPS receiver 1105.
  • the GPS antenna 1112 may be disposed on the outside or the inside of the housing 1201.
  • the GPS antenna 1112 may pick up GPS signals and relay the GPS signals to the GPS receiver 1105.
  • FIGS. 14A and 14B depict exemplary graphs 1400, 1450 for a pressure sensor 1101 output and an accelerometer 1102 output, respectively, during a single exemplary weapon firing of the exemplary weapon 1302.
  • the exemplary weapon 1302 may generate generic waveforms and/or unique waveform when compared to a related weapon.
  • a generic waveform may be identical or similar to waveforms generated by related weapons.
  • a unique waveform may be a waveform that is specific to the exemplary weapon 1302.
  • the exemplary weapon 1302 may generate a waveform which is, in part, both generic and unique when compared to a related weapon.
  • a related weapon may refer to a weapon of the same model type, a weapon of a related model type, and/or a weapon of a different model type which contains one or more components in common with the exemplary weapon 1302, such as, but not limited to, components of the firing mechanism and/or the loading mechanism.
  • Attorney Docket No.: 13346-286631 weapons may generate generic and/or unique waveforms when compared to other related weapons depending on the behavior of the common components.
  • FIG. 14A may represent exemplary pressure sensor
  • the pressure sensor line 1406 of graph 1400 may plot the values sensed by pressure sensor 1 101, for example, in pounds per square inch, on the y-axis 1402 versus the time on the x-axis 1404, measured, for example, in milliseconds.
  • FIG. 14B may represent exemplary accelerometer 1102 data resulting from a single shot fired from the exemplary weapon 1302 with the apparatus 1100 attached.
  • the exemplary weapon 1302 may be a M16 rifle.
  • the accelerometer line 1456 of graph 1450 plots the values sensed by the accelerometer 1102, for example, in pounds per square inch, on the y-axis 1452 versus the time on the x-axis 1454, measured, for example, in milliseconds.
  • both sensors may be quiet from 0 ms until approximately 2.5 ms.
  • the exemplary weapon 1302 may be aimed, held still, etc.
  • both sensors may detect movement of the firing pin forward towards the primer and the firing pin's contact with the primer, which starts the pyrotechnic chain.
  • the exemplary weapon 1302 may reach maximum rearward acceleration.
  • the rearward acceleration of the exemplary weapon 1302 may stop and the sensors detect a maximum pressure as the bullet exits the muzzle.
  • the time point for example, but not limited to, at which the bullet exits the gun may be marked and the GPS location of the M16 rifle is stored in memory 1106.
  • Sensor readings recorded after the bullet exits the muzzle i.e. at approximately 4.5 ms to 10 ms, may illustrate the decay of oscillations after a firing.
  • FIG. 15A may depict exemplary pressure sensor 1 101 data resulting from a double round burst from an exemplary weapon firings of the exemplary weapon 1302.
  • the exemplary weapon 1302 may be a M16 rifle.
  • the pressure sensor line 1506 of graph 1500 may plot the values sensed by pressure sensor 1 101, for example, in pounds per square inch, on the y-axis 1502 versus the time on the x-axis 1504, measured, for example, in milliseconds.
  • FIG. 15B may depict exemplary accelerometer 1102 data resulting from a double round burst from an exemplary weapon firings of the exemplary weapon 1302.
  • the exemplary weapon 1302 may be a M16 rifle.
  • the accelerometer line 1556 of graph 1550 may plot the values sensed by pressure sensor 1101, for example, in pounds per square inch, on the y-axis 1552 versus the time on the x-axis 1554, measured, for example, in milliseconds.
  • both sensors may be quiet from 0 ms until approximately 1 1 ms, as indicated by pressure sensor line 1506 and accelerometer line 1556.
  • the exemplary weapon 1302 may be aimed, held still, etc.
  • both sensors may detect movement of the firing pin forward towards the primer and the firing pin's contact with the primer, which starts the pyrotechnic chain.
  • the exemplary weapon 1302 may reach maximum rearward acceleration.
  • the rearward acceleration of the exemplary weapon 1302 may stop and the sensors detect a maximum pressure as the bullet exits the muzzle. This time point is marked and the GPS location of the M16 rifle is stored in memory 1106. Sensor readings recorded after the bullet exits the muzzle, i.e. at 14 ms to 25 ms, may illustrate the decay of oscillations after a firing.
  • the pressure sensor 1101 and/or the accelerometer 1102 may detect the bolt stopping abruptly in the buffer in its rearward travel. From approximately 90 ms to 100 ms, the pressure sensor 1101 and/or the accelerometer 1102 may detect the bolt picking up the next round from the clip, the bolts movement forward, and the bolt closing. At approximately 111 ms both sensors may detect movement of the firing pin forward towards the primer and the firing pin's contact with the primer, which starts the pyrotechnic chain. At approximately 1 11.75 ms the exemplary weapon 1302 reaches maximum rearward acceleration.
  • the rearward acceleration of the exemplary weapon 1302 stops and the sensors detect a maximum pressure as the bullet exits the muzzle. This time point is marked and the GPS location of the Ml 6 rifle is stored in memory 1106. Sensor readings recorded after the bullet exits the muzzle, i.e. at 1 13 ms to 120 ms, illustrate the decay of oscillations after a firing.
  • FIGS. 14A, 14B, 15A and 15B may be included in an exemplary firing signature for an exemplary Ml 6 rifle, with the pressure sensor lines 1406 and 1506
  • FIGS. 14A and 14B may be a firing signature for a single shot from an Ml 6 rifle, and the microcontroller 1104 may determine if a weapon has been fired by comparing data from the pressure sensor 1101 and the accelerometer 1102 of the weapon to the known firing signature.
  • FIGS. 14A and 14B may be a firing signature for a first shot and a consecutive shot from exemplary weapon 1302.
  • the microcontroller 1104 may determine if a weapon has been fired by comparing data from the pressure sensor 1 101 and the accelerometer 1 102 to the known firing signature for the exemplary weapon.
  • the data from the pressure sensor 1101 and the accelerometer 1102 may be output to another computer where the data may be compared to the firing signature for the weapon in order to determine if the weapon was fired.
  • FIG. 16 depicts an exemplary flowchart 1600 for the operation of an exemplary apparatus for registering the time and location of weapon firings, and will be described with respect to FIGS. 11, 13, 14A, and 14B.
  • Flowchart 1600 may, for example, but not limited to, take place in real-time or on a time delay.
  • the apparatus 1100 may be turned on, or remain on, and the microcontroller 1104 may being monitoring data received from the pressure sensor 1101 and the accelerometer 1102. From 1601, 1600 may continue with both 1602 and 1603 in parallel, in an exemplary embodiment.
  • the microcontroller 1104 may monitor data received from the pressure sensor 1101. Data from the pressure sensor 1101 may be sent continuously to the microcontroller 1104, or the microcontroller 1104 may poll the pressure sensor 1101 for data. The data received may be stored in memory 1106. From 1602, 1600 may continue with 1604.
  • the microcontroller 1 104 may monitor data received from the accelerometer 1102. Data from the accelerometer 1102 may be sent continuously to the microcontroller 1104, or the microcontroller 1 104 may poll the accelerometer 1102 for data. Block 1602 and block 1603 may be performed simultaneously if the microcontroller 1104 is
  • the microcontroller 1104 may check the data received from the pressure sensor 1101 to determine if a potential weapon firing event has occurred.
  • a potential weapon firing event may result from a weapon firing event or a non-weapon firing event.
  • a non- weapon firing event may be any event, other than a weapon firing event, which appears to be similar to a weapon firing event based on the data from the pressure sensor 1101. For example, the firing of a different weapon in close proximity to the pressure sensor 1101 may result in data from the pressure sensor 1 101 that would appear to the microcontroller 1104 to be similar to an actual firing of the weapon.
  • the microcontroller 1104 may determine if a potential weapon firing event has occurred by comparing data received from the pressure sensor 1101 with previously stored/known data and/or parameters, for example, data gathered during testing of the weapon and the pressure sensor 1101 (such as, e.g., but not limited to, data gathered in FIGS. 14A, 14B, 15A, and 15B).
  • the stored data and/or parameters may be in the form of a firing signature. If no potential firing event has occurred, flow may proceed to block 1606 of flow diagram 1600. Otherwise, if a potential firing event has occurred, flow may proceed to block 1608 of flow diagram 1600.
  • the microcontroller 1104 may check the data received from the accelerometer 1102 to determine if a potential weapon firing event has occurred.
  • a potential firing event may result from a weapon firing event or a non-weapon firing event.
  • a non- weapon firing event may be any event, other than a weapon firing event, which appears to be similar to a weapon firing event based on the data from the accelerometer 1102. For example, the weapon being dropped or jarred may result in data from the accelerometer 1102 that would appear to the microcontroller 1104 to be similar to an actual firing of the weapon.
  • the microcontroller 1104 determine if a potential weapon firing event has occurred by comparing data received from the accelerometer 1 102 with previously stored data and/or parameters, for example, data gathered during testing of the weapon and the accelerometer 1102 (such as, e.g., but not limited to, data gathered in FIGS. 14A, 14B, 15A, and 15B).
  • the stored data and/or parameters may be in the form of a firing signature. If no potential firing event has occurred, flow may proceed back to block 1607 of flow diagram 1600. If a potential firing event has occurred, flow may proceed to block 1608 of flow diagram 1600.
  • the data from the accelerometer 1102 may be compared with accelerometer line 1456 and/or accelerometer line 1556 from FIGS. 14B and 15B.
  • the accelerometer lines 1456 and 1556 may represent the accelerometer 1102 firing signature for a single shot and burst shot, respectively, of an exemplary weapon. Combining the accelerometer 1 102 firing signatures with the respective pressure sensor 1101 firing signatures may result in a single shot firing signature and burst shot firing signature for an exemplary weapon.
  • Block 1604 and block 1605 may be performed simultaneously if the microcontroller 1 104 is capable of parallel receipt and processing of data, or in a sequential, alternating cycle.
  • the microcontroller 1104 may write data from the non-potential weapon firing event to the memory 1106 and/or transmit the data in real-time via input/output data port 1109.
  • the data may include data from the pressure sensor 1101, the time at which the non- potential weapon firing event took place, and the location of the weapon when the non-potential weapon firing event took place.
  • the microcontroller 1104 may receive data on the time and the location of the exemplary weapon 1302 from the GPS receiver 1105.
  • a non-weapon firing event may include, e.g., but is not limited to, the dropping of the weapon, a weapon malfunction (such as, but not limited to, a jam), reloading the weapon, and/or the firing of another weapon in proximity to the exemplary weapon, etc. From 1606, flow 1600 may continue to 1602.
  • the microcontroller 1104 may write data from the non-potential weapon firing event to the memory 1106 and/or transmit the data in real-time via input/output data port 1109.
  • the data may include data from the accelerometer 1102, the time at which the non- potential weapon firing event took place, and the location of the weapon when the non-potential weapon firing event took place.
  • the microcontroller 1104 may receive data on the time and the location of the exemplary weapon 1302 from the GPS receiver 1105.
  • a non-weapon firing event may include, e.g., but is not limited to, the dropping of the weapon, a weapon malfunction (such as, but not limited to, a jam), reloading the weapon, and/or the firing of another weapon in proximity to the exemplary weapon, etc. From 1607, flow 1600 may continue with 1603.
  • the microcontroller 1104 may check the data from the pressure sensor 1101 and/or the accelerometer 1102 to determine if a weapon firing event occurred (i.e.
  • Attorney Docket No.: 13346-286631 determine whether the potential weapon firing events detected in block 1604 and/or 1605 are weapon firing events).
  • the microcontroller 1104 may determine that a weapon firing event occurred when a potential weapon firing event was detected in both block 1604 and block 1605.
  • the microcontroller 1104 may also compare the data from both the pressure sensor 1101 and the accelerometer 1102 to previously stored data and/or parameters, as in blocks 1604 and 1605, to confirm that a weapon firing event has occurred. If a non-weapon firing event has occurred (i.e. a potential firing event was not detected in both block 1604 and 1605), flow 1600 may proceed to block 1609. If it is determined in 1608 that a weapon firing event has occurred, flow 1600 may proceed to block 1610. In another exemplary embodiment, in the event of a non-weapon firing event, flow 1600 may continue to 1601.
  • the microcontroller 1104 may write data from the non- weapon firing event to the memory 1106 and/or transmit the data in real-time via input/output data port 1109.
  • the data may include data from the pressure sensor 1101 and the accelerometer 1102, the time at which the non-weapon firing event took place, and the location of the weapon when the weapon firing event took place.
  • the microcontroller 1104 may receive data on the time and the location of the exemplary weapon 1302 from the GPS receiver 1105.
  • a non-weapon firing event may include, e.g., but is not limited to, the dropping of the weapon, a weapon malfunction (such as, but not limited to, a jam), reloading the weapon, and/or the firing of another weapon in proximity to the exemplary weapon, etc. From 1609, flow 1600 may continue with 1601.
  • the data from the pressure sensor 1101 may appear to indicate that the exemplary weapon 1302 has been fired, matching, for example, the weapon's pressure sensor 1101 firing signature.
  • the data from the accelerometer 1102 would not corroborate the data from the pressure sensor 1101, as the data would not, for example, match the weapon's accelerometer 1102 firing signature.
  • the firing of a different weapon in proximity to the accelerometer 1102 may not result in the exemplary weapon 1302 the accelerometer 1102 is attached to moving, so data from the accelerometer 1102 would not match the stored data and/or parameters, i.e., the weapon firing signature, for an actual weapon firing.
  • the data from accelerometer 1102 may appear to indicate that the weapon has been fired, for example, matching the weapon's accelerometer 1102 firing signature.
  • data from the pressure sensor 1101 may not corroborate the data from the accelerometer 1102, for example, not matching the weapon's pressure sensor 1101 firing signature, as dropping a weapon may not result in the pressure sensor 1102 registering changes in pressure that are consistent with a weapon firing.
  • the microcontroller 1104 may write data from the weapon firing event to the memory 1 106 and/or transmit the data in real-time via input/output data port 1109.
  • the data may include data from the pressure sensor 1101 and the accelerometer 1102, the time at which the weapon firing event took place, and the location of the weapon, when the weapon firing event took place, etc.
  • the microcontroller 1104 may receive data on the time and the location of the weapon from the GPS receiver 1105.
  • the memory 1106 may include a record of every firing or non- weapon firing event of the exemplary weapon 1302 to which the apparatus has been attached, including the time of the firing, the location of the weapon during each weapon firing event, the data from the pressure sensor 1101, and the accelerometer 1102 that caused the microcontroller 1104 to determine that a firing took place.
  • the memory 1106 may also include data from the momentary switch 1110, indicating, for example, the time of a weapon jam, and the time the jam was cleared.
  • the data may also be transmitted in real-time via input/output data port 1109 to an external computing device, for example.
  • the record of the weapon firing may be used for a variety of purposes, including, for example, testing the efficacy of the weapon in a live fire situation, manufacturing additional apparatuses for registering the time and location of weapon firings, testing the ability of the user of the weapon, and/or tracking weapon usage for maintenance purposes.
  • the record of weapon firing may be used to load generic waveforms into the additional apparatuses.
  • the record of exemplary weapon firings over a period of time may be compared to determine if the weapon is in need of
  • targets may be set up with equipment capable of recording data of projectiles fired at the targets or in proximity to the targets. Such data may be correlated, by various means, with the data from the memory 1106 of one or more of the apparatus 1100 attached to one or more weapons, allowing for most, if not all, of the shots fired in the testing to be tracked from the firing of the weapon to the projectile passing on or near a target, or completely missing the target. Methods and systems for such tracking are discussed elsewhere in this application.
  • FIG. 17 depicts diagram illustrating an exemplary computer system 1700 such as may be used in, or in combination with devices 1101-1112, etc. and that may be used in implementing an exemplary embodiment of the present invention.
  • FIG. 17 depicts an exemplary embodiment of a computer system 1700 that may be used in computing devices such as, e.g., but not limited to, a client and/or a server, etc., according to an exemplary embodiment of the present invention.
  • the present invention (or any part(s) or function(s) thereof) may be implemented using hardware, software, firmware, and/or a combination thereof and may be implemented in one or more computer systems 1700 or other processing systems.
  • FIG. 17 depicts an example computer 1700, which in an exemplary embodiment may be, e.g., but not limited to, a personal computer (PC) system running an operating system such as, e.g., (but not limited to) MICROSOFT® WINDOWS® NT/98/2000/XP7CE/ME/VISTA/etc. available from MICROSOFT® Corporation of Redmond, WA, U.S.A.
  • PC personal computer
  • the invention may not be limited to these platforms. Instead, the invention may be implemented on any appropriate computer system running any appropriate operating system such as, e.g., but not limited to, an Apple computer executing MAC OS. In one exemplary embodiment, the present invention may be implemented on a computer system operating as discussed herein. An exemplary computer system, computer 1700 is shown in FIG. 17. Other exemplary computer systems may include additional components, such as, e.g., but not limited to, a computing
  • Attorney Docket No.: 13346-286631 device a communications device, mobile phone, a telephony device, an iPhone (available from Apple of Cupertine, CA USA), a 3G wireless device, a wireless device, a telephone, a personal digital assistant (PDA), a personal computer (PC), a handheld device, a portable device, an interactive television device (iTV), a digital video recorder (DVD), client workstations, thin clients, thick clients, fat clients, proxy servers, network communication servers, remote access devices, client computers, server computers, peer-to-peer devices, routers, gateways, web servers, data, media, audio, video, telephony or streaming technology servers, game consoles, content delivery systems, etc., may also be implemented using a computer such as that shown in FIG.
  • services may be provided on demand using, e.g., but not limited to, an interactive television device (iTV), a video on demand system (VOD), via a digital video recorder (DV ), and/or other on demand viewing system.
  • iTV interactive television device
  • VOD video on demand system
  • DV digital video recorder
  • the computer system 1700 may include one or more processors, such as, e.g., but not limited to, processor(s) 1704.
  • the processor(s) 1704 may be coupled to and/or connected to a communication infrastructure 1706 (e.g., but not limited to, a communications bus, cross-over bar, or network, etc.).
  • a communication infrastructure 1706 e.g., but not limited to, a communications bus, cross-over bar, or network, etc.
  • Various exemplary embodiments may be described in terms of this exemplary computer system 1700. After reading this description, it may become apparent to a person skilled in the relevant art(s) how to implement the invention using other computer systems and/or architectures.
  • Computer system 1700 may include a display interface 1731 that may forward, e.g., but not limited to, graphics, text, and other data, etc., from the communication infrastructure 1706 (or from a frame buffer, etc., not shown) for display on the display unit 1730.
  • a display interface 1731 may forward, e.g., but not limited to, graphics, text, and other data, etc., from the communication infrastructure 1706 (or from a frame buffer, etc., not shown) for display on the display unit 1730.
  • the computer system 1700 may also include, e.g., but may not be limited to, a main memory 1708, random access memory (RAM), and a secondary memory 1710, etc.
  • the secondary memory 1710 may include a computer readable medium such as, for example, (but not limited to) a hard disk drive 1712 and/or a removable storage drive 1714, representing a floppy diskette drive, a magnetic tape drive, an optical disk drive, magneto-optical, a compact disk drive CD-ROM, etc.
  • the removable storage drive 1714 may, e.g., but not limited to, read from and/or write to a removable storage unit 1718 in a well known manner.
  • Removable storage unit 1718 also called a program storage device or a computer program product, may represent, e.g., but not limited to, a floppy disk, magnetic tape, optical disk, compact disk, etc. which may be read from and written to by removable storage drive 1714. As may be
  • the removable storage unit 1718 may include a computer usable storage medium having stored therein computer software and/or data.
  • a "machine- accessible medium” may refer to any storage device used for storing data accessible by a computer. Examples of a machine-accessible medium may include, e.g., but not limited to: a magnetic hard disk; a floppy disk; an optical disk, like a compact disk read-only memory (CD- ROM), flash memory, non-volatile memory, or a digital versatile disk (DVD); digital video recorder disk (DVR); a magnetic tape; and a memory chip, etc.
  • secondary memory 1710 may include other similar devices for allowing computer programs or other instructions to be loaded into computer system 1700.
  • Such devices may include, for example, a removable storage unit 1722 and an interface 1720.
  • Examples of such may include a program cartridge and cartridge interface (such as, e.g., but not limited to, those found in video game devices), a removable memory chip (such as, e.g., but not limited to, an erasable programmable read only memory (EPROM), or programmable read only memory (PROM) and associated socket, and other removable storage units 1722 and interfaces 1720, which may allow software and data to be transferred from the removable storage unit 1722 to computer system 1700.
  • a program cartridge and cartridge interface such as, e.g., but not limited to, those found in video game devices
  • EPROM erasable programmable read only memory
  • PROM programmable read only memory
  • Computer 1700 may also include an input device such as, e.g., (but not limited to) a mouse 1706 or other pointing device such as a digitizer, an audio capture device 1728 (such as, e.g., but not limited to, a microphone), an image video/visual capture device 1732 (such as, e.g., but not limited to, a camera), and a keyboard 1705 and/or other data entry device (not shown), etc.
  • an input device such as, e.g., (but not limited to) a mouse 1706 or other pointing device such as a digitizer
  • an audio capture device 1728 such as, e.g., but not limited to, a microphone
  • an image video/visual capture device 1732 such as, e.g., but not limited to, a camera
  • keyboard 1705 and/or other data entry device not shown
  • Computer 1700 may also include output devices, such as, e.g., (but not limited to) display 1730, display interface 1731, and/or a speaker 1707, etc. Other output devices may also be used, including, e.g., but not limited to, a printer, etc.
  • Computer 1700 may include input/output (I/O) devices such as, e.g., (but not limited to) communications interface 1724 and communications path 1726, etc. These devices may include, e.g., but not limited to, a network interface card 1702, and modem(s) 1703.
  • Communications interface 1724 may allow software and data to be transferred between computer system 1700 and external devices.
  • computer program medium and “computer readable medium” may be used to generally refer to media such as, e.g., but not limited to removable storage drive 1714, a hard disk installed in hard disk drive 1712, a storage area network (SAN),
  • SAN storage area network
  • ⁇ may provide software to computer system 1700.
  • the invention may be directed to such computer program products.
  • a computer program product may include software which may be distributed via a communication system and then may be stored on a storage device.
  • FIG. 18 depicts an exemplary system for use with an exemplary method of correlating weapon firing events, from multiple weapons, with scoring events.
  • the exemplary system 1800 may be comprised of, for example, but not limited to, a scoring area 1801, two (or more) weapons 1814A, 1814B, two (or more) apparatuses for registering the time and location of weapon firings (hereinafter referred to as 'player packs') 1812A and 1812B for registering the time and location of a weapon firing (mounted to the weapons 1814A and 1814B, respectively), a target interface unit (TIU) 1808, and a lifter 1804.
  • a scoring area 1801 two (or more) weapons 1814A, 1814B
  • 'player packs' two apparatuses for registering the time and location of weapon firings
  • TIU target interface unit
  • Scoring area 1801 may include, e.g., but is not limited to, a target 1802 and a suppression zone 1803.
  • An exemplary scoring area is described elsewhere in this application.
  • a scoring event may refer to the passage of a projectile through the scoring area 1801.
  • Player packs 1812A, 1812B which are described elsewhere in this application, may be capable of unambiguously identifying a weapon firing event and recording data related to that event.
  • Data related to a weapon firing event may be, e.g., but not is limited to, the time the event occurred and the position where the event occurred.
  • the TIU 1808 which is described elsewhere in this application, may be capable of detecting scoring events that occur in the scoring area 1801 and recording data related to those events.
  • Data related to a scoring event may be, e.g., but is not limited to, the time at which each scoring event occurred, where the projectile passed through the scoring area 1801, whether the target 1802 was exposed when each scoring event occurred, the location of the target 1802 when the scoring event occurred, the orientation of the scoring area 1801 with respect to a reference direction (such as, e.g., true north), and/or the angle of incidence of the scoring event (e.g. the angle of incidence of the projectile which caused the scoring event) with respect to the reference direction.
  • a reference direction such as, e.g., true north
  • the angle of incidence of the scoring event e.g. the angle of incidence of the projectile which caused the scoring event
  • the determination of time at which each scoring event occurred and the time at which each weapon firing event took place may be synchronized with a common source of time, such as, e.g., but not limited to, an atomic clock or a GPS signal.
  • player packs 1812A, 1812B and the TIU 1808 may have internal clocks which have been synchronized to a common source of time.
  • player packs 1812A, 1812B and the TIU 1808 may continuously and/or periodically receive the time from a common source, such as a global positioning system (GPS) signal.
  • GPS global positioning system
  • the player packs 1812A, 1812B and/or the TIU 1808 may be able to exchange, e.g., on a delay, or in real-time, recorded data with one another or with computer 1810, TIU 1808, sensor
  • the player packs 1812A and 1812B, TIU 1808, and computer 1810 may be coupled to one another wirelessly or by wires while information is exchanged.
  • the computer 1810 may be able to execute a method of correlating weapon firing events, recorded by player packs 1812A and 1812B, with scoring events, recorded by the TIU 1808, which occur in the scoring area 1801.
  • the computer 1810 may be comprised of hardware, software, or a combination of hardware and software, and communications networking hardware and software.
  • FIG. 19 depicts an exemplary flowchart 1900 for an exemplary method of correlating weapon firing events, from multiple weapons, with scoring events.
  • the exemplary method 1900 begins in block 1905 and may proceed immediately to block 1910.
  • exercise parameters may be received.
  • Exercise parameters may refer to characteristics of an exemplary exercise which may be monitored by at least one player pack 1812A, 1812B and at least one TIU 1808. Exercise parameters may improve the accuracy or efficiency of the exemplary method of correlating weapon firing events, from multiple weapons, with scoring events.
  • Exercise parameters may refer to time of flight (TOF) tables for the type(s) of weapon(s)/monition(s) that will be used in the exercise, the number of weapons 1814A, 1814B used in the exercise, the number of targets 1802 used in the exercise, the dimensions or size of the area where the exercise will be conducted, anticipated GPS location calculation errors (including WAAS and non-WAAS GPS errors), the upper and lower limits of an average weapon burst count, the average number of burst shots that result in "No Scores," the average
  • flow diagram 1900 may continue with 1915.
  • scoring event data from the TIU 1808 may be received.
  • Scoring event data accessed from the TIU 1808 may include, e.g., but is not limited to, the time at which each scoring event occurred due to the impact of a projectile, whether the target 1802 was in an exposed position when the scoring event occurred, the location of the target 1802 when the scoring event occurred, the orientation of the scoring area 1801 with respect to a reference direction, and/or the angle of incidence of the projectile with respect to the reference direction.
  • the scoring event data may be sorted by scoring area 1801 (in the event more than one scoring area 1801 is in use) and the time at which the scoring event occurred.
  • the computer 1810 may receive data from the TIU 1808, e.g., in real-time, at set intervals, and/or upon completion of an event, such as a training exercise. From 1915, flow diagram 1900 may continue with 1920.
  • weapon firing event data from the player packs 1812A, 1812B may be received.
  • Weapon firing event data accessed from the player packs 1812A, 1812B may include, e.g., but is not limited to, the time at which each weapon firing event took place, the location of the weapon 1814A, 1814B during each firing event, the data from the pressure sensor within the player pack 1812A, 1812B, and the data from the accelerometer that caused the player pack 1812A, 1812B to determine that a firing took place.
  • the weapon firing data may be sorted by weapon 1814A, 1814B (in the event more than one weapon firing event occurred) and the time at which the weapon firing event occurred.
  • the computer 1810 may receive data from the TIU 1808 in real-time, at set intervals, and/or upon completion of an event, such as a training exercise. From 1920, flow diagram 1900 may continue with 1925.
  • a correlation of unambiguous, one-to-one pairings between scoring events and weapon firing events may occur.
  • the scoring event and weapon firing event information may be marked as resolved.
  • exemplary weapon-firing event information may be associated with the exemplary scoring event and exemplary scoring event information may be associated with exemplary weapon firing event information. Both the exemplary weapon-firing event and the exemplary scoring event
  • Attorney Docket No.: 13346-286631 may be marked as a resolved pair. Once a resolved pair is established, it may be removed from further consideration in blocks 1930 through 1955. An exemplary embodiment of block 1925 is described further below with reference to FIG. 20. From 1925, flow diagram 1900 may continue with 1930.
  • one or more additional correlations of unambiguous, one-to-one pairings between the remaining scoring events and weapon firing events may occur.
  • the one or more additional correlations may occur by removing all previously resolved weapon firing events and scoring events from consideration and re-running block 1925.
  • weapon firing event A may ambiguously match scoring events A and B in block 1925.
  • weapon firing event A is determined to be within the time and angular windows of scoring event A and scoring event B.
  • weapon firing event A does not unambiguously match scoring event A or scoring event B.
  • weapon firing event B may unambiguously match scoring event B and, therefore, be removed from consideration following block 1925.
  • weapon firing event A may now be the only weapon firing event which unambiguously matches the time and angular window of scoring event A.
  • weapon firing event A may be an unambiguous match with scoring event A.
  • the time window and angular window may increase, decreased or remain unchanged from one correlation to the next.
  • the time window may be increased/decreased, for example, by assuming the TOF for an exemplary projectile is longer/shorter than originally calculated.
  • the angular window may be increased/decreased, for example, by assuming the location determination of the weapon firing event and/or scoring event is less/more accurate than originally calculated. From 1930, flow diagram 1900 may continue with 1935.
  • one or more additional correlations of unambiguous, one-to-one pairings between the remaining scoring events and weapon firing events may occur.
  • the third correlation may occur by removing all previously resolved weapon firing events and scoring events from consideration and performing the method of block 1925.
  • the time window and angular window may increase, decreased or remain unchanged from one correlation to the next.
  • the time window may be increased/decreased, for example, by assuming the TOF for an exemplary projectile is longer/shorter than originally calculated.
  • the angular window may be increased/decreased, for example, by assuming the location determination of the weapon firing event and/or scoring event is less/more accurate than originally calculated. From 1940, flow diagram 1900 may continue with 1945.
  • the computer 1810 may correlate unresolved scoring event data with unresolved weapon firing event data and identify additional unambiguous, one-to-one pairings by repeating block 1925 with a reduced the time and angular window. From 1945, flow diagram 1900 may continue with 1950.
  • the process may identify two or more unresolved weapon firing events which are within a given time window and angular window associated with two or more unresolved scoring events. In an exemplary embodiment, these events may be resolved and/or recorded separately as unresolved events. From 1950, flow diagram 1900 may continue with 1955.
  • the unresolved weapon firing events and unresolved scoring events may be arbitrarily resolved (i.e. arbitrary matched).
  • Weapon firing events may be arbitrarily matched to scoring events in a variety of situations. For example, where accuracy is a concern and there are two unresolved weapon firing events (weapon firing events A and B) and two unresolved scoring events (scoring events A and B), weapon firing event A may be arbitrarily matched to scoring event B and weapon firing event B may be arbitrarily matched to scoring event A.
  • neither weapon firing event may be arbitrarily matched to scoring event A.
  • weapon firing event A may be arbitrarily matched to scoring event A.
  • the process may identify any remaining weapon firing events which are not within the time window and angular window associated with any scoring event (i.e. not even an unresolved ambiguous pairings). These weapon firing events may be marked as a "No Score" shots in the shooter record. From 1955, flow diagram 1900 may continue with 1960.
  • FIG. 20 depicts an exemplary method 2000 by which an exemplary embodiment of block 1925 of flow diagram 1900 may correlate unambiguous one-to-one pairings among scoring events and weapon firing events.
  • the time of each scoring event may be compared to the time of each weapon firing event. If, for example, an exemplary weapon firing event occurred within a given time window of an exemplary scoring event, the exemplary weapon firing event and the exemplary scoring event may match.
  • a time window may refer to a period of time in which the exemplary projectile, which caused the exemplary weapon firing event, may have caused the exemplary scoring event.
  • a time window may refer to, e.g., but is not limited to, the exemplary time-of-flight (TOF) of the projectile plus or minus any potential variation in the exemplary projectile's TOF.
  • TOF time-of-flight
  • the time window is added to the time of the exemplary weapon firing event to produce an adjusted weapon firing event time.
  • the adjusted weapon firing event time is then compared to the time of the exemplary scoring event. If the adjusted time of the exemplary weapon firing event occurred at the same time as the exemplary scoring event, accounting for the potential variations in the exemplary TOF of the projectile, the exemplary weapon firing event and the exemplary scoring event may match.
  • TOF may refer to the time a projectile may take to reach the scoring area 1801 from where it was fired (i.e. the weapon firing event location). TOF may be based on a particular projectile's known muzzle velocity, bullet aerodynamics, and the ambient temperature as well as the distance between the weapon event and the scoring area 1801.
  • Potential variations in the TOF of the projectile may depend on the muzzle velocity variations among a particular type of ammunition and/or the accuracy of the location determinations of the weapon firing event and the scoring event. Variations in muzzle velocity for an exemplary type of ammunition may be known and/or controlled by, for example, a government entity, to be within an acceptable range, for example 40 ft/sec.
  • the accuracy of the location determinations of the weapon firing event and the scoring event depends on the accuracy of the location determination means, which are discussed elsewhere in this application. If, for example, the distance between a weapon firing event and a potential scoring event is calculated to be 300 feet, but the weapon firing event location determination is accurate to within +/- 25 feet and the scoring event location determination is
  • the time window may be large enough to encompass the TOF of a projectile over a distance which is within +/- 30 feet of the calculated distance between the weapon firing event and the potential scoring event (i.e. 300 feet +/- 30 feet). From 2005, flow diagram 2000 may continue with 2010.
  • the angle of incidence with respect to a reference direction for each scoring event may be compared to a position-calculated angle of incidence for each weapon firing event under consideration.
  • the position-calculated angle of incidence may refer to the angle between a line connecting the location of the scoring area 1801 to the location of each weapon firing event and the reference direction. If, for example, the position-calculated angle of incidence for an exemplary weapon firing event is within a given angular window for the angle of incidence of an exemplary scoring event, the exemplary scoring event and the exemplary weapon firing event may match.
  • the TIU 1808 may determine the angle of incidence for the scoring event with the scoring area 1801. An exemplary TIU 1808 is described elsewhere in this application. In addition, the TIU 1808 may also determine the direction of the reference direction.
  • the computer 1810 may calculate the position-calculated angle of incidence for each weapon firing event under consideration.
  • the computer 1810 may calculate the position-calculated angle by, for example, receiving the position of an exemplary weapon associated with an exemplary weapon firing event, from player packs 1812A or 1812B, and the position of the scoring area 1801 associated with an exemplary scoring event, from TIU 1808, when the firing event under consideration occurred.
  • the computer 1810 may also receive the reference direction from TIU 1808.
  • the position-calculated angle may also be determined via a reference point instead of the location of the scoring area 1801.
  • the reference point may be, for example, but not limited to, a location of the projectile as it passed through the scoring area 1801 (such as the location of the projectile as it first enters the scoring area 1801, exits the scoring area 1801, or as mid-way through the scoring area 1801) or the center of scoring area 1801.
  • the computer 1810 may "draw" a reference line between the weapon position and the scoring area 1801 position.
  • the computer 1810 may then determine the angle created by the reference line and the reference direction.
  • An exemplary process by which a position-calculated angle may be determined is discussed further below with reference to FIGS. 23 A and 23B.
  • an angular window may refer to a range of position- calculated angles within which an exemplary projectile, which may have caused an exemplary scoring event, may have originated.
  • the angular window may, for example, refer to the position-calculated angle of incidence plus or minus any potential variations in the position- calculated angle of incidence and/or the angle of incidence for the scoring event with the scoring area 1801, with respect to the reference direction.
  • Potential variations in the position-calculated angle of incidence between the scoring area 1801 and the weapon may be caused by, for example, but not limited to, the accuracy of the location determination of the scoring area 1801 (such as, for example, the center of the scoring area 1801) and the weapon location where the weapon firing event being considered occurred.
  • the angular window therefore, may be large enough to encompass all potential position- calculated angles.
  • the angular window may be large enough to encompass a position-calculated angle of incidence caused by a projectile fired within +/- 30 feet of the weapon firing event location determination at a scoring area 1801 within +/- 5 feet of the scoring event location determination.
  • the location determination accuracy may impact the size of an angular window for an exemplary scoring event and an exemplary weapon firing event.
  • an angular window for an exemplary weapon firing event and an exemplary scoring event separated by 50 feet +/- 30 feet may be considerably larger than an angular window for an exemplary weapon firing event and an exemplary scoring event separated by 300 feet +/- 25 feet.
  • the applicable angular window therefore, maybe inverse to the distance between the weapon firing event and the scoring event.
  • the accuracy of the location determination of the scoring event when the scoring event occurred may depend on whether the scoring area 1801 is moving or stationary.
  • the location of a stationary scoring area 1801 may be averaged over time and, therefore, be fairly accurate.
  • the location of a moving scoring area 1801 may be averaged over a smaller amount of time and, therefore, be less accurate.
  • Potential variations in the angle of incidence for the scoring event with the scoring area 1801, with respect to the reference direction may be due to, for example, but not limited to, improper setup of the TIU 1808 and/or a known accuracy range of the TIU 1808.
  • an exemplary TIU 1808 may be able to calculate the angle of incidence of the scoring event within the scoring area 1801 and the reference direction to within +/- 3 degrees. From 2010, flow diagram 2000 may continue with 2015.
  • the computer 1810 may identify unambiguous, one-to-one pairings between scoring events and weapon firing events. For example, where only a single exemplary scoring event that is within both a given time window and a given angular window of an exemplary weapon firing event, there may be an unambiguous, one-to-one pairing between the single scoring event and the weapon firing event and may be removed from further consideration. However if, for example, an exemplary weapon firing is within the time and angular window for two exemplary scoring events, the weapon firing event and the two scoring events may be considered an ambiguous and not removed from further consideration. From 2015, flow diagram 2000 may continue with block 1930 of FIG. 19.
  • FIGS. 21 A and 21B depict an exemplary process by which a position-calculated angle may be determined.
  • FIG. 21A depicts front view of an exemplary TIU 2100 including the scoring area 2101 which is attached to a lifter 2104 as well as a target 2102 and a suppression zone 2103.
  • a sensor 2106 may be located in front of scoring area 2101.
  • the scoring area 2101, lifter 2104, and sensor 2106 may be coupled electrically, wired, wirelessly, physically and/or mechanically, including via a communications link (directly, or indirectly) to the TIU 2108
  • FIG. 21B depicts a top view of exemplary scoring area 2101, lifter 2104, sensor 2106, and TIU 2108.
  • FIG. 21B also shows the reference plane 2118 (e.g. true north) as well as the position 2120 of an exemplary weapon 2114 associated with an exemplary weapon firing event and the position 2116 (represented by, for example, but not limited to the center of the scoring area 2101) of the scoring area 2101.
  • the computer 1810 may "draw" a reference line 2110 between the weapon position 2120 and the scoring area 2101 position 2116.
  • the computer may
  • FIG. 22 depicts an exemplary method 2200 by which an exemplary embodiment of block 1935 may correlate unambiguous, one-to-one pairings among remaining scoring events and weapon firing events from individual weapons.
  • block 1935 may be used to identify burst shots. Burst shots may be, for example, two or more shots fired at the same target 1802, by the same weapon, within a short period of time. Block 1935 may also be used to identify two or more shots fired by the same weapon within several milliseconds to approximately .5 from one another. Thus, block 1935 may assume the location of the weapon has not changed significantly between shots. Since the location between the two or more shots is substantially the same, location determination accuracy no longer impacts the TOF variations for the projectile and, therefore, the time window may be decreased.
  • the computer 1810 may identify an unresolved scoring event which has two or more unresolved weapon firing events within the time window and angular window associated with the unresolved scoring event.
  • the two or more weapon firing events may originate from one or more weapons 1814A, 1814B.
  • flow diagram 2200 may continue with 2210.
  • the computer 1810 may identify a weapon 1814A, 1814B, from which the first weapon firing event originated, within the applicable time and angular window. From 2210, flow diagram 2200 may continue with 2215.
  • the computer 1810 may identify all resolved scoring events which have been matched with weapon firing events from the identified weapon 1814A, 1814B.
  • the computer 1810 may also identify a subset of all the relevant, resolved scoring events from a period of time before/after the unresolved scoring event (such as, e.g., but not limited to, +/- 1 second, a 1/2 second, or 1/10 of a second from the unresolved scoring event).
  • the relevant, resolved scoring events, along with the first unresolved scoring event may be arranged chronologically and the time between the events may be calculated. From 2215, flow diagram 2200 may continue from 2220.
  • the computer 1810 may identify all resolved and unresolved firing events from the identified weapon.
  • the computer 1810 may also take a subset of the resolved and
  • the computer 1810 may compare the temporal spacing of the scoring events identified in block 2220 with the firing events of 2215. If the unresolved scoring event aligns, with TOF variations window, with an unresolved firing event from the identified weapon and no other firing events are within that window, the computer 1810 proceeds to block 2230, if the two events do not align, the process continues to block 2235.
  • the two events are matched and. marked as resolved.
  • the first weapon event of block 2210 and the unresolved firing event of block 2220 may be burst shots from the same weapon. The process may then continue to 2235.
  • the process may identify a next weapon, from which a next firing event originated, within the applicable time and angular window, and proceed to block 2220.
  • blocks 2220 through 2230 may be repeated for each weapon firing event which originated within the applicable time and angular window of the scoring event until a match is found or no more weapon firing events are available. If a next weapon is not identified, the process may continue to block 2240.
  • the computer 1810 may identify a next unresolved scoring event which may have a group of two or more unresolved weapon firing events within its time window and angular window and may proceed to block 2210.
  • blocks 2210-2230 may be repeated for all remaining unresolved scoring events which have a group of two or more unresolved weapon firing events within its time window and angular window.
  • FIG. 23 illustrates an exemplary process by which weapon firing events from multiple weapons may be correlated with multiple scoring events.
  • FIG. 23 will be described in connection with FIGS. 18-22.
  • the computer 1810 may receive exercise parameters. These parameters may include one or of the parameters discussed in block 1910 of FIG. 19. From block 1910, the flow diagram 1900 may continue to block 1915.
  • the computer 1810 may access and organize scoring event data 2302. See block 1915 of FIG. 19.
  • the scoring event data 2302 may comprise eleven scoring events SEISE 11 gathered from a TIU 1808, of FIG. 18, which is coupled to target 1802. From block 1915, flow diagram 1900 may continue to block 1920.
  • the computer 1810 may then access and organize weapon firing event data 2304, 2306 from weapon 1812A and 1812B of FIG. 19.
  • Weapon firing event data from weapon 1812A 2304 may be comprised of seven weapon firing events WFE1A- WFE7A.
  • Weapon firing event data 2306 from weapon 1812B may be comprised of eight weapon firing events WFE1B-WFE9B.
  • the flow diagram 1900 may continue to block 1925.
  • the computer 1810 may compare scoring events SE1-SE11 and weapon firing events WFE1A-WFE7A and WFE1B-WFE9B in order to identify unambiguous matches based on a given time and angular window. For example, the computer 1810 may identify the following unambiguous matches based on a first time and first angular window: SEl and WFE1A; SE2 and WFE1B; SE4 and WFE3B; and SE8 and WFE5A. From block 1925, the flow diagram 1900 may continue to block 1930.
  • the computer 1810 may then compare the remaining scoring events SE3, SE5-SE7, and SE9-SE11 and the remaining weapon firing events WFE2A-WFE4A, WFE6A, WFE7A, WFE2B, and WFE4B-WFE9B in order to identify additional unambiguous matches based on the first time and the first angular window. See block 1930 in FIG. 19.
  • the computer 1810 may identify the following unambiguous matches based on the first time and the first angular window: SE3 and WFE2B; and SEl 1 and WFE7B. From block 1930, the flow diagram 1900 may continue to 1935.
  • the computer may correlate unambiguous, one-to-one pairings among remaining scoring events and weapon firing events from individual weapons according to blocks 2205 - 2240 of flow diagram 2200 of FIG. 22.
  • the computer may identify unresolved scoring event SE9 with two or more unresolved weapon firing events WFE6A and WFE7A within a given time window and angular window. From block 2205, the flow diagram 2200 may continue to 2210.
  • the computer 1810 may identify weapon 1812A as being associated with
  • the computer may identify resolved scoring events SE8, which has been matched to weapon firing events WFE5A from weapon 1812A, as the only resolved scoring event within a period of time before/after the unresolved scoring event SE9.
  • the computer 1810 may also calculate the time between the unresolved scoring event SE9 and the resolved scoring event SE8. From block 2215, the flow diagram 2200 may continue to 2220.
  • the computer 1810 may identify WFE4A-WFE7A as all of the resolved and unresolved weapon firing events from weapon 1812A that are within a period of time of unresolved scoring event SE9. The computer 1810 may also calculate the time between each weapon firing event. From block 2220, the flow diagram 2200 may continue to 2220.
  • the computer 1810 may compare the resolved scoring event SE8 as well as unresolved scoring event SE9 to the resolved and unresolved weapon firing events WFE4A- WFE7A. Based on the temporal spacing of scoring events SE8, and SE9 with firing events WFE4A-WFE7A, the computer 1810 may determine that SE9 unambiguously matches WFE6A. SE9 and WFE6A may be matched in block 2230 and the flow diagram 2200 may continue to 2235.
  • computer 1810 may repeat blocks 2220-2230 and unambiguously match
  • computer 1810 may repeat blocks 2205-2235 in an attempt to resolve unresolved scoring events SE5-SE7. For example, the computer 1810 may be unable to make any additional correlations. From block 2240, the flow diagram 2200 may continue to block 1940 of flow diagram 1900 in FIG.19.
  • the computer 1810 may attempt to correlate the remaining unresolved scoring events SE5-SE7 and SE12 with the remaining unresolved weapon firing events WFE2A-WFE4A, WFE4B-WFE6B, WFE8B, and WFE9B and identify additional unambiguous, one-to-one pairings, similar to block 1925 above. For example, the computer 1810 may determine that SE12 and WFE9B unambiguously match based on the first time and the first angular window. From block 1940, the flow diagram 1900 may continue to 1945.
  • the computer 1810 may associate a second time window and a second angular window with SE5, which are both smaller than the first time window and the first angular window, and successfully correlate and mark as resolved SE6 and WFE3A as an
  • the process may identify unresolved weapon firing events WFE6B and
  • WFE4A which are within the second time window and the second angular window associated with unresolved scoring events SE6 and SE7.
  • SE6 and WFE6B as well as SE7 and WFE4A may then be arbitrarily resolved and/or recorded separately. From block 1950, the flow diagram 1900 may continue to 1955.
  • the process may identify and mark each remaining weapon firing events
  • WFE2A, WFE4B, WFE5B, and WFE8B which are not within the time window and angular window associated with any scoring event (i.e. not even an unresolved ambiguous pairing) as a "No Score" in the weapon firing event data 2304, 2306. From block 1955, the flow diagram 1900 may continue to block 1960 where it may end.
  • the accuracy of the exemplary method may be impacted by the number of near coincident shots from shooters at nearly the some position and at the same scoring area 1801.
  • the probability of coincident shots is highest when multiple shooters are firing automatic weapons at a single scoring area 1801.
  • FIG. 24 depicts diagram illustrating an exemplary computer system 2400 such as may be used in, or in combination with devices 1801-1804, 1806, 1808, 1810, 1812A, 1812B, 1814A, and 1814B, etc. and that may be used in implementing an exemplary embodiment of the present invention.
  • FIG. 24 depicts an exemplary embodiment of a computer system 2400 that may be used in computing devices such as, e.g., but not limited to, a client and/or a server, etc., according to an exemplary embodiment of the present invention.
  • the present invention may be implemented using hardware, software, firmware, and/or a combination thereof and may be implemented in one or more computer systems 2400 or other processing systems. In fact, in one exemplary embodiment, the invention may be directed toward one or more computer systems capable of carrying out the functionality described herein.
  • An example of a computer system 2400 is shown in FIG. 24, depicting an exemplary embodiment of a block diagram of an exemplary computer system 2400 useful for
  • FIG. 24 illustrates an example computer 2400, which in an exemplary embodiment may be, e.g., but not limited to, a personal computer (PC) system running an operating system such as, e.g., (but not limited to) MICROSOFT® WINDOWS® NT/98/2000/XP/CE/ME/VISTA/etc. available from MICROSOFT® Corporation of Redmond, WA, U.S.A.
  • an Apple computer executing MAC OS such as, e.g., but not limited to, an Apple computer executing MAC OS.
  • the present invention may be implemented on a computer system operating as discussed herein.
  • An exemplary computer system, computer 2400 is shown in FIG. 24.
  • Other exemplary computer systems may include additional components, such as, e.g., but not limited to, a computing device, a communications device, mobile phone, a telephony device, an iPhone (available from Apple of Cupertine, CA USA), a 3G wireless device, a wireless device, a telephone, a personal digital assistant (PDA), a personal computer (PC), a handheld device, a portable device, an interactive television device (iTV), a digital video recorder (DVD), client workstations, thin clients, thick clients, fat clients, proxy servers, network communication servers, remote access devices, client computers, server computers, peer-to-peer devices, routers, gateways, web servers, data, media, audio, video, telephony or streaming technology servers, game consoles, content delivery systems, etc., may also be implemented using a computer such as that shown in FIG.
  • services may be provided on demand using, e.g., but not limited to, an interactive television device (iTV), a video on demand system (VOD), via a digital video recorder (DVR), and/or other on demand viewing system.
  • iTV interactive television device
  • VOD video on demand system
  • DVR digital video recorder
  • the computer system 2400 may include one or more processors, such as, e.g., but not limited to, processor(s) 2404.
  • the processor(s) 2404 may be coupled to and/or connected to a communication infrastructure 2406 (e.g., but not limited to, a communications bus, cross-over bar, or network, etc.).
  • a communication infrastructure 2406 e.g., but not limited to, a communications bus, cross-over bar, or network, etc.
  • Various exemplary embodiments may be described in terms of this exemplary computer system 2400. After reading this description, it may become apparent to a person skilled in the relevant art(s) how to implement the invention using other computer systems and/or architectures.
  • Computer system 2400 may include a display interface 2431 that may forward, e.g., but not limited to, graphics, text, and other data, etc., from the communication infrastructure 2406 (or from a frame buffer, etc., not shown) for display on the display unit 2430.
  • a display interface 2431 may forward, e.g., but not limited to, graphics, text, and other data, etc., from the communication infrastructure 2406 (or from a frame buffer, etc., not shown) for display on the display unit 2430.
  • the computer system 2400 may also include, e.g., but may not be limited to, a main memory 2408, random access memory (RAM), and a secondary memory 2410, etc.
  • the secondary memory 2410 may include a computer readable medium such as, for example, (but not limited to) a hard disk drive 2412 and/or a removable storage drive 2414, representing a floppy diskette drive, a magnetic tape drive, an optical disk drive, magneto-optical, a compact disk drive CD-ROM, etc.
  • the removable storage drive 2414 may, e.g., but not limited to, read from and/or write to a removable storage unit 2418 in a well known manner.
  • Removable storage unit 2418 also called a program storage device or a computer program product, may represent, e.g., but not limited to, a floppy disk, magnetic tape, optical disk, compact disk, etc. which may be read from and written to by removable storage drive 2414.
  • the removable storage unit 2418 may include a computer usable storage medium having stored therein computer software and/or data.
  • a "machine- accessible medium" may refer to any storage device used for storing data accessible by a computer.
  • Examples of a machine-accessible medium may include, e.g., but not limited to: a magnetic hard disk; a floppy disk; an optical disk, like a compact disk read-only memory (CD- ROM), flash memory, non-volatile memory, or a digital versatile disk (DVD); digital video recorder disk (DVR); a magnetic tape; and a memory chip, etc.
  • a magnetic hard disk e.g., but not limited to: a magnetic hard disk; a floppy disk; an optical disk, like a compact disk read-only memory (CD- ROM), flash memory, non-volatile memory, or a digital versatile disk (DVD); digital video recorder disk (DVR); a magnetic tape; and a memory chip, etc.
  • secondary memory 2410 may include other similar devices for allowing computer programs or other instructions to be loaded into computer system 2400.
  • Such devices may include, for example, a removable storage unit 2422 and an interface 2420.
  • Examples of such may include a program cartridge and cartridge interface (such as, e.g., but not limited to, those found in video game devices), a removable memory chip (such as, e.g., but not limited to, an erasable programmable read only memory (EPROM), or programmable read only memory (PROM) and associated socket, and other removable storage units 2422 and interfaces 2420, which may allow software and data to be transferred from the removable storage unit 2422 to computer system 2400.
  • EPROM erasable programmable read only memory
  • PROM programmable read only memory
  • Computer 2400 may also include an input device such as, e.g., (but not limited to) a mouse 2406 or other pointing device such as a digitizer, an audio capture device 2428 (such as,
  • Attorney Docket No.: 13346-286631 e.g., but not limited to, a microphone
  • an image video/visual capture device 2432 such as, e.g., but not limited to, a camera
  • a keyboard 2405 and/or other data entry device not shown
  • Computer 2400 may also include output devices, such as, e.g., (but not limited to) display 2430, display interface 2431, and/or a speaker 2407, etc. Other output devices may also be used, including, e.g., but not limited to, a printer, etc.
  • Computer 2400 may include input/output (I/O) devices such as, e.g., (but not limited to) communications interface 2424 and communications path 2426, etc. These devices may include, e.g., but not limited to, a network interface card 2402, and modem(s) 2403.
  • Communications interface 2424 may allow software and data to be transferred between computer system 2400 and external devices.
  • computer program medium and “computer readable medium” may be used to generally refer to media such as, e.g., but not limited to removable storage drive 2414, a hard disk installed in hard disk drive 2412, a storage area network (SAN), database, etc.
  • These computer program products may provide software to computer system 2400.
  • the invention may be directed to such computer program products.
  • a computer program product may include software which may be distributed via a communication system and then may be stored on a storage device.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • Physics & Mathematics (AREA)
  • Educational Administration (AREA)
  • Educational Technology (AREA)
  • General Physics & Mathematics (AREA)
  • Aiming, Guidance, Guns With A Light Source, Armor, Camouflage, And Targets (AREA)
  • Radar Systems Or Details Thereof (AREA)

Abstract

La présente invention, selon un exemple de mode de réalisation, porte sur un procédé pour corréler au moins un évènement de tir d'arme à au moins un évènement de marquage de points. Le procédé comprend : la réception d'une information associée à un premier évènement de marquage de points; la réception d'une information associée à un premier évènement de tir d'arme; le calcul d'un angle entre une ligne de référence, s'étendant de l'emplacement du premier évènement d'arme à l'emplacement du premier évènement de marquage de points, et la direction de référence, dans le premier dispositif de calcul; la comparaison du temps du premier évènement de marquage de points au temps de l'évènement du tir d'arme dans le premier dispositif de calcul; la comparaison de l'angle d'incidence pour le projectile à l'angle calculé dans le premier dispositif de calcul; et l'identification du fait que l'évènement de tir d'arme et l'évènement de marquage de points sont un appariement de un à un non ambigu dans le premier dispositif de calcul.
PCT/US2010/039044 2009-06-18 2010-06-17 Procédé et système pour corréler des évènements de tir d'arme à des évènements de marquage de points WO2011041001A1 (fr)

Applications Claiming Priority (6)

Application Number Priority Date Filing Date Title
US12/487,539 US8706440B2 (en) 2009-06-18 2009-06-18 Apparatus, system, method, and computer program product for registering the time and location of weapon firings
US12/487,545 2009-06-18
US12/487,539 2009-06-18
US12/487,545 US8275571B2 (en) 2009-06-18 2009-06-18 Method and system for correlating weapon firing events with scoring events
US12/487,542 2009-06-18
US12/487,542 US8234070B2 (en) 2009-06-18 2009-06-18 Apparatus, system, method, and computer program product for detecting projectiles

Publications (1)

Publication Number Publication Date
WO2011041001A1 true WO2011041001A1 (fr) 2011-04-07

Family

ID=43796426

Family Applications (3)

Application Number Title Priority Date Filing Date
PCT/US2010/039052 WO2011037662A2 (fr) 2009-06-18 2010-06-17 Appareil, système, procédé et produit programme d'ordinateur pour la détection de projectiles
PCT/US2010/039044 WO2011041001A1 (fr) 2009-06-18 2010-06-17 Procédé et système pour corréler des évènements de tir d'arme à des évènements de marquage de points
PCT/US2010/039049 WO2011037661A2 (fr) 2009-06-18 2010-06-17 Appareil, système, procédé et produit programme d'ordinateur permettant d'enregistrer les données spatio-temporelles de tirs d'armes

Family Applications Before (1)

Application Number Title Priority Date Filing Date
PCT/US2010/039052 WO2011037662A2 (fr) 2009-06-18 2010-06-17 Appareil, système, procédé et produit programme d'ordinateur pour la détection de projectiles

Family Applications After (1)

Application Number Title Priority Date Filing Date
PCT/US2010/039049 WO2011037661A2 (fr) 2009-06-18 2010-06-17 Appareil, système, procédé et produit programme d'ordinateur permettant d'enregistrer les données spatio-temporelles de tirs d'armes

Country Status (1)

Country Link
WO (3) WO2011037662A2 (fr)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103047982B (zh) * 2013-01-07 2015-05-13 哈尔滨工业大学 基于角度信息的目标自适应跟踪方法
AU2021350391A1 (en) * 2020-09-24 2023-04-06 Fraunhofer-Gesellschaft zur Förderung der angewandten Forschung e. V. Combat training system
GB2610604A (en) * 2021-09-10 2023-03-15 Cervus Defence And Security Ltd Methods and systems for live fire analysis

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6549872B2 (en) * 2000-10-13 2003-04-15 Stn Atlas Electronik Gmbh Method and apparatus for firing simulation
US20030136900A1 (en) * 1997-08-25 2003-07-24 Motti Shechter Network-linked laser target firearm training system
US6669477B2 (en) * 2001-04-20 2003-12-30 The United States Of America As Represented By The Secretary Of The Navy System and method for scoring supersonic aerial projectiles
US20080167835A1 (en) * 2004-06-10 2008-07-10 Bae Systems Information And Electronic Systems Intergration Inc. Method and Apparatus for Detecting Sources of Projectiles

Family Cites Families (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5577733A (en) * 1994-04-08 1996-11-26 Downing; Dennis L. Targeting system
US6109614A (en) * 1996-07-19 2000-08-29 Tardis Systems, Inc. Remote sensing apparatus of supersonic projectile
US6415211B1 (en) * 2000-06-09 2002-07-02 The United States Of America As Represented By The Secretary Of The Navy Weapon and launcher test set (WALT)
US20030082502A1 (en) * 2001-10-29 2003-05-01 Stender H. Robert Digital target spotting system
FI111659B (fi) * 2002-01-17 2003-08-29 Honestas Oy Maalitaululaitteisto
US7509766B2 (en) * 2003-02-07 2009-03-31 Eduardo Carlos Vasquez Weapon use tracking and signaling system
US7233545B2 (en) * 2004-09-08 2007-06-19 Mcginn-Harvey Holdings, Llc System and method for determining the location of an acoustic event
US7335026B2 (en) * 2004-10-12 2008-02-26 Telerobotics Corp. Video surveillance system and method
EP1875151A4 (fr) * 2005-04-11 2011-11-09 Bruce Hodge Procede et appareil permettant de determiner et de recuperer des informations de position
US7581497B2 (en) * 2005-09-21 2009-09-01 The United States Of America As Represented By The Secretary Of The Navy Self-contained, non-intrusive data acquisition in ammunition
US7614333B2 (en) * 2007-05-24 2009-11-10 Recon/Optical, Inc. Rounds counter remotely located from gun

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030136900A1 (en) * 1997-08-25 2003-07-24 Motti Shechter Network-linked laser target firearm training system
US6549872B2 (en) * 2000-10-13 2003-04-15 Stn Atlas Electronik Gmbh Method and apparatus for firing simulation
US6669477B2 (en) * 2001-04-20 2003-12-30 The United States Of America As Represented By The Secretary Of The Navy System and method for scoring supersonic aerial projectiles
US20080167835A1 (en) * 2004-06-10 2008-07-10 Bae Systems Information And Electronic Systems Intergration Inc. Method and Apparatus for Detecting Sources of Projectiles

Also Published As

Publication number Publication date
WO2011037661A2 (fr) 2011-03-31
WO2011037661A3 (fr) 2011-05-26
WO2011037662A3 (fr) 2011-07-28
WO2011037662A2 (fr) 2011-03-31

Similar Documents

Publication Publication Date Title
US8706440B2 (en) Apparatus, system, method, and computer program product for registering the time and location of weapon firings
US8234070B2 (en) Apparatus, system, method, and computer program product for detecting projectiles
US8826575B2 (en) Self calibrating weapon shot counter
US9022785B2 (en) Monitoring shots of firearms
US20150285593A1 (en) Monitoring shots of firearms
US9612092B2 (en) Portable target shooting system with sensors and remote control
US9250035B2 (en) Precision aiming system for a weapon
US20160091285A1 (en) Portable, wireless electronic target devices, systems and methods
US20160209173A1 (en) Monitoring shots of firearms
US20160258722A9 (en) Wireless target systems and methods
CN106440948A (zh) 一种射击训练系统及射击训练方法
US20190293375A1 (en) A Device for Monitoring Firearms Use
CN103913095B (zh) 枪械记录跟踪方法与装置
US11835311B2 (en) Devices, systems, and computer program products for detecting gunshots and related methods
US11719511B2 (en) Apparatus and methods for detection of a shot firing event
WO2011041001A1 (fr) Procédé et système pour corréler des évènements de tir d'arme à des évènements de marquage de points
KR101551698B1 (ko) 다수 총기 무선사격 시뮬레이션 시스템
CN116067234A (zh) 一种基于线性霍尔技术的自动报靶系统和方法
US8275571B2 (en) Method and system for correlating weapon firing events with scoring events
AU2020225664A1 (en) Device and method for shot analysis
AU2019363145A1 (en) Device and method for shot analysis
CN209978711U (zh) 一种影像射击训练系统
CN116608728A (zh) 一种子弹计数装置、方法及设备
KR101229862B1 (ko) 대인탄 모의 화기에 의한 피해를 모의하는 레이저 감지 장치 및 그 제어 방법
CN114909947A (zh) 基于lora物联网的步枪射击子弹计数方法和装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 10820967

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 10820967

Country of ref document: EP

Kind code of ref document: A1