The present invention relates to software, methods and systems for the operation for target range equipment, and more specifically to self-calibration or correction for moveable target systems.
In shooting ranges, targets and bullet traps are often provided to assist a shooter in improving his or her ability to reliably hit a target. While shooting at a stationary target is beneficial, shooting at moving or changing targets more accurately replicates real life situations. This is particularly true for law enforcement officers and military personnel. If an officer or soldier can be taught to quickly and accurately make “shoot” or “no shoot” decisions in a high stress environment, the risk to both the officer/soldier and the general public is reduced. Acquiring this skill, however, takes considerable training in life-like scenarios.
To replicate real life situations, targets may move forward and back on tracks, may run side-to-side, or may rotate or swing in a generally fixed position. In some scenarios, a shooter may practice firing at a rapidly-approaching target, simulating an attack, while other scenarios include the target or multiple targets moving laterally across the shooter's field of vision.
In other training exercises, the target may be rotated 90 degrees in either direction to show one of two faces of the target. One face shows an image consistent with a “shoot situation,” such as a person holding a gun aimed at the shooter. The opposing side shows a “no shoot situation,” such as a person holding a cell phone, or a criminal standing behind a hostage. Still other targets are designed to indicate when the target has been incapacitated.
In some training exercises, often called “dual running man” scenarios, two target carriers run simultaneously on the same track, adjacent tracks or overhead cable(s). The target or targets pass sideways or laterally across the shooter's field of vision. One carrier may edge a little forward of the other so that its target peeks out from behind the other, or the targets may travel together, only to unexpectedly separate and head in different directions. This may simulate a hostage scenario, in which a dangerous individual is pulling an innocent individual along and using him for cover. To allow repeated training, these target systems are usually motorized, or automatically resetting, so that the target systems run multiple cycles or at least so users can press a button to reset the targets to their original locations.
Moving or pivoting targets, however, are subject to increasing malfunctions over time. Moving track-mounted target carriers often gradually lose their calibration. The target carriers may be struck by bullet fragments, or may lose calibration simply because of sudden stops, starts, or jolting movements combined with slippage of the drive cable. This results in a target carrier which may be directed to collide against the track-stop on one end of the track, potentially causing damage to components, or which increasingly stops in the wrong place—thereby interfering with the training scenarios. Likewise, a user may not be able to direct a poorly-calibrated target carrier close enough for the user to change out the target attached to the carrier. The miscalibration may also put additional strain on the motor and the cable, and decrease the length of time the target carrier can operate between maintenance visits.
In a dual target scenario, an error regarding the position of the target carrier may result in the second target not being covered by the first target when the opposite is desired, or may result in one or both of the targets arriving at a desired position either too early or too late. Either way, it can interfere with proper execution of the training scenario.
Swinging or pivoting target paddles may, when struck by a bullet, pivot or fall only part of the way. For example, a drop (or bobber) target may not fall all of the way and therefore not properly indicate that it has been struck or may not be properly returned to its original position. Likewise, a turn target may get off its initial calibration so that when rotated the image on the target is not clearly presented to the shooter.
Moving target carriers and motorized pivoting targets are often controlled with a button or switch, and often operate at a single speed only. It may thus be difficult for a user to precisely position the target or make an appropriate correction. When a user attempts to make fine adjustments in position, the target carrier or target paddle may sway and jerk as it is repeatedly started and stopped by the motor. Additionally, this sudden stopping and starting may loosen the attachment of a target silhouette to the motorized portion of the target system. This can be hazardous—if a target silhouette is held to the motorized portion by, for example, clips, the clips may be shaken off by the movement, causing the target to fall off. It then cannot be retrieved without stopping all shooting on the range. Fallen metallic clips or even targets may present a danger of bullet deflection.
Track-mounted target carriers are costly, and are used in an environment that can increase the likelihood of mechanical errors. For example, there may be lead dust in the range, and target carriers as well as target carrier rails and cables may be struck by stray bullets. Because of this, some types of target carriers are error prone—e.g., a bullet dent in a rail may cause the target carrier to drag and become damaged, which then causes the target carrier motor to burn out prematurely—and expensive to repair.
Likewise, motorized pivoting or swinging targets may be susceptible to mechanical errors. Because these target systems are typically intended to be picked up and moved, their motor and drive systems are low powered and self-contained. Some operate from 12-volt batteries. It is thus advantageous if a motorized target system is both smart enough to halt activity if damage or unusual events are detected, and requires very little power to run. It is further advantageous if the target system provides for several means of notifying users of faults.
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 system requires very little servicing and/or that the need for servicing can be more accurately predicted so that it can be performed when the range is not in use.
It is also beneficial if target systems are programmable. For example, carriers that can be instructed to perform particular maneuvers such as turns, approaches, and retreats on their own via a program, without the need for a shooter to continuously hold down a direction button. It is advantageous if stationary motorized or automatically resetting targets can be programmed to present their target face to shooters at intervals, to turn the target face part way to present a smaller and more challenging target, and the like.
An additional challenge is synchronicity. Most of these target installations—whether the targets are turning, bobbing, or moving—are not used in isolation. Rather, it is typical for several of these mechanized targets to be placed on a range, to be simultaneously fired at by multiple shooters. Targets which move or turn at a different rate from their neighboring targets results in some of the shooters having an easier or harder challenge to hit such targets. For example, if all officers are given 5 seconds to place 5 kill shots in the torso and some targets turn more slowly or incompletely, those officers are at a distinct disadvantage. This is a major problem for law enforcement and military personnel, because they cannot adequately measure how individual shooters are performing relative to the group without redoing the exercise.
For example, during some military training scenarios, a bobber-like target may be intended to pop up in front of each of the shooters for exactly two seconds, before ducking back down. Simultaneously, a loud and surprising noise is played, or another distraction is provided. If the target for shooter A remains upright for 1.9 seconds, but shooter B's target is exposed for 2.1 seconds, it is difficult to judge which has better quick-fire and target discrimination skills when faced with a startling noise. Both shooters cannot take turns firing at the same target, because the later shooter will not be surprised by the noise.
Similarly, in the case of moving targets or target carriers, the various targets on a range may tend to move at different speeds or accelerate in different manners, simply due to mechanical wear, damage, frost, or installation variances. This can result in large differences in the difficulty faced by shooters firing at these targets. An individual shooter has difficulty measuring his own progress in skill and accuracy, both over time and as compared against other shooters on the range.
Finally, ranges often receive requests for highly complex scenarios. For example, some users may request a dual running man training scenario, in which additional ‘innocent bystander’ targets pop up in front or behind the ‘dangerous person’ target. Most ranges cannot easily accommodate such a request, as the running man target carriers function according to one set of programming, while the pop up or bobbing targets respond to a different set of protocols. Moreover, current known ranges provide minimal ability to maintain synchronization of multiple targets.
Thus, there is a need for a simple, reliable, and robust new system for providing linear, rotational, and/or pivoting movement to a target carrier with improved operation and accuracy in the system. It is advantageous if many, if not all of the targets on a range, have mechanisms to report their position and velocity status to a central network, which can signal some targets to move differently in order to match nearby targets. It is further advantageous if the network is aware of faults or targets moving too slowly or too quickly, and can adjust the targets to comply with the request, cancel the program, or provide an indication that the scenario desired is unachievable in the event that some target units persist in behaving out of synch with the others. Likewise, it is desirable to have a system which can report the fault to the user, and flag misbehaving targets for maintenance. It is also an advantage if the system is flexible enough to accommodate and coordinate multiple types of target hardware on the same range.
Various embodiments described by the present specification are described in greater detail below.
The present disclosure discusses control systems for various types of moveable targets which may increase the accuracy and/or reliability of the system to allow improved use in the short term and prolonged life while minimizing required maintenance.
One advantage of the present disclosure is to provide a control system for one or more track-mounted target carriers, equipped with sensors to ensure the proper position of the target carrier systems before and/or during an exercise. This may include maintaining multiple carriers in desired positions relative to one another during the exercise. An additional advantage is to provide a control system for other automated targets to ensure proper target position. Still another advantage may be providing notification when the carrier is in need of service.
One advantage of the present disclosure is to provide a control system for a rotating target to ensure that the target is being properly rotated for presentment to the shooter. This may relate to the relative position of a single target, or the positions of multiple targets relative to each other. In addition to improving presentment, the system may be able to signal the need to service a particular control system.
Yet another advantage of the present disclosure is to provide a control system for a drop target or bobber which improves accuracy of the system to better record when a target has been properly struck and/or reset. In addition, the system may indicate when servicing is required.
One more advantage of the present disclosure is to provide a control system which can adjust the behavior of individual targets of the same type, so that they move in nearly identical fashions, despite differing wear, damage, or installation idiosyncrasies. This may include, for example, increasing the speed of some actuator systems and/or reducing the speed of other actuator systems, e.g. controlling motor speed, so all of the targets are presented at substantially the same time or in the correct order.
An additional advantage is to provide a sensor suite compatible with many types of targets, which can report on the targets' velocity, position, and relative orientation and status (upright or fallen, turned broadside to the shooter or edge-on, etc.) in order to coordinate movement across an entire range and different types of targets.
The present disclosure includes different systems and methods for moving and interacting with the target system, and are thus applications of a common inventive concept. It should be appreciated that various devices, systems, methods and applications will have some benefits and may lack other benefits which are present in different devices, systems, methods and applications described herein. Therefore, the teachings of the present disclosure and any actual or intended benefit of any embodiments should not be read into the claims unless expressly stated therein.
In accordance with some aspects of the present disclosure, a method for moving and operating the target system may include: using a movement control station in conjunction with a target holder and a target carrier motor; supplying a movement control station; monitoring the movement process of at least one of the target carrier, the target carrier motor, and the movement control station; and controlling or adjusting a moving speed or distance of the target carrier; and iteratively monitoring the movement of the target carrier. The system may adjust a single target carrier to ensure that the target is in the proper location, or may be able to adjust a plurality of targets to ensure that a training scenario is properly performed.
In other embodiments, a method of moving and operating a target carrier may also include: a movement process module which has a mechanism for turning the target holder.
In yet other embodiments, the target carrier may include a primary sensor mechanism, such as a rotary encoder and a target carrier or secondary sensor; and operating the target carrier may include the steps of: providing a target carrier track; identifying a selected position along the target carrier track; using a signal from the target carrier sensor to predetermine a first end and a second end of the target carrier track; and receiving a signal from the rotary encoder, calculating a current position of the target carrier, and moving the target carrier to the selected position at a speed, the speed being variably dependent on the distance between the current position and the selected position and the time window for accomplishing the movement.
In yet other embodiments, the target carrier may include a rotary encoder and a target carrier sensor; and operating the target carrier may include the steps of: providing a target carrier rotational point; identifying a selected position of rotation; using a signal from the target carrier sensor to predetermine a first desired position and a second desired position; and receiving a signal from calculating a current position of the target carrier, and moving the target carrier to the selected position and verifying the second position by means of a sensor independent of the signal to predetermine the first desired position and adjusting the signal accordingly.
In still other embodiments, the method of operating a target carrier may include limiting a control effort of the target carrier motor; and adapting the target carrier and the target carrier motor so that they cease operation if they do not receive a confirming signal from the movement process module within about one second.
These and other aspects of the present disclosure may be realized in various motorized target control systems and methods of use as shown and described in the following figures and related description. It will be appreciated that various aspects of the invention can be used separately and that the invention is defined by the appended claims rather than this summary.
Non-limiting and non-exhaustive embodiments are described with reference to the following drawings, wherein like labels refer to like parts throughout the various views unless otherwise specified. The sizes and relative positions of elements in the drawings are not necessarily drawn to scale. For example, the shapes of various elements are selected, enlarged, and positioned to improve drawing legibility. The particular shapes of the elements as drawn have been selected for ease of recognition in the drawings. Various embodiments of the present invention are shown and described in reference to the accompanied drawings, wherein:
It will be appreciated that 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. It is appreciated that 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 will be further appreciated that elements shown in different drawings may be combined as set forth in the claims.
The disclosure and accompanying drawings are discussed below, using reference numerals to identify parts and features so as to enable one skilled in the art to practice the present invention. The drawings and descriptions are exemplary of various aspects of the invention and are not intended to limit or narrow the scope of the appended claims.
Furthermore, it will be appreciated that the drawings may show aspects of the invention in isolation and the elements in one figure may be used in conjunction with elements shown in other figures. In light of the present disclosure, the skilled artisan will understand that the methods described below can be practiced without employing these specific details, or that they can be used for purposes other than those described herein. Indeed, they can be modified and can be used in conjunction with products and techniques known to those of skill in the art in light of the present disclosure.
Reference in the specification to “one configuration,” “one embodiment” “one aspect” or “a configuration,” “an embodiment” or “an aspect” means that a particular feature, structure, or characteristic described in connection with the configuration may be included in at least one configuration and not that any particular configuration is required to have a particular feature, structure or characteristic described herein unless set forth in the claim. The appearances of the phrase “in one configuration” or similar phrases in various places in the specification are not necessarily all referring to the same configuration, and may not necessarily limit the inclusion of a particular element of the invention to a single configuration, rather the element may be included in other or all configurations discussed herein. Thus, it will be appreciated that the claims are not intended to be limited by the representative configurations shown herein. Rather, the various representative configurations are merely representative examples and are provided to help one of ordinary skill in the art to practice the inventive concepts claimed herein.
Furthermore, the described features, structures, steps or characteristics of embodiments or aspects of the invention may be combined in any suitable manner in one or more embodiments. In the following description, numerous specific details are provided, such as examples of products or manufacturing techniques that may be used, to provide a thorough understanding of embodiments of the invention. One skilled in the relevant art will recognize, however, that embodiments of the invention may be practiced without one or more of the specific details, or with other methods, components, materials, and so forth. In other instances, well-known structures, materials, or operations may not be shown or described in detail to avoid obscuring aspects of the invention.
Before the present invention is disclosed and described in detail, it should be understood that the present invention is not limited to any particular structures, process steps, or materials discussed or disclosed herein, but is extended to include equivalents thereof as would be recognized by those of ordinarily skill in the relevant art. More specifically, the invention is defined by the terms set forth in the claims. It should also be understood that terminology contained herein is used for the purpose of describing particular aspects of the invention only and is not intended to limit the invention to the aspects or embodiments shown unless expressly indicated as such. Likewise, the discussion of any particular aspect of the invention is not to be understood as a requirement that such aspect must be present apart from an express inclusion of the aspect in the claims.
It should also be noted that, as used in this specification and the appended claims, singular forms such as “a,” “an,” and “the” may include the plural unless the context clearly dictates otherwise. Thus, for example, reference to “a track reference mark” may include one or more of such marks, and reference to “the target” may include reference to one or more of such targets.
As used herein, the term “substantially” refers to the complete or nearly complete extent or degree of an action, characteristic, property, state, structure, item, or result to function as indicated. For example, an object that is “substantially” enclosed would mean that the object is either completely enclosed or nearly completely enclosed. Likewise, a reference that something is substantially perpendicular would mean that the object is sufficiently perpendicular to carry out a particular function. The exact allowable degree of deviation from absolute completeness may in some cases depend on the specific context, such that an enclosure encircling nearly all of a wheel would be substantially enclosing, even if one side of the enclosure had a slit or channel formed along a portion thereof. The use of “substantially” is equally applicable when used in a negative connotation to refer to the complete or near complete lack of an action, characteristic, property, state, structure, item, or result. For example, structure which is “substantially” upright would either be completely upright or so nearly completely upright that the effect would be effectively the same as if it was completely upright.
Likewise, the term “generally” is used to designate something having an aspect which has more of the matter indicated than not, to perform a function or such that common usage would cover the matter indicated, but is used herein more broadly the substantially. Thus, an item may be described as generally vertical if it is sufficiently more vertical than horizontal that common language would be consistent with use of the term. Thus, for example, a slope at 60 degrees may be called generally vertical, while a slope above 75 degrees may be substantially vertical.
As used herein, the term “about” is used to provide flexibility to a numerical range endpoint by providing that a given value may be “a little above” or “a little below” the endpoint while still accomplishing the function associated with the range.
As used herein, a plurality of items, structural elements, compositional elements, and/or materials may be presented in a common list for convenience. However, these lists should be construed as though each member of the list is individually identified as a separate and unique member.
Concentrations, amounts, proportions and other numerical data may be expressed or presented herein in a range format. It is to be understood that such a range format is used merely for convenience and brevity and thus should be interpreted flexibly to include not only the numerical values explicitly recited as the limits of the range, but also to include all the individual numerical values or sub-ranges encompassed within that range as if each numerical value and sub-range is explicitly recited. As an illustration, a numerical range of “about 1 to about 5” should be interpreted to include not only the explicitly recited values of about 1 to about 5, but also include individual values and sub-ranges within the indicated range. Thus, included in this numerical range are individual values such as 2, 3, and 4 and sub-ranges such as from 1-3, from 2-4, and from 3-5, etc., as well as 1, 2, 3, 4, and 5, individually. This same principle applies to ranges reciting only one numerical value as a minimum or a maximum. Furthermore, such an interpretation should apply regardless of the breadth of the range or the characteristics being described.
The invention and accompanying drawings will now be discussed in reference to the numerals provided therein so as to enable one skilled in the art to practice the present invention. The drawings and descriptions are intended to be exemplary of various aspects of the invention and are not intended to narrow the scope of the appended claims. Furthermore, it will be appreciated that the drawings may show aspects of the invention in isolation and the elements in one figure may be used in conjunction with elements shown in other figures.
Turning now to
The term target actuator system is intended to cover the means and mechanisms by which a target is moved into position. To this end the target actuator system may include a motor, cable, track and target carrier of a retriever, or the drive mechanism, including the motor, pistons, etc., of a turning target. A variable frequency drive may be considered to be part of a target actuator system. The target actuator system may be electromechanical, hydraulic or pneumatic. A target carrier is a portion of the target actuator system which engages the target and, in response to other portions of the actuator system, moves the target.
The target system 10 may include a target actuator system, generally indicated at 12 having one or more tracks 14 on which target carriers 18 move back and forth to move targets 22 toward and away from the shooter(s). The target carriers 18 may be self-driving, or may be driven by a cable 26. The cable 26 may be driven by a motor unit 30 to move the target carrier 18 between a proximal end 14a of the track 14 and a distal end 14b of the track. Anywhere along the track 14, a target mount 24 (if provided) may be used to rotate a target so that it is perpendicular or parallel with the track 14 and the line of fire.
A rotary encoder 34 or other measuring device may be placed on each motor unit 30 or other structure to measure the movement of the cable 26 and thereby indicate position of the target carrier 18 along the track 14. If a command is sent to move the target carrier 18 to the distal end 14b of the track 14, the motor unit 30 will operate to drive the cable 26 until the rotary encoder 34 indicates that the target carrier 18 is adjacent the distal end. Generally, it is desirable to drive the target carrier 18 quickly to avoid wasted time and to make the scenario realistic. However, if the rotary encoder 34 has calculations which are off, the target carrier 18 will not be in the proper position. It may be a foot or two short, or it may cause the target carrier 18 to ram into a stop 38 at the distal end 14b of the track 14—potentially damaging the target carrier 18, or causing the target to fall or be mis-positioned.
While rotary encoders 34 and other similar devices are generally accurate, lead dust on the track, damage to the track 14 or target carrier 18 from ricochets, stretching of the cable, slippage and other issues can cause the rotary encoder to have a reading which is inaccurate. While a slippage of 1/32 of an inch may not appear to present a problem, when a target carrier 18 is moved thousands of times and the slippage occurs in one direction more commonly than the other, the disconnect between the rotary encoder's calculation and the actual position of the target carrier 18 can be significant. If the error is in one direction, the target carrier 18 will not advance a sufficient distance along the track 14 toward the distal end 14b. If the error is in the other direction, the target carrier might not advance to the proximal end 14a so that the shooter can inspect his or her target.
One common scenario is for a number of police officers to shoot at a target at a given distance for a given time. Thus, for example, if a police officer must take a qualification test at 25 feet, entering the distance of 25 feet may cause the target carrier 18 to go only 22 feet, potentially changing the timing at which that target turns, changing the difficulty caused by distance, and also potentially rendering the test invalid. While it may be appreciated that Officer A's target is not as far out as the other officers' targets, fixing the problem may be difficult without temporarily shutting down the range. Likewise, when the target carrier 18 should be returned 25 feet so that the officer may take his or her target down, the target carrier 18 is more likely to run into a stop 40 at the proximal end 14a of the trap, rather than being braked to come to rest shortly before the stop.
To resolve these concerns common to retrievers and other target systems, the present invention may utilize at least one secondary sensor 50 disposed adjacent the target actuator system. Thus, for example, as shown in
The information regarding the actual location of the target carrier 18 can also be used to determine when the system 10 needs to be serviced. If the actual position sensed is repeatedly beyond a desired threshold proximally or distally from the estimated position, the system can determine that, for example, the cable 26 has stretched and is slipping as it is driving the target carrier 18. The system may then be serviced to correct the problem. Some ranges include dozens of retrievers. When one system 10 indicates that a particular retriever needs to be serviced, it can save a considerable amount of time over manually checking and servicing all of the systems at once.
While shown as a separate processor 58 for each retriever, a single processor or networked processors may be used. The processor(s) 58 may receive information from a plurality of rotary encoders 34, and sensors 50 to determine where each retriever is located. This may be updated multiple times per second so that the processor(s) 58 are always aware of the location of the target carriers 18. This can be used to provide a wide range of scenarios and to ensure that the scenario is being carried out properly. For example, one scenario may have two adjacent target carriers 18 advance to a certain point, and then one target carrier suddenly advance while the other suddenly retreats. The officer must then respond to two targets acting in different manners and adjust his or her response accordingly.
In another scenario, a large number of retrievers may be positioned side by side at a shooting range. Upon a signal, all of the target carriers 18 advance along their respective tracks to 25 yards. The processor(s) 58, however, collect information from the rotary encoder 34 and sensors 50 to determine if one or more of the targets carriers is moving at a different rate of speed than the others. If all of the target carriers turn once they have traveled 25 yards, then some of the targets will not turn at the same time, thereby interrupting the exercise. Others may ordinarily be out of place if there is slippage between the motor unit 30 and the cable 26. In response to the collected information, the processor(s) 58 can send one or more signals to: 1) indicate a fault that the scenario cannot be completed; 2) adjust the perceived position of a target carrier when it passes by one of the secondary sensors and compensate in the time period the motor unit drives the cable; 3) increase power to the motor unit 30 associated with a lagging target carrier 18 so that it catches up with the others; or 3) slow down the other motor units 30 in order to allow the lagging target carrier(s) 18 to catch up with the others. By sampling multiple times per second (e.g. every 0.03 seconds), the processor(s) 58 can often make adjustments before the lagging or mispositioned target carrier 18 is even noticed by users.
In
In
Turning now to
A turn target 62 of such a system typically has at least three states. In an initial state, a target 62 is disposed parallel to the line of fire so that a shooter can only see the edge of the target. Upon actuation, the target 62 is rotated 90 degrees in one direction to show one side of the target, or is rotated 90 degrees in the opposite direction to show the opposite side of the target. Often one side of the target will show a “shoot” scenario, as shown on target 62a, such as a person holding a gun. The other side, as shown on target 62b, may have a “no shoot” scenario, such as a person holding a cell phone, or a criminal standing behind a hostage. The key to the shooting scenario is that the officer or soldier does not know what will be presented, and must quickly and accurately determine whether it is a shoot or no shoot scenario.
The target 62 is rotated between the three positions by a target actuator system 64. There are numerous types of target actuator systems 64, including both electromechanical, hydraulic and pneumatic systems. The actuator system 64 shown in
In the highly demanding environment of a shooting range, however, these mechanisms can become damaged and can become worn or develop leaks over time. This loss of calibration may cause the actuator system to turn the target too much or too little. Regardless of whether a stepper motor with a rotary encoder is used or a pneumatic piston assembly 66 is used, there is an ever-increasing risk that the target will not turn in proper 90 degree increments. The rotary encoder associated with the motor may get out of alignment, one of the pistons may develop a leak, or the engagement between the drive unit (motor or pistons) and the drive shaft 68 may slip or become loose—thereby preventing the target 62 from moving into and staying in the proper position. For example, if the target 62 is not parallel to the line of fire at the initial position, the shooter may be able to see enough of the target on one side to know in advance if it is a shoot or no shoot situation on that side of the target. This limits the usefulness of the exercise.
In order to solve this problem, the turn target system 60 can be equipped with a secondary sensor system 70. The secondary sensor system 70 may be an optical or other sensor which detects when the edge of the target passes over it. Alternately, the sensor may be, for example, a Hall effect proximity sensor or a magnetic sensor, which detects a strip of metal 72 or other indicator embedded in one side of the target 62, or may be a magnet attached to the drive shaft or target clamp. Additionally, other sensor markers could be placed in the target so that the sensor system knows which side is being displayed to the shooter. Thus, the sensor may not only detect the positioning of the target 62, but also which of the faces is presented to the shooter. Alternatively, the sensor system 70 may read optical markers 74 attached to the drive shaft 68 to determine the orientation of the target 62. Regardless of the type of sensors, the sensors may be used to communicate with a processor 58 which can determine whether the target is in the correct place, whether the target is moving quickly enough, etc., and make adjustments as appropriate or signal that there is a fault situation which needs to be fixed prior to running the exercise.
In the event that the target 62 does not rotate fully, moves too slowly, etc., the output of the secondary sensor system 70 may be used to modify the motion provided to the drive shaft or other structures of the target actuator system in some embodiments. In the context of a motor, the power supplied can be adjusted to provide for the proper turning distance or speed of the target, e.g. via use of a variable frequency drive (VFD). In a piston-driven system, combinations of pistons may be used to compensate for the piston which is not functioning properly until the malfunctioning piston can be repaired or replaced. The secondary sensor system 70 may also provide an output to report a malfunction and the need for service. Additionally, the output of the secondary sensor system 70 can be used in conjunction with actuation signals to determine if the target is turning too slowly, which may indicate a leak or slippage. The secondary sensor system 70 communicates with a control system to make appropriate corrections via the target actuator system.
Attached on top of the first arm 96 is a target 94 having a first configuration. In the embodiment shown in
The drop target system 90 may be used to accurately test a shooter's reflexes, as well as their ability to discriminate between targets. For example, shooters may be instructed that the blue target represents a bystander, while the red target represents a dangerous individual. In such scenarios, the shooter must strike the red target quickly, causing it to fall, but then avoid firing a second time to hit the blue target standing directly behind the first. Across the three targets, the rear target may be blue in one, two or all three. Thus, the shooter must constantly be alert and avoid hitting a target representing an innocent bystander.
Due to wear and vibration of the drop target system 90, however, the actuator system in the base 97 may become damaged, so the actuators do not cause the targets to pop up in the correct sequence or at the correct speed. Alternately, paddles may “stick” or fail to drop all the way, so that they must be struck several times. In order to solve this problem, one or more additional or secondary sensors 99 may be provided. These may be proximity sensors, optical sensors, or the like. They may be positioned to detect only when a target paddle 93 or 94 is upright, or may be positioned to detect when a target paddle is down. In the present embodiment, if the actuator systems in the bases 97 report that they have activated to an upright position, but a sensor 99 does not detect that the paddle has been placed in an upright position in a timely manner, then the system 90 may recognize that a fault has occurred, and may either direct the actuator system(s) to activate again in an effort to clear the obstruction, or may warn the user or the range operator. Alternately, if the target paddles drop too quickly after being raised, this may indicate that the hinges have become damaged such that the force of gravity causes them to fall without ever being struck. The system 90 thus compensates for a variety of common types of damage.
The system 90 can be controlled by a processor 58 which may have communications lines 91 to each of the drop targets 89, or a wireless system may be used. Likewise, embedded controllers could be used. The processor 58 can determine the status of each of the targets and provide signals to cause the system to resolve problems at a very high rate of speed, often without the users even realizing that adjustments were made. Moreover, the processor 58 can track repeated errors and adjust for the same. For example, if one target consistently is not reset completely with the first activation of the actuator system, the processor may send signals to that actuator system to go through the actuation movement twice each time that particular target needs to be reset.
Various figures and descriptions herein indicate steps or processes that may be taken by portions of the system and the system as a whole. It will be appreciated that these steps are outlined as occurring in a particular order and as discrete steps only for illustrative purposes. Thus, many steps may be performed in a different order and/or simultaneously to achieve the desired results of the present disclosure. The listing of steps in a particular order does not mean that the process requires that particular order.
With reference to
The receiver/transmitter 206 also emits or sends or transmits a signal 212 to control and receive data from a transmitter and secondary sensors 214. Sensors 214 may be positioned on the track itself or may be onboard the target carrier, or positioned at the end of the track. Sensors 214 may include, for example, linear variable, ultrasonic, optical, or proximity sensors, a rotary encoder, idler wheel with encoder, laser distance, and other sensors for detecting target carrier speed, location/position, target orientation, and the like.
The target carrier movement computing software 204 may further receive input from a customer service and update function, such as an internet connection 216. The customer service function may receive error codes from the movement computing software 204. Alternately and in addition, an update function may be configured to provide remote access to the software 204 to update the software version or to add functionality, for example, via a subscription service. Further, the customer service function may include recording functions. For example, if a user completes three of the five shooting programs contained in a training course, and then logs out, the customer service function may be adapted to store this data. When the customer returns, the remaining shooting programs may be highlighted or otherwise highlighted for the customer's attention.
Thus, a user at a movement control station can input a shooting program, or select from a menu of common shooting programs. Signals are then sent and received between the movement computing software, the sensors 214, and the motor 210, to result in movement to the target carrier.
It will be appreciated that in some embodiments, the microprocessor 202 and movement computing software 204 may be onboard the target carrier, or may be housed separately or remotely, and may communicate wirelessly with the target carrier and a user-operable movement computing station (not indicated). In such embodiments, the user control station may be a separate terminal equipped with an input device such as touchscreen, or a cell phone or tablet application, or other means known to one of skill in the art of inputting user commands.
It will be appreciated that the processor 202 receives the information from the sensors 214 and can make adjustments to signals sent to the target carrier motor 210 to adjust the position, direction, speed or actuation of the target carrier. Thus, for example, the target carrier motor 210 may be determined to be moving too slowly to be at a desired location in order to perform part of a scenario of a shooting exercise. In response, the processor can either 1) generate a fault message to an operator indicating that the scenario is not possible because of the position or movement of the target; 2) send signals to adjust the motor unit to speed up the target to get the target into place by the time necessary; or 3) send signals to slow down other target carriers (not shown) so that the target carrier arrives in time due to the delayed positioning of the other targets. Such a system allows a processor 202 to control an entire range and ensure that all of the targets are in position and actuated at an appropriate time to perform a training scenario.
It will be appreciated that errant target carriers can create a significant problem at a range. For example, if a shooting range has 20 lanes across and is being used for a qualifying test in which the target advances 25 feet, turns for 3 seconds, returns to its original position and retracts, any officer whose target does not advance to the proper location, turn at the proper time and return will have to retake the certification. Moreover, the error may negatively impact the other officers. If the target in lane 3 turns prematurely, the officer in that lane will start firing, thereby distracting the other officers whose targets have not yet turned. If the target in lane 14 remains exposed to the officer for longer than 3 seconds, the results of the test will not be accurate and may result in an officer passing the test who should not have passed. If the target in lane 10 only advanced half way to the desired location, the misplaced target may be distracting to the officers in lanes 9 and 11. By providing a plurality of position, motion and/or other sensors, the processor 202 can better control the testing conditions or warn in advance if the scenario chosen in not possible.
Turning now to
At 300, the startup calibration begins when the target carrier is powered on. The target carrier then tests operating status of the drive motor (302). In the present embodiment, the drive motor may be a variable frequency drive (VFD) with onboard comms or an embedded controller. It will be recognized, however, that any type of motor suitable for moving the target carrier along the overhead rail track may be used. In the event of a VFD error 304, the target carrier software system returns an error. During the calibration phase, this error occurs when the target carrier reaches the end of the stop at the end of the track or rail, because the motor is pulling on the carrier but no movement results. This error notifies the movement computing software that an end of the track has been reached.
In the event the motors report ready, the target carrier movement computing system clears faults 306 and starts the VFD motors to move the cable and the target carrier mounted thereto.
At 308, the sensors associated with the target carrier register a first end of the track when sensors detect that the target carrier reaches the end of the track. This may be accomplished by, for example, increased resistance on the motors, by a triggered bumper system, a position sensor or other means known to one of skill in the art. One advantage of using the error produced by increased resistance on the motors as described above (during the calibration phase) as a signal that the target carrier has reached the end of the track is that the error can be averaged over a sliding window.
In some embodiments, the error registered by the carrier motor during step 304 is averaged over several hundred sensor transmissions, or a few seconds of the target carrier contacting the end stop. Even if the target carrier vibrates somewhat due to motion as it contacts the end stop, the sliding window average of the increased resistance against the motor will remain steady. However, if the target carrier contacts fallen debris on the track, such as leaves or twigs, the sliding window average of the error will not remain steady, indicating that a user must check the track.
When the target carrier has contacted the first end of the track, the target carrier movement computing software then 310 clears or resets to zero the value recorded by a rotary encoder or other mechanism commonly used to determine position or movement. The rotary encoder may be, for example, an absolute multi-turn rotary encoder, a quadrature encoder, or the like. It will be appreciated that other means of translating mechanical linear movement into an electrical signal may be used, such as a laser distance sensor, ultrasonic measurement, etc.
At 312, the motor pull is reversed, so that the target carrier crawls or moves along the track in the opposite direction. In some embodiments, a Hall effect or similar proximity sensor may be stationary and mounted to the track. Other secondary sensors such as optical sensors, etc., may also be used. When the target carriage crosses over the proximity sensor, the sensor triggers, and the movement computing software records the signal and requests the rotary encoder position. At 314, when the end of the track is reached, the target carrier movement computing software records the rotary encoder value and stops the target carrier motor. At 316, the target carrier movement computing software calls a function to monitor and calibrate the rotary encoder with the proximity sensor.
The 316 step ensures that, at the calibration stage, the movement computing software recognizes the rotary encoder readout that correctly matches to the location of the proximity sensor mounted on the track. During later usage of the target carrier, after the calibration, the movement computing software compares the current rotary encoder readout with the proximity sensor location each time the target carrier passes the proximity sensor. Thus, even if the rotary encoder becomes inaccurate over time—a common problem when rotary encoders are used to measure location when a distance is traveled back and forth repeatedly—the software corrects or readjusts the rotary encoder value. In the pictured embodiment, the target carrier is therefore constantly self-calibrating with each pass over the checkpoint or proximity sensor, even after days or weeks of uninterrupted use.
At 318, the movement computing software checks to ensure that the rotary or linear encoder value is aligned with the motor direction. A relatively simple wiring error may result in the encoder of a target carrier, for example, transmitting a negative value when the correct value is positive. Alternately, a motor may be reverse-wired. In either case, locating the mis-wiring and correcting it may take considerable installation time. The check at 318 compares the target carrier location (as reported by the increased resistance against the motor or other means of registering when a target carrier has reached one end of the track) with the value transmitted by the rotary coder. If necessary, at 320, the software may apply a value correction and return to the steps of the self-calibration and startup sequence. The software-level correction may thus accommodate wiring mistakes that previously could require many hours to correct.
At 322, the target carrier movement computing system detects the second end of the track, and then at 324 compares the recorded distance between the first and second ends of the tracks. If there are certain mechanical faults in the target carrier system, (for example, the motor will operate only for a short time, causing the target carrier to stop along the track) the recorded distance will not approximately equal the true length of the track. In this case, the track length is not acceptable, and at 326 the system returns an error and places the target carrier on standby.
At 328, the system runs a second check of the proximity sensor, and at 330 returns an error if a proximity sensor is not detected. The system then returns the carrier to home at 332. Home may be the original starting location, or may be for example the most commonly-used shooting distance from the shooter for a particular track or range, or may be the location of the proximity sensor which is typically located at a midpoint distance along a track. At 334, the system checks for any fatal errors recorded during self-calibration and startup, and will either mark the self-calibration as failed and output a warning at 336, or mark success and place the target carrier in a ready state at 338.
If the target carrier is far from the desired location (as reported by the rotary encoder) and far from the maximum cruise velocity (as reported by the motor speed), the movement computing software then directs the motor to accelerate 406, provided that 414 the control effort (voltage or current applied to motor actuators) is limited to the range recommended for the particular motor. In this control method, the control effort may be accelerated by the equation:
controlEffort=controlEffort+(accelerationRate×loopPeriod)
Because acceleration rate and loop periods are constant, the control effort is increased at a linear rate, providing smooth constant acceleration up or down to the cruising speed.
By monitoring the control effort applied by a motor, the control effort thus functions as an additional (albeit comparatively error-prone) target position sensor. The control effort also acts like a throttle. In the pictured embodiment, the motor is a variable frequency drive (VFD) with a recommended control effort limited to 30 Hz. It will be appreciated, however, that more or less robust motors, and other types of motors, may be used.
If the target carrier is outside an acceptable threshold from the desired position (as reported by the rotary encoder), but is at or near maximum velocity (as reported by the motor speed), the movement computing software directs (408) the motor to maintain cruise speed, provided that the control effort (voltage or current applied to motor actuators) is limited to the range recommended for the particular motor (414). This acceptable threshold from the desired position is dynamic, and may depend, for example, on the speed of the trolley. Typically, it may be between three and ten feet.
Accurate cruising velocity may be maintained through use of the equation:
controlEffort=controlEffort+(VelocityError×loopPeriod)
(VelocityError) in the equation above is a signed number that represents the difference between the current velocity, and desired velocity (which may be directed/programed by a user). (loopPeriod) in the equation scales this number down since the calculation is typically being made many times per second. This equation allows the cruising velocity to be either increased slightly or decreased slightly when the velocity is not equal to the ideal cruising velocity.
As the target carrier approaches the desired position, as indicated by the rotary encoder, the movement computing software directs (410) the motor to apply feathered braking, provided that the control effort (voltage or current applied to motor actuators) is limited to the range recommended for the particular motor (414). The following equation may be used to determine the distance at which feathered braking can be applied:
Velocity squared divided by two times the acceleration may provide an appropriate distance (errorPosition) which brakes need to be applied to stop at the correct position. In these equations, (errorPosition) is equal to the desired position minus the current position.
Once it has been determined the carrier is in the braking zone (determined by equation above), the feathered braking control method is used. An equation for control of the feathered braking may be
In this equation, (controlEffort) is the application of the brakes on the carrier, (errorPosition) is the distance of the carrier from the desired location, and (loopPeriod) is a number which allows the calculation to be scaled, as the calculation is typically made several times per second. The gain may be a suitable multiplier, and in one configuration a 1.4 multiplier may work. Suitable gains may be experimentally obtained for a specific configuration, depending on the type of motor, length of track, etc., and any suitable “gain” or multiplier may be used. This equation may allow additional braking to be applied if the carrier is not decelerating fast enough, and/or less braking to be applied in the carrier is decelerating too fast.
As the target carrier grows very close to the desired position as indicated by the rotary encoder, the movement computing software directs (412) the motor to apply very little force (again provided that the control effort is limited to the range recommended for the particular motor (414)). This “polishing mode” is typically entered into between 1 and 5 feet. An equation for calculating the distance in which polishing mode is entered is defined by the equation:
errorPosition<0=gain×currentVelocity+offset
According to experimental data, an appropriate gain may be 0.35, and an appropriate offset may be 400. The 0.35 factor is an experimentally obtained value, used to scale the number down according to experimentally obtained numbers. Any gain or appropriate factor may be used. The addition of 400 is also an experimentally obtained value, indicative of the appropriate offset. The 400 generally ensures that 400 millimeters away from the desired position will always be in polishing mode. Any appropriate offset value may be used.
When in this mode, the motion equation used may be
controlEffort=feed forward+(Vref−currentVelocity)×loopPeriod
This equation may allow lower maximum control effort values, which may result in slower and more fine-tuned control of the carrier when it is close to the desired position. The “feed forward” may be, for example, 300 where the particular VFD used cannot produce movement if the controlEffort is below 300. In this equation, Vref is ±600 when greater than 200 mm from the desired position, and ±300 when less than 200 mm away from the desired position. These particular values were experimentally obtained for a specific system, and one with skill in the art will appreciate that any suitable numbers for a particular system may be used for scaling the equations to that system.
This slow final stop step results in a polished look to the target carrier movement. The reduction in jolting or jarring stops reduces the risk of the target falling out of the target holder, and can reduce wear and tear on the system from stress induced by jolts or jerking, as well.
The movement computing software then calculates the deadband or error band (416)—that is, the difference between the target carrier's position as measured by the rotary encoder and the relative location of the proximity sensor. The deadband is the area contained within about 4 inches of the desired position. If the carrier is within about 4 inches of the desired position, it will report as being “at position” and will make no attempt to move the carrier. This may avoid “hunting” of the carrier, or the carrier moving back and forth across the desired position since it cannot be precise enough to achieve the position exactly. The deadband allows the carrier to stop and rest when it is “close enough” to the desired position. For example, during the calibration phase outlined above, if the proximity sensor triggered when the rotary encoder output was 2503, and now triggers when the rotary encoder output is 2505, the difference is 2. The movement computing software thus deducts 2 from the values reported by the rotary encoder, resulting in a target carrier system which self-calibrates with every pass over the proximity sensor.
In the event that the target carrier does not pass over the proximity sensor, despite repeated movement as reported by the rotary encoder, the movement computing software may flag the target carrier. This may occur if, for example, the target carrier is moved back and forth repeatedly but only over a small portion of the track each time. During a prolonged idle period, the movement computing software may therefore direct the target carrier to travel slowly down the length of the track to seek out the proximity sensor.
This self-calibration behavior prevents the location inaccuracies common in target carriers, which often resulted in the target carrier colliding repeatedly against an end stop at one end of the track. Because the collisions may damage even a robustly-built target carrier over time, the self-calibration of the present disclosure is a strong advantage.
If the motor, such as a VFD, needs to be disabled (418) (e.g., because an error has been detected) or enabled (e.g., due to timeout) the appropriate command (420) is sent to the motor and the loop is repeated. If the software determines that a directional change is required (422) in order to move the target carrier to the new position specified by the user, the movement computing software then directs (424) the motor to reverse directions and the loop is repeated.
If the direction does not need to be changed, and no enable/disable command is needed, the software then sends (426) the appropriate control effort adjustment command packet (calculated in one of steps 406, 408, 410, and 412) to the motor (a VFD, in the pictured embodiment) and repeats the loop. As drawn, the loop may limit the number of control packets sent to the motor to the response rate of the motor. However, the loop may be run more often than the response rate, and the results averaged over these loops. In the pictured embodiment, the loop is run at triple the motor's response rate. The result is particularly smooth-looking, crisp target carrier movement, further enhancing the aesthetic effect and reducing the chance that sudden jolting will jostle the target from the target carrier or damage the system.
The movement computing software then initializes (506) motion control, rotary encoder, and motor control receiver/transmitter (VFD UART (universal asynchronous receiver/transmitter) in the pictured embodiment) functionalities. Thereafter, the system initializes (508) standard driver and controller scripts (only the function USBController.c is listed in the image for clarity, however it will be appreciated that many such scripts may be initialized depending on the chipset and the programming language). One advantage of initializing several safety features, such as the proximity sensors and watchdog function (described in further detail below) before the main controllers is that the target carrier and motor will not be activated before the safety features are in place.
The movement computing software then adjusts (510) the states of indicator LEDs and outputs system status and debug information. In the pictured embodiment, the watchdog loop, generally indicated at 512, includes monitoring the status of Modbus® (or other serial communication protocol) tasks over RX channels. In general, the serial communication protocol slaves in the system (e.g., the motor and target carrier sensors and their associated transmitters/receivers, such as one or more UARTs) must respond to the movement computing software within about one second. If they do not, the watchdog loop 512 trips. The watchdog loop may either positively halt any other responding slaves in the RX channel, or the safety feature may be coded as a deadman trigger, in which a lack of communication from the movement computing software automatically halts or cuts power to all non-responsive slaves. Coding such software would be readily accomplished in light of the disclosure.
At 514, which may be executed in a parallel process, motor tasks are initialized (here indicated as VFD tasks). At 516, the movement computing software performs error checks, and sets any position, velocity, and acceleration boundaries as discussed in
It will be appreciated that, although the functions of
Turning now to
In order to present complex training scenarios, the target carriers 602 and 604 must move in a highly coordinated fashion—for example, when a shooter wishes to simulate a gunman hiding behind a hostage and simultaneously dragging the hostage along, or pushing the hostage away and running. Similar to the discussion in
The target carriers 602 and 604 may be self-driving or may be drawn along a cabled track, generally indicated at 610, by motors 612—in the pictured embodiment, the motors are variable frequency drives (VFDs), though other motors can be used. The motors 612 may include embedded controllers. The motors may include a radio-frequency (RF) transponder 614 or other transponder or output device, which is in electronic communication with a server (not shown) and a user control device 516, such as a tablet or phone.
As described in
In addition, the pictured embodiment of the target system includes a turning target carrier 620 and a pop-up target carrier, 624, equipped with sensors to monitor target position, in accordance with the present disclosure. The data from these may be distributed to the network message brokering bus, such as Modbus®, via receiver/transmitters 614. As previously discussed, a server may coordinate the messages sent to all receiver/transmitters 614 via the Modbus®, in order to raise or rotate the additional targets 622 when the target carriers 602 and 604 pass predetermined points. This synchronized behavior has the advantage of allowing a user to select challenging training scenarios from a controller 616 such as a tablet or laptop, such as a hostile gunman moving rapidly through a crowd. Synchronicity errors may be flagged as indicating that the slow target requires maintenance. Additionally, the system may accommodate and correct for small synchronicity errors by momentarily pausing or slowing the faster target units, until the slow one can catch up.
Thus, the constant monitoring of target positions and statuses as herein described enables the coordination of many types of targets to a common, user-programmable network. The fault-recognition functions of the software enable a training program to be aborted and the targets to be reset and flagged for maintenance, if synchronicity cannot be maintained.
A further advantage of the target system of the present disclosure is that the system is self-healing. Minor faults, such as a dropped transmission, may cause one target to momentarily move more quickly or more slowly (e.g., the watchdog loop 512 of
The system may also coordinate with a central network. For example,
It will be appreciated that the functional steps taken by the software has been disclosed above. These functional steps may be executed by various modules, or equivalent functional units. Modules are at least partially implemented in hardware, in one form or another. For example, a module may be implemented in a processor have a hardware circuit comprising custom VLSI circuits or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components. A module may also be implemented in programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices or the like.
Modules may also be implemented using software, stored on a physical storage device (e.g., a computer readable storage medium), for execution by various types of processors. Reference to a computer readable storage medium may take any physical form capable of storing machine-readable instructions, at least for a time in a non-transient state, on a digital processing apparatus. Examples of a computer readable storage medium include, but are not limited to, a semiconductor or solid state memory, magnetic tape, a removable computer diskette, a random access memory (RAM), a read-only memory (ROM), a Bernoulli drive, ARDUINO, a magnetic disk, flash memory, integrated circuits, or other digital processing apparatus memory device, and an optical disk. Current examples of optical disks include a compact disk with read only memory (CD-ROM), a compact disk with read/write (CD-R/W), and a digital video disk (DVD).
An identified module of executable code may, for instance, comprise one or more physical or logical blocks of computer instructions which may, for instance, be organized as an object, procedure, or function. Nevertheless, the executables of an identified module need not be physically located together, but may comprise disparate instructions stored in different locations which, when joined logically together, comprise the module and achieve the stated purpose for the module. Software modules may include script, batch, or other executable files that may be stored on a computer-readable storage medium or in a computing system. In some embodiments, these software modules may configure a computing system to perform one or more of the exemplary embodiments disclosed herein.
Indeed, a module of executable code may be a single instruction, or many instructions, and may even be distributed over several different code segments, among different programs, and across several storage or memory devices. Similarly, operational data may be identified and illustrated herein within modules, and may be embodied in any suitable form and organized within any suitable type of data structure. The operational data may be collected as a single data set, or may be distributed over different locations including over different storage devices, and may exist, at least partially, merely as electronic signals on a system or network. Where a module or portions of a module are implemented in software, the software portions are stored on one or more physical devices which are referred to herein as computer readable media and/or electronic data storage devices.
In some embodiments, the software portions are stored in a non-transitory state such that the software portions, or representations thereof, persist in the same physical location for a period of time. Additionally, in some embodiments the software portions are stored on one or more non-transitory storage devices, which include hardware elements capable of storing non-transitory states and/or signals representative of the software portions, even though other portions of the non-transitory storage devices may be capable of altering and/or transmitting the signals. One example of a non-transitory storage device includes a read-only memory (ROM) which can store signals and/or states representative of the software portions for a period of time. However, the ability to store the signals and/or states is not diminished by further functionality of transmitting signals that are the same as or representative of the stored signals and/or states. For example, a processor may access the ROM to obtain signals that are representative of the stored signals and/or states in order to execute the corresponding software instructions.
Furthermore, the described features, structures, functions or characteristics of embodiments or implementations of the invention may be combined in any suitable manner in one or more embodiments or implementations. One skilled in the relevant art will recognize, however, that the invention may be practiced without one or more of the specific details, or with other methods, components, materials, and so forth. In other instances, well-known structures, materials, or operations are not shown or described in detail to avoid obscuring aspects of the invention.
The schematic flow chart diagrams discussed above are generally set forth as logical flow chart diagrams. As such, the depicted order and labeled operations are indicative of one embodiment of the presented method. Other operations and methods may be conceived that are equivalent in function, logic, or effect to one or more operations, or portions thereof, of the illustrated method. Additionally, the format and symbols employed are provided to explain the logical operations of the method and are understood not to limit the scope of the method. Although various arrow types and line types may be employed in the flow chart diagrams, they are understood not to limit the scope of the corresponding method. Indeed, some arrows or other connectors may be used to indicate only the logical flow of the method. For instance, an arrow may indicate a waiting or monitoring period of unspecified duration between enumerated operations of the depicted method. Additionally, the order in which a particular method occurs may or may not strictly adhere to the order of the corresponding operations shown.
Although the operations of the methods herein are shown and described in a particular order, the order of the operations of each method may be altered so that certain operations may be performed in an inverse order or so that certain operations may be performed, at least in part, concurrently with other operations. In another embodiment, instructions or sub-operations of distinct operations may be implemented in an intermittent and/or alternating manner.
Those skilled in the art will recognize various modifications which could be made to the embodiments disclosed herein without departing from the scope and spirit of the invention. The following claims are intended to cover such modifications.
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. Accordingly, the claims are not limited by the disclosure.
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 | Parnail | 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 |
2483690 | Carlson | Oct 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 | Valkenburg | Apr 1955 | A |
2809836 | Clair | 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 |
3443505 | Kaufman | May 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 |
3650179 | Stenger | Mar 1972 | A |
3720138 | Van Scoy | Mar 1973 | A |
3720411 | Vogelaere | Mar 1973 | A |
3755942 | Samsing | Sep 1973 | A |
3802098 | Sampson et al. | Apr 1974 | A |
3889466 | Castela et al. | Jun 1975 | 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 |
4177835 | Paley | Dec 1979 | A |
4182094 | Leider et al. | Jan 1980 | A |
4184802 | Cook et al. | Jan 1980 | 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 |
4524976 | Seitz et al. | Jun 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 |
4786059 | Barini | Nov 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 |
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 |
5768972 | Christenson et al. | 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 |
5848791 | Beyer | Dec 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 |
5967522 | Corcoran et al. | 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 |
7114725 | Camp | Oct 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 |
7448967 | Panneri | Nov 2008 | B1 |
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 |
7823466 | Glass | Nov 2010 | B2 |
7914004 | Wright et al. | Mar 2011 | B2 |
7950666 | Stincelli et al. | May 2011 | B2 |
8006981 | Gibson | Aug 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 |
8806952 | Glass | Aug 2014 | B1 |
8813401 | Diercks | Aug 2014 | B2 |
8827273 | John et al. | Sep 2014 | B2 |
9157706 | Shea | Oct 2015 | B2 |
9217623 | Sovine et al. | Dec 2015 | B2 |
9228810 | Bateman et al. | Jan 2016 | B2 |
9360283 | Tejada | Jun 2016 | B1 |
9482498 | Miller | Nov 2016 | B1 |
9513091 | Roberts | Dec 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 |
20070234800 | Stout et al. | Oct 2007 | A1 |
20080047365 | Hsieh | Feb 2008 | A1 |
20080185786 | Loveland et al. | Aug 2008 | A1 |
20080216645 | Jacobsen et al. | Sep 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 |
20110024985 | Potterfield | Feb 2011 | A1 |
20110062668 | Leimberer | Mar 2011 | 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 |
20140138916 | Wright et al. | May 2014 | A1 |
20140232068 | Henson et al. | Aug 2014 | 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 |
20160209182 | Sovine et al. | Jul 2016 | A1 |
20160209184 | Anderson et al. | Jul 2016 | A1 |
20170350677 | Sovine et al. | Dec 2017 | A1 |
20180172409 | Anderson et al. | Jun 2018 | A1 |
20180180372 | Scott et al. | Jun 2018 | A1 |
20180180373 | Scott et al. | Jun 2018 | A1 |
20180202777 | Green et al. | Jul 2018 | A1 |
20180209767 | Anderson et al. | Jul 2018 | A1 |
20180299232 | Thompson | Oct 2018 | A1 |
20190145172 | Parker | May 2019 | A1 |
20190212107 | Sharp et al. | Jul 2019 | A1 |
20190219369 | Harmon et al. | Jul 2019 | A1 |
20190219370 | Anderson et al. | Jul 2019 | A1 |
20200208947 | DeCosta et al. | Jul 2020 | A1 |
Number | Date | Country |
---|---|---|
2100631 | Feb 1994 | CA |
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. |
Metal Spinning Target, Inc., Dueling Trees, Jul. 8, 2003. |
Mike Gibson Manufacturing, Dueling Tree, Jul. 8, 2003. |
Outwest MFG. Products, Product Literature, Jul. 8, 2003. |
Porta Target, Product Literature, Circa 2000. |
Shootrite, Tactical Training Target, published prior to Apr. 4, 2005. |
Action Target DRM Pro, available at <https://www.actiontarget.com/products/drm_pro/>. |
Number | Date | Country | |
---|---|---|---|
20210208557 A1 | Jul 2021 | US |
Number | Date | Country | |
---|---|---|---|
62446424 | Jan 2017 | US | |
62446281 | Jan 2017 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 15867584 | Jan 2018 | US |
Child | 17120669 | US |