None.
None.
RuBee® is a registered trademark of Visible Assets, Inc. of the United States. Other names used herein may be registered trademarks, trademarks or product names of Visible Assets, Inc. or other companies.
The invention disclosed broadly relates to the field of firearms and more specifically to monitoring the maintenance for a firearm.
When firearms are shot the barrel and its other parts experience various degrees of wear and tear. In the case of semi-automatic or automatic firearms (such as the SigSauer 556 or Colt M41A automatic rifles), each firing cycle results in the expansion of the chamber by the hot corrosive gases, the acceleration of the bullet down the barrel, and an ejection of the spent case and re-loading of a new cartridge for the next firing cycle. This cycle may be repeated in different rates such as single shots, burst fire (e.g. 3 shots in rapid succession) and full automatic fire. All of the weapons parts wear, including those in the gun's action and barrel such as the hammer, firing pin, and the bolt, as well as the chamber, gas ports/vents, barrel, and the various springs, screws, and washers in a gun that control the magazine, control recoil, control gases, and control movement of bullets into the chamber.
The parts become progressively worn until they are no longer serviceable and must be repaired or replaced. In many cases the wear status of these parts and overall usefulness (accuracy) and safety of the firearm is directly proportional to the number of shots that have been fired. Therefore, routine maintenance on a firearm is critical, especially for professionals who depend on the accuracy and reliability of the weapon, such as those in the military and law enforcement disciplines. Unfortunately, the need for routine maintenance is typically calculated by the shooter's memory of the type (rapid fire versus single shot), firing cadence and the total number of shots fired since the prior maintenance.
This is not accurate because humans can fail to remember the exact total number of shots fired or the proportion of those shots fired at a specific rate of fire (also known as cadence), especially in war or other hostile situations. For example, a manufacture may recommend that routine maintenance be performed (for example, changing the springs) after 3,000 rounds. Or, after 10,000 rounds the barrel should be replaced, and so on. In many other weapons the wear and tear may be accelerated depending upon how close the rounds were fired together. This is especially true in automatic and semi-automatic weapons that can fire up to 13-15 rounds per second. At this rate the heat generated from bullets can have a harmful affect on the barrel and other moving parts, especially if it is a sustained action. For example, if a specific firearm (automatic or semi-automatic type) has a total of 3,000 rounds fired over its lifetime, the rate of fire for these past firings has a profound effect on the maintenance required by the firearm. For a specific type and model of firearm, a firing rate of one shot per second for 3,000 rounds may be acceptable for maximum barrel life, bolt life, spring life and overall maximum lifespan of the weapon. However, if the same 3,000 rounds are shot at much higher rates of fire such as ten rounds per second, the accelerated wear may make the weapon inaccurate, or unusable and unsafe.
For more background on the effect of shot cadence and accuracy, reliability, and safety for military firearms, refer to the public document “SOPMOD Program Overview” published by the NSWC of the US Navy on April, 2006.
Therefore a system that monitors shots and shot timing is necessary for these weapons.
Briefly, according to an embodiment of the present invention, a method for identifying, tracking, and monitoring a firearm includes steps of: attaching a low frequency radio tag to the firearm; storing, in the data storage device of the radio tag, identification data relating to the firearm and data related to the shot count; reading the identification data from the transceiver by interrogating the radio tag; and transmitting the identification data and shot count data. The radio tag includes a shot sensor, a shot count register for tracking the number of shots fired and cadence registers for tracking the intervals between shots.
To describe the foregoing and other exemplary purposes, aspects, and advantages, we use the following detailed description of an exemplary embodiment of the invention with reference to the drawings, in which:
While the invention as claimed can be modified into alternative forms, specific embodiments thereof are shown by way of example in the drawings and will herein be described in detail. It should be understood, however, that the drawings and detailed description thereto are not intended to limit the invention to the particular form disclosed, but on the contrary, the intention is to cover all modifications, equivalents and alternatives falling within the scope of the present invention.
We describe a mean kinetic shot (MKC) system and method for providing automatic shot counting and maintenance management of firearms within a network. The MKC system uses the RuBee® radio tag as described in co-pending application Ser. No. 12/108,877. The net effect is that the MKC empirically reflects the actual wear and tear on the weapon based not simply on number of shots, but how fast those shots were fired.
According to the present invention, a method and apparatus stores shot data to create a simplified way to monitor and gauge the overall effect of firing rate fluctuation or variation on the lifespan of a firearm. The method further provides an indicator of the safety and/or accuracy of a specific firearm as a single calculated value. This value, called a Mean Kinetic Shot Count or MKSC, is a weighted average of fired shots.
The key feature of this invention is the RuBee® active tag system. RuBee® is a radio tag technology designed to provide full asset visibility and identification in harsh environments. The tags use the standard, IEEE P1902.1, “RuBee Standard for Long Wavelength Network Protocol,” which allows for networks encompassing thousands of radio tags operating below 450 KHz. RuBee® networks provide for real-time tracking under harsh environments, e.g., near metal and water and in the presence of electromagnetic noise. The tags are also programmable.
Background on RuBee® Radio Tags.
Radio tags communicate via magnetic (inductive communication) or electric radio communication to a base station or reader, or to another radio tag. A RuBee® radio tag works through water and other bodily fluids, and near steel, with an eight to fifteen foot range, a five to ten-year battery life, and three million reads/writes. It can operate at 132 KHz and is a full on-demand peer-to-peer, radiating transceiver.
RuBee® is a bidirectional, on-demand, peer-to-peer transceiver protocol operating at wavelengths below 450 KHz (low frequency). A transceiver is a radiating radio tag that actively receives digital data and actively transmits data by providing power to an antenna. A transceiver may be active or passive. The RuBee® standard is documented in the IEEE Standards body as IEEE P1902.1.
Low frequency (LF), active radiating transceiver tags are especially useful for visibility and for tracking both inanimate and animate objects with large area loop antennas over other more expensive active radiating transponder high frequency (HF)/ultra high frequency (UHF) tags. These LF tags function well in harsh environments, near water and steel, and may have full two-way digital communications protocol, digital static memory and optional processing ability, sensors with memory, and ranges of up to 100 feet. The active radiating transceiver tags can be far less costly than other active transceiver tags (many under one dollar), and often less costly than passive back-scattered transponder RFID tags, especially those that require memory and make use of EEPROM. With an optional on-board crystal, these low frequency radiating transceiver tags also provide a high level of security by providing a date-time stamp, making full AES (Advanced Encryption Standard) encryption and one-time pad ciphers possible.
One of the advantages of the RuBee® tags is that they can transmit well through water and near steel. This is because RuBee® operates at a low frequency. Low frequency radio tags are immune to nulls often found near steel and liquids, as in high frequency and ultra high-frequency tags. This makes them ideally suited for use with firearms made of steel. Fluids have also posed significant problems for current tags. The RuBee® tag works well through water. In fact, tests have shown that the RuBee® tags work well even when fully submerged in water. This is not true for any frequency above 1 MHz. Radio signals in the 13.56 MHz range have losses of over 50% in signal strength as a result of water, and anything over 30 MHz have losses of 99%.
Another advantage is that RuBee® tags can be networked. One tag is operable to send and receive radio signals from another tag within the network or to a reader. The reader itself is operable to receive signals from all of the tags within the network. These networks operate at long-wavelengths and accommodate low-cost radio tags at ranges to 100 feet. The standard, IEEE P1902.1, “RuBee Standard for Long Wavelength Network Protocol,” will allow for networks encompassing thousands of radio tags operating below 450 KHz.
The inductive mode of the RuBee® tag uses low frequencies, 3-30 kHz VLF or the Myriametric frequency range, 30-300 kHz LF in the Kilometric range, with some in the 300-3000 kHz MF or Hectometric range (usually under 450 kHz). Since the wavelength is so long at these low frequencies, over 99% of the radiated energy is magnetic, as opposed to a radiated electric field. Because most of the energy is magnetic, antennas are significantly (10 to 1000 times) smaller than ¼ wavelength or 1/10 wavelength, which would be required to efficiently radiate an electrical field. This is the preferred mode.
As opposed to the inductive mode radiation above, the electromagnetic mode uses frequencies above 3000 kHz in the Hectometric range, typically 8-900 MHz, where the majority of the radiated energy generated or detected may come from the electric field, and a ¼ or 1/10 wavelength antenna or design is often possible and utilized. The majority of radiated and detected energy is an electric field.
RuBee® tags are also programmable, unlike RFID tags. The RuBee® tags may be programmed with additional data and processing capabilities to allow them to respond to sensor-detected events and to other tags within a network.
Additionally, RuBee® tags can be coupled with sensors so that activity parameters, such as shots fired can be accurately determined. RuBee® tags and base stations produce only microwatts of radio energy and it is this low output that makes them ideal for hospital and operating room (OR) applications. These signals are of such low frequency that there is no biological interaction. Labeled as a non-significant risk, RuBee® tags have no effect on cardiac pacemakers and automated external defibrillators (AEDs). RuBee® has a field strength that is even lower than that of airport metal detectors and antitheft detectors in retail stores.
Radio tags communicate via magnetic (inductive communication) or electric radio communication to a base station or reader, or to another radio tag. A RuBee® radio tag works through water and other bodily fluids, and near steel, with an eight to fifteen foot range, a five to ten-year battery life, and three million reads/writes. It operates at 132 kHz and is a full on-demand peer-to-peer, radiating transceiver.
RuBee® is a bidirectional, on-demand, peer-to-peer transceiver protocol operating at wavelengths below 450 kHz (low frequency). A transceiver is a radiating radio tag that actively receives digital data and actively transmits data by providing power to an antenna.
Low frequency (LF), active radiating transceiver tags are especially useful for visibility and for tracking both inanimate and animate objects with large area loop antennas over other more expensive active radiating transponder high frequency (HF)/ultra high frequency (UHF) tags. These LF tags function well in harsh environments, near water and steel, and may have full two-way digital communications protocol, digital static memory and optional processing ability, sensors with memory, and ranges of up to 100 feet. The active radiating transceiver tags can be far less costly than other active transceiver tags (many under one US dollar), and often less costly than passive back-scattered transponder RFID tags, especially those that require memory and make use of an EEPROM.
With an optional on-board crystal, these low frequency radiating transceiver tags also provide a high level of security by providing a date-time stamp, and make it possible to associate elapsed time with shots fired in order to record the shot cadence.
Firearm Embodiment.
Referring now in specific detail to the drawings and particularly
The grip is the preferred location for the tag 102, but not necessarily the only location that the RuBee tag 102 can be used. The tag 102 may be affixed to the outside of the firearm 100, although this is not the preferred arrangement. The radio tag 102 as shown in this example is preferably placed in the handgun grip, but it could be placed in another part of the firearm 100 if a different firearm form factor is used. The placement of the radio tag 102 depends on the form factor of the weapon and the size of the weapon. The tag 102 in this example is embedded into a cavity of the inside of the grip. Embedding the tag 102 in this manner is the preferred embodiment. Alternatively, the tag 102 may be affixed to the firearm 100 by attaching it to the outside surface of the weapon, but this is not recommended. The tag 100 may be constructed with a waterproof housing made to sustain wear and tear, yet remain lightweight.
The tag 102 is able to detect shots fired through a sensor using known detection technology, such as that used in piezoelectric sensors and inertial sensors. The sensor technology is analogous to that used with the currently popular Nintendo® Wii™ game console. Because the sensor can be very small, it is ideal for use with handguns and can easily fit within the handle of a handgun. One sensor is able to detect each shot that is fired through the chamber of the firearm, thus providing the ability to count the shots. By incorporating a timing device into the tag, such as a crystal, the cadence of the shots can be tracked as well.
For example, if a tag 102 associated with a specific firearm 100 has detected a total of 5,000 rounds fired, with 4,000 of those rounds fired in full automatic mode (e.g. 950 round/min for an M4A1 carbine in full-auto mode), and 1,000 rounds fired as single semi-automatically fired rounds with a rate less than 30 rounds/min, then a weighted average of the two values is useful in determining the effect of the shots fired on the weapon.
In another embodiment of the present invention, the MKSC provides a more meaningful measurement when it provides greater weight to additional factors. For example, more weight may be given to full-automatic firing rates versus slower firing rates. In one example, a firing rate will be assigned a progressively decreased weighting from a fire rate of 750-950 rounds/min, 500-750 rounds/min, 250-500 rounds/min, 100-250 rounds/min, to single shots at 60 rounds/min. The weights can be pre-loaded into the tag 102. Preferably, the weights are loaded into separate registers, with one fire rate associated with each register. Then, the number of shots fired at each firing rate are loaded into (added into) the appropriate register. This makes the calculation of a weighted average a simple matter of multiplying the count in each register by its associated weight value, then adding the products.
To further increase the meaningfulness of the MKSC, the weighting can be modified according to the specific weapon used (e.g. SigSauer 556, FN SCAR-H (7.62 mm) or FN SCAR-L (5.56 mm) or the Colt M4A1) and also other factors, such as ammunition type (size, power), barrel length, or if there is a specific rest or cooling period between rounds being fired at a specific rate (e.g. 0-60 seconds, 61-300 seconds, 301-600 seconds, over 600 seconds) and so forth.
For example, assume we are to provide a MKSC for a firearm with a total shot count of 5,000 rounds. Of those 5,000 rounds, 4,000 rounds are fired at 750-900 rounds/min. However, this weapon could have been fired as a combination of 400 ten shot full-auto groups each with a large cool down period of over 10 minutes (600 seconds) between each 10 shots. Alternatively, the rounds may have been fired with 10 seconds cool down between each 10 round full-auto burst. These scenarios can affect the cumulative stress on the weapon and therefore its overall lifespan, reliability, accuracy, and safety.
In order to apply a meaningful weighting, a preferred embodiment of the present invention uses a statistical database of firearm performance parameters correlated against the recorded shot cadences and the other stored values in the shot counting tag disclosed in the present invention.
Referring to
The antenna 280 shown in
The energy source shown in this example is a battery 240, preferably a lithium (Li) CR2525 battery approximately the size of an American quarter-dollar with a five to fifteen year life and up to three million read/writes. Note that only one example of an energy source is shown. The tag 102 is not limited to a particular source of energy, the only requirement is that the energy source is small in size, lightweight, and operable for powering the electrical components.
The tag 102 also includes a memory 230 and a four bit microprocessor 210, using durable, inexpensive 4 micron CMOS technology and requiring very low power. What has been shown and discussed so far is a basic embodiment of the tag 102. With the components as discussed, the tag 102 can perform the following functions: 1) the tag 102 can be configured to receive (via the modem 220) and store data about the firearm to which it is attached and/or the network to which it belongs (in the memory 230); 2) the tag 102 can emit signals which are picked up by a reader, the signals providing data about the firearm; 3) the tag 102 can store data in the form of an internet protocol address so that the tag's data can be read on the internet.
Note that the electrical components of the tag 102 are housed within the body of the tag 102 and are completely enclosed within the tag 102 when the device is sealed. This makes the tag 102 waterproof and tamperproof. All communications take place at very low frequencies (e.g. under 300 kHz). By using very low frequencies the range of the tag 102 is somewhat limited; however power consumption is also greatly reduced. Thus, the receiver of modem 220 may be on at all times and hundreds of thousands of communication transactions can take place, while maintaining a life of many years (up to 15 years) for battery 240.
Operatively connected to the modem 220 is a RuBee® chipset 225. The chipset 225 is configured to detect and read analog voltages. The chipset 225 is operatively connected to the modem 220 and the microprocessor 210.
The tag's memory 230 records the shots fired as detected by the sensor 250 in accordance with their firing cadence or rate or other factors (e.g. rest or cool down interval). Each shot that is fired can be counted and then recorded to a specific memory “bin” or register which identifies how fast the shot was fired.
As shown in
For any shots fired over a pre-determined reasonable period of time (one second in this example) there is no need to store interval data. If all 5,000 rounds are fired at 10/second in this example register number 2 will be equal to the count in register 0. This indicates that the gun's wear and tear is high.
When it is determined that a particular firearm exceeds a pre-determined optimal MKSC then it may be brought in for preventative maintenance. Once maintenance is performed, the counts can be reset back to zero. A user can easily track the shot count status at any point in time by simply reading the information using a reader, such as a handheld reader, or picking up the information at a base station and transferring it to a computer. A web interface can be used to keep track of shot count for all of the weapons within a network, such as a police force, or military organization. In this manner, a user can monitor the MSKC for each firearm from a remote location and then advise the handler of the firearm when it is time to perform maintenance. This frees the soldier or officer on the field from having to keep track of the maintenance requirements.
In another embodiment, depending upon a weapon type, a weighted calculation is used, taking into account the interval data stored in registers 1-14 or similar intervals. The total number of shots fired stored in register 0, plus a weighted sum of the interval registers 1-14, can be used to establish maintenance and stats for the weapon 100. The weights may be empirical and determined based on actual wear and tear. For example, register 1 may have a weight of 10, 3 of 7 and so on based on the weapon and measured wear. The final calculated number is called the Mean Kinetic Shot Count and can be tied to maintenance schedules and weapons replacement. A typical weapon MKC profile might look like:
MKC=Shot Counter+(R2*.8+R3*.6+R4*.3+R5*.2+R6*.1+R6*.05+R7*.05)
The activity parameter sensor 250 can detect the number of shots fired by using a piezoelectric sensor or by detecting the number of projectiles remaining in the cartridge. Another sensor 250 may be able to detect if the tag 102 has been removed from the handgun. In fact, additional sensors may be placed on the back of the tag 102 for just this purpose. Each instance of motion and/or acceleration is a status event and it is detected by the sensor 250. Sensors 250 are ideal for providing an event history of the event statuses they detect. Other sensors not mentioned here may be advantageously used within the spirit and scope of the invention.
Additionally, a clock 260 may be included inside the tag 102. The clock 260 can provide a time history to correspond with status events detected by the sensors 250. The clock 260 can be configured to provide a time signal to correspond with a signal emitted by the sensor 250. The processor 210 records the time signal together with the sensor signal in order to provide a temporal history that can be mapped to a status history. The history data can be stored in the memory 230 along with status events. Tying events to a time stamp provides for a more meaningful history of events. For example, mapping shots fired to a date and time affords very useful information.
The tag 102 may be programmed to emit a warning signal when at least one of the sensors 250 detects a condition that meets a predetermined value. For example, a sensor 250 in the tag 102 may emit a signal when the ammunition falls below a predetermined amount. A jog sensor 250 may emit a signal when the weapon 100 has been dropped. A signal could also be emitted when it is time to perform maintenance on the weapon 100.
To secure the stored data in the tag 102 an onboard crystal may be used to provide optical encoding using liquid crystal spatial light modulators. One-time pad ciphers are another security measure that can be advantageously used with a radio tag 102. Using known security measures with the radio tag 102 is recommended when needed to assure that the tag data does not fall into the wrong hands.
The router 290 of
The data storage within the tag 102 can store all of the information necessary to identify the weapon, its owner/carrier and its event history. Some of the data fields for weapon identification may include: a unique identifier for the weapon, its date of purchase, its location, its affiliation (such as police department), and its current maintenance status. Note that this is merely a representative sampling of the data which can be stored in a tag 102. As stated earlier, the data stored in the tags 102 is easily accessible via a handheld reader as shown in
Gathering information about one weapon is important. Equally important, if not more so, is gathering information about all of the weapons within a network. Note that in this discussion we refer to a “network” of weapons as all of the weapons within one networked RuBee® tag system. A network of weapons may or may not be restricted to one affiliation (such as a police department) or group of weapons (all revolvers). It is critical to track the shots fired, event histories, maintenance schedules, and condition of the weapons to be able to predict future events and to know what conditions will need to be changed and/or further monitored. It is well known in the art of database software that manipulating data in different ways produces different views of the data. Data from RuBee® tags 102 can be used for various purposes within the scope of this invention.
Next in step 620, other data concerning the weapon is entered. This data may be the model number, the purchase date, the affiliation (agency, police department), and/or the maintenance record of the weapon, to name just a few data items that can be stored in the tag 102. The tag 102 is enabled to constantly transmit low frequency radio signals through its modem 220. The radio tag 102 may also transmit a signal or signals responsive to the detection of a status event, such as a change in ammunition status of the weapon. Note that the data may be entered before attaching the tag 102 to the firearm 100.
In step 630 the tag registers are pre-loaded with the applicable weights. Pre-selected benchmarks are also programmed into the tag 102. These benchmarks may be: when the shot count reaches 1,000 the gun must be cleaned; when the shot count reaches 3,000, a signal must be transmitted to the base station requesting more ammunition; when more than 100 shots have been fired at a cadence over eight shots per second, a warning signal should be emitted, and so forth.
In step 640 the firearm 100 is put into (or returned to) service. In step 650 the shot counter records each shot fired, and the cadence of the shots is recorded in the appropriate registers. In step 650 at predetermined intervals, the MKSC is calculated from the data stored in the registers. Alternatively, the MKSC can be calculated and stored on a continuous basis, in real-time.
In step 660 an onboard sensor emits a signal when a benchmark is reached. The signal will indicate that maintenance should be performed on the firearm. Alternatively, a user monitoring the MKSC may transmit a signal to the tag 102 in order to sound an alarm so that the firearm handler knows to perform maintenance.
In step 670 the data from the tag 102 is transmitted to a remote location for storage before the registers are zeroed. In this way, complete service data is kept for each firearm 100. The radio tag 102 signals are picked up by a reader operable to receive low frequency radio signals below 450 kilohertz within range of the tag antenna 280. The reader may be a handheld reader, such as a wand reader. The signals may also be picked up by a router 290, or another tag in the network. The data is then transmitted via a wireless connection (or a wired connection if a local network is used) to a computer. The data may be encrypted with known encryption methods. As stated earlier, a web interface is an ideal way to provide secure access to meaningful data. A user will be required to log into the network. The firearm data can be accessed individually by selecting the unique identifiers for each firearm, or the firearm network data can be viewed in its entirety.
In step 680 after a full maintenance is performed, the registers are zeroed out. This zeroing out can be activated remotely when the processor 210 receives a signal that maintenance has been performed. The processor 210 can then perform a load instruction to load zeroes into the registers. In an alternative embodiment, a handler performing full maintenance on the firearm 100 disassembles the firearm 100, exposing the radio tag 102. A button on the tag 102 can be pressed once the maintenance is complete. This is analogous to a driver pressing a button to zero out a trip counter at the end of a car trip.
In step 690 the transmitted data, after it is decrypted, if necessary, is viewable through a computer. The data may be accessed from a database configured to process the tag data and displayed through a computer monitor, or a personal digital assistant (PDA) screen, a cell phone display, or any other display means according to advancing technology. The data may also be viewable via web browser. When the data is available on the Internet, it then becomes critical to safeguard the data, either by requiring a login and password, or using data encryption methods known in the art. In one embodiment, the login name may be the serial number of the weapon.
In step 695, the data gathered from the tag 102 or all of the tags in the network may be compiled into a report such as that shown. The report may be confined to one particular weapon, showing event and time histories for that weapon, or it may report on some or all of the weapons within an inventory shelf or a network. The report may be produced daily, monthly, seasonally, or yearly. The report may be automatically generated or may be generated upon user request. Optionally, a report may be auto-generated according to data received from the tag 102 which meets a pre-determined condition. For example, a user might want a report on a particular weapon generated when an ammunition sensor registers that the weapon has been fired. The report may be viewable on the Internet and/or distributed to appropriate personnel.
Therefore, information gathered from a report may be used to add to or change the programming of the tags. To implement this, a user would make any needed changes on a computer. The data is transmitted to a RuBee® router 290 which in turn communicates with a radio tag 102 through its antenna (either the tag antenna directly or a field antenna). The modem 220 of the tag 102, using the chipset 225 transmits the signals to the processor 210. The processor 210 records the data and makes the necessary changes. Many other additions and modifications can be made to the data to assist an end user in monitoring and tracking weapons within a network.
Therefore, while there have been described what are presently considered to be the preferred embodiments, it will be understood by those skilled in the art that other modifications can be made within the spirit of the invention. The above descriptions of embodiments are not intended to be exhaustive or limiting in scope. The embodiments, as described, were chosen in order to explain the principles of the invention, show its practical application, and enable those with ordinary skill in the art to understand how to make and use the invention.
This application is a non-provisional of and claims priority from, U.S. Patent Application Ser. No. 61/084,165, filed on Jul. 28, 2008, which is a continuation-in-part of, and claims priority from, commonly-owned, co-pending U.S. patent application Ser. No. 12/108,877, “Firearm Visibility Network,” filed on Apr. 24, 2008, which application is incorporated by reference as if fully set forth herein.
Number | Date | Country | |
---|---|---|---|
61084165 | Jul 2008 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 12108877 | Apr 2008 | US |
Child | 12510000 | US |