The present invention relates generally to the field of firearm shooting ranges, and more particularly to a system for detecting strikes or hits to a target and/or a target carrier and for providing remote information responsive to the strikes.
In range shooting, it is important to provide multiple different scenarios to train a shooter (often a soldier or law enforcement officer) to react properly in a number of different situations—thereby protecting both the trainee and the public at large. Target equipment, such as target retrievers, are installed on the ranges to give versatility in training and ease in placing and returning a target. Target retrievers and the like are typically expensive to install and maintain. An inaccurate shooter can cause a retriever to be out of sync with other retrievers and can even do significant damage to a target retriever that may be costly to repair. Further, servicing a target system can typically only be done after closing or when the rest of the range is shut down, due to the danger of entering a range while shooters are active. Thus, it is beneficial if the target equipment and system requires very little servicing.
It can also be difficult to determine which shooter hit the equipment. Even the actual shooter may not know that they hit the target retriever, etc. One current method for detecting whether a target retriever has been hit is for a range worker to spray paint the target retriever prior to each use, and then manually inspect the target retriever after each shooter to determine if any spray paint has been removed by a bullet hit. This can be time consuming and difficult. Additionally, this method does not determine if the hit came from the shooter in the lane of the specific target retriever, or if it came from a shooter on another lane. Accordingly, there is a need to provide an improved method of detecting whether a target carrier has been hit. There is also a need to protect the target carrier from further damage if multiple hits are sustained. It is also beneficial if target systems are programmable to automatically protect the target carrier.
It may also be difficult for a shooter to determine if, during the shooting scenario, they have correctly hit the target which was presented. For example, if the target is downrange several yards, it may be difficult for the shooter to have a visual indication of where, or even if, the shooter hit the target. Thus, there is a need to provide a shooter with a real-time visual indication of a target.
The present invention relates to systems and methods for detecting strikes to a target carrier and taking protective measures in response to such strikes. In one embodiment, the system comprises a target carrier, the target carrier having a sensor disposed thereon. The sensor may be in communication with a controller, and the controller may be in control of and/or in communication with the necessary equipment on the carrier to effectuate a response or corrective measure when the sensor detects a strike to the target carrier.
The present invention also relates to a camera system onboard a target carrier. According to one aspect, the camera may be mounted to the target carrier behind a bullet proof steel plate. A piece of rubber or other impact-absorbing material may be placed between the camera and the steel plate to absorb impacts and dampen vibrational energy. According to another configuration, the camera may be provided with a bulletproof case.
In another configuration, the camera may be directed at an angle to view a target carried by the target carrier. The camera may be in communication with a controller to transmit the image of the target in real time to a screen located near the shooter and/or located in a control room. In some configurations, the camera image may be provided with keystone correction. According to another aspect, the camera may be provided with a tilt-shift lens.
According to one configuration, the controller may be in communication with a target carrier motor such that the target carrier may be sent to a “home” position in response to a strike signal received at the controller from the sensor. According to another configuration, the controller may be in communication with a target actuator such that the target may be turned 90 degrees (or placed on edge with respect to a shooter) in response to a strike signal received at the controller from the sensor.
According to another aspect, the sensor may be in communication with a range server such that a range operator is alerted when the sensor detects a strike to the target carrier.
According to another aspect, the system may further comprise a shooter interface that alerts the shooter when the sensor detects a strike to the target carrier.
According to another aspect, the system may comprise a range controller interface which may allow a range operator to select default settings for corrective actions to be taken when a predetermined threshold of strike signals are generated by the sensor, and/or select custom settings for an individual shooter.
According to another aspect, the system may be implemented on a single target carrier without connection to a range server and/or range network. The controller of the target carrier may implement corrective measures in response to a strike signal received from the sensor.
According to yet another aspect, any suitable sensor may be used. In some configurations, more than one sensor and/or more than one type of sensor may be used. For example, the sensor(s) may comprise one or more of an accelerometer, a piezo electric sensor, a microphone, a thermocouple, and a strain gauge sensor.
A method is also described herein to sense hits to a target carrier, and take corrective measures after a predetermined number of hits are detected. Such corrective measures may include actuating a carrier motor to move the carrier to a home position, edging or otherwise altering the position of a target held by the carrier, changing the lighting on the lane of the carrier, sending a signal to the shooter's user interface, and/or sending a signal to the range operator.
The following drawings illustrate what are currently considered to be specific representative configurations for carrying out the invention and are not limiting as to embodiments which may be made in accordance with the present invention. The components in the drawings are not necessarily to scale relative to each other. Like reference numerals designate corresponding parts throughout the several views.
The drawings are illustrative and not limiting of the scope of the invention which is defined by the appended claims. The various elements of the invention accomplish various aspects and objects of the invention. Not every element of the invention can be clearly displayed in a single drawing, and as such not every drawing shows each element of the invention.
It should be appreciated by those skilled in the art that any block diagrams herein represent conceptual views of illustrative systems embodying the principles of the present subject matter. Similarly, it will be appreciated that any flow charts, flow diagrams, state transition diagrams, pseudo code, and the like represent various processes which may be substantially represented in computer readable medium and so executed by a computer or processor, whether or not such computer or processor is explicitly shown.
The following provides a detailed description of particular embodiments of the present invention. Reference will now be made to the drawings in which the various elements of the illustrated configurations will be given numerical designations and in which the invention will be discussed so as to enable one skilled in the art to make and use the invention. It is to be understood that the following description is only exemplary of the principles of the present invention, and should not be viewed as narrowing the scope of the claims which follow, which claims define the full scope of the invention.
It will be appreciated that various aspects discussed in one drawing may be present and/or used in conjunction with the embodiment shown in another drawing, and each element shown in multiple drawings may be discussed only once. For example, in some cases, detailed description of well-known items or repeated description of substantially the same configurations may be omitted. The reason is to facilitate the understanding of those skilled in the art by avoiding the following description from being unnecessarily redundant. The accompanying drawings and the following description are provided in order for those skilled in the art to fully understand the present disclosure, and these are not intended to limit the gist disclosed in the scope of claims.
For a firmware, and/or software implementation of the target carrier strike detection system described herein, the methodologies can be implemented with modules (e.g., procedures, functions, and so on) that perform the functions described herein. Any machine readable medium tangibly embodying instructions can be used in implementing the methodologies described herein. For example, software codes and programs can be stored in a memory and executed by a processing unit. Memory can be implemented within the processing unit or may be external to the processing unit. As used herein the term “memory” refers to any type of long term, short term, volatile, nonvolatile, or other storage devices and is not to be limited to any particular type of memory or number of memories, or type of media upon which memory is stored.
In another firmware and/or software implementation, the functions may be stored as one or more instructions or code on a non-transitory computer-readable medium. Examples include computer-readable media encoded with a data structure and computer- readable media encoded with a computer program. Computer-readable media may take the form of an article of manufacturer. Computer-readable media includes physical computer storage media. A storage medium may be any available medium that can be accessed by a computer. By way of example, and not limitation, such computer-readable media can comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage, flash memory, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to store reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above should also be included within the scope of computer-readable media.
In addition to storage on computer readable medium, instructions and/or data may be provided as signals on transmission media included in a communication apparatus. For example, a communication apparatus may include a transceiver having signals indicative of instructions and data. The instructions and data are configured to cause one or more processors to implement the functions outlined in the claims. That is, the communication apparatus includes transmission media with signals indicative of information to perform disclosed functions. At a first time, the transmission media included in the communication apparatus may include a first portion of the information to perform the disclosed functions, while at a second time the transmission media included in the communication apparatus may include a second portion of the information to perform the disclosed functions.
It should be noted that the description merely illustrates the principles of the present subject matter. It will thus be appreciated that those skilled in the art will be able to devise various arrangements that, although not explicitly described herein, embody the principles of the present subject matter and are included within its spirit and scope. Furthermore, all examples recited herein are principally intended expressly to be only for pedagogical purposes to aid the reader in understanding the principles of the invention and the concepts contributed by the inventor(s) to furthering the art, and are to be construed as being without limitation to such specifically recited examples and conditions. Moreover, all statements herein reciting principles, aspects, and embodiments of the invention, as well as specific examples thereof, are intended to encompass equivalents thereof.
The present disclosure generally relates to a system including a carrier having one or more sensors that allow a hit or strike to the carrier to be detected. The system may automatically indicate if a hit has occurred and take further action (such as edging the target and/or returning the carrier to the home position). As used herein, the term “carrier” is used to refer to any type of target carrier, such as a target retriever, runner, or the like.
The following provides a detailed description of a single target carrier provided with one or more hit detection sensors. It is understood, however, that two or more carriers may be used together to provide a plurality of carriers with hit detection to be used on a shooting range with multiple lanes. Typically, one target carrier will be provided for each lane of a shooting range.
The functions of the various elements shown in the figures, including any functional blocks labeled as “controller(s),” may be provided through the use of dedicated hardware as well as hardware capable of executing software in association with appropriate software. When provided by a controller, the functions may be provided by a single dedicated controller, by a single shared controller, or by a plurality of individual controllers, some of which may be shared. Moreover, explicit use of the term “controller” should not be construed to refer exclusively to hardware capable of executing software, and may implicitly include, without limitation, digital signal processor (DSP) hardware, network processor, application specific integrated circuit (ASIC), field programmable gate array (FPGA), read only memory (ROM) for storing software, random access memory (RAM), non-volatile storage. Other hardware, conventional and/or custom, may also be included.
One particular embodiment of the present disclosure is shown and described in
In the implementation shown in
The sensor 25 may be any suitable sensor known in the art to detect hits directly to the target carrier 20. The sensor 25 may be able to distinguish between motion of the target carrier 20 due to a bullet strike to the target carrier 20 and motion due to other forces (such as motion which may be caused by motor 32 moving the target carrier 20 over a track, motion caused by movement of target actuator 35 and/or motion caused by hits to target 38). This distinguishing can be accomplished, for example, by calibration/tuning of the sensor 25. The carrier 20 may also be equipped with additional sensor(s) at multiple locations to distinguish the cause of motion of the target carrier 20. In one configuration, the sensor 25 is located behind a front plate of the target carrier 20. In another configuration, the sensor 25 is located on the main printed circuit board of the controller 30. Placement of the sensor(s) 25 may depend on the type of sensor(s) used. Suitable sensors include accelerometers, piezo electric sensors, microphones, thermocouples, strain gauge sensors, etc. Any suitable sensor known in the art may be used.
The sensor 25 may be in communication with the controller (for example, as stated above, the sensor 25 may be attached to the main printed circuit board of the controller) either directly or indirectly, and may send a strike signal to the controller when the sensor 25 detects a hit to the target carrier 20. The controller may effect a change to the target 38 in response to the strike signal (or in response to a predetermined threshold of strike signals) received from the sensor 25. As will be discussed in additional detail below, the predetermined threshold may be based on the number of strike signals indicated (i.e. a threshold zero, on, etc., where exceeding the threshold causes the controller to affect a corrective measure). Alternatively, the predetermined threshold may be based on cumulative force sensed. Thus, for example, the target carrier could be hit by several small caliber, low impact rounds (i.e. .22 long rifle) or a glancing blow without surpassing the threshold, while a single direct hit from a .45 bullet or a 30-06 may exceed the predetermined threshold and cause corrective measures to be taken.
The controller may also send a signal to a range server 40 over a network 50 to alert range operators that a target carrier 20 has been hit. The signal sent from the target carrier controller 30 to the range server may include information, for example, the lane number of the carrier, the number of strikes the carrier has received during a particular shooter's session, the shooting scenario selected by the particular shooter, the type of weapon being used, information relating to the particular shooter, etc.
The network 50 connecting the target carrier controller 30, range server 40, and interfaces 42, 48 may be a wireless or a wired network, or a combination thereof. Depending on the technology, the network 50 includes various network entities, such as gateways, routers, etc.; however, such details have been omitted for ease of understanding.
The range server 40 may have one or more controller(s) 45. Like the controller 30 of the target carrier 20, the range server controller(s) 45 may be implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, state machines, logic circuitries, and/or any devices that manipulate signals based on operational instructions. Among other capabilities, the range server controller(s) 45 may be configured to fetch and execute computer-readable instructions stored in the memory. Such instructions may include, for example, instructions to send a signal to a target carrier controller 30 to move the target carrier 20 to a home position after one or more strike signals are received at the range server 40, and/or send a signal to a target carrier controller 30 to move a target 38 to present the edge to the shooter so that the target face is no longer visible after one or more strikes signals are received at the range server 40. It will be appreciated that instructions to send the target carrier 20 to a home position and/or edge the target 38 could be affected either by the controller 30 in the target carrier 20, or by a signal from the range server 40 to the controller 30 in the target carrier 20.
The range server 40 may also comprise a corrective measures module 47 in communication with the controller 45. The corrective measures module 47 may allow range operators to set default corrective measures and/or set unique corrective measures for a particular user.
As explained above, the target carrier 20, may receive a hit as detected by one or more sensors 25 that results in a corrective measure being taken to address a detected strike to the target carrier 20. This may be a user-selectable option by the range operator(s), and may be modified based on user selectable options. Selection of such options may be provided to the range operator(s) via a menu or other graphical user interface 48 to modify and/or program the corrective measures module 47. For example, the range operator(s) may select to allow only one strike to a carrier before a corrective measure is taken, such as placing the target on edge. Alternatively, the range operator(s) may select to allow multiple hits or may select to turn off the option to automatically take corrective measure when the target carrier is hit. Other options include sending a warning to the shooter interface 42 when the target carrier 20 is hit. A default may be set, for example, to take corrective measures after two strikes are detected. Subsequent unique settings for an individual shooter may be changed from the default by the range operator(s). In use the sensors may be configured to estimate the location of the shooter who impacted the target. In some scenarios, the shooter hitting the target carrier 20 may be the shooter in the lane in which the target carrier is operating. One or more strikes may indicate that the shooter is shooting carelessly and is likely to damage or cause excessive wear to the target carrier. Thus, the shooter interface 42 may display a message to the shooter that he or she has struck the target carrier too many times and that the shooter's session had ended. The sensors 25, however, may detect that the impact is coming from a bullet traveling at an angle to the target carrier 20 inconsistent with being fired in the same lane. By determining the location of the target carrier and the direction at which the force impacts the target carrier 20, the system can determine which shooter is likely responsible. For example, the seniors 25 on the target carrier 20 in lane 3 may detect an impact which, when considering the location of the target carrier and the direction of force indicates that the bullet hitting the target carrier actually came from the shooter in lane 1. The shooter interface on claim 1 may then flash a warning to the shooter in that lane that the session with be terminated if the shooter is responsible for another strike to one of the target carriers. Additionally, the same sensors 25 can detect the force of the hit so that the controllers 30/45 may determine whether it is advisable to turn off the target carrier, or simply mark the target carrier for inspection at the end of the day.
According to an implementation of the present disclosure, each of the carriers 20 may be connected to one system 10. However, in another implementation, each of the carriers 20 may include an individual system 10 capable of controlling the target actuator and/or motor of the carrier, etc. associated with that carrier.
Turning now to
As the shooter proceeds, if the target carrier 20 is struck by a bullet, the processor may receive a signal from the sensor 25 that a strike has occurred. In some configurations, a single strike may cause the controller 30 to take corrective measures, such as by sending the target to the “home” position as shown in
As seen in
Turning now to
After a start 105, the system may move the target carrier to a first, presented position 110 or through a training scenario, etc. The sensor 25 may check for strikes to the target carrier 115. The sensor may perform this check nearly continuously, such as every 0.01 seconds, or as often as desired. It will be appreciated that the logic of the sensor may be programmed to perform this check as often as desired. The sensor then determines if it has detected a hit to the target carrier (120). Where no hit is detected, the sensor may loop to 115 and check again to detect a strike to the target carrier. The loop of checking for strikes and determining if a strike is detected (115, 120) may repeat continuously until the sensor detects a hit to the target carrier. Alternatively, controllers could be passive and only respond to a signal generated by the sensors when impacted by a bullet.
When the sensor detects a hit to the target carrier, the sensor may then send a strike signal from the sensor to the controller (125). The number of strikes signals may be incremented by one (130). The controller may determine if the number of strike signals is less than the predetermined maximum (135). As stated above, the system may have a default setting that allows, for example, three strike signals before corrective measures are taken. Or, a custom setting may be selected (for example, at the range server a custom setting may be selected for a particular shooter). When the number of strike signals is less than the maximum, the system may return to the loop 115, 120. When the number of strike signals is equal to or greater than the maximum, corrective measures may be taken (140).
The sensors 25 may also be able to detect the magnitude of the strike and use the magnitude of the impact in the calculation as well. For example, a 30-06 bullet will impact the target carrier with far greater force than will a .22 bullet at the same distance due both to the mass of the bullet and the velocity at which it travels for most common rounds. A target carrier we may be hit by 10 rounds fired from a .22 without concern, while a single impact from a 30-06 or more powerful round may suggest deactivating the target carrier until it can be inspected.
Exemplary corrective measures may be sending the target carrier 20 to a home position (such as at either the near end or far end of a track), placing the target 38 on edge so it is no longer presented, sending a signal to the range server 40, sending a message to the shooter interface 42, etc. It will be appreciated that the system may be programmed to have one or more default corrective measures happen at the same time or in a particular order, and/or the system may be programmable by a person in charge of the range to customize the corrective measures for a particular shooter.
Turning now to
Similarly,
Various embodiments described also can be practiced without some of the specific details described herein, or with other specific details, such as changes with respect to the ordering of the code flow shown in the figures, different code flows, and the like. Thus, the scope of the techniques and/or functions described are not limited by the particular order, selection, or decomposition of steps described with reference to any particular module, component, or routine.
As mentioned above, in some configurations, the system may be programmed to not only detect a hit or no hit, but the relative force of the hit, and take appropriate corrective steps. For example, if a shooter was using a low impact round such as .22 long rifle, or the hit is minor because it is only a glancing blow as opposed to a direct hit, the system may only send a message to the shooter, having determined that the hits are unlikely to cause significant damage. Thus, the system may allow a greater number of such low-impact hits. In contrast, if the sensors detect a hit from a larger caliber round (such as a .45 caliber or a high velocity round with substantial inertia), such a detected hit may have enough force to cause the target retriever to shut down even if the predetermined number of hits has not been detected. Additionally, while the number of hits allowed has been discussed as three, the actual number of hits used can be decided by the range based on their use profiles, type of equipment, etc., and may be 1, 2 3, 4, 5, or any other number or a combination of a number and detected force of the impact.
According to another aspect of the present disclosure, the target carrier 20 may comprise an onboard camera 60. As seen in
The camera 60 may be placed at any suitable location on the target carrier 20. In one configuration, the camera is placed behind a steel plate 64 (see
The camera 60 may direct its view towards a target 38 mounted on the target carrier 20. Because the target 38 may typically be located at an angle below camera 60, the camera image output may be provided with keystone correction. Keystone correction may allow the image to be flattened for presentation on a screen as the image would appear if the camera 60 were directly in front of target 38 (instead of located above target 38). In other configurations, the camera 60 may be provided with a tilt-shift lens for optimizing the view of the target 38.
In configurations where the camera 60 is in communication with the target carrier controller 30 (it will be appreciated that the camera 60 may be provided with its own controller or may use the controller of the carrier), the image viewed by the camera 60 may be transmitted in real time to a remote screen. For example, the image may be sent to a screen proximal to a shooter. This may allow the shooter to closely examine the target (which is often several yards away) to see hits to the target.
Additionally, software may be provided which analyzes the visual output of camera 60 to automatically determine if a hit has occurred in a desired area. Such software may also be programmed to send a visual and/or audible alert to the shooter to indicate a hit. For example, when the software determines a hit has occurred, the screen located near the shooter may flash a large message that says “HIT,” and/or provide an auditory signal, such as a beep or chime. Other indicators include flashing the lights on the shooter's lane, etc. Similarly, the software may be able to automatically assign a score to a shooter for a particular shooting scenario. This may simplify training scenarios and make it easier for shooters to identify mistakes made during the scenario.
In another configuration, the camera output may be transmitted to a range server 40 for remote viewing. For example, when the training scenario is for police officers, a training officer in a remote room may have access to the camera images of each target for review and analysis.
While the invention has been described in particular with reference to certain illustrated configurations, such is not intended to limit the scope of the invention. The present invention may be embodied in other specific forms without departing from its spirit or essential characteristics. The described configurations are to be considered as illustrative and not restrictive. The scope of the invention is, therefore, indicated by the appended claims rather than by the foregoing description. All changes which come within the meaning and range of equivalency of the claims are to be embraced within their scope.
Described herein is a system for detecting hits to a target carrier, which may comprise: a carrier, the carrier comprising a sensor to detect a strike to the carrier and send a strike signal to a controller in response to the strike signal; the controller in communication with the sensor and a actuator, the controller configured to actuate the actuator when the controller receives a predetermined number of strike signals from the sensor. The actuator may comprise a target actuator and wherein the target actuator turns a target on edge relative to the shooter when the controller receives the predetermined number of strike signals from the sensor. The system may further comprise a target controlled by the actuator, wherein the target has a first, presented position and a second, non-presented position. The actuator may be configured to move the target from the first, presented position to the second, non-presented position when the controller receives the predetermined number of strike signals from the sensor.
According to another aspect, the actuator may comprise a motor and the motor may move the carrier to a home position when the controller receives the predetermined number of strike signals from the sensor.
In some configurations, the sensor comprises a first sensor and a second sensor. The sensor may comprise one or more of: an accelerometer, a piezo electric sensor, a microphone, a thermocouple, and a strain gauge sensor.
The system may further comprise a shooter interface in communication with the controller, wherein the controller is configured to send a warning message to the shooter interface when the controller receives the strike signal from the sensor. The warning message may comprise one or more of an audible sound and a visual alert.
The system may further comprise a range server in communication with the controller, and wherein the controller is configured to send a warning message to the range server when the controller receives the strike signal from the sensor.
Also described herein is a method for protecting a target carrier from hits to the target carrier, the method may comprise: selecting a carrier, the carrier having a strike sensor located thereon; providing a controller in communication with the carrier and the strike sensor, sensing on the strike sensor a strike to the target carrier, and sending a strike signal from the strike sensor to the controller; and taking at least one corrective measure when the controller receives a predetermined number of strike signals from the strike sensor.
The step of selecting a carrier may comprise selecting a carrier having a target actuator for turning a target between a first, presented position and a second, non-presented position. The method may further comprise the step of incrementing the number of strike signals by one for each strike signal received by the controller, and comparing the number of strike signals to a predetermined number of strike signals.
According to one aspect, the method may include the step of sending a warning message to a range server when the controller receives at least one strike signal from the strike sensor. The method may also include the step of sending a warning message to a user interface when the controller receives at least one strike signal from the strike sensor.
The step of taking at least one corrective measure when the controller receives a predetermined number of strike signals from the strike sensor may comprise actuating the actuator to turn the target from the first, presented position to the second, non-presented position.
The step of selecting a carrier may comprise selecting a carrier having a motor and wherein the step of taking at least one corrective measure when the controller receives a predetermined number of strike signals from the strike sensor comprises actuating the motor to move the carrier to a home position. The method may further comprise the step of providing at least one light for a lane of the carrier and controlling the at least one light with the controller, and also the step of the controller making a change to the at least one light of the lane of the carrier when the controller receives the strike signal from the strike sensor.
The predetermined number of strike signals may be, for example, as low as one. According to other configurations, the predetermined number of strike signals may be 1, 2, 3, 4, 5, etc.
According to another aspect, as shown in
The various embodiments described above can be combined to provide further embodiments. All of the U.S. patents, U.S. patent application publications, U.S. patent applications, foreign patents, foreign patent applications and non-patent publications referred to in this specification and/or listed in the Application Data Sheet are incorporated herein by reference, in their entirety. Aspects of the embodiments can be modified, if necessary, to employ concepts of the various patents, applications and publications to provide yet further embodiments.
These and other changes can be made to the embodiments in light of the above-detailed description. In general, in the following claims, the terms used should not be construed to limit the claims to the specific embodiments disclosed in the specification and the claims, but should be construed to include all possible embodiments along with the full scope of equivalents to which such claims are entitled.
Number | Name | Date | Kind |
---|---|---|---|
157335 | Lyon | Dec 1874 | A |
429942 | McBride | Jun 1890 | A |
483060 | Holm | Sep 1892 | A |
570820 | Scratton | Nov 1896 | A |
631175 | Parnall | Aug 1899 | A |
840610 | Easdale | Jan 1907 | A |
879670 | Petry | Feb 1908 | A |
937733 | Worrell | Oct 1909 | A |
950101 | Green | Feb 1910 | A |
960085 | Giles | May 1910 | A |
960892 | Gates | Jun 1910 | A |
1025944 | Elliott | May 1912 | A |
1036879 | Miner | Aug 1912 | A |
1207456 | Whelan | Dec 1916 | A |
1348283 | Koehl | Aug 1920 | A |
1424632 | Fenton | Aug 1922 | A |
1517461 | Robinson | Aug 1924 | A |
1540802 | Ordway | Jun 1925 | A |
1543605 | Gavard | Jun 1925 | A |
1559171 | Knowles | Oct 1925 | A |
1657931 | Krantz | Jul 1926 | A |
1640954 | Mach | Aug 1927 | A |
1738874 | Domingo | Dec 1929 | A |
1831289 | Dally | Nov 1931 | A |
2048155 | Armantrout | Jan 1935 | A |
2008359 | Lamb | Jul 1935 | A |
2039552 | Reynolds | May 1936 | A |
2085933 | Vaughan | Jul 1937 | A |
2104171 | Schwerin | Jan 1938 | A |
2179471 | Lee | Nov 1939 | A |
2284510 | Cates | May 1942 | A |
2290297 | Smith | Jul 1942 | A |
2344829 | McAvoy | Mar 1944 | A |
2372111 | Norberg | Mar 1945 | A |
2547478 | Lieberman | Jul 1948 | A |
2538118 | Miller | Jun 1949 | A |
2494210 | Robinson | Jan 1950 | A |
2535280 | Gartrell | Dec 1950 | A |
2586958 | Keller | Feb 1952 | A |
2587042 | Haiselup | Feb 1952 | A |
2613934 | Tabler | Oct 1952 | A |
2706634 | Van Valkenburg | Apr 1955 | A |
2809836 | Musser | Oct 1957 | A |
2838309 | Merz et al. | Jun 1958 | A |
2819903 | Saunders | Aug 1958 | A |
2905469 | Taylor | Sep 1959 | A |
2957694 | Barber | Oct 1960 | A |
2967712 | Breitenfeldt | Jan 1961 | A |
3014725 | Lewis | Dec 1961 | A |
3032808 | Fleming | May 1962 | A |
3064976 | Kuhn | Nov 1962 | A |
3087701 | Wallace | Apr 1963 | A |
3103362 | Elofson | Sep 1963 | A |
3113773 | Ripepe | Dec 1963 | A |
3140874 | Jensen et al. | Jul 1964 | A |
3233904 | Gillam et al. | Feb 1966 | A |
3348843 | Stanley | Oct 1967 | A |
3363900 | Cadle | Jan 1968 | A |
3385405 | Cullen | May 1968 | A |
3392980 | Ortega | Jul 1968 | A |
3422538 | Panissidi | Jan 1969 | A |
3471153 | Baumler | Oct 1969 | A |
3510133 | Gretzky | May 1970 | A |
3515388 | Zachmeier | Jun 1970 | A |
3540729 | Rahberger | Nov 1970 | A |
3601353 | Dale | Aug 1971 | A |
3614102 | Nikoden, Sr. | Oct 1971 | A |
3638894 | Leutenegger | Feb 1972 | A |
3720411 | Vogelaere | Mar 1973 | A |
3755942 | Samsing | Sep 1973 | A |
3802098 | Sampson et al. | Apr 1974 | A |
3914879 | Taylor, III | Oct 1975 | A |
3992007 | Seeman | Nov 1976 | A |
4072313 | Murso et al. | Feb 1978 | A |
4076247 | Kim et al. | Feb 1978 | A |
4084299 | Noda | Apr 1978 | A |
4086711 | Gammarino et al. | May 1978 | A |
4129299 | Busch | Dec 1978 | A |
4177835 | Paley | Dec 1979 | A |
4205847 | Steiger et al. | Jun 1980 | A |
4228569 | Snyder | Oct 1980 | A |
4232867 | Tate, Sr. | Nov 1980 | A |
4249743 | Lee | Feb 1981 | A |
4288080 | Laporte et al. | Sep 1981 | A |
4294452 | Schlotter et al. | Oct 1981 | A |
4340370 | Marshall et al. | Jul 1982 | A |
4361330 | Scharer | Nov 1982 | A |
4395045 | Baer | Jul 1983 | A |
4440399 | Smith | Apr 1984 | A |
4501427 | Payne | Feb 1985 | A |
4506416 | Ohminato et al. | Mar 1985 | A |
4540182 | Clement | Sep 1985 | A |
4546984 | Towle et al. | Oct 1985 | A |
4614345 | Doughty | Sep 1986 | A |
4657261 | Saunders | Apr 1987 | A |
4691925 | Scholem | Sep 1987 | A |
4706963 | Geuss | Nov 1987 | A |
4726593 | Wade | Feb 1988 | A |
4739996 | Vedder | Apr 1988 | A |
4743032 | Summers et al. | May 1988 | A |
4807888 | Pidde | Feb 1989 | A |
4844476 | Becker | Jul 1989 | A |
4890847 | Cartee et al. | Jan 1990 | A |
4898391 | Kelly et al. | Feb 1990 | A |
4911453 | Essex et al. | Mar 1990 | A |
4913389 | McCracken | Apr 1990 | A |
4953875 | Sudit | Sep 1990 | A |
4979752 | Fosseen | Dec 1990 | A |
5054723 | Arnold | Oct 1991 | A |
5145133 | France | Sep 1992 | A |
5163689 | Bateman | Nov 1992 | A |
5213336 | Bateman | May 1993 | A |
5232227 | Bateman | Aug 1993 | A |
5240258 | Bateman | Aug 1993 | A |
5242172 | Bateman | Sep 1993 | A |
5257790 | Meadows | Nov 1993 | A |
5263721 | Lowrance | Nov 1993 | A |
5277432 | Bateman | Jan 1994 | A |
5316479 | Wong et al. | May 1994 | A |
5324043 | Estrella | Jun 1994 | A |
5346226 | Block | Sep 1994 | A |
5350180 | Acock | Sep 1994 | A |
5352170 | Condo et al. | Oct 1994 | A |
5361455 | Kiefer | Nov 1994 | A |
5400692 | Bateman | Mar 1995 | A |
5433451 | De Vries | Jul 1995 | A |
5518251 | Liu | May 1996 | A |
5535662 | Bateman | Jul 1996 | A |
5598996 | Rath | Feb 1997 | A |
5605335 | Simpson | Feb 1997 | A |
5618044 | Bateman | Apr 1997 | A |
5621950 | White | Apr 1997 | A |
5636995 | Sharpe, III et al. | Jun 1997 | A |
5641288 | Zaenglein, Jr. | Jun 1997 | A |
5648794 | Jelsma et al. | Jul 1997 | A |
5649706 | Treat, Jr. et al. | Jul 1997 | A |
5676378 | West | Oct 1997 | A |
5695196 | Yanosky | Dec 1997 | A |
5765832 | Huff | Jun 1998 | A |
5802460 | Parvulescu et al. | Sep 1998 | A |
5811718 | Bateman | Sep 1998 | A |
5822936 | Bateman | Oct 1998 | A |
5829753 | Wiser | Nov 1998 | A |
5865439 | Marcuson | Feb 1999 | A |
5906552 | Padilla | May 1999 | A |
5907930 | Ricco | Jun 1999 | A |
5934678 | Theissen et al. | Aug 1999 | A |
5947477 | Turnipseed | Sep 1999 | A |
5950283 | Sato | Sep 1999 | A |
5951016 | Bateman | Sep 1999 | A |
5963624 | Pope | Oct 1999 | A |
5967523 | Brownlee | Oct 1999 | A |
5988645 | Downing | Nov 1999 | A |
6018847 | Lu | Feb 2000 | A |
6109614 | Ciarcia | Aug 2000 | A |
6223029 | Stenman et al. | Apr 2001 | B1 |
6230214 | Liukkonen et al. | May 2001 | B1 |
6283756 | Danckwerth et al. | Sep 2001 | B1 |
6289213 | Flint et al. | Sep 2001 | B1 |
6308062 | Chien et al. | Oct 2001 | B1 |
6311980 | Sovine et al. | Nov 2001 | B1 |
6322444 | Matsui et al. | Nov 2001 | B1 |
6325376 | Elliott et al. | Dec 2001 | B1 |
6328651 | Lebensfeld et al. | Dec 2001 | B1 |
6332243 | Kim | Dec 2001 | B1 |
6378870 | Sovine | Apr 2002 | B1 |
6398215 | Carroll | Jun 2002 | B1 |
6463299 | Macor | Oct 2002 | B1 |
6478301 | Witmeyer | Nov 2002 | B1 |
6484990 | Marshall | Nov 2002 | B1 |
6502820 | Slifko | Jan 2003 | B2 |
6533280 | Sovine et al. | Mar 2003 | B1 |
6543778 | Baker | Apr 2003 | B2 |
6575753 | Rosa et al. | Jun 2003 | B2 |
6588759 | Bateman | Jul 2003 | B1 |
6679795 | Ouimette et al. | Jan 2004 | B2 |
6718596 | Kohlstrand et al. | Apr 2004 | B2 |
6728546 | Peterson et al. | Apr 2004 | B1 |
RE38540 | Bateman | Jun 2004 | E |
6761357 | Witt | Jun 2004 | B2 |
6776418 | Sovine et al. | Aug 2004 | B1 |
6808177 | Dehart | Oct 2004 | B2 |
6808178 | Sovine | Oct 2004 | B1 |
6896267 | Le Anna | May 2005 | B1 |
6975859 | Lambert et al. | Dec 2005 | B1 |
6994347 | Tessel et al. | Feb 2006 | B2 |
6994348 | Lambert et al. | Feb 2006 | B2 |
6994349 | Lambert et al. | Feb 2006 | B2 |
7128321 | Brown | Oct 2006 | B1 |
7134977 | Campbell et al. | Nov 2006 | B2 |
7140615 | Sovine et al. | Nov 2006 | B1 |
7175181 | Bateman et al. | Feb 2007 | B1 |
7194944 | Lambert et al. | Mar 2007 | B2 |
7201376 | Kuosa | Apr 2007 | B2 |
7219897 | Sovine et al. | May 2007 | B2 |
7234890 | Marshall et al. | Jun 2007 | B1 |
7264246 | Sovine et al. | Sep 2007 | B2 |
7275748 | Lambert et al. | Oct 2007 | B2 |
7302768 | Gajdacs | Dec 2007 | B2 |
7303192 | Marshall et al. | Dec 2007 | B2 |
7306230 | Lambert et al. | Dec 2007 | B2 |
7322771 | Marshall et al. | Jan 2008 | B1 |
7427069 | Bateman et al. | Sep 2008 | B2 |
7431302 | Bassett et al. | Oct 2008 | B2 |
7469903 | Marshall et al. | Dec 2008 | B2 |
7497441 | Marshall et al. | Mar 2009 | B2 |
7503250 | Lambert et al. | Mar 2009 | B2 |
7556268 | Bateman et al. | Jul 2009 | B2 |
7653979 | Bateman et al. | Feb 2010 | B2 |
7775526 | Lambert et al. | Aug 2010 | B1 |
7793937 | Bateman et al. | Sep 2010 | B2 |
7815192 | Kreiman et al. | Oct 2010 | B1 |
7914004 | Wright et al. | Mar 2011 | B2 |
7950666 | Stincelli et al. | May 2011 | B2 |
8016291 | Wright et al. | Sep 2011 | B2 |
8091896 | Lambert et al. | Jan 2012 | B2 |
8128094 | Lambert et al. | Mar 2012 | B2 |
8162319 | Stincelli et al. | Apr 2012 | B2 |
8276916 | Bateman et al. | Oct 2012 | B2 |
8469364 | Bassett et al. | Jun 2013 | B2 |
8485529 | Bateman et al. | Jul 2013 | B2 |
8550465 | Wright et al. | Oct 2013 | B2 |
8579294 | Wright et al. | Nov 2013 | B2 |
8684361 | Henson et al. | Apr 2014 | B2 |
8713829 | Crofford | May 2014 | B1 |
8813401 | Diercks | Aug 2014 | B2 |
8827273 | John et al. | Sep 2014 | B2 |
9217623 | Sovine et al. | Dec 2015 | B2 |
9228810 | Bateman et al. | Jan 2016 | B2 |
9574855 | Davis | Feb 2017 | B2 |
9784538 | Sovine et al. | Oct 2017 | B2 |
20050001381 | Lambert et al. | Jan 2005 | A1 |
20050022658 | Bateman | Feb 2005 | A1 |
20050034594 | Parks et al. | Feb 2005 | A1 |
20060107985 | Sovine | May 2006 | A1 |
20060234069 | Sovine et al. | Oct 2006 | A1 |
20060240388 | Marshall et al. | Oct 2006 | A1 |
20060240391 | Sovine et al. | Oct 2006 | A1 |
20060290063 | Hagar | Dec 2006 | A1 |
20060290064 | Hagar | Dec 2006 | A1 |
20070072537 | Bateman et al. | Mar 2007 | A1 |
20070102883 | Parks et al. | May 2007 | A1 |
20080185786 | Loveland et al. | Aug 2008 | A1 |
20080277876 | Riley | Nov 2008 | A1 |
20090014961 | Bateman et al. | Jan 2009 | A1 |
20090206551 | Parks et al. | Aug 2009 | A1 |
20100311015 | Sovine et al. | Dec 2010 | A1 |
20110233869 | John et al. | Sep 2011 | A1 |
20120187631 | John et al. | Jul 2012 | A1 |
20120193872 | Henson et al. | Aug 2012 | A1 |
20120247314 | Bassett et al. | Oct 2012 | A1 |
20120274028 | Sudbeck et al. | Nov 2012 | A1 |
20130106059 | Larue | May 2013 | A1 |
20130207347 | Sovine et al. | Aug 2013 | A1 |
20150260486 | Trimbath | Sep 2015 | A1 |
20150276356 | Cesternino | Oct 2015 | A1 |
20150292842 | Pixton | Oct 2015 | A1 |
20150330747 | Ferrell | Nov 2015 | A1 |
20150330748 | Anzalone | Nov 2015 | A1 |
20160195371 | Bateman et al. | Jul 2016 | A1 |
20160209173 | Dribben | Jul 2016 | A1 |
20160334195 | Auld | Nov 2016 | A1 |
20180017362 | Rahmanian | Jan 2018 | A1 |
20180202777 | Green | Jul 2018 | A1 |
Number | Date | Country |
---|---|---|
2136932 | Sep 1984 | GB |
2 187 270 | Sep 1987 | GB |
2533147 | Jun 2016 | GB |
WO 2010119440 | Oct 2010 | WO |
Entry |
---|
Caswell International Corp., Product Literature, Copyright 2002. |
Duelatron, Product Literature 1995. |
Law Enforcement Targets, Inc., Product Literature, Jul. 8, 2003. |
Law Enforcement Targets, Inc., Product Literature, Oct. 12, 2004. |
Law Enforcement Targets, Inc., Product Literature, Jun. 26, 2007. |
Porta Target, Product Literature, Circa 2000. |
Shootrite, Tactical Training Target, published prior to Apr. 4, 2005. |
Number | Date | Country | |
---|---|---|---|
20190212107 A1 | Jul 2019 | US |
Number | Date | Country | |
---|---|---|---|
62614404 | Jan 2018 | US | |
62619674 | Jan 2018 | US |