Welding processes are utilized in virtually all industries, from manufacturing, to power production, to shipbuilding, to maintenance, just to mention a few. Conventional welding systems have operated as stand-alone installations, either fixed in factory or service center settings, or mobile, such as for adaptable manufacturing and field service. In many scenarios, it is increasingly useful to set performance criteria, monitor performance, and/or analyze performance for a particular welding task or job. In some situations, it may be beneficial to associate an operator to the particular welding task or job the operator is performing. In particular, it is increasingly useful to set, monitor, track, and/or analyze operator performance for the particular welding task or job.
Systems designed to associate and/or track an operator with a particular welding system, location, task, or job, however, have not reached a point where they are easily and effectively utilized. For example, in some current systems, a welding operator's identification card is scanned or identification/authenticating information is entered. Accordingly, there is a need for the efficient identification and/or authentication of an operator prior to commencing a welding task or job at a particular welding system or location. Accordingly, improvements in these areas may be beneficial to maintain operator performance and/or retrospectively review operator performance.
In one embodiment, a welding system having a welding power supply, a wire feeder coupled to the welding power supply, and a welding torch coupled to the wire feeder and configured to output wire from the wire feeder is provided. In particular, the welding system includes a wireless module (e.g., gateway) disposed within a component of the welding system, or as an independent component within the welding system. For example, the wireless module may be disposed within the welding power supply, the wire feeder, or the welding torch. The wireless module is configured to wirelessly transmit to and receive welding information, such as operator identification information, from a wireless personal device. The wireless personal device is uniquely associated with a welding operator operating the welding system.
These and other features, aspects, and advantages of the present invention will become better understood when the following detailed description is read with reference to the accompanying drawings in which like characters represent like parts throughout the drawings, wherein:
While only certain features of the invention have been illustrated and described herein, many modifications and changes will occur to those skilled in the art. It is, therefore, to be understood that the appended claims are intended to cover all such modifications and changes as fall within the true spirit of the invention.
Embodiments of the welding system described herein may include one or more personally allocated devices having wireless capabilities (e.g., smart phone, tablet, notepad, helmet, audio input device, personal clothing, tags, laptop, etc.) that are personally allocated to a welding operator. In particular, the personally allocated device may include information that is captured by the welding system to identify and/or authenticate the welding operator. As explained in greater detail below, the personally allocated device may be configured to wirelessly communicate with one or more components of the welding system, such as a wireless module or gateway. In certain embodiments, the personally allocated device may establish wireless communications with the wireless module or gateway with one or more different binding processes, as further detailed below. In other embodiments, the personally allocated device may establish more direct wireless communications with the wireless module or gateway via one or more different wireless communications standards, as further described below. Once wireless communications is securely established, the paired devices may transfer various welding related information, such as operator identification information.
In certain embodiments, the welding operator may be automatically identified via the personally allocated device when the operator is proximate to the welding system. Further, upon identification, the welding system may be configured to authenticate the operator for a particular welding system, location, or task. In some situations, the welding system may load an operator profile corresponding to the welding operator, which may, for example, have pre-set parameters that limit the operator's functions. In particular, the welding system may monitor and track operator performance, which may be communicated to a cloud storage or service. Furthermore, in certain embodiments, the personally allocated device may be utilized by the operator to view data, determine current settings or parameters, control one or more welding parameters, control a power source, determine deficiencies or configuration problems, troubleshoot, and so forth.
Turning now to the drawings,
In certain embodiments, the system 10 includes a monitoring/analysis system 18 that communicates with the welding systems 12 (and any ancillary support equipment) to collect information. For example, the welding systems 12 include sensors, control circuitry, feedback circuits, and so forth that allow for the collection of welding parameter data. In some situations, system parameters such as arc on time are analyzed and collected, and may reflect when welding arcs are established in times during which welding arcs are maintained. In addition, currents and voltages will commonly be sensed and data representative of these will be stored. Additionally, the monitoring/analysis system 24 may collect information directly from other systems or from other support components within the system 10 that collect and store the data. The data will typically be tagged with such identifying information as system designations, system types, time and date, part and weld specification, where applicable, operation identifications, and so forth. In addition, the data may be tagged to identify the welding operator associated with the data collected.
The system 10 includes a cloud 22, which may refer to various evolving arrangements, infrastructure, networks, and the like that will typically be based upon the Internet. The term may refer to any type of cloud, including a client clouds, application clouds, platform clouds, infrastructure clouds, server clouds, and so forth. As will be appreciated by those skilled in the art, such arrangements will generally allow for third party entities to receive and store data related to welding applications, transmit data to welders and entities in the welding community for welding applications, provide software as a service (SaaS), provide various aspects of computing platforms as a service (PaaS), provide various network infrastructures as a service (IaaS) and so forth. Moreover, included in this term should be various types and business arrangements for these products and services, including public clouds, community clouds, hybrid clouds, and private clouds. Any or all of these may be serviced by third party entities. Moreover, servicing by third party entities is particularly attractive in many contexts because resources discussed below can provide products and services that are otherwise unavailable to the welding community. However, in certain embodiments, particularly large entities with distributed manufacturing operations, private clouds or hybrid clouds may be attractive to allow for sharing of welding-relating product and services across the enterprise.
The cloud 22 may be configured for two-way communications with components of the system 10, such as to the monitoring/analysis system 18. In certain embodiments, various wired connections 24 may be utilized for such communications, and may include conventional telephony systems, cable systems, hardware-based Internet communications systems, including routers, servers, gateways, and any other hardware, software, and firmware required with such communications. In some embodiments, various wireless connections 26 (e.g., wireless communications) may be utilized, and may include cellular communications, various wireless protocols, satellite communication, and the like. Further, in some situations, the cloud 22 may communicate to a network 28, which may be configured to receive and transfer information from a plurality of monitoring/analysis systems 18 within one or more systems 10. As noted above, communications between the cloud 22 and the network 28 may be wired or wireless, or may include various intermediate devices, such as desktop and portable computers, hand-held computing devices, cellular and smart telephones, and so forth.
The system 10 allows for the grouping, analysis, and presentation of the information collected by the monitoring/analysis system 18 on one or more operator interfaces 20. In many cases the operator interface 20 may comprise a conventional computer workstation, a handheld device, a tablet computer, or any other suitable interface. A number of different device platforms may be accommodated on the operator interface 20, and webpages containing useful interfaces, analysis, reports, and the like will be presented in a general purpose interface, such as a browser. A wide range of information may be processed through the operator interface 20, such as welding job/work order identification, machine performance feedback to the operator, alerts to the operator, operator inputs, barcodes (e.g., barcodes of materials, work orders, or other identifiers), and so forth. In particular, the system 10 may include identification, verification, and authentication features, such as prompting the operator (e.g., user) for user names, passwords, and so forth, via the operator interface 20. The identification, verification, and authentication features may be provided to the system 10 by the operator via the operator interface 20. In some embodiments, such as those detailed below, identification information associated with the welding operator may be automatically captured by the system 10.
For example, in certain embodiments, one or more personally allocated devices 30 may be configured to establish wireless communications 26 (e.g., wireless communications channel) with the welding system 12. The personally allocated device 30 may be any device that is associated with a particular welding operator, such as a smart phone, a tablet, a notepad, a welding helmet, an audio input device, a personal clothing item, a personal welding clothing item, an employee tag, a laptop, a personal welding tool, or any item or device that may be configured with wireless capabilities. In particular, the personally allocated device 30 may be configured to wirelessly communicate with one or more components of the welding system, such as a wireless module 32 or a gateway 32 disposed within a particular welding system 12 or location 16, to exchange welding related information. For example, certain personally allocated devices 30 may be configured with a wireless module 34 to wirelessly communicate with the gateway 32. Other personally allocated devices 30, such as a smart phone or a tablet, may be pre-configured with wireless capabilities.
In some embodiments, the personally allocated devices 30 may automatically establish wireless communications 26 (e.g., wireless communication data and/or authentication channels) with the gateway 32 to enable an exchange of information. The channel 26 may be established using any suitable protocol when the device 30 is proximate to the gateway 32 (e.g., within a particular range, distance, or radius). For example, wireless communications may be established using the IEEE 802.15.4 standard, and may be, for example, ZigBee, WirelessHART, or MiWi protocols. Additionally or alternatively, wireless communications may be established using the Bluetooth standard, one or more of the IEEE 802.11 standards, an ultra-wideband (UWB) standard, or a near-field communication (NFC) standard. In certain embodiments, the personally allocated device 30 may establish wireless communications 26 (e.g., wireless communication data and/or authentication channels) with the gateway 32 when a binding or pairing process is activated to enable an exchange of information, as further described in detail with respect to
Upon either automatically or actively establishing wireless communications between the personally allocated device 30 and the gateway 32, identification information corresponding to the operator may be transferred, which the system 10 may use to verify and authenticate the operator. For example, in certain embodiments, the monitoring/analysis system 18 or the cloud 22 may include a plurality of profiles, where each profile corresponds to a different user or operator. In some situations, the user profile associated with that operator may be locally loaded and displayed, and may include information related to operational parameters, permissions, or limitations set for the operator. In this manner, the system 10 may be configured to enable or disable one or more functions of the welding operator (e.g., limit operational functionalities of the welding operator) based on the permissions allocated to the operator for that particular welding system 12, location 16, experience level, welding task/job, or any other factor. In some embodiments, the operator's functions during a particular welding task/job are monitored and tracked, and the data collected during this period may be associated with the user profile of the operator. Indeed, after an initial authentication and verification of the operator, other forms of welding related information may be transmitted via the wireless communications 26, as further explained below with respect to
In some situations, the data collected may be stored in a remote location (e.g., the cloud 22 or the monitoring/analysis system 18) with a tag associating the data to a user profile. In such situations, the data collected may be automatically transferred to the cloud 22. Alternatively, in some situations, the data collected may be stored locally at the gateway 32 if communications to the cloud 22 are unavailable via the network 28 or the monitoring/analysis system 18, and may be transferred to the cloud 22 (or other storage devices) at a later time. It should be noted that data associated with a particular operator may be monitored and tracked during the operation, or may be retrieved and analyzed to measure operator performance at a later time.
In the embodiment illustrated in
In certain embodiments, the operator interface 20 may be incorporated with the monitoring/analysis system 18, and may be configured to receive a user input to determine a weld process, a weld application, an operator identification or authentication, etc. A controller 58 utilizes a processor 60 to execute instructions loaded to the monitoring/analysis system 18 and/or stored into a memory 62 to determine the weld process and/or the weld variables. For example, in certain embodiments, the monitoring/analysis system 18 may load a user profile associated with a particular operator, and may limit the operational functionalities of the operator based on the user profile. In particular, as noted above with respect to
For example, in the illustrated embodiment, the gateway 32 may be incorporated into the welding power supply unit 36. In some situations, the gateway 32 may be disposed proximate to a welding control panel 59 on the welding power supply unit 36, which may include a display and/or a human machine interface that displays information related to the gateway 32 (e.g., status, connectivity, etc.). In other embodiments, the gateway 32 may be incorporated into the wire feeder 38, or may be a standalone component of the welding system 12. As noted above with respect to
In some embodiments, the gateway 32 and the personally allocated device 30 establish wireless communications 26 via a binding or pairing process. The binding/pairing process involves activating the association between the gateway 32 and the personally allocated device 30 in order to establish wireless communications 26, thereby securely enabling the exchange of welding related information. For example, in some situations, a personally allocated device 30, such as a computing device 66 (e.g., smartphone, iPad, portable electronic device, etc.) associated with a particular user or operator, may scan a barcode disposed on the welding system 12, such as a barcode disposed on the power supply unit 36, the wire feeder 38, the gas supply system 40, the welding torch 42, and so forth. Likewise, a unique serial number associated with a component of the welding system 12 may be entered into the computing device 66 to activate the association between the gateway 32 and the computing device 66. Further, in some situations, the binding process may be activated simultaneously at the gateway 32 and the personally allocated device 30 via an activation feature 68 (e.g., activation button 68). In this example, the operator may trigger the feature 68 (e.g., activation button 68) on the gateway 32 at the same time that a feature 68 of the personally allocated device 30 is triggered. Triggering the two devices approximately simultaneously may activate the binding process, and allow the devices to recognize each other to establish wireless communications 26. As a further example, in some situations, a feature 68 of the personally allocated device 30 or the gateway 32 may be triggered first. The triggered device begins to search for the complementary device, at which point a feature 68 on the complementary device 30 or complementary gateway 32 is triggered to activate the binding process.
In certain embodiments, the binding and/or pairing process involves a helmet as the personally allocated device 30. For example, when the auto-darkening feature of a helmet is activated with 90% synchronization with the Arc On/Off signals from the power supply unit 36, a binding and/or pairing association may be made between the particular helmet in use and the gateway 32 disposed within the power supply unit 36. In some situations, if two helmets are within a pairing range, the helmet that establish a binding or pairing process with the gateway 32 may be the helmet that autodarkens in-synch with the power supply unit 36. It should be noted that in some situations, redundancy may be a way to increase confidence in the collected information. For example, if two or more devices allocated to one operator are in the work area, it is more probable that this operator is the person in this work area. Even if another personally allocated device is in the area, the system may determine the correct operator is the one with the highest number of personally allocated devices reporting. Another example, the gateway 32 may be configured to recognize personally allocated devices 30 that are frequently and/or repeatedly used. Accordingly, the gateway 32 may include intelligence that allows it to more likely establish a pairing with frequently and/or repeatedly used personally allocated devices 30 rather than a personally allocated device 30 with less historical significance. For example, in a situation where a previously used helmet is within the welding area and has on/off synchronization, if another personally allocated device 30, such as, for example, protective clothing, Smartphone, or HMI, was also proximate to the gateway 32, then the personally allocated device 30 that establishes the communications may be the helmet that has made a previous binding or pairing. Indeed, redundancy may help the gateway 32 weed through a plurality of devices 30 by analyzing the historical backlog of previous communications, and/or the personally allocated device 30 that is more secure (e.g., greater confidence in the identification of the operator).
As noted above, once wireless communications 26 is established between the gateway 32 and the personally allocated device 30, welding related information may be exchanged between the two devices. For example, the gateway 32 may receive identification information that corresponds to the particular user or operator the personally allocated device 30 is associated with. Further, as noted above, the monitoring/analysis system 18 and/or the cloud 22 may utilize the identification information to retrieve a user profile associated with that operator. However, it should be noted that in some embodiments, a user profile may be unavailable or non-existent. In such circumstances, the monitoring/analysis system 18 may still correlate, store, or tag any data gathered during operation of the system 10 to the operator with a unique identification number associated with the device 30, an IP address associated with the device 30, a unique employee ID, etc.
As illustrated, the welding system 12 includes the power supply unit 36 having the welding control panel 59. In some embodiments, the welding control panel 59 includes a user interface 70 through which a user may choose a process or input desired welding parameters. The control panel 59 may receive inputs via the user interface 70 using a keypad, keyboard, buttons, touch screen, voice activation system, etc. Further, the control panel 59 includes a display 72 for presenting, showing, or indicating, welding related information to an operator. For example, the control panel 59 may display the status (e.g., connected, weak signal, strong signal, disconnected, available devices 30 for connection, etc.) of the wireless connection (e.g., wireless communications channel 26) between the gateway 32 and the personally allocated device 30. Further, the control panel 59 may provide a selection of devices 30 that are within a range of the gateway 32, so that the user may select the corresponding personally allocated device 30 via user interface 70. The selected device 30 may be utilized to establish the wireless connection channel 26. In this manner, the operator may be sure that the desired device 30 is operatively coupled to the welding system 12, and that welding related information transmitted between the devices is from the intended source.
The gateway 32, whether disposed within the power supply unit 36, another component of the welding system 12, or as an independent component of the welding system 12, utilizes the processor 60 to execute instructions loaded to the gateway 32, received from the monitoring/analysis system 18, and/or stored into a memory 62. In particular, the gateway 32 may contain additional storage 74 where operating data collected by the welding system 12 is stored locally until it is transferred to the monitoring/analysis system 18, the network 28, and/or the cloud 22 at a later time.
As noted above, the personally allocated device 30 may be any device that is associated with a particular welding operator, such as a smart phone, a tablet, a notepad, a welding helmet, an audio input device, a personal clothing item, a personal welding clothing item, an employee tag, a laptop, a welding glove, a personal welding tool, or any item or device that may be configured with wireless capabilities. In some embodiments, the personally allocated device 30 may be any device that may be configured with a radio-frequency identification (RFID) tag. In certain embodiments, the personally allocated device 30 is a computing device 66 (e.g., smartphone, iPad, portable electronic device, etc.) that includes at least one processor 76, a memory device 78, and a storage device 80. Each of these devices may incorporate features of similar devices previously described. Further, the computing device 66 also includes a user interface 82 for providing inputs to and/or receiving outputs from the computing device 66. For example, the user interface 82 may be disposed on or may be utilized with a display 84 for displaying data, video, etc.
During welding operations, the computing device 66 may be utilized for a variety of purposes. For example, as described above, the computing device 66 may be associated with a particular operator, so it may be utilized to establish wireless communications 26 to the welding system 12 and transfer welding related information, such as identification information corresponding to the operator. Upon receiving the identification information, the welding system 12 may identify and authorize the operator for certain welding operations or tasks. In some embodiments, a user profile may be retrieved from the cloud 22, the network 28, and/or the monitoring/analysis system 18, where the user profile corresponds to the operator. Accordingly, the welding system 12 may limit the operations of the operator based on the permissions allocated to the operator. The user profile, the limitations, the permissions, and generally any other information related to the operator may be displayed on the display 84 of the computing device 66.
Further, once wireless communications 26 is established, other forms of welding related information may be transmitted between devices. In some situations, the data from a welding operation performed by the operator may be logged by the welding system 12 and/or the computing device 66. The logged data may be correlated to the operator via the computing device 66 (e.g., the personally allocated device 30), and may be transferred to the monitoring/analysis system 18 or the cloud 22 for further processing and/or analysis. In some situations, operator performance may be determined by the logged data. Further, in some situations, welding parameters being utilized by the operator may be monitored by a third party during the welding operation, and the operator may be altered or informed if the welding parameters are outside of desired boundaries via the computing device 66. For example, a number of audio and/or visual alerts or alarms may be triggered by a third party monitoring the data received at the monitoring/analysis system 18 or the cloud 22 and received by the operator via the computing device 66.
In particular, in some embodiments, the personally allocated device 30 (e.g., computing device 66) may include a welding application stored within the memory 78 of the computing device 66. The welding application may be a set of executable instructions stored within the memory 78 and executed by the processor 76. The welding application may be selected by the operator using the user interface 82, and the welding application may be utilized to perform the functionalities of the personally allocated device 30 described above. For example, the welding operator may engage the welding application (e.g., via voice activation, touch screen, buttons, keyboard, keypad, etc.) to perform a wide variety of activities, such as establishing wireless communications 26 (e.g., wireless communications channel), transferring welding related information, activating the binding or pairing process, logging data corresponding to an operator or component of the welding process such as a consumable or the part to be welded, transferring identification information correlating to the operator, authenticating the operator, providing user profile information on the display 84, providing welding operations limitations and/or permissions on the display 84, providing information related to the welding parameters, solicit input from the operator, etc.
In particular, in certain embodiments, the welding application may additionally be utilized as a controller to control various components and parameters of the welding system 12. For example, the welding operator may engage the welding application on the personally allocated device 30 prior to commencing a welding operation, establish wireless communications 26 to a gateway 32 of the welding system to enable the exchange of information, and commence the welding operations within the designated operating parameters and permissions allocated to the operator. Once the welding operations commence, the operator can control various welding parameters (e.g., voltage output, current output, a wire feed speed, pulse parameters, etc.) from the personally allocated device 30 via one or more controls signals, as can be appreciated by one skilled in the art. For example, the operator may wirelessly adjust one or more welding parameters of the welding system 12 from a remote location (e.g., a location removed from the welding system 12, but within the operational range of the gateway 32). The adjustments may be preferences on the welding application that the operator may easily control, and may be provided to the device 30 via the user interface 82, as can be appreciated by one skilled in the art. Further, the device 30 may transmit the operator's changes/adjustments of the welding parameters as control signals to the welding system 12.
It should be noted that a plurality of personally allocated devices 30 may be within the range of the gateway 32 of the welding system 12. Accordingly, the welding application on the personally allocated device 30 may be configured to control the welding system 12 that has established wireless communications 26 (e.g., devices that have been securely paired via the binding process). In this manner, the operator may securely control welding parameters from a remote location via the welding application.
Once wireless communications 26 is established, welding related information may be transmitted between the paired devices. Accordingly, in some embodiments, the personally allocated device 30 may transfer operator identification information that identifies the operator associated with the device 30, and the welding system 12 receives the same (block 90). The identification information may be utilized by the system 10 to identify, verify, and authenticate the operator (block 92). For example, in some situations, the identification information received may be compared to the local or remote database to determine access settings. Further, in some embodiments, the identification information may be used to retrieve a user profile from the monitoring/analysis system 18 or the cloud 22 that corresponds to the operator. The access settings or permissions/limitations may be predetermined and stored within the monitoring/analysis system 18 and/or the cloud 22, and may be based on a number of factors, such as the welding system 12 in question, the location 16 of the welding task, the experience level of the operator, the welding task/job, material to be welded, consumables allocated for this job, and so forth.
Based on the access settings allocated for the particular operator and/or based on the permissions or limitations allocated to the operator, the system 10 may be configured to enable welding operations for the operator within particular boundaries (block 94). In this manner, the welding system 12 may limit the operational functionalities of the welding operator based on the authentication process.
While only certain features of the invention have been illustrated and described herein, many modifications and changes will occur to those skilled in the art. It is, therefore, to be understood that the appended claims are intended to cover all such modifications and changes as fall within the true spirit of the invention.
This application claims priority to, and is a continuation of, co-pending U.S. application Ser. No. 14/462,255 having a filing date of Aug. 18, 2014, the contents of which is incorporated herein in its entirety.
Number | Name | Date | Kind |
---|---|---|---|
2043331 | Notvest | Jun 1936 | A |
2175891 | Graham | Oct 1939 | A |
2289474 | Anderson | Jul 1942 | A |
2526597 | Winslow | Oct 1950 | A |
2617913 | Oestreicher | Nov 1952 | A |
2642515 | Bagg | Jun 1953 | A |
3567902 | Stearns | Mar 1971 | A |
3992565 | Gatfield | Nov 1976 | A |
4020907 | Luck | May 1977 | A |
4051344 | Robbins | Sep 1977 | A |
4079231 | Toth | Mar 1978 | A |
4093845 | Hairgrove | Jun 1978 | A |
4147919 | Matasovic | Apr 1979 | A |
4216367 | Risberg | Aug 1980 | A |
4216368 | Delay | Aug 1980 | A |
4227066 | Bulwidas | Oct 1980 | A |
4247752 | Stringer | Jan 1981 | A |
4266114 | Hansen | May 1981 | A |
4410789 | Story | Oct 1983 | A |
4450340 | Corrigall | May 1984 | A |
4467174 | Gilliland | Aug 1984 | A |
4484059 | Lillquist | Nov 1984 | A |
4508954 | Kroll | Apr 1985 | A |
4521572 | Cuscurida | Jun 1985 | A |
4521672 | Fronius | Jun 1985 | A |
4531045 | Kemp | Jul 1985 | A |
4547855 | Lanyi | Oct 1985 | A |
4561059 | Davis | Dec 1985 | A |
4584685 | Gajjar | Apr 1986 | A |
4641292 | Tunnell | Feb 1987 | A |
4716274 | Gilliland | Dec 1987 | A |
4767908 | Dallavalle | Aug 1988 | A |
4825038 | Smartt | Apr 1989 | A |
4998005 | Rathi | Mar 1991 | A |
5025500 | Phinney | Jun 1991 | A |
5039635 | Stempin | Aug 1991 | A |
5039835 | Schwiete | Aug 1991 | A |
5043557 | Tabata | Aug 1991 | A |
5136139 | Gilliland | Aug 1992 | A |
5263897 | Kondo | Nov 1993 | A |
5276305 | Hsien | Jan 1994 | A |
5376894 | Petranovich | Dec 1994 | A |
5406050 | Macomber | Apr 1995 | A |
5426426 | Hymel | Jun 1995 | A |
5500512 | Goldblatt | Mar 1996 | A |
5651903 | Shirk | Jul 1997 | A |
5653902 | Chang | Aug 1997 | A |
5708253 | Bloch | Jan 1998 | A |
5731799 | Kee | Mar 1998 | A |
5889671 | Autermann | Mar 1999 | A |
5982253 | Perrin | Nov 1999 | A |
6002104 | Hsu | Dec 1999 | A |
6040555 | Tiller | Mar 2000 | A |
6040829 | Croy | Mar 2000 | A |
6087622 | Summers | Jul 2000 | A |
6091048 | Lanouette | Jul 2000 | A |
6096994 | Handa | Aug 2000 | A |
6103994 | Decoster et al. | Aug 2000 | A |
6130407 | Villafuerte | Oct 2000 | A |
6156999 | Ignatchenko | Dec 2000 | A |
6242711 | Cooper | Jun 2001 | B1 |
6247058 | Miller | Jun 2001 | B1 |
6248975 | Lanouette | Jun 2001 | B1 |
6267291 | Blankenship | Jul 2001 | B1 |
6365868 | Borowy | Apr 2002 | B1 |
6369952 | Rallison | Apr 2002 | B1 |
6417995 | Wu | Jul 2002 | B1 |
6423936 | Reed | Jul 2002 | B1 |
6458157 | Suaning | Oct 2002 | B1 |
6476354 | Jank | Nov 2002 | B1 |
6479793 | Wittmann | Nov 2002 | B1 |
6486439 | Spear et al. | Nov 2002 | B1 |
6510984 | Blankenship et al. | Jan 2003 | B2 |
6515251 | Wind | Feb 2003 | B1 |
6531673 | Fedorcak | Mar 2003 | B2 |
6536660 | Blankenship et al. | Mar 2003 | B2 |
6552303 | Blankenship | Apr 2003 | B1 |
6563085 | Lanouette | May 2003 | B2 |
6570132 | Brunner | May 2003 | B1 |
6583386 | Ivkovich | Jun 2003 | B1 |
6624388 | Blankenship | Sep 2003 | B1 |
6636776 | Barton et al. | Oct 2003 | B1 |
6700097 | Hsu | Mar 2004 | B1 |
6708877 | Blankenship et al. | Mar 2004 | B2 |
6710299 | Blankenship | Mar 2004 | B2 |
6734393 | Friedl | May 2004 | B1 |
6750428 | Okamoto | Jun 2004 | B2 |
6781095 | Hayes | Aug 2004 | B2 |
6797921 | Niedereder | Sep 2004 | B1 |
6809292 | Spear | Oct 2004 | B2 |
6841752 | Ward | Jan 2005 | B2 |
6852949 | Lanouette | Feb 2005 | B2 |
6858817 | Blankenship | Feb 2005 | B2 |
6906285 | Zucker | Jun 2005 | B2 |
6909285 | Jordan | Jun 2005 | B2 |
6924459 | Spear | Aug 2005 | B2 |
7032814 | Blankenship | Apr 2006 | B2 |
7038167 | Hayes | May 2006 | B2 |
7041936 | Oberzaucher | May 2006 | B2 |
7045742 | Feichtinger | May 2006 | B2 |
7089337 | Senoo | Aug 2006 | B2 |
7130255 | Smith | Oct 2006 | B2 |
7180029 | Ott | Feb 2007 | B2 |
7205503 | Reynolds | Apr 2007 | B2 |
7220941 | Niedereder | May 2007 | B2 |
7245875 | Clark | Jul 2007 | B2 |
7257465 | Perez | Aug 2007 | B2 |
7307241 | Hayes | Dec 2007 | B2 |
7336259 | Li | Feb 2008 | B2 |
7342210 | Fergason | Mar 2008 | B2 |
7363137 | Brant | Apr 2008 | B2 |
7369156 | Heinke | May 2008 | B1 |
7375304 | Kainec et al. | May 2008 | B2 |
7501613 | Fergason | Mar 2009 | B2 |
7510047 | Muto | Mar 2009 | B2 |
7510151 | Perez-Sanchez | Mar 2009 | B2 |
7523069 | Friedl et al. | Apr 2009 | B1 |
7550689 | Wech | Jun 2009 | B2 |
7574172 | Clark et al. | Aug 2009 | B2 |
7643890 | Hillen et al. | Jan 2010 | B1 |
7810937 | Garbergs | Oct 2010 | B2 |
7873495 | Lindell | Jan 2011 | B2 |
7908302 | Nagaralu | Mar 2011 | B1 |
7979162 | Niemela | Jul 2011 | B2 |
8338743 | Wanner | Dec 2012 | B2 |
8569655 | Cole | Oct 2013 | B2 |
8890031 | Vogel | Nov 2014 | B2 |
9119023 | Dina | Aug 2015 | B2 |
9566192 | Becker et al. | Feb 2017 | B2 |
20010043656 | Koslar | Nov 2001 | A1 |
20020099774 | Yamato | Jul 2002 | A1 |
20030184515 | Tsai | Oct 2003 | A1 |
20040050905 | Endo | Mar 2004 | A1 |
20040099648 | Hu | May 2004 | A1 |
20040199846 | Matsumoto | Oct 2004 | A1 |
20040232128 | Niedereder et al. | Nov 2004 | A1 |
20040260407 | Wimsatt | Dec 2004 | A1 |
20040262279 | Spear | Dec 2004 | A1 |
20050002083 | Fergason | Jan 2005 | A1 |
20050007504 | Fergason | Jan 2005 | A1 |
20050007667 | Fergason | Jan 2005 | A1 |
20050016975 | Reynolds | Jan 2005 | A1 |
20050017152 | Fergason | Jan 2005 | A1 |
20050133488 | Blankenship | Jun 2005 | A1 |
20050152294 | Yu | Jul 2005 | A1 |
20050155068 | Chang | Jul 2005 | A1 |
20050197115 | Clark et al. | Sep 2005 | A1 |
20050205647 | Wang | Sep 2005 | A1 |
20050230372 | Ott | Oct 2005 | A1 |
20050263511 | Fosbinder | Dec 2005 | A1 |
20050263513 | Leisner | Dec 2005 | A1 |
20050289264 | Illowsky | Dec 2005 | A1 |
20060027980 | Hiestand | Feb 2006 | A1 |
20060077046 | Endo | Apr 2006 | A1 |
20060138113 | Ott | Jun 2006 | A1 |
20060163227 | Hillen | Jul 2006 | A1 |
20060207980 | Jacovetty | Sep 2006 | A1 |
20060213892 | Ott | Sep 2006 | A1 |
20060276288 | Iwanaka | Dec 2006 | A1 |
20070056942 | Daniel et al. | Mar 2007 | A1 |
20070080149 | Albrecht et al. | Apr 2007 | A1 |
20070080150 | Albrecht | Apr 2007 | A1 |
20070080151 | Albrecht et al. | Apr 2007 | A1 |
20070080152 | Albrecht | Apr 2007 | A1 |
20070080153 | Albrecht et al. | Apr 2007 | A1 |
20070089215 | Biche | Apr 2007 | A1 |
20070114216 | Ott | May 2007 | A1 |
20070158319 | Connally | Jul 2007 | A1 |
20070199047 | Gibart | Aug 2007 | A1 |
20070262065 | Peters | Nov 2007 | A1 |
20080003997 | Parkkinen | Jan 2008 | A1 |
20080041553 | Snyder | Feb 2008 | A1 |
20080061049 | Albrecht | Mar 2008 | A1 |
20080078811 | Hillen | Apr 2008 | A1 |
20080116185 | Luck et al. | May 2008 | A1 |
20080116186 | Luck et al. | May 2008 | A1 |
20080149611 | Roth | Jun 2008 | A1 |
20080149686 | Daniel et al. | Jun 2008 | A1 |
20090013210 | McLntosh | Jan 2009 | A1 |
20090039064 | Enyedy | Feb 2009 | A1 |
20090071949 | Harris | Mar 2009 | A1 |
20090120919 | O'Donnell | May 2009 | A1 |
20090152251 | Dantinne | Jun 2009 | A1 |
20090173726 | Davidson et al. | Jul 2009 | A1 |
20090200283 | Bland | Aug 2009 | A1 |
20090234483 | Leko | Sep 2009 | A1 |
20090272221 | Long | Nov 2009 | A1 |
20090272222 | Long | Nov 2009 | A1 |
20090276930 | Becker | Nov 2009 | A1 |
20090298024 | Batzler | Dec 2009 | A1 |
20090313549 | Casner et al. | Dec 2009 | A1 |
20090327035 | Allard | Dec 2009 | A1 |
20100086003 | Pfitzner | Apr 2010 | A1 |
20100217440 | Lindell | Aug 2010 | A1 |
20100223706 | Becker et al. | Sep 2010 | A1 |
20100224610 | Wallace | Sep 2010 | A1 |
20100257228 | Staggs | Oct 2010 | A1 |
20100299185 | Caro | Nov 2010 | A1 |
20110049116 | Rappl | Mar 2011 | A1 |
20110117527 | Conrardy | May 2011 | A1 |
20110172796 | Sohmshetty | Jul 2011 | A1 |
20110180517 | Schneider | Jul 2011 | A1 |
20110198329 | Davidson | Aug 2011 | A1 |
20110248008 | Long | Oct 2011 | A1 |
20110316516 | Schiefermuller | Dec 2011 | A1 |
20120026996 | Yamaguchi | Feb 2012 | A1 |
20120065972 | Strifler | Mar 2012 | A1 |
20120136692 | Ohishi | May 2012 | A1 |
20120226478 | Bender | Sep 2012 | A1 |
20120265996 | Kaal | Oct 2012 | A1 |
20130075380 | Albrech et al. | Mar 2013 | A1 |
20130085380 | Velusamy | Apr 2013 | A1 |
20130091567 | Finch | Apr 2013 | A1 |
20130094551 | Ling | Apr 2013 | A1 |
20130119036 | Daniel | May 2013 | A1 |
20140014638 | Artelsmair | Jan 2014 | A1 |
20140027427 | Fosbinder | Jan 2014 | A1 |
20140048522 | Dina | Feb 2014 | A1 |
20140069899 | Mehn | Mar 2014 | A1 |
20140277648 | Chong | Sep 2014 | A1 |
20140277684 | Lamers | Sep 2014 | A1 |
20140278242 | Lamers | Sep 2014 | A1 |
20140278243 | Lamers | Sep 2014 | A1 |
20150012865 | Lamers et al. | Jan 2015 | A1 |
20150019594 | Lamers | Jan 2015 | A1 |
20150121309 | Reed | Apr 2015 | A1 |
Number | Date | Country |
---|---|---|
1255684 | Jun 2000 | CN |
1538306 | Oct 2004 | CN |
1746833 | Mar 2006 | CN |
1778990 | May 2006 | CN |
1841321 | Oct 2006 | CN |
2832401 | Nov 2006 | CN |
101341755 | Jan 2009 | CN |
101360580 | Feb 2009 | CN |
101374624 | Feb 2009 | CN |
201493592 | Jun 2010 | CN |
101978389 | Feb 2011 | CN |
102059433 | May 2011 | CN |
102239025 | Nov 2011 | CN |
102298858 | Dec 2011 | CN |
102371414 | Mar 2012 | CN |
102378666 | Mar 2012 | CN |
102458748 | May 2012 | CN |
102601493 | Jul 2012 | CN |
102609123 | Jul 2012 | CN |
102821903 | Dec 2012 | CN |
102922089 | Feb 2013 | CN |
103513638 | Jan 2014 | CN |
19624027 | Dec 1997 | DE |
19828986 | Dec 1999 | DE |
202006009014 | Aug 2006 | DE |
0575082 | Dec 1993 | EP |
0626635 | Nov 1994 | EP |
0895826 | Feb 1999 | EP |
0903195 | Mar 1999 | EP |
1112800 | Jul 2001 | EP |
1295673 | Mar 2003 | EP |
1380377 | Jan 2004 | EP |
1445055 | Aug 2004 | EP |
1586403 | Oct 2005 | EP |
1635508 | Mar 2006 | EP |
1681122 | Jul 2006 | EP |
1486283 | Apr 2007 | EP |
1958738 | Aug 2008 | EP |
2131145 | Dec 2009 | EP |
1683599 | May 2014 | EP |
1295673 | Jun 2016 | EP |
2454232 | May 2009 | GB |
61137675 | Jun 1986 | JP |
04162964 | Jun 1992 | JP |
04162966 | Jun 1992 | JP |
H1147950 | Feb 1999 | JP |
3024700 | Mar 2000 | JP |
2000176675 | Jun 2000 | JP |
2001245174 | Sep 2001 | JP |
2002054494 | Feb 2002 | JP |
2003069911 | Mar 2003 | JP |
2003088957 | Mar 2003 | JP |
2003154455 | May 2003 | JP |
2003191075 | Jul 2003 | JP |
2003211378 | Jul 2003 | JP |
2003236663 | Aug 2003 | JP |
2003236669 | Aug 2003 | JP |
4017977 | Dec 2007 | JP |
2011224661 | Nov 2011 | JP |
2011255472 | Dec 2011 | JP |
2013193091 | Sep 2013 | JP |
20120017189 | Feb 2012 | KR |
20130001955 | Jan 2013 | KR |
9958285 | Nov 1999 | WO |
0134337 | May 2001 | WO |
2002058878 | Aug 2002 | WO |
02085566 | Oct 2002 | WO |
02086656 | Oct 2002 | WO |
02095323 | Nov 2002 | WO |
03028389 | Jan 2003 | WO |
2008060753 | May 2008 | WO |
2010111722 | Oct 2010 | WO |
2010142858 | Dec 2010 | WO |
2011100214 | Aug 2011 | WO |
2012000650 | Jan 2012 | WO |
2013184593 | Feb 2013 | WO |
2013184589 | Dec 2013 | WO |
Entry |
---|
How to Measure Performance—A Handbook of Techniques and Tools, U.S. Department of Energy, Oct. 1, 1995, http://www.orau.gov/pbm/handbook/handbook_all.pdf. |
“Miller PC-300 Owner's Manual”, Aug. 1989 (Aug. 1989), http://igor.chudov.com/manuals/Miller/Miller-PC-300-Pulse-Control_Manual.pdf. |
Avocent, “LongView Wireless User Guide”, 2005, http://site.i-techcompany.com/DataSheet/Avocent/lv5800UG.pdf. |
Echelon, “PL 3120 / PL 3150 Power Line Smart Transceiver Data Book, ” Version 2, 005-0154-01, 255 pgs. |
Gilsinn, Jim et al.: “A Welding Cell That Supports Remote Collaboration”, Ninth International Conference on Computer Technology in Welding, Sep. 30, 1999. |
Hackl et al., “Digitally Controlled GMA Power Sources,” Fronius, www.fronius.com/worldwide/usa/products/paper_digitally_controlld_power_sources_gb.pdf, pp. 1-7, publication date not provided. |
Intellon, “CEBus Power Line Encoding and Signaling,” White Paper #0027, Mar. 1997, Version 0.1, pp. 1-6. |
International Search Report for application No. PCT/US2010/045906 dated Nov. 29, 2010. |
International Search Report for PCT application No. PCT/US2015/039687, dated Oct. 13, 2015, 11 pgs. |
International Search Report for PCT application No. PCT/US2013/058592 dated May 2, 2014, 16 pgs. |
International Search Report from PCT application No. PCT/US2014/45049, dated Jan. 29, 2015, 9 pgs. |
International Search Report from PCT application No. PCT/US2015/010252 dated Mar. 30, 2015, 9 pgs. |
International Search Report from PCT application No. PCT/US2015/010257 dated Apr. 2, 2015, 9 pgs. |
International Search Report from PCT application No. PCT/US2015/010258 dated Apr. 1, 2015, 9 pgs. |
International Search Report from PCT application No. PCT/US2015/010264 dated Mar. 31, 2015, 8 pgs. |
International Search Report from PCT application No. PCT/US2016/068407, dated Feb. 17, 2017, 10 pgs. |
International Search Report from PCT application No. PCT/US2013/058099 dated Feb. 5, 2014, 12 pgs. |
International Search Report from PCT application No. PCT/US2014/017862 dated May 8, 2014, 13 pgs. |
International Search Report from PCT application No. PCT/US2014/017863 dated May 12, 2014, 21 pgs. |
International Search Report from PCT application No. PCT/US2014/020920 dated May 12, 2014, 11 pgs. |
International Search Report from PCT application No. PCT/US2014/045047, dated Jun. 3, 2015, 15 pgs. |
Wireless Universal Serial Bus Specification, Revision 1.0, May 12, 2005. |
Office Action for European Patent Application No. 15751164.3 dated Oct. 19, 2018, 7 pages. |
Number | Date | Country | |
---|---|---|---|
20210346975 A1 | Nov 2021 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 14462255 | Aug 2014 | US |
Child | 17385014 | US |