The present invention relates to power tools with a compartment for receiving another device.
In one embodiment, the invention provides a power tool including a housing, a motor, an output device driven by the motor, a controller, and a compartment defined by the housing. The compartment includes an irreversible lock and is configured to receive a wireless communication device and, with the irreversible lock, to irreversibly lock the wireless communication device within the compartment. The power tool also includes a data connection between the controller and the compartment such that when the wireless communication device is positioned inside the compartment, the controller exchanges power tool data with the wireless communication device. The wireless communication device also including a transceiver configured to communicate with an external device, and to exchange the power tool information with the external device.
Another embodiment provides a power tool including a housing including a compartment with an irreversible lock. The power tool further includes a wireless communication device including a wireless communication controller with a transceiver. The wireless communication device is configured to be received in the compartment and to engage with the irreversible lock. The power tool further includes a motor within the housing and having a rotor and a stator. The motor is configured to drive an output drive device. The power tool further includes a controller within the housing and having an electronic processor, a memory, and a data connection. The data connection is configured to couple the electronic processor to the wireless communication device when the wireless communication device is inserted into the compartment. The controller is configured to control operation of the motor, and communicate with an external device via the data connection and the wireless communication controller.
Another embodiment provides a method of deterring removal of a wireless communication device inserted into a compartment of a housing of a power tool. The method includes receiving, by the compartment of the housing, the wireless communication device. The compartment includes an irreversible lock configured to engage with the wireless communication device. The wireless communication device includes a wireless communication controller with a transceiver. The method further includes controlling, with a controller located within the housing, operation of a motor of the power tool to drive an output drive device. The controller includes an electronic processor, a memory, and a data connection. The data connection is configured to couple the electronic processor to the wireless communication device when the wireless communication device is inserted into the compartment. The method further includes communicating, by the controller, with an external device via the data connection and the wireless communication controller.
For example, the controller may transmit data to the wireless communication controller by way of the data connection, and the wireless communication controller wirelessly transmits the data via the transceiver to the external device. Further, the wireless communication controller may wirelessly receive data from the external device via the transceiver, and provide the data to the controller by way of the data connection.
Yet another embodiment provides a power tool device including a housing including a compartment with an irreversible lock and including a power tool battery pack interface configured to receive a power tool battery pack. The power tool device further includes a wireless communication device including a wireless communication controller with a transceiver. The wireless communication device is configured to be received in the compartment and to engage with the irreversible lock. The power tool device further includes a powered element configured to be selectively coupled to power provided by the power tool battery pack. The power tool device further includes a controller within the housing and having an electronic processor, a memory, and a data connection. The data connection is configured to couple the electronic processor to the wireless communication device when the wireless communication device is inserted into the compartment. The controller is configured to control the powered element, and communicate with an external device via the data connection and the wireless communication controller.
One embodiment provides a power tool including a housing including a compartment. The compartment is configured to receive a wireless communication device that includes a wireless communication controller including a transceiver. The power tool further includes a motor within the housing and having a rotor and a stator. The motor is configured to drive an output drive device. The power tool further includes a controller within the housing and having an electronic processor, a memory, and a data connection. The data connection is configured to couple the electronic processor to the wireless communication device when the wireless communication device is inserted into the compartment. The controller is configured to: communicate with the wireless communication device to implement an electronic lock mechanism to inhibit at least one selected from the group of operation of the motor of the power tool and communication between the controller and the wireless communication controller.
Another embodiment provides a method of deterring removal of a wireless communication device inserted into a compartment of a housing of a power tool. The method includes receiving, by the compartment of the housing, the wireless communication device. The power tool includes a motor within the housing and having a rotor and a stator. The motor is configured to drive an output drive device. The method further includes controlling, with a controller located within the housing, operation of the motor. The controller includes a data connection configured to couple to the wireless communication device when the wireless communication device is inserted into the compartment. The method further includes enabling the controller to communicate with an external device via the data connection and a wireless communication controller included in the wireless communication device. The method further includes implementing, via communication between the controller and the wireless communication controller, an electronic lock mechanism to inhibit at least one selected from the group of operation of the motor of the power tool and communication between the controller and the wireless communication controller.
Other aspects of the invention will become apparent by consideration of the detailed description and accompanying drawings.
Before any embodiments of the invention are explained in detail, it is to be understood that the invention 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 invention is capable of other embodiments and of being practiced or of being carried out in various ways. Also, it is to be understood that the phraseology and terminology used herein is for the purpose of description and should not be regarded as limited. The use of “including,” “comprising” or “having” and variations thereof herein is meant to encompass the items listed thereafter and equivalents thereof as well as additional items. The terms “mounted,” “connected” and “coupled” are used broadly and encompass both direct and indirect mounting, connecting and coupling. Further, “connected” and “coupled” are not restricted to physical or mechanical connections or couplings, and can include electrical connections or couplings, whether direct or indirect.
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 invention. Furthermore, and as described in subsequent paragraphs, the specific configurations illustrated in the drawings are intended to exemplify embodiments of the invention and that other alternative configurations are possible. The terms “processor” “central processing unit” and “CPU” are interchangeable unless otherwise stated. Where the terms “processor” or “central processing unit” or “CPU” are used as identifying a unit performing specific functions, it should be understood that, unless otherwise stated, those functions can be carried out by a single processor, or multiple processors arranged in any form, including parallel processors, serial processors, tandem processors or cloud processing/cloud computing configurations.
When the power tool devices 104a, 104b, 104c include the wireless communication device in the compartment, the power tool devices 104a, 140b, 104c can operate similar to the power tool device 104d as if the wireless communication device was integrally formed within the power tool 104. The power tool 104 may communicate power tool status, power tool operation statistics, power tool identification, stored power tool usage information, power tool maintenance data, and the like. Therefore, using the external device 108, a user can access stored power tool usage or power tool maintenance data. With this tool data, a user can determine how the power tool 104 has been used, whether maintenance is recommended or has been performed in the past, and identify malfunctioning components or other reasons for certain performance issues. The external device 108 can also transmit data to the power tool 104 for power tool configuration, firmware updates, or to send commands (e.g., turn on a work light, lock the power tool 104, and the like). The external device 108 also allows a user to set operational parameters, safety parameters, select tool modes, and the like for the power tool 104. The external device 108 may also communicate with a remote server 112 and may receive configuration and/or settings for the power tool 104, or may transmit operational data or other power tool status information to the remote server 112.
The external device 108 may be, for example, a laptop computer, a tablet computer, a smartphone, a cellphone, or another electronic device capable of communicating wirelessly with the power tool 104 and providing a user interface. The external device 108 provides the user interface and allows a user to access and interact with tool information. The external device 108 can receive user inputs to determine operational parameters, enable or disable features, and the like. The user interface of the external device 108 provides an easy-to-use interface for the user to control and customize operation of the power tool 104.
As shown in
The memory 130 of the external device 108 also stores core application software 134. The external device processor 114 accesses and executes the core application software 134 in memory 130 to launch a control application that receives inputs from the user for the configuration and operation of the power tool 104. The short-range transceiver 118 of the external device 108 is compatible with a transceiver of the power tool 104 (described in further detail below). The short-range transceiver may include, for example, a Bluetooth® communication controller. The short-range transceiver allows the external device 108 to communicate with the power tool 104.
The remote server 112 may store data obtained by the external device 108 from, for example, the power tool 104. The remote server 112 may also provide additional functionality and services to the user. In one embodiment, storing the information on the remote server 112 allows a user to access the information from a plurality of different devices and locations (e.g., a remotely located desktop computer). In another embodiment, the remote server 112 may collect information from various users regarding their power tool devices and provide statistics or statistical measures to the user based on information obtained from the different power tools. For example, the remote server 112 may provide statistics regarding the experienced efficiency of the power tool 104, typical usage of the power tool 104, and other relevant characteristics and/or measures of the power tool 104. In some embodiments, the power tool 104 may be configured to communicate directly with the server 112 through an additional wireless interface or with the same wireless interface that the power tool 104 uses to communicate with the external device 108.
The power tool 104 is configured to perform one or more specific tasks (e.g., drilling, cutting, fastening, pressing, lubricant application, sanding, heating, grinding, bending, forming, impacting, polishing, lighting, etc.). For example, an impact wrench is associated with the task of generating a rotational output (e.g., to drive a bit), while a reciprocating saw is associated with the task of generating a reciprocating output motion (e.g., for pushing and pulling a saw blade). The task(s) associated with a particular tool may also be referred to as the primary function(s) of the tool.
Although the power tool 104 illustrated and described herein is an impact wrench, embodiments of the invention similarly apply to and can be used in conjunction with a variety of power tools (e.g., a power drill, a hammer drill, a pipe cutter, a sander, a nailer, a grease gun, etc.). As shown in
In the illustrated embodiment, the battery pack receiving portion 206 also includes a compartment 277, also referred to as an irreversibly locking compartment 277. The compartment 277 is positioned adjacent the connecting structure that receives the battery pack and is a separate compartment of the tool housing. In particular, the compartment 277 is positioned under the selection switch 208 in a recess spanning a dividing line of the power tool's clam shell housing. The foot of the power tool 104 (i.e., the battery pack receiving portion 206) defines a footprint perimeter of the power tool 104. The perimeter is defined by the edges A, B, C, D of the battery pack receiving portion 206. As shown in
The compartment 277 includes an irreversible lock 279 (
The lock mating tooth 325 engages with the lock 279, as shown in
In the illustrated embodiment, the lock 279 includes a single mating tab 330 that engages with the mating tooth 325 of the wireless communication device 300. In other embodiments, however, the lock 279 may include multiple mating tabs to more securely retain the wireless communication device 300. For example, the lock 279 may include two mating tabs, one at each side, such that when the wireless communication device 300 is inserted, two mating teeth can engage with the lock 279. In some embodiments, the irreversible lock includes a lock mating tooth that engages with a mating tab of the wireless communication device 300. In such embodiments, the wireless communication device 300 is inserted into the compartment until the mating tab passes the mating tooth of the lock. When the mating tab has passed the mating tooth of the lock, the wireless communication device 300 becomes permanently secured to the power tool 104. In other embodiments, a different type of irreversible locking mechanism is used. For example, the wireless communication device 300 may be rotated to engage the irreversible lock 279.
The position of the compartment 277, even when the wireless communication device 300 is inserted, also does not interfere with any of the foot accessories of the power tool 104. For example, on the same side of the foot that houses the compartment 277, a belt hook mount 336 is provided having three recesses 338a, 338b, and 338c (
In one embodiment, the compartment 277 includes a plastic cover 342, as shown in
As shown in
The switching network 216 enables the controller 226 to control the operation of the motor 214. Generally, when the trigger 212 is depressed (i.e., the trigger switch 213 is closed), electrical current is supplied from the battery pack interface 222 to the motor 214, via the switching network 216. When the trigger 212 is not depressed, electrical current is not supplied from the battery pack interface 222 to the motor 214. In some embodiments, the trigger switch 213 may include sensors to detect the amount of trigger pull (e.g., released, 20% pull, 50% pull, 75% pull, or fully depressed). In some embodiments, the amount of trigger pull detected by the trigger switch 213 is related to or corresponds to a desired speed of rotation of the motor 214. In other embodiments, the amount of trigger pull detected by the trigger switch 213 is related to or corresponds to a desired torque, or other parameter. In response to the controller 226 receiving the activation signal from the trigger switch 213, the controller 226 activates the switching network 216 to provide power to the motor 214. The switching network 216 controls the amount of current available to the motor 214 and thereby controls the speed and torque output of the motor 214. The switching network 216 may include numerous field effect transistors (FETs), bipolar transistors, or other types of electrical switches.
The sensors 218 are coupled to the controller 226 and communicate to the controller 226 various signals indicative of different parameters of the power tool 104 or the motor 214. The sensors 218 include, for example, one or more current sensors, one or more voltage sensors, one or more temperature sensors, one or more speed sensors, one or more Hall Effect sensors, etc. For example, the speed of the motor 214 can be determined using a plurality of Hall Effect sensors to sense the rotational position of the motor 214. In some embodiments, the controller 226 controls the switching network 216 in response to signals received from the sensors 218. For example, if the controller 226 determines that the speed of the motor 214 is increasing too rapidly based on information received from the sensors 218, the controller 226 may adapt or modify the active switches or switching sequence within the switching network 216 to reduce the speed of the motor 214. Data obtained via the sensors 218 may be saved in the controller 226 as tool usage data.
The indicators 220 are also coupled to the controller 226 and receive control signals from the controller 226 to turn on and off or otherwise convey information based on different states of the power tool 104. The indicators 220 include, for example, one or more light-emitting diodes (“LED”), or a display screen. The indicators 220 can be configured to display conditions of, or information associated with, the power tool 104. For example, the indicators 220 are configured to indicate measured electrical characteristics of the power tool 104, the status of the power tool 104, etc. The indicators 220 may also include elements to convey information to a user through audible or tactile outputs.
As described above, the controller 226 is electrically and/or communicatively connected to a variety of modules or components of the power tool 104. In some embodiments, the controller 226 includes a plurality of electrical and electronic components that provide power, operational control, and protection to the components and modules within the controller 226 and/or power tool 104. For example, the controller 226 includes, among other things, a processing unit 230 (e.g., a microprocessor, a microcontroller, or another suitable programmable device), a memory 232, input units 234, and output units 236. The processing unit 230 includes, among other things, a control unit 240, an arithmetic logic unit (“ALU”) 242, and a plurality of registers 244 (shown as a group of registers in
The memory 232 includes, for example, a program storage area 233a and a data storage area 233b. The program storage area 233a and the data storage area 233b can include combinations of different types of memory, such as read-only memory (“ROM”), random access memory (“RAM”) (e.g., dynamic RAM [“DRAM”], synchronous DRAM [“SDRAM”], etc.), electrically erasable programmable read-only memory (“EEPROM”), flash memory, a hard disk, an SD card, or other suitable magnetic, optical, physical, or electronic memory devices. The processing unit 230 is connected to the memory 232 and executes software instructions that are capable of being stored in a RAM of the memory 232 (e.g., during execution), a ROM of the memory 232 (e.g., on a generally permanent basis), or another non-transitory computer readable medium such as another memory or a disc. Software included in the implementation of the power tool 104 can be stored in the memory 232 of the controller 226. The software includes, for example, firmware, one or more applications, program data, filters, rules, one or more program modules, and other executable instructions. The controller 226 is configured to retrieve from memory and execute, among other things, instructions related to the control processes and methods described herein. The controller 226 is also configured to store power tool information on the memory 232. The power tool information stored on the memory 232 may include power tool identification information (e.g., including a unique identifier of the power tool 104) and also power tool operational information including information regarding the usage of the power tool 104, information regarding the maintenance of the power tool 104, power tool trigger event information, parameter information to operate the power tool 104 in a particular mode, and other information relevant to operating or maintaining the power tool 104, such information is generally referred to as power tool information. In other constructions, the controller 226 includes additional, fewer, or different components.
The controller 226 also includes a data connection (e.g., a communication channel) 262 to optionally couple to the insertable wireless communication device 300. In some embodiments, the data connection 262 includes a ribbon cable that is connected from the controller 226 to a set of leads in the compartment 277. When the wireless communication device 300 is inserted into the compartment 277, a set of leads on the wireless communication device 300 connect with the leads inside the compartment 277 and communication between the controller 226 and the wireless communication device 300 is thereby enabled (for example, see
The wireless communication controller 250 includes an antenna and radio transceiver 254, a memory 256, a processor 258, and the real-time clock (RTC) 260. The antenna and radio transceiver 254 operate together to send and receive wireless messages to and from an external device 108 and the processor 258. The memory 256 can store instructions to be implemented by the processor 258 and/or may store data related to communications between the power tool 104 and the external communication device 108 or the like. The processor 258 for the wireless communication controller 250 controls wireless communications between the power tool 104 and the external device 108. For example, the processor 258 associated with the wireless communication controller 250 buffers incoming and/or outgoing data, communicates with the controller 226, and determines the communication protocol and/or settings to use in wireless communications. In other words, the wireless communication controller 250 is configured to receive data from the power tool controller 226 and relay the information to the external device 108 via the antenna and transceiver 254. In a similar manner, the wireless communication controller 250 is configured to receive information (e.g., configuration and programming information) from the external device 108 via the antenna and transceiver 254 and relay the information to the power tool controller 226.
In the illustrated embodiment, the wireless communication controller 250 is a Bluetooth® controller. The Bluetooth® controller communicates with the external device 108 employing the Bluetooth® protocol. Therefore, in the illustrated embodiment, the external device 108 and the power tool 104 are within a communication range (i.e., in proximity) of each other while they exchange data. In other embodiments, the wireless communication controller 250 communicates using other protocols (e.g., Wi-Fi, cellular protocols, etc.) over a different type of wireless network. For example, the wireless communication controller 250 may be configured to communicate via Wi-Fi through a wide area network such as the Internet or a local area network, or to communicate through a piconet (e.g., using infrared or NFC communications). The communication via the wireless communication controller 250 may be encrypted to protect the data exchanged between the power tool 104 and the external device 108 (or network) from third parties.
When the wireless communication device 300 is first inserted into the compartment 277, the controller 226 initializes the wireless communication device 300. In one example, one of the leads in the compartment 277 includes a sensing lead coupled to the controller 226. When the signal on the sensing lead changes (e.g., from a high signal to a low signal), the controller 226 detects the insertion of the wireless communication device 300. The controller 226 then transmits identification information for the power tool 104 and for the controller 226 to the wireless communication device 300. The wireless communication device 300, and in particular, the wireless communication controller 250 stores the identification information of the power tool 104 and the controller 226. In the illustrated embodiment, the wireless communication controller 250 is configured to periodically broadcast the identification signal for the power tool 104, also referred to as identification information or identification data. The identification signal includes identification information for the power tool 104, such as a unique identifier. The external device 108 identifies the power tool 104 via the identification signal. Additionally or alternatively, the wireless communication controller 250 may be configured to respond to a ping signal from the external device 108. In other words, the wireless communication controller 250 may not periodically broadcast the identification signal, but rather the wireless communication controller 250 may wait for a ping signal from the external device 108 to send the identification signal. In some embodiments, the external device 108 generates a graphical user interface that identifies the wireless communication device 300 and allows the user to associate the wireless communication device 300 with the power tool 104. In some embodiments, such an association prompts the communication between the wireless communication device 300 and the controller 226.
The identification signal for the power tool 104 can then be used, via the wireless communication controller 250, to track the power tool 104. For example, the wireless communication controller 250 switches between operating in a connectable (e.g., full power) state and operating in an advertisement state. The wireless communication controller 250 operates in the connectable state when the battery pack 104b is attached to the power tool 104 and contains sufficient charge to power the wireless communication controller 250 and the controller 226, and to support substantive electronic data communication between the power tool 104 and the external device 108. When the power tool 104 is not connected to the battery pack 104b, the wireless communication controller 250 is powered by the backup power source 252 and operates in the advertisement state. While in the advertisement state, the wireless communication controller 250 receives power from the backup power source 252 (e.g., a coin cell battery, another type of battery cell, a capacitor, or another energy storage device). The backup power source 252 provides sufficient power for the wireless communication controller 250 to periodically broadcast an advertisement message, but may not provide sufficient power to allow the wireless communication controller 250 to engage in further data exchange with the external device 108, or, such further data exchange would deplete the backup power source 252 more rapidly than desired. In both the connectable state and the advertisement state, the wireless communication controller 250 periodically outputs the identification code corresponding to the power tool 104. In other words, the wireless communication controller periodically advertises the identity of the power tool 104. The external devices 108 that are within the communication range of the wireless communication controller 250 can receive the identification code from the wireless communication controller 250. The identification codes may include, for example, a global unique identification (GUID) that includes the power tool's specific make, model, and serial number.
The RTC 260 increments and keeps time independently of the other power tool components. In the illustrated embodiment, the RTC 260 is powered through the wireless communication controller 250 when the wireless communication controller 250 is powered. In some embodiments, however, the RTC 260 is a separate component from the wireless communication controller 250 and may be integrated into the power tool 104. In such embodiments, the RTC 260 receives power from the battery pack 104b (e.g., a main or primary power source) when the battery pack 215 is connected to the power tool 104. The RTC 260 receives power from the backup power source 252 (e.g., a coin cell battery, another type of battery cell, a capacitor, or another energy storage device) when the battery pack 104b is not connected to the power tool 104. Therefore, the RTC 260 keeps track of time regardless of whether the power tool 104 is in operation, and regardless of whether the battery pack 104b is connected to the power tool 104. When no power source is present (i.e., the battery pack 104b is detached from the power tool 104 and the backup power source 252 is removed or depleted), the RTC 260 stores the last valid time. When a power source is replaced (i.e., the battery pack 104b is attached to the power tool 104 and/or the backup power source 252 is replaced), the RTC 260 uses the stored time as a starting point to resume keeping time.
The starting time for the RTC 260 is set to current Greenwich Mean Time (GMT) time at the factory at time of manufacture. The time is updated or synchronized whenever the wireless communication controller 250 communicates with the external device 108. Because GMT time is independent of calendar, seasons, or time schemas, using GMT time allows the power tool 104 or the external device 108 to convert from time indicated by the RTC 260 to localized time for display to the user.
The backup power source 252 also provides power to the RTC 260 to enable continuous tracking of time. The backup power source 252 does not provide power to energize the motor 214, drive the drive device 210, or power the controller 226, and generally only powers the wireless communication controller 250, the indicator light 320, and the RTC 260 (e.g., in embodiments in which the RTC 260 is separate from the wireless communication controller 250) when the battery pack 104b is not attached to the power tool 104. In other embodiments, the backup power source 252 also provides power to low-power elements such as, for example, LEDs, and the like. In some embodiments, the wireless communication controller 250 includes a voltage sensor 265 (see
In the illustrated embodiment, the backup power source 252 includes a coin cell battery 315 located on the PCB 305. The coin cell battery 315 is merely exemplary. In some embodiments, the backup power source 252 may be another type of battery cell, a capacitor, or another energy storage device. The coin cell battery 315 provides sufficient power to allow the wireless communication controller 250 to operate in the advertisement state and broadcast minimal identification information. In the illustrated embodiment, the coin cell battery 315 can run for several years by allowing the power tool 104 to only “broadcast” or “advertise” once every few seconds when operating the advertisement state.
In the illustrated embodiment, the coin cell battery 315 is a primary (i.e., non-rechargeable) backup battery. In other embodiments, the backup power source 252 includes a secondary (rechargeable) backup battery cell or a capacitor. In such embodiments, the battery pack 104b provides charging power to recharge the secondary backup battery cell or the capacitor. For example, the power input unit 224 may include charging circuitry to charge the backup power source 252. The rechargeable cell and capacitor may be sized to provide power for several days or weeks before needing to recharge.
The indicator light 320 of the wireless communication device 300 is configured to indicate the state of the wireless communication device 300. For example, the indicator light 320 may, in a first indication state, light in a first color (or blink in a first predetermined pattern) to indicate that the wireless communication device 300 is currently communicating with an external device 108. The indicator light 320 may, in a second indication state, light in a second color (or blink in a second predetermined pattern) to indicate that the power tool 104 is locked (e.g., the motor 214 is inoperable because a security feature has been enabled) as described in more detail below in
The wireless communication controller 250 and the RTC 260 enable the power tool 104 to implement a lock-out feature. For example,
In other embodiments, the power tool 104 is locked or unlocked based on other security conditions different than a lock out time or timer amount. In such embodiments, the wireless communication controller 250 receives the security settings (e.g., whether the power tool 104 is locked or unlocked and the specific security parameters for when the power tool 104 is to change security states). The wireless communication controller 250 transmits the security parameters to the controller 226. The controller 226 may then monitor the security parameters and determine when the security parameters or security conditions are met. The controller 226 may then change the security state of the power tool 104 based on the security parameters (e.g., unlock the power tool 104 when a security condition is met).
Because the RTC 260 is able to maintain accurate time whether or not the battery pack 104b is attached to the power tool 104, the RTC 260 is configured to time-stamp (i.e., associate a specific time with) the operational data of the power tool 104. For example, the controller 226 can store the operational data when, for example, the power tool 104 is fastening a group of fasteners. The controller 226 then receives an indication of time (e.g., a GMT time) from the RTC 260 or from the processor 258 associated with the wireless communication controller 250. The controller 226 proceeds to store the operational data (e.g., the torque output by the power tool 104, the speed of the motor 214, the number of trigger pulls, etc.) with a time-stamp provided based on the received time from the RTC 260. The RTC 260 can continuously or periodically provide an indication of time to the controller 226. In other embodiments, the controller 226 requests a time signal from the processor 258 of the wireless communication controller 250 and waits for the time signal from the RTC 260.
When the wireless communication controller 250 operates in the connectable state, wireless communication between the power tool 104 and the external device 108 is enabled. In the connectable state, the wireless communication controller 250 obtains and exports tool operational data including tool usage data, maintenance data, mode information, drive device information, and the like from the power tool 104. The exported operational data is received by the external device 108 and can be used by tool users or owners to log operational data related to a particular power tool 104 or to specific job activities. The exported and logged operational data can indicate when work was accomplished and that work was accomplished to specification. The logged operational data can also provide a chronological record of work that was performed, track duration of tool usage, and the like. In the connectable state, the wireless communication controller 250 also imports (i.e., receives) configuration data from the external device 108 into the power tool 104 such as, for example, operation thresholds, maintenance thresholds, mode configurations, programming for the power tool 104, feature information, and the like. The configuration data is provided by the wireless communication controller 250 to the controller 226 over the data connection 262, and the processing unit 230 stores the configuration data in the memory 232. The processing unit 230 further accesses the configuration data stored in the memory 232 and controls driving of the motor 214 in accordance with the configuration data. For example, the processing unit 230 may drive the motor 214 at a particular speed or until a particular torque is reached (e.g., as detected by the sensors 218), where the particular speed or torque is provided as part of the configuration data.
The wireless communication device 300 has been described as including both the wireless communication controller 250 and the backup power source 252. In some embodiments, however, the wireless communication controller 250 is separate from the backup power source 252.
On the other hand, the second compartment 615 is similar to the compartment 277 described above. As shown in
While in the illustrated embodiment, the first compartment 610 and the second compartment 615 are both positioned in a battery pack receiving portion 625 of the power tool 600, in other embodiments, one or both of the first compartment 610 and the second compartment 615 may be located elsewhere on the power tool 600. For example,
Because the top portion 660 of the housing 655 replicates the mating structure of a battery pack and the lower portion 665 of the housing 655 replicates the mating structure of the battery receiving portion 206, the secondary device 650 is interchangeable with a battery pack that is compatible with the power tool 104. In other words, the battery pack may be coupled to the power tool 104, via the secondary device 650, when the secondary device 650 is coupled to the power tool 104 and may be coupled directed to the power tool 104 when the secondary device 650 is decoupled from the power tool 104.
In some embodiments, the battery receiving portion 206 of the power tool 104 incorporates the increase of height of the secondary device 650. That is, in some embodiments, the battery receiving portion 206 increases in size to accommodate both the secondary device 650 and the battery pack. For example, in some embodiments,
In the illustrated embodiment, the power tool 104 receives a slide-on style battery pack including guides rails that secure the battery pack to the power tool 104. Accordingly, the top portion 660 also includes two guide rails 680a, 680b to mate with the corresponding structure in the battery receiving portion 206. The secondary device 650 also includes pass-through connections (not shown) that allow the battery terminals to be accessible through the lower portion 665. For example, the pass-through connections may include a set of terminal ports on the top portion 660 of the secondary device 650 and a set of terminal connections on the lower portion 665 of the secondary device 650. The terminal ports receive the battery terminals on the battery receiving portion 206 of the power tool 104, while the set of terminal connections are received by an attached battery pack. Similar to the compartment 277 described above, the secondary device 650 includes an irreversible locking mechanism. That is, once the secondary device 650 is coupled to the power tool 104 and the locking mechanism is engaged, the secondary device 650 becomes permanently attached to the power tool 104. As discussed above with respect to
As shown in
The secondary device 700 further includes conductive data and power terminals 714 (
Because the secondary device 700 is coupled to the exterior of the housing of the power tool 104, the size and specific design of the secondary device 700 may not be as restricted as compared to when, for example, the secondary device 700 fits inside the housing of the power tool 104. Accordingly, the secondary device 700 may include additional features than those described with respect to the wireless communication device 300 and the back-up power source 252. When the secondary device 700 includes the wireless communication device 300, the external position of the secondary device 700 may increase the power and range of the wireless communication device 300 as compared to when the secondary device is enclosed within the housing of the power tool 104. For example, the secondary device 700 may include a larger back-up power source 252 and be less susceptible to electromagnetic interface from the power tool 104 with the additional spacing provided from battery terminals and electronics of the tool. Additionally, with an external mounting, the secondary device 700 may serve as a theft deterrent due to its visibility on the power tool 104. While the secondary device 700 is illustrated in
In the illustrated embodiment, the engagement structure 760 includes a set of horizontal (e.g., perpendicular to the handle of the power tool 140) guide rails 775 and an irreversible locking mechanism (not shown). The set of horizontal guide rails 775 engage with a compatible structure 780 on the exterior of the power tool 104. Because the guide rails 775 extend for approximately the length of the secondary device 750, the engagement structure 760 of the secondary device 750 of
Because the secondary device 750 is coupled to the exterior of the housing of the power tool 104, the size and specific design of the secondary device 750 may be less restricted and may allow for other features or devices to be incorporated into the secondary device 750. When the secondary device 750 includes the wireless communication device 300, the external position of the secondary device 750 may increase the power and range of the wireless communication device 300 as compared to when the secondary device is enclosed within the housing of the power tool 104. For example, the secondary device 700 may include a larger back-up power source 252 and be less susceptible to electromagnetic interface from the power tool 104 with the additional spacing provided from battery terminals and electronics of the tool. Additionally, the secondary device 750 may serve as a theft deterrent due to its visibility on the power tool 104. While the secondary device 750 is illustrated in
Although the power tool 104 has been illustrated and described as an impact wrench, the compartments 277 and secondary devices 650, 700, 750 may be included in other power tools or power tool devices.
On the other hand,
Finally,
In some embodiments, the power tool 104 includes a set of conductive data terminals in communication with the data connection 262 of the controller 226 (
The controller 226 also includes a data connection (e.g., a communication channel) 262 to optionally couple to the insertable wireless communication device 300. In some embodiments, the data connection 262 includes a ribbon cable that is connected from the controller 226 to a set of leads in the compartment 277. When the wireless communication device 300 is inserted into the compartment 277, a set of leads on the wireless communication device 300 connect with the leads inside the compartment 277 and communication between the controller 226 and the wireless communication device 300 is thereby enabled (for example, see
The descriptions above of the compartment 277 and the secondary devices 650, 700750 indicate that the secondary devices 650, 700, 750 are permanently locked into the compartments 277 once they have been coupled to the power tool 104. In some embodiments, the locking mechanism is a combination of mechanical structures that allow an initial coupling of the secondary device 650, 700, 750, but inhibits the removal of the same. In some embodiments, an electronic locking mechanism may be used. In such embodiments, the secondary devices 650, 700, 750 may be physically removed from the power tool 104, but doing so may render both the secondary device 600, 650, 700 and the power tool 104 inoperable.
In the illustrated embodiment, the engagement structure includes an irreversible locking mechanism 985 including a lock mating tooth 990 engaging a mating tab of the power tool (see, e.g., the mating tab 330 in
During operation of the power tool 104, the controller 226 then receives a trigger signal (step 1020), for example in response to the trigger 212 being actuated. The trigger signal indicates a desired operation of the power tool 104. In response to receiving the trigger signal, the controller 226 requests the identification code from the coupled wireless communication device 330 (step 1025). The wireless communication device 330 responds to the request by providing the identification code of the wireless communication device 330 to the controller 226. The controller 226 then determines whether an identification code was received from a wireless communication device 330 (step 1027). When the controller 226 does not receive an identification code from a wireless communication device 330 (e.g., within a predetermined time-out time period), the controller 226 proceeds to step 1040 and inhibits operation of the power tool 104. For example, the controller 226 may not receive an identification code from the wireless communication device 330 because the wireless communication device has been forcibly disconnected from the power tool 104 or damaged by a thief.
Otherwise, when the controller 226 receives the identification code, the controller 226 then determines whether the received identification code matches the stored identification code for the wireless communication device 330 (step 1030). When the received identification code matches the stored identification code, the controller 226 operates the power tool 104 according to the received trigger signal (step 1035). On the other hand, when the received identification code does not match the stored identification code (for example, when the wrong wireless communication device 330 is coupled to the power tool 104), the controller 226 inhibits operation of the power tool (step 1040). In one embodiment, the controller 226 disconnects the motor from the power source such that the motor cannot be activated. In other embodiments, the controller 226 destroys a portion of the controller 226 or other electrical components of the power tool 104. For example, the controller 226 may transmit an excessive amount of power through some of the electrical components of the power tool 104 to prevent the power tool 104 from operating again. In the illustrated embodiment, the power tool 104 also generates an alert signal (step 1045). The alert signal indicates to the user that the original wireless communication device 330 is no longer coupled to the power tool 104 and the power tool 104 is therefore inoperable. In some embodiments, the power tool 104 may transmit the alert signal to the external device 108 via the attached wireless communication device 330.
By matching the received identification code with the stored identification code, the controller 226 detects when the original wireless communication device 330 is removed, even if a replacement wireless communication device 330 was coupled to the power tool 104. Additionally, as described above with respect to step 1027, when the original wireless communication device 330 is removed from the power tool 104, the controller 226 does not receive an identification code, and the power tool 104 also becomes inoperable. In some embodiments, for example, when the original wireless communication device 330 is malfunctioning or is accidentally removed, a service center may provide a universal passcode that will clear the stored identification code from the memory 232 of the power tool 104. After the stored identification code is cleared, the power tool 104 may operate without the wireless communication device 330 or may be paired with a different wireless communication device 330.
In some embodiments, in steps 1010 and 1015, the power tool 104 provides an identification code to the wireless communication device 330 (step 1010) and the wireless communication device 330 stores the identification code of the power tool 104 in 256 (step 1015). In particular, the wireless communication controller 250 of the wireless communication device 330 performs these steps and the actions explained below as being performed by the wireless communication device 330. In some embodiments, the identification code for the power tool 104 includes, for example, a unique identifier stored in the memory 232 of the power tool 104. In some embodiments, the identification code for the power tool 104 may include, for example, a global unique identification (GUID) that includes the power tool's specific make, model, and serial number. Then, in step 1025, the wireless communication device 330 request the identification code from the power tool 104. The wireless communication device 330 then determines whether an identification code was received (step 1027) and, if not, the wireless communication device 330 inhibits further communication with the power tool 104 (step 1040). If an identification code is received, the wireless communication device 330 determines, in step 1030, whether the power tool 104 coupled to the wireless communication device 330 corresponds to the power tool 104 of the stored identification code. When the wireless communication device 330 determines that the attached power tool 104 does not correspond to the power tool 104 of the stored identification code, the wireless communication device 330 inhibits further communication between the wireless communication device 330 and the power tool 104 (step 1040). For example, to inhibit further communication, the processor 258 enters a disabled mode in which communications are not sent to the power tool 104. In some embodiments, after inhibiting communication in step 1040, the wireless communication device 330 transmits an alert message to the external device 108 to alert the user that the wireless communication device 330 is inoperable with the power tool 104 (step 1045). When the wireless communication device 330 determines that the attached power tool 104 corresponds to the power tool 104 of the stored identification code by comparing the received identification code and identification the stored code and determining a match, the wireless communication device 330 enables further communications with the power tool 104 (step 1040).
While described with respect to the secondary devices 650, 700, 750, 975, the flow chart 1000 similarly applies to the wireless communication devices 300 of other embodiments described herein, such as shown and discussed with respect to
In
Thus, the invention provides, among other things, a power tool including a compartment with an irreversible lock for receiving and retaining a wireless communication device.
This application is a continuation of U.S. patent application Ser. No. 16/684,455, filed Nov. 14, 2019, which is a continuation of U.S. patent application Ser. No. 16/056,710, filed Aug. 7, 2018, now U.S. Pat. No. 10,510,199, which claims priority to U.S. Provisional Patent Application No. 62/590,819, filed on Nov. 27, 2017, and to U.S. Provisional Patent Application No. 62/541,860, filed on Aug. 7, 2017, the entire contents of all of which are hereby incorporated by reference.
Number | Name | Date | Kind |
---|---|---|---|
1990035 | Franz et al. | Feb 1935 | A |
3616864 | Sorenson et al. | Nov 1971 | A |
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 |
8113066 | Eckstein et al. | Feb 2012 | 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 |
8418778 | Eshleman 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 |
8792598 | Cendrillon et al. | Jul 2014 | B1 |
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 | Koshikawa 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 |
11085582 | Mergener et al. | Aug 2021 | B2 |
11212909 | Smith et al. | Dec 2021 | 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 |
20100295747 | Zeltser et al. | 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 |
20180212377 | Zimmermann et al. | 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 |
20190173349 | Smith et al. | Jun 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 |
---|---|---|
1324125 | Nov 2001 | CN |
102983399 | Mar 2013 | CN |
103579741 | Feb 2014 | CN |
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 |
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 |
2019171523 | Oct 2019 | JP |
1020180108895 | Oct 2018 | KR |
2007058596 | May 2007 | WO |
2012035815 | Mar 2012 | WO |
2012035854 | Mar 2012 | WO |
2013014914 | Jan 2013 | WO |
2013112469 | Aug 2013 | WO |
2013116303 | Aug 2013 | WO |
2013136917 | Sep 2013 | WO |
2015061370 | Apr 2015 | WO |
2016206859 | Dec 2016 | WO |
2016206860 | Dec 2016 | WO |
2017089100 | Jun 2017 | WO |
2017089452 | Jun 2017 | WO |
2017093160 | Jun 2017 | WO |
2017151954 | Sep 2017 | WO |
2018024637 | Feb 2018 | WO |
2018162233 | Sep 2018 | WO |
2018177669 | Oct 2018 | WO |
2018177671 | Oct 2018 | WO |
2019115434 | Jun 2019 | WO |
Entry |
---|
Pixie 2.0 User Guide, 6 pages, accessed Jan. 31, 2019. |
Pixie, <https://getpixie.com> webpage accessed Jan. 31, 2019. |
Number | Date | Country | |
---|---|---|---|
20210183188 A1 | Jun 2021 | US |
Number | Date | Country | |
---|---|---|---|
62590819 | Nov 2017 | US | |
62541860 | Aug 2017 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 16684455 | Nov 2019 | US |
Child | 17188327 | US | |
Parent | 16056710 | Aug 2018 | US |
Child | 16684455 | US |