US20160195369A1

US20160195369A1 - Automated target system and method

Info

Publication number: US20160195369A1
Application number: US14/986,190
Authority: US
Inventors: Kyle Perry; William R. Seely
Original assignee: Kyle Perry; William R. Seely
Current assignee: Battleboxxx (mo) LLC
Priority date: 2015-01-02
Filing date: 2015-12-31
Publication date: 2016-07-07

Abstract

A target enclosure is provided. The target enclosure includes a target arm rotatable about a first axis between a first position and a second position. The target arm includes a target plate configured to be exposed to projectile fire of a shooter when in the first position, and a counterbalance lever arm coupled to the target plate. The target enclosure also includes a pneumatic system. The pneumatic system includes an air compressor providing compressed air to the pneumatic system. The pneumatic system also includes a dual-action pneumatic cylinder having a piston rod, the piston rod being coupled to the counterbalance lever arm. The pneumatic system further includes at least one valve configured to provide the compressed air to the cylinder causing the piston rod to actuate between an extended state and a retracted state, thereby causing the target arm to rotate between the first position and the second position.

Description

RELATED APPLICATIONS

This application claims the benefit of priority to U.S. Provisional Patent Application Ser. No. 62/099,354, filed Jan. 2, 2015, and to U.S. Provisional Patent Application Ser. No. 62/194,536, filed Jul. 20, 2015, both of which are herein incorporated by reference in their entirety.

TECHNICAL FIELD

The subject matter disclosed herein relates generally to target shooting and, more specifically, to target shooting systems and methods for training, tracking, and improving shooting accuracy.

BACKGROUND

Target shooting is both a sport enjoyed recreationally by civilians as well as a skill discipline practiced professionally by, for example, law enforcement personnel and members of the armed services. Shooters traditionally practice with firearms such as pistols, rifles, and shotguns, or air-powered guns such as pellet or BB guns. Target practice sessions may be conducted at a special facility, such as a shooting range, that is designed to reduce some risks associated with such weapons. The shooting range, for example, may provide one or more “gun ranges” that present an area in which the shooter or the range may set up a target with which the shooter can practice.
Some known shooting systems include steel plates that may be positioned vertically and presented to the shooter as a target. During shooting practice, the shooter may fire one or more shots at the steel target plate. Upon being struck, the momentum of the projectile may be sufficient to knock the plate down, as well as produce an audible noise based on the impact. As such, the shooter is able to perceive when he hits the target with a particular shot.

BRIEF DESCRIPTION OF THE DRAWINGS

Various ones of the appended drawings merely illustrate example embodiments of the present disclosure and cannot be considered as limiting its scope.

FIGS. 1-5 illustrate example embodiments of the methods and systems described herein, in which like characters represent like parts throughout the drawings.

FIG. 1 is a perspective view of an example target enclosure.

FIG. 2 is a perspective view of the example target enclosure shown in FIG. 1.

FIG. 3 is a perspective view of the example target enclosure shown in FIGS. 1 and 2.

FIG. 4 is a side view of the target enclosure as seen from a left side perspective.

FIG. 5 is a diagram of an example shooting system that includes a target set including three of the target enclosures shown in FIGS. 1-4.

FIG. 6A is a rear right-side perspective view illustrating target enclosure with a target arm in an upright position.

FIG. 6B is a rear right-side perspective view illustrating target enclosure as shown in FIG. 6A, but excluding some components of target enclosure, such as right side plate, rear plate, and rear cover, for purposes of illustration (e.g., to better reveal the interior of target enclosure).

FIG. 7 is a perspective view of target enclosure in a down position, with the air cylinder extended, or pushed out (e.g., after a “push action”).

FIG. 8 is a rear left-side perspective view illustrating target enclosure, but excluding some components of target enclosure, such as left side plate, rear cover, and rear plate, for purposes of illustration (e.g., to better reveal the interior of target enclosure).

FIG. 9 illustrates a computerized method, in accordance with an example embodiment, for providing a training routine for a shooter.

FIG. 10 is a block diagram illustrating an example software architecture, which may be used in conjunction with various hardware architectures herein described

FIG. 11 is a block diagram illustrating components of a machine, according to some example embodiments, able to read instructions from a machine-readable medium (e.g., a machine-readable storage medium) and perform any one or more of the methodologies discussed herein.

The headings provided herein are merely for convenience and do not necessarily affect the scope or meaning of the terms used. Like numbers in the Figures indicate like components.

DETAILED DESCRIPTION

The description that follows includes systems, methods, techniques, instruction sequences, and computing machine program products that embody illustrative embodiments of the disclosure. In the following description, for the purposes of explanation, numerous specific details are set forth in order to provide an understanding of various embodiments of the inventive subject matter. It will be evident, however, to those skilled in the art, that embodiments of the inventive subject matter may be practiced without these specific details. In general, well-known instruction instances, protocols, structures, and techniques are not necessarily shown in detail.
Embodiments of the present disclosure provide automatic target systems and methods for tracking and improving shooting accuracy. In some example embodiments, an automatic target system is provided. The target system includes a target enclosure having a target arm that swings from a horizontal or “down” position to a vertical or “upright” position. The target arm is controlled or acted upon by a gear assembly or an air or hydraulic cylinder that can perform both a “push action” to cause the target arm to fall into the down position, as well as a “pull action” to cause the target arm to rise to the upright position. The gear assembly or air or hydraulic cylinder is controlled by an “onboard” microcontroller (e.g., within the target enclosure).
In some embodiments, the microcontroller is communicatively coupled to a nearby “remote” control unit which generates raise and lower action commands or events (e.g., when to raise and lower the target arm). The target system is configured to present the shooter with a shooting “simulation” that includes a series of operations automatically raising and lowering of the target in a random pattern, or in some other pre-determined pattern that may or may not be known to the shooter. In other words, the target system may raise the target at one time, and then lower the target at a later time (e.g., if the shooter has not struck the target within 3 seconds of the raise event).
In some embodiments, the target system also includes a piezoelectric sensor, or “hit sensor”, that detects when a shot has struck the target. This hit detection is transmitted to the remote control unit, and may be used to compute accuracy of the shooter. Further, in some embodiments, a shooting system is provided that includes a plurality of target enclosures, such as three target enclosures sitting side-by-side. For example, the target system may be configured to present a shooting event to the shooter over the course of 30 seconds. The shooting system may be configured to raise each of the three targets at various times during the simulation. The control unit generates the actions for each of the three targets a number of times during the shooting event, and the hit counter determines the number of times each particular target was struck. The target system may then present the shooter with an accuracy measurement related to, for example, how many targets were missed. The target system may be configured with various parameters such as, for example, the duration of the shooting event, the number of targets each enclosure is to present during the shooting event, and the pattern or timing of presentation of targets. As such, the target system may be used to collect accuracy information of the shooter, both at the time of a given shooting event, as well as over time. This information may be used to track accuracy performance and skill evaluation.
As used herein, an element or step recited in the singular and proceeded with the word “a” or “an” should be understood as not excluding plural elements or steps unless such exclusion is explicitly recited. Furthermore, references to “one embodiment” of the present invention are not intended to be interpreted as excluding the existence of additional embodiments that also incorporate the recited features.
FIG. 1 is a perspective view of an example target enclosure 100. In the example embodiment, target enclosure 100 includes a front guard plate 102 disposed at a front end 120 of enclosure 100. Target enclosure 100 also includes a left side plate 104 and a right side plate 108 (not visible in FIG. 1). Enclosure 100 further includes a splatter guard 106 covering a portion of enclosure 100 along a top side 130, and a rest bar 112 at a rear end 140 of enclosure 100.
Enclosure 100 also includes a target plate 110. In the example shown in FIG. 1, target plate 110 is illustrated in an upright position in which a front surface 111 target plate 110 is exposed to a target shooter 150 wielding a projectile weapon 152 such as, for example, firearms such as pistols or rifles, air-powered weapons such as pellet, BB, or paintball guns, and bow weapons such as compound bows or crossbows. In the example embodiment, projectile weapon 152 is a .38 caliber revolver firing 148 grain lead “wadcutter” bullets at a load generating approximately a 700 foot per second (fps) muzzle velocity (e.g., a common “match load” used in competitive shooting). Further, in the example embodiment, target plate 110 is made of a hardened steel. In some embodiments, target plate 110 is made of a hardened steel having a Brinell value of approximately 500 or more. In other embodiments, target plate 110 may be made of a material having a Brinell value less than 500, such as certain irons or aluminums, which may be suitable for projectiles having lower kinetic energy and/or penetration potential such as, for example, pellets, BBs, and paintballs.
In the example embodiment, front guard plate 102 is made of hardened steel. In some embodiments, front guard plate 102 is made of hardened steel having a Brinell value of approximately 500 or more. Front guard plate 102 may improve protection of internal components of enclosure 100 from, for example, shots fired by shooter 150. In some embodiments, enclosure 100 does not include a front guard plate 102, or includes a front guard plate 102 that is less resistant to penetration. For example, enclosure 100 may be deployed behind a barrier (not shown) such as a natural or artificial berm or wall such that only portions of target plate 110 are exposed to shooter 150 during operation, and the barrier facilitates protection of internal components of enclosure 100. Further, in the example embodiment, front guard plate 102 is removably coupled to enclosure 100 such as to facilitate, for example, ease of access to internal components and/or cleaning of enclosure 100.
During operation, target enclosure 100 is in proximity to shooter 150, for example at a shooting range. In the example embodiment, target enclosure 100 presents target plate 110 to shooter 150 in an “upright” or “exposed” position (e.g., approximately vertical, and/or approximately perpendicular to a line of fire of shooter 150), and shooter 150 attempts to hit target plate 110 by firing one or more projectiles (e.g., bullets) at target plate 110. Upon a projectile hitting target plate 110, target plate 110 is configured to fall backward, propelled by a transfer of kinetic energy from the projectile to target plate 110. When in the down position, target plate 110 rests on rest bar 112.
In the example embodiment, target plate 110 is configured to swing into a “down” or “unexposed” position (e.g., approximately horizontal, and/or approximately parallel to line of fire 150) upon a successful “hit” (i.e., a projectile striking target plate 110). In some embodiments, as projectiles strike front surface 111 of target plate 110, the projectiles may fragment or shatter, causing portions of the projectiles to shower the nearby area. Splatter guard 106 facilitates prohibiting at least some fragments of projectiles from entering an interior of target enclosure.
In the example embodiment, upon a successful hit, target plate 110 is configured to remain in the down position for a period of time. Additional details regarding additional target plate 110 movement and actions performed by target enclosure 100 are described in greater detail below.
FIG. 2 is a perspective view 200 of example target enclosure 100 shown in FIG. 1. In the example embodiment, perspective view 200 excludes left side plate 104 (shown in FIG. 1) to better reveal an interior 204 of target enclosure 100. Target enclosure 100 includes three corner supports 202 that, together with rest bar 112, connect right side plate 108 to left side plate 104, thereby forming at least some of the structure of target enclosure 100. Target enclosure 100 includes three main components and/or assemblies that interact to provide at least some of the features and benefits described herein: a target arm 210, a gear assembly 240, and a detent 220.
In the example embodiment, target arm 210 includes target plate 110 coupled to a counterbalance 212. As described above in reference to FIG. 1, target arm 110 includes a front surface 111, a portion of which is exposed to projectile fire during operation (e.g., when in the upright position shown in FIG. 2). Counterbalance 212 includes an L-shaped body 214 and a shaped push wedge 216. Shaped push wedge 216 defines a push surface 218. In the example embodiment, shaped push wedge 216 defines a convex push surface 218. In some embodiments, push surface 218 may be a linear in shape, which may, for example, simplify manufacturing of the component. In other embodiments, push surface 218 may be concave in shape, which may, for example, allow application of force to the push surface for a longer time, as it may keep contact as the target rotates.
In the example embodiment, target arm 210 is fixedly coupled to a target arm bar 230 that extends between right side plate 108 and left side plate 104. Target arm bar 230 enables target arm 210 to rotate about a target arm bar axis (not shown in FIG. 2). More specifically, and in the example embodiment, target arm bar 230 enables target arm 210 to rotate through approximately 90 degrees of rotation. The rotational range of target arm 210 is bordered by a stopping edge 226 of splatter plate 106 (e.g., when in the upright position shown in FIG. 2) and rest bar 112 (e.g., when in a down position). In other words, when target arm 210 rotates to the upright position, rotation of target arm 210 is stopped by stopping edge 226 (e.g., when front surface 111 makes contact with stopping edge 226). Similarly, when target arm 210 rotates to the down position, rotation of target arm 210 is stopped by rest bar 112 (e.g., when a rear surface (not shown in FIG. 2) of target arm 210 makes contact with rest bar 112.
As discussed herein, the upright position shown in FIGS. 1 and 2 is described as approximately a 90 degree angle, and the down position is described as approximately a 180 degree angle (e.g., target arm 210 rotates between 90 degrees (upright) and 180 degrees (down)). Further, as discussed herein, rotational direction is referred to using “clockwise” and “counter-clockwise” in relation to a leftside view (e.g., the approximate left-side view shown in FIG. 2). In other words, target arm 210 rotates clockwise to get to the upright position and counterclockwise to get to the down position.
In the example embodiment, target enclosure 100 includes detent 220. Detent 220, in the example embodiment, is a ball detent that includes a ball component 224 configured to roll in place, and is not compliant. In some embodiments, detent 220 may be pressed outward by an internal spring. Detent 220 is coupled to right side plate 108 such that a center (not separately shown) of detent 220 is set slightly forward (e.g., toward front side 120) of a right side edge 222 of target arm 210 when target arm 210 is in the upright position. Further, detent 220 and target arm 210 are configured relative to each other such that ball component 224 is configured to make contact with and hamper rotation of target arm 210.
In the example embodiment, target arm bar 230 includes a shaft (not shown in FIG. 2) welded to target arm 210. The shaft is free to spin inside bearings or bushings installed in side plates, thus allowing target arm 210 to rotate between upright and down positions. Target arm bar 230 also includes a spring on an opposite side from detent 220. Target arm 210 is configured to slide axially along an axis of target arm bar 230 (e.g., toward and/or away from right side plate 108). In the example embodiment, the “slide range”, or distance that target arm 210 may slide (e.g., left to right) is less than 1 inch. During operation, the spring acts as a force pushing and/or holding target arm 210 toward right side plate 108. As target arm 210 (e.g., right side edge 222 of counterbalance 212) encounters detent 220 (e.g., when in transition between upright and down positions), ball component 224 tends to push target arm 210 away from right side plate 108. The spring and axial slide of target arm 210 allows detent 220 to push target arm 210 to the left as counterbalance 212 passes detent. Once past, the spring again tends to push and/or hold target arm 210 toward right side plate 108. As such, the spring acts as a resistant force countering detent 220, and the slide range of target arm 210 provides the flexibility to both assist target arm 210 to rotate past detent 220 when enough rotational force is applied (e.g., when being pushed by actuator arm 270, but also allows detent 220 to resist rotation of target arm 210 when not enough rotational force is applied (e.g., during elastic rebound of target arm 210 after being raised to upright position.
Further, in the example embodiment, detent 220 inhibits rotation of target arm 210 from a range between approximately 90 and 95 degrees. This “wiggle range” is provided by the positioning of detent 220 such that target arm 210 may rotate from 90 degrees (e.g., upright) through the wiggle range before coming into contact with detent 220. In some embodiments, the wiggle range may be less than 10 degrees, or less than 5 degrees, or any range between 0 and 5 degrees. During operation, when target arm 210 transitions between down position and upright position (e.g., rotating clockwise), rotational speed and/or momentum of target arm 210 carry right side edge 222 of target arm 210 past or through detent 220 (e.g., allowing target arm 210 to become fully upright, and be stopped by stopping surface 226), but detent 220 facilitates resisting a rotational “bounce-back” or reciprocal counter-rotation based on, for example, elasticity of the collision between target arm 210 and splatter shield 106 (e.g., occurring after target arm 210 strikes stopping surface 226). As such, target arm 210 is maintained in an approximately upright position (e.g., at approximately 90 degrees, and/or within the wiggle range), assisted by detent 220 in at least some situations.
In the example embodiment, gear assembly 240 includes a servo unit (“servomechanism” or just “servo”) 250 enclosed within a servo mount bracket 252. Servo 250 provides angular position control for a servo gear 254 that is fixedly coupled to a servo arm 256. In the example embodiment, servo 250 is an HS-7954SH (commercially available from Hitec RCD USA, Inc., of Poway California), modified for 360 degrees rotation, and the servo mount is a bottom mount gearbox with a 3:1 gear ratio, and a large gear OD of 2.25 inches. Servo arm 256 includes a pin 258 disposed within a slide slot 272 of an actuator arm 270. Actuator arm 270 is coupled to a pivot bar 274 that enables actuator arm 270 to pivot through an angular range of motion, and in the same plane of motion of target arm 210 (e.g., pivot bar 274 is approximately parallel to target arm bar 230, in a plane including axes of both bars 274, 230). More specifically, actuator arm 270 is positioned on a plane of motion with shaped push wedge 216 of counterbalance 212 such that, during rotation, actuator arm 270 may contact shaped push wedge 216 on push surface 218 (e.g., when target arm 210 is in the upright position as shown in FIG. 2). In other words, the distance between actuator arm 270 and right side plate 108 is approximately the same as the distance between shaped push wedge 216 and right side plate 108.
In the example embodiment, servo 250 controls the rotational motion and angular position of actuator arm 270. As servo arm 256 rotates, pin 258 causes actuator arm 270 to rotate as well. Further, pin 258 slides radially inward and outward, relative to pivot bar 274, within slide slot 272. For description purposes, a similar frame of reference is used to describe the angular position of actuator arm 270 herein as is used to describe the angular position of target arm 210. In other words, if actuator bar 270 is rotated to a forward horizontal position, that angular position would be described as zero degrees, and if actuator bar is rotated to a vertical position similar to the upright position of target plate 210 as shown in FIG. 2, the angle of actuator bar 270 would be described as 90 degrees. As shown in FIG. 2, the angle of actuator bar 270 is at approximately 75 degrees.
Further, in the example embodiment, servo 250 is mounted to right side plate 108 such that the rotational axis of servo gear 254 is positioned a distance forward of, and another distance above, servo gear 254 (and servo arm 256). Servo arm 256 is at approximately the same angle as actuator arm 270 when actuator arm 270 is at approximately 75 degrees (the “aligned position”). As such, pin 258 is at its radially outward-most point relative to pivot bar 274 when servo arm 256 and actuator arm 270 are “aligned” (e.g., approximately zero degrees difference between servo arm 256 and actuator arm 270). In other words, as servo bar 256 rotates, either counterclockwise or clockwise from the aligned position, pin 258 becomes closer to pivot bar 274. As such, gear assembly 240 provides varying degrees of, e.g., angular speed and angular acceleration, of a radially outward end 278 of actuator arm 270.
In the example embodiment, target enclosure 100 also includes a pull chain (not shown in FIG. 2). The pull chain is coupled (e.g., on one end) to outward end 278 of actuator arm 270 (the “servo end” of the pull chain), such as connected via a clip or spring through chain hole 276. The pull chain is also coupled (e.g., on an opposite end) to target arm 210. In the example embodiment, the pull chain is coupled to connection point 219 on a side surface of push wedge 216.
During operation, gear assembly 240 exerts two types of motive actions on target arm 210: a “push” action and a “pull” action, both of which impute force to target arm 210 through actuator arm 270. The push action is available and occurs primarily when target arm 210 is in the upright position (e.g., as shown in FIG. 2). The push action occurs when actuator arm 270 is rotated clockwise (e.g., from the aligned position shown in FIG. 2) such that contact is made between outward end 278 of actuator arm 270 and push surface 218 of push wedge 216, “pushing” on counterbalance 212, thereby causing target arm 210 to rotate counterclockwise (e.g., toward, and ultimately into, the down position). The pull action is available and occurs primarily when target arm 210 is in the down position (not shown in FIG. 2). The pull action occurs when actuator arm 270 is rotated counterclockwise (e.g., from the aligned position) such that actuator arm 270 brings the pull chain taught and “pulls” on counterbalance 212 (e.g., at connection point 219), thereby causing target arm 210 to rotate clockwise (e.g., toward, and ultimately into, the upright position).
In the example embodiment, target enclosure 100 includes a power source (not shown in FIG. 2), a controller (not shown in FIG. 2), and a communications interface (not shown in FIG. 2). The power source powers one or more of servo 250, the controller, and the communications interface. In some embodiments, the power supply is an electrochemical battery. In other embodiments, the power supply is an alternating current (AC) or a direct current (DC) power supply (e.g., connected to a conventional power distribution network or a power generator). The controller, in the example embodiment, is an Arduino® Pro Mini microcontroller communicatively coupled to servo 250 and the communications interface (commercially available from Arduino LLC, Massachusetts, USA). The communications interface, in the example embodiment, is an XBee® Pro 900HP radio module (Digi International Inc., Delaware, USA) with an RP-SMA antenna. It should be understood that the example power source, controller, and communications interface are merely examples, and that any power source, controller, and communications interface that enables the systems and methods described herein may be used.
FIG. 3 is a perspective view 300 of example target enclosure 100, also shown in FIGS. 1 and 2. In the example embodiment, perspective view 300 excludes left side plate 104 (shown in FIG. 1) to better reveal an interior 204 of target enclosure 100. Perspective view 300 again illustrates target arm 210 in an upright position, and prepared for a “push” action as described above in reference to FIG. 2.
During a push action, in the example embodiment, and as described above, servo 250 rotates actuator arm 270 clockwise (e.g., from the “aligned position”), causing outward end 278 of actuator arm 270 to make contact with push surface 218. More specifically, FIG. 3 illustrates a push range 318 along push surface 218, bordered by an upper contact position 319 a and a lower contact position 319 b. Upper contact position 319 a represents where actuator arm 270, while rotating clockwise, first makes contact with target arm 210 during a push action. When actuator arm 270 first makes contact with push surface 218 during a push operation (e.g., at position 319 a), actuator arm 270 defines an angle referred to herein as the “actuator arm initial push angle”, and servo arm 256 (shown in FIG. 2) defines an angle referred to herein as the “servo arm initial push angle.” As servo 250 continues to rotate actuator arm 270 clockwise, outward end 278 of actuator arm 270 slides along push range 318 of push surface 218 until contact between actuator arm 270 and target arm 210 is lost. When actuator arm 270 last makes contact with push surface 218 during a push action, actuator arm 270 defines an angle referred to herein as the “actuator arm final push angle,” and servo arm 256 defines an angle referred to herein as the “servo arm final push angle.”
In the example embodiment, servo 250 drives actuator arm 270 slightly past the actuator arm final push angle (e.g., to zero degrees) before reversing rotational direction of actuator arm 270 and returning actuator arm to, for example, a neutral position and/or the aligned position. During the push operation, servo 250 drives actuator arm 270 through push range 318 such as to cause target arm 210 to rotate counterclockwise. More specifically, in some embodiments, the force of rotation of actuator arm 270 and/or the actuator arm final push angle is sufficient to at least rotate target arm 210 past detent 220. Further, in some embodiments, the rotational velocity and/or momentum imparted to target arm 210 by actuator arm 270 is sufficient to cause enough rotation of target arm 210 to allow a center of gravity of target plate 110 (e.g., associated with the mass of target arm 210 above target arm bar 230) to overcome a center of gravity of counterbalance 212 (e.g., associated with the mass of target arm 210 below target arm bar 230). This push action causes target arm bar 210 to transition from the upright position, past the detent, and into the down position. In other words, in the example embodiment, target arm 210 is “top heavy”, or balanced such that target arm 210 tends to fall toward the down position and naturally remain at rest there due, at least in part, to gravity.
FIG. 4 is a side view 400 of target enclosure 100 as seen from a left side perspective. Side view 400 excludes left side plate 104 (shown in FIG. 1) to better reveal an interior 204 of target enclosure 100.
In the example embodiment, side view 400 illustrates an upright position 410 of target arm 210 in solid line, as well as a down position 420 of target arm 210 in dashed line. As described above, target arm 210 transitions between these two positions during operation. For example, target arm 210 may transition from upright position 410 to down position 420 after being struck by a projectile fired by shooter 150 (shown in FIG. 1), or may be automatically pushed counterclockwise toward down position 420 by actuator arm 270 (a “push” or “lower” event, as described above). While in down position 420, target arm 210 may transition from down position 420 into upright position 410, for example, by actuator arm 270 pulling target arm 210 clockwise (a “pull” or “raise” event, as described above).
Target arm 210, upright position 410, and down position 420 are referenced herein relative to a target arm axis “A”. In the example embodiment, target arm 210 is at an upright angle α₁of approximately 90 degrees, and target arm 210 is at a down angle α₂of approximately 180 degrees. As such, target arm 210 pivots between approximately 90 and 180 degrees.
Side view 400 also illustrates the range of actuator arm 270 during operation in the example embodiment. Side view 400 illustrates a “neutral position” 450 of actuator arm 270 in solid line, and a “minimum actuator position” 460 and a “maximum actuator position” 470 of actuator arm 270 in dashed line. Neutral position 450 represents the position of actuator arm 270 when not engaged in a push operation or a pull operation. In other words, and in the example embodiment, after a push or pull operation, actuator arm 270 may be returned to neutral position 450. As such, neutral position 450 also represents the starting position for at least some push and pull operations.
Actuator arm 270, neutral position 450, minimum actuator position 460, and maximum actuator position 470 are referenced herein relative to an actuator arm axis “B”. In the example embodiment, actuator arm 270 is at an angle (not shown) of approximately 0 degrees when at minimum actuator position 460. When at neutral position 450, actuator arm 270 is at neutral angle (e.g., 45 degrees in the example embodiment). A push angle β₁represents the rotational change when actuator arm 270 rotates through a push action. In other words, during a push action, servo 250 (shown in FIGS. 2 and 3) rotates actuator arm 270 from neutral position 450, through β₁degrees of clockwise rotation, to minimum actuator position 460 and back to neutral position 450 thereby, for example, pushing target arm 210 past detent 220 and causing target arm 210 to fall to down position 420. When at maximum actuator position 470, actuator arm is at a maximum angle (β₁+β₂), where β₂represents the rotational change when actuator arm 270 rotates through a pull action. In other words, during a pull action, servo 240 rotates actuator arm 270 from neutral position 450, through β₂degrees of counterclockwise rotation, to maximum actuator position 470 and clockwise back to neutral position 450 thereby, for example, pulling target arm 210 from down position 420 past detent 220 and into upright position 410. In the example embodiment, the neutral position 450 is approximately 45 degrees from axis B, the push angle β₁is approximately 45 degrees, and the pull angle β₂is approximately 50 degrees. In another embodiment, the neutral position 450 is approximately 45 degrees from axis B, the push angle β₁is approximately 10 degrees, and the pull angle β₂is approximately 50 degrees.
As described above, actuator arm 270 is coupled to target arm 210 via a chain (not shown) connecting chain hole 276 and connection point 219. In the example embodiment, the pull chain is at least as long as a distance (not separately identified in FIG. 4) between chain hole 276 when actuator arm 270 is in neutral position 450 and connection point 219 when target arm 210 is in down position 410. Further, the pull chain is no longer than a distance (not separately identified in FIG. 4) between chain hole 276 when actuator arm 270 is in maximum actuator position 470 and connection point 219 when target arm 210 is in down position.
In the example embodiment, when target arm 210 is in upright position 410 and actuator arm 270 is in neutral position 450, the pull chain dangles loose between chain hole 276 and connection point 219. When target arm 210 is in down position 420 and actuator arm 270 is in neutral position 450, the pull chain also dangles loose between chain hole 276 and connection point 219. During a pull action, for example initiated when target arm 210 is in down position 420 and actuator arm 270 is in neutral position 450, actuator arm 270 is rotated through a first, counterclockwise phase, and then through a second, clockwise phase, by servo 250 (e.g., through β₂).
Continuing the pull action example, actuator arm 270 continues to rotate counterclockwise until actuator arm 270 reaches maximum actuator position 470 (e.g., between approximately 45 degrees and approximately 105 degrees). During this phase, referred to herein as the “pull stroke,” actuator arm 270 is exerting a force on target arm 210 and, more particularly, counterbalance 212 at connection point 219. This force causes a moment of force on target arm 210 (e.g., rotating about target arm bar 230 (shown in FIG. 2). The pull force generated on target arm 210 and, more particularly, the momentum generated in target arm 210 by the end of the pull stroke causes target arm 210 to swing through detent 220 and into upright position 210. The pull force and momentum generated is not so much as to enable the elastic bounce-back of target arm 210 to overcome detent 220 after the bounce-back. In other words, the power of the pull stroke is configured, relative to one or more of the mass of target arm 210 and configuration of detent 220 relative to target arm, within a range that enables target arm 210 to reach, and stay in, upright position 210.
In some situations, actuator arm 270 may be subjected to forces other than from servo 250 (a “counter-force”). For example, target arm 210 is configured to be struck by projectiles on front surface 211 (shown in FIGS. 1 and 2). When a projectile strikes target plate 210, the projectile exerts a moment of force on target plate 210 tending to cause a counterclockwise rotation (e.g., causing target plate 210 to fall from upright position 410 to down position 420). Because counterbalance 212 is a component of target arm 210, this also causes counterbalance 212 to rotate as well. As described above, counterbalance 212 is coupled to actuator arm 270 by the pull chain. If actuator arm 270 is in neutral position 450 as shown in FIG. 4 and the pull chain is a length as described above, target arm 210 falling after the projectile strike will still leave at least some slack in the pull chain. Such a situation will not cause a counter-force on actuator arm 270.
However, in some situations, target arm 210 may be struck when there is no slack in the pull chain, thereby causing actuator arm 270 to be subjected to a counter-force. For example, and as described above, during a pull action, actuator arm 270 is raising target arm 210 from down position 420 to up position 410. More particularly, during the pull stroke of the pull action, all slack has been removed from the pull chain, and actuator arm 270 is exerting the force on target arm 210 as described above. While actuator arm 270 is exerting this force, target arm 210 is partly exposed to fire from shooter 150. If a projectile strikes target arm 210 during the pull stroke (e.g., after actuator arm 270 reaches the initial pull angle but prior to actuator arm 270 reaching maximum actuator position 470), the projectile will exert a counter-force (e.g., counterclockwise) on target arm 210 tending to resist the clockwise force from servo 250 and actuator arm 270.
This counterforce may tend to cause damage to gear assembly 240 and, more particularly, servo 250. As such, a shorter pull stroke may help avoid at least some such projectile strikes. However, shortening the pull stroke too much may not enable the pull action to generate enough momentum in target arm 210 to cause it to achieve upright position 410, and/or to overcome the initial pass by detent 220. At least some of the factors that may affect the length of time and angle of the pull stroke may be the power imparted by servo 250, the length of the pull chain, the position of connection point 219 on counterbalance 212, the mass of target arm 210 and/or components of target arm 210, the length of actuator arm 270, the length of servo arm 256, and the placement of servo bracket 252 and servo 250. In the example embodiment, target enclosures 100 is configured such as to exert enough force to pop the target arm 210 from down position 420 into upright position 410 and past detent 220, with a shortened pull stroke.
Further, in some embodiments, target enclosure 100 also includes a “hit sensor” that detects when a projectile has struck target arm 210. In the example embodiment, the hit sensor is a piezoelectric sensor. Further, in some embodiments, the hit sensor is mounted to right side wall 108 or left side wall 104 (shown in FIG. 2) approximately adjacent to target arm 210. This positioning may help reduce any resonance in the target housing that could produce false hit readings. In some embodiments, the hit sensor is mounted to a back surface 311 (shown in FIG. 3) of target plate 110. In other embodiments, three hit sensors may be mounted to back surface 311 such that hit location may be determined by triangulation between the three sensors. With hit sensor(s) mounted to back surface 311, in some embodiments, the hit sensors may be mounted without a housing to reduce mass and/or make the sensor compliant, as bullet impact may tend to transfer through the plate and possibly detach the hit sensor on from back surface 311. In the example embodiment, the hit sensor is communicatively coupled to a controller included within target enclosure 100.
FIG. 5 is a diagram of an example shooting system 500 that includes one or more target enclosures 510 in a target set 502. In some embodiments, target enclosures 510 are similar to target enclosure 100 (shown in FIGS. 1-4) or target enclosure 600 (shown in FIGS. 6A-8). Shooting system 500, in the example embodiment, includes a set of three target enclosures 510 communicatively coupled to a control unit 520. In some embodiments, control unit 520 includes a display 522. Further, in some embodiments, control unit 520 is positioned in proximity to shooter 150 or another user (not shown) associated with shooter 150, such as a shooting instructor or administrator. In the example embodiment, control unit 520 and target enclosures 510 each include a wireless communications interface 512 such as, for example, an XBee® radio module (e.g., 900 megahertz). In other embodiments, control unit 520 may be communicatively coupled to target enclosures 510 via a wired network 524 using wired communications interfaces (e.g., Ethernet, or serial).
In some embodiments, control unit 520 may also be communicatively coupled to a mobile computing device 530 (e.g., smartphone, handheld tablet computing device, and laptop computing device) via a wired or wireless network such as, for example, using near-field communications (NFC) technology (e.g., Bluetooth®). In other embodiments, mobile computing device 530 may be coupled to target enclosures 510, control unit 520, and/or a system server 540 via a wired or wireless network, for example via a Wi-Fi device 550 or a cellphone network 552. Shooting system 500, in the example embodiment, includes a database 542 for providing at least some of the benefits described herein.
In the example embodiment, control unit 520 transmits commands to, and receives data from, target set 502 and, more particularly, individual target enclosures 510 a, 510 b, and 510 c (collectively, “target enclosures 510”). For example, in some embodiments, control unit 520 transmits pull action commands and push action commands to raise and lower target arms 210 (shown in FIGS. 2-4) of target enclosures 510. In some embodiments, each target enclosure 510 (e.g., target enclosure 510 a) includes an enclosure identifier distinct from at least the other nearby (e.g., different than the enclosure identifiers of target enclosures 510 b and 510 c). In some embodiments, each individual target enclosure 510 is configured with an enclosure identifier. In other embodiments, target enclosures 510 are assigned enclosure identifiers by control unit 520 (e.g., when first powered on). In still other embodiments, network identifiers (e.g., IP addresses) of target enclosures 510 may be used as enclosure identifiers. As such, control unit 520 is able distinguish between individual target enclosures for transmitting individual commands to particular enclosures.
In some embodiments, control unit 520 transmits a series of pull and push actions to each target enclosure 510 of target set 502. This series of coordinated actions is referred to herein as a “target actions sequence.” The target actions sequence may also be referred to herein as a “simulation” or a “training program” in which, for example, shooter 150 begins the target actions sequence, shoots at target actions during the sequence, and the simulation concludes when the sequence is complete.
A target actions sequence may, for example, comprise a time-synchronized series of events for each of the three target enclosures 510 a, 510 b, and 510 c. A target actions sequence may, for example, include three separate “individual target sequences”, which may include an ordered series of pull and push actions with intervening delays before, during, and/or after each. For example, a target actions sequence may include:

TABLE 1

Example Target Actions Sequence

Operation #

510a

510b

	510c

(1)	Pull @ 2.0 s	Pull @ 0.5 s	Pull @ 6.0 s
(2)	Push @ 3.2 s	Push @ 2.5 s	Push @ 7.3 s
(3)	Pull @ 4.5 s	Pull @ 3.5 s	Pull @ 8.2 s
(4)	Push @ 6.0 s	Push @ 5.5 s	Push @ 9.0 s
(5)	Pull @ 8.5 s	Pull @ 7.9 s	Pull @ 10.1 s
(6)	Push @ 10.5 s	Push @ 9.9 s	Push @ 11.0 s

Table 1 includes three individual target sequences (e.g., the three columns for

target enclosures

510 a, 510 b, and 510 c). Each individual target sequence includes six separate motive actions or “operations” identified by in the “Operation #” column. Each operation is defined as either a push action or a pull action, as described above. Further, each operation includes a time to perform the action on (e.g., transmit an operation to) the associated target enclosure. It should be understood that the number of target enclosures 510, the number of operations, and the particular timings of operations shown in Table 1 are exemplary only, and that each may vary within the scope of this disclosure.

In the example shown in Table 1, the time of the operation is referenced as “@” (“at”) an elapsed time, t, in seconds (s), from a start time of t=0.0 seconds. As such, each individual target action sequence defines when the given operations are to be transmitted and performed by the associated target enclosure 510. For example, at time t=2.0 seconds, control unit 520 transmits a pull action to target enclosure 510 a, thereby causing servo 250 (shown in FIGS. 2-3) to “pull” target arm 210 into upright position 410 (shown in FIG. 4), and thereby exposing target plate 110 (shown in FIGS. 1-2) to potential fire from shooter 150. Then, at time t=3.2 seconds, control unit 520 transmits a push action to target enclosure 510 a, thereby causing servo 250 to “push” target arm 210 into down position 420 (shown in FIG. 4), and “hiding” target plate 110 from potential fire from shooter 150.
Accordingly, during operation, control unit 520 sends signals to three target enclosures 510 a, 510 b, and 510 c during the example simulation. For example, targets may begin the simulation shown in Table 1 in the down position. At time t=0.5 seconds, control unit 520 sends a pull action to target enclosure 510 b (e.g., raising that target). At time t=2.0 seconds, control unit 520 sends a pull action to target enclosure 510 a. At time t=2.5 seconds, control unit 520 sends a push action to target enclosure 510 b. This target enclosure 510 b may have been struck and knocked down by shooter 150. In the example embodiment, control unit 520 and/or the associated target enclosure may skip a push action if, for example, a hit has been registered since the last pull action (e.g., if shooter 150 has just scored a hit). At various times throughout the example simulation, targets are raised and lowered according to the simulation commands. At any given time, none or one or more of the targets may be raised and subsequently lowered if not hit, depending on the series of simulation operations.
In some embodiments, control unit 520 may identify the target action sequence (e.g., the data from Table 1) for the simulation from a database 542 (e.g., as a pre-generated or pre-created target action sequence). Database 542 may include a plurality of simulations, and shooter 150 may select a pre-defined simulation from database 542. For example, and in some embodiments, some simulations may include a degree of difficulty, such as “hard”, “medium”, and “easy”, and shooter 150 may select a simulation based at least in part on the degree of difficulty.
In other embodiments, control unit 520 may generate the target action sequence at “run time” (e.g., just prior to execution). For example, control unit 520 may generate three individual target sequences by alternating pull and push actions separated by a random or pseudo-random amount of time between each (referred to herein as “delay times” between two operations on either a single target enclosure or on target enclosures within a target set). In some embodiments, to provide randomization for up and down times, a random number generator function of Arduino software is used. The random seed is sourced by reading an analog input of the Arduino which has electrical noise. This provides that the times are random and do not repeat. These random times are generated every time the Arduino code loops, which in some embodiments is several thousand times per second (e.g., depending on processor clock speed and/or code complexity). In some embodiments, the simulation may be programmed to leave a target up until it is hit, and/or may immediately come back up after being hit. In some embodiments, the simulation may be configured with a total number of presentations, such as, for example, when the shooter has a 30 round magazine, and may want to only have 30 chances to hit targets.
In some embodiments, control unit 520 generates operations “on the fly,” or after commencing the simulation. Control unit 520 may identify or be provided with various parameters that may influence generation of the target action sequence for an upcoming simulation. For example, in some embodiments, parameters may include: a total simulation time, or a total time that the target action sequence should run (e.g., run the simulation for 30 seconds); a number of presentations for one or more of the target enclosures during the simulation (e.g., enclosure 510 b should present itself, or be pulled into upright position 410, a total of 5 times during the simulation); a presentation time or presentation time range (e.g., enclosure 510 b should remain in upright position 410 for 1.5 seconds during each presentation, or a random amount of time between 0.8 seconds and 2.5 seconds during each presentation); a down time or down time range (e.g., enclosure 510 b should remain in down position 420 for 2.2 seconds between each presentation, or a random amount of time between 1.2 seconds and 3.0 seconds); a maximum or minimum number of targets simultaneously presented (e.g., no more than 2 targets in target set 502 may ever be presented at the same time); a rate at which targets are presented to shooter 150; a maximum number of hits (e.g., perform the simulation until 15 hits are registered); and a minimum number of hits (e.g., perform the simulation for at least 30 seconds, then stop only after 5 hits are registered).
As described above, in the example embodiment, each target enclosure 510 also includes a controller 514 (e.g., a microcontroller such as an Arduino® microcontroller) communicatively coupled to a hit sensor (not shown). Controller 514 is configured to identify a “hit” (e.g., a projectile strike to target arm 210) when the hit sensor provides an amplitude of impulse above a pre-determined threshold. In the example embodiment, the threshold for a hit is determined by using the analog-to-digital converter input of controller 514. The Arduino controller 514 has a maximum voltage input of 5 Volts, so a resistor is wired in parallel with the piezo hit sensor to reduce the maximum voltage generated. The hit sensor is capable of generating around 30 Volts. The controller 514 constantly reads this input and converts the readings to a digital value between 0 and 1023. If this value is above a pre-defined threshold (e.g., 600), then controller 514 registers a hit. Other thresholds may be used, based on variables such as sensor placement, construction materials, densities, and weights of various parts, and the types of projectiles that may be used with target enclosure 100.
In the example embodiment, after identifying a hit, controller 514 transmits a hit detection signal to control unit 520 (e.g., via respective communications interfaces 512). In some embodiments, hits are tracked by a hit counter. This hit counter may be reset (e.g., set to zero) at, for example, the beginning of a simulation. In some embodiments, hits may influence the simulation while the simulation is running. For example, in some embodiments, control unit 520 may alter a rate or speed at which targets are presented to shooter 150 if a hit rate or hit percentage is above or below a pre-determined threshold, or outside or inside of a predetermined range. Or for another example, a hit signal may advance the target action sequence if the simulation is programmed to maintain a minimum of one target always presented.
In the example embodiment, presentation data (e.g., how many total targets were presented during the simulation) and hit data (e.g., how many hits were registered) are collected during a simulation (referred to herein, collectively, as “results data”, the results of a given simulation). In some embodiments, the results data is presented to shooter 150 during and/or after the simulation. For example, in some embodiments, control unit 520 may track a total number of presentations of targets during the simulation, and a total number of hits registered during the simulation. Control unit 520 may generate a “knock-down percentage” based at least in part on the number of targets presented to the number of hits registered. Control unit 520 may then present to shooter 150, for example via display 522 or mobile computing device 530, one or more of: total hits (e.g., the total number of hits registered during the simulation), total presentations (e.g., the number of times that targets were presented to shooter 150 during the simulation), knock-down percentage, hits per target, timer time remaining, hit timing, elapsed time, hits per second, time target has been up, and/or time target was up before being hit. Further, in some embodiments, control unit 520 may identify a number of rounds expended by shooter 150 during the simulation. For example, shooter 150 may only be allowed a fixed number of shots, such as when using a 6-shot revolver, or shooter 150 or the target actions sequence may provide a limit or total number of shots fired during the simulation. As such, control unit 520 may also present a hits percentage (e.g., the number of shots fired that registered a hit) based at least in part on the number of shots fired and the number of hits registered.
Further, in some embodiments, control unit 520 may track an amount of elapsed time that the target is presented to shooter 150 before being hit, or if multiple targets were up simultaneously, how long it took between each hit and the total time it took to knock them down. As such, control unit 520 may present this additional data to shooter 150 for their tracking and analysis.
In some embodiments, simulation data, such as a target actions sequence, and/or results data, such as hit data from a given simulation, may be stored and tracked over time. For example, shooter 150 may perform a particular simulation X on Aug. 1, 2014. Shooting system 500 may store the simulation data (e.g., target actions sequence of Table 1) and/or the results data of shooter 150 during simulation Xin database 542. At a later time, such as a year later, shooter 150 may perform the same simulation X, generating new results data, and shooting system 500 may present both the historical results data and the current results data to shooter 150, as well as comparative data indicating how shooter 150 improved or regressed over time. As such, shooting system 500 may provide measurable skills data for various shooters, and relative to their own performance on the same simulation. Further, other shooters may use the same simulation Xto generate results data of their own. As such, shooting system 500 may provide measurable skills data to compare the performance of shooters to other shooters under the same simulation.
FIGS. 6A-8 illustrate an example embodiment of a target enclosure 600 that may be used in the shooting system 500 shown in FIG. 5 (e.g., as target enclosure(s) 510). Target enclosure 600 is capable of maintaining an upright position after projectile strikes based on control of a target arm 610 by an actuator (e.g., a pneumatic or hydraulic actuator).
FIG. 6A is a rear right-side perspective view illustrating target enclosure 600 with a target arm 610 in an upright position. Target arm 610 may have some components similar to target arm 210 (shown in FIGS. 2-4). Target enclosure 600 includes right side wall 108 and left side wall 104, with splatter guard 106 covering the front top of the enclosure 600, and with front guard plate 102. Further, target enclosure 600 also includes a rear cover 606 and a rear plate 604. A carrying handle 602 is coupled to rear plate 604, and may be used to carry target enclosure 600 when not in use. Target enclosure 600 also includes rest bar 112, on which target arm 610 rests when in the down position. Target enclosure 600 also includes one or more hit sensors (not shown), which may be similar to the hit sensors described with respect to target enclosure 100.
FIG. 6B is a rear right-side perspective view illustrating target enclosure 600 as shown in FIG. 6A, but excluding some components of target enclosure 600, such as right side plate 104, rear plate 604, and rear cover 606, for purposes of illustration (e.g., to better reveal the interior of target enclosure 600). In some embodiments, target enclosure 600 may include some components similar to the target enclosure 100 shown in FIGS. 1-4, though not necessarily labeled in FIGS. 6A-8. Target arm 610 includes target plate 110 coupled to a counterbalance lever arm 612. Target enclosure 600 represents another embodiment for raising and lowering target arm 610 that, among other things, enables target arm 610 to maintain an upright position after projectile strikes. In the example embodiment, target enclosure 600 includes a pneumatic system 640 that raises and lowers target arm 610 between the upright and down positions. In other embodiments, target enclosure 600 may include a hydraulic system for raising and lowering target arm 610, which may include some components similar to pneumatic system 640.
In the example embodiment, pneumatic system 640 includes an air cylinder 650 (e.g., a double-acting pneumatic actuator). Air cylinder 650 includes an internal chamber (not shown) in which a piston (not shown) is moved or actuated (e.g., via compressed air pressure) to cause a piston rod 656 to extend or retract from air cylinder 650. As a double-acting actuator, air cylinder 650 includes two ports 658A and 658B to enable extension and retraction of piston rod 656. For example, compressed air flow into “extension port” 658A tends to force extension of piston rod 656, and compressed air flow into “retraction port” 658B tends to force retraction of piston rod 656.
Air cylinder 650 also includes a first end 652A and a second end 652B. At first end 652A, air cylinder 650 is coupled to a threaded rod end 654A, which in turn is rotatably coupled to a support rod 630. Threaded rod end 654A enables air cylinder 650 to rotate through a small range during operation (e.g., during raising and lowering of target arm 610). At second end 652B, piston rod 656 is coupled to threaded rod end 654B, which is rotatably coupled to counterbalance lever arm 612 of target arm 610. Threaded rod end 654B enables piston rod 656 to rotate through a small range during operation (e.g., relative to target arm 610). In FIG. 6B, air cylinder 650 is shown in a retracted state (e.g., with piston arm 656 retracted within the internal chamber), and as such, target arm 610 is in an upright position.
Pneumatic system 640 also includes an air compressor 670 and a directional solenoid valve 660 configured to generate and distribute compressed air to air cylinder 650 (e.g., into and out of ports 658A and 658B). Air compressor 670 generates compressed air used to actuate air cylinder 650. In the example embodiment, air compressor 670 is an air compressor such as those commercially available from VIAIR® (a California corporation) (e.g., a “C” model, such as model “100 c”, or an “IG” model). Air compressor 670 is powered by a power supply 680 (e.g., an electrochemical battery) and is coupled in flow communication with valve 660 (e.g., via pneumatic hose (not shown) or similar conduit or coupling).
Valve 660 distributes compressed air from air compressor 670 to air cylinder 650. In the example embodiment, valve 660 is a dual-solenoid valve such as those commercially available from MCMASTER-CARR® (an Illinois corporation) (e.g., 5-port double solenoid air directional control valve, 12 volt DC, style F, ⅛ NPT port size). Valve 660 is coupled in flow communication with air compressor 670, and optionally other components, as a source for the compressed air. For distribution of the compressed air, valve 660 is coupled in flow communication with both extension port 658A and retraction port 658B (collectively, ports 658) on air cylinder 650 (e.g., via pneumatic tube (not shown), or fixedly attached to one of the ports 658).
During operation, valve 660 controls air flow from air compressor 670 and a reservoir 810 (shown in FIG. 8) to air cylinder 650, causing piston rod 656 to extend (e.g., compressed air flow into extension port 658A during a “push action”), thereby lowering target arm 610, or causing piston rod 656 to retract (e.g., compressed air flow into retraction port 658B during a “pull action”), thereby raising target arm 610. Valve 660 (e.g., the solenoids of valve 660) is powered by the power supply, and is communicatively coupled to the microcontroller, enabling the microcontroller and, by proxy, mobile computing device 530 or control unit 520, to control the position of target arm 610 by controlling compressed air flow to either extension port 658A or retraction port 658B using the solenoids of valve 660.
In the example embodiment, as mentioned above, pneumatic system 640 is configured such that piston rod 656 is retracted while target arm 610 is in the upright position (e.g., while exposing target arm 610 to projectile fire from shooter 150). During an impact event (e.g., when a projectile strikes target arm 610), target arm 610 may experience a reciprocal force from decelerating the projectile, thereby causing a rotational force on target arm 610 (e.g., around target arm bar 230). This rotational force transfers to air cylinder 650, which is under air pressure in the pneumatic system 640. As such, air cylinder 650 acts as an air cushion, absorbing some of the shock and rotational force by allowing air within air cylinder 650 to compress and expand slightly, acting like a “pneumatic spring,” thereby allowing target arm 610 to flex back and forth slightly with the impact. This cushion effect reduces some of the shock that might otherwise reverberate through other components of target enclosure 600. Further, because the air cylinder 650 and piston rod 656 are in a substantially retracted position (e.g., as shown in FIG. 6B), those components are in a more secure positon to withstand impact shock (e.g., protecting against bending of piston rod 656).
In the example embodiment, pneumatic system 640 also includes a pressure switch (not shown) that regulate certain actions of air compressor 670. For example, the pressure switch may be configured to maintain system pressure within pneumatic system 640 (e.g., reservoir 810) within a pressure range (e.g., between a lower threshold and an upper threshold). The pressure switch may cause air compressor 670 to activate when the pressure in reservoir 810 is below the lower threshold, or the pressure switch may cause air compressor 670 to deactivate when the pressure in reservoir 810 is at or above the upper threshold. The pressure range settings may depend on various other factors and components of target enclosure 600 such as, for example, the weight, shape, and various other aspects of target arm 610, which might cause target arm 610 to require more or less pressure to effectively and timely raise and lower during operation (e.g., heavier target arms 610 may require a greater lower threshold than lighter target arms 610). In the example embodiment, the pressure range is maintained (e.g., by the pressure switch) between 85 pounds per square inch (PSI) (e.g., the lower threshold) and 105 PSI (e.g., the upper threshold).
In some embodiments, the pressure switch builds pressure to a pre-determined level (e.g., the upper threshold), and then shuts off. When valve 660 actuates and moves air cylinder 650 (e.g., piston rod 656), a pressure drop is caused, and the pressure switch causes air compressor 670 to engage to re-establish pressure. In some embodiments, the microcontroller controls the compressor via a relay. In other words, rather than using a pressure switch, the microcontroller interfaces with a pressure transducer (not shown), and the microcontroller controls both the raising and lowering events, as well as the pressure build for valve 660. As such, the microcontroller may “anticipate” an upcoming raising or lowering event and engage air compressor 670 based on the upcoming event (e.g., at a pre-determined amount of time before the upcoming event, rather than as a reaction to a pressure drop), thereby building pressure more efficiently.
In other embodiments, pneumatic system 640 may include pressure sensors configured to detect the pressure within the pneumatic system 640 (e.g., within reservoir 810). The pressure sensors may interface with the microcontroller and, by proxy, control unit 520 or mobile computing device 530 (e.g., for pressure readings). Further, pneumatic system 640 may include relays (not shown), communicatively coupled to the microcontroller, that are configured to activate or deactivate air compressor 670. As such, the microcontroller and, by proxy, control unit 520 or mobile computing device 530, may control the pressure within reservoir 810 by controlling activation of air compressor 670. In some embodiments, the microcontroller, the mobile computing device 530, or the control unit 520 may operate to maintain the pressure within the reservoir 810 within a pre-determined range. In some embodiments, the shooter 150 may configure one or more of the lower threshold and the upper threshold.
In some embodiments, pneumatic system 640 includes an exhaust flow control orifice (or “bleed-off orifice”) 662. The exhaust flow control orifice 662 is a flow-control orifice such as those commercially available from MCMASTER-CARR® (e.g., NPT threaded brass flow-control orifice, hex head, ⅛ NPT male, 0.020″ or 0.025″ diameter). The exhaust flow control orifice 662 is screwed into an exhaust port (not separately identified on FIG. 6B) of valve 660, and controls the rate at which air exhausts from air cylinder 650 (e.g., altering the rate at which target arm 610 may fall). Use of flow control orifice 662 may be used to control the speed of the target during raising or lowering events (e.g., pull actions and push actions, respectively). For example, flow control orifice 662 may counteract the pneumatic power of pneumatic system 640 during a push action, thereby reducing the speed of descent of target arm 610, and thus the impact shock placed upon rest bar 112 as target arm 610 reaches the down position. In the example shown in FIG. 6B, flow control orifice 662 is illustrated on a right-side port of the three ports shown on valve 660, but the flow control orifice 662 may be installed on a left-side port of valve 660.
Target enclosure 600 also includes two flanged bearing mounts 614 opposed each other and supporting target arm bar 230. Flanged bearing mounts 614 include needle bearings configured to enable target arm 610 to rotate about target arm bar 230 in approximately 90 degrees of motion (e.g., between the upright and down positions). Target enclosure also includes two torsion springs 616 that provide force assist when raising target arm 610. One end 616 of each torsion spring 616 acts on the lever arm 612, while the other end (not visible in FIG. 6B) acts on the underside of splatter guard 106. Torsion springs 616 are shown in FIG. 6B in a “relaxed” or uncompressed state (e.g., relatively). As such, relatively little force is applied by torsion springs 616 to maintain target arm 610 in the upright position. When target arm 610 is lowered to the down position, torsion springs 616 compress and apply greater force (e.g., toward raising target arm 610). This raising force is overcome by pneumatic system 640 (e.g., by the extension of piston rod 656), which maintains target arm 610 in the down position (e.g., via pneumatic pressure). When target arm 610 is being raised from the down to the upright position, torsion springs 616 act to assist pneumatic system 640, thereby providing a smoother and more efficient upright movement of target arm 610.
In the example embodiment, target enclosure 600 also includes an electronics enclosure (“control unit”) 634 mounted to the rear plate 604 of the enclosure 600. The electronics enclosure 634 houses some of the electronics components of the enclosure 600, such as, for example, the wireless communications interface 512, the microcontroller (e.g., for performing the push and pull actions, when directed, which may be similar to controller 514), relays for controlling valve 660, and an on/off switch. In the example embodiment, the microcontroller is a controller such as those commercially available from Particle (www.particle.io; Spark Labs Inc. doing business as Particle) (e.g., Particle Photon microcontroller) or from Adafruit Industries, LLC (a New York Limited Liability Company) (e.g., Adafruit Pro Trinket).
In some embodiments, target enclosure 600 may include one or more flyback diodes (not shown). For example, a flyback diode may be included for the air compressor 670 and/or the solenoids on valve 660. Flyback diodes are connected across the terminals or leads of the associated device. Air compressor 670 may periodically generate a voltage spike (e.g., when shutting off after reaching a pressure threshold). The voltage spike may damage other components of target enclosure 600 such as, for example, the microcontroller. The flyback diodes allow the spike to flow back through the inductor that caused the spike until it is dissipated. In other embodiments, a transformer-based DC-to-DC power converter or power supply may be used (e.g., in lieu of or in addition to flyback diodes). As such, the DC-to-DC power converter may isolate the compressor from other electronics components.
In some embodiments, pneumatic system 640 may use two single-acting pneumatic actuators (e.g., in lieu of double-acting air cylinder 650, one for raising target arm 610 and the other for lowering target arm 610). In some embodiments, pneumatic system 640 may use two single-solenoid valves (e.g., in lieu of dual-solenoid valve 660, one for raising the target arm 610, one for lowering target arm 610, either with a single double-acting pneumatic actuator such as air cylinder 650, or with two single-acting pneumatic actuators). In some embodiments, valve 660 may be an air-directional control valve (e.g., in lieu of solenoids).
In some embodiments, pneumatic system 640 may be implemented as a hydraulic system (not separately shown). For example, air compressor 670 may be substituted with a hydraulic compressor (not shown), air cylinder 650 may be substituted with a double-acting hydraulic actuator, and the hydraulic system may use a fluid rather than air. Further, the hydraulic system may include a reservoir for system fluid. The hydraulic system may also include an accumulator to, for example, dampen shocks to the hydraulic system and other components upon proj ectile impacts.
FIG. 7 is a perspective view of target enclosure 600 in a down position, with the air cylinder 650 extended, or pushed out (e.g., after a “push action”). FIG. 7 shows rear cover 606 and rear plate 604, but excludes right side plate 108 for purposes of illustration. In the down position, target arm 610 rests on rest bar 112. In some embodiments, rear cover 606 is fixedly coupled to rear plate 604, thereby forming an L-shaped “service hatch” (not separately identified). Rear plate 604 is coupled to a hinge 632, which is coupled to underside plate 620. Hinge 632 enables the service hatch to rotate out (e.g., when target arm 610 is in an upright position), thereby exposing components within the interior of target enclosure 600 for inspection or service.
FIG. 8 is a rear left-side perspective view illustrating target enclosure 600, but excluding some components of target enclosure 600, such as left side plate 108, rear cover 606, and rear plate 604, for purposes of illustration (e.g., to better reveal the interior of target enclosure 600). In the example embodiment, target enclosure 600 also includes a reservoir 810. The reservoir 810 is a multi-purpose device, acting as a filter (e.g., removing particulates), a drain (e.g., to remove fluid and debris from the compressed air), and a reservoir of compressed air. In some configurations, it may be advantageous to maintain a relatively small reservoir 810, in which air compressor 670 is engaged regularly after raise and lower events (e.g., where the stored compressed air is just enough to perform a single event). A smaller reservoir may, for example, cause an advantageous power loss near the end of the extension stroke of cylinder rod 656, thereby partially reducing the force at which target arm 610 strikes rest bar 112.
Referring now to FIGS. 6B and 8, in the example embodiment, an exit port 820 of air compressor 670 is coupled in flow communication with reservoir 810 at a reservoir entry port 822 (e.g., via pneumatic tube or conduit). A reservoir exit port (not visible in FIG. 8) of reservoir 810 is coupled in flow communication with a valve entry port 664 of valve 660. Valve 660 is fixedly coupled to, and coupled in flow communication with, air cylinder 650 at extension port 658A. Valve 660 is also coupled in flow communication with retraction port 658B (e.g., via pneumatic tube or conduit). As such, compressed air may transit from air compressor 670 through reservoir 810 and valve 660 to be used on either port 658A, 658B of air cylinder 650.
Referring now to FIG. 5, in some embodiments, training programs may be performed on target enclosure 600 (e.g., with a pneumatic or hydraulic actuator that enables target arm 610 to remain upright after one or more strikes). In some embodiments, shooting system 500 provides a training program that provides for a random number of hits (“random hits”) or a pre-determined number of hits before lowering a particular target 510 (e.g., a random number within a pre-determined range of hits, such as between 1 and 7 hits). In other words, a random number between 1 and 7 is selected (e.g., “5” is selected by controller 514 or by control unit 520), a particular target 510 is raised, and that target 510 remains upright until the target 510 is struck 5 times, at which time it is lowered. In some embodiments, microcontroller 514 may identify the hits and initiate the down action once the number of hits has been reached. In other embodiments, target enclosure 510 may transmit hit data back to control unit 520 and control unit 520 may initiate the down action once the number of hits has been reached.
In some embodiments, shooting system 500 provides a training program that provides for a random selection of which target enclosure 510 is raised at a particular time (e.g., one at a time in sequence, one at a time randomly, or all at once). Further, these training programs may be combined with the number of hits to generate a hybrid training program (e.g., random target enclosure 510, one at a time, with random number of hits between 1 and 7 before lowering).
In some embodiments, a timer is included (e.g., on target enclosure 510 or on control unit 520). The shooting system 500 may provide training programs that maintain a target enclosure 510 upright for a period of time (“time-based routines”, e.g., a random amount of time in a range, or a pre-determined amount of time). The time-based routines may be combined with the target selection routines described above to form hybrid routines. In some embodiments, control unit 520 transmits a “target uptime value” to a target enclosure 510. That target enclosure 510 raises the target upright, starts a timer, and maintains the target upright for the length specified by the target uptime value. In other words, the target uptime value determines how long the target is going to be upright (e.g., regardless of the number of hits). In some embodiments, the timer only runs after a first hit is registered on the particular enclosure 510 after raising the target. This timer delay may keep units from cycling while unattended. In other words, without the timer delay, an unattended shooting system 500 may continue to cycle through a training program even though the shooter 150 may not be engaged, thereby running down the power supplies on the enclosures 510.
In some embodiments, enclosures 510 include a listening window delay when registering hits with the hit sensor. The listing window delay is a length of time in which a subsequent shot will not register as a distinct “hit” after an initial hit. For example, a listing window delay of 500 milliseconds will only register one hit if two consecutive hits occur 300 milliseconds apart. In the example embodiment, the listing window delay is 100 milliseconds. In other embodiments, the listing window delay is 250 milliseconds.
In some embodiments, a single hit sensor is mounted to the target arm 610 and is calibrated to distinguish between an impact to the target arm 610 and to other areas of the enclosure 600 (e.g., via a threshold value). Impacts on the target arm 610 may register a greater value than impacts to other components, such as front plate 102. As such, the shooting system 500 may distinguish hits on target arm 610.
In some embodiments, multiple hit sensors may be provided within target enclosure 100, 600. For example, one piezoelectric sensor may be placed on target arm 610 (“target arm sensor”) and a second sensor may be placed on the interior surface of front plate 102 (“front plate sensor”). Readings from each sensor may be compared after a single hit, and may be used to distinguish between an impact on the target arm 610 and an impact on front plate 102 (e.g., based on a differential or absolute value comparison between the two readings). For example, an impact on front plate 102 may register a greater value on the front plate sensor than on the target arm sensor, and vice versa for a hit on the target arm 610. As such, the shooting system 500 may distinguish between the two different types of impacts (e.g., counting only the hits on the target arm 610).
In some embodiments, a shot sensor may be provided in proximity to shooter 150 that counts the number of shots fired by shooter 150 during a training routine. For example, control unit 520 may include a microphone (not shown) that is configured to detect the percussion of a round fired. As such, the shooting system 500 may compute a hit percentage (e.g., using the total number of hits over the total number of shots fired).
In some embodiments, the hit sensor(s) may only be active and register hits when the target arm 610 is upright, and/or while on the way up/down (e.g., controlled by the microcontroller or control unit 520).
In some embodiments, a light (not shown) may be provided on target enclosure 100, 600 (e.g., a white light-emitting diode (LED) light). The light may be mounted to splatter cover 106 and oriented to illuminate front surface 111 of target arm 210, 610. As such, the light may enable target enclosure 100, 600 to be used in darkness or low visibility situations. Further, in some embodiments, the light may be a multi-colored light (e.g., green and red). The shooting system 500 may control activation of the light, and may control which color is displayed. Training programs may also implement the multiple colors. For example, red may be a “do not shoot” situation, and green is a “shoot” situation. As such, shots impacting a “red” target may be counted separately than shots hitting a “green” target, where some may count against the shooter and others may count for the shooter.
FIG. 9 illustrates a computerized method 900, in accordance with an example embodiment, for providing a training routine for a shooter. The computerized method 900 is performed by a computing device comprising at least one processor. In the example embodiment, the computerized method 900 includes selecting, by a hardware processor, a first hit count associated with a first target enclosure at operation 910. At operation 920, the method 900 includes transmitting the first hit count to the first target enclosure. At operation 930, the method 900 includes receiving, by the hardware processor, indication from the first target enclosure that a number of projectile impacts on the first target enclosure equals or exceeds the hit count. At operation 940, the method 900 includes selecting, by the hardware processor, a second hit count associated with a second target enclosure after receiving indication from the first target enclosure. At operation 950, the method 900 includes transmitting the second hit count to the second target enclosure.
In some embodiments, the method 900 further includes transmitting a first raise event to the first target enclosure, wherein receiving indication from the first target enclosure further includes receiving projectile strike data from the first target enclosure, the projectile strike data including a number of projectile impacts on the first target enclosure, comparing, by the first hardware processor, the number of proj ectile impacts on the first target to the first hit count, and determining, by the first hardware processor, that the first hit count has been reached or exceeded based on the comparing. In some embodiments, the method 900 also includes receiving, by the hardware processor, first proj ectile strike data from the first target enclosure, receiving, by the hardware processor, second projectile strike data from the second target enclosure, and displaying the first projectile strike data and the second proj ectile strike data to the shooter during the training routine via a display device.
The exemplary methods and systems described herein provide an automated shooting system and target enclosure that may be used to enhance shooting accuracy. The target enclosure provides a gear assembly operated in conjunction with a target arm that can raise and lower a target plate automatically, thereby providing an automatic target for a shooter. Further, a control unit is provided in communication with one or more target enclosures for providing a series of control events such that a sequence of target actions may be executed by the one or more target enclosures. The target actions sequence, or simulation, may be pre-defined or generated during the simulation, and may be retained and stored for repeated use of the same simulation. Shooter statistics may be collected, stored, and compared to the same shooter or other shooters for accuracy metrics comparison.
FIG. 10 is a block diagram illustrating an example software architecture 1002, which may be used in conjunction with various hardware architectures herein described. FIG. 10 is a non-limiting example of a software architecture and it will be appreciated that many other architectures may be implemented to facilitate the functionality described herein. The software architecture 1002 may execute on hardware such as machine 1100 of FIG. 11 that includes, among other things, processors 1104, memory 1114, and input/output (I/O) components 1118. A representative hardware layer 1004 is illustrated and can represent, for example, the machine 1100 of FIG. 11. The representative hardware layer 1004 includes a processing unit 1006 having associated executable instructions 1008. Executable instructions 1008 represent the executable instructions of the software architecture 1002, including implementation of the methods, modules and so forth described herein. The hardware layer 1004 also includes memory and/or storage modules memory/storage 1010, which also have executable instructions 1008. The hardware layer 1004 may also comprise other hardware 1012.
In the example architecture of FIG. 10, the software architecture 1002 may be conceptualized as a stack of layers where each layer provides particular functionality. For example, the software architecture 1002 may include layers such as an operating system 1014, libraries 1016, frameworks or middleware 1018, applications 1020 and a presentation layer 1044. Operationally, the applications 1020 and/or other components within the layers may invoke application programming interface (API) API calls 1024 through the software stack and receive a response as in response to the API calls 1026. The layers illustrated are representative in nature and not all software architectures have all layers. For example, some mobile or special purpose operating systems may not provide the frameworks/middleware 1018, while others may provide such a layer. Other software architectures may include additional or different layers.
The operating system 1014 may manage hardware resources and provide common services. The operating system 1014 may include, for example, a kernel 1028, services 1030, and drivers 1032. The kernel 1028 may act as an abstraction layer between the hardware and the other software layers. For example, the kernel 1028 may be responsible for memory management, processor management (e.g., scheduling), component management, networking, security settings, and so on. The services 1030 may provide other common services for the other software layers. The drivers 1032 may be responsible for controlling or interfacing with the underlying hardware. For instance, the drivers 1032 may include display drivers, camera drivers, Bluetooth® drivers, flash memory drivers, serial communication drivers (e.g., Universal Serial Bus (USB) drivers), Wi-Fi® drivers, audio drivers, power management drivers, and so forth depending on the hardware configuration.
The libraries 1016 may provide a common infrastructure that may be used by the applications 1020 and/or other components and/or layers. The libraries 1016 typically provide functionality that allows other software modules to perform tasks in an easier fashion than to interface directly with the underlying operating system 1014 functionality (e.g., kernel 1028, services 1030 and/or drivers 1032). The libraries 1016 may include system libraries 1034 (e.g., C standard library) that may provide functions such as memory allocation functions, string manipulation functions, mathematic functions, and the like. In addition, the libraries 1016 may include API libraries API 1036 such as media libraries (e.g., libraries to support presentation and manipulation of various media format such as MPREG4, H.264, MP3, AAC, AMR, JPG, PNG), graphics libraries (e.g., an OpenGL framework that may be used to render 2D and 3D in a graphic content on a display), database libraries (e.g., SQLite that may provide various relational database functions), web libraries (e.g., WebKit that may provide web browsing functionality), and the like. The libraries 1016 may also include a wide variety of other libraries 1038 to provide many other APIs to the applications 1020 and other software components/modules.
The frameworks frameworks/middleware 1018 (also sometimes referred to as middleware) provide a higher-level common infrastructure that may be used by the applications 1020 and/or other software components/modules. For example, the frameworks/middleware 1018 may provide various graphic user interface (GUI) functions, high-level resource management, high-level location services, and so forth. The frameworks/middleware 1018 may provide a broad spectrum of other APIs that may be utilized by the applications 1020 and/or other software components/modules, some of which may be specific to a particular operating system or platform.
The applications 1020 include built-in applications 1040 and/or third-party applications 1042. Examples of representative built-in applications 1040 may include, but are not limited to, a contacts application, a browser application, a book reader application, a location application, a media application, a messaging application, and/or a game application. Third-party applications 1042 may include any an application developed using the Android™ or iOS™ software development kit (SDK) by an entity other than the vendor of the particular platform, and may be mobile software running on a mobile operating system such as iOS™, Android™ Windows® Phone, or other mobile operating systems. The third-party applications 1042 may invoke the API calls 1024 provided by the mobile operating system such as operating system 1014 to facilitate functionality described herein.
The applications 1020 may use built in operating system functions (e.g., kernel 1028, services 1030 and/or drivers 1032), libraries 1016, frameworks/middleware 1018 to create user interfaces to interact with users of the system. Alternatively, or additionally, in some systems interactions with a user may occur through a presentation layer, such as presentation layer 1044. In these systems, the application/module “logic” can be separated from the aspects of the application/module that interact with a user.
Some software architectures use virtual machines. In the example of FIG. 10, this is illustrated by a virtual machine 1048. The virtual machine 1048 creates a software environment where applications/modules can execute as if they were executing on a hardware machine. The virtual machine 1048 is hosted by a host operating system (e.g., operating system (OS) 650 in FIG. 10) and typically, although not always, has a virtual machine monitor 1046, which manages the operation of the virtual machine as well as the interface with the host operating system (i.e., operating system 1050). A software architecture executes within the virtual machine 1048 such as an operating system operating system (OS) 1050, libraries 1052, frameworks 1054, applications 1056 and/or presentation layer 1058. These layers of software architecture executing within the virtual machine 1048 can be the same as corresponding layers previously described or may be different.
FIG. 11 is a block diagram illustrating components of a machine 1100, according to some example embodiments, able to read instructions from a machine-readable medium (e.g., a machine-readable storage medium) and perform any one or more of the methodologies discussed herein. In some embodiments, machine 1100 may be similar to the microcontrollers or communications interfaces of target controllers 100, 510, 600 (e.g., controller 514, communications interface 512), or control unit 520, or computing devices 530, or server 540. Specifically, FIG. 11 shows a diagrammatic representation of the machine 1100 in the example form of a computer system, within which instructions 1016 (e.g., software, a program, an application, an applet, an app, or other executable code) for causing the machine 1100 to perform any one or more of the methodologies discussed herein may be executed. As such, the instructions may be used to implement modules or components described herein. The instructions transform the general, non-programmed machine into a particular machine programmed to carry out the described and illustrated functions in the manner described. In alternative embodiments, the machine 1100 operates as a standalone device or may be coupled (e.g., networked) to other machines. In a networked deployment, the machine 1100 may operate in the capacity of a server machine or a client machine in a server-client network environment, or as a peer machine in a peer-to-peer (or distributed) network environment. The machine 1100 may comprise, but not be limited to, a server computer, a client computer, a personal computer (PC), a tablet computer, a laptop computer, a netbook, a set-top box (STB), a personal digital assistant (PDA), an entertainment media system, a cellular telephone, a smart phone, a mobile device, a wearable device (e.g., a smart watch), a smart home device (e.g., a smart appliance), other smart devices, a web appliance, a network router, a network switch, a network bridge, or any machine capable of executing the instructions 1016, sequentially or otherwise, that specify actions to be taken by machine 1100. Further, while only a single machine 1100 is illustrated, the term “machine” shall also be taken to include a collection of machines that individually or jointly execute the instructions 1016 to perform any one or more of the methodologies discussed herein.
The machine 1100 may include processors 1010, memory memory/storage 1030, and input/output (I/O) components 1050, which may be configured to communicate with each other such as via a bus 1102. In an example embodiment, the processors 1110 (e.g., a Central Processing Unit (CPU), a Reduced Instruction Set Computing (RISC) processor, a Complex Instruction Set Computing (CISC) processor, a Graphics Processing Unit (GPU), a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Radio-Frequency Integrated Circuit (RFIC), another processor, or any suitable combination thereof) may include, for example, processor 1112 and processor 1114 that may execute instructions 1116. The term “processor” is intended to include multi-core processor that may comprise two or more independent processors (sometimes referred to as “cores”) that may execute instructions contemporaneously. Although FIG. 11 shows multiple processors, the machine 1100 may include a single processor with a single core, a single processor with multiple cores (e.g., a multi-core process), multiple processors with a single core, multiple processors with multiples cores, or any combination thereof.
The memory/storage 1130 may include a memory, such as a main memory 1132, static memory 1134, or other memory storage, and a storage unit 1136, both accessible to the processors 1110 such as via the bus 1102. The storage unit 1136 and memory 1132, 1134 store the instructions 1116 embodying any one or more of the methodologies or functions described herein. The instructions 1116 may also reside, completely or partially, within the memory 1132, 1134, within the storage unit 1136, within at least one of the processors 1110 (e.g., within the processor's cache memory), or any suitable combination thereof, during execution thereof by the machine 1100. Accordingly, the memory 1132, 1134, the storage unit 1136, and the memory of processors 1110 are examples of machine-readable media.
As used herein, “machine-readable medium” means a device able to store instructions and data temporarily or permanently and may include, but is not be limited to, random-access memory (RAM), read-only memory (ROM), buffer memory, flash memory, optical media, magnetic media, cache memory, other types of storage (e.g., Erasable Programmable Read-Only Memory (EEPROM)) and/or any suitable combination thereof. The term “machine-readable medium” should be taken to include a single medium or multiple media (e.g., a centralized or distributed database, or associated caches and servers) able to store instructions 1116. The term “machine-readable medium” shall also be taken to include any medium, or combination of multiple media, that is capable of storing instructions (e.g., instructions 1116) for execution by a machine (e.g., machine 1100), such that the instructions, when executed by one or more processors of the machine 1100 (e.g., processors 1110), cause the machine 1100 to perform any one or more of the methodologies described herein. Accordingly, a “machine-readable medium” refers to a single storage apparatus or device, as well as “cloud-based” storage systems or storage networks that include multiple storage apparatus or devices. The term “machine-readable medium” excludes signals per se.
The input/output (I/O) components 1150 may include a wide variety of components to receive input, provide output, produce output, transmit information, exchange information, capture measurements, and so on. The specific input/output (I/O) components 1150 that are included in a particular machine will depend on the type of machine. For example, portable machines such as mobile phones will likely include a touch input device or other such input mechanisms, while a headless server machine will likely not include such a touch input device. It will be appreciated that the input/output (I/O) components 1150 may include many other components that are not shown in FIG. 11. The input/output (I/O) components 1150 are grouped according to functionality merely for simplifying the following discussion and the grouping is in no way limiting. In various example embodiments, the input/output (I/O) components 1018 may include output components output components 1152 and input components 1154. The output components 1152 may include visual components (e.g., a display such as a plasma display panel (PDP), a light emitting diode (LED) display, a liquid crystal display (LCD), a projector, or a cathode ray tube (CRT)), acoustic components (e.g., speakers), haptic components (e.g., a vibratory motor, resistance mechanisms), other signal generators, and so forth. The input components 1154 may include alphanumeric input components (e.g., a keyboard, a touch screen configured to receive alphanumeric input, a photo-optical keyboard, or other alphanumeric input components), point based input components (e.g., a mouse, a touchpad, a trackball, a joystick, a motion sensor, or other pointing instrument), tactile input components (e.g., a physical button, a touch screen that provides location and/or force of touches or touch gestures, or other tactile input components), audio input components (e.g., a microphone), and the like.
In further example embodiments, the input/output (I/O) components 1150 may include biometric components 1156, motion components 1158, environmental environment components 1160, or position components 1162 among a wide array of other components. For example, the biometric components 1156 may include components to detect expressions (e.g., hand expressions, facial expressions, vocal expressions, body gestures, or eye tracking), measure biosignals (e.g., blood pressure, heart rate, body temperature, perspiration, or brain waves), identify a person (e.g., voice identification, retinal identification, facial identification, fingerprint identification, or electroencephalogram based identification), and the like. The motion components 1158 may include acceleration sensor components (e.g., accelerometer), gravitation sensor components, rotation sensor components (e.g., gyroscope), and so forth. The environmental environment components 1160 may include, for example, illumination sensor components (e.g., photometer), temperature sensor components (e.g., one or more thermometer that detect ambient temperature), humidity sensor components, pressure sensor components (e.g., barometer), acoustic sensor components (e.g., one or more microphones that detect background noise), proximity sensor components (e.g., infrared sensors that detect nearby objects), gas sensors (e.g., gas detection sensors to detection concentrations of hazardous gases for safety or to measure pollutants in the atmosphere), or other components that may provide indications, measurements, or signals corresponding to a surrounding physical environment. The position components 1162 may include location sensor components (e.g., a Global Position System (GPS) receiver component), altitude sensor components (e.g., altimeters or barometers that detect air pressure from which altitude may be derived), orientation sensor components (e.g., magnetometers), and the like.
Communication may be implemented using a wide variety of technologies. The input/output (I/O) components 1150 may include communication components 1164 operable to couple the machine 1100 to a network 1180 or devices 1170 via coupling 1182 and coupling 1172 respectively. For example, the communication components 1164 may include a network interface component or other suitable device to interface with the network 1180. In further examples, communication components 1040 may include wired communication components, wireless communication components, cellular communication components, Near Field Communication (NFC) components, Bluetooth® components (e.g., Bluetooth® Low Energy), Wi-Fi® components, and other communication components to provide communication via other modalities. The devices 1170 may be another machine or any of a wide variety of peripheral devices (e.g., a peripheral device coupled via a Universal Serial Bus (USB)).
Moreover, the communication components 1164 may detect identifiers or include components operable to detect identifiers. For example, the communication components processors communication components 1164 may include Radio Frequency Identification (RFID) tag reader components, NFC smart tag detection components, optical reader components (e.g., an optical sensor to detect one-dimensional bar codes such as Universal Product Code (UPC) bar code, multi-dimensional bar codes such as Quick Response (QR) code, Aztec code, Data Matrix, Dataglyph, MaxiCode, PDF417, Ultra Code, UCC RSS-2D bar code, and other optical codes), or acoustic detection components (e.g., microphones to identify tagged audio signals). In addition, a variety of information may be derived via the communication components 1162, such as, location via Internet Protocol (IP) geo-location, location via Wi-Fi® signal triangulation, location via detecting a NFC beacon signal that may indicate a particular location, and so forth.
Although an overview of the inventive subject matter has been described with reference to specific example embodiments, various modifications and changes may be made to these embodiments without departing from the broader scope of embodiments of the present disclosure. Such embodiments of the inventive subject matter may be referred to herein, individually or collectively, by the term “invention” merely for convenience and without intending to voluntarily limit the scope of this application to any single disclosure or inventive concept if more than one is, in fact, disclosed.
The embodiments illustrated herein are described in sufficient detail to enable those skilled in the art to practice the teachings disclosed. Other embodiments may be used and derived therefrom, such that structural and logical substitutions and changes may be made without departing from the scope of this disclosure. The Detailed Description, therefore, is not to be taken in a limiting sense, and the scope of various embodiments is defined only by the appended claims, along with the full range of equivalents to which such claims are entitled.
As used herein, the term “or” may be construed in either an inclusive or exclusive sense. Moreover, plural instances may be provided for resources, operations, or structures described herein as a single instance. Additionally, boundaries between various resources, operations, modules, engines, and data stores are somewhat arbitrary, and particular operations are illustrated in a context of specific illustrative configurations. Other allocations of functionality are envisioned and may fall within a scope of various embodiments of the present disclosure. In general, structures and functionality presented as separate resources in the example configurations may be implemented as a combined structure or resource. Similarly, structures and functionality presented as a single resource may be implemented as separate resources. These and other variations, modifications, additions, and improvements fall within a scope of embodiments of the present disclosure as represented by the appended claims. The specification and drawings are, accordingly, to be regarded in an illustrative rather than a restrictive sense.
This written description uses examples to disclose certain embodiments of the present invention, including the best mode, and also to enable any person skilled in the art to practice those certain embodiments, including making and using any devices or systems and performing any incorporated methods. The patentable scope of the present invention is defined by the claims, and may include other examples that occur to those skilled in the art. Such other examples are intended to be within the scope of the claims if they have structural elements that do not differ from the literal language of the claims, or if they include equivalent structural elements with insubstantial differences from the literal language of the claims.

Claims

1. A target enclosure comprising:

a target arm rotatable about a first axis between a first position and a second position, the target arm including:

a target plate configured to be exposed to projectile fire of a shooter when in the first position; and

a counterbalance lever arm coupled to the target plate; and

a pneumatic system including:

an air compressor providing compressed air to the pneumatic system;

a dual-action pneumatic cylinder having a piston rod, the piston rod being coupled to the counterbalance lever arm; and

at least one valve configured to provide the compressed air to the dual-action pneumatic cylinder causing the piston rod to actuate between an extended state and a retracted state, thereby causing the target arm to rotate about the first axis between the first position and the second position.

2. The target enclosure of claim 1, wherein the dual-action pneumatic cylinder maintains the target arm substantially in the first position while in the retracted state and in the second position while in the extended state.

3. The target enclosure of claim 1 further comprising a hit sensor configured to detect a projectile strike to the target arm.

4. The target enclosure of claim 3 further comprising a microcontroller configured to:

receive projectile strike data from the hit sensor while the target arm is in the first position;

determine, from the projectile strike data, that a number of projectile strikes has reached a pre-determined threshold; and

lower the target arm based on the determining.

5. The target enclosure of claim 1 further comprising a microcontroller communicatively coupled to the at least one valve, the microcontroller configured to:

transmit a signal to the at least one valve to cause the compressed air to flow into a first port of the dual-action pneumatic cylinder, thereby causing the piston rod to actuate from the retracted state to the extended state; and

transmit a signal to the at least one valve to cause the compressed air to flow into a second port of the dual-action pneumatic cylinder, thereby causing the piston rod to actuate from the extended state to the retracted state.

6. The target enclosure of claim 1, wherein the at least one valve further includes a flow control orifice configured to exhaust at least some air as the piston rod actuates between the extended state and the retracted state.

7. The target enclosure of claim 1 further comprising at least one torsion spring including a first spring arm in contact with the counterbalance lever arm, the torsion spring being configured to be in a compressed state when the target arm is in the second position and in an uncompressed state when the target arm is in the first position, thereby contributing energy during decompression as the target arm moves from the second position to the first position.

8. The target enclosure of claim 1 further comprising:

a microcontroller;

a power supply configured to provide power to at least the air compressor and the microcontroller; and

a flyback diode connected to a positive lead and a negative lead of the air compressor, the flyback diode configured to protect at least the microcontroller from voltage spikes caused by the air compressor.

9. A shooting system including:

a first target enclosure including:

a target arm;

a pneumatic system configured to raise and lower the target arm; and

a first target controller in communication with the pneumatic system and configured to cause the pneumatic system to raise and lower the target arm; and

a control unit including:

a control unit controller in networked communication with the first target controller, the control unit controller configured to transmit one of a raise event and a lower event to the first target controller, thereby causing the target arm to raise and lower.

10. The shooting system of claim 9, wherein the first target enclosure further includes a hit sensor in communication with the first target controller, the first target controller is configured to transmit projectile strike data to the control unit.

11. The shooting system of claim 10, wherein the control unit further includes a display interface, wherein the control unit is further configured to present the projectile strike data to a shooter using the display interface.

12. The shooting system of claim 9, wherein the control unit is further configured to:

receive a pressure value from the first target enclosure, the pressure value being associated with the pneumatic system;

determine that the pressure value is below a pre-determined threshold; and

transmit a compressor activation command to the first target enclosure, thereby activating an air compressor of the pneumatic system.

13. The shooting system of claim 9, wherein the control unit is further configured to:

select a hit count; and

transmit the hit count to the first target controller,

wherein the first target controller is further configured to:

receive the hit count;

initiate a first raise event, thereby causing the pneumatic system to raise the target arm;

count a number of projectile impacts to the target arm after initiation of the first raise event; and

initiate a first lower event after the number of projectile equals or exceeds the hit count.

14. The shooting system of claim 9 further comprising a second target enclosure including a second target controller in networked communication with the second controller, wherein the control unit is further configured to coordinate target presentation between the first target enclosure and the second target enclosure.

15. The shooting system of claim 14, wherein the controller unit is further configured to cause only one of the first target enclosure and the second target enclosure to be presented at a time.

16. The shooting system of claim 9, wherein the controller unit is further configured to transmit a first raise event to the first target controller, wherein the first target controller is further configured to:

receive the first raise event;

select a hit count;

initiate the first raise event, thereby causing the pneumatic system to raise the target arm;

17. The shooting system of claim 9, wherein the control unit is further configured to transmit a target uptime value to the first target controller, wherein the first target controller is further configured to:

receive the target uptime value;

initiate a timer; and

initiate a first lower event after the timer has ran for the target uptime value.

18. A computer-implemented method for providing a training routine for a shooter, the method comprising:

selecting, by a hardware processor, a first hit count associated with a first target enclosure;

transmitting the first hit count to the first target enclosure;

receiving, by the hardware processor, indication from the first target enclosure that a number of projectile impacts on the first target enclosure equals or exceeds the hit count;

after receiving indication from the first target enclosure, selecting, by the hardware processor, a second hit count associated with a second target enclosure; and

transmitting the second hit count to the second target enclosure.

19. The method of claim 18 further comprising:

transmitting a first raise event to the first target enclosure,

wherein receiving indication from the first target enclosure further includes:

receiving projectile strike data from the first target enclosure, the proj ectile strike data including a number of projectile impacts on the first target enclosure;

comparing, by the first hardware processor, the number of projectile impacts on the first target to the first hit count; and

determining, by the first hardware processor, that the first hit count has been reached or exceeded based on the comparing.

20. The method of claim 18 further comprising:

receiving, by the hardware processor, first projectile strike data from the first target enclosure;

receiving, by the hardware processor, second projectile strike data from the second target enclosure; and

displaying the first projectile strike data and the second projectile strike data to the shooter during the training routine via a display device.