Patent ID: 12197184

DETAILED DESCRIPTION

The present disclosure provides embodiments of portable, hand-held, battery operated, tools that have an operating cycle that perform a desired operation on a workpiece and that can communicate with external computing systems to for example upload images of operations performed on workpieces. Non-limiting examples of such desired operations include, crimping, sawing, cutting or grinding operations on a workpiece. The present disclosure provides embodiments of computing systems that communicate with such tools to receive tool operating cycle information and other tool information. The computing systems according to the present disclosure may include, for example, one or more computing devices and cloud computing services. The one or more computing devices may include, for example, desktop and laptop computers, smartphones and tablets. For ease of description, the tool operating cycle information may also be referred to herein as the “cycle information.” The cycle information includes information associated the operating cycles of the tool, and the other tool information includes, tool diagnostic information, tool connectivity with a computing system, and the like. For ease of description, the cloud computing services may also be referred to herein as the “web services.”

For ease of description, the tools described herein are portable, hand-held, battery operated, hydraulic crimping tools used for forming crimps and other electrical connections, and for monitoring and recording cycle information associated with crimp operating cycles of the crimping tools, and systems for verifying crimped electrical connections by, for example, uploading images of crimps on workpieces. For ease of description, the crimped electrical connections contemplated herein may also be referred to as the “crimp” in the singular and the “crimps” in the plural. The information associated with a crimp or crimps contemplated herein may also be referred to as the “cycle information.” The cycle information contemplated by the present disclosure for a crimping tool includes, but is not limited to, the type and size of the workpiece to be crimped, a force applied by the tool to form the crimp, a time stamp when the crimp was formed, a location of the tool when the crimp was formed, status of the crimp, a data flag setting, alpha-numeric information associated with the flag, and other alpha-numeric information associated with the crimp. Cycle information for a particular crimp is stored in a cycle data record. Each cycle data record may also include other information, such as other crimp related information and/or tool related information and/or images associated with particular crimps. An example of other crimp related information included in each cycle data record includes a Crimp Image flag or key with an associated binary value, e.g., 1 or 0. The “Crimp Image” flag set to “1” may reflect that there is an image associated with the cycle data record and the “Crimp Image” flag set to “0” may reflect that there is no image associated with the cycle data record. The workpieces contemplated by the present disclosure for the crimping tool described herein include, but are not limited to, lug connectors, splice connectors and other wire terminations or endpoints. The time stamps contemplated by the present disclosure include, but are not limited to, the time of day a crimp was formed, the date a crimp was formed.

Turning to the figures,FIGS.1-4show an exemplary embodiment of a hydraulic power tool10according to the present disclosure. The tool10includes a tool frame12and a working head14. The tool frame12includes a main body30and a handle40that form a pistol-like shape. However, the tool frame12could be in any suitable type of shape. Within the main body30of the tool frame12is a battery driven drive and control system11illustrated schematically inFIG.2. The drive and control system11includes a drive system and a control system. In the exemplary embodiment shown, the drive system is a hydraulic drive system that includes a motor18, a gear reduction box48, a pump15, a hydraulic fluid reservoir22, a hydraulic drive28and a relief valve29. However, the drive system may be an electro-mechanical system with the motor18and gear reduction box48. In the exemplary embodiment shown, the control system includes a battery20, a controller24, memory32, one or more operator controls42and44, a communication port21, a location system23, a stroke sensor16, a force sensor27, a flag switch19, a status indicator25and a work light26.

The battery20provides power to the controller24. The battery20also provides power to the motor18under the control of controller24and the operator controls42and44. The motor18drives the pump15via gear reduction box48. The pump15is in fluid communication with the hydraulic fluid reservoir22. When driven by the motor18, the pump15delivers fluid under pressure from reservoir22to the hydraulic drive28. Force generated by hydraulic drive28is delivered via an actuator60, such as a piston seen inFIG.4, to the working head14, as described below. The force sensor27is provided to measure the force applied to a workpiece as described below. Non-limiting examples of the force sensor27include pressure sensors or transducers, load cells, strain gauges and other force measuring devices. In the exemplary embodiment of the tool10described herein, the force sensor27is a pressure sensor. The pressure sensor27is connected to the hydraulic drive28and senses the hydraulic pressure in the hydraulic drive28. The controller24receives data indicating the pressure in the hydraulic drive28from the pressure sensor27and makes a determination (or computes) of a force applied by the tool10on the workpiece which is described in more detail below. The controller24receives signals from the one or more operator controls42,44to activate and deactivate the motor18which activates and deactivates the hydraulic drive28, respectfully. When the controller24activates the motor18, a work light26positioned on the main body30of the tool frame12may also be activated to illuminate an area of the working head14during a crimp cycle.

Continuing to refer toFIG.2, a relief valve29connects the hydraulic drive28with the fluid reservoir22. According to one embodiment, the relief valve29is a mechanically actuated valve designed to open when a predetermined maximum pressure is reached in the hydraulic and control system11. When the relief valve29is opened, fluid flows from the hydraulic drive28back to reservoir22relieving pressure in hydraulic drive28and removing the force applied on the workpiece by the actuator60. A spring (not shown) may be provided as part of hydraulic drive28to return the actuator60, e.g., the piston seen inFIG.4, to a home position, shown inFIG.3, when pressure in hydraulic drive28is relieved. It is noted that when the relief valve29opens, the relief valve29may make an audible indication, such as a “pop” like sound, that the relief valve29has opened.

The controller24monitors the pressure in hydraulic drive28to determine when a crimp cycle is complete. After actuating the motor18in response to activation of an operator control, e.g., trigger switch44, the controller24monitors the hydraulic fluid pressure in the hydraulic system via the force sensor27. When the relief valve29opens and the pressure in the hydraulic system drops below a predetermined minimum threshold, the controller24determines that a crimp cycle is complete. As shown inFIG.1, an indicator light25is positioned on a top portion of the main body30of the tool frame12facing in the proximal direction so that it is visible to the tool user. The indicator light25is electrically connected to the controller24. According to one embodiment, the light25is a bi-color LED that can be energized to illuminate in two distinct colors, such as red and green. However, other types of LED indicators may be used, such as a tri-colored LED capable of emitting red, green and yellow light. When the controller24determines that the crimp cycle is complete and that the hydraulic system has reached a predetermined threshold pressure, the controller24energizes light25to illuminate green to indicate a successful crimp. If the hydraulic system was not able to reach the predetermined threshold pressure during the crimp cycle, because, for example, there was insufficient battery power to reach the desired threshold pressure or because the pressure setting of the relief valve29is out of calibration, the controller24energizes the light25to illuminate red. It is noted that the present disclosure also contemplates that the controller24may activate a sound generating device (not shown) when the controller24determines that the crimp cycle is complete, and that the hydraulic system has reached a predetermined threshold pressure to indicate a successful crimp.

Referring again toFIGS.1and2, in this exemplary embodiment, the flag switch19is electrically connected to the controller24and permits a tool user to store a data flag along with other cycle information about a particular cycle operation of the tool10in the memory32. The flag switch19may be provided on the main body30so that a tool user can activate the flag switch19to set a flag in the cycle information associated with a cycle data record stored in the tool memory32. Such a flag may be used to remind a tool manager and/or a tool user to review or insert comments into the cycle information associated with a particular crimping cycle, as will be explained below. In addition, the flag may represent that a failed crimp was noticed by the tool user.

Also electrically connected to controller24is a location sensor23. The location sensor23may be a device to determine the location of the tool10based on radio frequency signals received from a global navigation system. Non limiting examples of global navigation system include the global navigation satellite system (GNSS), such as the Global Positioning System (GPS) or the Next Generation Operational Control System (OCX) operated by the United States government, the Global Navigation Satellite System (GLONASS) operated by the Russian government, the BeiDou Navigation Satellite System (BNS) operated by the Chinese government, the Quasi-Zenith Satellite System (QZSS) operated by the Japanese government, the Galileo Positioning System operated by the European Union, the India Regional Navigation Satellite System (NAVIC) or the like. As an example, if the global navigation system is the GNSS, the location sensor23would be a GNSS antenna module, such as the SAM-M8Q module manufactured by Ublox. The location sensor23may be located near the surface of the handle40of the tool frame12, as shown inFIG.1, to ensure that it can receive radio frequency signals from GNSS satellites. In another exemplary embodiment, the location sensor23may be located near the surface of the main body30of the tool frame12. The location sensor23may also include other means for determining a location of the tool10, such as a receiver capable of determining location information from radio frequency sources other than global navigation systems, including cellular phone network transmissions. The present disclosure also contemplates that a separate device may be used to provide the location information associated with a crimp. For example, a tool user may use the location service on their mobile smartphone to provide the location of the crimp. To illustrate, if a tool user has their mobile smartphone paired with a tool10after a crimp is formed the controller24may ping the smartphone to provide the location information, e.g., the latitude and longitude coordinates of the smartphone, to the tool10. The location information would then be stored in the cycle data record in memory32of the tool10.

The controller24may be a microprocessor, microcontroller, application specific integrated circuit, field programmable gate array (FPGA) or other digital processing apparatus as will be appreciated by those skilled in the relevant art. The controller24communicates with memory32to receive program instructions and to retrieve data. Memory32may be read-only memory (ROM), random access memory (RAM), flash memory, and/or other types of electronic storage know to those of skill in the art. The controller24communicates with computing devices or computing system via a communication port21, seen inFIG.1. The communication port21may be physical connection, such as a USB port, a wireless communication interface, such as WiFi, Bluetooth, and the like, a removeable memory device, such as a SIM card or flash drive, or combinations thereof. Non-limiting examples of external networks include Wireless Local Area Networks (WLAN). Non-limiting examples of computing devices include desktop and laptop computers, tablets, smartphones, and devices that manage networks, such as devices that manage a WLAN and is connected to multiple communication ports21, e.g., USB ports, on different tools10simultaneously. The computing devices200may also regularly monitor diagnostic information on the tool10and location information of the tool10and is capable of uploading this tool information to the web services210, as seen inFIG.10and described below.

Continuing to refer toFIGS.1and2, the battery20is removably connected to the bottom of the handle40. In another embodiment, the battery20could be removably mounted or connected to any suitable position on the tool frame12. In another embodiment, the battery20may be affixed to the tool10so that it is not removable. The battery20is preferably a rechargeable battery, such as a lithium ion battery, that can output a voltage of at least 16 VDC, and preferably in the range of between about 16 VDC and about 24 VDC. In the exemplary embodiment shown inFIG.1, the battery20can output a voltage of about 18 VDC.

The handle40also supports the one or more operator controls, such as the trigger switches42and44, which can be manually activated by a tool user. The handle40may include a hand guard46to protect a tool user's hand while operating the tool10and to prevent unintended operation of trigger switches42and44. According to an embodiment of the present disclosure, one of the operator controls (e.g., trigger switch44) may be used to activate the hydraulic and control system11while the other operator control (e.g., trigger switch42) may be used to cause the hydraulic and control system11to deactivate so that the hydraulic drive28is depressurized.

Referring now toFIGS.1,3and4the working head14of the tool10will be described. The working head14includes an impactor52, and anvil54, an arm56and a guide58. The impactor52has a working surface52aand is configured to move between a home position, shown inFIG.3, and a crimping position, shown inFIG.4. The impactor52is configured and dimensioned to connect to or couple with the actuator60of the hydraulic and control system11within the main body30of the tool frame12. In this exemplary embodiment, the actuator60is a piston and may also be referred to as the piston60. As described above, in an exemplary embodiment, one of the trigger switches (e.g., trigger switch44) may be used to activate the hydraulic and control system11by activating the motor18that causes the hydraulic pump15to activate via the gear reduction box48which pressurizes the hydraulic drive28to drive the piston60in the distal direction, as shown by the arrow inFIG.4. Driving the piston60distally causes the impactor52to move to the crimping position and deliver force to the workpiece, e.g., lug connector110seen inFIG.6, or splice connector114seen inFIG.7onto a conductor. The other trigger switch (e.g., trigger switch42) may be used to cause the hydraulic and control system11to deactivate so that the hydraulic drive28is depressurized causing the piston60to retract in the proximal direction to the home position, shown inFIG.3. As noted above, a spring (not shown) may be provided as part of hydraulic drive28to return the piston60to the home position when pressure in hydraulic drive28is relieved. The impactor52is operatively coupled to the guide58on the arm56of the working head14so that the impactor52can move along the guide58as the piston60moves the impactor52between the home and crimping positions. For example, when the piston60is driven in the distal direction, the piston60moves the impactor52along the guide58from the home position, seen inFIG.3, toward the crimping position, as shown inFIG.4.

The arm56has at its proximal end a ring35used to connect the working head14to the tool frame12, as is known. In one exemplary embodiment, the working head14and the frame12may be permanently joined with one another via the ring35. The ring35has a center aperture (not shown) through which the piston60passes in order to connect to the impactor52. The distal end of the arm56includes or forms the anvil54such that the anvil is fixed in position. The anvil54has a working surface54a. When a workpiece, such as a lug connector110or a splice connector114, is placed in the working head14between the impactor52and the anvil54, and a conductor or conductors are inserted into workpiece, the motor18of the tool10can be activated so that the piston60is driven from the home position toward the crimping position. As the impactor52moves toward the anvil54the workpiece may also move toward the anvil54. When the impactor52and anvil54both contact the workpiece further movement of the impactor52causes the working surface52aof the impactor52and the working surface54aof the anvil54to deform the workpiece thus making the crimp. It is noted that the home position is when the impactor52is adjacent the ring35and the crimping position is when the impactor52and anvil54deform the workpiece.

To measure the force applied by the impactor52on the workpiece, the force sensor27, which in this exemplary embodiment is a pressure sensor, is located in fluid communication with the hydraulic drive28. When the piston60drives the impactor52distally until the impactor52is in the crimping position, the force applied by the impactor52onto the workpiece is monitored by the pressure sensor27. According to yet another embodiment of the disclosure, the force sensor27may be located elsewhere, such as between the impactor52and the anvil54, or between the impactor52and one of the die100, seen inFIG.5, or between the anvil54and one of the die100to measure force applied by impactor52on the workpiece. According to another embodiment, the force sensor27may be a strain gauge mounted on arm56and used to measure the force applied to a workpiece.

According to one embodiment, the impactor52and anvil54may be configured and dimensioned so that when the piston60pressed the impactor52into the anvil54the working surface52aof the impactor52and the working surface54aof the anvil form a crimp connection with the desired shape. According to another embodiment, the impactor52and/or anvil54may include surface features that allow die100, such as the die shown inFIG.5to be releasably connected to the impactor52and the anvil54. Each die100has a working surface102or104. By using replaceable die, a variety of working surfaces, e.g., working surfaces102and104, can be provided on the tool10to produce a variety of different shaped crimp connections. As an example, to splice two conductors together, the die100, seen inFIG.5, can be fitted onto the impactor52and the anvil54. A splice connector114, such as the one shown inFIG.7, can be fitted onto the ends of the conductors (not shown) to be spliced. The splice connector114with the conductor ends can then be placed between the working surfaces102and104of the die100and the tool10is actuated causing the impactor52with one die100to move from the home position toward the crimping position. When the working surface102of one die100presses the splice connector114against the working surface104of the other die100, the force applied by the impactor52compresses the splice connector114between the working surfaces102and104of the die100to form the crimp. To form the complete splice, multiple crimp operations may be required, depending on the configuration and dimensions of the conductor and the connector.

Referring now toFIG.9, an illustrative example of the pressure in the hydraulic drive28as a function of time for a successful crimp cycle is shown. In this example, when the motor18is activated the pressure in the hydraulic system begins to rise and the piston60drives the impactor52toward the workpiece and the anvil54. Once the impactor52contacts the workpiece pressing the workpiece against the anvil54and the workpiece begins to deform, the pressure in the hydraulic drive28rises steeply. When the pressure reaches a threshold pressure value Pthreshold, the relief valve29opens causing the pressure in the hydraulic drive28to drop. When the pressure drops below a threshold minimum value Pendthe controller24determines that the crimp cycle is complete. Controller24then activates light25to illuminate green if Pthresholdwas reached during the crimp cycle. If the pressure were to drop below Pendwithout having achieved Pthresholdduring the crimp cycle, the controller24would activate light25to illuminate red, indicating a potentially defective crimp connection. As a non-limiting example, the threshold minimum pressure Pendmay be about 8,500 psi and the threshold pressure Pthresholdmay be about 9,000 psi. According to a further embodiment, instead of providing a mechanical relief valve29, an electrically operated relief valve electrically connected to the controller24may be provided. According to this embodiment, the controller24monitors the pressure in the hydraulic drive28based on a signal from the pressure sensor27and opens the relief valve29when that pressure reaches the predetermined threshold value Pthresholdending the crimp cycle. As in the previous embodiment, if the pressure reaches Pthresholdduring the crimp cycle, the light25is illuminated green. If the predetermined threshold value Pthresholdcannot be reached after a predetermined period of time, e.g., 5 seconds, the controller24will end the crimp cycle by turning power to the motor18off and the controller24would activate light25to illuminate red, indicating a potentially defective crimp connection.

According to yet another embodiment, a stroke sensor16, seen inFIG.2, may be provided. The stroke sensor16determines when piston60has reached the end of its range and/or that the working surfaces102and104of the die100are at their closest approach. When the working surfaces102and104of the die100are at their closest approach, the space defined by the working surfaces102and104of the die100forms the desired shape of the finished crimp connection. The controller24monitors the stroke sensor16and when the piston60is at the end of its range, the controller24opens the relief valve29completing the crimp cycle. The controller24may also monitor the pressure sensor27, and as with the previous embodiments, the light25is illuminated either green or red, depending on whether the threshold pressure Pthresholdwas reached during the crimp cycle.

According to a further embodiment, the force sensor27may be a load cell that monitors the force applied to the workpiece during the crimp cycle. The force measurement by the load cell27may be used by the controller24instead of (or possibly in addition to) the pressure monitored by a force sensor27, e.g., a pressure sensor, to determine whether sufficient maximum force is applied during a crimp cycle. The force sensor27may be a load cell that is positioned between the impactor52and the anvil54, or between the impactor52and one of the die100or between the anvil and one of the die100.

In operation, a tool user selects an appropriate die, such as die100shown inFIG.5, to form a desired crimp connection. The tool user selects the workpiece, which in this exemplary embodiment is a lug connector110or splice connector114, for connection to a conductor. The tool user prepares the conductor, for example, by cutting it to length and removing insulation on the end to be crimped and fits the workpiece onto the conductor. The tool user places the workpiece and conductor between the die faces102and104of the die100and presses trigger44to actuate the hydraulic and control system11. More specifically, when the trigger44is pressed, the controller24turns on the motor18causing the pump15to pressurize the hydraulic drive28which moves piston60distally. Movement of the piston60distally moves the impactor52from the home position to the crimping position. When the piston60is in the crimping position, the impactor52delivers a crimping force to the workpiece so that the impactor52and anvil54deform the workpiece to crimp the conductor to the workpiece. According to one embodiment, the pressure in the hydraulic drive28rises as the workpiece is being deformed. When the pressure reaches the predetermined threshold value Pthreshold, the relief valve29opens causing the pressure to drop below the minimum threshold value Pend. In response, the controller24determines that the crimp cycle is complete. With the crimp cycle complete, the controller24determines and stores the cycle information in memory32as a cycle data record. For example, the controller24determines the geographic location where the crimp was formed based on signals from the location sensor23. This location information may be in the form of a latitude, longitude and/or altitude where the crimp was formed. The controller24determines the time stamp in the form of time and date when the crimp was formed. The controller24also determines the maximum force that was applied to the workpiece during the crimping operation by analyzing signals received from the force sensor27, which in this exemplary embodiment is a pressure sensor. This cycle information is then stored in memory32as a cycle data record, similar to that shown inFIG.8. According to another exemplary embodiment, instead of or in addition to recording the maximum force, the controller24may record a series of forces or pressures applied as the crimp is formed, as shown by the graph ofFIG.9. If the tool user decides that further information about a last attempted crimp cycle should be provided, for example, because the tool user was cycling the tool10without actually forming a crimp, or because the tool user determined that a crimp was faulty and replaced it with a new crimp, the tool user can activate the flag switch19, seen inFIG.1, causing the controller24to add a data flag to the cycle data record of that particular crimp operation, as seen in row1ofFIG.8described below.

Referring toFIG.8, an example of cycle data records of cycle information stored in memory32is shown. The cycle data records are illustrated here by a table of data arranged in rows, but a variety of data structures known to those with skill in the relevant field could be used. In this embodiment, each row records cycle information for a particular crimp cycle of the tool10. In the first column of the table an index number is stored. According to one embodiment, the index number is indicative of the particular crimp cycle performed by the tool out of the total number of cycles the tool10has made and serves to uniquely identify each crimp cycle recorded. The index number may also be used to determine if the tool10needs to be recalibrated according to a maintenance schedule. The next column records the maximum force, e.g., pressure, applied or a maximum hydraulic pressure achieved by the hydraulic drive28during the crimp cycle. Alternatively, instead of recording a maximum force or pressure, a logical value (e.g., “Pass” or “Fail”) indicating that sufficient pressure was or was not achieved during the crimp cycle could be recorded. The next columns record the location of the tool10when the crimp is formed, i.e., at the completion of a crimp cycle. According to one embodiment, the tool location is recorded as a latitude and longitude. According to a further embodiment, the altitude of the tool10may be recorded so that if the tool10is used a floor of a building, the floor of the building where the crimp was made can be determined by the altitude. The next two columns record the time stamp associated with when the crimp cycle was completed or activated. In the exemplary embodiment ofFIG.8, the time stamp includes the time and date when the crimp cycle was activated. The next column holds a flag that may have been added to the data record by activating the flag switch19, seen inFIGS.1and2, following a crimp cycle. In the embodiment illustrated inFIG.8, the first cycle data record includes a flag. For each subsequent cycle of the tool10, a new cycle data record of cycle information is added to memory32, as illustrated by a new row of the table. The next column holds alpha-numeric comments that may have been added to the data record by the tool user, such as “crimped failed due to user error.” The present application also contemplates that the comments may include crimp location information or other information that may confirm or help with the location of crimps formed by a particular tool.

Referring now toFIGS.10-17, the cycle information and other tool information stored in memory32of one or more tools10can be communicated or transmitted to one or more computing devices200paired with the one or more tools10via the communication port21of each tool10, seen inFIG.1. The one or more computing devices200may then communicate or transmit the cycle information and other tool information to a cloud computing services210. The one or more computing devices200and the cloud computing services210may form part of an overall computing system250, seen inFIG.10. For ease of description, the cloud computing services210may also be referred to herein as the “web services.” Communicating the cycle information and other tool information to the computing devices200and/or web services210permits tool managers and tool users to manage one or more tools10, to manage one or more tool users and/or to manage crimps formed by the one or more tools10. The computing devices200and/or web services210may also regularly monitor tool diagnostic information, such as temperature information or warnings, information indicating that a particular tool10is no longer detected within the computing system network250, information indicating that a particular tool10has repeatedly failed recent crimps, and/or cycle dwell time on the one or more tools10and track the location of the tool10.

The cycle information stored in memory32of each tool10can be communicated to the computing devices200using wireless or wired networks. A non-limiting example of a wireless network includes a Wireless Local Area Networks (WLAN)212. Non-limiting examples of computing devices200include desktop and laptop computers, tablets, mobile smartphones, and devices that manage networks, such as devices that can manage a WLAN that can be connected to multiple communication ports21on different tools10simultaneously.

The computing devices200and/or web services210may also include operations or functions that can notify tool10managers and/or tool users about pertinent changes to tools10paired with or connected to the computing system250via a display message, a SMS text message, an email or other alert. Pertinent changes may include, but are not limited to, diagnostic information about one or more tools10, such as temperature information or warnings, information indicating that a particular tool is no longer detected within the network, e.g., the tool is no longer detected by the WLAN, or information indicating that a particular tool has repeatedly failed recent crimps.

Referring again toFIG.10, one such computing device200may be a smartphone running an application (also known as an “App”) used to store, display and analyze the cycle information and other tool information. The application running on the smartphone may also be referred to herein as the “App”. Such an App may provide the tool manager and/or tool user with the ability to review one or more cycle data records and to add additional information, e.g., alpha-numeric text comments or notes, to the cycle data record of a crimp including a data flag. The computing devices200either alone or in combination with the web services210may also perform data processing functions to analyze and display the cycle information and other tool information. These functions may include filtering cycle information to identify, for example, crimps formed at particular job sites, crimps formed between particular dates and times, or crimps where the maximum force is less than a predetermined threshold value. The data processing functions may also include generating a geographic map or a satellite based image of a geographic location showing the locations of the crimps formed by the tool10. Filtering criteria may also be used to display only a subset of crimps, such as crimps where the maximum force applied to form the crimp was insufficient representing crimps that failed.

In the exemplary embodiment of a computing system250shown inFIG.10, the computing system250includes cloud based web services210, such as the AWS provided by Amazon.com Inc., a computing device200, e.g., a mobile smartphone, running a mobile App connected to a tool management application running on the web services210and a laptop computer200running a browser connected to the tool management application running on the web services210. When the tool10communicates with the computing device200, e.g., a mobile smartphone, over Bluetooth, the smartphone200preferably transfers cycle information and other tool information using AES-128 bit encryption. When the computing device200, e.g., a mobile smartphone, uploads this cycle information and other tool information to the web services210, the smartphone uses AES-256 bit encryption. Additionally, the web services210may use a .Net 4.6 framework to communicate with the mobile Apps residing on the mobile computing devices200and the web services database214, as well as any push notifications. The web services based tool management application may utilize HTMLS, CSS, Bootstrap 4, JQuery 3.4.1 to support the user interface with the web services and functions. The web services server uses RDS-MySQL 6.07 database214, EC2 for web hosting, S3 for FTP, Enabled Apple and Android Push notifications.

Referring toFIG.11, an exemplary page display of a computing device200, such as a laptop computer, connected to the tool management application running on the web services210via a browser is shown. In this example, cycle information and other tool information for one or more tools10has been transferred into the web services database214via, for example, a computing device200running the mobile App. For example, a vendor of electrical installation services (a tool manager) may have cycle information and other tool information from each of the technicians (a tool user) working on its projects transferred into the web services database214, or a project manager (a tool manager) for a building site may have cycle information and other tool information from a number of vendors (tool users) transferred into the web services database214. This cycle information and other tool information may be used to check the quality of the work being performed and to track the progress of the work. The cycle information and other tool information from the web services database214may be displayed in a window titled “Crimp History” of a web page loaded into a computing device200, e.g., a laptop computer, which is connected to the tool management application running on the web services214via a browser. This cycle information and other tool information in the Crimp History may be presented as a table showing an index number for each crimp, e.g., “Crimp No.,” a time stamp for each crimp, e.g., a date and time for each crimp, a crimp “Status” identifier showing whether sufficient pressure or force was applied to form the crimp. The crimp Status may be logical value that may be presented as a “Pass” or “Fail” or the crimp Status may be represented as the pressure or force applied to form the crimp, and the location where the crimp was formed, in for example, the latitude and longitude of the tool10when the crimp was formed.

Continuing to refer toFIG.11, a user can filter the cycle information displayed by the computing device200, e.g., a laptop computer, of the computing system250by entering filter criteria. Non-limiting examples of filter criteria include the identity of a particular tool10in a “Tool” field, tools with a particular status in a “Status” field, a date crimps were made in a “Date” field, and a user defined alpha-numeric search in a “Search” field. To illustrate, if a user selects or enters a particular tool10in the “Tool” field, such as the “PAT750L5DC0V” tool, as seen inFIG.11, each of the cycle data records222of cycle information formed by that tool10would be displayed in the Crimp History window. In this exemplary embodiment, the cycle information displayed for each cycle data record222includes a time stamp, whether the crimp was formed with sufficient force, indicated by a logical Pass or Fail status value, and the location where the crimp was formed. According to one embodiment, the designation whether the Status field of a cycle data record has a Pass or Fail status may be indicated by the color of the typeface (or font) used to display the cycle data record222, for example, a green font may be used if the status is Pass and a red font may be used if the Status is Fail. A wide variety of filter criteria can be applied to filter the cycle information stored in the web services database214for presentation to the tool manager or the tool user. For example, a tool manager or tool user could query the web services database214to show only cycle data records222which have a Status of “Fail,” or to show cycle data records formed within a date or time range, or to show cycle data records222formed within a certain geographic range, and the like. Other display windows (not shown) could be provided to allow a user to enter Boolean logic operators (AND, OR, NOT, etc.) to combine filters using techniques known to those of skill in the relevant field could also be applied.

According to one embodiment, the cycle information retrieved from the web services database214based on the selected or entered filter criteria can also be displayed graphically on a map, as seen inFIGS.11and12. In the exemplary embodiment ofFIGS.11and12, the location of each of the crimps for tool PAT750L5DC0V (that fit the filter criteria) are overlaid on the map. Icons224can be used to display the location of the crimps on the map. The icons224may have a typographic designation or color coding, e.g., Green or Red, to show that the particular crimp has a “Pass” or “Fail” status. The map may include landmark information, such as the location and names of towns, streets, power lines, transmission towers, buildings and the like to provide the tool manager or the tool user with information to show the location where crimps or other tool operations were performed. According to one embodiment, the cycle information from multiple crimps and/or other tool operations can be used to track progress on a job site, grounding grids, or other work sites. According to another embodiment, instead of providing a map showing the locations of crimps, the web services210can analyze the cycle information to determine a street address of the job site where the crimps where formed. The street address of the crimp could be provided as text.

Referring now toFIGS.13-17, the operation of an exemplary embodiment of a mobile app running on a smartphone as a computing device200will be described. As shown inFIG.13, after the App is connected to the tool10, an exemplary tool information page of the App is displayed on the smartphone display. Selecting the “Sync with Cloud” icon initiates a sync operation between the App and the web services210of the latest cycle information associated with the tool10identified in the “Tool Information” fields. Selecting the “Change Nick Name” field permits the tool manager or tool user to assign an identifier to each unique tool10paired with the App and identified in the Tool Information fields. Such identifiers may include, but are not limited, to the user's custom serialization number, the owner of the tool10, the number of the truck in which the tool10is stored. Selecting the “Crimp History” icon displays the page shown inFIG.12. The crimp history page presents cycle information as a list of cycle data records222with an index column “Crimp No.,” a time stamp column “Date & Time,” and an “Output Force” column. In this exemplary page, the tool manager or the tool user can filter the records by date by selecting the “Calendar” icon to list cycle data records222for a particular tool10identified in the Tool Information fields, seen inFIG.13, to display only those cycle data records from the selected date or date range. The column headers, namely the “Crimp No.” and the “Output Force” headers, can be selected (e.g., tapped) to toggle between ascending or descending order of crimp numbers, or to filter crimps to those that have an Output Force of Pass or Fail. The Crimp History page may or may not include additional icons to represent the cycle information associated with each cycle data record222. For example, and referring toFIG.16, an icon216may be used to represent whether the tool10successfully recorded in memory32the location where the crimp was formed, an icon218can be used to represent whether or not there are comments saved for a particular cycle data record222, or an icon220used to represent whether or not the cycle data record222includes a flag.

If an individual cycle data record222, e.g., the Crimp No. 76 row of the cycle information displayed inFIG.14, is selected by the tool manager or tool user, the cycle data record222for Crimp No. 76 would be presented on the display of the mobile computing device200, as seen inFIG.15. From this window, the tool10manager or tool10user is able to review existing comments associated with the cycle data record or enter new comments about the selected cycle data record. It is noted that these comments can also be reviewed, entered and edited through the laptop computer as a computing device200running on a browser connected to the tool management application running on the web services210.

Referring again toFIG.13, if the tool manager or the tool user selects the “Service History” icon, the page shown inFIG.17is displayed. In this exemplary embodiment, the tool manager or the tool user can review, analyze and manage one or more tools10using the service history of the one or more tools10with service history records stored in the web services database214. As described above, cycle information about one or more tools may be uploaded to the web services database214. In addition, service history information associated with the one or more tools may also be added to the web services database214using a computing device. The cycle information and service history information for each tool may then be used when displaying the Service History. As shown inFIG.17, each service history data record may include, for example, a unique tool identification number as a “Tool Event,” the total number of crimps performed by the specific tool at the time of service as a “Total Crimps at Service,” and a time stamp as “Date & Time.” Through the Service History page, the tool manager or the tool user can filter service history data records by date by selecting the “Calendar” icon in the top right of the page to display only those service history data records from the selected date. One or more column headers, which in this example the “Service No.” headers, can be selected (e.g., tapped) to toggle between ascending or descending service numbers.

Referring again toFIG.13, if the tool10manager or the tool10user selects the “Unregister Tool” icon, the tool10manager or the tool10user can unregister the tool10from the users account in the computing system250. If the tool10manager or the tool10user selects the “Activate Light” icon, an instruction is sent from the computing device200to the tool10which is received at the communication port21and processed by the controller24. The controller24then activates the work light26on the tool10, seen inFIG.1, causing the work light26to illuminate. The work light26can illuminate for a continuous period of time or the work light26can blink two or more times so that the tool10can be located by the tool manager or the tool user. For example, activating the work light26as described can be used to easily and quickly determine which tool10the computing device200is connected to, as well as it can assist with locating the tool10if it is lost in a dark area. If the tool manager or the tool user selects the “Admin Security” icon, the App running on the computing device200can toggle between a “secured” operation mode and an “unsecured” operation mode. In the “secured” mode, only the tool manager or the tool user who has registered the tool10with the web services210or others authorized by the tool manager or the tool user to access the tool manager's or the tool user's account, is able to connect to the tool10and view, comment, and/or sync cycle information with the web services210. In the “unsecured” mode, anyone with a computing device200running the App can connect to the tool10to view, comment and/or sync cycle information with the web services210. If the tool manager or the tool user selects the “Edit Tool Notes” icon, a text field is presented by the App that allows the user to input alpha-numeric comments about the tool10identified in the Tool Information fields. An icon also allows the user to cancel their comments. This feature supplements the flag comments that may be entered which are focused on particular crimps. The inputted comments could be used to record instances when the tool10was dropped, notes about where and how the tool10should be stored, names, dates, or purchasing information. If the tool manager or the tool user selects the “Auto-Shut off” icon, the App running on the computing device200can toggle between “off” and “on” modes. In the “off” mode, the tool10operates such that whenever an operator control, e.g., trigger switches42or44, is activated the motor18activates and whenever the operator control, e.g., trigger switches42or44, is deactivated the motor18deactivates. In the “on” state, after the operator control is activated so that the motor18is activated to begin a crimp cycle, when the controller24determines the crimp cycle is complete the controller24automatically deactivates the motor18to prevent the tool10from re-pressurizing after the relief valve29has released. This mode reduces energy consumption from the battery20, reduces the force needed to trigger the return operator control, e.g., trigger switch42, limits the wear on the tool10, can initiate an auditory and/or tactile notification to the tool user the crimp cycle has completed, and can initiate the visual indication from the light25as described above.

The App running on the computing device200may also include “Frozen Timer” and “Job Scheduling” operations. With the Frozen Timer operation, a tool user can specify an amount of time on their account for which the tool can remain unconnected to a paired computing device200before being deactivated or frozen (“Time-to-Freeze”). This Time-to-Freeze may be entered in units of days, weeks, months or combinations thereof. A page may be presented to the tool user with a field that allows the tool user to input an integer to set the Time-to-Freeze, or the tool user may be presented with preset selections, such as “no time, 1 week, 1 month, or 3 months.” When the user's account has a Time-to-Freeze set, whenever a tool10connects to a computing device200, e.g., a mobile device, paired with or logged into the registered account for that tool, the tool10will check the current date and determine an end date (“Freeze Date”) based on the Time-to-Freeze. For example, if a tool user has set the Time-to-Freeze for 1 week and pairs the App to a tool10on October 1st, the tool10will determine the Freeze Date as October 8th. Thereafter, whenever a battery20is installed in the tool10and an operator switch, e.g., trigger switch44, is activated, the controller24in the tool10compares the current date to the Freeze Date. If the current date is after the Freeze Date, which in this exemplary embodiment is after October 8th, the tool10will be rendered “frozen” so that the controller24will not activate the motor18in response to the operator control being activated. In some embodiments, the tool10may provide the tool user with visual or audible feedback that the tool has been rendered inactive, such as by flashing the LED25and/or the work light26or by generating a sound. If the tool10is in the inactive mode the tool can be returned to the active mode the next time the tool10is paired with the computing device200registered for that tool100and syncs the tool's cycle information with the web services database214, which then set a new Freeze Date.

With the Job Scheduling operation, an operator can upload a file using a mobile application or web browser to the web services database214containing information about a job or project that is scheduled to be performed for a particular tool10. This file may be in a format such as .txt, .xls, or .csv. In another embodiment, the operator may be able to enter job scheduling details directly into the computing system database214using a computing device200logged into the Tool Application website without uploading a standalone file. The web services210functions on the database214will parse through the file to determine details about the job to be done and creates a data object with the job details. For ease of description, the data object may also be referred to herein as the Job File. The Job File can be modified. The details of the Job File include but are not limited to: Job Name, Job Location, Employee performing the Job, Expected Start Date, Expected End Date, and List of Tasks, with each Task having a Task Number, Task Name, and an Expected Number of Crimps. The user can then assign this job to a particular tool or tools10in the web services database214. When a user connects to the tool10scheduled for the particular job via the communication port21an indicator on the display of the computing device is rendered or activated indicating that this tool has been assigned a Job. The user can elect to view or start the job. When viewing the job, the user can see all the details stored in the Job File. Once the user elects to start the job, the device records the Actual Start Date and Time to the Job File. The display on the computing device200then shows a new page or window which may show, for example, a Task Number, a Task Description, the Expected Number of Crimps, and a numeric counter labeled as Crimps Since Task Start. When the user makes the first crimp in a task, the computing device200will automatically add an alpha-numeric text comment to that crimp indicating that the task has been started, e.g., “[Task Number] [Task Name] started”. As the user performs crimps, the Crimps Since Task Start counter increments accordingly. Once the user has completed the task, the user can select a button labeled “Next Task” on the computing device200to advance the display to show the next Task page or window. Crimps Since Task Start will be recorded to the respective Task in the Job File. The computing device200automatically adds the comment to the latest crimp “[Task Number] [Task Name] completed.” On the computing device display, the Task Number, Task Description, Expected Number of Crimps, will be updated to the next sequential task in the Job File, and Crimps Since Task Start will reset to zero. Once the user has advanced to the last task in a Job File, a button labeled “End Job” replaces the button labeled “Next Task” on the computing device display. Once “End Job” is selected, the computing device200records the Actual End Date and Time into the Job File. The computing device200automatically adds the comment to the latest crimp “[Task Number] [Task Name] and [Job Name] completed.” Then the tool10returns to normal use. In some embodiments, while in the middle of performing a task, the computing device200may allow the user to elect to pause a job. Crimps made during the pause are not counted towards the task currently displayed on the computing device200, but the crimps are added to the tool's crimp history. In addition, the computing device200automatically sets the flag and adds a comment to any crimps made during this pause such as “Task was paused during this crimp”. When the web services210generates a report for this tool10, the user may select to generate the report for a Job File rather than Start and End Dates. The generated report may show overall information from the Job File, and may determine a score for each task based on the number of crimps made vs the expected number of crimps. The report may also show a normal report output for all the crimps that were made between the Actual Start and End Date and Times.

According to a further embodiment, non-hydraulic mechanical crimping tools may also be equipped to determine, record, and communicate the location of crimps. Still further embodiments of the disclosure encompass tools other than those used to form crimps that are equipped with a location sensor to detect and record a location where the tool is used. These tools may include other hydraulic tools and non-hydraulic tools. Such tools might include welders, cutting tools, grinders, drills, and the like. According to one embodiment, geographic location information from these tools is also provided to the computing system and stored in the database. According to this embodiment, filtering criteria may be applied to show when and where these tools are used.

Referring toFIGS.18-33, as set forth above, the present disclosure also contemplates embodiments of computing systems250that include one or more tools10, one or more computing device200, e.g., smartphones or other computing devices, and the web services210. The computing system250also includes the App running on the smartphone that allows a user to take or upload an image (or picture) of one or more crimps and links the image (or picture) to a particular cycle data record associated with a crimp taken by a particular power tool10. For ease of description, the images (or pictures) taken by the computing devices200may also be referred to collectively as the “image” in the singular and the “images” in the plural. The images may be stored in the memory of the computing device200and/or viewed on the homepage. These images stored in the memory of the computing device200can then be viewed on the display of the computing device200using the App. The images can also be shared amongst tool managers, tool users or other parties, e.g., contractors or inspectors, using the computing device's200communication features described herein, or the images can be uploaded from the computing device200to the web services210or other internet based computing systems using the communication features described herein. The images would then be stored in the database214of, for example, the web services210. These images stored in the database214can then be viewed via the website. The images may also be uploaded to the tool10the images are associated with and stored in the memory32of that tool10. The images stored in memory32can then be viewed on, for example, an LED display31included in the tool10.

A process for imaging a crimp made by a tool10using a computing device200and uploading the image to a web service210will be described with reference toFIG.18-33. The process for imaging a crimp made by a tool10using a computing device200and uploading the image to a web service210will be described with reference toFIG.18-33. Initially, a tool user will be at a job site and making one or more crimps as described herein using the tool10. When each crimp is made by the tool10, the tool creates a cycle data record222for the crimp which is stored in memory32of the tool. As described above, the cycle information stored in the cycle data record222may include a time stamp, location information of the tool10when the crimp was made, and the crimp status when the crimp was made, seen inFIG.12. As described above, the time stamp may include, for example, a time and date when the crimp was made. The location information may include, for example, latitude and longitude coordinates of the tool10when the crimp was made. The crimp Status may be logical value, such as a “Pass” or “Fail” or the crimp Status may be represented as the pressure or force applied by the tool to form the crimp.

If when making a crimp the tool user is unsure that the crimp meets predefined requirements the tool user may retrieve their computing device200, here a smartphone, and launch the App to connect to or pair with the tool10. Examples of causes of such unsureness may be; 1) misaligned die positioning on, for example, the lug connector110(seen inFIG.6) or the splice connector114(seen inFIG.7), 2) too much cable stripped, or 3) the tool user released the trigger42or44of the tool10too early. Once the tool10and smartphone200are paired, the App can sync with the tool10to retrieve the crimp history for the tool10and other tool information from the tool which is displayed on the display of the smartphone200. The retrieved the crimp history for the tool10and other tool information may be stored in the memory of the computing device200. Referring toFIGS.14,15,19and20, the crimp history retrieved may include all cycle data records222for the tool10stored in the tool memory32, or the retrieved crimp history may include a portion of the cycle data records stored in the tool memory32, such as by a date range selected using the calendar icon. The other tool information may include, for example, information about the tool, such as the tool nickname, the tool model number and the tool serial number, and comments entered into the crimp comment field of the App for each cycle data record. The retrieved crimp history and other tool information may be upload to the web services database214, seen inFIG.10.

With the crimp history and other tool information stored in the memory of the smartphone200or the database214of the web services210, the App or website, can be used to retrieve and present the crimp history for the tool10for viewing by the tool user. As shown inFIG.18, the tool user viewing the crimp history can then search for the cycle data record of the crimp or crimps deemed to be questionable. As an example, and using the smartphone App, the tool user could base the search for the relevant crimp or crimps on the time stamp information, e.g., a certain date and time, or based on the order of the cycle data records defined by, for example, a crimp number. As shown inFIG.19, a crimp history of ten cycle data records222are displayed on the smartphone via the App. Once the relevant crimp or crimps are located in the crimp history, the tool user can select the relevant cycle data record222being displayed by the App on the smartphone200by, for example, tapping the relevant cycle data record222. As shown inFIG.19, the relevant cycle data record222is the record for Crimp No. 3. When the relevant cycle data record222is tapped, the App loads a new page presenting detailed cycle information from the cycle data record as shown inFIG.20(FIG.18, Step1). It is noted that is this point, the tool user can enter comments into the Enter Comment field using the App as shown inFIG.20. As seen inFIG.19, each cycle data record222does not include a camera icon which means that the “Crimp Image” flag for those cycle data records222is set to “0” representing that no crimp image has been associated with those cycle data records. In addition, at Step2, by looking at the cycle information for the cycle data record222for Crimp No. 3 displayed inFIG.20, the tool user can determine by the presence of an “Add Crimp Image” button that an image of the crimp has not been associated with the cycle data record. Pressing the “Add Crimp Image” button (FIG.18, Step3), opens or launches the App's built-in camera function in a new page on the computing device200, e.g., a smartphone, where a camera view is displayed, as seen inFIG.21. At this point, the tool user has the option of taking a picture using the App's built-in camera function, or the tool user can select an image from the smartphone's200image gallery, i.e., the images stored in the memory of the smartphone (FIG.18, Step4). If the tool user takes a picture, the image is presented to the tool user in a “Crimp Image Preview” display, seen inFIG.22, and if the image is acceptable the tool user can select the “Save Photo” button to store the image in the memory of the smartphone200(FIG.18, Step5). If the image is unacceptable, the tool user can select the “Retake” button to return to the App's built-in camera function ofFIG.21so that a new picture of the crimp can be taken. The tool user can also press the cancel button. When saving the image using the “Save Photo” button after either taking a picture or selecting an image from the gallery, the image is also uploaded to the web service210(FIG.18, Step5) and stored in the database214of the web service210(FIG.18, Step5). When the image is uploaded to the web service210and stored in the database214, the image is assigned a file name that includes the Serial Number of the tool10and the Cycle Data Record Index Number which is the Crimp Number seen inFIG.20. As an example, when the image is uploaded to the web service210(FIG.18, Step6) and stored in the database214(FIG.18, Step7), the image can be assigned the following address:

where the “LT12312346” in the folder name and in the file name represent the Serial Number of the tool10and the “3” in the file name represents the Cycle Data Record Index Number which in this example is 3 to match the “Crimp Number” shown inFIGS.19and20. By including the “Serial Number” of the tool10and the “Cycle Data Record Index Number” for the relevant cycle data record222an association is made between the stored image and the cycle data record. In addition, the “Crimp Image” flag in the cycle data record stored in the web service database214associated with the image is set to “1” reflecting that there is an image associated with the cycle data record. Once the image is uploaded to the web services database214, the image can be retrieved and viewed through a browser from a computing device200connected to the web service210, or through the App or another App of a computing device200connected to the web service210. As noted above, the user may choose to associate an image with a cycle data record222from a computing device200via the web service210. In such an instance, the user would retrieve the crimp history for the tool which is displayed on the display of the computing device200similar to that described above, and the user would select the relevant cycle data record222using, for example, the cursor of the computing device200. The cycle information associated with the selected cycle data record222is then displayed on a new page on the display of the computing device200, seen inFIG.23. The operator may also close the displayed information. It is noted that the cycle data record222did not include a camera icon such that the “Crimp Image” flag for the cycle data record222was set to “0” representing that no crimp image has been associated with those cycle data records. The user can associate an image to the selected cycle data record by clicking on the “Add Crimp Image” button which opens an “Add Image” page, seen inFIG.24. From the “Add Image” page the user can choose an image previously stored in the web service database214or other location by clicking on the “Choose Image” button. When the image is uploaded to the web service210and stored in the database214, the image is assigned a file name that includes the Serial Number of the tool10and the Cycle Data Record Index Number which is the Crimp Number seen inFIG.23as described above.

If at Step2the crimp history displayed by the App is shown inFIG.25, there is a camera icon in each cycle data record222. The camera icon appears in response to the “Crimp Image” flag in the cycle data records stored in the web service database214associated with the images is set to “1.” When a cycle data record222is selected by tapping on the cycle data record, the cycle information for the selected cycle data record, here the cycle information for Crimp No. 3, is displayed on the computing device200, e.g., smartphone, by the App, as seen inFIG.26. Pressing the “View Crimp Image” button (FIG.18, Step8) the crimp image is retrieved from the web service database214and displayed by the App on the display of the computing device200, e.g., smartphone, as seen inFIG.27. To retrieve the crimp image associated with Crimp No. 3, the App makes a request to the Web Service210to retrieve the image associated with Crimp No. 3 for the tool10with Serial No. LT12312346, by going to the following web service210address:

As noted above, the user may choose to retrieve and present the crimp history for the tool10for viewing on a computing device200via the web service210. In such an example, when a cycle data record222is selected by the user from the crimp history displayed on the display of the computing device200, the cycle information for the selected cycle data record, here the cycle information for Crimp No. 3, is displayed on the computing device200, as seen inFIG.28. Pressing the “View Image” button causes the crimp image to be retrieved from the web service database214and displayed on the display of the computing device200, as seen inFIG.29. To retrieve the crimp image associated with Crimp No. 3, the web services makes a request to the to retrieve the image associated with Crimp No. 3 for the tool10with Serial No. LT12312346, from the database214by going to the web service210address set forth above.

Using the tool10, computing device200and web service210described herein, a tool user can upload an image for a crimp (as explained above) and then contact their supervisor/inspector to review the image they just uploaded to the web service database214for that crimp. The tool user may also add a comment to the relevant cycle data record222, such as “Check out the image for Crimp No. 3 on ‘Bob's Tool.’ How does the crimp look to you?” The supervisor can then retrieve the image in their App or their web browser and can make a comment saying that the crimp was reviewed and either passed or needed to be redone.

Referring toFIGS.30-33, while logged into the computing system250on a web browser, the user has the ability to generate reports, e.g., PDF reports, for specific tools10. Such reports may include the Crimp No., the timestamp (e.g., date/time) when crimps were made by the tool10, the location (e.g., GPS location) of the tool10when the crimp was made, and verification of the crimp based on force or pressure data from the tool. If the crimps have any comments or images associated with them, they will be visible in the report as well. Exemplary images and comments from the questionable crimps described herein can be saved and associated to the relevant crimps so that any reports generated show that such information and provide full traceability of crimps.

Besides images of connectors, images of other objects could be used as well. For example, if using the tool10in a datacenter when GPS may be unreliable, tool users may instead form the habit of using the crimp comments to indicate location descriptions to help track crimps, e.g. “First crimp in cabinet B-32”. With the crimp image feature described herein, instead of typing out these descriptions, tool users can now take a picture of the location as well as of the crimp. A picture of the location itself could be helpful for locating the crimp at a later date, or a close up picture of identification information associated with the location of the crimp, e.g., a nameplate or label of cabinet B-32. Other images that could be taken include images of the tool10to document wear and tear of the tool over its lifetime. Images of people could be taken to indicate when a tool10was passed off to someone else. An image could be taken of a signed safety review checklist and uploaded with the first crimp of each day to indicate the operator was briefed on the safety measures for that work area. The user has flexibility to decide how and what they would like to take images of and associate them to crimps for their own tracking and responsible traceability.

In other exemplary embodiments, the tool10could include a camera to take pictures so that the tool10can store images in the tool's10memory32without using the App or browser. If some time has passed before the tool user uploads an image, there could be the option to suggest certain crimps based on the image's timestamp. Multiple images could be associated per crimp instead of just one, and visual processing could be done on the crimp images to automatically inspect the crimps to determine their viability.

As shown throughout the drawings, like reference numerals designate like or corresponding parts. While illustrative embodiments of the present disclosure have been described and illustrated above, it should be understood that these are exemplary of the disclosure and are not to be considered as limiting. Additions, deletions, substitutions, and other modifications can be made without departing from the spirit or scope of the present disclosure. Accordingly, the present disclosure is not to be considered as limited by the foregoing description.