EP2632623B1 - System and method for welder with help request functionality - Google Patents
System and method for welder with help request functionality Download PDFInfo
- Publication number
- EP2632623B1 EP2632623B1 EP11785476.0A EP11785476A EP2632623B1 EP 2632623 B1 EP2632623 B1 EP 2632623B1 EP 11785476 A EP11785476 A EP 11785476A EP 2632623 B1 EP2632623 B1 EP 2632623B1
- Authority
- EP
- European Patent Office
- Prior art keywords
- welder
- entity
- data
- help request
- address
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000000034 method Methods 0.000 title claims description 46
- 238000004891 communication Methods 0.000 claims description 87
- 230000000875 corresponding effect Effects 0.000 claims description 22
- 230000002596 correlated effect Effects 0.000 claims description 7
- 238000003466 welding Methods 0.000 description 31
- 238000010586 diagram Methods 0.000 description 16
- 238000004519 manufacturing process Methods 0.000 description 9
- 230000009471 action Effects 0.000 description 7
- 230000008569 process Effects 0.000 description 7
- 238000012545 processing Methods 0.000 description 6
- 238000012423 maintenance Methods 0.000 description 5
- 230000006870 function Effects 0.000 description 4
- 238000013459 approach Methods 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- RYGMFSIKBFXOCR-UHFFFAOYSA-N Copper Chemical compound [Cu] RYGMFSIKBFXOCR-UHFFFAOYSA-N 0.000 description 1
- 241000699670 Mus sp. Species 0.000 description 1
- 235000009470 Theobroma cacao Nutrition 0.000 description 1
- 239000008186 active pharmaceutical agent Substances 0.000 description 1
- 230000004075 alteration Effects 0.000 description 1
- 238000013473 artificial intelligence Methods 0.000 description 1
- 244000240602 cacao Species 0.000 description 1
- 238000010276 construction Methods 0.000 description 1
- 229910052802 copper Inorganic materials 0.000 description 1
- 239000010949 copper Substances 0.000 description 1
- 230000001934 delay Effects 0.000 description 1
- 238000010891 electric arc Methods 0.000 description 1
- 239000000835 fiber Substances 0.000 description 1
- 239000000203 mixture Substances 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 239000000126 substance Substances 0.000 description 1
Images
Classifications
-
- B—PERFORMING OPERATIONS; TRANSPORTING
- B23—MACHINE TOOLS; METAL-WORKING NOT OTHERWISE PROVIDED FOR
- B23K—SOLDERING OR UNSOLDERING; WELDING; CLADDING OR PLATING BY SOLDERING OR WELDING; CUTTING BY APPLYING HEAT LOCALLY, e.g. FLAME CUTTING; WORKING BY LASER BEAM
- B23K9/00—Arc welding or cutting
- B23K9/10—Other electric circuits therefor; Protective circuits; Remote controls
- B23K9/1006—Power supply
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/10—Office automation; Time management
- G06Q10/103—Workflow collaboration or project management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/20—Administration of product repair or maintenance
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q50/00—Information and communication technology [ICT] specially adapted for implementation of business processes of specific business sectors, e.g. utilities or tourism
- G06Q50/04—Manufacturing
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02P—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
- Y02P90/00—Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
- Y02P90/30—Computing systems specially adapted for manufacturing
Definitions
- the present disclosure relates generally to the field of welding and welding equipment. More particularly, the present disclosure relates to a welder with functionality for transmitting help requests, and to a method and article of manufacture.
- Welding systems are deployed in manufacturing facilities that often employ hundreds or thousands of welders.
- One example of such welders include electric arc welders.
- These systems are often deployed over great distances in relatively large manufacturing environments and are often spread across multiple manufacturing centers.
- increasing challenges are faced in upgrading, maintaining, servicing, and supplying welding systems.
- the invention provides a welder according to claim 1 and a method for a welder to receive and communicate help requests according to claim 8. Further embodiments, advantages and features of the invention are disclosed in the following description of exemplary and nonlimiting embodiments, drawings and claims.
- FIG. 1 illustrates a simplified block diagram of a welding system 100 with help request communication capability.
- the system 100 includes a welder 110.
- the welder 110 is equipped such that a user at the welder 110 may convey help requests via the welder 110 to a plurality of entities 120 1-n .
- An entity may be an individual, a group of individuals, a machine, a plurality of machines, an application program, a computer, a network of computers, combinations thereof, and so on.
- a user of the welder 110 may access a display of a subset of entities via operation of a user interface in the welder 110.
- the user may choose an appropriate entity to receive the help request from the subset of entities displayed by the welder 110.
- the user may select a subject or context to which the help request relates and the system 100 identifies the appropriate entity or entities to receive the help request.
- the user may request help with a quality issue by selecting "quality" as the context and the system may send a help request to a quality engineering department.
- the system 100 conveys the help request to the appropriate entity via a communication mode (e.g., electronic mail, voice, text message, and so on) that is the most suitable given the context or the entity.
- a communication mode e.g., electronic mail, voice, text message, and so on
- FIG. 2 illustrates a simplified block diagram of a welding system 200 with help request communication capability.
- the system 200 comprises a plurality of welders 210 1-m .
- the welding system includes one or more networks of welders.
- the welding system includes other machines or equipment that relate to welding and are connected in the network. At least some of the welders 210 1-m are equipped such that users may convey help requests via the welders 210 1-m to a plurality of entities 220 1-n .
- FIG. 3 illustrates a block diagram of an exemplary welding system 300.
- the welding system 300 includes a welder 310.
- the welder 310 includes a network interface 320 that connects the welder 310 to a network 315.
- the network interface 320 may connect the welder 310 to Local Area Networks (LAN) through technologies including, but not limited to, fiber distributed data interface (FDDI), copper distributed data interface (CDDI), Ethernet (IEEE 802.3), token ring (IEEE 802.5), wireless computer communication (IEEE 802.11), Bluetooth (IEEE 802.15.1), Zigbee (IEEE 802.15.4), combinations thereof, and so on.
- FDDI fiber distributed data interface
- CDDI copper distributed data interface
- Ethernet IEEE 802.3
- token ring IEEE 802.5
- wireless computer communication IEEE 802.11
- Bluetooth IEEE 802.15.1
- Zigbee IEEE 802.15.4
- the network interface 320 may connect the welder 310 to Wide Area Networks (WAN) through technologies including, but not limited to, point to point links, circuit switching networks like integrated services digital networks (ISDN), cable internet, Wi-MAX, High-Speed Downlink Packet Access (HSDPA), packet switching networks, and digital subscriber lines (DSL). While individual network types are described, it is to be appreciated that communications via, over, or through a network may include combinations and mixtures of communications.
- ISDN integrated services digital networks
- HSDPA High-Speed Downlink Packet Access
- DSL digital subscriber lines
- the welder 310 further includes a user interface 330.
- the user interface 330 indicates to a user of the welder 310 one or more entities to whom help requests may be sent.
- the user interface 330 also receives from the user a selection indicating a selected entity or entities from the plurality of entities.
- a user interface logic controls at least some functionality of the user interface 330.
- the user interface logic causes the user interface 330 to display at least one entity corresponding to one or more persons to whom help requests may be sent.
- the user interface logic also receives a selection signal including data indicating the user selection of an entity or entities via the user interface 330 on the welder 310.
- FIG 3a illustrates an exemplary user interface 330.
- the user interface 330 includes displays 332a-c, knobs 334a-c, and soft buttons 336a-b.
- a user may operate knob 334c, for example, to select from a series of menus.
- the user may operate the soft button 336a to select the help request menu (help) from the series of menus.
- help the help request menu
- the user may operate the knob 334c to scroll through entities to whom help requests may be sent.
- the user interface 330 indicates on display 332c that help requests may be sent to a maintenance entity (maint) and a quality entity (quality).
- the user may operate one of the soft buttons 336a-b to select between displayed entities.
- the user interface may include various types of displays (LED, LED displays, LCD, and so on) and various input types (touch screens, dials, knobs, buttons, click wheels, roller balls, roller pads, mice, and so on).
- the welder 310 includes a data store 340.
- the data store 340 stores welder data and entity data.
- Welder data includes welder identification and location information (e.g., serial number, model number, IP address, physical address, global positioning coordinates, physical location relative to a facility or other equipment, and so on).
- Entity data includes data correlating the entities to respective communication modes. Communication modes include, but are not limited to, electronic mail, SMS text message, push notifications, voice message, combinations thereof, and so on.
- the data correlating the entities to the respective communication modes include, but is not limited to, data indicating a device (e.g., PDA, telephone, smart phone, computer, pager, combinations thereof, and so on) in which the entity would receive the help request and data indicating the address at which the help request is to be sent or directed (e.g., telephone number, IP address, email address, MAC address, mobile equipment identifier (MEID), electronic serial number (ESN), username, combinations thereof, and so on).
- a device e.g., PDA, telephone, smart phone, computer, pager, combinations thereof, and so on
- data indicating the address at which the help request is to be sent or directed e.g., telephone number, IP address, email address, MAC address, mobile equipment identifier (MEID), electronic serial number (ESN), username, combinations thereof, and so on.
- MEID mobile equipment identifier
- ESN electronic serial number
- the entity data includes data correlating at least some of the entities to multiple communication modes or multiple addresses.
- the entity data may include data correlating an entity to electronic mail as the primary communication mode and to voice message as the secondary communication mode.
- the entity data may include data correlating an entity to a first address as the primary address and to a second address and the secondary address.
- Figure 3b illustrates an exemplary data store 340.
- the data store 340 includes entity data 342 and welder data 344.
- the entity data 342 includes a table correlating entities to modes of communication and addresses. For example, the entity data 342 correlates an entity named "Maintenance” to electronic email “Email” as the communication mode and "maint@lincolelectric.com” as the electronic email address. Similarly, the entity data 342 correlates other entities to communications modes and addresses.
- the welder data 344 includes a table correlating the welder to a serial number, an IP address, a physical location indicator. For example, the welder data 344 correlates the welder "PW S350" to serial number "S009876543,” to IP address "207.54.157.1,” and to a physical location indicator described as "1st Quadrant of Rim Production Floor, 22801 St. Clair Ave., Cleveland, OH 44117.”
- the welder 310 further includes a communication logic 350.
- the communication logic 350 receives a signal from the user interface 330 indicating the user selection of an entity.
- the communication logic 350 further receives from the data store 340 the welder data corresponding to the welder 310 and the entity data corresponding to the user selected entity.
- the communication logic 350 Based on the received information, the communication logic 350 generates help requests in at least one format corresponding to the communication mode or modes correlated in the entity data to the selected entity.
- the communication logic 350 generates the help requests directed to the address or addresses correlated to the selected entity in the entity data.
- the communication logic 350 generates the help request in at least two formats, a first format corresponding to a primary communication mode and a second format corresponding a secondary communication mode. In another embodiment, the communication logic 350 generates the help request directed to at least two addresses, a first address corresponding to a primary address and a second address corresponding a secondary address.
- an entity includes a plurality of persons or network devices and the communication logic 350 generates a plurality of instances of the help request, each instance corresponding to one person or network device from the plurality of persons or network devices. For example, if the maintenance group has three employees, A, B, and C, who perform maintenance on welders, the communication logic 350 generates three instances of the help request, a first instance addressed to employee A, a second instance addressed to employee B, and a third instance addressed to employee C.
- the welder 310 further includes a processor 360 operably connected to the network interface 320 and the communication logic 350.
- the processor 360 causes the network interface 320 to transmit the help request or multiple instances of the help request in the network 315.
- the welder 310 transmits the help request via the network 315 to a remote interface 370.
- the remote interface 370 includes servers configured to receive the help request and transmit it to the entity in the appropriate communication mode.
- the remote interface 370 includes an email server 375 that receives the help request and transmits a help request electronic mail to the entity in cases where electronic mail is the appropriate communication mode.
- the remote interface 370 includes a text messaging server 380 that receives the help request and transmits a help request text message to the entity in cases where text messaging is the appropriate communication mode.
- the remote interface 370 includes a voice messaging server 385 that receives the help request and transmits a help request voice message to the entity in cases where voice messaging is the appropriate communication mode.
- the remote interface 370 may include other messaging servers such as server 390 that receives the help request and transmits a help request message to the entity in the appropriate communication mode.
- Figure 4 illustrate an exemplary help request electronic mail 400.
- the electronic mail 400 includes a "To:” field indicating the entity receiving the help request electronic mail 400.
- the electronic mail 400 further includes a "From:” field indicating identification of the welder or related equipment whose user is requesting help.
- identification of the welder includes a given name such as the model number or some other name (e.g., PW S350).
- identification of the welder includes the welder serial number (e.g., S009876543).
- identification of the welder includes the welder's IP address (e.g., 207.54.157.1).
- identification of the welder includes a combination of the given name, the serial number, and the IP address. In other embodiments (hot shown), identification of the welder includes identification other than the given name, the serial number, and the IP address (e.g., an asset number, a tracking number, and so on).
- the electronic mail 400 further includes a "Subject:” field indicating that the electronic mail 400 is a help request message.
- the electronic mail 400 further includes body text indicating the physical location of the welder or related equipment whose user is requesting help. In one embodiment, physical location information appears in the "From:” or "Subject:” fields.
- Help request text messages, voice messages, or any other type of messages would have a similar format that includes at least information identifying the welder or related equipment whose user is requesting help.
- FIG. 5 illustrates an exemplary block diagram of an alternatively arranged welding system 500.
- the welding system 500 includes the welder 510 and additional welders 512 and 514, which all connect to the network 515.
- the welder 510 includes a network interface 520 that connects the welder 510 to the network 515.
- the welder 510 further includes a user interface 530 that indicates to a user of the welder 510 one or more entities to whom help requests may be sent.
- the user interface 530 also receives from the user a selection indicating a selected entity.
- the welding system 500 includes a data store 540, however unlike in exemplary welding system 300 discussed above, the data store 540 is located remote from the welder 510.
- the welder 510, as well as the other welders, 512 and 514, in the network 515 may obtain data from data store 540 via the network 515.
- the welder 510 further includes a communication logic 550 that receives a signal from the user interface 530 indicating the user selection of an entity.
- the communication logic 550 receives data from the data store 540.
- the communication logic 550 receives the welder data corresponding to the welder 510 and the entity data corresponding to the user selected entity from the data store 540.
- the communication logic 550 receives the welder data from a data store other than the data store 540 which may be local or remote to welder 510.
- the communication logic 550 receives only the entity data from the data store 540.
- the communication logic 550 Based on the received information, the communication logic 550 generates help requests in at least one format corresponding to the communication mode or modes correlated in the entity data to the selected entity. The communication logic 550 generates the help requests directed to the address or addresses correlated to the selected entity in the entity data.
- the welder 510 further includes a processor 560 operably connected to the network interface 520 and the communication logic 550.
- the processor 560 causes the network interface 520 to transmit the help request or multiple instances of the help request in the network 515.
- the welder 510 transmits the help request via the network 515 to a remote interface 570.
- the remote interface 570 includes servers 575, 580, 585, and 590 that receive the help request and transmit it to the entity in the appropriate communication mode.
- FIG. 6 illustrates an exemplary block diagram of an alternatively arranged welding system 600.
- the welding system 600 includes the welder 610 and additional welders 612 and 614, which all connect to the network 615.
- the welder 610 includes a network interface 620 that connects the welder 610 to the network 615.
- the welder 610 further includes a user interface 630 that indicates to a user of the welder 610 one or more entities to whom help requests may be sent.
- the user interface 630 also receives from the user a selection indicating a selected entity.
- the welder 610 includes a data store 640.
- the data store 640 stores at least one of welder data and entity data.
- the welder 610 further includes a communication logic 650 that receives a signal from the user interface 630 indicating the user selection of an entity.
- the communication logic 650 further receives from the data store 640 at least one of the welder data corresponding to the welder 610 and the entity data corresponding to the user selected entity.
- the communication logic 650 Based on the received information, the communication logic 650 generates help requests in at least one format corresponding to the communication mode or modes correlated in the entity data to the selected entity. The communication logic 650 generates the help request directed to the address or addresses correlated to the selected entity in the entity data.
- the welder 610 includes servers configured to receive the help request and transmit it to the entity in the appropriate communication mode.
- the welder 610 may include an email server 675 that receives the help request and generates a help request electronic mail that the network interface 620 transmits to the entity.
- the welder 610 may include a text messaging server 680 that receives the help request and generates a help request text message that the network interface 620 transmits to the entity.
- the welder 610 may include a voice messaging server 685 that receives the help request and generates a help request voice message that the network interface 620 transmits to the entity.
- the welder 610 may include other messaging servers such as server 690 that receives the help request and generates a help request message that the network interface 620 may transmit to the entity in the appropriate communication mode.
- the welder 610 further includes a processor 660 operably connected to the network interface 620 and the communication logic 650.
- the processor 660 causes the network interface 620 to transmit the help request message in the network 615.
- the network interface 620 transmits the help request messages in the appropriate communication mode via the network 615 to a remote interface 670 that may be local or remote to the entity receiving the help request.
- Example methods may be better appreciated with reference to the flow diagram of Figure 7 . While for purposes of simplicity of explanation, the illustrated methodologies are shown and described as a series of blocks, it is to be appreciated that the methodologies are not limited by the order of the blocks, as some blocks can occur in different orders or concurrently with other blocks from that shown or described. Moreover, less than all the illustrated blocks may be required to implement an example methodology. Furthermore, additional or alternative methodologies can employ additional, not illustrated blocks.
- processing blocks denote "processing blocks” that may be implemented with logic.
- the processing blocks may represent a method step or an apparatus element for performing the method step.
- a flow diagram does not depict syntax for any particular programming language, methodology, or style (e.g., procedural, object-oriented). Rather, a flow diagram illustrates functional information one skilled in the art may employ to develop logic to perform the illustrated processing. It will be appreciated that in some examples, program elements like temporary variables, routine loops, and so on, are not shown. It will be further appreciated that electronic and software applications may involve dynamic and flexible processes so that the illustrated blocks can be performed in other sequences that are different from those shown or that blocks may be combined or separated into multiple components. It will be appreciated that the processes may be implemented using hardware or software and using various programming approaches like machine language, procedural, object oriented or artificial intelligence techniques.
- methodologies are implemented as processor executable instructions or operations provided on a computer-readable medium.
- a computer-readable medium may store processor executable instructions operable to perform a method. While the above method is described being provided on a computer-readable medium, it is to be appreciated that other example methods described herein can also be provided on a computer-readable medium.
- Figure 7 illustrates various actions occurring in serial, it is to be appreciated that various actions illustrated in Figure 7 could occur substantially in parallel. While a number of processes are described, it is to be appreciated that a greater or lesser number of processes could be employed and that lightweight processes, regular processes, threads, and other approaches could be employed. It is to be appreciated that other example methods may, in some cases, also include actions that occur substantially in parallel.
- Figure 7 illustrates an exemplary flow diagram of a method 700 for a welder to receive and communicate help requests in a network.
- the method 700 includes at 710 presenting to a user a plurality of entities to whom help requests may be sent.
- An entity may be a single person or machine, or an entity may include a plurality of persons or network devices.
- the method 700 further includes at 720 receiving a user selection of an entity from the plurality of entities to whom to send a help request. The user makes the selection via a user interface in the welder.
- the method 700 further includes at 730 receiving welder data including welder identification and location information.
- the welder data maybe local or remote to the welder and includes at least the minimum information necessary to identify the physical location of the welder whose user is requesting help.
- the method 700 further includes at 740 receiving entity data including data correlating the entity to communication mode information including at least one communication format (e.g., electronic mail, text message, voice message, and so on) and at least one address (e.g., email address, IP address, telephone number, ESN, and so on).
- the method 700 further includes at 750 generating a help request message directed to the entity.
- the help request message is formatted and addressed based on the communication mode information.
- the method generates a plurality of instances of the help request message, each instance corresponding to one person or network device.
- Data store refers to a physical or logical entity that can store data.
- a data store may be, for example, a database, a table, a file, a list, a queue, a heap, a memory, a register, and so on.
- a data store may reside in one logical or physical entity or may be distributed between two or more logical or physical entities.
- connection is one by which the operably connected entities or the operable connection perform its intended purpose. For example, two entities may be operably connected to each other directly or through one or more intermediate entities.
- Logic includes but is not limited to hardware, firmware, software or combinations of each to perform a function(s) or an action(s), or to cause a function or action from another logic, method, or system.
- logic may include a software controlled microprocessor, discrete logic like an application specific integrated circuit (ASIC), a programmed logic device, a memory device containing instructions, or the like.
- ASIC application specific integrated circuit
- Logic may include one or more gates, combinations of gates, or other circuit components.
- Logic may also be fully embodied as software. Where multiple logical logics are described, it may be possible to incorporate the multiple logical logics into one physical logic. Similarly, where a single logical logic is described, it may be possible to distribute that single logical logic between multiple physical logics.
- an operable connection or a connection by which entities are “operably connected,” is one in which signals, physical communications, or logical communications may be sent or received.
- an operable connection includes a physical interface, an electrical interface, or a data interface, but it is to be noted that an operable connection may include differing combinations of these or other types of connections sufficient to allow operable control.
- two entities can be operably connected by being able to communicate signals to each other directly or through one or more intermediate entities like a processor, operating system, a logic, software, or other entity.
- Logical or physical communication channels can be used to create an operable connection.
- Query refers to a semantic construction that facilitates gathering and processing information.
- a query might be formulated in a database query language like structured query language (SQL) or object query language (OQL).
- a query might be implemented in computer code (e.g., C#, C++, Javascript) that can be employed to gather information from various data stores or information sources.
- Signal includes but is not limited to one or more electrical or optical signals, analog or digital signals, data, one or more computer or processor instructions, messages, a bit or bit stream, or other means that can be received, transmitted or detected.
- Software includes but is not limited to, one or more computer or processor instructions that can be read, interpreted, compiled, or executed and that cause a computer, processor, or other electronic device to perform functions, actions or behave in a desired manner.
- the instructions may be embodied in various forms like routines, algorithms, modules, methods, threads, or programs including separate applications or code from dynamically or statically linked libraries.
- Software may also be implemented in a variety of executable or loadable forms including, but not limited to, a stand-alone program, a function call (local or remote), a servelet, an applet, instructions stored in a memory, part of an operating system or other types of executable instructions.
- Suitable software for implementing the various components of the example systems and methods described herein may be produced using programming languages and tools like Java, Java Script, Java.NET, ASP.NET, VB.NET, Cocoa, Pascal, C#, C++, C, CGI, Perl, SQL, APIs, SDKs, assembly, firmware, microcode, or other languages and tools.
- Software whether an entire system or a component of a system, may be embodied as an article of manufacture and maintained or provided as part of a computer-readable medium as defined previously.
- Another form of the software may include signals that transmit program code of the software to a recipient over a network or other communication medium.
- a computer-readable medium has a form of signals that represent the software/firmware as it is downloaded from a web server to a user.
- the computer-readable medium has a form of the software/firmware as it is maintained on the web server. Other forms may also be used.
- User includes but is not limited to one or more persons, which is typically an operator of the machine in question.
Landscapes
- Engineering & Computer Science (AREA)
- Business, Economics & Management (AREA)
- Human Resources & Organizations (AREA)
- Strategic Management (AREA)
- Physics & Mathematics (AREA)
- General Business, Economics & Management (AREA)
- Theoretical Computer Science (AREA)
- Marketing (AREA)
- Economics (AREA)
- General Physics & Mathematics (AREA)
- Tourism & Hospitality (AREA)
- Entrepreneurship & Innovation (AREA)
- Quality & Reliability (AREA)
- Operations Research (AREA)
- Data Mining & Analysis (AREA)
- Plasma & Fusion (AREA)
- Mechanical Engineering (AREA)
- Manufacturing & Machinery (AREA)
- Health & Medical Sciences (AREA)
- General Health & Medical Sciences (AREA)
- Primary Health Care (AREA)
- Telephonic Communication Services (AREA)
- Information Transfer Between Computers (AREA)
- Arc Welding Control (AREA)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PL11785476T PL2632623T3 (pl) | 2010-10-29 | 2011-10-31 | System i sposób dla spawarki z funkcją prośby o pomoc |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US12/915,315 US8688815B2 (en) | 2010-10-29 | 2010-10-29 | System and method for welder with help request functionality |
PCT/IB2011/002568 WO2012056309A1 (en) | 2010-10-29 | 2011-10-31 | System and method for welder with help request functionality |
Publications (2)
Publication Number | Publication Date |
---|---|
EP2632623A1 EP2632623A1 (en) | 2013-09-04 |
EP2632623B1 true EP2632623B1 (en) | 2021-08-04 |
Family
ID=45002074
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP11785476.0A Active EP2632623B1 (en) | 2010-10-29 | 2011-10-31 | System and method for welder with help request functionality |
Country Status (9)
Country | Link |
---|---|
US (1) | US8688815B2 (zh) |
EP (1) | EP2632623B1 (zh) |
JP (1) | JP2013543795A (zh) |
CN (1) | CN103282152A (zh) |
BR (1) | BR112013010183A2 (zh) |
CA (1) | CA2815441A1 (zh) |
MX (1) | MX2013004671A (zh) |
PL (1) | PL2632623T3 (zh) |
WO (1) | WO2012056309A1 (zh) |
Families Citing this family (16)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US10293425B2 (en) * | 2011-03-29 | 2019-05-21 | Illinois Tool Works Inc. | Method for determining arc consistency in pulsed gas metal arc welding systems |
US9270520B2 (en) | 2012-08-17 | 2016-02-23 | Illinois Tool Works Inc. | Wireless communication network sensor information for control of industrial equipment in harsh environments |
US10286475B2 (en) | 2012-08-17 | 2019-05-14 | Illinois Tool Works Inc. | Wireless communication network for control of industrial equipment in harsh environments |
US9119023B2 (en) * | 2012-08-17 | 2015-08-25 | Illinois Tool Works Inc. | Wireless communication network association and security for control of industrial equipment in harsh environments |
US9712947B2 (en) * | 2012-08-17 | 2017-07-18 | Illinois Tool Works Inc. | Wireless communication network improved robustness for control of industrial equipment in harsh environments |
US9449498B2 (en) | 2012-08-17 | 2016-09-20 | Illinois Tool Works Inc. | Wireless communication network power optimization for control of industrial equipment in harsh environments |
US10682720B2 (en) * | 2012-09-07 | 2020-06-16 | Illinois Tool Works Inc. | Welding systems and devices having a configurable personal computer user interface |
JP5988918B2 (ja) * | 2013-06-03 | 2016-09-07 | 株式会社神戸製鋼所 | 溶接装置、複数の溶接装置を備える溶接システム、および溶接装置に用いられるプログラム |
DE102013216420A1 (de) * | 2013-08-20 | 2015-02-26 | Robert Bosch Gmbh | Steueranlage zum Steuern von zumindest einem Schweißprozess |
US9993890B2 (en) * | 2013-10-28 | 2018-06-12 | Illinois Tool Works Inc. | System and method for data exchange and control with a wireless remote control for welding systems |
CN104014906B (zh) * | 2014-04-02 | 2016-08-24 | 唐山松下产业机器有限公司 | 焊接电源管理系统及其管理方法 |
US9583814B2 (en) * | 2014-09-08 | 2017-02-28 | Illinois Tool Works Inc. | System and method for an antenna on a cable |
US9786992B2 (en) | 2014-09-17 | 2017-10-10 | Illinois Tool Works Inc. | System and method for cavity-backed antenna |
US10363627B2 (en) | 2014-12-16 | 2019-07-30 | Illinois Tool Works Inc. | Systems and methods for providing location services for a welding power supply |
US10369652B2 (en) | 2015-07-24 | 2019-08-06 | Illinois Tool Works Inc. | Wireless and powerline communications in a welding-type system |
US11311958B1 (en) * | 2019-05-13 | 2022-04-26 | Airgas, Inc. | Digital welding and cutting efficiency analysis, process evaluation and response feedback system for process optimization |
Family Cites Families (24)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5510596A (en) * | 1993-04-27 | 1996-04-23 | American Welding Institute | Penetration sensor/controller arc welder |
US20010037363A1 (en) * | 2000-05-22 | 2001-11-01 | Battilega Eric A. | Method and system for consulting services |
JP2002149863A (ja) * | 2000-11-10 | 2002-05-24 | Nec Corp | 保守サービスシステム |
JP2002203064A (ja) * | 2000-12-28 | 2002-07-19 | Toshiba Corp | 保守管理システム及び保守管理方法 |
US6624388B1 (en) | 2001-01-25 | 2003-09-23 | The Lincoln Electric Company | System and method providing distributed welding architecture |
US7375304B2 (en) | 2001-01-25 | 2008-05-20 | Lincoln Global, Inc. | System and method providing automated welding notification |
US6486439B1 (en) | 2001-01-25 | 2002-11-26 | Lincoln Global, Inc. | System and method providing automated welding information exchange and replacement part order generation |
US7245875B2 (en) | 2001-04-24 | 2007-07-17 | Lincoln Global, Inc. | System and method to facilitate wireless communication in a welding environment |
US6795778B2 (en) | 2001-05-24 | 2004-09-21 | Lincoln Global, Inc. | System and method for facilitating welding system diagnostics |
AT413658B (de) | 2001-09-12 | 2006-04-15 | Fronius Int Gmbh | Fernregler und bedieneinheit für ein schweissgerät |
CN100386172C (zh) * | 2002-07-04 | 2008-05-07 | 弗罗纽斯国际有限公司 | 操作焊接设备的方法及焊接设备 |
US6744011B1 (en) * | 2002-11-26 | 2004-06-01 | General Motors Corporation | Online monitoring system and method for a short-circuiting gas metal arc welding process |
US6912447B2 (en) | 2002-12-23 | 2005-06-28 | Caterpillar Inc | System and method for determining weld procedures |
JP2005128818A (ja) * | 2003-10-24 | 2005-05-19 | M & C:Kk | 生産設備管理システム |
US7687741B2 (en) | 2005-02-03 | 2010-03-30 | Lincoln Global, Inc. | Triggering events in a welder with a real-time clock |
US8115138B2 (en) * | 2005-03-15 | 2012-02-14 | Lincoln Global, Inc. | Comprehensive identification and designation of welding procedures |
WO2007044135A1 (en) * | 2005-10-07 | 2007-04-19 | Illinois Tool Works Inc. | Wireless communication system for welding-type devices |
JP2007172011A (ja) * | 2005-12-19 | 2007-07-05 | Ebara Techno-Serve Co Ltd | 現場作業支援システム |
US7683290B2 (en) | 2006-05-12 | 2010-03-23 | Lincoln Global, Inc. | Method and apparatus for characterizing a welding output circuit path |
US20080189612A1 (en) | 2007-02-01 | 2008-08-07 | Sony Corporation | Using unique help utility identifier as parameter in application to facilitate extraction of help tutorial from library |
US8847115B2 (en) * | 2008-06-16 | 2014-09-30 | Illinois Tool Works Inc. | Configurable welding interface for automated welding applications |
US9483959B2 (en) * | 2008-08-21 | 2016-11-01 | Lincoln Global, Inc. | Welding simulator |
US8321253B2 (en) * | 2009-06-09 | 2012-11-27 | Accenture Global Services Limited | Technician control system |
US8445816B2 (en) * | 2009-11-13 | 2013-05-21 | Lincoln Global, Inc. | Modular process list for welding power supply |
-
2010
- 2010-10-29 US US12/915,315 patent/US8688815B2/en active Active
-
2011
- 2011-10-31 BR BR112013010183A patent/BR112013010183A2/pt not_active IP Right Cessation
- 2011-10-31 MX MX2013004671A patent/MX2013004671A/es not_active Application Discontinuation
- 2011-10-31 JP JP2013535527A patent/JP2013543795A/ja active Pending
- 2011-10-31 CA CA2815441A patent/CA2815441A1/en not_active Abandoned
- 2011-10-31 CN CN2011800638055A patent/CN103282152A/zh active Pending
- 2011-10-31 PL PL11785476T patent/PL2632623T3/pl unknown
- 2011-10-31 EP EP11785476.0A patent/EP2632623B1/en active Active
- 2011-10-31 WO PCT/IB2011/002568 patent/WO2012056309A1/en active Application Filing
Non-Patent Citations (1)
Title |
---|
None * |
Also Published As
Publication number | Publication date |
---|---|
EP2632623A1 (en) | 2013-09-04 |
US8688815B2 (en) | 2014-04-01 |
JP2013543795A (ja) | 2013-12-09 |
WO2012056309A1 (en) | 2012-05-03 |
BR112013010183A2 (pt) | 2016-09-13 |
PL2632623T3 (pl) | 2021-12-06 |
US20120110091A1 (en) | 2012-05-03 |
CA2815441A1 (en) | 2012-05-03 |
CN103282152A (zh) | 2013-09-04 |
MX2013004671A (es) | 2013-10-28 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
EP2632623B1 (en) | System and method for welder with help request functionality | |
US9269078B2 (en) | Method and system for associating a contact with multiple tag classifications | |
US20080307086A1 (en) | Workflow Anywhere: Invocation of Workflows from a Remote Device | |
US11151518B2 (en) | Natural language event | |
US20100321175A1 (en) | Alerts Issued Upon Component Detection Failure | |
CN1452345A (zh) | 配合过程控制系统使用的万维网业务确认 | |
WO2016003728A1 (en) | System and method for implementing workflow management using messaging | |
US11663276B1 (en) | Systems and methods for generating hypermedia-based graphical user interfaces for mobile devices | |
EP2338293A2 (en) | System and method for time tracking on a mobile computing device | |
EP2406724A2 (en) | Method, computer program product, and apparatus for enabling task aggregation in an enterprise environment | |
US11340966B2 (en) | Issue tracking system having temporary notification suppression corresponding to group activity | |
US20140297318A1 (en) | Systems and methods for automatically scheduling patient visits based on information in clinical notes of electronic medical records | |
US20090210499A1 (en) | Service Identification And Decomposition For A Health Care Enterprise | |
US10860960B2 (en) | Project support system and method | |
CN115660589A (zh) | 业务审核方法、装置、设备、计算机可读介质和程序产品 | |
CN112102099A (zh) | 保单数据处理方法、装置、电子设备及存储介质 | |
US11600381B2 (en) | System for referral management | |
US20180005189A1 (en) | Identifying contacts | |
JP6204552B1 (ja) | 予約受付装置および予約受付プログラム | |
JP2011048435A (ja) | 推定論理構築支援システム、ユーザ行動推定装置、ユーザ行動推定方法およびユーザ行動推定プログラム | |
CN113011858A (zh) | 审计项目配置、执行方法和装置 | |
CN106130869A (zh) | 一种语音签到实现方法、系统及装置 | |
WO2024025522A1 (en) | Method, system and computer program product for customizable presentation of workflow transition | |
CA2533256A1 (en) | A method of notifying an invitee to an event of changes to the event in an electronic calendar system | |
KR100453389B1 (ko) | 모바일 터미널과 이를 이용한 도시가스 안전 점검 시스템및 그 방법 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
PUAI | Public reference made under article 153(3) epc to a published international application that has entered the european phase |
Free format text: ORIGINAL CODE: 0009012 |
|
17P | Request for examination filed |
Effective date: 20130429 |
|
AK | Designated contracting states |
Kind code of ref document: A1 Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR |
|
DAX | Request for extension of the european patent (deleted) | ||
17Q | First examination report despatched |
Effective date: 20140604 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: EXAMINATION IS IN PROGRESS |
|
RAP1 | Party data changed (applicant data changed or rights of an application transferred) |
Owner name: LINCOLN GLOBAL, INC. |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: EXAMINATION IS IN PROGRESS |
|
GRAP | Despatch of communication of intention to grant a patent |
Free format text: ORIGINAL CODE: EPIDOSNIGR1 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: GRANT OF PATENT IS INTENDED |
|
INTG | Intention to grant announced |
Effective date: 20210203 |
|
GRAS | Grant fee paid |
Free format text: ORIGINAL CODE: EPIDOSNIGR3 |
|
GRAA | (expected) grant |
Free format text: ORIGINAL CODE: 0009210 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: THE PATENT HAS BEEN GRANTED |
|
RIN1 | Information on inventor provided before grant (corrected) |
Inventor name: CHANTRY, BRUCE, JOHN |
|
AK | Designated contracting states |
Kind code of ref document: B1 Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR |
|
REG | Reference to a national code |
Ref country code: GB Ref legal event code: FG4D |
|
REG | Reference to a national code |
Ref country code: AT Ref legal event code: REF Ref document number: 1416476 Country of ref document: AT Kind code of ref document: T Effective date: 20210815 |
|
REG | Reference to a national code |
Ref country code: CH Ref legal event code: EP |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R096 Ref document number: 602011071494 Country of ref document: DE |
|
REG | Reference to a national code |
Ref country code: FI Ref legal event code: FGE |
|
REG | Reference to a national code |
Ref country code: IE Ref legal event code: FG4D |
|
REG | Reference to a national code |
Ref country code: SE Ref legal event code: TRGR |
|
REG | Reference to a national code |
Ref country code: LT Ref legal event code: MG9D |
|
REG | Reference to a national code |
Ref country code: NL Ref legal event code: MP Effective date: 20210804 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: HR Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20210804 Ref country code: LT Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20210804 Ref country code: BG Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20211104 Ref country code: ES Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20210804 Ref country code: NO Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20211104 Ref country code: PT Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20211206 Ref country code: RS Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20210804 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: LV Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20210804 Ref country code: GR Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20211105 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: NL Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20210804 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: DK Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20210804 |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R097 Ref document number: 602011071494 Country of ref document: DE |
|
REG | Reference to a national code |
Ref country code: CH Ref legal event code: PL |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: SM Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20210804 Ref country code: SK Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20210804 Ref country code: RO Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20210804 Ref country code: EE Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20210804 Ref country code: CZ Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20210804 Ref country code: AL Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20210804 |
|
PLBE | No opposition filed within time limit |
Free format text: ORIGINAL CODE: 0009261 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT |
|
REG | Reference to a national code |
Ref country code: BE Ref legal event code: MM Effective date: 20211031 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: MC Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20210804 |
|
26N | No opposition filed |
Effective date: 20220506 |
|
GBPC | Gb: european patent ceased through non-payment of renewal fee |
Effective date: 20211104 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: LU Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20211031 Ref country code: IT Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20210804 Ref country code: BE Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20211031 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: SI Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20210804 Ref country code: LI Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20211031 Ref country code: CH Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20211031 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: FR Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20211031 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: IE Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20211031 Ref country code: GB Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20211104 |
|
REG | Reference to a national code |
Ref country code: AT Ref legal event code: UEP Ref document number: 1416476 Country of ref document: AT Kind code of ref document: T Effective date: 20210804 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: HU Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT; INVALID AB INITIO Effective date: 20111031 Ref country code: CY Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20210804 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: SE Payment date: 20231025 Year of fee payment: 13 Ref country code: FI Payment date: 20231023 Year of fee payment: 13 Ref country code: DE Payment date: 20231018 Year of fee payment: 13 Ref country code: AT Payment date: 20231019 Year of fee payment: 13 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: PL Payment date: 20231024 Year of fee payment: 13 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: MK Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20210804 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: MT Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20210804 |