The present invention relates to power tools, such as hand-held hydraulic power tools, that communicate with an external device.
Hydraulic crimpers and cutters are different types of hydraulic power tools for performing work (e.g., crimping or cutting) on a workpiece. In such tools, a hydraulic pump is utilized for pressurizing hydraulic fluid and transferring it to a cylinder in the tool, causing an extensible piston to be displaced. The piston exerts a force on the head of the power tool, which may include opposed jaws with crimping or cutting features, depending upon the particular configuration of the power tool. In this case, the force exerted by the piston may be used for closing the jaws to perform work on a workpiece.
Embodiments of the invention relate to a power tool (e.g., a hydraulic crimper or cutter) that captures tool operational data and exports the captured data to an external device, such as a smart phone, and to a remote server. In some instances, the tool operational data includes one or more data curves of pressure versus time, current versus time, motor speed versus time, and force versus time, which are captured over the course of the tool action (e.g., a cutting or a crimping action). The captured tool operational data may be monitored and analyzed by the tool, external device, and/or server to confirm that the tool is operating correctly before performing a tool action (e.g., a crimp or a cut), to provide early notification of tool performance degradation, to assess whether the tool action reached full pressure, and/or to assess whether the action was acceptable based on curve data.
One embodiment of the invention provides a method of operating a hydraulic power tool. The method includes performing an operation by a hydraulic drive of the hydraulic power tool, detecting, with a sensor, an operational parameter of the hydraulic drive during the operation, and storing a plurality of data points based on the operational parameter detected during the operation. The method also includes sending, via a transceiver on the hydraulic power tool, the plurality of data points to an external device, displaying, on a display screen of the external device, an expected data point for the operational parameter, and displaying, on the display screen of the external device, an actual data curve based on the plurality of data points. The actual data curve is displayed overlaid on the expected data point.
Another embodiment of the invention provides a power tool system including a hydraulic power tool and an external device. The hydraulic power tool includes a hydraulic drive, a sensor, and a first electronic processor. The hydraulic drive includes a pump and a motor configured to drive the pump. The sensor is configured to detect an operational parameter of the hydraulic drive during an operation by the hydraulic drive. The first electronic processor is configured to store a plurality of data points based on the operational parameter detected during the operation, and send, via a transceiver on the hydraulic power tool, the plurality of data points to the external device. The external device includes a display screen and a second electronic processor. The second electronic processor is coupled to the display screen and is configured to receive the plurality of data points from the hydraulic power tool, control the display screen to display an expected data point for the operational parameter, and control the display screen to display an actual data curve based on the plurality of data points. The actual data curve is displayed overlaid on the expected data point.
In another embodiment of the invention, a method of operating a hydraulic power tool is provided. The method includes performing an operation by a hydraulic drive of the hydraulic power tool and detecting, with a sensor, an operational parameter of the hydraulic drive during the operation. The method further includes comparing, with an electronic processor, the operational parameter to a threshold to determine that the operation of the hydraulic power tool was successful when the operational parameter exceeds the threshold. The method also includes providing an indication that the operation of the hydraulic power tool was successful based on the determination.
Other features and aspects of the invention will become apparent by consideration of the following 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.
Referring to
With reference to
The pawls 52, 56 are pivotally coupled to the body 48 and extend and retract from the body 48 in response to rotation of the input shaft 50. The pawls 52 extend when the input shaft 50 is driven in a clockwise direction from the frame of reference of
Prior to initiating a crimping operation, the return valve 34 is in an open position shown in
The pressure in the piston cylinder 26 is sensed by a pressure sensor 68 (
The speed of the motor 12 is sensed by a speed sensor (see, e.g. Hall sensors 114 of
The electric current flow through the motor 12 is sensed by an ammeter (see, e.g., current sensor 112 of
At this time when the return valve 34 is in an open position, the piston 30 is biased toward the retracted position, shown in
The valve actuator 46 will continue to co-rotate with the input shaft 50 after the return valve 34 reaches the closed position; however, a sufficient gap is created between the pawls 56 and the projection 64 such that they will not come into contact during subsequent rotations of the input shaft 50. The pump 14 draws hydraulic fluid from the reservoir and discharges it under pressure to the piston cylinder 26, causing the piston 30 to extend against the bias of the spring 70. The extension or contraction motion of the piston 30 in a cycle of reciprocation is a stroke. The time the piston takes to extend or contract is the stroke time. The closed return valve 34 prevents the pressurized fluid in the piston cylinder 26 and the return passageway 42 from returning to the reservoir. In the illustrated embodiment of the crimper 10, the piston 30 acts on the jaws 32 as it extends, thereby pivoting the jaws 32 to a closed position. The pressure in the piston cylinder 26, the speed of the motor 12, and the electric current flow through the motor varies based on different positions of the jaws, the position of the jaws in relation to the workpiece, the die used by the crimper head 72, and/or the material of the workpiece. The workpiece provides a resistance against the jaws that increases the force against the jaws. For example, as a crimp is made on the workpiece, the pressure in the piston cylinder 26 increases. Alternatively, in different hydraulic tools in which the auto return valve assembly 18 and valve actuator 46 are incorporated, the piston 30 may act on different portions of the tool for performing work on a workpiece.
When a pressure in excess of a predetermined pressure threshold is detected in the piston cylinder 26 (e.g., by a pressure sensor 68;
The extension and retraction of the piston 30 in the cylinder 26 is referred to as a pressure cycle (or a cycle). Completion of a full pressure cycle occurs when the pressure detected by the pressure sensor 68 exceeds the predetermined pressure threshold. Detection of a full pressure cycle can provide one indication that a satisfactory crimp was performed. Full pressure results in a full output force that causes the piston to push forward (or extend), which in turn causes the jaws 32 to close around a workpiece. If a proper jaw is installed in the hydraulic power tool and proper dies have been used on the proper connector, the dies within jaws 32 close the appropriate distance around the workpiece and a normal crimp is made.
Each type of die (e.g., size and shape) for a particular hydraulic power tool along with the type of workpiece material (e.g., malleable metal) can have different piston cylinder pressure, motor speed, motor current, and other characteristics over the time the crimp is being performed (i.e., the crimper head 72 is closing and opening). These characteristics (e.g., piston cylinder pressure, motor speed, or motor current) are used to monitor and analyze the activity of the hydraulic power tool. For instance, monitored characteristics are compared with the expected characteristics of good crimps for a particular die and material to determine if the crimp is acceptable and if hydraulic power tool is operating properly, which is explained below in greater detail.
As also shown in
The indicators 116 are also coupled to the electronic processor 100 and receive control signals from the electronic processor 100 to turn on and off or otherwise convey information based on different states of the crimper 10. The indicators 116 include, for example, one or more light-emitting diodes (LEDs), or a display screen. The indicators 116 can be configured to display conditions of, or information associated with, the crimper 10. In addition or in place of visual indicators, the indicators 116 may also include speaker or vibratory elements to convey information to a user through audible or tactile outputs.
As described above, the electronic processor 100 is electrically and/or communicatively connected to a variety of modules or components of the crimper 10. In some embodiments, the electronic processor 100 includes a plurality of electrical and electronic components that provide power, operational control, and protection to the components and modules within the electronic processor 100 and/or crimper 10. For example, the electronic processor 100 includes, among other things, a controller 130 (e.g., a microprocessor, a microcontroller, or another suitable programmable device), a memory 132, input units 134, and output units 136. The controller 130 (herein, controller 130) includes, among other things, a control unit 140, an arithmetic logic unit (“ALU”) 142, and a plurality of registers 144 (shown as a group of registers in
The memory 132 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 controller 130 is connected to the memory 132 and executes software instructions that are capable of being stored in a RAM of the memory 132 (e.g., during execution), a ROM of the memory 132 (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 crimper 10 can be stored in the memory 132 of the electronic processor 100. The software includes, for example, firmware, one or more applications, program data, filters, rules, one or more program modules, and other executable instructions. The electronic processor 100 is configured to retrieve from memory and execute, among other things, instructions related to the control processes and methods described herein. The electronic processor 100 is also configured to store crimper information on the memory 132 including operational data, information identifying the type of tool, a unique identifier for the particular tool, and other information relevant to operating or maintaining the crimper 10. The tool usage information may be captured or inferred from data output by the sensors 110.
As shown in
In the illustrated embodiment, the wireless communication controller 122 is a Bluetooth® controller. The Bluetooth® controller communicates with the external device 164 employing the Bluetooth® protocol. Therefore, in the illustrated embodiment, the external device 164 and the crimper 10 are within a communication range (i.e., in proximity) of each other while they exchange data. In other embodiments, the wireless communication controller 122 communicates using other protocols (e.g., Wi-Fi, cellular protocols, a proprietary protocol, etc.) over different type of wireless networks. For example, the wireless communication controller 122 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 controller 122 may be encrypted to protect the data exchanged between the crimper 10 and the external device/network 164 from third parties.
The wireless communication controller 122 is configured to receive data from the electronic processor 100 and relay the information to the external device 164 via the antenna and transceiver 154. In a similar manner, the wireless communication controller 122 is configured to receive information (e.g., configuration and programming information) from the external device 164 via the antenna and transceiver 154 and relay the information to the electronic processor 100.
The RTC 160 increments and keeps time independently of the other power tool components. The RTC 160 receives power from the battery pack 104 when the battery pack 104 is connected to the crimper 10 and receives power from the back-up power source 124 when the battery pack 104 is not connected to the crimper 10. Having the RTC 160 as an independently powered clock enables time stamping of operational data (stored in memory 132 for later export) and a security feature whereby a lockout time is set by a user (e.g., via the external device 164) and the tool is locked-out when the time of the RTC 160 exceeds the set lockout time.
The processor 158 for the wireless communication controller 122 switches between operating in a connected (e.g., full power) state and operating in an advertisement state. In the illustrated embodiment, the wireless communication controller 122 switches between operating in the connected state and the advertisement state based on whether the battery pack 104 is connected to the crimper 10 and whether the battery pack 104 holds sufficient power to operate the wireless communication controller 122 in connected state. When the battery pack 104 is connected to the crimper 10 and holds sufficient charge, the wireless communication controller 122 is powered by the battery pack 104 and operates in the connected state. When the battery pack 104 is not connected to the crimper 10, the wireless communication controller 122 receives power from the back-up power source 124 and the crimper 10 operates in the advertisement state.
When the wireless communication controller 122 operates in the advertisement state, the crimper 10 identifies itself to the external device 164, but data exchange between the crimper 10 and the external device 164 is limited to select information. In other words, in the advertisement state, the wireless communication controller 122 outputs an advertisement message to the external device 164. The advertisement message includes identification information regarding the tool identity, remaining capacity of the back-up power source 124, and other limited amount of crimper information. The advertisement message also identifies the product as being from a particular manufacturer or brand via a unique binary identification UBID identifying the type of power tool and uniquely identifying the particular power tool. Thus, even when operating in the advertisement state, the external device 164 can identify the crimper 10 and determine that the crimper 10 is within a communication range of the external device 164 (e.g., locate the crimper), but further data between the external device 164 and the crimper 10 is not exchanged.
When the wireless communication controller 122 operates in the connected state, full wireless communication between the crimper 10 and the external device 164 is enabled. In the connected state, the wireless communication controller 122 obtains and exports crimper usage data to the external device 164 and receives configuration data from the external device 164.
In the illustrated embodiment, from the frame of reference of
In other embodiments, the components of the communication control board 178 are located on the control board 184, and the communication control board 178 is not included as a separate board in the crimper 10. In further embodiments, the communication control board 178 is located in other positions within the crimper 10, such as near the trigger switch 108, above the motor 12, or behind the motor 12 on a side having the cooling fan 188. In such further embodiments, a further projection of the housing 172 may be provided to accommodate the communication control board 178.
With reference to
With reference to
As discussed in greater detail below, the hydraulic power tool (e.g., crimper 10 and cutter 210) also includes communication interface and/or circuitry (e.g., wireless communication controller 122) that communicates with external devices (e.g., external device 164) and interfaces with the electronic control and monitoring circuitry (e.g., electronic processor 100). The electronic control and monitoring circuitry can monitor and log various parameters (e.g., piston cylinder pressure, motor speed, or motor current) of the hydraulic power tool sensed by sensor to verify and confirm that the tool is operating correctly before performing a crimp or a cut. The various parameters also provide early notification if tool performance is degrading. The various parameters of the hydraulic power tool can be provided to external devices via the communication interface.
More specifically, the power tool 302 can monitor, log, and/or communicate various tool parameters that can be used for confirmation of correct tool performance, detection of a malfunctioning tool, and determination of a need or desire for service. Taking, for example, the crimper 10 or cutter 210 as the power tool 302, the various tool parameters detected, determined, and/or captured by the electronic processor 100 and output to the external device 164 can include a no load stroke time (i.e., stroke time of the tool 302 when the tool does not act on a workpiece), loaded stroke time (i.e., stroke time of the tool 302 when the tool does act on a workpiece, a time (e.g., a number of seconds) that the power tool 202 is on, a number of overloads (i.e., a number of times the tool 202 exceeded the pressure rating for the die, the jaws 32, and/or the tool 202), a total number of cycles performed by the tool, a number of cycles performed by the tool since a reset and/or since a last data export, a number of full pressure cycles (e.g., number of acceptable crimps performed by the tool 202), a number of remaining service cycles (i.e., a number of cycles before the tool 202 should be serviced, recalibrated, repaired, or replaced), a number of transmissions sent to the external device 208, a number of transmissions received from the external device 208, a number of errors generated in the transmissions sent to the external device 208, a number of errors generated in the transmissions received from the external device 208, a code violation resulting in a master control unit (MCU) reset, a short in the power circuitry (e.g., a metal-oxide-semiconductor field-effect transistor (MOSFET) short), a hot thermal overload condition (i.e., a prolonged electric current exceeding a full-loaded threshold that can lead to excessive heating and deterioration of the winding insulation until an electrical fault occurs), a cold thermal overload (i.e., a cyclic or in-rush electric current exceeding a zero load threshold that can also lead to excessive heating and deterioration of the winding insulation until an electrical fault occurs), a motor stall condition (i.e., a locked or non-moving rotor with an electrical current flowing through the windings), a bad Hall sensor, a non-maskable interrupt (NMI) hardware MCU Reset (e.g., of the electronic processor 100), an over-discharge condition of the battery pack 104, an overcurrent condition of the battery pack 104, a battery dead condition at trigger pull, a tool FETing condition, gate drive refresh enabled indication, thermal and stall overload condition, a malfunctioning pressure sensor condition for the pressure sensor 68, trigger pulled at tool sleep condition, Hall sensor error occurrence condition for one of the Hall sensors 114, heat sink temperature histogram data, MOSFET junction temperature histogram data, peak current histogram data (from current sensor 112), average current histogram data (from current sensor 112), and the number of Hall errors indication.
Using the external device 164, a user can access the tool parameters obtained by the power tool 302. With the tool parameters (i.e., tool operational data), a user can determine how the power tool device 302 has been used (e.g., crimps performed), 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 164 can also transmit data to the power tool device 302 for power tool configuration, firmware updates, or to send commands. The external device 164 also allows a user to set operational parameters, safety parameters, select dies used, select tool modes, and the like for the power tool 302.
The external device 164 may be, for example, a smart phone (as illustrated), a laptop computer, a tablet computer, a personal digital assistant (PDA), or another electronic device capable of communicating wirelessly with the power tool device 302 and providing a user interface. The external device 164 provides the user interface and allows a user to access and interact with the power tool device 302. The external device 164 can receive user inputs to determine operational parameters, enable or disable features, and the like. The user interface of the external device 164 provides an easy-to-use interface for the user to control and customize operation of the power tool device 302. The external device 164, therefore, grants the user access to the tool operational data of the power tool device 302, and provides a user interface such that the user can interact with the controller of the power tool device 302.
In addition, as shown in
Also stored in the memory 232 is tool operational data 322, which includes the tool operational data noted above such as information regarding the usage of the crimper 10 (e.g., obtained via the sensors 110), information regarding the maintenance of the crimper 10 (e.g., last service date), and power tool trigger event information (e.g., whether and when the trigger is depressed and the amount of depression).
The memory 232 further includes die and application data 324, which specifies one or more of the type of die attached to the body 1, the workpiece size, the workpiece shape, the workpiece material, and the application type (e.g., electrical or plumbing). The memory 232 also includes expected curve data 326, which is described in more detail below. The die and application data 324 may be communicated to and stored in the memory 232 by a user via the external device 164.
The external device 164 includes a memory 330 storing core application software 332, tool interfaces 334, tool data 336 including received tool identifiers 338 and received tool operational data 340, and the expected curve data 326. The external device further includes an electronic processor 342, a touch screen display 344, and an external wireless communication controller 346. The electronic processor 342 and memory 330 may be part of a controller having similar components as electronic processor 100. The touch screen display 344 allows the external device 164 to output visual data to a user and receive user inputs. Although not illustrated, the external device 164 may include further user input devices (e.g., buttons, dials, toggle switches, and a microphone for voice control) and further user outputs (e.g., speakers and tactile feedback elements). Additionally, in some instances, the external device 164 has a display without touch screen input capability and receives user input via other input devices, such as buttons, dials, and toggle switches. The external device 164 communicates wirelessly with the wireless communication controller 122 via the external wireless communication controller 346, e.g., using a Bluetooth® or Wi-Fi® protocol. The external wireless communication controller 346 further communicates with the network 314. In some instances, the external wireless communication controller 346 includes two separate wireless communication controllers, one for communicating with the wireless communication controller 122 (e.g., using Bluetooth® or Wi-Fi® communications) and one for communicating with the network 314 (e.g., using Wi-Fi or cellular communications).
The server 312 includes a processor 350 that communicates with the external device 164 over the network 314 using a network interface 352. The communication link between the network interface 352, the network 314, and the external wireless communication controller 346 may include various wired and wireless communication pathways, various network components, and various communication protocols. The server 312 further includes a memory 354 including the expected curve data 326 and tool data 358.
Returning to the external device 164, the core application software 332 is executed by the electronic processor 342 to generate a graphical user interface (GUI) on the touch screen display 344 enabling the user to interact with the crimper 10 and server 312. In some embodiments, a user may access a repository of software applications (e.g., an “app store” or “app marketplace”) using the external device 164 to locate and download the core application software 332, which may be referred to as an “app.” The tool interfaces 334 may be bundled for downloading with the core application software 332. In some embodiments, the app is obtained using other techniques, such as downloading from a website using a web browser on the external device 164.
The advertising tools 364 may be in either an advertising state or a connectable state, depending on whether a charged power tool battery pack 104 is coupled to the respective tool. More particularly, when a charged power tool battery pack 104 is coupled to a power tool 302, the power tool 302 is in the connectable state and has essentially full communication capabilities. In contrast, when no battery pack or a discharged battery pack 104 is coupled to the power tool 302, the power tool 302 is in the advertising state and is generally limited to broadcasting an advertisement message that includes its UBID, an indication that a charged power tool battery pack 104 is not present, and the state of charge of the back-up power source 124. In some embodiments, further information is provided by the power tool 302 to the external device 164 in the advertising state, although this additional data transmission may increase power usage and reduce the life of the back-up power source 124.
The external device 164 provides a visual state indication 368 in the identified tool list 366 of whether an advertising tool 364 is in the connectable state or the advertising state. For instance, the advertising tools 364 that are in a connectable state are shown normally with full color and boldness, while the advertising tools 364 in the advertising state are shown grayed-out. The external device 164 is operable to pair with advertising tools 364 that are in the connectable state, but not those advertising tools 364 that are in the advertising state. When one of the advertising tools 364 in the connectable state is paired with the external device 164, the tool is in the connected state.
The UBID received from the advertising tools 364 is used by the external device 164 to identify the tool type of each advertising tool 364. The external device 164 displays the tool type for example, by catalog number (e.g., “2757-20” and “7206-20”) or in another form or language (e.g., “impact driver” or “circular saw”). Additionally, UBIDs received from advertising tools 364 in response to a scan are used to obtain further information about the tools, if available. For instance, the UBID is sent to the server 312 and used as an index or search term for a database of tool information that is part of the tool data 358. For instance, the database may store and respond to the external device 164 with the ASCII nickname (e.g., “Steve's Crimper”), other tool identifiers, and an icon. In some instances, this further information is available as part of the tool data 336 of the external device 164.
From the nearby devices screen 360, a user can select one of the advertising tools 364 from the identified tool list 366 to communicatively pair with the selected advertising tool 364. Each type of power tool 302 with which the external device 164 can communicate includes an associated tool graphical user interface (tool interface) stored in the tool interfaces 334. Once a communicative pairing occurs, the core application software 332 accesses the tool interfaces 334 (e.g., using the UBID) to obtain the applicable tool interface for the type of tool that is paired. The touch screen display 344 then shows the applicable tool interface. A tool interface includes a series of screens enabling a user to obtain and display tool operational data, configure the tool, or both. While some screens and options of a tool interface are common to multiple tool interfaces of different tool types, generally, each tool interface includes screens and options particular to the associated type of tool.
The home screen 370 also provides some overview information regarding the crimper 10. In particular, the home screen 370 includes a crimper data overview window 380. As shown in
When initially paired with the crimper 10, the data displayed in the window 380 may be obtained from the tool data 358 of the server 312 or from the tool operational data 340 of the external device 164. Upon the external device 164 receiving a user selection of the sync tool data input 374, the external device 164 requests the crimper 10 to transmit the tool operational data 322 to the external device 164. Upon receipt of the tool operational data 322, the window 380 is updated with the received data. In some embodiments, the crimper 10 sends the tool operational data 322 to the external device 164 automatically upon pairing (i.e., independent of the user selecting the sync tool data input 374). The window 380 also lists the last sync date, which is updated when new tool operational data is received from the crimper 10.
As a particular example, in response to selecting the sync tool data 374, the crimper 10 sends pressure, current, motor speed, and other sensor data captured during each crimping operation that the crimper 10 performed (e.g., since the last data synchronization). Additionally, the external device 164 receives the sensor data from the crimper 10 and forwards the data to the server 312 for storage in the tool data 358.
In response to receiving a user selection of the view tool details input 376, the external device 164 provides a GUI screen allowing the user to change tool information, such as a tool nickname displayed in the list 366. In some embodiments, the view tool details input 376 also enables the user to reach a GUI screen to configure the profile 320 and change the die and application data 324 of the crimper 10.
In some embodiments, curve data over a crimp cycle is captured for certain tool parameters, rather than a single maximum, minimum, or average value for the tool parameter. For example, in step 404, the electronic processor 100 captures (e.g., store) a data curve for one or more of motor speed, motor revolutions (and, thus, pump 14 activations), pressure, and motor current over time during a crimp cycle. A data curve includes a plurality of sensor data sample points over time, such as a sample per millisecond (ms), per 8 ms, per 10 ms, per 16 ms, per 32 ms, per 50 ms, per 64 ms, per 100 ms, per 128 ms, or another sample rate (e.g., between a sample/ms and a sample/128 ms).
The electronic processor 100 then analyzes the data curves obtained for various different operational parameters (step 406). For example, the electronic processor 100 compares the maximum pressure or current value to a predetermined threshold to determine whether full pressure was achieved in the cycle. After the analysis technique of step 406, in step 408, the electronic processor 100 provides an indication via the feedback indicators 174 whether the obtained curve data was within acceptable parameters. For instance, a green LED is illuminated if full pressure was achieved, and a red LED is illuminated if full pressure was not achieved
In step 410, the electronic processor 100 determines whether a request for data has been received from the external device 164. If no request has been received, in step 412, the electronic processor 100 determines whether a further trigger actuation has been received. If so, the method returns to step 402 to capture further data on the next crimp cycle. If not, the method returns to step 410 to determine whether a request for data has been received. Accordingly, the crimper 10 cycles between steps 410 and 412 until either a data request is received or the user actuates the trigger 106. In some embodiments, the method 400 begins at step 410, rather than step 402.
Upon receipt of a data request, the electronic processor 100 exports the tool operational data 322, including the data obtained in each instance of step 404 since a previous export, to the external device 164 in step 414. While the external device 164 is operable to obtain the data after each crimp cycle, commonly, the external device 164 will obtain tool operational data covering a plurality of crimp cycles (e.g., at the end of a shift or project). The external device 164 stores the received data in the tool operational data 340 portion of the memory 330.
In step 416, the external device 164 compares the received tool operational data to thresholds to analyze the operation of the crimper 10. In step 418, the various cycle counts being tracked by the external device 164 are updated in the tool data 336, including those counts displayed in the crimper data overview window 380 of the home screen 370 (total cycles, total full pressure cycles, cycles since last service). Additionally, the state of charge of the back-up power source 124 displayed in the sub-window 380d is updated based on data obtained in step 404 and provided to the external device 164 in step 414.
In step 420, the data obtained by the external device 164 is forwarded to the server 312. The server 312, in turn, stores the received data in the memory 354 as part of the tool data 358. In step 422, the server 312 analyzes the data. For instance, instead of or in addition to one or both of the comparison steps 406 and 416, the server 312 may perform similar comparisons in step 422 to analyze the data from the crimper 10.
In some instances, the controller 130 uses one data curve to generate a data curve of another parameter type. For instance, the controller 130 is operable to take pressure versus time data curve from a cycle and generate a characteristic output force versus time data curve deduced from a relationship between pressure and force.
With the additional data points from the pressure, current, motor speed, and force data curves, a more thorough analysis of a crimp cycle is achieved. For example, the expected curve data 326 stores a plurality of expected data curves that the electronic processor 100 is expected to capture during a successful crimp. The expected data curves may include a plurality (e.g., at least one) expected data points over time at a granularity similar to an obtained data curve. Each expected data curve is associated with a particular die and workpiece characteristics because, as illustrated in
Based on the operational parameter, the electronic processor 100 generates an actual data curve (step 515), as described above with respect to
In the first method 600, the electronic processor 100 calculates a difference value between each of a plurality of selected point of the expected data curve and corresponding points of the actual data curve (step 605). In other words, certain data points are selected from the expected data curve. These selected data points are then compared to the data points of the actual data curve that correspond to the selected data points from the expected data curve. In some embodiments, the selected data points may include all the data points of the expected data curve. In other embodiments, the selected data points only include a portion of the data points that define the expected data curve. Generally, the more data points that are selected the more complex the calculations become and the more processing power that is required. After calculating the plurality of difference values, the electronic processor 100 sums absolute values of each of the difference values to generate a cumulative difference value (step 610). By summing the absolute values of each of the difference values, the electronic processor 100 considers both deviations from the expected data curve (i.e., when the actual data curve exceeds the expected data curve and when the actual data curve is lower than the expected data curve). As shown in
In some embodiments, other curve comparison techniques are used in step 406 to determine whether a crimp cycle was successful. For instance, the expected data curve may include select data points, such as expected maximums and minimum values, and expected instances in time for those data points given the die and workpiece characteristics.
The electronic processor 100 also identifies an expected time period during which the expected curve feature is identified (step 710). The expected time period is shorter than the duration of the operation of the crimper 10 (e.g., shorter than a crimp cycle). Again, with respect to
The electronic processor 100 then determines whether the identified actual curve feature occurs within the expected time period (step 720). For example, the electronic processor 100 may determine whether the first actual curve feature of
In the embodiments described above, the actual data curve is compared to a specific expected data curve. This expected data curve may be selected by the electronic processor 100 based on specified head type, die type, and workpiece characteristics. For example, a user may input the head type, die type, and workpiece characteristics using the touch display 344 on the external device 164. The external device 164 (e.g., the electronic processor 342) may then determine an appropriate expected data curve from a plurality of expected data curves stored in the expected curve data 326. The external device 164 may then send the expected data curve to the crimper 10, and/or may send an indication to the crimper 10 of which expected data curve to use. Additionally or alternatively, the external device 164 may send the data specified by the user to the crimper 10 for the electronic processor 100 to determine an appropriate expected data curve.
In other embodiments, however, the electronic processor 100 compares the actual curve data to a plurality of expected data curves stored in the expected curve data 326 and performs a curve matching function to identify the type of crimp. The curve matching function may include, for instance, comparing the actual curve data to the expected data curves stored in the expected curve data 326 and determining the closest match based on a sum of absolute differences of each or of select data points on the curve or using another curve matching technique. If the actual data curve does not match any of the expected data curves (e.g., the sum of the absolute differences exceeds a threshold for each expected data curve), the controller 130 determines that the crimp was not successful. In the case of no match, the controller 130 may also determine whether the trigger 106 was released early (e.g., the trigger 106 was depressed for less than a predetermined threshold) and, in turn, indicate a crimp error and no match based on the early release of the trigger 106. Additionally, the controller 130 may determine that the actual curve data matches an expected data curve generally, but is still too different from the curve and indicates that the crimp was not successful. The controller 130 may also output a type of crimp and an indication of whether the crimp was successful based on the matched expected data curve to the external device 164 for display on the touch display 344. As an example, the external device 164 may identify the crimp type as using crimper head 72, using die type X for 3/0 wire, and crimping 3/0 aluminum wire.
The electronic processor 100 then determines whether the first difference value exceeds the second difference value (step 815). When the electronic processor 100 determines that the first difference value does not exceed the second difference value (e.g., the actual data curve more closely resembles the first expected data curve), the electronic processor 100 proceeds to identify a type of operation based on the first expected data curve (step 820). For example, the electronic processor 100 may identify the crimp type as using crimper head 72, using die type X for 3/0 wire, and crimping 3/0 aluminum wire. The electronic processor 100 can also determine whether the particular operation (e.g., crimp cycle) was completed successfully. As shown in
Referring back to step 815, when the electronic processor 100 determines that the first difference value exceeds the second difference value, the electronic processor 100 proceeds to identify a type of operation based on the second expected data curve. For example, and as mentioned above, the electronic processor 100 may identify a type of crimp performed by the hydraulic power tool (e.g., the crimper 10) at step 840. The electronic processor 100 may identify the crimp type as using a crimper head 50, using die type X for 3/0 wire, and crimping 3/0 aluminum wire. The electronic processor 100 can also then determine whether the crimp cycle was completed successfully. The electronic processor 100 determines whether the second difference value exceeds a second deviation threshold (step 845). As mentioned above, the second deviation threshold may be different than the first deviation threshold, since the second deviation threshold is based on a different expected data curve. In some embodiments, however, the second deviation threshold and the first deviation threshold are the same.
When the electronic processor 100 determines that the second difference value exceeds the second deviation threshold, the electronic processor 100 determines that the operation (e.g., the crimp cycle) was completed unsuccessfully (step 835). As described above, the electronic processor 100 may generate an alert indicating that the operation was unsuccessful. On the other hand, when the electronic processor 100 determines that the second difference value does not exceed the second deviation threshold, the electronic processor 100 determines that the operation (e.g., the crimp cycle) was completed successfully (step 850). Again, the electronic processor 100 may generate an indication using, for example, the indicators 116 to show that the operation was completed successfully.
Although
The external device 164 may display one or more of the obtained data curves on the touch screen display 344, e.g., in response to a user request entered via the touch screen display 344 of the external device 164. Additionally, in some instances, the expected curve may be overlaid on the touch screen display 344 so that a user can compare the expected versus actual data curves of the crimper 10. In some instances, a user inputs crimp information (e.g., head type, die type, and workpiece characteristics) and the external device 164 uses the crimp information to obtain the expected data curve from the expected curve data 326 stored in memory, and overlays the obtained expected data curve on the display with the actual data curve.
In other embodiments, the electronic processor 342 of the external device 164 compares the actual curve data to the expected data curves stored in the expected curve data 326 and performs a curve matching function as described above (e.g., with respect to
In some embodiments, the crimper 10 performs a more rapid, less complex analysis involving fewer data comparisons than the external device 164. For instance, after each cycle performed by the crimper 10, the electronic processor 100 of the crimper 10 compares the maximum pressure value of each cycle to the predetermined threshold and determines whether full pressure was obtained. However, the external device 164 performs the more thorough comparison techniques as described above with respect to the data curve analysis. In these embodiments, the expected curve data 326 may reside in the memory 330 of the external device 164, but not in the crimper 10.
On the other hand, when the electronic processor 100 determines that the maximum output pressure does not exceed the pressure threshold, the electronic processor 100 determines that the operation (e.g., the crimp cycle) was unsuccessful (step 925) and the electronic processor 100 generates an indication via, for example, the indicators 116 that the operation was unsuccessful (step 930). For example, the electronic processor 100 provides an indication (e.g., signal) that causes the indicators 116 to generate an indication, such as lighting up red when the operation was completed unsuccessfully.
The electronic processor 100 also sends the operational data to the external device 164 through the antenna and transceiver 154 (step 935). The external device 164 receives the operational data from the crimper 10 and analyzes the operational data to determine whether the crimper 10 completed the operation successfully. As shown in
With respect to
Additionally, although
The electronic processor 100, electronic processor 342 and/or electronic processor 350, respectively, are also operable to detect a malfunctioning crimper 10. For instance, these devices may generate an alert if the maximum pressure received over a certain number of or percentage of crimp cycles is below a predetermined threshold. Additionally, these devices may generate an alert if current, pressure, or motor speed is substantially below or above an expected value at any, select, or one point along the obtained data curves. For instance, the analysis methods may have high and low alert threshold levels that, when crossed during a crimp cycle, cause an alert. The generated alerts are perceptible to a human and may be generated via, for instance, the feedback indicators 174 or the touch screen display 344.
The crimper 10 then proceeds to send the plurality of data points to the external device 164 via the transceiver 154 on the crimper 10 (step 1020). The external device 164, and in particular, the electronic processor 342, proceeds to control the display screen 344 to display an expected data point for the operational parameter (step 1025). In some embodiments, the expected data point is display along with, and as part of, an expected data curve. The electronic processor 342 also controls the display screen 344 to display an actual data curve overlaid on the expected data point (1030). The actual data curve is based on the plurality of data points over time. In other words, the actual data curve is a plot of the plurality of data points over time based on the sampling rate and/or the specific sampling times for each data point. As discussed above, when the actual data curve is overlaid on the expected data point, the actual data curve and the expected data point are displayed simultaneously on the same section of the display screen 344. In some embodiments when the actual data curve is overlaid on the expected data point, the expected data point is displayed on top of the actual data curve. In other embodiments, the actual data curve is displayed on top of the expected data point.
Additionally, as shown in
Furthermore, the electronic processor 100, electronic processor 342 and/or processor 350, respectively, are also operable to provide early notification if the crimper performance is degrading over time. For instance, rather than comparing a parameter obtained from the tool operational data 322 to a particular threshold for a single data point, the parameter over several or many data points across multiple crimp cycles may be analyzed. If the data points are trending away from a desired value, even if not yet in excess of an alert threshold for an individual data point, the electronic processor 100, electronic processor 342, and/or processor 350 is operable to generate an alert providing an early notification of performance degradation. For instance, if the maximum achieved pressure over a set of 50 cycles is still above the predetermined threshold used to determine whether a fully pressure cycle occurred, but the detected pressure values are trending closer to the predetermined threshold at a predetermined rate, an early notification alert indicating performance degradation may be generated. In turn, a user may take the crimper 10 in for service before the crimper 10 is actually malfunctioning such that it cannot consistently achieve full pressure cycles.
Additionally, a series of overcurrent or other error conditions over a certain number of cycles will cause the electronic processor 100, electronic processor 342 and/or processor 350, to generate an early notification alert indicating performance degradation.
Furthermore, service technicians performing maintenance or diagnostic analysis of the crimper 10 may obtain tool operational data 322 from the crimper 10 via the external device 164 associated with the service personnel or via another device (e.g., via a web browser on a laptop computer) accessing the information previously stored on the memory 354 of the server 312. The service technicians may manually compare current, pressure, and/or motor speed data curves to expected data curves for the respective parameters. Particular deviations of the actual data curves from the expected data curves can indicate to the service technicians a particular issue with the crimper 10, such as a malfunctioning motor 12 or pump 14.
Although
Furthermore, the method 400 is operable to analyze each of the parameters making up the tool operational data noted above. For instance, the electronic processor 100 in step 406, the external device 164 in step 416, and/or the server 312 in step 422 are each operable to analyze tool operational data (e.g., compare the data values to particular thresholds) to determine whether a threshold is exceeded. The analysis may be used to provide general statistical and tool usage information to a user, and/or to generate alerts in the instance of malfunctions, maintenance requirements, or performance degradation.
This application claims the benefit of U.S. Provisional Application No. 62/175,958 filed on Jun. 15, 2015, the entire contents of which are hereby incorporated by reference.
Number | Name | Date | Kind |
---|---|---|---|
3882305 | Johnstone | May 1975 | 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 |
5113949 | Ohkubo et al. | May 1992 | A |
5277261 | Sakoh | Jan 1994 | A |
5315501 | Whitehouse | May 1994 | A |
5592396 | Tambini et al. | Jan 1997 | A |
5727417 | Moffatt et al. | Mar 1998 | A |
5903462 | Wagner et al. | May 1999 | A |
5942975 | S∅rensen | Aug 1999 | A |
6028669 | Tzeng | Feb 2000 | 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 |
6446482 | Heskey et al. | Sep 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 |
6547014 | McCallops et al. | Apr 2003 | B2 |
6598684 | Watanabe | Jul 2003 | B2 |
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 |
6836614 | Gilmore | Dec 2004 | B2 |
6848516 | Giardino | Feb 2005 | B2 |
6863502 | Bishop et al. | Mar 2005 | B2 |
6868351 | Schoch | Mar 2005 | B1 |
6872121 | Wiener et al. | Mar 2005 | B2 |
6913087 | Brotto et al. | Jul 2005 | B1 |
6923285 | Rossow et al. | Aug 2005 | B1 |
6938689 | Farrant et al. | Sep 2005 | B2 |
6954048 | Cho | Oct 2005 | B2 |
6968908 | Tokunaga et al. | Nov 2005 | B2 |
6981311 | Seith et al. | Jan 2006 | B2 |
6986274 | Lefavour et al. | Jan 2006 | B2 |
7034711 | Sakatani et al. | Apr 2006 | B2 |
7035710 | Balling | Apr 2006 | B2 |
7036703 | Grazioli et al. | May 2006 | B2 |
7062998 | Hohmann et al. | Jun 2006 | B2 |
7086483 | Arimura et al. | Aug 2006 | B2 |
7102303 | Brotto et al. | Sep 2006 | B2 |
7112934 | Gilmore | Sep 2006 | B2 |
7137541 | Baskar et al. | Nov 2006 | B2 |
7174324 | Kakuhari et al. | Feb 2007 | B2 |
7211972 | Garcia et al. | May 2007 | B2 |
7243440 | DeKeyser | Jul 2007 | B2 |
7298240 | Lamar | Nov 2007 | B2 |
7328086 | Perry et al. | Feb 2008 | B2 |
7328757 | Davies | Feb 2008 | B2 |
7330129 | Crowell et al. | Feb 2008 | B2 |
7343764 | Solfronk | Mar 2008 | B2 |
7346406 | Brotto et al. | Mar 2008 | B2 |
7346422 | Tsuchiya et al. | Mar 2008 | B2 |
7359762 | Etter et al. | Apr 2008 | B2 |
7382272 | Feight | Jun 2008 | B2 |
7383882 | Lerche et al. | Jun 2008 | B2 |
7437204 | Lev-Ami et al. | Oct 2008 | B2 |
7464769 | Nakazawa et al. | Dec 2008 | B2 |
7496852 | Eichorn et al. | Feb 2009 | B2 |
7501778 | Hashimoto et al. | Mar 2009 | B2 |
7540334 | Gass et al. | Jun 2009 | B2 |
7613590 | Brown | Nov 2009 | B2 |
7646155 | Woods et al. | Jan 2010 | B2 |
RE41185 | Gilmore et al. | Mar 2010 | E |
7690569 | Swanson et al. | Apr 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 |
7834566 | Woods et al. | Nov 2010 | B2 |
7850071 | Sakamoto et al. | Dec 2010 | B2 |
7868591 | Phillips et al. | Jan 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 |
7931096 | Saha | Apr 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 |
8044796 | Carr, Sr. | Oct 2011 | B1 |
8049636 | Buckingham et al. | Nov 2011 | B2 |
8056473 | Frenken | Nov 2011 | B2 |
8161613 | Schuele et al. | Apr 2012 | B2 |
8171828 | Duvan 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 |
8330426 | Suzuki et al. | Dec 2012 | B2 |
8344879 | Harmon et al. | Jan 2013 | B2 |
8351982 | Rofougaran | 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 |
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 |
9030145 | Brennenstuhl et al. | May 2015 | B2 |
9031585 | Kahle et al. | May 2015 | B2 |
9038743 | Aoki | May 2015 | B2 |
9061392 | Forgues et al. | Jun 2015 | B2 |
9073134 | Koeder et al. | Jul 2015 | B2 |
9111234 | Wallace et al. | Aug 2015 | B2 |
9126317 | Lawton et al. | Sep 2015 | B2 |
9144875 | Schlesak et al. | Sep 2015 | B2 |
9194917 | Brochhaus | Nov 2015 | B2 |
9216505 | Rejman et al. | Dec 2015 | B2 |
9232614 | Hiroi | Jan 2016 | B2 |
9233457 | Wanek et al. | Jan 2016 | B2 |
9242356 | King et al. | Jan 2016 | B2 |
9256988 | Wenger et al. | Feb 2016 | B2 |
9257865 | Hiuggins et al. | Feb 2016 | B2 |
9281770 | Wood et al. | Mar 2016 | B2 |
20010052416 | Wissmach et al. | Dec 2001 | A1 |
20020033267 | Schweizer et al. | Mar 2002 | A1 |
20030009262 | Colangelo, III et al. | Jan 2003 | A1 |
20030121677 | Kady et al. | Mar 2003 | A1 |
20030079513 | Miyamoto et al. | May 2003 | A1 |
20040182587 | May et al. | Sep 2004 | A1 |
20050035659 | Hahn et al. | Feb 2005 | A1 |
20060009879 | Lynch et al. | Jan 2006 | A1 |
20060076385 | Etter et al. | Apr 2006 | 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 |
20080086685 | Janky et al. | Apr 2008 | A1 |
20080252446 | Dammertz | Oct 2008 | A1 |
20090056467 | Newman | Mar 2009 | A1 |
20090250364 | Gerold et al. | Oct 2009 | A1 |
20090251330 | Gerold et al. | Oct 2009 | A1 |
20100096151 | Östling | Apr 2010 | A1 |
20100101785 | Khvoshchev et al. | Apr 2010 | A1 |
20100116519 | Gareis | May 2010 | A1 |
20100154599 | Gareis | Jun 2010 | A1 |
20100176766 | Brandner et al. | Jul 2010 | A1 |
20110056716 | Jönsson et al. | Mar 2011 | A1 |
20110067895 | Nobe et al. | Mar 2011 | A1 |
20110073343 | Sawano et al. | Mar 2011 | A1 |
20110162858 | Coste | Jul 2011 | A1 |
20110186353 | Turner et al. | Aug 2011 | A1 |
20110309931 | Rose | Dec 2011 | A1 |
20120167721 | Fluhrer | Jul 2012 | A1 |
20120168189 | Eckert | Jul 2012 | A1 |
20120267134 | Matthias et al. | Oct 2012 | A1 |
20120284981 | Bungter et al. | Nov 2012 | A1 |
20120292070 | Ito et al. | Nov 2012 | A1 |
20120325507 | Fluhrer et al. | Dec 2012 | A1 |
20130024245 | Nichols et al. | Jan 2013 | A1 |
20130062086 | Ito et al. | Mar 2013 | A1 |
20130071815 | Hudson 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 |
20130187587 | Knight et al. | Jul 2013 | A1 |
20130188058 | Nguyen et al. | Jul 2013 | A1 |
20130255980 | Linehan et al. | Oct 2013 | A1 |
20130327552 | Lovelass et al. | Dec 2013 | A1 |
20130328512 | Ozaki | Dec 2013 | A1 |
20130328513 | Odenthal et al. | Dec 2013 | A1 |
20140006295 | Zeiler et al. | Jan 2014 | A1 |
20140015389 | Vatterott et al. | Jan 2014 | A1 |
20140069672 | Mashiko et al. | Mar 2014 | A1 |
20140107853 | Ashinghurst et al. | Apr 2014 | A1 |
20140122143 | Fletcher et al. | May 2014 | A1 |
20140151079 | Furui et al. | Jun 2014 | A1 |
20140158389 | Ito et al. | Jun 2014 | A1 |
20140159662 | Furui et al. | Jun 2014 | A1 |
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 |
20140259597 | Lavalley | Sep 2014 | A1 |
20140266024 | Chinnadurai et al. | Sep 2014 | A1 |
20140284070 | Ng et al. | Sep 2014 | A1 |
20140292245 | Suzuki et al. | Oct 2014 | A1 |
20140324194 | Larsson et al. | Oct 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 | Duesselberg et al. | Jan 2015 | A1 |
20150002089 | Rejman et al. | Jan 2015 | A1 |
20150014058 | Wassell et al. | Jan 2015 | A1 |
20150042247 | Kusakawa | Feb 2015 | A1 |
20150122524 | Papp | May 2015 | A1 |
20150127205 | Brochhaus | May 2015 | A1 |
20150135306 | Winkler et al. | May 2015 | A1 |
20150135907 | Hirabayashi et al. | May 2015 | A1 |
20150137721 | Yamamoto et al. | May 2015 | A1 |
20150158157 | Hirabayashi et al. | Jun 2015 | A1 |
20150158170 | Nitsche et al. | Jun 2015 | A1 |
20150171654 | Horie et al. | Jun 2015 | A1 |
20150179036 | Heine et al. | Jun 2015 | A1 |
20150191096 | Becker et al. | Jul 2015 | A1 |
20150340921 | Suda et al. | Nov 2015 | A1 |
20170008159 | Boeck et al. | Jan 2017 | A1 |
Number | Date | Country |
---|---|---|
1413801 | Apr 2003 | CN |
101968924 | Feb 2011 | CN |
102480096 | May 2012 | CN |
102822752 | Dec 2012 | CN |
104295233 | Jan 2015 | CN |
4337796 | May 1995 | DE |
10309703 | Sep 2004 | DE |
202006014606 | Jan 2007 | DE |
2147750 | Jan 2010 | EP |
2000176850 | Jun 2000 | JP |
2004072563 | Mar 2004 | JP |
2006123080 | May 2006 | JP |
WO2002030624 | Apr 2002 | WO |
WO2007090258 | Aug 2007 | WO |
WO2013116303 | Aug 2013 | WO |
WO-2014104025 | Jul 2014 | WO |
2014104025 | Jul 2017 | WO |
Entry |
---|
Google Translation from WIPO webpage of WO-2014104025-A1 (Year: 2019). |
International Search Report and Written Opinion for Application No. PCT/2016037678 dated Sep. 9, 2016 (17 pages). |
Chinese Patent Office Action for Application No. 201680048494.8 dated Dec. 17, 2018 (13 pages, English translation included). |
European Patent Office Search Report for Application No. 16812361.0 dated Jan. 18, 2019, 7 pages. |
Chinese Patent Office Action for Application No. 201680048494.8 dated Sep. 9, 2019 (12 pages, partial English translation included). |
Number | Date | Country | |
---|---|---|---|
20160363510 A1 | Dec 2016 | US |
Number | Date | Country | |
---|---|---|---|
62175958 | Jun 2015 | US |