Patent Grant
10569398
The present invention relates to enabling communication with power tools and power tool devices.
In one embodiment, the invention provides an adapter for a power tool. The adapter includes a housing, a tool-side connector supported by the housing and configured to couple to a power tool or a charger, and a battery-side connector supported by the housing and configured to couple to a battery pack. The battery-side connector is in electrical communication with the tool-side connector. The adapter also includes a communication interface supported by the housing and configured to couple with an external device, and a controller. The communication interface is in electrical communication with the tool-side connector and the battery-side connector. The controller is supported by the housing and coupled to the tool-side connector, the battery-side connector, and the communication interface. The controller is configured to determine a state of the power tool. The state of the power tool is one of an active state in which an actuator of the power tool is in operation or an idle state during which the actuator is idle. The controller is also configured to operate in a data transmission mode, in which the adapter exchanges data between the external device and one of the power tool or the battery pack when the power tool is in the idle state, operate in a pass-through mode, in which the adapter transfers power from the battery pack to the power tool when the power tool is in the active state, and switch between the data transmission mode and the pass-through mode based on the state of the power tool.
In another embodiment, the invention provides a method of operating a power tool including an adapter. The adapter includes a tool-side connector configured to couple to the power tool, a battery-side connector configured to couple to a battery pack, and a communication interface configured to couple with an external device. The power tool is in one of an active state or an idle state. The method includes determining, by the adapter, whether the power tool is in the active state or the idle state, exchanging data between the external device and one of the power tool or the battery pack when the power tool is in the idle state, and transferring, by the tool-side connector and the battery-side connector, electrical power from the battery pack to the power tool when the power tool is in the active state. The method further includes switching between transferring electrical power and exchanging data based on the state of the power tool. During the active state, a motor of the power tool is in operation and during the idle state, the motor is idle.
In another embodiment, the invention provides an adapter for a power tool. The adapter includes a housing having a first side, a second side opposite the first side, and a sidewall connecting the first side and the second side. The sidewall is substantially perpendicular to the first side and the second side. The adapter also includes a tool-side connector supported by the housing and positioned on the first side of the housing. The tool-side connector is configured to couple to the power tool. The adapter further includes a latching mechanism supported by the housing, and positioned on the first side of the housing, a battery-side connector, and a port. The latching mechanism is configured to secure the adapter to the power tool. The battery-side connector is supported by the housing and positioned on the second side of the housing. The battery-side connector is configured to couple to a battery pack. The port is supported by the housing and positioned on the sidewall of the housing. The port is configured to couple with an external device.
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.
Using the external device 800, 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 200 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 800 also allows a user to set operational parameters, safety parameters, select tool modes, and the like for the power tool 200 or the battery pack 400.
The external device 800 may be, for example, a laptop computer, a tablet computer, a smartphone, a cellphone, or another electronic device capable of communicating with the adapter 600 and providing a user interface. The external device 800 includes a communication interface that is compatible with the adapter 600. The communication interface of the external device 800 may include a USB port, a micro USB port, another suitable power and/or data port, a wireless communication module (e.g., a Bluetooth® module), or a combination thereof. The external device 800, therefore, grants the user access to data related to the power tool 200, the battery pack 400, or another power tool device (e.g., a charger), and provides a user interface such that the user can interact with the controller of the power tool 200, the battery pack 400, or another power tool device.
In addition, as shown in
Although the power tool 200 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
The device receiving portion 206 is configured to receive and couple to the battery pack 400, the adapter 600, or another power tool device with a compatible connector. The device receiving portion 206 includes a device interface 222 (see
In the illustrated embodiment, the trigger 212 extends partially down a length of the handle 204; however, in other embodiments the trigger 212 extends down the entire length of the handle 204 or may be positioned elsewhere on the power tool 200. The trigger 212 is moveably coupled to the handle 204 such that the trigger 212 moves with respect to the tool housing. The trigger 212 is coupled to a push rod, which is engageable with a trigger switch 213 (see
As shown in
As shown in
The four male blade terminals 252a-d, include a power positive (“B+”) terminal 252a, a power negative (“B−”) terminal 252b, a first communication terminal 252c, and a second communication terminal 252d. The power positive terminal 252a and the power negative terminal 252b are configured to connect to power terminals on the battery pack 400 or on the adapter 600. The power tool 200 does not include an internal power supply for driving the motor 214 or powering the controller 226. Rather, the power tool 200 receives power through the power terminals 252a-b.
The first communication terminal 252c and the second communication terminal 252d exchange information with the battery pack 400, the adapter 600, or another connected power tool device. For example, the power tool 200 communicates to the battery pack 400 through the first communication terminal 252c and/or the second communication terminal 252d when the power tool 200 is ready to receive electrical power to energize the motor 214. The power tool 200 is also configured to determine certain characteristics of the battery pack 400 based on the signals exchanged over the first communication terminal 252c and/or the second communication terminal 252d. For example, the communication terminals 252c-d can be used by the battery pack 400 or the power tool 200 to identify the other of the battery pack 400 or the power tool 200. For example, the power tool 200 can identify the battery pack 400 as a high capacity battery pack or a normal capacity battery pack, as a lithium-based battery or a nickel-based battery, as a battery pack having a particular voltage, a higher resistance battery pack, a lower resistance battery pack, etc.
The battery pack 400 can also receive identification information from the power tool 200 through the first and/or second communication terminals 252c-d. For example, the battery pack 400 can identify the power tool 200 as a hammer drill, a drill/wrench, an impact wrench, a brushless power tool, a brushed power tool, a higher resistance power tool (e.g., capable of lower power output), a lower resistance power tool (e.g., capable of higher power output), etc.
The power tool 200 is also configured to exchange data with the adapter 600 through the first communication terminal 252c and the second communication terminal 252d. The power tool 200 can be queried for and export data or information regarding power tool usage, specific parameters utilized to monitor the power tool 200, specific modes stored within the power tool 200, and/or maintenance data regarding the power tool 200. The power tool 200 can also receive through the first and second communication terminals 252c-d new configuration and/or programming information from the adapter 600. For example, the adapter 600 may upload software implementing alternate algorithms to control operation of the motor 214, or algorithms for protecting different power tool circuitry.
The device interface 222 is coupled to the power input unit 224. The device interface 222 transmits the power received through the power terminals 252a-b to the power input unit 224. The power input unit 224 includes combinations of active and passive components to regulate or control the power received through the device interface 222 and to the controller 226. For instance, the power input 224 may receive 18V from the device interface 222 and output 5V to the controller 226. When the device interface 222 is connected to the battery pack 400, the power input unit 224 receives power directly from the battery pack 400. When the device interface 222 is connected to the adapter 600, the power input unit 224 receives power through the adapter 600. The adapter 600 may receive power from the battery pack 400 when the battery pack 400 is connected to the adapter 600 or from the external device 800 when the external device 800 is coupled to the adapter 600. In some situations, the adapter 600 may be coupled to both the battery pack 400 and the external device 800. In such situations, the adapter 600 may select whether to provide electrical power from the battery pack 400, the external device 800, or a combination thereof.
The controller 226 is also coupled to the trigger switch 213 to receive an activation signal from the trigger 212. In the illustrated embodiment, the trigger switch 213 is a push-button electrical switch positioned within the handle 204. The trigger switch 213 includes a push button and electrical contacts. When the push button is activated, such as by the push rod discussed above, the electrical contacts are in a CLOSED position. Generally, when the electrical contacts are in the CLOSED position, electrical current is supplied from the device interface 222 to the motor 214, via the switching network 216. When the push button is not activated, the electrical contacts are in the OPEN position. When the electrical contacts are in the OPEN position, electrical current is not supplied from the device interface 222 to the motor 214. Although the trigger switch 213 is illustrated as a push-button electrical switch with contacts, other types of electrical switches may be used in addition to or in place of the push-button electronic switch. For instance, 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.
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 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 200 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.
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 200. 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 200. For example, the indicators 220 are configured to indicate measured electrical characteristics of the power tool 200, the status of the power tool 200, 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 200. 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 200. 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 and a data storage area. The program storage area and the data storage area 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 200 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 controller 226 also stores on the memory 232 information regarding the usage of the power tool 200, information regarding the maintenance of the power tool 200, power tool trigger event information, and other information relevant to operating or maintaining the power tool 200. Such power tool information may then be accessed by a user with the external device 800 through the adapter 600. In other constructions, the controller 226 includes additional, fewer, or different components.
At a given point in time, the power tool 200 may be in an active state or an idle state. The idle state refers to a state of the power tool 200 during which the power tool 200 is not performing the task associated with the power tool 200. In contrast, the active state refers to when the power tool 200 is actively performing the associated task.
The state of the power tool 200 can be determined in different ways. For example, in some embodiments, the state of the power tool 200 is determined based on the position of the trigger 212. In such embodiments, the power tool 200 is determined to be in the active state when the trigger 212 is depressed. The power tool 200 is determined to be in the idle state when the trigger 212 is not depressed by the user.
In other embodiments, the state of the power tool can be determined based on the output signals from the sensors 218. In such embodiments, the power tool 200 is determined to be in the active state when the sensors 218 indicate that the motor 214 is in motion (i.e., the motor 214 is energized). The power tool 200 is determined to be in the idle state when the sensors 218 indicate that the motor 214 is stationary (i.e., the motor 214 is not energized). Additionally, or alternatively, the state of the power tool 200 can be determined based on the state of the electrical switches in the switching network 216 or from the output signals from the controller 226 to the switching network 216. When the switches in the switching network 216 are off or inactive, the state of the power tool 200 is determined to be idle. When the switches in the switching network 216 are on or active, the state of the power tool 200 is determined to be active. The state of the power tool can also be determined in other ways not explicitly described above. Additionally, the state of the power tool can also be determined by a combination or combinations of the techniques described above and those not explicitly described above.
The battery pack 400 is connectable to and supportable by the power tool 200 and the adapter 600. As shown in
The battery pack 400 is removably and interchangeably connected to the power tool 200, the adapter 600, and other power tool devices through the coupling mechanism 408. The coupling mechanism 408 includes a pair of actuators 414 and a pair of tabs 416. One of the actuators 414 and one of the tabs 416 are shown in
The illustrated battery pack 400 includes ten battery cells 404. In other embodiments, the battery pack 400 can have more or fewer battery cells 404. The battery cells 404 can be arranged in series, parallel, or a series-parallel combination. For example, in the illustrated embodiment, the battery pack 400 includes a total of ten battery cells 404 configured in a series-parallel arrangement of two sets of five series-connected cells 404. The series-parallel combination of battery cells 404 allows for an increased voltage and an increased capacity of the battery pack 400. In some embodiments, the battery pack 400 includes a single set of five series-connected battery cells 404. In other embodiments, the battery pack 400 includes a different number of battery cells 404 (e.g., between 3 and 12 battery cells) connected in series, parallel, or a series-parallel combination in order to produce a battery pack 400 having a desired combination of nominal battery pack voltage and battery capacity.
In the illustrated embodiment, the battery cells 404 are lithium-based battery cells having a chemistry of, for example, lithium-cobalt (“Li—Co”), lithium-manganese (“Li—Mn”), or Li—Mn spinel. In some embodiments, the battery cells 404 have other suitable lithium or lithium-based chemistries, such as a lithium-based chemistry that includes manganese, etc. The battery cells 404 within the battery pack 400 provide operational power (e.g., voltage and current) to the power tool 200. In one embodiment, each battery cell 404 has a nominal voltage of approximately 3.6V, such that the battery pack 400 has a nominal voltage of approximately 18V. In other embodiments, the battery cells 404 have different nominal voltages, such as, for example, between 3.6V and 4.2V, and the battery pack 400 has a different nominal voltage, such as, for example, 10.8V, 12V, 14.4V, 24V, 28V, 36V, between 10.8V and 36V, etc. The battery cells 404 also have a capacity of, for example, approximately between 1.0 ampere-hours (“Ah”) and 5.0 Ah. In exemplary embodiments, the battery cells 404 have capacities of approximately, 1.5 Ah, 2.4 Ah, 3.0 Ah, 4.0 Ah, between 1.5 Ah and 5.0 Ah, etc. The battery cells 404 are also arranged to provide an efficient use of space and to maintain a relatively small pack size.
As shown in
The fuel gauge 422 provides visible indications to the user regarding the state of charge of the battery cells 404. The fuel gauge 422 includes, for example, one or more indicators, such as light-emitting diodes (“LEDs”). The fuel gauge 422 is coupled to and controlled by the controller 420 to display conditions of, or information associated with, the state-of-charge of the battery cells 404. The fuel gauge 422 may include a pushbutton 427. The controller 420 detects depression of the pushbutton 427 and, in response, causes the fuel gauge 422 to display the state of charge information for a predetermined period of time.
The electrical power provided by the battery pack 400 is controlled, monitored, and regulated using control electronics within the power tool 200 and within the battery pack 400 as illustrated in the electromechanical diagrams of
As discussed above, the battery cells 404 are coupled to the controller 420 and to the charge/discharge module 426. The battery cells 404 generate electrical power provided to the power tool 200, the adapter 600, or another power tool device. The charge/discharge control module 426 includes, for example, one or more switches (e.g., FETs) for controlling the charging current to and discharge current from the battery cells 404.
The power interface 424 is coupled to the controller 420 and to the charge/discharge control module 426. The power interface 424 communicates with the controller 420 and receives electrical power from the charge/discharge control module 426. The power interface 424 includes a contact block 410 having a plurality of contacts 412a-e as shown in
The battery pack 400 is removably and interchangeably connected to the power tool 200, the adapter 600, or another power tool device to provide operational power (i.e., voltage and current) to the power tool 200, the adapter 600, or the other power tool device through the contacts 412a-e. The contacts 412a-e are in electrical communication with the terminals 252a-d of the power tool 200 when the battery pack 400 is directly or indirectly (e.g., via the adapter 600) coupled to the power tool 200. When the battery pack 400 is coupled directly to the power tool 200, the battery pack contacts 412a-e mate directly with the terminals 252a-d. When the battery pack 400 is coupled to the power tool 200 through the adapter 600, the contacts 412a-e mate with the adapter 600, which provides electrical communication between the contacts 412a-e of the battery pack 400 and the terminals 252a-d of the power tool 200.
The five contacts 412a-e include a positive power (“B+”) contact 412a, a negative power (“B−”) contact 412b, and three communication contacts 412c-e. The positive power contact 412a and the negative power contact 412b are configured to connect to the power terminals 252a,b, respectively, on the power tool 200 to provide operational power (i.e., voltage and current) to the power tool 200. The power contacts 412a-b are also configured to couple to power terminals on the adapter 600 as will be discussed below. The battery pack 400 communicates with the power tool 200, the adapter 600, or another power tool device through at least two of the communication contacts 412c-e. The two communication terminals 252c-d of the power tool 200 align with two of the three communication contacts 412c-e of the battery pack 400 to enable communication between the devices. The third contact of the communication contacts 412c-e is unmated and not used in this instance, but may be used in connection with other power tools and devices. The battery pack 400 communicates with the power tool 200 to determine when the power tool 200 is ready to receive electrical power and to communicate to the power tool 200 when the battery pack 400 is ready to provide electrical power to the power tool 200. The battery pack 400 is also configured to exchange data with the adapter 600 through at least two of the communication contacts 412c-e.
The sensors 428 include, for example, one or more current sensors, one or more voltage sensors, one or more temperature sensors, etc. The controller 420 uses the sensors 428 to monitor operation of the battery pack 400. The controller 420 also includes a variety of preset or calculated fault condition values related to temperatures, currents, voltages, etc., associated with the operation of the power tool 200. For example, the controller 420 uses the sensors 428 to monitor an individual state of charge of each of the battery cells 404, monitor a current being discharged from the battery cells 404, monitor the temperature of one or more of the battery cells 404, etc., for fault condition interrupts. If the voltage of one of the battery cells 404 is equal to or above an upper voltage limit (e.g., a maximum charging voltage), the charge/discharge control module 426 prevents the battery cells 404 from being further charged or requests that a battery charger (not shown) provide a constant voltage charging scheme. Alternatively, if one of the battery cells 404 falls below a low-voltage limit, the charge/discharge control module 426 may prevent the battery cells 404 from being further discharged. Similarly, if an upper or lower operational temperature limit for the battery cells 404 of the battery pack 400 is reached, the controller 420 can control the charge/discharge module 426 to prevent further charging or discharging until the temperature of the battery cells 404 or the battery pack 400 is within an acceptable temperature range.
The controller 420 is electrically and/or communicatively connected to a variety of modules or components of the battery pack 400. For example, the illustrated controller 420 is connected to the fuel gauge 422, the sensors 428, the power interface 424, the battery cells 404, and the charge/discharge control module 426 (optional within battery pack 400). The controller 420 includes combinations of hardware and software that are operable to, among other things, control the operation of the battery pack 400, activate the fuel gauge 422 (e.g., including one or more LEDs), monitor the operation of the battery pack 400, etc.
In some embodiments, the controller 420 includes a plurality of electrical and electronic components that provide power, operational control, and protection to the components and modules within the controller 420 and/or battery pack 400. For example, the controller 420 includes, among other things, a processing unit 430 (e.g., a microprocessor, a microcontroller, or another suitable programmable device), a memory 432, input units 434, and output units 436. The processing unit 430 includes, among other things, a control unit 440, an arithmetic logic unit (“ALU”) 442, and a plurality of registers 444 (shown as a group of registers in
The memory 432 includes, for example, a program storage area and a data storage area. The program storage area and the data storage area 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 430 is connected to the memory 432 and executes software instructions that are capable of being stored in a RAM of the memory 432 (e.g., during execution), a ROM of the memory 432 (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 battery pack 400 can be stored in the memory 432 of the controller 420. 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 420 is configured to retrieve from the memory 432 and execute, among other things, instructions related to the control of the battery pack 400 described herein. The controller 420 can also store on the memory 432 various battery pack parameters and characteristics (including battery pack nominal voltage, chemistry, battery cell characteristics, maximum allowed discharge current, maximum allowed temperature, etc.).
The battery pack 400 is also configured to store other information related to the operation of the battery pack 400 in the memory 432. For example, the controller 420 may obtain and store information regarding the number of charge and discharge cycles, the discharge time, the type of power tools the battery pack 400 is coupled to, the average temperature, the temperature as the state-of-charge of the battery cells 404 decrease, and other such relevant information. This information may then be transmitted or shared with the external device 800 through the adapter 600. In other constructions, the controller 420 includes additional, fewer, or different components.
The battery pack 400 is also configured to couple to a battery pack charger (not shown). The battery pack 400 utilizes one of the communication contacts 412e to receive charging current from the charger. In other words, charging current is delivered to the battery pack 400 on the negative power contact 412b and the third communication contact 412e. The battery pack 400 also communicates information regarding charging schemes, charging status, and the like to the charger through the three communication contacts 412c-e. Although the battery pack 400 is described as including five contacts 412a-e, in other embodiments, the battery pack 400 may include more or less contacts. The battery pack 400, however, includes at least a positive power contact, a negative power contact, and at least one communication contact.
As explained above with respect to the power tool 200, the battery pack 400 is configured to communicate different information to the power tool 200, the adapter 600, or another power tool device. For example, the battery pack 400 may communicate certain characteristics of the battery pack 400 to the power tool 200, the adapter 600, or another power tool device through communication contacts 412c-e and corresponding structure (e.g., communication terminals 252c-d) on the power tool 200, the adapter 600, or another power tool device. For example, the battery pack 400 and the power tool 200 may exchange identification signals to identify to one another the type of power tool 200 or the type of battery pack 400. In some embodiments, the battery pack 400 may also send an identification signal to the adapter 600 to identify the battery pack to the adapter 600. Other information can also be exchanged through the communication contacts 412c-e of the battery pack 400 such as, for example, battery pack capacity, battery pack voltage, battery pack chemistry, discharge and charging algorithms stored in the battery pack 400 (i.e., in the memory 432 of the battery pack), thresholds monitored by the controller 420 of the battery pack 400, discharge and charge history for the battery pack 400, and other relevant information for the battery pack 400. The battery pack 400 uses the communication contacts 412c-e to export and import such information from the external device 800 through the adapter 600. The battery pack 400 may also share some, or all, of this information with the power tool 200 or with a battery pack charger.
When coupled to the power tool 200, the adapter 600, or another power tool device, the battery pack 400 substantially encloses and covers corresponding terminals (e.g., the terminals 252a-d) on the power tool 200, the adapter, and other power tool devices. That is, the battery pack 400 functions as a cover for the terminals 252a-d of the power tool 200 and the connecting portion of the adapter 600.
As shown in
The tool-side receiving portion 606 includes a tool-side connector 622 (see
The tool-side connector 622 (see
In the illustrated embodiment, the tool-side connector 622 also includes a raised bar 630. The raised bar 630 physically inhibits the adapter 600 from coupling to power tools 200 that are incompatible with the adapter 600. For example, in some embodiments, high-power power tools may not couple with the adapter 600 and thereby, not exchange information with the external device 800. In other embodiments, power tools 200 may be incompatible with the adapter 600 for other reasons such as, for example, the power tool communication protocol is not compatible with the adapter, the power tool 200 does not accept reconfiguration files from the external device 800 for security reasons, the power tool 200 does not record information to be exported through the adapter 600, etc. In other embodiments, the adapter 600 does not include the raised bar 630 and is not prevented from coupling to certain power tools.
When the adapter 600 is coupled to the power tool 200, or another power tool device including a similar device receiving portion 206, the adapter 600 substantially encloses and covers the blade terminals 252a-d on the power tool 200. That is, the adapter 600 functions as a cover for the terminals 252a-d of the power tool 200. Once the adapter 600 is disconnected from the power tool 200, the terminals 252a-d on the power tool 200 are generally exposed to the surrounding environment. In the illustrated embodiment, the adapter 600 is designed to substantially follow the contours of the power tool 200 to match the general shape of the outer casing of the handle 204 of the power tool 200. The adapter 600 also generally increases (e.g., extends) the length of the grip of the tool (i.e., the portion of the power tool below the main body).
The adapter 600 is removable and interchangeably connected to various power tools through the latching mechanism 616. The latching mechanism 616 releasably secures the adapter 600 to the power tool 200. As shown in
The battery-side receiving portion 608 includes a battery-side connector 624 (see
The four male blade terminals 638a-d are connected to the adapter 600 through the terminal block 636, which connects the blade terminals 638a-d to the housing 604 and to the other electronics of the adapter 600. When the adapter 600 is not coupled to the battery pack 400, the blade terminals 638a-d are generally exposed to the surrounding environment. However, as discussed above with respect to the battery pack 400, when the battery 400 is coupled to the adapter 600, the female contacts 412a-e of the battery pack 400 receive the blade terminals 638a-d of the adapter 600. The female contacts 412a-e, therefore, cover the terminals 638a-d and protect them from the surrounding environment. As shown in
As shown in
The communication port 612 is positioned on the first surface 644 of the front sidewall. The communication port 612 is also connected to a PCB 650 of the adapter 600 (see
The communication port 612 is protected by a cover 654. The cover 654 is attached with a hinge on an upper edge of the cavity 652. The cover 654 is pivotable between an open position and a closed position. In the open position, the cover 654 is at an angle with the first surface 644 of the sidewall and the cavity 652 is exposed to the environment. In the closed position, the cover 654 is flush with the sidewall of the housing 604 and the cavity 652 is protected from the external environment (see
The adapter 600 also includes other electronic components that are mounted on the PCB 650 and positioned within the adapter housing 604. The housing 604 includes a base plate 656 and a cover 657 (see
As shown in
The contacts 628a-e are coupled to the housing 604 through a support plate 668. The support plate 668 holds the contacts 628a-e above the PCB such that they are accessible to a connected device (e.g., the power tool 200) on the top side 618 of the housing 604. A portion of each of the contacts 628a-e extends below the support plate 668 and is connected to the PCB 650 by a second set of connecting wires 670. Similar to the connecting wires 662, the connecting wires 670 are illustrated as having a free end, but in a final assembly, the free ends of the connecting wires 670 are each connected (e.g., soldered) to a respective contact 628a-e.
As shown in
As shown in
The controller 674 is electrically and/or communicatively connected to a variety of modules and/or components of the adapter 600, as shown in
The memory 688 includes, for example, a program storage area and a data storage area. The program storage area and the data storage area 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 686 is connected to the memory 688 and executes software instructions that are capable of being stored in a RAM of the memory 688 (e.g., during execution), a ROM of the memory 688 (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 adapter 600 can be stored in the memory 688 of the controller 674. 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 674 is configured to retrieve from memory and execute, among other things, instructions related to the control processes and methods described herein.
In the illustrated embodiment, the controller 674 is also configured to store power tool information, battery pack information, or information received from another power tool device on the memory 688 of the adapter 600. When the adapter 600 receives data from, for example, the power tool 200 through the tool-side connector 622, the adapter 600 stores the received data in the memory 688. The adapter 600 may at a future point in time be coupled to the external device 800 to output the power tool data stored in memory 688. Analogously, the adapter 600 may be coupled to the external device 800 to obtain configuration data and/or programming data specific for the power tool 200. The adapter 600 may couple to the power tool 200 at a future point in time and relay the configuration and programming information to the power tool 200 via the tool-side connector 622.
The tool-side connector 622 includes the five contacts 628a-e. The five contacts 628a-e include a positive power contact 628a, a negative power contact 628b, and three communication contacts 628c-e. The positive power contact 628a and the negative power contact 628b are configured to connect to the power terminals 252a,b on the power tool 200. The positive and negative power contacts 628a-b provide operational power (i.e., voltage and current) to the power tool 200. The adapter 600 communicates with the power tool 200, or another power tool device through at least two of the communication contacts 628c-e. The two communication terminals 252c-d of the power tool 200 align with two of the three communication contacts 628c-e of the adapter 600 to enable communication between the devices. The third contact of the communication contacts 628c-e is unmated and not used in this instance, but may be used in connection with other power tools and devices. The adapter 600 communicates with the power tool 200 to obtain information regarding the power tool status, operation statistic, or power tool identification. The adapter 600 can also write data to the power tool 200 for power tool configuration, firmware upgrades, or to send commands (e.g., turn on a worklight).
The adapter 600 exchanges data/information with the power tool 200, or another similar power tool device by transmitting and receiving signals through the two communication terminals 252c-d and two communication contacts 628c-d. The adapter 600 and the power tool 200 include programmed instructions specifying which terminal/contact will be used for the adapter 600 to transmit data and which terminal/contact will be used for the power tool 200 to transmit data. In other words, when explained from the perspective of the adapter 600, one communication contact 628c is used to transmit data to the power tool 200 and the second communication contact 628d is used to receive data from the power tool 200. In other embodiments, the adapter 600 may transmit data to the power tool 200 using the second communication contact 628d and receive data from the power tool 200 using the first communication contact 628c. Once the transmitter/receiver terminals/contacts have been established, the adapter 600 and the power tool 200 may exchange data over the two communication links.
In the illustrated embodiment, the adapter 600 and the power tool 200 use a software communication technique to exchange data over the communication terminals 252c-d and the communication contacts 628c-d. In the illustrated embodiment, the adapter 600 becomes the master device and the power tool 200 becomes the slave device. The master device (i.e., the adapter 600) initiates data communication. In other embodiments, the power tool 200 is the master device and the adapter 600 the slave device. To begin communication, the adapter 600 sends a start signal to the power tool 200. After the start signal has been sent, the adapter 600 utilizes software executed by the processing unit 686 to alternate (i.e., switch between a high output and a low output) a transmit pin of the controller 674 that is coupled to the communication contact 628c. The start signal is used to communicate to the power tool 200 (or slave device) the baud rate and stop bits for the communication between the adapter 600 and the power tool 200. The power tool 200 detects the start signal, determines the communicated baud rate and stop bits, and begins sampling the terminal 252c coupled to the communication contact 628c. The adapter 600 sends a predetermined number of bits and then sends a stop signal. In the illustrated embodiment, the start signal is a high output on the transmitter contact 628c for the duration of two bits and the stop signal is a low output on the transmitter contact 628c for the duration of two bits. The power tool 200 detects the start signal and begins sampling the terminal 252c coupled to the communication contact 628c to receive data bits output by the adapter 600. The power tool 200 samples the value of each bit and stores it in a register. The power tool 200 then recognizes the stop signal and waits for another start signal from the adapter 600. If the adapter 600 has finished transmitting bits to the power tool 200, the power tool 200 can respond to the adapter 600 by sending the start signal, a predetermined number of bits, and the stop signal. In other words, the power tool 200 can transmit information/data to the adapter 600 using a similar procedure with reversal of roles (e.g., the power tool 200 transmits, the adapter 600 receives) and using the other communication terminal 252d and communication contact 628d.
To ensure that communication occurs accurately, the power tool 200 and the adapter 600 set or are preprogrammed with certain communication parameters. For example, the power tool 200 and the adapter 600 communicate at the same baud rate, which allows the power tool 200 and the adapter 600 to sample the signals on the transmit pins appropriately. The power tool 200 and the adapter 600 also communicate using a specific data packet size. The data packet size refers to the number of bits the power tool 200 or the adapter 600 transmits between each start and stop signal. In the illustrated embodiment, the power tool 200 and the adapter 600 communicate with a data packet size of eight bits. That is, the transmitting device (either the adapter 600 or the power tool 200) transmits the start signal, eight data bits, and the stop signal. The receiving device then knows that the first bit corresponds to the start signal, the following eight bits correspond to encoded data, and the last signal corresponds to the stop signal. Communicating in such a way allows the power tool 200 and the adapter 600 to segment the data and make it easier for the receiving device to decode. The power tool 200 and the adapter 600 also set or are programmed to communicate in the same endiannes, which refers to the order in which bits are transmitted. In the illustrated embodiment, the most significant bit is transmitted first. In other embodiments, the least significant bit is transmitted first. These and other communication parameters may be preprogrammed into the adapter 600 and the power tool 200. In other embodiments, the user may be able to change some of these parameters such as, for example, the baud rate. The user may adjust the baud rate using the external device 800 and communicating the change in baud rate to both the adapter 600 and the power tool 200.
In other embodiments, rather than communicating using the software implemented method described above, the adapter 600 and the power tool 200 exchange data over the communication terminals 252c-d and the communication contacts 628c-d using one or more universal asynchronous transmitter/receivers (“UART”) to encode and decode the transmissions between the adapter 600 and the power tool 200. In other embodiments, the power tool 200 and the adapter 600 may use similar hardware to encode and decode the communication over the data terminals 252c-d and the communication contacts 628c-d.
The battery-side connector 624 includes the four terminals 638a-d. The four male blade terminals 638c-d include a power positive terminal 638a, a power negative terminal 638b, a first communication terminal 638c, and a second communication terminal 638d. The power positive terminal 638a and the power negative terminal 638b are configured to connect to power terminals on the battery pack 400 or other power tool device. The power terminals 638a, 638b on the battery-side connector 624 receive operational power (i.e., voltage and current) from the battery pack 400. The operational power may be transmitted to the power tool 200, used to power the adapter 600, or both.
The adapter 600 uses the first communication terminal 638c and the second communication terminal 638d to exchange information with the battery pack 400. The adapter 600 uses a similar communication protocol as was described between the power tool 200 and the adapter 600. Therefore, software executed by the processing unit 686 allows a transmit pin of the controller 674 to be toggled between low output and high output to send a start signal, data bits, and a stop signal. The battery pack 400 uses the processing unit 430 to sample and decode the transmitted bits.
The communication interface 680 is coupled between the external device 800 and the controller 674 of the adapter 600 to allow the adapter 600 to communicate and exchange data with the external device 800. As shown in
The communication port 612 includes a positive power terminal, a negative power terminal, and at least one data terminal. The communication port 612 receives power from the external device 800 through the positive power terminal and the negative power terminal. The adapter 600 may receive electrical power from the external device 800 and power the controller 674 as well as other electrical components of the adapter 600. The adapter 600 and the external device 800 exchange data over the at least one data terminal of the communication port 612 using serial communication protocols.
In the illustrated embodiment, the communication port 612 includes a universal serial bus (USB) port. The USB port 612 includes a positive power terminal, a negative power terminal, and two data terminals. The adapter 600 and the external device 800 utilize the two data terminals on the USB port 612 to exchange data using differential signaling. As discussed above, the adapter 600 and the external device 800 exchange data regarding the power tool 200, the battery pack 400, or another power tool device to which the adapter 600 can be connected.
In other embodiments, the communication port 612 may include another type of communication port. For example, the communication port 612 may include an RS-232 port, a microUSB port, a proprietary port, etc. Furthermore, the adapter 600 may include more than one communication port 612 such that the adapter 600 is compatible with different external devices 800 that may include different types of communication ports or connectors.
The wireless communication module 684 provides an alternative way for the adapter 600 to communicate with the external device 800. That is, the wireless communication module 684 selectively uses the communication port 612 or the wireless communication module 684 to communicate with the external device 800. The wireless communication module 684 includes a radio transceiver and an antenna to send and receive wireless messages to and from the external device 800. The wireless communication module 684 may be used, for example, when the external device 800 does not include a connector or port compatible with the communication port 612, or when wireless communication is preferred by a user. The wireless communication module 684 may include its own controller to effect wireless communications between the adapter 600 and the external device 800. For example, a controller associated with the wireless communication module 684 may buffer incoming and/or outgoing data, communicate with the controller 674, and determine the communication protocol and/or settings to use in wireless communications.
In the illustrated embodiment, the wireless communication module 684 is a Bluetooth® module. The Bluetooth® module communicates with the external device 800 employing the Bluetooth® protocol. Therefore, in the illustrated embodiment, the external device 800 and the adapter 600 are in proximity of each other while they exchange data. In other embodiments, the wireless communication module 684 communicates using other protocols (e.g., Wi-Fi, cellular protocols, etc.) over a different type of wireless networks. For example, the wireless communication module 684 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 communication interface 680, both wired and wireless, may be encrypted to protect the data exchanged between the adapter 600 and the external device/network 800 from third parties.
By electrically coupling the tool-side connector 622, the battery-side connector 624, and the communication interface 680, the adapter 600 enables communications between the external device 800 and the power tool 200, the battery pack 400, or another power tool device. The adapter 600 is configured to receive data from the power tool 200 and the battery pack 400 and relay the information to the external device 800. In a similar manner, the adapter 600 is configured to receive information (e.g., configuration and programming information) from the external device 800 and relay the information to the power tool 200, the battery pack 400, or another power tool device.
The communication indicator 614 provides a visual indication to the user regarding the power and communication status of the adapter 600. The communication indicator 614 includes an LED that is connected to the PCB 650 of the adapter 600 (see
In yet other embodiments, when the adapter 600 communicates with the external device 800 through the communication port 612, the communication indicator 614 does not light up. Instead, when the adapter 600 communicates with the external device 800 using the wireless communication module 684, the communication indicator 614 lights up. In other embodiments, the adapter 600 may include one indicator for each type of communication interface with the external device 800. In other embodiments, the adapter 600 may, additionally or alternatively, activate the indicator 614 when the adapter 600 communicates with the external device 800 via the communication port 612.
The power input module 682 is configured to receive the electrical power from the battery pack 400, the external device 800, an integrated power source (e.g., a 9V battery), or a combination thereof. The power input module 682 is also configured to condition the received power into usable power for the various components of the adapter 600. Conditioning the power may include, for example, reducing the electrical power received by the power input module 682 into the appropriate voltage and/or current parameters, or filtering the power received by the power input module 382. The power input module 682 communicates with the controller 674 to determine the power parameters necessary for the controller 674 and ensure that the power provided by the power input module 682 meets the necessary power parameters of the controller 674 and of the other electronic components of the adapter 600.
The power input module 682 is in electrical communication with the battery-side connector 624 and with the communication port 612. As described above, both the battery-side connector 624 and the communication port 612 are configured to receive electrical power through the power terminals (e.g., 638a-b). The power input module 682 is configured to receive electrical power from at least one of the battery side connector 624 and the communication port 612. When the adapter 600 is coupled to the battery pack 400, the adapter 600 receives electrical power (i.e., voltage and current) from the battery pack 400 through the battery side connector 624 (i.e., the blade terminals 638a-b). When the adapter 600 is coupled to the external device 800 through the communication port 612, the adapter 600 receives electrical power from the communication port 612. Although the external device 800 is configured to provide electrical power to the power tool 200 through the communication port 612, the power from the external device 800 may not be sufficient to energize the motor 214 of the power tool 200. Rather, the power from the external device 800 is used to power the controller 226 of the power tool 200, such that data can still be exchanged between the power tool 200 and the external device 800.
In some situations, the adapter 600 may be coupled to both the battery pack 400 via the battery side connector 624 and the external device 800 through the communication port 612 at the same time. In such instances, the adapter 600 defaults to receiving electrical power from the battery pack 400. In other embodiments, the adapter 600 may default to receiving electrical power from the external device 800 through the communication port 612. In some embodiments, the adapter 600 may be configured to receive electrical power from both the battery pack 400 and the external device 800 when both the battery pack 400 and the external device 800 are physically and electrically coupled to the adapter 600. In such embodiments, the battery pack 400 may be utilized to power some components of the adapter (e.g., an LCD display, the communication indicator 614, etc.) while the external device 800 is utilized to power different components of the adapter (e.g., the controller 674, the wireless communication module 684, etc.).
The power switch 610 is a push-button switch that turns the adapter 600 on and off. When the adapter 600 is on, communication between the external device 800 and the power tool 200 or the battery pack 400 is enabled. When the adapter 600 is off, communications between the power tool 200 and the external device 800 or between the battery pack 400 and the external device 800 cease. In some embodiments, the power switch 610 also includes a lighting element that lights up when the adapter 600 is powered and lights off when the adapter 600 is not powered, thereby providing a visual indication to the user of the power status of the adapter 600. In some embodiments, if the adapter 600 is coupled to both the power tool 200 and the battery pack 400, the power tool 200 and the battery pack 400 can communicate with each other and perform general operations (i.e., the battery pack 400 can transmit electrical power to the power tool 200 to drive the motor 214) regardless of whether the adapter 600 is on or off. In other embodiments, however, the power tool 200 and the battery pack 400 can only communicate with each other and perform general operations when the adapter 600 is either on or removed such that the battery pack 400 is connected directly with the power tool 200.
The adapter 600 switches between a data transmission mode and a pass-through mode. In the data transmission mode, the adapter 600 communicates with the power tool 200, the battery pack 400, or another power tool device using the techniques described above. During the data transmission mode, the adapter 600 can receive and transmit information related to, for example, power tool usage data, usage statistics, power too identification, power tool maintenance data, battery pack discharge cycles, battery pack charge cycles, battery pack conditions and characteristics, configuration and programming data, firmware updates, or a command (e.g., sound an alert tone or flash an LED).
The pass-through mode refers to the operation of the adapter 600 during which data communication does not occur and during which electrical power from the battery pack 400 is passed through the adapter 600 to reach the power tool 200. Instead of exchanging information between the power tool 200 or the battery pack 400, the adapter 600 serves as an intermediary pathway between the device interface 222 of the power tool 200 and the power interface 424 of the battery pack 400. During the pass-through mode, the battery pack 400 transmits electrical power to the power tool 200, which enables the power tool 200 to perform the associated task (e.g., drilling, driving, sawing, sanding, etc.).
The adapter 600 switches between the data transmission mode and the pass-through mode based on the state of the power tool 200. When the power tool 200 is in the active state, the adapter 600 operates in the pass-through mode such that the power tool 200 receives electrical power from the battery pack 400 and communication between the power tool 200 and the battery 400 is enabled. On the other hand, when the power tool 200 is in the idle state, the adapter 600 is able to exchange data with the power tool 200 or with the battery pack 400, if connected. Accordingly, the adapter 600 operates in the data transmission mode when the power tool 200 is in the idle state and operates in the pass-through mode when the power tool 200 is in the active state.
In some embodiments, during the data transmission mode, the adapter 600 does not store received data in memory 688. Rather, the adapter 600 is connected to both the external device 800 and the power tool device (e.g., the power tool 200 or the battery pack 400) simultaneously to exchange data between the external device 800 and the power tool device. In such embodiments, since the data is moving seemingly immediately from the power tool 200 to the external device 800 or from the external device 800 to the power tool 200, the adapter 600 optionally does not store the data in the memory 688. Rather, the adapter 600 may include a buffer that momentarily holds the data received from the power tool 200 or battery pack 400 before the adapter 600 transmits the data to the external device 800, and that holds the data received from the external device 800 en route to the power tool 200 or the battery pack 400.
In some embodiments, the adapter 600 may be capable of both storing power tool data, battery pack data, and data received from another power tool device in the memory 688 and retrieve the data at a later time, and of transmitting the data seemingly instantaneously between the power tool 200, the battery pack 400, or another power tool device and the external device 800. In such embodiments, the adapter 600 may default to exchanging data seemingly instantaneously when both a power tool device (e.g., the power tool 200, the battery pack 400, etc.) and the external device 800 are coupled to the adapter 600.
In the illustrated embodiment, the controller 674 is also coupled to the external memory receiver 678 to store additional or duplicative data on an external memory coupled thereto. The external memory receiver 678 may include, for example, a port positioned on the housing 604 of the adapter 600 for receiving an external memory (e.g., an SD card). The port for the external memory is not shown in the figures, but may be positioned on a sidewall of the housing 604. For example, a slot for receiving an SD card can be positioned on a back sidewall opposite the communication port 612. The external memory receiver 678 allows power tool data and battery pack data to be stored separate from the adapter 600. For example, a set of power tools may be associated with the same owner. Tool and/or battery pack data can be exported from each power tool one at a time, and saved onto the external memory. The owner can then keep the data associated with the set of power tools in the same external memory to back up the data stored on the external device 800, or to avoid storing the data on the external device 800. The external memory may also provide additional protection for the data stored therein. In the illustrated embodiment, the external memory includes a Secure Digital (“SD”) card. In other embodiments, the external memory may include other types of memory such as, for example, a USB flash drive.
The controller 674 is also connected to the display connector 676. The display connector 676 is provided on the adapter 600 to provide the user with an alternative way of interacting with the communication system 100, and in particular, with the adapter 600. A user may connect a display to the display connector 676 and be able to access information without exporting the data to the external device 800. For example, if the user wishes to quickly access maintenance information for the power tool 200, the user may couple the power tool 200 to the adapter 600, connect a display to the display connector 676, and access the maintenance information stored on the tool. Therefore, the user can access power tool 200 and/or battery pack 400 information without exporting data from the power tool device (e.g., the power tool 200, the battery pack 400, etc.) and importing data from the adapter 600 to the external device 800. In some embodiments, the display can be integral to the adapter 600 and positioned on a sidewall of the housing 604.
The first power tool 1200, the battery pack 1400, and the second power tool 1300 each include a wireless communication module that allows the power tool devices to communicate directly with the external device 1800. The power tool devices (e.g., the first power tool 1200, the second power tool 1300, and the battery pack 1400 may communicate power tool status, power tool operation statistics, power tool identification, stored power tool usage information, power tool maintenance data, battery pack status, battery pack state of charge, battery pack operation statistics, battery pack identification, battery pack discharge and charge cycles, battery pack maintenance data, and the like. The external device 1800 can also write data to the first power tool 1200, the second power tool 1300, and/or the battery pack 1400 for power tool configuration, battery pack configuration, firmware upgrades, or to send commands (e.g., turn on a worklight). The external device 1800 also allows a user to set operational parameters, safety parameters, select tool modes, select battery pack options, and the like.
The external device 1800 may be, for example, a laptop computer, a tablet computer, a smartphone, a cellphone, or another electronic device capable of communicating with the adapter 600 and providing a user interface. The external device 1800 includes a wireless communication module that is compatible with the wireless communication module of the first power tool 1200, the second power tool 1300, and the battery pack 1400. The external device 1800, therefore, grants the user access to data related to the first power tool 1200, the second power tool 1300, the battery pack 1400, or another power tool device (e.g., a charger), and provides a user interface such that the user can interact with the controller of the first power tool 1200, the second power tool 1300, the battery pack 1400, or another power tool device.
In addition, the external device 1800 can also share the information obtained from the first power tool 1200, the second power tool 1300, the battery pack 1400, or another power tool device with a remote server 1900. The remote server 1900 may be used to store the data obtained from the external device 1800, provide additional functionality and services to the user, or a combination thereof. In one embodiment, storing the information on the remote server 1900 allows a user to access the information from a plurality of different locations. In another embodiment, the remote server 1900 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 1900 may provide statistics regarding the experienced efficiency of the power tools 1200, 1300, or battery pack 1400, typical usage of the power tools 1200, 1300, and other relevant characteristics and/or measures of the power tools 1200, 1300 or the battery pack 1400.
As shown in
In the illustrated embodiment, the wireless communication module 1250 is a Bluetooth® module. The Bluetooth® module communicates with the external device 1800 employing the Bluetooth® protocol. Therefore, in the illustrated embodiment, the external device 1800 and the first power tool 1200 are in proximity of each other while they exchange data. In other embodiments, the wireless communication module 1250 communicates using other protocols (e.g., Wi-Fi, cellular protocols, etc.) over a different type of wireless networks. For example, the wireless communication module 1250 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 communication module 1250 may be encrypted to protect the data exchanged between the first power tool 1200 and the external device/network 1800 from third parties.
As discussed above, the wireless communication module 1250 is configured to receive data from the power tool controller 1226 and relay the information to the external device 1800. In a similar manner, the wireless communication module 1250 is configured to receive information (e.g., configuration and programming information) from the external device 1800 and relay the information to the power tool controller 1226. The other components and operations of the power tool 1200 are similar to those described with reference to the power tool 200 of the communication system shown in
As shown in
As shown in
In the illustrated embodiment, the wireless communication module 1450 is a Bluetooth® module. The Bluetooth® module communicates with the external device 1800 employing the Bluetooth® protocol. Therefore, in the illustrated embodiment, the external device 1800 and the battery pack 1400 are in proximity of each other while they exchange data. In other embodiments, the wireless communication module 1450 communicates using other protocols (e.g., Wi-Fi, cellular protocols, etc.) over a different type of wireless networks. For example, the wireless communication module 1450 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 communication module 1450 may be encrypted to protect the data exchanged between the first battery pack 1400 and the external device/network 1800 from third parties.
As discussed above, the wireless communication module 1450 is configured to receive data from the battery pack controller 1420 and relay the information to the external device 1800. In a similar manner, the wireless communication module 1450 is configured to receive information (e.g., configuration and programming information) from the external device 1800 and relay the information to the battery pack controller 1420. The other components and operations of the battery pack 1400 are similar to those described with reference to the battery pack 400 of the communication system shown in
In the illustrated embodiment, the wireless modules 1250, 1350, 1450 included in the first power tool 1200, the second power tool 1300, and the battery pack 1400 are substantially similar (e.g., Bluetooth® communication modules). Using similar wireless communication modules 1250, 1350, 1450 allows the power tool devices to be compatible with each other and with generally the same external devices 1800. In other embodiments, however, the wireless communication module 1250, 1350, 1450 in each of the power tool devices may be different from each other. In such embodiments, the external device 1800 may include different communication modules to accommodate the wireless communication modules 1250, 1350, 1450 of the different power tool devices, or each of the power tool devices 1200, 1300, 1400 may be compatible with different sets of external devices 1800.
The first power tool 1200 and the battery pack 1400 shown in
The mode selection switches 1508 allow a user to select a mode of operation for the impact driver 1500. As shown in
Through communication with the external device 800, 1800, the impact driver 1500 can determine which four modes are accessible to the user when operating the impact driver 1500. In other words, the user can select and assign a mode to each of the mode indicators 1511a-d from on a list of different operation modes for the impact driver 1500. The other modes that are compatible with the impact driver 1500 and available for assignment to the mode indicators 1511a-d, but that are not currently assigned, may be referred to as unassigned modes of the impact driver 1500. The user may select modes for assignment from a variety of pre-configured modes and user-defined modes. The pre-configured modes and the user-defined modes may be stored in a memory of the impact driver 1500 and the user may select which mode is assigned to which mode indicator 1511a-d through the external device 800, 1800. In other embodiments, the pre-configured modes and the user-defined modes are stored on the external device 800, 1800 or on the remote server 900, 1900 and the user selects which modes to assign to and store on the impact driver 1500 using the external device 800, 1800. In these embodiments, the four modes assigned to the mode indicators 1511a-d are stored on the impact driver 1500, while the other potential (unassigned) modes remain on a memory outside of the tool (e.g., on the external device 800,1800 or remote server 900,1900).
A pre-configured mode is, for instance, a mode that sets specific performance characteristics (or variables) of the tool for addressing certain applications. A pre-configured mode may have certain default settings for particular applications (e.g., working with certain screw types or lengths or with certain types of work pieces like metal or wood), and a user may further configure certain relevant performance characteristics within a pre-configured mode. A user-defined mode allows the user to adjust certain performance characteristics (or variables) controllable on the tool. The performance characteristics that are adjustable may depend on the selected user-defined mode. A user-defined mode may rely on the user to set performance characteristics to fit their particular application, rather than using pre-programmed settings selected based on particular applications.
The pre-configured modes for the impact driver 1500 include a low speed mode, a medium speed mode, a high speed mode, a self-tapping screw mode, a screwdriver mode, a stainless steel mode, an anti-slip mode, an anti-strip mode, and an anti-spin off mode. The low speed mode is generally used for precision work. In the first mode, a motor of the impact driver 1500 operates at low speeds (e.g., between 0-200 revolutions per minute (RPM)). The medium speed mode is generally used to prevent damage to the fastener and/or to the material on which the fastener is secured. In the medium speed mode, the motor of the impact driver 1500 operates at medium speeds (e.g., between 0-2,000 RPMs). The high speed mode is generally used to utilize the maximum speed and power available on the impact driver 1500. In the high speed mode, the motor of the impact driver 1500 operates at high speeds (e.g., between 0-2,900 RPMs). The low speed mode, medium speed mode, and high speed mode are, in some embodiments, by default assigned to the first mode indicator 1511a, second mode indicator 1511b, and third mode indicator 1511c, respectively. Other modes may be assigned as the default modes, and the fourth mode indicators 1511d may be assigned a default mode as well, such as the self-tapping screw mode. A user can continue to use these default modes, or the user may find that other modes are better suited for a task or project and may change the modes accordingly.
The self-tapping screw mode is generally used for driving self-tapping screws into galvanized steel, and it prevents a user from overdriving and stripping screws by operating the impact driver at too high a level of RPMs and impacts per minute (IPMs). In the self-tapping screw mode, the impact driver 1500 begins turning at a high speed (e.g., 1000 RPMs) and reduces the speed when an impact mechanism trips. During the self-tapping screw mode, a controller of the impact driver 1500 monitors an impact mechanism. When the controller determines that the impact mechanism has been activated, the controller reduces the power provided to the motor of the impact driver 1500 to thereby reduce the rotating speed of the impact driver 1500. A user may be able to further configure/customize the self-tapping screw mode by selecting, for example, the starting speed for the impact driver 1500, the finishing or lowered speed for the impact driver 1500, and/or the rate at which the impact driver 1500 decreases speed. The user may change such parameters using the external device 800/1800.
The screwdriver mode is generally used for driving small machine screws. Many users find it challenging to use an impact driver for more delicate applications because they may worry that the impact mechanism may damage the fastener and/or the material. In the screwdriver mode, the impact driver 1500 operates at low rotational speeds (e.g., 0-500 RPMs). During the screwdriver mode, the impact driver 1500 also activates an electronic clutch such that operation of the impact driver 1500 stops before the impact mechanism is activated. The electronic clutch anticipates when the impact mechanism may be activated and instead interrupts power to the motor of the impact driver 1500 to prevent the impact driver 1500 from damaging the fastener and/or the material. A user may determine the maximum speed (e.g., maximum RPMs) when the impact driver 1500 operates in the screwdriver mode.
The stainless steel mode is generally used for driving self-tapping screws into 12-16 gauge stainless steel. Due to the nature of stainless steel, users have encountered that some screw tips melt before cutting the surface of stainless steel. Many users have been sacrificing fasteners until the surface is cut and a fastener can be properly installed. In the stainless steel mode, the impact driver 1500 automatically pulses the trigger 1512. By pulsing the trigger 1512, the impact driver 1500 operates at slower speeds. Slower speeds actually perforate stainless steel faster and generate less heat between the screw tip and the surface of the stainless steel. Therefore, by using the stainless steel mode, the user may not need to sacrifice fasteners until the surface of the stainless steel is finally perforated. A user may further customize the stainless steel mode by setting maximum RPMs and IPMS, setting minimum RPMs and IPMs, and/or setting the pulsing frequency for the impact driver 1500.
The anti-slip mode is generally used for driving screws at high speeds into metal or wood. Some users, when trying to drive screws at high speeds, lose engagement between the impact driver 1500 and the fastener head and/or have the fastener slip off the desired drive position on the surface of the material. In the anti-slip mode, the impact driver 1500 begins driving at a lower speed (e.g., 250 RPMs) and automatically increases the driving speed when the impact mechanism is activated. Therefore, by starting at a lower speed, slipping of the impact driver 1500 and/or slipping of the fastener becomes less likely, and efficiency is achieved by automatically increasing the fastening speed once the impact mechanism is activated. The user may further customize the anti-slip mode by setting starting RPMs or IPMs, setting increased and/or finishing RPMs or IPMs, and/or setting the rate at which the fastening speed increases.
The anti-strip mode is generally used for driving concrete screws into a concrete block or concrete slab. The anti-strip mode may also be used for driving small sheet metal screws into sheet metal. Concrete screws can sometimes break in the middle of the screw or at the head of the screw, rendering the screw unusable because the impacts are too fast or too strong, and the screw is overdriven. In the anti-strip mode, the impact driver 1500 begins fastening the concrete screws at a high speed (e.g., 1500 RPMs) and decreases the fastening speed when the impact mechanism is activated. The user may customize the anti-strip mode by selecting the starting RPMs or IPMs, setting the finishing RPMs or IPMs, and/or setting the rate at which the fastening speed decreases.
The anti-spin off mode is generally used for removing fasteners such as, nuts and bolts. When removing nuts and bolts, the nuts and bolts can sometimes lose engagement with the impact driver 1500 and fall from a lift or elevated surface. In the anti-spin off mode, the impact driver 1500 begins rotating at a high speed (e.g., 1500 RPMs) and automatically decreases the fastening speed when the impact mechanism is deactivated. The user can further customize the anti-spin off mode by selecting starting RPMs/IPMs, selecting finishing RPMs or IPMs, and/or setting the rate at which the fastening speed decreases.
The selectable modes of the impact driver 1500 can also be assigned user-defined modes. The user-defined modes include modes for which the user defines the operation of the impact driver 1500. The user-defined modes for the impact driver 1500 include an impact counting mode, a memory mode, an impacting variable speed mode, and a non-impacting mode. The impact counting mode is generally used for repetitive pre-fabrication and/or production fastening. The impact counting mode can also be used for driving anchors on projects with seismic regulations. The impact counting mode ensures that the same torque is applied to every fastener. In the impact counting mode, the impact driver 1500 employs a counter and/or a timer to count how many impacts the impact driver 1500 delivers to a fastener. When the impact driver 1500 uses a timer, the timer determines the period of time during which the impact driver 1500 impacts the fastener. In the impact counting mode, specific maximum and minimum rotational speeds are assigned to the trigger 1512, such that the same torque is applied to every fastener. The impact driver 1500 can then be used to secure one fastener, and any subsequent fastener will be secured with the same number of impacts or for the same amount of time as the first fastener, thereby ensuring equal torque is applied to each fastener. A user may further specify the minimum and maximum RPMs set to the trigger 1512.
The memory mode is also used for repetitive pre-fabrication and/or production fastening. In the memory mode, the impact driver 1500 records a fastening operation and then repeats the fastening operation on subsequent fasteners. For example, for the first fastening operation, the impact driver 1500 may record the RPMs, the IPMS, and/or the trigger 1512 travel profile. Then, when fastening a second fastener, the impact driver 1500 follows the trigger travel profile, the RPMs, and the IPMs as recorded.
The impacting variable speed mode is generally used for driving fasteners for which users may prefer more control over the minimum and maximum speeds (e.g., RPMs) than those specified by the low speed, medium speed, and high speed modes for the impact driver 1500. Therefore, the impacting variable speed mode allows a user to specifically set the maximum and the minimum speeds for the impact driver 1500. In some embodiments, the user may set the maximum and the minimum speeds for the impact driver 1500 at the same speed, and thereby deactivate the variable speed mode of the impact driver 1500.
The non-impacting mode is generally used for driving small fasteners that require low torque. As discussed above, some fasteners or particular applications for fasteners are fragile. Therefore, the impacting mechanism may damage the fastener and/or the material. In the non-impacting mode, the user selects the maximum fastening speed such that the impacting mechanism is not activated. In some embodiments, the user can use the non-impacting mode for setting the minimum and maximum fastening speeds to the same speed and thereby deactivating the variable speed mode for the impact driver 1500.
The external device 800/1800 can be also used to program and/or change different parameters on the impact driver 1500. The external device 800/1800 may set, for example, minimum and maximum fastening speeds (e.g., max and min RPMs), speed oscillation, soft start time, trigger travel, downshift/upshift mid-application (which can be triggered by the impact mechanism being activated), maximum number of impacts, and/or activation and operation of a worklight for the impact driver 1500.
The external device 800/1800 can also be used to measure speed on the impact driver 1500 in real time, measure trigger travel on impact driver 1500 in real time, as well as measuring other operational parameters of the impact driver 1500 in real time. For instance, the power tool 1500 may wirelessly communicate tool data in real time to the external device 800, 1800.
Like the impact driver 1500, the impact wrench 1600 includes four assigned operation modes at a given time. Each mode indicator 1611a-d can be assigned by the user a a different operation mode. The user selects a mode for each mode indicator 1611a-d using the external device 800, 1800. The user may select from a variety of pre-configured modes and user-defined modes. The pre-configured modes and the user-defined modes may be stored in a memory of the impact wrench 1600, and the user may select which mode is assigned to which mode indicator 1611a-d through the external device 800, 1800. In other embodiments, the pre-configured modes and the user-defined modes are stored on the external device 800, 1800, or on the remote server 900, 1900, and the user selects which modes to assign and store on the impact wrench 1600 using the external device 800, 1800. In these embodiments, the four modes assigned to the mode indicators 1611a-d are stored on the impact wrench 1600, while the other potential (unassigned) modes remain on a memory outside of the tool (e.g., on the external device 800,1800 or remote server 900,1900).
The pre-configured modes for the impact wrench 1600 include a low speed mode, a medium speed mode, a high speed mode, a consistent torque mode, and an anti-spin off mode. The low speed mode is generally used for precision work. In the first mode, a motor of the impact wrench 1600 operates at low speeds (e.g., between 0-200 revolutions per minute (RPM)). The medium speed mode is generally used to prevent damage to the fastener and/or to the material on which the fastener is secured. In the medium speed mode, the motor of the impact wrench 1600 operates at medium speeds (e.g., between 0-2,000 RPMs). The high speed mode is generally used to utilize the maximum speed and power available on the impact wrench 1600. In the high speed mode, the motor of the impact wrench 1600 operates at high speeds (e.g., between 0-2,900 RPMs). A fourth mode is a programmable mode assigned to a fourth mode indicator 1611d. The programmable mode varies based on user interaction with the external device 800, 1800. In some embodiments, the low speed mode, medium speed mode, and high speed mode are by default assigned to the first mode indicator 1611a, second mode indicator 1611b, and third mode indicator 1611c, respectively. Other modes may be assigned as the default modes, and the fourth mode indicators 1611d may be assigned a default mode as well, such as the self-tapping screw mode. A user can continue to use these default modes, or the user may find that other modes are better suited for a task or project and may change the modes accordingly.
The consistent torque mode is generally used for driving the same type of fastener multiple times where a consistent bolt tension is desired. In the consistent torque mode, the impact wrench 1600 counts the number of impacts performed by the impact wrench and stores the RPMs used for each particular fastener. When a subsequent fastener is secured, the impact wrench 1600 counts the number of impacts and ceases operation when the same number of impacts are performed on the subsequent fastener. The impact wrench 1600 also ensures that the fastening speed is the same for a set of fasteners, thereby ensuring that the same torque is applied to each fastener. Therefore, a user can use an external device 800, 1800 to select from a first group of modes a programmable mode for a first power tool and from a second group of modes, a programmable mode for a second power tool.
The anti-spin off mode is generally used for removing nuts and bolts. When removing nuts and bolts, the nuts and bolts can sometimes lose engagement with the impact wrench 1600 and fall from a lift or elevated surface. In the anti-spin off mode, the impact wrench 1600 begins rotating at a high speed (e.g., 1500 RPMs) and automatically decreases the fastening speed when the impact mechanism is deactivated. The user can further customize the anti-spin off mode by selecting starting RPMs/IPMs, selecting finishing RPMs or IPMs, and/or setting the rate at which the fastening speed decreases.
The selectable modes can also be assigned a user-defined mode. The user defined modes for the impact wrench 1600 include an impact counting mode, a memory mode, an impacting variable speed mode, and a non-impacting mode. The user-defined modes are substantially similar to the user-defined modes for the impact driver 1500 and will therefore not be discussed in further detail.
The external device 800/1800 can be also used to program and/or change different parameters on the impact wrench 1600. The external device 800/1800 may set, for example, minimum and maximum fastening speeds (e.g., max and min RPMs), speed oscillation, soft start time, trigger travel, downshift/upshift mid-application (which can be triggered by the impact mechanism being activated), maximum number of impacts, and/or activation and operation of a worklight for the impact wrench 1600. The external device 800/1800 can also be used to measure speed on the impact wrench 1600 real time, measure trigger travel on impact wrench 1600 in real time, as well as measuring other operational parameters of the impact wrench 1600 in real time. In some embodiments, the impact wrench 1600 communicates with the external device 800 through the adapter 600 using similar techniques as those described above with respect to the power tool 200. In other embodiments, the impact wrench 1600 includes a wireless communication module, and communicates with the external device 1800 using similar techniques as those described above with respect to the power tool 1200.
The external device 800, 1800 can also be used to program and/or define different features on the hammer drill 1700. For example, the external device 800, 1800 can allow a user to set a constant speed mode, a variable bounded speed mode, settings for soft start, electronic clutch, PWM pulse mode, and a TEK screw mode for the hammer drill 1700. The constant speed mode allows the hammer drill 1700 to ignore the position of the trigger. Instead, the hammer drill runs the hammer drill motor at a constant speed as defined by the user. The speed of the motor is then controlled by closed-loop control using sensors determining the position and speed of the motor.
The variable bounded speed mode allows the hammer drill 1700 to be operated in different speeds according to the trigger displacement. The user may set the minimum speed and/or the maximum speed. When the trigger is fully depressed, the motor operates at the maximum speed, and when the trigger is minimally depressed, the motor operates at the minimum speed. The hammer drill 1700 then operates at linearly increasing speeds between the minimally depressed position of the trigger and full depression of the trigger. The variable bounded speed mode for the hammer drill 1700 is similar to the impacting variable speed mode of the impact wrench 1600 and the impact driver 1500.
The PWM pulse mode allows the hammer drill 1700 to ignore the position of the trigger and, rather, oscillate between a minimum speed and a maximum speed. The user can select the minimum speed, the maximum speed, and the oscillation rate between the two. The hammer drill 1700 does not monitor the position of the trigger and, instead, simply begins oscillating between the two predetermined speeds. In a variation of the PWM pulse mode, the hammer drill 1700 changes the duty cycle to achieve the minimum speed and the maximum speed of the hammer drill 1700. The hammer drill 1700, in such embodiments, alternates between oscillating the motor duty cycle between a first duty cycle and a second duty cycle at a predetermined oscillation period.
The TEK screw mode, also referred to as the self-drilling screw mode, allows the hammer drill 1700 to operate in a current controlled mode. In particular, in the TEK screw mode, the hammer drill 1700 operates at a first maximum speed (e.g., 1000 RPMs). The hammer drill 1700 monitors the current of the hammer drill 1700. When the current drawn by the motor of the hammer drill 1700 exceeds a first predetermined current threshold, the hammer drill 1700 lowers the operating speed and continues to monitor the current of the hammer drill 1700. When the current of the hammer drill 1700 is below a second predetermined current threshold (e.g., 2A below the first predetermined current threshold) for a particular period of time (e.g., one second), the hammer drill 1700 resumes operating at the first maximum speed. The hammer drill 1700 operates via an open-loop control in this mode. Generally, an increase in motor current indicates an increase in resistance to driving the fastener and represents increased energy used to overcome the increased resistance.
The user can also select for the hammer drill 1700 to activate soft start and/or the electronic clutch. Soft start refers to a setting in which the hammer drill 1700 slowly increases the speed of the motor to full speed. When the trigger is first pulled, the hammer drill 1700 begins increasing the speed slowly at a predetermined rate. The electronic clutch allows the hammer drill 1700 to monitor the output torque through a current measurement. When the electronic clutch is enabled, the hammer drill 1700 operates normally until the current of the hammer drill 1700 exceeds a predetermined threshold. Once the current of the hammer drill 1700 exceeds the predetermined threshold, the hammer drill 1700 begins to pulse the hammer drill motor at low PWMs to simulate the function of a mechanical clutch. In some embodiments, the electronic clutch can program the torque range of a current ring electronic clutch setting on the hammer drill 1700.
In some embodiments, the hammer drill 1700 communicates with the external device 800 through the adapter 600 using similar techniques as those described above with respect to the power tool 200. In other embodiments, the hammer drill 1700 includes a wireless communication module, and communicates with the external device 1800 using similar techniques as those described above with respect to the power tool 1200.
Communication with the external device 800, 1800 provides a graphical user interface through which the user can select and customize the different operation modes for the different power tools 1500, 1600, 1700.
As shown in
In some embodiments, as shown in
Although
In some embodiments, a system and method for customizing a power tool includes first establishing a communication link between an external device (e.g., external device 800/1800) and the power tool (e.g., hammer drill 1700). Although not necessary, in some instances, establishing a communication link includes setting the power tool to an adaptive mode (e.g., via mode selection ring 1708) and selecting a programmable mode (e.g., using mode selection switch 1707). Establishing a communication link wirelessly can include instructing (e.g., via a user interface) the external device to wirelessly link to the power tool, which may include the user specifying to the external device details of the tool. Alternatively, a communication link can be established by attaching the adapter 600 to the power tool and either physically connecting the external device to the adapter 600 (e.g., via USB cable) or wirelessly linking the external device to the adapter 600.
After a communication link is established, the external device may generate a graphical user interface (GUI) providing mode options (see
After selecting a mode on the graphical user interface, the user may further navigate to customize (e.g., set parameters of) the selected mode, as shown and described with respect to
The exemplary screenshots of the graphical user interface generated by the external device 800, 1800 can also be used for customizing different modes for different power tools 1500, 1600, 1700. The exemplary screens 2012, 2023, 2030, 2034, 2036 can also be used to request information such as, for example, the maximum speed for a particular power tool 1500, 1600, 1700. It should be understood that the earlier modes discussed above with respect to the impact driver 1500, the impact wrench 1600, and the hammer drill 1700 can be customizable and selected using similar screens as those shown in
Thus, the invention provides, among other things, a communication system among power tool devices and an external device, in which the external device provides a user interface to obtain information from different power tool devices and provides information to the power tool devices. Various features and advantages of the invention are set forth in the following claims.
The present application is a continuation of U.S. patent application Ser. No. 15/833,356, filed Dec. 6, 2017, which is a continuation of U.S. patent application Ser. No. 15/030,756, filed Apr. 20, 2016, now U.S. Pat. No. 10,131,042, which is a national stage filing under 35 U.S.C. § 371 of International Application No. PCT/US2014/061651, filed on Oct. 21, 2014, which claims priority benefit to U.S. Provisional Application No. 61/893,765, filed Oct. 21, 2013, the entire contents of all of which are hereby incorporated by reference. The present application is also related to U.S. application Ser. No. 15/868,116, filed on Jan. 11, 2018, now U.S. Pat. No. 10,131,043, which is also a continuation of U.S. application Ser. No. 15/833,356, filed Dec. 5, 2017.
| Number | Name | Date | Kind |
|---|---|---|---|
| 2980218 | Young | Apr 1961 | A |
| 3382305 | Breen | May 1968 | A |
| 3739659 | Workman, Jr. | Jun 1973 | A |
| 3882305 | Johnstone | May 1975 | A |
| 3965778 | Aspers et al. | Jun 1976 | A |
| 4545106 | Juengel | Oct 1985 | A |
| 4680862 | Wieland et al. | Jul 1987 | A |
| 4685050 | Polzer et al. | Aug 1987 | A |
| 4854786 | Alexander et al. | Aug 1989 | A |
| 4881435 | Hansson | Nov 1989 | A |
| 5109540 | Dzung et al. | Apr 1992 | A |
| 5154242 | Soshin et al. | Oct 1992 | A |
| 5188188 | Mars | Feb 1993 | A |
| 5203242 | Hansson | Apr 1993 | A |
| 5277261 | Sakoh | Jan 1994 | A |
| 5315501 | Whitehouse | May 1994 | A |
| 5526460 | DeFrancesco et al. | Jun 1996 | A |
| 5592396 | Tambini et al. | Jan 1997 | A |
| 5637968 | Kainec et al. | Jun 1997 | A |
| 5903462 | Wagner et al. | May 1999 | A |
| 5903762 | Sakamoto et al. | May 1999 | A |
| 5942975 | Sørensen | Aug 1999 | A |
| 6005489 | Siegle et al. | Dec 1999 | A |
| 6055484 | Lysaght | Apr 2000 | A |
| 6123241 | Walter et al. | Sep 2000 | A |
| 6157313 | Emmermann | Dec 2000 | A |
| 6161629 | Hohmann et al. | Dec 2000 | A |
| 6279668 | Mercer | Aug 2001 | B1 |
| 6349266 | Lysaght et al. | Feb 2002 | B1 |
| 6390205 | Wallgren et al. | May 2002 | B2 |
| 6405598 | Bareggi | Jun 2002 | B1 |
| 6424799 | Gilmore | Jul 2002 | B1 |
| 6431425 | Moorman et al. | Aug 2002 | B1 |
| 6432425 | Siamon | Aug 2002 | B1 |
| 6469615 | Kady et al. | Oct 2002 | B1 |
| 6508313 | Carney et al. | Jan 2003 | B1 |
| 6520270 | Wissmach et al. | Feb 2003 | B2 |
| 6522949 | Ikeda et al. | Feb 2003 | B1 |
| 6536536 | Gass et al. | Mar 2003 | B1 |
| 6547014 | McCallops et al. | Apr 2003 | B2 |
| 6598684 | Watanabe | Jul 2003 | B2 |
| 6607041 | Suzuki et al. | Aug 2003 | B2 |
| 6614349 | Proctor et al. | Sep 2003 | B1 |
| 6668212 | Colangelo, II et al. | Dec 2003 | B2 |
| 6675196 | Kronz | Jan 2004 | B1 |
| 6768994 | Howard et al. | Jan 2004 | B1 |
| 6687567 | Watanabe | Feb 2004 | B2 |
| 6784801 | Watanabe et al. | Aug 2004 | B2 |
| 6834730 | Gass et al. | Dec 2004 | B2 |
| 6836614 | Gilmore | Dec 2004 | B2 |
| 6845279 | Gilmore et al. | Jan 2005 | B1 |
| 6848516 | Giardino | Feb 2005 | B2 |
| 6872121 | Wiener et al. | Mar 2005 | B2 |
| 6876173 | Mastaler et al. | Apr 2005 | B2 |
| 6913087 | Brotto et al. | Jul 2005 | B1 |
| 6920050 | Little et al. | Jul 2005 | B2 |
| 6923285 | Rossow et al. | Aug 2005 | B1 |
| 6938689 | Farrant et al. | Sep 2005 | B2 |
| 6945337 | Kawai et al. | Sep 2005 | B2 |
| 6954048 | Cho | Oct 2005 | B2 |
| 6967972 | Volftsun et al. | Nov 2005 | B1 |
| 6968908 | Tokunaga et al. | Nov 2005 | B2 |
| 6978846 | Kawai et al. | Dec 2005 | B2 |
| 6981311 | Seith et al. | Jan 2006 | B2 |
| 6992585 | Saleh et al. | Jan 2006 | B2 |
| 7034711 | Sakatani et al. | Apr 2006 | B2 |
| 7035710 | Balling | Apr 2006 | B2 |
| 7035898 | Baker | Apr 2006 | B1 |
| 7036605 | Suzuki et al. | May 2006 | B2 |
| 7036703 | Grazioli et al. | May 2006 | B2 |
| 7054696 | Crowell | May 2006 | B2 |
| 7062998 | Hohmann et al. | Jun 2006 | B2 |
| 7064502 | Garcia et al. | Jun 2006 | B2 |
| 7064520 | Heigl et al. | Jun 2006 | B2 |
| 7086483 | Arimura et al. | Aug 2006 | B2 |
| 7093668 | Gass et al. | Aug 2006 | B2 |
| 7102303 | Brotto et al. | Sep 2006 | B2 |
| 7112934 | Gilmore | Sep 2006 | B2 |
| 7116969 | Park | Oct 2006 | B2 |
| 7119686 | Bertness et al. | Oct 2006 | B2 |
| 7121358 | Gass et al. | Oct 2006 | B2 |
| 7123149 | Nowak et al. | Oct 2006 | B2 |
| 7137541 | Baskar et al. | Nov 2006 | B2 |
| 7182147 | Cutler et al. | Feb 2007 | B2 |
| 7182150 | Grossman | Feb 2007 | B2 |
| 7185998 | Oomori et al. | Mar 2007 | B2 |
| 7211972 | Garcia et al. | May 2007 | B2 |
| 7218227 | Davis et al. | May 2007 | B2 |
| 7227335 | Sakakibara et al. | Jun 2007 | B2 |
| 7228917 | Davis et al. | Jun 2007 | B2 |
| 7243440 | DeKeyser | Jul 2007 | B2 |
| 7298240 | Lamar | Nov 2007 | B2 |
| 7314097 | Jenner et al. | Jan 2008 | B2 |
| 7391326 | Puzio et al. | Jan 2008 | B2 |
| 7328086 | Perry et al. | Feb 2008 | B2 |
| 7328752 | Gass et al. | Feb 2008 | B2 |
| 7328757 | Davies | Feb 2008 | B2 |
| 7330129 | Crowell et al. | Feb 2008 | B2 |
| 7336181 | Nowak et al. | Feb 2008 | B2 |
| 7343764 | Solfronk | Mar 2008 | B2 |
| 7346406 | Brotto et al. | Mar 2008 | B2 |
| 7346422 | Tsuchiya et al. | Mar 2008 | B2 |
| 7357526 | Zeiler | Apr 2008 | B2 |
| 7359762 | Etter et al. | Apr 2008 | B2 |
| 7382272 | Feight | Jun 2008 | B2 |
| 7383882 | Lerche et al. | Jun 2008 | B2 |
| 7419013 | Sainomoto et al. | Sep 2008 | B2 |
| 7428934 | Arimura | Sep 2008 | B2 |
| 7437204 | Lev-Ami et al. | Oct 2008 | B2 |
| 7443137 | Scott et al. | Oct 2008 | B2 |
| 7464769 | Nakazawa et al. | Dec 2008 | B2 |
| 7501778 | Hashimoto et al. | Mar 2009 | B2 |
| 7540334 | Gass et al. | Jun 2009 | B2 |
| 7594548 | Puzio et al. | Sep 2009 | B1 |
| 7613590 | Brown | Nov 2009 | B2 |
| 7638958 | Phiipp et al. | Dec 2009 | B2 |
| 7641518 | Lee et al. | Jan 2010 | B2 |
| 7646155 | Woods et al. | Jan 2010 | B2 |
| RE41160 | Gilmore et al. | Mar 2010 | E |
| RE41185 | Gilmore et al. | Mar 2010 | E |
| 7688028 | Phillips et al. | Mar 2010 | B2 |
| 7690569 | Swanson et al. | Apr 2010 | B2 |
| 7723952 | Phillips et al. | May 2010 | B2 |
| 7750811 | Puzio et al. | Jul 2010 | B2 |
| 7772850 | Bertness | Aug 2010 | B2 |
| 7784104 | Innami et al. | Aug 2010 | B2 |
| 7787981 | Austin et al. | Aug 2010 | B2 |
| 7795829 | Seiler et al. | Sep 2010 | B2 |
| 7809495 | Leufen | Oct 2010 | B2 |
| 7817062 | Li et al. | Oct 2010 | B1 |
| 7823458 | Kibblewhite et al. | Nov 2010 | B2 |
| 7834566 | Woods et al. | Nov 2010 | B2 |
| 7850071 | Sakamoto et al. | Dec 2010 | B2 |
| 7868591 | Phillips et al. | Jan 2011 | B2 |
| 7896098 | Suzuki et al. | Mar 2011 | B2 |
| 7898403 | Ritter et al. | Mar 2011 | B2 |
| 7900524 | Calloway et al. | Mar 2011 | B2 |
| 7911379 | Cameron | Mar 2011 | B2 |
| 7928673 | Woods et al. | Apr 2011 | B2 |
| 7928845 | LaRosa | Apr 2011 | B1 |
| 7931096 | Saha | Apr 2011 | B2 |
| 7940321 | Sudo | May 2011 | B2 |
| 7942084 | Wilson, Jr. et al. | May 2011 | B2 |
| 7942211 | Scrimshaw et al. | May 2011 | B2 |
| 7953965 | Qin et al. | May 2011 | B2 |
| 7982624 | Richter et al. | Jul 2011 | B2 |
| 8004397 | Forrest et al. | Aug 2011 | B2 |
| 8004664 | Etter et al. | Aug 2011 | B2 |
| 8005647 | Armstrong et al. | Aug 2011 | B2 |
| 8026814 | Heinze et al. | Sep 2011 | B1 |
| 8044796 | Carr, Sr. | Oct 2011 | B1 |
| 8049636 | Buckingham et al. | Nov 2011 | B2 |
| 8062060 | Rejman | Nov 2011 | B2 |
| 8074731 | Iwata et al. | Dec 2011 | B2 |
| 8154885 | Anderson | Apr 2012 | B2 |
| 8159345 | Stevens | Apr 2012 | B2 |
| 8161613 | Schuele et al. | Apr 2012 | B2 |
| 8169298 | Wiesner et al. | May 2012 | B2 |
| 8171828 | Duvan et al. | May 2012 | B2 |
| 8179069 | Matsunaga et al. | May 2012 | B2 |
| 8210275 | Suzuki et al. | Jul 2012 | B2 |
| 8255358 | Ballew et al. | Aug 2012 | B2 |
| 8260452 | Austin et al. | Sep 2012 | B2 |
| 8264374 | Obatake et al. | Sep 2012 | B2 |
| 8281871 | Cutler et al. | Oct 2012 | B2 |
| 8286723 | Puzio et al. | Oct 2012 | B2 |
| 8294424 | Bucur | Oct 2012 | B2 |
| 8306836 | Nichols et al. | Nov 2012 | B2 |
| 8310206 | Bucur | Nov 2012 | B2 |
| 8316958 | Schell et al. | Nov 2012 | B2 |
| 8324845 | Suzuki et al. | Dec 2012 | B2 |
| 8330426 | Suzuki et al. | Dec 2012 | B2 |
| 8344879 | Harmon et al. | Jan 2013 | B2 |
| 8351982 | Rofougaran | Jan 2013 | B2 |
| 8354183 | Konuma et al. | Jan 2013 | B2 |
| 8360166 | Iimura et al. | Jan 2013 | B2 |
| 8406697 | Arimura et al. | Mar 2013 | B2 |
| 8412179 | Gerold et al. | Apr 2013 | B2 |
| 8438955 | Wilson, Jr. et al. | May 2013 | B2 |
| 8464808 | Leü | Jun 2013 | B2 |
| 8485049 | Yokoyama et al. | Jul 2013 | B2 |
| 8576095 | Harmon et al. | Nov 2013 | B2 |
| 8611250 | Chen et al. | Dec 2013 | B2 |
| 8627900 | Oomori et al. | Jan 2014 | B2 |
| 8645176 | Walton et al. | Feb 2014 | B2 |
| 8657482 | Malackowski et al. | Feb 2014 | B2 |
| 8666936 | Wallace | Mar 2014 | B2 |
| 8678106 | Matsunaga et al. | Mar 2014 | B2 |
| 8818617 | Miller et al. | Aug 2014 | B2 |
| 8823322 | Noda et al. | Sep 2014 | B2 |
| 8890449 | Suzuki et al. | Nov 2014 | B2 |
| 8919456 | Ng et al. | Dec 2014 | B2 |
| 8954222 | Costantino | Feb 2015 | B2 |
| 8954227 | Bertosa et al. | Feb 2015 | B2 |
| 8965841 | Wallace | Feb 2015 | B2 |
| 8981680 | Suda et al. | Mar 2015 | B2 |
| 8996237 | Bertosa et al. | Mar 2015 | B2 |
| 9002572 | Lipscomb et al. | Apr 2015 | B2 |
| 9022702 | Kasuya et al. | May 2015 | B2 |
| 9022705 | Sibata et al. | May 2015 | B2 |
| 9027452 | Nagy et al. | May 2015 | B2 |
| 9027666 | Hecht et al. | May 2015 | B2 |
| 9029197 | Funatsu et al. | May 2015 | B2 |
| 9030145 | Brennenstuhl et al. | May 2015 | B2 |
| 9030169 | Christensen et al. | May 2015 | B2 |
| 9031585 | Kahle et al. | May 2015 | B2 |
| 9033769 | Mizutani et al. | May 2015 | B2 |
| 9034507 | Matthias | May 2015 | B2 |
| 9035596 | Sugiura et al. | May 2015 | B2 |
| 9035611 | Kikuchi et al. | May 2015 | B2 |
| 9038743 | Aoki | May 2015 | B2 |
| 9041543 | Inada | May 2015 | B2 |
| 9044836 | Blatz | Jun 2015 | B2 |
| 9044847 | Kohlschmied et al. | Jun 2015 | B2 |
| 9044849 | Maute et al. | Jun 2015 | B2 |
| 9048505 | Christensen et al. | Jun 2015 | B2 |
| 9048667 | Nagaoka et al. | Jun 2015 | B2 |
| 9048687 | Nakajima et al. | Jun 2015 | B2 |
| 9048699 | Oomori et al. | Jun 2015 | B2 |
| 9049641 | Wible et al. | Jun 2015 | B2 |
| 9050713 | Hartmann et al. | Jun 2015 | B2 |
| 9050715 | Umemura et al. | Jun 2015 | B2 |
| 9061359 | Wiker et al. | Jun 2015 | B2 |
| 9061392 | Forgues et al. | Jun 2015 | B2 |
| 9062827 | Krishnarao et al. | Jun 2015 | B2 |
| 9063558 | Fukumura | Jun 2015 | B2 |
| 9063569 | Tanaka et al. | Jun 2015 | B2 |
| 9065116 | Shimooka et al. | Jun 2015 | B2 |
| 9067292 | Appel | Jun 2015 | B2 |
| 9067293 | Bernardi et al. | Jun 2015 | B2 |
| D735006 | Aoki et al. | Jul 2015 | S |
| 9072403 | Braden et al. | Jul 2015 | B2 |
| 9073127 | Esenwein | Jul 2015 | B2 |
| 9073134 | Koeder et al. | Jul 2015 | B2 |
| 9073160 | Appel et al. | Jul 2015 | B2 |
| 9079258 | Chung | Jul 2015 | B2 |
| 9079290 | Esenwein | Jul 2015 | B2 |
| 9079291 | Ikuta et al. | Jul 2015 | B2 |
| 9079502 | Kikuchi et al. | Jul 2015 | B2 |
| 9080988 | Okada et al. | Jul 2015 | B2 |
| 9081883 | Wittliff, III et al. | Jul 2015 | B2 |
| 9083184 | Okabayashi et al. | Jul 2015 | B2 |
| 9085075 | Ikuta | Jul 2015 | B2 |
| 9089941 | Moreno | Jul 2015 | B2 |
| 9089989 | Hörtling | Jul 2015 | B2 |
| 9091369 | Froehlich et al. | Jul 2015 | B2 |
| 9093843 | Wirnitzer et al. | Jul 2015 | B2 |
| 9093883 | Wiszniewski et al. | Jul 2015 | B2 |
| 9097331 | Saur et al. | Aug 2015 | B2 |
| 9100019 | Akiyama | Aug 2015 | B2 |
| 9100529 | Yoshioka et al. | Aug 2015 | B2 |
| 9108283 | Simm et al. | Aug 2015 | B2 |
| 9108284 | Tada et al. | Aug 2015 | B2 |
| 9108306 | Hecht et al. | Aug 2015 | B2 |
| 9109670 | Roehm et al. | Aug 2015 | B2 |
| 9111209 | Utoh et al. | Aug 2015 | B2 |
| 9111234 | Wallace et al. | Aug 2015 | B2 |
| 9112360 | Goto et al. | Aug 2015 | B2 |
| 9114491 | Kakiuchi et al. | Aug 2015 | B2 |
| 9114514 | Leong et al. | Aug 2015 | B2 |
| 9114519 | Iwata et al. | Aug 2015 | B2 |
| 9114520 | Hirabayashi et al. | Aug 2015 | B2 |
| 9121478 | Herr | Sep 2015 | B2 |
| 9123478 | Esenwein et al. | Sep 2015 | B2 |
| 9123938 | Sasaki et al. | Sep 2015 | B2 |
| 9126317 | Lawton et al. | Sep 2015 | B2 |
| 9126320 | Shinma et al. | Sep 2015 | B2 |
| 9126321 | Muller et al. | Sep 2015 | B2 |
| 9128156 | Jardine | Sep 2015 | B2 |
| 9132541 | John et al. | Sep 2015 | B2 |
| 9133909 | Blum et al. | Sep 2015 | B2 |
| 9141128 | Cizek et al. | Sep 2015 | B2 |
| 9144875 | Schlesak et al. | Sep 2015 | B2 |
| 9147882 | Hanasaki et al. | Sep 2015 | B2 |
| 9148134 | Shibuya | Sep 2015 | B2 |
| 9148232 | Yamamoto et al. | Sep 2015 | B2 |
| 9149872 | Saur et al. | Oct 2015 | B2 |
| 9149873 | Meyers et al. | Oct 2015 | B2 |
| 9153229 | Xu et al. | Oct 2015 | B2 |
| 9156093 | Meyers | Oct 2015 | B2 |
| 9156153 | Dvorak et al. | Oct 2015 | B2 |
| 9156182 | Moreno | Oct 2015 | B2 |
| 9159376 | Akiyama | Oct 2015 | B2 |
| 9162293 | Meyers | Oct 2015 | B2 |
| 9162349 | Ikuta et al. | Oct 2015 | B2 |
| 9165387 | Gilbert | Oct 2015 | B2 |
| 9166417 | Muramatsu et al. | Oct 2015 | B2 |
| 9166738 | Kaeriyama | Oct 2015 | B2 |
| 9167140 | Nakajima et al. | Oct 2015 | B2 |
| 9168597 | Wiker et al. | Oct 2015 | B2 |
| 9168651 | Hecht et al. | Oct 2015 | B2 |
| 9171595 | Fujiwara | Oct 2015 | B2 |
| 9172436 | Miyauchi et al. | Oct 2015 | B2 |
| 9174552 | Ikeda et al. | Nov 2015 | B2 |
| 9175745 | Saur | Nov 2015 | B2 |
| 9180841 | Suzuki et al. | Nov 2015 | B2 |
| 9181913 | Kellermann | Nov 2015 | B2 |
| 9184633 | Obayashi et al. | Nov 2015 | B2 |
| 9186808 | Hirabayashi et al. | Nov 2015 | B2 |
| 9189094 | Morikawa et al. | Nov 2015 | B2 |
| 9189663 | Goren et al. | Nov 2015 | B2 |
| 9191765 | Totsuka et al. | Nov 2015 | B2 |
| 9193021 | Machida et al. | Nov 2015 | B2 |
| 9193043 | Guenther et al. | Nov 2015 | B2 |
| 9193045 | Saur et al. | Nov 2015 | B2 |
| 9194462 | Blum et al. | Nov 2015 | B2 |
| 9194917 | Brochhaus | Nov 2015 | B2 |
| 9195633 | Enami et al. | Nov 2015 | B2 |
| 9199353 | Ota et al. | Dec 2015 | B2 |
| 9202430 | Tsuchi | Dec 2015 | B2 |
| 9203249 | Noda et al. | Dec 2015 | B2 |
| 9206782 | Chinnadurai et al. | Dec 2015 | B2 |
| 9211620 | Nagy | Dec 2015 | B2 |
| 9211622 | Nagy | Dec 2015 | B2 |
| 9211639 | Hecht et al. | Dec 2015 | B2 |
| 9216490 | Boeck et al. | Dec 2015 | B2 |
| 9216505 | Rejman et al. | Dec 2015 | B2 |
| 9216518 | Frolov | Dec 2015 | B2 |
| 9218924 | Coussins et al. | Dec 2015 | B2 |
| 9221164 | Schneider et al. | Dec 2015 | B2 |
| 9221165 | Wiedner et al. | Dec 2015 | B2 |
| 9221169 | Seidel | Dec 2015 | B2 |
| 9224994 | Ota et al. | Dec 2015 | B2 |
| 9225223 | Bekavac et al. | Dec 2015 | B2 |
| 9227553 | Nordbruch | Jan 2016 | B2 |
| 9231341 | Appel | Jan 2016 | B2 |
| 9232614 | Hiroi | Jan 2016 | B2 |
| 9233424 | Grolimund et al. | Jan 2016 | B2 |
| 9233457 | Wanek et al. | Jan 2016 | B2 |
| 9233460 | Liptak et al. | Jan 2016 | B2 |
| 9236588 | Hanawa et al. | Jan 2016 | B2 |
| 9242353 | Hecht et al. | Jan 2016 | B2 |
| 9242356 | King et al. | Jan 2016 | B2 |
| 9242362 | Abante et al. | Jan 2016 | B2 |
| 9242363 | Moessnang et al. | Jan 2016 | B2 |
| 9243674 | Esenwein | Jan 2016 | B2 |
| D749389 | Aoki et al. | Feb 2016 | S |
| 9248507 | Rohm | Feb 2016 | B2 |
| 9248562 | Bernardi et al. | Feb 2016 | B2 |
| 9248566 | Horiyama et al. | Feb 2016 | B2 |
| 9249716 | Takayanagi | Feb 2016 | B2 |
| 9250861 | Okabayashi | Feb 2016 | B2 |
| 9254562 | Furusawa et al. | Feb 2016 | B2 |
| 9254563 | Yamaguchi et al. | Feb 2016 | B2 |
| 9254580 | Frolov | Feb 2016 | B2 |
| 9256988 | Wenger et al. | Feb 2016 | B2 |
| 9257807 | Betcher et al. | Feb 2016 | B2 |
| 9257865 | Hiuggins et al. | Feb 2016 | B2 |
| 9259831 | Boeck et al. | Feb 2016 | B2 |
| 9259832 | Miyazawa et al. | Feb 2016 | B2 |
| 9261171 | Doering | Feb 2016 | B2 |
| 9262254 | Bertosa et al. | Feb 2016 | B2 |
| 9262997 | Hamada et al. | Feb 2016 | B2 |
| 9266217 | Esenwein | Feb 2016 | B2 |
| 9266503 | Katou | Feb 2016 | B2 |
| 9270195 | Fujino et al. | Feb 2016 | B2 |
| 9272344 | Thomas | Mar 2016 | B2 |
| 9272347 | Holmes et al. | Mar 2016 | B2 |
| 9274465 | Samei et al. | Mar 2016 | B2 |
| 9275256 | Amanuma et al. | Mar 2016 | B2 |
| 9276509 | Kato et al. | Mar 2016 | B2 |
| 9278426 | Numata | Mar 2016 | B2 |
| 9278437 | Rakaczki et al. | Mar 2016 | B2 |
| 9278705 | Murata et al. | Mar 2016 | B2 |
| 9281770 | Wood et al. | Mar 2016 | B2 |
| 9282695 | Goto | Mar 2016 | B2 |
| 9289833 | Schmidt et al. | Mar 2016 | B2 |
| 9290078 | Ota et al. | Mar 2016 | B2 |
| 9296079 | Miwa et al. | Mar 2016 | B2 |
| 9296374 | Yamakado et al. | Mar 2016 | B2 |
| 9302329 | Rohr, Jr. | Apr 2016 | B2 |
| 9302405 | Rubens et al. | Apr 2016 | B2 |
| 9302406 | Kato et al. | Apr 2016 | B2 |
| 9303606 | Moreira Coletto et al. | Apr 2016 | B2 |
| 9308637 | Tsuchiya et al. | Apr 2016 | B2 |
| 9308638 | Kondo et al. | Apr 2016 | B2 |
| 9308916 | Buerkle et al. | Apr 2016 | B2 |
| 9312080 | Boeck et al. | Apr 2016 | B2 |
| 9314908 | Tanimoto et al. | Apr 2016 | B2 |
| 9314914 | Suda et al. | Apr 2016 | B2 |
| 9314916 | Tsuchiya | Apr 2016 | B2 |
| 9318729 | Ogura | Apr 2016 | B2 |
| 9321164 | Onoda et al. | Apr 2016 | B2 |
| 9327377 | Keller-Sornig et al. | May 2016 | B2 |
| 9327424 | Jönsson et al. | May 2016 | B2 |
| 9330465 | Schumacher | May 2016 | B2 |
| 9330858 | Boeck et al. | May 2016 | B2 |
| 9331625 | Stock et al. | May 2016 | B2 |
| 9333638 | Powell et al. | May 2016 | B2 |
| 9333669 | Okouchi et al. | May 2016 | B2 |
| 9337453 | Ogura et al. | May 2016 | B2 |
| 9337677 | Suzuki | May 2016 | B2 |
| 9337763 | Funabashi et al. | May 2016 | B2 |
| 9339878 | Fuchs et al. | May 2016 | B2 |
| 9340148 | Ehlgen et al. | May 2016 | B2 |
| 9340953 | Sakamoto et al. | May 2016 | B2 |
| 9343451 | Funatsu et al. | May 2016 | B2 |
| 9343986 | Kimura et al. | May 2016 | B2 |
| 9345168 | Suzuki et al. | May 2016 | B2 |
| 9346144 | Tan | May 2016 | B2 |
| 9346154 | Roehm | May 2016 | B2 |
| 9346157 | Morioka et al. | May 2016 | B2 |
| 9346356 | Hisatsugu | May 2016 | B2 |
| 9352460 | Steinke et al. | May 2016 | B2 |
| 9358624 | Bantle et al. | Jun 2016 | B2 |
| 9358677 | Kuhnle et al. | Jun 2016 | B2 |
| 9359937 | Ichihashi | Jun 2016 | B2 |
| 9360064 | Nadig et al. | Jun 2016 | B2 |
| 9362724 | Hansom et al. | Jun 2016 | B2 |
| 9364906 | Abe et al. | Jun 2016 | B2 |
| 9364927 | Bohn et al. | Jun 2016 | B2 |
| 9364944 | Aoki | Jun 2016 | B2 |
| 9366299 | Roehm | Jun 2016 | B2 |
| 9367062 | Volpert | Jun 2016 | B2 |
| 9368839 | Schumann et al. | Jun 2016 | B2 |
| 9370860 | Rieger et al. | Jun 2016 | B2 |
| 9373458 | Welke et al. | Jun 2016 | B2 |
| 9375795 | Oberheim | Jun 2016 | B2 |
| 9375832 | Boeck et al. | Jun 2016 | B2 |
| 9379560 | Brandner et al. | Jun 2016 | B2 |
| 9395257 | Li et al. | Jul 2016 | B2 |
| 9537335 | Furui et al. | Jan 2017 | B2 |
| 9713116 | Wible et al. | Jun 2017 | B2 |
| 9746860 | Sakaue et al. | Aug 2017 | B2 |
| 9756402 | Stampfl et al. | Sep 2017 | B2 |
| 9780583 | Furui et al. | Oct 2017 | B2 |
| 9819132 | Peloquin et al. | Nov 2017 | B2 |
| 20010017531 | Sakakibara et al. | Aug 2001 | A1 |
| 20010052416 | Wissmach et al. | Dec 2001 | A1 |
| 20020033267 | Schweizer et al. | Mar 2002 | A1 |
| 20020062991 | Earrant et al. | May 2002 | A1 |
| 20030009262 | Colangelo, II et al. | Jan 2003 | A1 |
| 20030030565 | Sakatani et al. | Feb 2003 | A1 |
| 20030043016 | Kady et al. | Mar 2003 | A1 |
| 20030058101 | Watanabe et al. | Mar 2003 | A1 |
| 20030121677 | Kady et al. | Mar 2003 | A1 |
| 20030062999 | Saleh et al. | Apr 2003 | A1 |
| 20030090239 | Sakakibara | May 2003 | A1 |
| 20040160212 | Mastaler et al. | Aug 2004 | A1 |
| 20040182587 | May et al. | Sep 2004 | A1 |
| 20040186613 | Balling | Sep 2004 | A1 |
| 20050011655 | Crowell et al. | Jan 2005 | A1 |
| 20050035659 | Hahn et al. | Feb 2005 | A1 |
| 20050126821 | Davies | Jun 2005 | A1 |
| 20050197093 | Wiklof et al. | Sep 2005 | A1 |
| 20060009879 | Lynch et al. | Jan 2006 | A1 |
| 20060076385 | Etter et al. | Apr 2006 | A1 |
| 20060087283 | Phillips et al. | Apr 2006 | A1 |
| 20070034394 | Gass et al. | Feb 2007 | A1 |
| 20070224492 | Scott et al. | Sep 2007 | A1 |
| 20070252675 | Lamar | Nov 2007 | A1 |
| 20070276513 | Sudo | Nov 2007 | A1 |
| 20080084334 | Ballew | Apr 2008 | A1 |
| 20080086320 | Ballew | Apr 2008 | A1 |
| 20080086323 | Ballew et al. | Apr 2008 | A1 |
| 20080086349 | Petrie et al. | Apr 2008 | A1 |
| 20080086427 | Petrie | Apr 2008 | A1 |
| 20080086428 | Wallace | Apr 2008 | A1 |
| 20080086497 | Wallace et al. | Apr 2008 | A1 |
| 20080086685 | Janky et al. | Apr 2008 | A1 |
| 20080135272 | Wallgren | Jun 2008 | A1 |
| 20080236220 | Calvet et al. | Oct 2008 | A1 |
| 20080252446 | Dammertz | Oct 2008 | A1 |
| 20080293446 | Rofougaran | Nov 2008 | A1 |
| 20080313452 | Qin et al. | Dec 2008 | A1 |
| 20090108806 | Takano et al. | Apr 2009 | A1 |
| 20090200053 | Scrimshaw et al. | Aug 2009 | A1 |
| 20090250364 | Gerold et al. | Oct 2009 | A1 |
| 20090251330 | Gerold et al. | Oct 2009 | A1 |
| 20090251880 | Anderson | Oct 2009 | A1 |
| 20090254203 | Gerold et al. | Oct 2009 | A1 |
| 20090273436 | Gluck et al. | Nov 2009 | A1 |
| 20100062326 | Konuma | Mar 2010 | A1 |
| 20100096151 | Östling | Apr 2010 | A1 |
| 20100116519 | Gareis | May 2010 | A1 |
| 20100154599 | Gareis | Jun 2010 | A1 |
| 20100176766 | Brandner et al. | Jul 2010 | A1 |
| 20100216415 | Arimura et al. | Aug 2010 | A1 |
| 20100282482 | Austin et al. | Nov 2010 | A1 |
| 20110015764 | Chen et al. | Jan 2011 | A1 |
| 20110056716 | Jönsson et al. | Mar 2011 | A1 |
| 20110067895 | Nobe et al. | Mar 2011 | A1 |
| 20110073343 | Sawano et al. | Mar 2011 | A1 |
| 20110114345 | Schlesak et al. | May 2011 | A1 |
| 20110121782 | Marsh et al. | May 2011 | A1 |
| 20110132155 | Chiapuzzi | Jun 2011 | A1 |
| 20110162858 | Coste | Jul 2011 | A1 |
| 20110193789 | Lin | Aug 2011 | A1 |
| 20110309931 | Rose | Dec 2011 | A1 |
| 20120007748 | Forgues et al. | Jan 2012 | A1 |
| 20120035804 | Roberts | Feb 2012 | A1 |
| 20120111589 | Schmidt et al. | May 2012 | A1 |
| 20120167721 | Fluhrer | Jul 2012 | A1 |
| 20120168189 | Eckert | Jul 2012 | A1 |
| 20120187851 | Huggins et al. | Jul 2012 | A1 |
| 20120199372 | Nishikawa et al. | Aug 2012 | A1 |
| 20120234569 | Lawton et al. | Sep 2012 | A1 |
| 20120238119 | Rejman et al. | Sep 2012 | A1 |
| 20120267134 | Matthias et al. | Oct 2012 | A1 |
| 20120279736 | Tanimoto et al. | Nov 2012 | A1 |
| 20120292070 | Ito et al. | Nov 2012 | A1 |
| 20120302101 | Brotto et al. | Nov 2012 | A1 |
| 20120312570 | Wanek et al. | Dec 2012 | A1 |
| 20120325507 | Fluhrer et al. | Dec 2012 | A1 |
| 20130024245 | Nichols et al. | Jan 2013 | A1 |
| 20130035978 | Richardson et al. | Feb 2013 | A1 |
| 20130062086 | Ito et al. | Mar 2013 | A1 |
| 20130071815 | Hudson et al. | Mar 2013 | A1 |
| 20130076271 | Suda et al. | Mar 2013 | A1 |
| 20130087355 | Oomori et al. | Apr 2013 | A1 |
| 20130109375 | Zeiler et al. | May 2013 | A1 |
| 20130118767 | Cannaliato et al. | May 2013 | A1 |
| 20130126202 | Oomori et al. | May 2013 | A1 |
| 20130133907 | Chen et al. | May 2013 | A1 |
| 20130133911 | Ishikawa et al. | May 2013 | A1 |
| 20130138465 | Kahle et al. | May 2013 | A1 |
| 20130138606 | Kahle et al. | May 2013 | A1 |
| 20130153250 | Eckert | Jun 2013 | A1 |
| 20130154584 | Sakaue et al. | Jun 2013 | A1 |
| 20130187587 | Knight et al. | Jul 2013 | A1 |
| 20130188058 | Nguyen et al. | Jul 2013 | A1 |
| 20130191417 | Petrie et al. | Jul 2013 | A1 |
| 20130193891 | Wood et al. | Aug 2013 | A1 |
| 20130200831 | Nakano et al. | Aug 2013 | A1 |
| 20130204753 | Wallace | Aug 2013 | A1 |
| 20130255980 | Linehan et al. | Oct 2013 | A1 |
| 20130295426 | Halavart et al. | Nov 2013 | A1 |
| 20130304545 | Ballew et al. | Nov 2013 | A1 |
| 20130327552 | Lovelass et al. | Dec 2013 | A1 |
| 20130333910 | Tanimoto et al. | Dec 2013 | A1 |
| 20140006295 | Zeiler et al. | Jan 2014 | A1 |
| 20140008093 | Patel et al. | Jan 2014 | A1 |
| 20140015389 | Vatterott et al. | Jan 2014 | A1 |
| 20140069672 | Mashiko et al. | Mar 2014 | A1 |
| 20140070924 | Wenger et al. | Mar 2014 | A1 |
| 20140107853 | Ashinghurst et al. | Apr 2014 | A1 |
| 20140122143 | Fletcher et al. | May 2014 | A1 |
| 20140149416 | Wallace | May 2014 | A1 |
| 20140151079 | Furui et al. | Jun 2014 | A1 |
| 20140158389 | Ito et al. | Jun 2014 | A1 |
| 20140159640 | Yoshikawa et al. | Jun 2014 | A1 |
| 20140159662 | Furui et al. | Jun 2014 | A1 |
| 20140159919 | Furui et al. | Jun 2014 | A1 |
| 20140159920 | Furui et al. | Jun 2014 | A1 |
| 20140166324 | Puzio et al. | Jun 2014 | A1 |
| 20140184397 | Volpert | Jul 2014 | A1 |
| 20140240125 | Burch et al. | Aug 2014 | A1 |
| 20140266024 | Chinnadurai et al. | Sep 2014 | A1 |
| 20140284070 | Ng et al. | Sep 2014 | A1 |
| 20140292245 | Suzuki et al. | Oct 2014 | A1 |
| 20140316837 | Fosburgh et al. | Oct 2014 | A1 |
| 20140324194 | Larsson et al. | Oct 2014 | A1 |
| 20140326477 | Thorson et al. | Nov 2014 | A1 |
| 20140331829 | King et al. | Nov 2014 | A1 |
| 20140331830 | King et al. | Nov 2014 | A1 |
| 20140334270 | Kusakawa | Nov 2014 | A1 |
| 20140336810 | Li et al. | Nov 2014 | A1 |
| 20140336955 | Li et al. | Nov 2014 | A1 |
| 20140350716 | Fly et al. | Nov 2014 | A1 |
| 20140365259 | Delplace et al. | Dec 2014 | A1 |
| 20140367134 | Phillips et al. | Dec 2014 | A1 |
| 20140379136 | Schlegel et al. | Dec 2014 | A1 |
| 20150000944 | Dusselberg et al. | Jan 2015 | A1 |
| 20150002089 | Rejman et al. | Jan 2015 | A1 |
| 20150042247 | Kusakawa | Feb 2015 | A1 |
| 20150122523 | Yamamoto et al. | May 2015 | A1 |
| 20150122524 | Papp | May 2015 | A1 |
| 20150122526 | Bernardi et al. | May 2015 | A1 |
| 20150127205 | Brochhaus | May 2015 | A1 |
| 20150128429 | Yan et al. | May 2015 | A1 |
| 20150129810 | Tenzer et al. | May 2015 | A1 |
| 20150130330 | Nagy et al. | May 2015 | A1 |
| 20150130413 | Wolf | May 2015 | A1 |
| 20150135306 | Winkler et al. | May 2015 | A1 |
| 20150135541 | Ishikawa et al. | May 2015 | A1 |
| 20150135907 | Hirabayashi et al. | May 2015 | A1 |
| 20150137717 | Werner | May 2015 | A1 |
| 20150137721 | Yamamoto et al. | May 2015 | A1 |
| 20150141159 | Machida | May 2015 | A1 |
| 20150144366 | Machida | May 2015 | A1 |
| 20150144368 | Ishikawa et al. | Jun 2015 | A1 |
| 20150150488 | Saitou et al. | Jun 2015 | A1 |
| 20150151415 | Burger et al. | Jun 2015 | A1 |
| 20150151423 | Tenzer et al. | Jun 2015 | A1 |
| 20150155547 | Ishikawa et al. | Jun 2015 | A1 |
| 20150155597 | Kato | Jun 2015 | A1 |
| 20150158157 | Hirabayashi et al. | Jun 2015 | A1 |
| 20150158160 | Sinzig et al. | Jun 2015 | A1 |
| 20150158170 | Nitsche et al. | Jun 2015 | A1 |
| 20150158198 | Sgarz et al. | Jun 2015 | A1 |
| 20150160362 | Suzuki et al. | Jun 2015 | A1 |
| 20150162646 | Kawase et al. | Jun 2015 | A1 |
| 20150163962 | Padget | Jun 2015 | A1 |
| 20150165633 | Kannan et al. | Jun 2015 | A1 |
| 20150170848 | Eckl et al. | Jun 2015 | A1 |
| 20150171427 | Juretko et al. | Jun 2015 | A1 |
| 20150171654 | Horie et al. | Jun 2015 | A1 |
| 20150171692 | Juretko et al. | Jun 2015 | A1 |
| 20150175146 | Quirant et al. | Jun 2015 | A1 |
| 20150179036 | Heine et al. | Jun 2015 | A1 |
| 20150180307 | Inuzuka | Jun 2015 | A1 |
| 20150183106 | Schnell et al. | Jul 2015 | A1 |
| 20150188332 | Nakano et al. | Jul 2015 | A1 |
| 20150191096 | Becker et al. | Jul 2015 | A1 |
| 20150193924 | Schumacher | Jul 2015 | A1 |
| 20150194646 | Yoshinari et al. | Jul 2015 | A1 |
| 20150194647 | Yoshinari et al. | Jul 2015 | A1 |
| 20150196987 | Hayashi et al. | Jul 2015 | A1 |
| 20150198448 | Sanma et al. | Jul 2015 | A1 |
| 20150208142 | Gladigau et al. | Jul 2015 | A1 |
| 20150209948 | Hecht et al. | Jul 2015 | A1 |
| 20150209950 | Lutz et al. | Jul 2015 | A1 |
| 20150209951 | Lutz et al. | Jul 2015 | A1 |
| 20150213381 | Hagiwara | Jul 2015 | A1 |
| 20150214209 | Funatsu et al. | Jul 2015 | A1 |
| 20150214520 | Nishikawa et al. | Jul 2015 | A1 |
| 20150214857 | Kosuga et al. | Jul 2015 | A1 |
| 20150217422 | Esenwein | Aug 2015 | A1 |
| 20150217807 | Schumacher et al. | Aug 2015 | A1 |
| 20150220953 | Hagiwara et al. | Aug 2015 | A1 |
| 20150222205 | Suda | Aug 2015 | A1 |
| 20150223366 | Horiuchi et al. | Aug 2015 | A1 |
| 20150224588 | Kohl | Aug 2015 | A1 |
| 20150224895 | Morita et al. | Aug 2015 | A1 |
| 20150224988 | Buerkle et al. | Aug 2015 | A1 |
| 20150228940 | Fujisawa | Aug 2015 | A1 |
| 20150228943 | Umemura et al. | Aug 2015 | A1 |
| 20150229011 | Gless | Aug 2015 | A1 |
| 20150229256 | Forstner et al. | Aug 2015 | A1 |
| 20150231974 | Yunoue et al. | Aug 2015 | A1 |
| 20150236532 | Umemura | Aug 2015 | A1 |
| 20150239396 | Gijkokaj et al. | Aug 2015 | A1 |
| 20150239442 | Yamakado et al. | Aug 2015 | A1 |
| 20150245753 | Schuele et al. | Sep 2015 | A1 |
| 20150246435 | Wörz et al. | Sep 2015 | A1 |
| 20150249237 | Naito | Sep 2015 | A1 |
| 20150255773 | Yoshinari et al. | Sep 2015 | A1 |
| 20150256096 | Nishizawa et al. | Sep 2015 | A1 |
| 20150258703 | Steingruber et al. | Sep 2015 | A1 |
| 20150263579 | Sengiku et al. | Sep 2015 | A1 |
| 20150263592 | Kawakami et al. | Sep 2015 | A1 |
| 20150266170 | Weller | Sep 2015 | A1 |
| 20150268858 | Kondo et al. | Sep 2015 | A1 |
| 20150273645 | Steurer | Oct 2015 | A1 |
| 20150274139 | Okada et al. | Oct 2015 | A1 |
| 20150280468 | Müller et al. | Oct 2015 | A1 |
| 20150280476 | Osswald | Oct 2015 | A1 |
| 20150283685 | Kynast et al. | Oct 2015 | A1 |
| 20150283690 | Welte et al. | Oct 2015 | A1 |
| 20150283691 | Rubens et al. | Oct 2015 | A1 |
| 20150283694 | Goto et al. | Oct 2015 | A1 |
| 20150289451 | Koizumi et al. | Oct 2015 | A1 |
| 20150290789 | Ontl et al. | Oct 2015 | A1 |
| 20150290790 | Schomisch et al. | Oct 2015 | A1 |
| 20150290791 | Takahashi et al. | Oct 2015 | A1 |
| 20150293745 | Suzuki et al. | Oct 2015 | A1 |
| 20150298308 | Kato | Oct 2015 | A1 |
| 20150298311 | Meixner et al. | Oct 2015 | A1 |
| 20150298354 | Greitmann et al. | Oct 2015 | A1 |
| 20150298355 | Ohlendorf | Oct 2015 | A1 |
| 20150300614 | Tamura et al. | Oct 2015 | A1 |
| 20150302749 | Kitagawa | Oct 2015 | A1 |
| 20150303417 | Koeder et al. | Oct 2015 | A1 |
| 20150303458 | Guo et al. | Oct 2015 | A1 |
| 20150303848 | Beck | Oct 2015 | A1 |
| 20150303916 | Hernandez Blasco et al. | Oct 2015 | A1 |
| 20150305188 | Maeda et al. | Oct 2015 | A1 |
| 20150309640 | Vuckovic | Oct 2015 | A1 |
| 20150310258 | Omi | Oct 2015 | A1 |
| 20150311730 | Aradachi et al. | Oct 2015 | A1 |
| 20150316585 | Forstner | Nov 2015 | A1 |
| 20150318720 | Aradachi et al. | Nov 2015 | A1 |
| 20150318732 | Heine et al. | Nov 2015 | A1 |
| 20150318733 | Stock et al. | Nov 2015 | A1 |
| 20150318734 | Lohr et al. | Nov 2015 | A1 |
| 20150321266 | Sattler et al. | Nov 2015 | A1 |
| 20150321305 | Saur et al. | Nov 2015 | A1 |
| 20150321381 | Engelfried et al. | Nov 2015 | A1 |
| 20150324566 | Miura et al. | Nov 2015 | A1 |
| 20150324650 | Langenberg | Nov 2015 | A1 |
| 20150325826 | Verhaag et al. | Nov 2015 | A1 |
| 20150326098 | Hirata | Nov 2015 | A1 |
| 20150328694 | Hoop | Nov 2015 | A1 |
| 20150328695 | Hoop | Nov 2015 | A1 |
| 20150328701 | Kauz et al. | Nov 2015 | A1 |
| 20150328742 | Scuele et al. | Nov 2015 | A1 |
| 20150328762 | Padget et al. | Nov 2015 | A1 |
| 20150328763 | Ito et al. | Nov 2015 | A1 |
| 20150328764 | Yoshikane et al. | Nov 2015 | A1 |
| 20150328765 | Schubert | Nov 2015 | A1 |
| 20150328796 | Okouchi et al. | Nov 2015 | A1 |
| 20150332839 | Stock et al. | Nov 2015 | A1 |
| 20150333301 | Ota et al. | Nov 2015 | A1 |
| 20150333559 | Lohr et al. | Nov 2015 | A1 |
| 20150333664 | Bantle | Nov 2015 | A1 |
| 20150337521 | Sakamoto et al. | Nov 2015 | A1 |
| 20150340153 | Lohr et al. | Nov 2015 | A1 |
| 20150340894 | Horie et al. | Nov 2015 | A1 |
| 20150340921 | Suda et al. | Nov 2015 | A1 |
| 20150343539 | Hoop | Dec 2015 | A1 |
| 20150343617 | Kondo et al. | Dec 2015 | A1 |
| 20150345460 | Eichler et al. | Dec 2015 | A1 |
| 20150346914 | Ebi | Dec 2015 | A1 |
| 20150348696 | Lohr et al. | Dec 2015 | A1 |
| 20150349576 | Krupezevic et al. | Dec 2015 | A1 |
| 20150349577 | Breitenbach et al. | Dec 2015 | A1 |
| 20150349600 | Huber et al. | Dec 2015 | A1 |
| 20150349695 | Hosokawa et al. | Dec 2015 | A1 |
| 20150353064 | Spoeri et al. | Dec 2015 | A1 |
| 20150353889 | Wakao et al. | Dec 2015 | A1 |
| 20150355280 | Iwata | Dec 2015 | A1 |
| 20150357632 | Nishimura et al. | Dec 2015 | A1 |
| 20150357683 | Lohr et al. | Dec 2015 | A1 |
| 20150364099 | Shibuya | Dec 2015 | A1 |
| 20150364955 | Aumann | Dec 2015 | A1 |
| 20150366133 | Nojiri et al. | Dec 2015 | A1 |
| 20150367490 | Satou et al. | Dec 2015 | A1 |
| 20150367495 | Takeda | Dec 2015 | A1 |
| 20150367497 | Ito et al. | Dec 2015 | A1 |
| 20150367823 | Baenzler et al. | Dec 2015 | A1 |
| 20150372633 | Machida et al. | Dec 2015 | A1 |
| 20150375388 | Ullrich | Dec 2015 | A1 |
| 20150375416 | Haneda et al. | Dec 2015 | A1 |
| 20150379897 | Nadig et al. | Dec 2015 | A1 |
| 20150380945 | Krupezevic et al. | Dec 2015 | A1 |
| 20160006005 | Sakakibara | Jan 2016 | A1 |
| 20160006542 | Kaeriyama | Jan 2016 | A1 |
| 20160008893 | Tussing | Jan 2016 | A9 |
| 20160013514 | Yoshida et al. | Jan 2016 | A1 |
| 20160016240 | Koegel | Jan 2016 | A1 |
| 20160016241 | Taylor et al. | Jan 2016 | A1 |
| 20160020492 | Azami et al. | Jan 2016 | A1 |
| 20160020494 | Kamizori et al. | Jan 2016 | A1 |
| 20160023663 | Kajiwara | Jan 2016 | A1 |
| 20160027502 | Fujiwara | Jan 2016 | A1 |
| 20160028118 | Shimanuki et al. | Jan 2016 | A1 |
| 20160028123 | Kawasaki et al. | Jan 2016 | A1 |
| 20160031021 | Marinov et al. | Feb 2016 | A1 |
| 20160031212 | Kida | Feb 2016 | A1 |
| 20160043714 | Yanagigawa | Feb 2016 | A1 |
| 20160046011 | Ogle et al. | Feb 2016 | A1 |
| 20160046035 | Laghate et al. | Feb 2016 | A1 |
| 20160048122 | Lukosz et al. | Feb 2016 | A1 |
| 20160052119 | Yamada et al. | Feb 2016 | A1 |
| 20160056507 | Eberle | Feb 2016 | A1 |
| 20160065030 | Fujimoto | Mar 2016 | A1 |
| 20160067800 | Frolov et al. | Mar 2016 | A1 |
| 20160067802 | Frolov | Mar 2016 | A1 |
| 20160067859 | Rejman et al. | Mar 2016 | A1 |
| 20160067880 | Frolov | Mar 2016 | A1 |
| 20160072106 | Baumgartner et al. | Mar 2016 | A1 |
| 20160075007 | Kutsuna et al. | Mar 2016 | A1 |
| 20160076603 | Granacher | Mar 2016 | A1 |
| 20160079801 | Zhang et al. | Mar 2016 | A1 |
| 20160089757 | Wirnitzer et al. | Mar 2016 | A1 |
| 20160089810 | Padmanabhan et al. | Mar 2016 | A1 |
| 20160095487 | Koura et al. | Apr 2016 | A1 |
| 20160099606 | Zhang et al. | Apr 2016 | A1 |
| 20160101494 | Nagy | Apr 2016 | A1 |
| 20160101512 | Hecht et al. | Apr 2016 | A1 |
| 20160102762 | Brennenstuhl et al. | Apr 2016 | A1 |
| 20160107297 | Ishikawa et al. | Apr 2016 | A1 |
| 20160109896 | Shiraishi et al. | Apr 2016 | A9 |
| 20160114472 | Holubarsch et al. | Apr 2016 | A1 |
| 20160121466 | Kiyohara et al. | May 2016 | A1 |
| 20160121467 | Ng et al. | May 2016 | A1 |
| 20160121473 | Brennenstuhl et al. | May 2016 | A1 |
| 20160121477 | Zhang | May 2016 | A1 |
| 20160121513 | Mahoney | May 2016 | A1 |
| 20160126877 | Endoh | May 2016 | A1 |
| 20160129576 | Nishikawa et al. | May 2016 | A1 |
| 20160129582 | Ullrich | May 2016 | A1 |
| 20160136801 | Furusawa et al. | May 2016 | A1 |
| 20160144685 | Ochiai et al. | May 2016 | A1 |
| 20160144861 | Cao et al. | May 2016 | A1 |
| 20160146209 | Sakai | May 2016 | A1 |
| 20160149512 | Nakatsu et al. | May 2016 | A1 |
| 20160151845 | Yamamoto et al. | Jun 2016 | A1 |
| 20160151846 | Suzuki | Jun 2016 | A1 |
| 20160151905 | Tada et al. | Jun 2016 | A1 |
| 20160158929 | Brennenstuhl et al. | Jun 2016 | A1 |
| 20160162708 | Amanuma et al. | Jun 2016 | A1 |
| 20160167142 | Talesky et al. | Jun 2016 | A1 |
| 20160169365 | Hecht et al. | Jun 2016 | A1 |
| 20160170413 | Mueller | Jun 2016 | A1 |
| 20160171788 | Wenger et al. | Jun 2016 | A1 |
| 20160172641 | Zahn | Jun 2016 | A1 |
| 20160172722 | Rejman et al. | Jun 2016 | A1 |
| 20160173496 | Saka et al. | Jun 2016 | A1 |
| 20160175895 | Suzuki | Jun 2016 | A1 |
| 20160176064 | Okouchi et al. | Jun 2016 | A1 |
| 20160178398 | Krapf et al. | Jun 2016 | A1 |
| 20160181613 | Yuge et al. | Jun 2016 | A1 |
| 20160184948 | Padget et al. | Jun 2016 | A1 |
| 20160184952 | Kabza et al. | Jun 2016 | A1 |
| 20160184956 | Klabunde et al. | Jun 2016 | A1 |
| 20160184957 | Rubens | Jun 2016 | A1 |
| 20160184984 | Dresen et al. | Jun 2016 | A1 |
| 20160185003 | Padget | Jun 2016 | A1 |
| 20160185006 | Padget | Jun 2016 | A1 |
| 20160185167 | White et al. | Jun 2016 | A1 |
| 20160190531 | Neuberger et al. | Jun 2016 | A1 |
| 20160190858 | Zhang et al. | Jun 2016 | A1 |
| 20160273708 | Voong et al. | Sep 2016 | A1 |
| 20160311040 | Koegel | Oct 2016 | A1 |
| 20160311094 | Mergener et al. | Oct 2016 | A1 |
| 20160313868 | Weng et al. | Oct 2016 | A1 |
| 20160318109 | Koegel | Nov 2016 | A1 |
| 20160318204 | Truesdale et al. | Nov 2016 | A1 |
| 20160332244 | Koegel | Nov 2016 | A1 |
| 20160375570 | Boeck et al. | Dec 2016 | A1 |
| 20170008159 | Boeck et al. | Jan 2017 | A1 |
| 20170051697 | Campbell | Feb 2017 | A1 |
| 20170100790 | Rubens et al. | Apr 2017 | A1 |
| 20180054032 | Peloquin et al. | Feb 2018 | A1 |
| Number | Date | Country |
|---|---|---|
| 3803357 | Aug 1989 | DE |
| 19904776 | Aug 2000 | DE |
| 19961374 | Jun 2001 | DE |
| 10029132 | Jan 2002 | DE |
| 10029138 | Jan 2002 | DE |
| 10309703 | Sep 2004 | DE |
| 202006014606 | Jan 2007 | DE |
| 1151821 | Nov 2001 | EP |
| 2147750 | Jan 2010 | EP |
| 2894505 | Jun 2007 | FR |
| H10151578 | Jun 1998 | JP |
| 2000176850 | Jun 2000 | JP |
| 2002260611 | Sep 2002 | JP |
| 2002358079 | Dec 2002 | JP |
| 4359018 | Sep 2003 | JP |
| 2004072563 | Mar 2004 | JP |
| 2004322262 | Nov 2004 | JP |
| 2005278375 | Oct 2005 | JP |
| 2006123080 | May 2006 | JP |
| 2006352559 | Dec 2006 | JP |
| 2009103073 | May 2009 | JP |
| 2010243429 | Oct 2010 | JP |
| 2011031313 | Feb 2011 | JP |
| WO97023986 | Jul 1997 | WO |
| WO02030624 | Apr 2002 | WO |
| WO2004003695 | Jan 2004 | WO |
| WO2004028749 | Apr 2004 | WO |
| WO2007090258 | Aug 2007 | WO |
| WO2012132040 | Oct 2012 | WO |
| WO2013116303 | Aug 2013 | WO |
| WO2015195615 | Dec 2015 | WO |
| WO2016085862 | Jun 2016 | WO |
| WO2016085910 | Jun 2016 | WO |
| WO2016089764 | Jun 2016 | WO |
| WO2016094532 | Jun 2016 | WO |
| Entry |
|---|
| International Search Report and Written Opinion for Application No. PCT/2014/061651 dated Jan. 27, 2015 (13 pages). |
| European Patent Office Search Report for Application No. 17152521.5 dated May 30, 2017 (7 pages). |
| United States Patent Office Action for U.S. Appl. No. 15/030,756 dated Nov. 30, 2017, 17 pages. |
| United States Patent Office Action for U.S. Appl. No. 15/868,116 dated Mar. 22, 2018, 19 pages. |
| United States Patent Office Action for U.S. Appl. No. 15/833,356 dated Apr. 2, 2018, 11 pages. |
| Number | Date | Country | |
|---|---|---|---|
| 20190143495 A1 | May 2019 | US |
| Number | Date | Country | |
|---|---|---|---|
| 61893765 | Oct 2013 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 15833356 | Dec 2017 | US |
| Child | 16246017 | US | |
| Parent | 15030756 | US | |
| Child | 15833356 | US |
