The present invention relates to tracking devices for communication and locating tools and other devices.
In one embodiment, a power tool tracking clip is provided. The power tool tracking clip includes a wireless beacon transmitter that includes a memory storing an identifier and a transmitter configured to wirelessly transmit the identifier, a clip body that has a beacon receptacle, the wireless beacon transmitter positioned within the beacon receptacle. A first arm member is coupled to a first end of the clip body and has a first inner surface configured to engage a power tool. A second arm member coupled to a second end of the clip body has a second inner surface configured to engage the power tool. A mounting feature on the first arm member aligns with a corresponding mounting feature on a corresponding outer wall of the power tool when the power tool tracking clip is mated to the power tool. In some embodiments the second arm member includes a second mounting feature that aligns with a corresponding mounting feature on an outer wall of the power tool when the power tool tracking clip is mated to the power tool.
In some embodiments, the first arm member and second arm member define an opening, or power tool receiving portion, to receive the power tool. In some embodiments, the opening has a u-shape. In some embodiments, a belt clip accessory is received by the first arm member or the second arm member for fastening the belt clip accessory and the power tool tracking clip to the power tool. In some embodiments, a bit clip accessory is received by the first arm member or the second arm member for fastening the bit clip accessory and the power tool tracking clip to the power tool.
In some embodiments the mounting feature on the first arm member includes a screw hole that aligns with a screw hole on the corresponding mounting feature of the power tool for fastening the power tool tracking clip to the power tool. The first arm member and the second arm member may be flexible and inwardly biased to grip the power tool. In some embodiments the wireless beacon transmitter repeatedly transmits a first beacon signal and subsequently transmits a second advertising beacon signal comprising the identifier.
In another embodiment, a method is provided for tracking a power tool. The method includes receiving a power tool by a power tool tracking clip having a clip body. A wireless beacon transmitter is received in a beacon receptacle of the clip body. An identifier is stored in a memory of the wireless beacon transmitter and is wirelessly transmitted to an external device. The power tool tracking clip includes a first arm member coupled to a first end of the clip body. The first arm member has a first inner surface configured to engage the power tool. The power tool tracking clip includes a second arm member coupled to a second end of the clip body. The second arm member has a second inner surface configured to engage the power tool. A mounting feature on the first arm member aligns with a corresponding mounting feature on an outer wall of the power tool when the power tool tracking clip is mated to the power tool.
In some embodiments of the method, receiving of the power tool in the power tool tracking clip includes receiving the power tool in an opening of a receiving portion of the power tool tracking clip defined by the first arm member and the second arm member. In some embodiments, receiving of the power tool in the power tool tracking clip includes receiving a fastener by a screw hole of the mounting feature on the first arm member and by an aligned screw hole on the corresponding mounting feature of the power tool. In some embodiments, the method further includes receiving, by at least one selected from the group of the first arm member and the second arm member, at least one selected from the group of a belt clip accessory and a bit clip accessory. In some embodiments, receiving of the power tool in the power tool tracking clip includes gripping the power tool by the first arm member and the second arm member, wherein the first arm member and the second arm member are flexible and inwardly biased to grip the power tool. In some embodiments, the method further includes separating, by the power tool tracking clip, from the power tool; receiving a tracked object other than the power tool in an opening of a receiving portion of the power tool tracking clip defined by the first arm member and the second arm member; and wirelessly transmitting the identifier to the external device after the tracked object is received by the power tool tracking clip.
In some embodiments a system is provided for tracking a power tool. The system includes a power tool including a mounting feature and a power tool tracking clip secured to the power tool. The power tool tracking clip includes a wireless beacon transmitter, a clip body, a first arm member, and a second arm member. The wireless beacon transmitter includes a memory storing an identifier and a transmitter configured to wirelessly transmit the identifier. The first arm member is coupled to a first end of the clip body and has a first inner surface engaged with the power tool. The second arm member is coupled to a second end of the clip body and has a second inner surface engaged to the power tool. The power tool tracking clip further includes a corresponding mounting feature on the first arm member, the corresponding mounting feature aligning with the mounting feature of the power tool when the power tool tracking clip is mated to the power tool.
In some embodiments of the system, the system includes an external wireless device configured to receive the identifier from the wireless beacon transmitter of the power tool tracking clip, determine a geographical location, and transmit the identifier and the geographical location to a server. In some embodiments, the system includes a second external wireless device is configured to receive the identifier from the wireless beacon transmitter of the power tool tracking clip, determine a geographical location of the second external wireless device, and transmit the identifier and the geographical location of the second external wireless device to the server.
Other aspects of the invention will become apparent by consideration of the detailed description and accompanying drawings.
Before any embodiments are explained in detail, it is to be understood that the disclosure is not limited in its application to the details of construction and the arrangement of components set forth in the following description or illustrated in the following drawings. The disclosure is capable of other embodiments and of being practiced or of being carried out in various ways.
It should also be noted that a plurality of hardware and software based devices, as well as a plurality of different structural components, may be used to implement the embodiments. In addition, it should be understood that embodiments of the disclosure may include hardware, software, and electronic components or modules that, for purposes of discussion, may be illustrated and described as if the majority of the components were implemented solely in hardware. However, one of ordinary skill in the art, and based on a reading of this detailed description, would recognize that, in at least one embodiment, the electronic based aspects of the disclosure may be implemented in software (e.g., stored on non-transitory computer-readable medium) executable by one or more electronic processors. As such, it should be noted that a plurality of hardware and software based devices, as well as a plurality of different structural components may be utilized to implement the embodiments. Furthermore, and as described in subsequent paragraphs, the specific mechanical configurations illustrated in the drawings are intended to exemplify embodiments of the disclosure and that other alternative mechanical configurations are possible. For example, “controllers” described in the specification can include processing components, such as one or more processors, one or more computer-readable medium modules, one or more input/output interfaces, and various connections (e.g., a system bus) connecting the components. In some instances, the controllers described in the specification may be implemented in one of or a combination of a microprocessor, an application specific integrated circuit (ASIC), a digital signal processor (DSP), a field programmable gate array (FPGA), or the like.
The power tool tracking clip 102 includes a wireless beacon transmitter 104 that is a communication device that includes a transmitter and communicates via wireless signals 118 (e.g., Bluetooth™ low energy transmissions) with a personal wireless device 114 configured to receive such signals. However, the wireless beacon transmitter 104 is not limited in this regard, and may be configured to communicate via a network with the personal wireless device 114 utilizing other suitable wireless technology supported by the personal wireless device 114. The wireless beacon transmitter 104 may be referred to as a beacon transmitter. The personal wireless device 114 (also referred to as a receiving device) may be, for example, a mobile smart phone, laptop computer, desktop computer, personal digital assistant (PDA), or other receiving device. Personal wireless device 114 communicates via a network 108 with the location server 116. The network 108 may include one more of a local area network (LAN), wide area network (WAN) (e.g., the Internet), a cellular network, or other networks.
As described in further detail below, the wireless beacon transmitter 104 may transmit a wireless signal 118 and the personal wireless device 114 may receive the wireless signal 118. The signal 118 may include beacon data from the wireless beacon transmitter 104. The beacon data may include one or more of a transmitter identifier, a user identifier, user contact information, timestamp, state of charge of a battery (110, shown in
The location server 116 includes a tracking database 112. A tracking application may be executed by an electronic processor of the location server 116. The tracking application receives tracking data from the personal wireless device 114, updates the tracking database 112, and receives and responds to database queries for the tracking database 112. The tracking database 112 stores tracking data for the beacon transmitter 104 including one or more of a transmitter identifier, a user identifier (e.g., an owner or user of the beacon transmitter 104), user contact information, timestamp, last known location, state of charge of the battery 110, other status information, personal wireless device identifier (e.g., identifying the most recent personal wireless device 114 that received communications from the beacon transmitter 104 and communicated to the location server 116), and location history (e.g., including previous known locations, timestamps, and personal wireless device identifiers). The tracking database 112 also stores a lost/not-lost indication (e.g., a flag) that indicates, based on a value of the indicator, whether the beacon transmitter 104 is considered “lost” or “not lost.”
Although a single beacon transmitter 104 is illustrated in
Although the location server 116 is illustrated as a singular unit, the location server 116 may be made up of various servers located together or remotely and coupled via one or more networks. Similarly, the tracking database 112 may be made up of various databases in communication with one another. In some embodiments, in instances when the system 100 includes a plurality of personal wireless devices 114 that each receive a wireless beacon signal from the wireless beacon transmitter 104, and forward signal information to the location server 116, the location server 116 may determine a location of the power tool 106 based on multiple reference points provided by the plurality of personal wireless devices 114.
The illustrated power tool 106 is a drill powered by a removable battery pack 119. Although the power tool 106 is illustrated in
In operation, the power tool 106 may be received and secured by a power tool tracking clip 102 that includes the wireless beacon transmitter 104. The wireless beacon transmitter 104 may store an identifier and may wirelessly transmit the identifier to the personal wireless device 114 via the wireless communication link 118. In some embodiments, when the personal wireless device 114 receives a signal from the wireless beacon transmitter 104, the personal wireless device 114 may determine that the wireless beacon transmitter 104 and/or an attached power tool 106, are within a limited distance from the personal wireless device 114 according to a known range for wireless communication used by the wireless beacon transmitter 104, for example, Bluetooth™ low energy transmissions.
In some embodiments, the personal wireless device 114 may be operable to determine a location or proximity of the wireless beacon transmitter 104 relative to the wireless personal device 114 based on characteristics of a received signal from the wireless beacon transmitter 104. In some embodiments, the personal wireless device 114 may execute an application that presents information about the location or proximity of the wireless beacon transmitter 104, for example, in display, or with an audible alert to a user. In some embodiments, the wireless personal device may communicate information received from the wireless beacon transmitter 104 to the server 116 for location determination or for location tracking of the wireless beacon transmitter 104.
In some embodiments, the first arm member 212 and the second arm member 214 of the power tool tracking clip 102 define an opening 217 to receive the power tool. The opening 217, also referred to as a power tool receiving portion, may form a u-shape. Although the shape of the opening 217 is shown in
The first arm member 212 may include a mounting feature 218. The second arm member 214 may include a second mounting feature 216. The mounting features 216 and 218 may align with corresponding accessory mounting features 1100 (see
The mounting features 216 and 218 may be located in recesses 720 of the first and second arm members 212, 214. For example,
In some embodiments, other suitable mounting features may be utilized for securing the power tool tracking clip 102 to a power tool 106 or to another device. For example, the mounting features 216 and 218 may include an adhesive, hook and loop fasteners, or the like, rather than securing the power tool tracking clip 102 using fasteners through the mounting holes. Additionally, in some embodiments, the first and second arm members 212, 214 are flexible and angled inward such that the opening 217 is defined more narrowly than the portion of the power tool 106 that is received in the opening 217. The first and second arm members 212, 214 are flexed outward to receive the power tool 106 in the opening 217, and then the first and second arm members 212, 214, which are inwardly biased, grip the power tool 106. In some embodiments, the first and second arm members 212, 214 may still include the mounting features 216 and 218 to receive tool accessories, such as the belt clip or bit clip.
The power tool tracking clip 102 includes the receptacle 210 for receiving the wireless beacon transmitter 104. As described below, the wireless beacon transmitter 104 may be situated within the receptacle 210 between a back cover 206 and a front cover 208. The front and back covers 206 and 208 may secure the wireless beacon transmitter 104 within the receptacle 210, and may protect the wireless beacon transmitter 104 from being damaged during use of the power tool or upon impact.
The power tool tracking clip 102 may be a single molded object or may be assembled from multiple parts. The power tool tracking clip 102 may be made of durable plastic or metal materials.
Although,
In some embodiments, as described in further detail below, the wireless beacon transmitter 104 may repeatedly transmit, via the transmitter and wireless antenna 140, a first beacon signal and a second advertising beacon signal according to a transmission pattern, which, in some embodiments, enables power-efficient location tracking of the wireless beacon transmitter 104 and an object such as the power tool 106 to which it is attached.
The battery 110 provides direct current (DC) power to the power block 130. The battery 110 includes a housing within which is one or more battery cells, such as lithium ion (“Li-ion”) cells, Nickel-Cadium (“Ni-Cad”) cells, or cells of another chemistry type. In some embodiments, the battery 110 is a coin cell battery. In some embodiments, the wireless beacon transmitter 104 includes another power source in addition to the battery 110 or in place of the battery 110, such as a circuit for connection to alternating current power (e.g., including a rectifier), photovoltaic cells and related circuitry for solar-based power generation, or a wind-based power generator.
The power block 130 is coupled to the battery 110 via terminals of the battery 110 and matching terminals of the power block 130. The power block 130 provides DC power to components of the wireless beacon transmitter 104. The power block 130 may include power regulating and conversion circuitry to ensure that the power provided to various components of the wireless beacon transmitter 104 is at the appropriate level(s).
The controller 125 is further coupled to the wireless antenna unit 140, and the input/output (I/O) port 145. As will be described in greater detail below, the power block 130, wireless antenna unit 140, and I/O port 145 enable the wireless beacon transmitter 104 to communicate with external devices and may be collectively referred to as a physical interface.
The controller 125, which may be an electronic processor, is in communication with the memory 160. In some embodiments, the memory 160 stores and provides to the controller 125, for transmission, the data making up the first beacon signal and the second advertising beacon signal, which are described in further detail below. The memory 160 further includes, among other elements, instructions that are executed by the controller 125 to control the functions of the wireless beacon transmitter 104 described herein. Although the instructions are described as software stored in memory 160 and executed by the controller 125, the instructions may be implemented in part or wholly in hardware of the controller 125 or outside of the controller 125. For example, the instructions may be implemented by one or more separate digital signal processors (DSPs) or general purpose processors executing the instructions, or by one or more field programmable gate arrays (FPGAs) or application specific integrated circuits (ASICs). Although the memory 160 is shown as a singular unit, the memory 160 may be made up of various memories individually coupled to the controller 125 or coupled to the controller 125 via a bus. Additionally, portions of the memory 160 may be embedded within the controller 125. For instance, parameters such as a status of the battery 110 may be stored within a memory of the controller 125. The data stored in the memory 160 described herein may be provided from an external computing device via the wireless antenna 140 or I/O port 145 and stored in the memory 160 by the controller 125.
The user input 155 and sensors 170 include one or more of buttons, microphones, accelerometers, temperature sensors, humidity sensors, and light sensors capable of detecting external stimuli from the environment or the user. The user output 175 includes one or more of LEDs, a speaker, a vibrating element, etc. to inform the user of the status of the wireless beacon transmitter 104. For example, if an error occurs, such as low battery power, the wireless beacon transmitter 104 may output an audible alert, an LED may flash, and/or the vibrating element may provide tactile feedback to the user. The user output 175 may be controlled by output signals from the controller 125.
The controller 125 is further coupled to the wireless antenna unit 140 and the I/O port 145. As described in further detail below, the controller 125 may transmit wireless communications via the wireless antenna unit 140 and may receive wireless communications via the wireless antenna unit 140. The I/O port 145 may include a wired connection for the wireless beacon transmitter 104 to enable, for example, programming of the wireless beacon transmitter 104 or data export from the wireless beacon transmitter 104.
As noted above,
After completing the first number of transmission repetitions, the wireless beacon transmitter 104 withholds further transmission (e.g., of the first beacon signal) during a transition interval (block 304). After the transition interval, the wireless beacon transmitter 104 repeatedly transmits a second advertising beacon signal through a second number of transmission repetitions at a second repeat interval (block 306). In some embodiments, the second advertising beacon signal is a signal for providing identification of a device (e.g., the wireless beacon transmitter 104) transmitting the second advertising beacon signal. In some embodiments, the second advertising beacon signal is a signal using a second proprietary protocol, rather than an open protocol, that is different than the protocol of the first beacon signal.
In some embodiments, the first repeat interval of block 302 is of a length different from a length of the second repeat interval of block 306. In some embodiments, the first repeat interval of block 302 is of a fixed length different from a fixed length of the second repeat interval of block 306. In some embodiments, the first repeat interval of block 302 is of a length that is less than a length of the second repeat interval of block 306, such as less than 1/50th of a length of the second repeat interval of block 306. In some embodiments, the first repeat interval is set at 100 ms for purposes of standards compliance. In some embodiments, the second repeat interval is 7.8 seconds to compromise between transmitter battery life and user experience. In some embodiments, an overall cycle time of 40 seconds results from the selection of the two intervals. In some embodiments, the first repeat interval and the second repeat interval are selected to be the same. One of ordinary skill in the art will readily ascertain, in light of having read the present disclosure that the selection of particular repeat intervals and cycle times will vary between embodiments without departing from the scope and intent of the present disclosure.
In some embodiments, after completing the second number of transmission repetitions in block 306, the process returns to block 302 to perform the repeated transmissions of the first beacon signal through the first number of transmission repetitions spaced at the first repeat interval. In some embodiments, a terminal interval elapses between the completing the second number of transmissions in block 306 and returning to block 302 perform the repeatedly transmitting the first beacon signal through the first number of transmission repetitions spaced at the first repeat interval.
The transmitter location logging application of the personal wireless device 114 listens for a second advertising beacon signal (block 704). For example, to listen, the personal wireless device 114 may execute a software loop that repeatedly checks for a second advertising beacon signal being received by a wireless antenna of the personal wireless device 114. In block 706, the personal wireless device 114 receives the second advertising beacon signal, such as one of a plurality of second beacon signals, from the wireless beacon transmitter 104.
In block 708, a location of the wireless beacon transmitter 104 that transmitted the second advertising beacon signal is logged by the transmitter location logging application of the personal wireless device 114. For example, upon receipt of one of the plurality of second advertising beacon signals including beacon data, the personal wireless device 114 determines the transmitter identifier of the wireless beacon transmitter 104 based on beacon data, and determines the location of the personal wireless device 114 based on an output from a global navigation satellite system (GNSS) receiver of the personal wireless device 114. As one of skill in the art will readily ascertain from having read the present disclosure, while GNSS is described as an example of location detection, embodiments will include other forms of location awareness, such as registration of location (e.g. stored in a memory as part of an initial set-up) or location detection through detection of wireless networks, without departing from the scope and intent of the present disclosure. The personal wireless device 114 logs (e.g., stores in a memory) the determined location with the transmitter identifier of the wireless beacon transmitter 104 such that the location of the personal wireless device 114 is logged as the location of the wireless beacon transmitter 104.
In some embodiments, the additional information may be logged by the personal wireless device 114 for the wireless beacon transmitter 104 in block 708. For example, additional information from the beacon data including one or more of a user identifier, user contact information, timestamp, state of charge of the battery 110, and other status information may be logged for the wireless beacon transmitter 104 in block 708. Furthermore, additional information from the personal wireless device 114 may be logged for the wireless beacon transmitter 104 in block 708, such as a timestamp (e.g., when not provided as part of the beacon data) and receiving device identifier that identifies the personal wireless device 114 or the user thereof. The data that is logged by the personal wireless device 114 in block 708 may be referred to as logged data for the wireless beacon transmitter 104.
In some embodiments, the personal wireless device 114 further sends the logged data, including the transmitter identifier and location of the wireless beacon transmitter 104 to the location server 116 for storage and processing. In some embodiments, the receiving device sends the logged data to the location server 116 each time block 708 is executed. In other embodiments, the receiving device may be configured to delay sending the logged data when the receiving device has already sent similar data recently (e.g., within the past minute, ten minutes, or hour) to limit data transmissions and conserve power. In some embodiments, delaying transmission of the logged data enables the receiving device to obtain further logged data for other beacon transmitters using a similar process and to bundle the logged data for multiple beacon transmitters for a single transmission.
In some embodiments, the method of
In some embodiments, the method of
In some embodiments, in addition to being able to be activated upon receipt of the first beacon signal (e.g., as described with respect to blocks 700 and 702), the transmitter location logging application of the personal wireless device 114 may also be activated in response to receiving a user activation input through a user interface. For example, the user activation input may include a user input indicating a selection of the transmitter location logging application for execution. In response to the user activation input, the receiving device proceeds to block 704-708 as previously described.
The personal wireless device 114 then performs a scan (e.g., a Bluetooth™ scan) for devices transmitting device-specific advertisements (block 712). For example, to scan, the personal wireless device 114 may execute a software loop that repeatedly checks for a device-specific advertising beacon signal being received by a wireless antenna of the personal wireless device 114. In block 714, the personal wireless device 114 discovers the device associated with each received device-specific advertising beacon signal and, in response, saves to a local database the identity of each discovered device, a current longitude and latitude, and a time stamp.
For example, upon receipt of one of the device-specific advertisements, such as a plurality of second advertising beacon signals, including the beacon data, the personal wireless device 114 determines the transmitter identifier of the wireless beacon transmitter 104 based on the beacon data, and determines the location of the personal wireless device 114 based on an output from a global navigation satellite system (GNSS) receiver of the personal wireless device 114. The personal wireless device 114 logs (e.g., stores in a memory) the determined location with the transmitter identifier of the wireless beacon transmitter 104 such that the location of the personal wireless device 114 is logged as the location of the wireless beacon transmitter 104.
In some embodiments, the personal wireless device 114 further sends the logged data, including the transmitter identifier and location of the wireless beacon transmitter 104 to the location server 116 for storage and processing by periodically transmitting the data in the local database to an API for processing (block 716). In some embodiments, the receiving device sends the logged data to the location server 116 each time block 714 is executed. In other embodiments, the receiving device may be configured to delay sending the logged data when the receiving device has already sent similar data recently (e.g., within the past minute, ten minutes, or hour) to limit data transmissions and conserve power. In some embodiments, delaying transmission of the logged data enables the receiving device to obtain further logged data for other beacon transmitters using a similar process and to bundle the logged data for multiple beacon transmitters for a single transmission.
In some embodiments, the method of
In some embodiments, the method of
In some embodiments, in addition to being able to be activated upon receipt of the generic advertisement beacon (e.g., as described with respect to blocks 710), the transmitter location logging application of the personal wireless device 114 may also be activated in response to receiving a user activation input through a user interface. For example, the user activation input may include a user input indicating a selection of the transmitter location logging application for execution. In response to the user activation input, the receiving device proceeds to block 712-716 as previously described.
In some embodiments, the personal wireless device 114 generates and displays a user interface, for example, in response to a user selection of the wireless beacon transmitter 104 on an inventory interface displayed on the personal wireless device 114. The user interface includes an image, which may be of the wireless beacon transmitter 104, the power tool 106 on which the wireless beacon transmitter 104 is mounted. The displayed image may be stored on the personal wireless device 114 or the tracking database 112 and is associated with the wireless beacon transmitter 104 via, for example, the transmitter identifier of the wireless beacon transmitter 104. A map showing a logged location of the wireless beacon transmitter 104 may be displayed. The logged location may be the last known location of the wireless beacon transmitter 104 obtained from a memory of the personal wireless device 114 or the tracking database 112. A timestamp associated with the logged location may also be illustrated on the user interface. The user interface further displays information about the wireless beacon transmitter 104 (e.g., obtained from the tracking database 112 or a memory of the personal wireless device 114).
A missing device control for reporting the wireless beacon transmitter 104 missing is also displayed. The personal wireless device 114 is operable to receive, via the missing device control, user input that indicates that the wireless beacon transmitter 104 (identified by the displayed information) is lost. The personal wireless device 114, in response, communicates lost device information to the tracking database 112 including one or more of a transmitter identifier of the wireless beacon transmitter 104, an indication that the wireless beacon transmitter 104 is lost, a timestamp, a user identifier, user contact information, and personal wireless device identifier. In response to receiving the lost device information, the location server 116 updates the tracking database 112 to indicate that the wireless beacon transmitter 104 is lost (e.g., sets the lost/not-lost indicator to “lost”), and may update the wireless beacon transmitter 104 data in the tracking database 112 with other of the lost device information as well. For example, the user contact information associated with the wireless beacon transmitter 104 on the tracking database 112 may be updated to contact information for the personal wireless device 114 that is reporting the wireless beacon transmitter 104 lost.
As can be appreciated based on the previous description of the system 100 and related methods, after the wireless beacon transmitter 104 is reported lost, a second personal wireless device (similar to the personal wireless device 114) may later receive beacon data for the wireless beacon transmitter 104 (e.g., in accordance with the method of
Embodiments of location logging module and/or of the various location logging methods and techniques as described herein may be executed on one or more computer systems, which may interact with various other devices. In different embodiments, the computer system may be any of various types of devices, including, but not limited to, a personal computer system, desktop computer, laptop, notebook, or netbook computer, mainframe computer system, handheld computer, mobile telephone (e.g., a smart phone), workstation, network computer, a camera, a set top box, a mobile device, a consumer device, video game console, handheld video game device, application server, storage device, a peripheral device such as a switch, modem, router, or another type of computing or electronic device. The computer system is an example of a computer system that may be configured to implement the location server 116 (
The computer system may include one or more processors coupled to a system memory via an input/output (I/O) interface, a network interface coupled to the I/O interface, and one or more input/output devices, such as cursor control device, keyboard, and display(s). In some embodiments, it is contemplated that embodiments may be implemented using a single instance of computer system, while in other embodiments multiple such systems, or multiple nodes making up the computer system, may be configured to host different portions or instances of embodiments. For example, in one embodiment some elements may be implemented via one or more nodes of computer system that are distinct from those nodes implementing other elements.
In some embodiments the power tool 106 includes a power tool battery pack or other power tool power supply, a tool controller, a tool motor, and a tool output component. The power tool power supply may include a circuit for connection to alternating current power, may include power generation components, such as a wind or solar generator, or may be a battery pack that may include one or more battery cells (e.g., lithium-ion cells) within a housing, which includes contacts and an attachment mechanism for selectively securing and removing the power tool battery pack to the power tool. The power tool 106 controller is coupled to and powered by the power tool power supply, and controls the tool motor to drive the tool output component. The tool output component may be, for example, a drill chuck. The tool controller may control the tool motor based on user input received via user input component, which may be, for example, a trigger. The power tool 106 may further include a tool housing that house the tool controller, and the tool motor.
The wireless beacon transmitter 104 may be coupled to the tool controller and the power tool power supply of the power tool 106. For example, the wireless beacon transmitter 104 may be powered by the power tool 106 power supply when present, and by the battery 110 of the wireless beacon transmitter 104 when the power tool 106 power supply is not coupled to the wireless beacon transmitter 104. Additionally, the wireless beacon transmitter 104 may communicate with the power tool 106 controller to, for example, (i) obtain tool usage data stored on a memory of the tool controller (e.g., obtained by sensors of the power tool 106) to send to the personal wireless device 114 and/or (ii) provide tool configuration data (e.g., that is sent to the tool controller for storage on a memory thereof) received from the personal wireless device 114. The wireless beacon transmitter 104, may store within the memory 160 (see
Further, in some embodiments, the wireless beacon transmitter 104 acts as a repeater device that receives other beacon signals (e.g., similar to the beacon signals emitted by the wireless beacon transmitter 104) and repeats (i.e., transmits) those beacon signals using beaconing techniques as described herein.
The various methods as illustrated in the Figures and described herein represent example embodiments of methods. The methods may be implemented in software, hardware, or a combination thereof. The order of method may be changed, and various elements may be added, reordered, combined, omitted, modified, etc.
Various modifications and changes may be made as would be obvious to a person skilled in the art having the benefit of this disclosure. It is intended that the invention embrace all such modifications and changes and, accordingly, the above description to be regarded in an illustrative rather than a restrictive sense.
Thus, the invention provides, among other things, a systems and methods for location logging of transmission devices. Various features and advantages of the invention are set forth in the following claims.
This application claims priority to and claims the benefit of U.S. Provisional Patent Application No. 62/592,181, filed Nov. 29, 2017, which is incorporated by reference herein in its entirety.
Number | Name | Date | Kind |
---|---|---|---|
5809432 | Yamashita | Sep 1998 | A |
6536536 | Gass et al. | Mar 2003 | B1 |
6607041 | Suzuki et al. | Aug 2003 | B2 |
6834730 | Gass et al. | Dec 2004 | B2 |
6872121 | Wiesner et al. | Mar 2005 | B2 |
6913087 | Brotto et al. | Jul 2005 | B1 |
7022924 | Patton | Apr 2006 | B2 |
7036605 | Suzuki et al. | May 2006 | B2 |
7093668 | Gass et al. | Aug 2006 | B2 |
7121358 | Gass et al. | Oct 2006 | B2 |
7146667 | Elsener | Dec 2006 | B2 |
7237990 | Deng | Jul 2007 | B2 |
7253736 | Tethrake et al. | Aug 2007 | B2 |
7256699 | Tethrake et al. | Aug 2007 | B2 |
7298240 | Lamar | Nov 2007 | B2 |
7311025 | Wilson, Jr. | Dec 2007 | B1 |
7328752 | Gass et al. | Feb 2008 | B2 |
7373681 | Elsener | May 2008 | B2 |
7513179 | Wilson, Jr. | Apr 2009 | B2 |
7540334 | Gass et al. | Jun 2009 | B2 |
7608790 | Patton | Oct 2009 | B2 |
RE41160 | Gilmore et al. | Mar 2010 | E |
RE41185 | Gilmore et al. | Mar 2010 | E |
7784104 | Innami et al. | Aug 2010 | B2 |
7827718 | Luebkert et al. | Nov 2010 | B2 |
7837694 | Tethrake et al. | Nov 2010 | B2 |
7850071 | Sakamoto et al. | Dec 2010 | B2 |
7887559 | Deng et al. | Feb 2011 | B2 |
7896098 | Suzuki et al. | Mar 2011 | B2 |
7942084 | Wilson, Jr. et al. | May 2011 | B2 |
7969116 | Aradachi et al. | Jun 2011 | B2 |
8035487 | Malackowski | Oct 2011 | B2 |
8062060 | Rejman | Nov 2011 | B2 |
8066533 | Tomita et al. | Nov 2011 | B2 |
8115621 | Rajala et al. | Feb 2012 | B2 |
8157826 | Deng et al. | Apr 2012 | B2 |
8169298 | Wiesner et al. | May 2012 | B2 |
8189043 | Schneider et al. | May 2012 | B2 |
8200354 | Freeman et al. | Jun 2012 | B2 |
8210275 | Suzuki et al. | Jul 2012 | B2 |
8251157 | Gray et al. | Aug 2012 | B2 |
8253559 | Howard et al. | Aug 2012 | B2 |
8253560 | Howard et al. | Aug 2012 | B2 |
8254878 | Howard et al. | Aug 2012 | B2 |
8264374 | Obutake et al. | Sep 2012 | B2 |
8274273 | Nguyen et al. | Sep 2012 | B2 |
8285248 | Howard et al. | Oct 2012 | B2 |
8406697 | Arimura et al. | Mar 2013 | B2 |
8412179 | Gerold et al. | Apr 2013 | B2 |
8454613 | Tethrake et al. | Jun 2013 | B2 |
8500769 | Deng | Aug 2013 | B2 |
8535342 | Malackowski et al. | Sep 2013 | B2 |
8555755 | Cattaneo | Oct 2013 | B2 |
8588806 | Howard et al. | Nov 2013 | B2 |
8624721 | Barker, Jr. et al. | Jan 2014 | B2 |
8630729 | Freeman et al. | Jan 2014 | B2 |
8659652 | Schneider et al. | Feb 2014 | B2 |
8666936 | Wallace | Mar 2014 | B2 |
8686831 | Fgreen et al. | Apr 2014 | B2 |
8764466 | Million | Jul 2014 | B2 |
8766798 | Howard et al. | Jul 2014 | B2 |
8768381 | Howard et al. | Jul 2014 | B2 |
8776644 | Harper et al. | Jul 2014 | B2 |
8847754 | Buchheim et al. | Sep 2014 | B2 |
8847755 | Howard et al. | Sep 2014 | B2 |
8851200 | Gray et al. | Oct 2014 | B2 |
8870078 | Webb et al. | Oct 2014 | B2 |
8878671 | Buchheim et al. | Nov 2014 | B2 |
8884756 | Howard et al. | Nov 2014 | B2 |
8884871 | Howard et al. | Nov 2014 | B2 |
8890686 | Howard et al. | Nov 2014 | B2 |
8896457 | Howard et al. | Nov 2014 | B2 |
8928463 | Landau et al. | Jan 2015 | B2 |
8938315 | Freeman et al. | Jan 2015 | B2 |
8981952 | Howard et al. | Mar 2015 | B2 |
8988522 | Schneider et al. | Mar 2015 | B2 |
9041528 | Howard et al. | May 2015 | B2 |
9049641 | Wible et al. | Jun 2015 | B2 |
9078481 | Howard et al. | Jul 2015 | B2 |
9082277 | Howard et al. | Jul 2015 | B2 |
9089952 | Gatling et al. | Jul 2015 | B2 |
9129499 | Howard et al. | Sep 2015 | B2 |
9189663 | Goren et al. | Nov 2015 | B2 |
9196881 | Gray et al. | Nov 2015 | B2 |
9232357 | Buchheim et al. | Jan 2016 | B2 |
9256988 | Wenger et al. | Feb 2016 | B2 |
9295024 | Howard et al. | Mar 2016 | B2 |
9367062 | Volpert | Jun 2016 | B2 |
9392404 | Daoura et al. | Jul 2016 | B2 |
9430928 | Ikeda et al. | Aug 2016 | B2 |
9449268 | Goren et al. | Sep 2016 | B2 |
9466198 | Burch et al. | Oct 2016 | B2 |
9467862 | Zeiler et al. | Oct 2016 | B2 |
9491578 | Saucedo | Nov 2016 | B1 |
9495847 | Howard et al. | Nov 2016 | B2 |
9501883 | Handville et al. | Nov 2016 | B2 |
9537335 | Furui et al. | Jan 2017 | B2 |
9547965 | Goren et al. | Jan 2017 | B2 |
9564774 | Daoura et al. | Feb 2017 | B2 |
9576235 | Kim et al. | Feb 2017 | B2 |
9577450 | Yoshikawa et al. | Feb 2017 | B2 |
9595839 | Furui et al. | Mar 2017 | B2 |
9626851 | Xi et al. | Apr 2017 | B2 |
9639722 | Landau et al. | May 2017 | B2 |
9664808 | Nguyen et al. | May 2017 | B2 |
9672708 | Goren et al. | Jun 2017 | B2 |
9693024 | Schneider et al. | Jun 2017 | B2 |
9707026 | Malackowski et al. | Jul 2017 | B2 |
9711017 | Howard et al. | Jul 2017 | B2 |
9713116 | Wible et al. | Jul 2017 | B2 |
9715807 | Howard | Jul 2017 | B2 |
9756402 | Stampfl et al. | Sep 2017 | B2 |
9759402 | Stampfl et al. | Sep 2017 | B2 |
9779601 | Goren et al. | Oct 2017 | B2 |
9780583 | Furui et al. | Oct 2017 | B2 |
9819132 | Peloquin et al. | Nov 2017 | B2 |
9833890 | Ito et al. | Dec 2017 | B2 |
9875629 | Goren et al. | Jan 2018 | B2 |
9888300 | Stampfl et al. | Feb 2018 | B2 |
9892626 | Daoura et al. | Feb 2018 | B2 |
9908182 | Phillips et al. | Mar 2018 | B2 |
9916739 | Suzuki | Mar 2018 | B2 |
9942700 | Howard et al. | Apr 2018 | B2 |
9943746 | Kennard et al. | Apr 2018 | B2 |
9955993 | Deng | May 2018 | B2 |
9967713 | Buchheim et al. | May 2018 | B2 |
9973831 | Mejegard et al. | May 2018 | B2 |
9979149 | Peloquin et al. | May 2018 | B2 |
9986212 | Schneider et al. | May 2018 | B2 |
10022853 | Mollica | Jul 2018 | B1 |
10049549 | Howard | Aug 2018 | B2 |
10051910 | Howard et al. | Aug 2018 | B2 |
10074049 | Daoura et al. | Sep 2018 | B2 |
10090692 | Yoshikawa et al. | Oct 2018 | B2 |
10123161 | Howard et al. | Nov 2018 | B2 |
10124455 | Ito et al. | Nov 2018 | B2 |
10131042 | Mergener et al. | Nov 2018 | B2 |
10131043 | Mergener et al. | Nov 2018 | B2 |
10136198 | Stampfl et al. | Nov 2018 | B2 |
10213908 | Mergener et al. | Feb 2019 | B2 |
10277964 | Stampfl et al. | Apr 2019 | B2 |
10295990 | Dey, IV et al. | May 2019 | B2 |
10322522 | DeCicco et al. | Jun 2019 | B2 |
10354181 | Freienstein et al. | Jul 2019 | B2 |
10368186 | Stampfl et al. | Jul 2019 | B2 |
10380883 | Matson et al. | Aug 2019 | B2 |
10391622 | Tanaka et al. | Aug 2019 | B2 |
10396573 | Furui et al. | Aug 2019 | B2 |
10398032 | Bailey et al. | Aug 2019 | B1 |
10424189 | Daoura et al. | Sep 2019 | B2 |
10431064 | Howard | Oct 2019 | B2 |
10440501 | Howard et al. | Oct 2019 | B2 |
D867909 | Kachar | Nov 2019 | S |
10510199 | Hoossainy et al. | Dec 2019 | B2 |
10516920 | Stampfl et al. | Dec 2019 | B2 |
10518343 | Ogino et al. | Dec 2019 | B2 |
10569398 | Mergener et al. | Feb 2020 | B2 |
20020110431 | Dils et al. | Aug 2002 | A1 |
20030090239 | Sakakibara | May 2003 | A1 |
20030093103 | Malackowski et al. | May 2003 | A1 |
20040108120 | Wiesner et al. | Jun 2004 | A1 |
20040135692 | Below et al. | Jul 2004 | A1 |
20040198382 | Hammond | Oct 2004 | A1 |
20050075149 | Gerber et al. | Apr 2005 | A1 |
20050173142 | Cutler et al. | Aug 2005 | A1 |
20050197093 | Wiklof et al. | Sep 2005 | A1 |
20050267988 | Ferguson et al. | Dec 2005 | A1 |
20060179473 | Innami et al. | Aug 2006 | A1 |
20080125040 | Kalayjian | May 2008 | A1 |
20080135272 | Wallgren | Jun 2008 | A1 |
20080177267 | Sands et al. | Jul 2008 | A1 |
20080196910 | Radle et al. | Aug 2008 | A1 |
20080238609 | Wiesner et al. | Oct 2008 | A1 |
20080252446 | Dammertz | Oct 2008 | A1 |
20090145187 | Deppner et al. | Jun 2009 | A1 |
20090251330 | Gerold et al. | Oct 2009 | A1 |
20100096151 | Ostling | Apr 2010 | A1 |
20100186976 | Tsubakimoto et al. | Jul 2010 | A1 |
20100265097 | Obatake et al. | Oct 2010 | A1 |
20100295665 | Landau | Nov 2010 | A1 |
20110003504 | Rejman | Jan 2011 | A1 |
20110073343 | Sawano et al. | Mar 2011 | A1 |
20110253402 | Aradachi et al. | Oct 2011 | A1 |
20120169485 | Eckert | Jul 2012 | A1 |
20120292070 | Ito et al. | Nov 2012 | A1 |
20120304367 | Howard et al. | Dec 2012 | A1 |
20130109375 | Zeiler et al. | May 2013 | A1 |
20130256349 | Styth et al. | Oct 2013 | A1 |
20130267247 | Wible et al. | Oct 2013 | A1 |
20130295426 | Halavart et al. | Nov 2013 | A1 |
20130296910 | Deng | Nov 2013 | A1 |
20130313925 | Mergener et al. | Nov 2013 | A1 |
20130344885 | Parisi et al. | Dec 2013 | A1 |
20140031831 | Malackowski et al. | Jan 2014 | A1 |
20140070924 | Wenger et al. | Mar 2014 | A1 |
20140132411 | Buchheim et al. | May 2014 | A1 |
20140151079 | Furui et al. | Jun 2014 | A1 |
20140158389 | Ito et al. | Jun 2014 | A1 |
20140159662 | Furui et al. | Jun 2014 | A1 |
20140180464 | Koerber | Jun 2014 | A1 |
20140184397 | Volpert | Jul 2014 | A1 |
20140240125 | Burch et al. | Aug 2014 | A1 |
20140326477 | Thorson et al. | Nov 2014 | A1 |
20140367134 | Phillips et al. | Dec 2014 | A1 |
20150054627 | Landau et al. | Feb 2015 | A1 |
20150133170 | Buchheim et al. | May 2015 | A1 |
20150195807 | Wible et al. | Jul 2015 | A1 |
20150197093 | Berry et al. | Jul 2015 | A1 |
20150219257 | Harper et al. | Aug 2015 | A1 |
20150286209 | Kreuzer et al. | Oct 2015 | A1 |
20150316913 | Rickey et al. | Nov 2015 | A1 |
20150340921 | Suda et al. | Nov 2015 | A1 |
20150356861 | Daoura et al. | Dec 2015 | A1 |
20160019512 | Buchheim et al. | Jan 2016 | A1 |
20160048122 | Lukosz et al. | Feb 2016 | A1 |
20160171788 | Wenger et al. | Jun 2016 | A1 |
20160226132 | Kim et al. | Aug 2016 | A1 |
20160311094 | Mergener et al. | Oct 2016 | A1 |
20160325391 | Stampfl et al. | Nov 2016 | A1 |
20160342151 | Dey, IV et al. | Nov 2016 | A1 |
20170008159 | Boeck et al. | Jan 2017 | A1 |
20170201295 | Kusakawa | Jul 2017 | A1 |
20170201853 | Chen et al. | Jul 2017 | A1 |
20170216986 | Dey, IV et al. | Aug 2017 | A1 |
20170259422 | Takeyama et al. | Sep 2017 | A1 |
20170303984 | Malackowski | Oct 2017 | A1 |
20170343966 | Schadow et al. | Nov 2017 | A1 |
20180071907 | Myhill | Mar 2018 | A1 |
20180076639 | Furui et al. | Mar 2018 | A1 |
20180104802 | Mergener et al. | Apr 2018 | A1 |
20180114423 | Goren et al. | Apr 2018 | A1 |
20180126537 | Tanaka et al. | May 2018 | A1 |
20180133873 | Mergener et al. | May 2018 | A1 |
20180154456 | Phillips et al. | Jun 2018 | A1 |
20180199955 | Deng | Jul 2018 | A1 |
20180302753 | Langton | Oct 2018 | A1 |
20180319003 | Freienstein et al. | Nov 2018 | A1 |
20180322376 | Henry et al. | Nov 2018 | A1 |
20180345474 | Brennenstuhl et al. | Dec 2018 | A1 |
20180354118 | Brennenstuhl et al. | Dec 2018 | A1 |
20180357523 | Freienstein et al. | Dec 2018 | A1 |
20190026619 | Cecchin et al. | Jan 2019 | A1 |
20190027002 | Esenwein et al. | Jan 2019 | A1 |
20190043292 | Hoossainy et al. | Feb 2019 | A1 |
20190103012 | Daoura et al. | Apr 2019 | A1 |
20190160646 | Hoossainy et al. | May 2019 | A1 |
20190215584 | Stampfl et al. | Jul 2019 | A1 |
20190219990 | Dey, IV et al. | Jul 2019 | A1 |
20190298122 | Tahara et al. | Oct 2019 | A1 |
20190299386 | Tanaka et al. | Oct 2019 | A1 |
20190334357 | Furui et al. | Oct 2019 | A1 |
20200094393 | Schadow et al. | Mar 2020 | A1 |
Number | Date | Country |
---|---|---|
203956880 | Nov 2014 | CN |
107877457 | Apr 2018 | CN |
8102453 | Sep 1982 | DE |
10238710 | Mar 2003 | DE |
202004020457 | Jun 2005 | DE |
202005010622 | Nov 2006 | DE |
102005053821 | May 2007 | DE |
102005053821 | Jul 2007 | DE |
102006046801 | Apr 2008 | DE |
202008012687 | Dec 2008 | DE |
102010041278 | Mar 2012 | DE |
102011050393 | Nov 2012 | DE |
102011089499 | Jun 2013 | DE |
102012105483 | Dec 2013 | DE |
202014006084 | Aug 2014 | DE |
102015226734 | Jun 2017 | DE |
102016211937 | Jan 2018 | DE |
1270150 | Jan 2003 | EP |
1291999 | Mar 2003 | EP |
1690648 | Aug 2006 | EP |
1781074 | May 2007 | EP |
2072192 | Jun 2009 | EP |
2581168 | Apr 2013 | EP |
2628427 | Aug 2013 | EP |
3200313 | Jun 2017 | EP |
3272467 | Jan 2018 | EP |
2010194662 | Sep 2010 | JP |
1020180108895 | Oct 2018 | KR |
WO 2007058596 | May 2007 | WO |
WO 2012035815 | Mar 2012 | WO |
WO 2012035854 | Mar 2012 | WO |
WO 2013014914 | Jan 2013 | WO |
2013112469 | Aug 2013 | WO |
WO 2013116303 | Aug 2013 | WO |
WO 2013136917 | Sep 2013 | WO |
WO 2015061370 | Apr 2015 | WO |
WO 2016206859 | Dec 2016 | WO |
WO 2016206860 | Dec 2016 | WO |
WO 2017089100 | Jun 2017 | WO |
WO 2017089452 | Jun 2017 | WO |
WO 2017093160 | Jun 2017 | WO |
2017151954 | Sep 2017 | WO |
2018024637 | Feb 2018 | WO |
2018162233 | Sep 2018 | WO |
WO 2018177669 | Oct 2018 | WO |
WO 2018177671 | Oct 2018 | WO |
2019115434 | Jun 2019 | WO |
Entry |
---|
United States Patent Office Notice of Allowance for U.S. Appl. No. 16/056,710 dated Aug. 16, 2019 (8 pages). |
International Search Report and Written Opinion for Application No. PCT/US2020/016752 dated Jun. 5, 2020 (13 pages). |
International Preliminary Report on Patentability for Application No. PCT/US2018/045500 dated Feb. 11, 2020 (13 pages). |
United States Patent Office Non Final Office Action for U.S. Appl. No. 16/684,455 dated Mar. 23, 2020 (9 pages). |
International Search Report and Written Opinion for Application No. PCT/US2018/062803 dated Mar. 19, 2019, 12 pages. |
International Search Report and Written Opinion for Application No. PCT/US2018/045500 dated Dec. 6, 2018, 15 pages. |
Pixie 2.0 User Guide, 6 pages, accessed Jan. 31, 2019. |
Pixie, <https://getpixie.com> webpage accessed Jan. 31, 2019. |
Number | Date | Country | |
---|---|---|---|
20190160646 A1 | May 2019 | US |
Number | Date | Country | |
---|---|---|---|
62592181 | Nov 2017 | US |