The present invention relates generally to the field of welding systems, and more particularly to welding systems with multiple user interface modules that are synchronized.
In typical welding systems, user interface (UI) modules may appear in many locations. However, the UI modules may each display different sets of information at the different locations. In some cases, a UI module may even display outdated information. This disconnect of information within the system may result in conflicting settings, leading to operator confusion.
In one embodiment, a welding system user interface module includes a front panel comprising a first input device and a first display screen. The welding system user interface module also includes circuitry comprising a memory storing machine-readable instructions, a processor for executing the machine-readable instructions, and communication circuitry configured to receive UI data from the first input device or a second input device of a remote welding system user interface module, and to broadcast synchronized data to the first display screen and a second display screen of the remote welding system user interface module.
In another embodiment, a welding system includes a first user interface module located on a first welding system component, and a second user interface module located on a second welding system component. Data displayed by the first and second user interface modules is synchronized.
In another embodiment, a method includes receiving UI data from a first user interface module of a welding system or a second user interface module of the welding system. The method also includes broadcasting synchronized data to the first and second user interface modules based at least in part on the received UI data.
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:
The embodiments described herein include improvements to welding system user interface modules. Such improvements may provide consistent data throughout all UI modules in the system, resulting in synchronized data (e.g., relating to operating parameters of the various welding system components, parameters relating to the welding process as a whole, and so forth) being provided to all of the components for improved welding system operability. The UI modules enable an operator to adjust and monitor the inputs and outputs of the welding system, which may be received from and distributed to multiple locations in a welding environment. The welding system may include multiple UI modules on various components within the system, such as a welding power source, a welding wire feeder, a welding torch, a welding helmet, a welding remote device (e.g., a pendant), a welding cooling system, a personal computer (PC), and so forth. The UI modules may be specifically designed for the specific components for which they are designed. However, the UI modules may include certain types of UI modules that may be interchangeably (e.g., removable and replaceable) used between various components of a welding system. In addition, UI modules within a welding system may be synchronized such that the data are always relatively synchronized (e.g., within a given updating period, such as less than 1 millisecond) across the various UI modules. For example, as described in greater detail below, in certain embodiments, one of the UI modules in a welding system may always function as the synchronization module, receiving UI data (e.g., data relating to manipulation of input devices, data relating to changes in state for the particular UI module, data relating to changes in system states, and so forth) from the various UI modules within the welding system, and broadcasting synchronized data to the various UI modules.
Turning to the figures,
In the embodiment illustrated in
The illustrated welding system 10 includes a gas supply system 16 that supplies a shielding gas or shielding gas mixtures to the welding torch 18. In the depicted embodiment, the gas supply system 16 is directly coupled to the welding torch 18 via a gas conduit 32 that is part of the weld cable 20 from the welding power supply unit 12. In another embodiment, the gas supply system 16 may instead be coupled to the welding wire feeder 14, and the welding wire feeder 14 may regulate the flow of gas from the gas supply system 16 to the welding torch 18. A shielding gas, as used herein, may refer to any gas or mixture of gases that may be provided to the arc and/or weld pool in order to provide a particular local atmosphere (e.g., shield the arc, improve arc stability, limit the formation of metal oxides, improve wetting of the metal surfaces, alter the chemistry of the weld deposit, and so forth).
In addition, in certain embodiments, other welding equipment and welding accessories (e.g., welding-related devices) may be used in the welding system 10. For example, in most welding applications, a welding helmet 34 may be worn by an operator of the welding system 10. The welding helmet 34 provides protection to the operator of the welding system 10, particularly protecting the eyes of the operator from the flashing associated with the welding arc during welding operations. In addition, in certain embodiments, the welding helmet 34 may provide feedback to the operator related to parameters of the welding operations. For example, the welding helmet 34 may include an internal display configured to display the welding parameters to the operator during the welding operations. In addition, in certain embodiments, a welding remote device (e.g., a pendant) 36 may be used to communicate between the welding wire feeder 14 and the welding torch 18. The welding remote device 36 is a device that may be used at a welding application remote from an associated welding power supply unit 12 and/or welding wire feeder 14, yet still provide substantially the same display and input devices that the remote welding power supply unit 12 and/or welding wire feeder 14 provide. In other words, the welding remote device 36 may be used as a remote control panel when it is not feasible or practical to use control panels on an associated remote welding power supply unit 12 and/or welding wire feeder 14.
The welding equipment and accessories illustrated in
As illustrated in
As described above, the UI modules 38, 40, 42 may include different input devices and display screens (e.g., plasma panels, LCDs panels, LED panels, and so forth), which generally depend upon the general functionality of the welding equipment or accessory for which the UI module is used. For example,
In contrast to the upper and lower UI modules 38, 40, the torch UI module 42 illustrated in
All of the various input devices (e.g., the control knobs 48, the control buttons 50, the power buttons 52, the memory buttons 54, the control buttons 62, and so forth), as well as various other input devices that may be included in the UI modules 38, 40, 42, may be used to receive user inputs from the operator from the various welding equipment and accessories to which the UI modules 38, 40, 42 are attached. In addition, as described in greater detail below, the various display screens 56, 58, 60 may display information that has been synchronized between the various UI modules 38, 40, 42. The operator may change and/or view any of the welding system settings from any of the UI modules 38, 40, 42 in the welding system 10. As such, the UI hardware, software, and data may be duplicated at every UI module 38, 40, 42 in the welding system 10. Therefore, each UI module 38, 40, 42 may display the same information, and only one set of data may need to be managed and relayed to each UI module 38, 40, 42. Using duplicated data at each UI module 38, 40, 42 may result in synchronized data throughout the welding system 10, reducing the possibilities for mistakes and/or confusion. Furthermore, the welding system 10 may be able to receive input information at multiple locations and have the information recognized across the entire welding system 10 immediately (e.g., within a given updating period, such as every 100 milliseconds). Additionally, the synchronization mechanism may enable locking and/or limiting of system parameters, improving the security of the welding system 10.
For example, as illustrated in
Each of the UI modules 38, 40, 42 includes machine-readable instructions stored in the respective memory 66 that may be executed by the respective processor 68. The machine-readable instructions of the controlling UI module (the upper UI module 38 of the welding power supply unit 12 in
The communication circuitry 70 of the UI modules 38, 40, 42 may similarly include either wireless or wired communication circuitry for communicating between the UI modules 38, 40, 42. For example, in certain embodiments, the communication circuitry 70 may use Ethernet, RS485, RS232, SPI, fiber optics, RF, or any other suitable communication methods to communicate the UI data and the synchronized data between the UI modules 38, 40, 42. In addition, in certain embodiments, the UI modules 38, 40, 42 may also communicate (e.g., via WiFi or other suitable communication techniques) with a personal computer (PC) (e.g., the PC 46 illustrated in
As described above, each cycle of the method 74 may be performed by the controlling UI module at a given time interval (e.g., at least approximately every second, at least approximately every 100 milliseconds, at least approximately every 50 milliseconds, at least approximately every 10 milliseconds, at least approximately every 1 millisecond, or even more frequently). However, in certain embodiments, the rate at which the synchronized data is re-broadcast will change over time. For example, the rate at which the synchronized data is re-broadcast may be reduced when there are no new changes to the synchronized data (e.g., when the broadcast token stays the same between cycles). However, when a change in the synchronized display data occurs (e.g., due to system behavior or new control values), the re-broadcast time is momentarily sped up to ensure that each receiving display node (e.g., the UI modules 38, 40, 42) receives the update more rapidly. The broadcast rate reduction logic reduces the total number of network messages that the UI modules 38, 40, 42 have to process. For example, in certain embodiments, three broadcast display data messages including the synchronized data may be sent within approximately 1 millisecond (e.g., approximately 400 microseconds apart), and then the broadcast rate reduces to only once every 50 milliseconds (e.g., a baseline broadcast rate). In certain embodiments, the broadcast rate can also be increased while actively welding (e.g., from approximately 50 milliseconds to approximately 10 milliseconds or approximately 20 milliseconds). As such, the controlling UI module of the welding system 10 may vary the broadcast rate to optimize network performance and to ensure prompt display updates. In particular, the broadcast rate may be varied based on single occurrences or frequencies of occurrences of changes caused by, for example, manual changes via the input devices of the UI modules 38, 40, 42 and/or automatic changes such as system state or feedback changes.
The modularity of the UI modules 38, 40, 42 described herein enables relatively complex welding systems, such as the welding system 10 illustrated in
Furthermore, in certain embodiments, remote control nodes may be used that include no display screens or input devices, but nevertheless may receive and apply the synchronized data that is broadcast by the controlling UI module. Such remote control nodes may still be capable of sending data to the controlling UI module. For example, a current or temperature sensor may function as a remote control node, and may send control messages to the controlling UI module, and receive the synchronized data as control values or state changes. In addition, automation or programmable logic controllers (PLCs) may use the same UI synchronization messages (e.g., in the synchronized data) to automatically adjust settings as a sequence of welded parts are changed, for example.
As described above, the modularity and interchangeability of the UI modules 38, 40, 42 described herein enable virtually unlimited combinations of UI functionality. Again, it should be noted that the UI hardware, software, and even the data communicated, of the UI modules 38, 40, 42 are substantially identical, enabling each of the UI modules 38, 40, 42 to function as a controlling UI module or simply a node in the communication network of welding components of the welding system 10. In addition, all of the UI modules 38, 40, 42 will have the same look and feel as well as data management style. However, each of the UI modules 38, 40, 42 may individually display, at the same time, the exact same parameters, some of the same parameters and some different parameters, or entirely different parameters, depending on the specific needs of the particular UI modules 38, 40, 42. For all UI modules 38, 40, 42 that are displaying the same parameters, they match and are synchronized. For example, if one display screen changes a parameter that is on other display screens, the other display screens update as the parameter changes. For all UI modules 38, 40, 42 that are displaying parameters that are not currently on other UI modules 38, 40, 42, some parameters may be edited with no affect to the other UI modules. In certain embodiments, all of the upper UI modules 38 may display exactly the same parameters. For example, if a change is made to what is being displayed on one upper UI module 38, all of the upper UI modules 38 will be updated to match what is being displayed. Conversely, all of the lower UI modules 40 display may be independent from each other, and display the same or different parameters. For example, if a change is made to what is being displayed on one lower UI module 40, the other lower UI modules 40 may not necessarily follow (e.g., the data displayed may be synchronized, but the particular parameters being displayed may not be). It will be understood that any grouping of UI modules 38, 40, 42 may have differing functionality. For example, in other embodiments, the upper UI modules 38 may potentially display different parameters, while the lower UI modules 40 may display exactly the same parameters. The parameter values themselves, however, will always be synchronized regardless of the UI module 38, 40, 42 upon which they are displayed.
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 from and the benefit of U.S. Provisional Application Ser. No. 61/697,993, entitled “WELDING SYSTEM WITH MULTIPLE USER INTERFACE MODULES,” filed Sep. 7, 2012, which is hereby incorporated by reference in its entirety for all purposes.
Number | Name | Date | Kind |
---|---|---|---|
2043331 | Robert | Jun 1936 | A |
2175891 | Graham | Oct 1939 | A |
2526597 | Howard | Oct 1950 | A |
2617913 | Sol | Nov 1952 | A |
2642515 | Bagg | Jun 1953 | A |
3567902 | Stearns | Mar 1971 | A |
3992565 | Gatfield | Nov 1976 | A |
4051344 | Robbins | Sep 1977 | A |
4079231 | Toth | Mar 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 |
4508954 | Kroll | Apr 1985 | A |
4521572 | Cuscurida | Jun 1985 | A |
4521672 | Fronius | Jun 1985 | A |
4531045 | Gerrit | Jul 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 |
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 |
5276305 | Hsien | Jan 1994 | A |
5376894 | Petranovich | Dec 1994 | A |
5406050 | Macomber | Apr 1995 | A |
5426426 | Hymel | Jun 1995 | A |
5653902 | Chang | Aug 1997 | A |
5708253 | Bloch | Jan 1998 | A |
5731799 | Kee | Mar 1998 | A |
5982253 | Perrin | Nov 1999 | A |
6040555 | Tiller | Mar 2000 | A |
6040829 | Croy | Mar 2000 | A |
6087622 | Summers | Jul 2000 | A |
6103994 | Decoster | Aug 2000 | A |
6156999 | Ignatchenko | Dec 2000 | A |
6247058 | Miller et al. | Jun 2001 | B1 |
6365868 | Borowy | Apr 2002 | B1 |
6417995 | Wu et al. | Jul 2002 | B1 |
6423936 | Reed | Jul 2002 | B1 |
6458157 | Suaning | Oct 2002 | B1 |
6531673 | Fedorcak | Mar 2003 | B2 |
6570132 | Brunner | May 2003 | B1 |
6624388 | Blankenship | Sep 2003 | B1 |
6734393 | Friedl et al. | May 2004 | B1 |
6781095 | Hayes | Aug 2004 | B2 |
6841752 | Ward | Jan 2005 | B2 |
6906285 | Zucker | Jun 2005 | B2 |
6909285 | Jordan | Jun 2005 | B2 |
7038167 | Hayes | May 2006 | B2 |
7041936 | Oberzaucher | May 2006 | B2 |
7045742 | Feichtinger et al. | May 2006 | B2 |
7180029 | Ott | Feb 2007 | B2 |
7205503 | Reynolds | Apr 2007 | B2 |
7245875 | Clark et al. | 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 et al. | Apr 2008 | B2 |
7375304 | Kainec et al. | May 2008 | B2 |
7574172 | Clark et al. | Aug 2009 | B2 |
7810937 | Garbergs et al. | Oct 2010 | B2 |
7873495 | Lindell | Jan 2011 | B2 |
7979162 | Niemela et al. | Jul 2011 | B2 |
20010043656 | Koslar | Nov 2001 | A1 |
20020099774 | Yamato | Jul 2002 | A1 |
20030184515 | Tsai | Oct 2003 | A1 |
20040199846 | Matsumoto | Oct 2004 | A1 |
20040232128 | Niedereder | Nov 2004 | A1 |
20040260407 | Wimsatt | Dec 2004 | A1 |
20050016975 | Reynolds | Jan 2005 | A1 |
20050017152 | Fergason | Jan 2005 | A1 |
20050155068 | Chang | Jul 2005 | A1 |
20050230372 | Ott | Oct 2005 | A1 |
20050263513 | Leisner | Dec 2005 | A1 |
20050289264 | Illowsky et al. | Dec 2005 | A1 |
20060077046 | Endo | Apr 2006 | A1 |
20060138113 | Ott | Jun 2006 | A1 |
20060163227 | Hillen | Jul 2006 | A1 |
20060213892 | Ott | Sep 2006 | A1 |
20060276288 | Iwanaka | Dec 2006 | A1 |
20070080149 | Albrecht et al. | Apr 2007 | A1 |
20070080150 | Albrecht et al. | Apr 2007 | A1 |
20070080151 | Albrecht et al. | Apr 2007 | A1 |
20070080152 | Albrecht et al. | Apr 2007 | A1 |
20070080153 | Albrecht et al. | Apr 2007 | A1 |
20070114216 | Ott | May 2007 | A1 |
20080003997 | Parkkinen | Jan 2008 | A1 |
20080061049 | Albrecht | Mar 2008 | A1 |
20080116185 | Luck et al. | May 2008 | A1 |
20080116186 | Luck et al. | May 2008 | A1 |
20080149611 | Roth et al. | Jun 2008 | A1 |
20090039064 | Enyedy | Feb 2009 | A1 |
20090200283 | Bland et al. | Aug 2009 | A1 |
20090272221 | Long et al. | Nov 2009 | A1 |
20090272222 | Long et al. | Nov 2009 | A1 |
20110180517 | Schneider | Jul 2011 | A1 |
20110248008 | Long et al. | Oct 2011 | A1 |
20110316516 | Schiefermuller | Dec 2011 | A1 |
20120026996 | Yamaguchi | Feb 2012 | A1 |
20120065972 | Strifler | Mar 2012 | A1 |
20130091567 | Finch | Apr 2013 | A1 |
20140014638 | Artelsmair | Jan 2014 | A1 |
20140027427 | Fosbinder | Jan 2014 | A1 |
20140048522 | Dina | Feb 2014 | A1 |
Number | Date | Country |
---|---|---|
1538306 | Oct 2004 | CN |
1746833 | Mar 2006 | CN |
101341755 | Jan 2009 | CN |
101360580 | Feb 2009 | CN |
102378666 | Mar 2012 | CN |
102609123 | Jul 2012 | CN |
19828986 | Dec 1999 | DE |
0575082 | Dec 1993 | EP |
0626635 | Nov 1994 | EP |
1112800 | Jul 2001 | EP |
1112800 | Jul 2001 | EP |
1380377 | Jan 2004 | EP |
1586403 | Oct 2005 | EP |
1635508 | Mar 2006 | EP |
1681122 | Jul 2006 | EP |
1683599 | Jul 2006 | EP |
2131145 | Dec 2009 | EP |
61137675 | Jun 1986 | JP |
4162964 | Jun 1992 | JP |
04162964 | Jun 1992 | JP |
04162966 | Jun 1992 | 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 |
2003236663 | Aug 2003 | JP |
2003236669 | Aug 2003 | JP |
4017977 | Dec 2007 | JP |
2011224661 | Nov 2011 | JP |
2011255472 | Dec 2011 | JP |
2013193091 | Sep 2013 | JP |
20130001955 | Jan 2013 | KR |
9958285 | Nov 1999 | 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 |
2013184593 | Feb 2013 | WO |
2013184589 | Dec 2013 | WO |
Entry |
---|
International Search Report from PCT application No. PCT/US2013/058099 dated Feb. 5, 2014, 12 pgs. |
“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/Iv5800UG.pdf. |
Echelon, “PL 3120 / PL 3150 Power Line Smart Transceiver Data Book,” Version 2, 005-0154-01C. |
Heinrich Hackl et al., ‘Digitally Controlled GMA Power Sources,’ pp. 1-7. |
Wireless Universal Serial Bus Specification, Revision 1.0, May 12, 2005. |
Number | Date | Country | |
---|---|---|---|
20140069899 A1 | Mar 2014 | US |
Number | Date | Country | |
---|---|---|---|
61697993 | Sep 2012 | US |