Patent Application
20100184575
1. Field of the Invention
The present invention generally relates to robotic arm end actuators and their control. More particularly, the present invention relates to methods and systems for operating and communicating to and from tools to optimize tool performance.
2. Description of Related Art
In the art of automation control, for example, the control of robots and robot-like manipulators, the robot, the robotic tool changer, and the tools handled by the robot are typically controlled by a controller, for example, a programmable logic controller (PLC) or computer. The communication between the controller and these components is typically made via a cable or bus, for example, a controller-area network (CAN) bus. The communications bus is adapated to allow communication between the controller and the tool changer and the tools to provide the desired tools and tool operation.
As is common in the art, the communication between a controller and a tool changer is typically comprises a “master-slave” relationship, whereby the controller is the “master” and tool changer and tools are the “slaves.” In the present art of automation control, the accepted communications protocol for typical master-slave communications is the DeviceNet protocol. As is known in the art, DeviceNet is a communications networking protocol used in the automation industry to interconnect control devices for the communication of data and control signals. DeviceNet is supported by the independent, international Open-source DeviceNet Vendors Association (ODVA).
However, though the DeviceNet protocol is a generally accepted communications protocol in the automation industry, DeviceNet and related protocols are characterized by disadvantages that may hamper the operation and efficiency of tool changers and tools so controlled. For example, the present applicants found such communications protocols unacceptable for the high-speed connections and disconnections and performance information gathering requirements typically encountered in this competitive industry. Moreover, the applicants also found such protocols limited in their ability to monitor, collect, and report certain operating parameters of tool changers and tools. Accordingly, aspects of the present invention were developed to overcome these disadvantages.
A robotic tool changer and systems and methods for controlling the operation of a robotic tool changer are provided that are advantageous for performing high-speed robotic connections and for gathering tool and tool changer performance information.
One aspect of the invention that addresses or overcomes the disadvantages of the prior art is a tool changer including or comprising: a robot-side component mountable to a robot arm end interface; a tool-side component adapted to engage a tool; a first slave module associated with the robot-side component and adapted to communicate with a first master module; and a second master module associated with the robot-side component and adapted to communicate with a second slave module associated with a tool. In one aspect, the first master module communicates with the first slave module by employing a first network protocol and the second master module communicates with the second slave module employing a second network protocol, for example, a common network protocol, such as the DeviceNet network protocol. In another aspect, the second slave module further comprises a power supply, for example, a rechargeable temporary power supply, such as, a super capacitor.
Another aspect of the invention is a system for controlling the operation of a robotic tool changer, the system including or comprising: a controller having a first master module; a robot having an arm end interface; a tool changer having a robot-side component mounted to the arm end interface and a tool-side component adapted to engage a tool; a first slave module associated with the robot-side component, the first slave module adapted to communicate with the first master module; a second master module associated with the robot-side component; and a second slave module associated with the tool-side component and adapted to communicate with the second master module. In one aspect, the system further comprises a robot-side module housing mounted to the robot-side component, the robot-side module housing containing the first slave module and the second master module. In another aspect, the system further comprises a tool-side module housing mounted to the tool-side component, the tool-side module housing containing the second slave module. In another aspect, the second slave module of the tool changer further comprises a power supply, such as, a super capacitor. In another aspect, the second master module may be adapted to communicate with an external receiver, for example, to an internet-enabled server. The second master module may communicate with the external receiver employing a network protocol, different from the DeviceNet protocol, for example, via the Ethernet protocol or Ethernet I/P protocol. The second master module may transmit tool changer operating parameters or tool operating parameters to, for example, an internet web page.
A further aspect of the invention is a method for monitoring the operation of a robot tool changer mounted to a robot, the tool changer having a robot-side component and a tool-side component, and the tool changer communicating to a controller via a network communications bus (for example, a CAN), the method including or comprising detecting an operational parameter of the tool changer or tool; transmitting the operational parameter to an external receiver (for example, to a receiver over the Internet) over a communications bus (for example, an Ethernet cable), different from the control network communications bus (for example, a CAN). The operational parameter of the tool changer may be input status, output status, power status, number of couplings, number of coupling/uncoupling cycles, coupling time, uncoupling time.
Another aspect of the invention is a system for monitoring the operation of a robot tool changer mounted to a robot, the tool changer having a robot-side component and a tool-side component, and the tool changer communicating to a controller via a network communications bus (for example, a CAN), the system including or comprising: a detector adapted to detect an operational parameter of the tool changer or a tool; a transmitter adapted to transmit the operational parameter; and a communications bus (for example, an Ethernet cable), different from the control network communications bus (for example, a CAN), for transmitting the operational parameter to a receiver (for example, to a receiver over the Internet).
A still further aspect of the invention is a method for controlling the operation of a robotic tool changer, the tool changer operated under the guidance of a controller having a master module and the tool changer having a robot-side component mounted to a robotic arm end and a tool-side component mounted to a tool, the robot-side component further having a slave module in communication with the controller master module and the robot-side component further having a master module in communication with a slave module associated with the tool, the method including or comprising: communicating a first control signal from the controller master module to the robot-side component slave module; communicating a second control signal, corresponding to the first control signal, from the robot-side component slave module to the robot-side component master module; and communicating a third control signal, corresponding to the second control signal, from the robot-side component master module to the slave module associated with the tool. In one aspect, the method may further comprise, prior to communication the first control signal, engaging the robot-side component with the tool-side component. In another aspect, the method may further comprise energizing at least one device on the tool side component prior to engaging the robot-side component with the tool-side component, for example, by providing a power supply, such as, a super capacitor, coupled to the at least one device to the tool-side component.
A further aspect of the invention is a method for reducing the connection time between a robot-side component and the tool-side component of a robot tool changer, the method including or comprising: energizing at least one device adapted to store at least some information about the tool-side component; coupling the robot-side component with the tool-side component; and communicating at least some date from the energized device to the robot side component. In one aspect, energizing may comprise providing a power supply, for example, a rechargeable power supply, such as, a capacitor, coupled to the at least one device to the tool-side component.
These and other aspects, features, and advantages of this invention will become apparent from the following detailed description of the various aspects of the invention taken in conjunction with the accompanying drawings
The subject matter, which is regarded as the invention, is particularly pointed out and distinctly claimed in the claims at the conclusion of the specification. The foregoing and other objects, features, and advantages of the invention will be readily understood from the following detailed description of aspects of the invention taken in conjunction with the accompanying drawings in which:
According to the prior art, the operation of the robot 14, of the actuator 12, and of the tools 22 is typically controlled by a controller 26. Controller 26, for example, a programmable logic controller (PLC) or computer, typically communicates with actuator 12 via a controller cable, wire, or bus 28. Bus 28 is typically controller-area network (CAN) bus, that is, is a network communications bus adapated to allow communication between controller 26 and actuator 12.
As is common in the art, the communication between controller 26 and actuator 12 typically comprises a “master-slave” relationship, whereby controller 26 is the “master” and actuator 12 and tools 22 are the “slaves.” For example, in the master-slave communication relationship, the master device typically has unidirectional control over the operation of the slave devices. The accepted communications protocol for a typical master-slave communications is the DeviceNet protocol. As is known in the art, DeviceNet is a communications networking protocol used in the automation industry to interconnect control devices for the communion of data and control signals. DeviceNet is supported by the international Open-source DeviceNet Vendors Association (ODVA) [having a website http://www.odva.org, which is incorporated by reference herein]. For example, as shown in
However, though the DeviceNet protocol is a generally accepted communications protocol in the automation industry, DeviceNet and related protocols are characterized by disadvantages that may hamper the operation and efficiency of the actuator 12 and tools 22 so controlled. For example, the present applicants found such communications protocols unacceptable for the high-speed connections and disconnections and performance information gathering requirements typically encountered in this competitive industry. Moreover, the applicants also found such protocols limited in their ability to monitor, collect, and report certain operating parameters of actuator 12 and/or tools 22. Accordingly, aspects of the present invention were developed to overcome these disadvantages.
In a manner similar to prior art system 10 shown in
In one aspect of the invention, system 30 may operate with a network connection from master module 47 to a slave module in robot-side component 50 via bus 48 without the knowledge of or interfacing with the master-slave network between tool-side module 52 and tools 42. For example, a master-slave network relationship may be provided between DeviceNet master module 47 and DeviceNet slave module in robot-side component 50 of actuator 32 with little or no influence or communication with the network associated with the master module 55 in robot-side module 52 of robot-side component 50 of actuator 32 and the tool 42 slave modules.
According to aspects of the invention, the applicants have found that this mode of option with a subnetwork communications system provides improved connection speeds between the tool changer 32 and the tool 42.
In one aspect of the invention, communication between the master module in tool-side component 52 in actuator or tool changer 32 and the slave modules in tools 42 is facilitated by one or more modules or subcontrollers 52 mounted to robot-side component 50 and module 60 mounted to tool-side component 61, for example, robot-side module 52 may include an electronic controller board having embedded software, associated with actuator 32. Module 60 may also function as a slave module to the master module 55 in tool-side module 52 of tool-side component 50. Modules 52 and 60 may be mounted in components 50 or 61 of actuator 32 or mounted to components 50 or 61, for example, mounted to the housing of the tool-side component of tool changer 32. According to aspects of the invention, modules 52 includes a slave module 53 that communicates with the master module 47 in controller 46 and includes a master module 55 that communicates with a slave modules (not shown) in tool-side component 60, and to one or more tools 42.
In one aspect of the invention, tool-side module 60 of tool-side component 61 may include one or more power supplies or energy storage devices 43. Power supplies 43 may be provided to provide at least some electrical power to module 60 to power one or more devices or facilitate or expedite subsequent communications, for example, handshaking, between actuator 32 and tool 42. In one aspect, power supply 43 may provide temporary electrical power to tool 42, for example, in one aspect, power supply 43 may be one or more batteries, for example, a rechargeable battery, or one or more capacitors, for instance, one or more “super capacitors” as will be described below.
According to one aspect, power supply 43 may be a chargeable or rechargeable device, for example, that may be charged or recharged when actuator 32, for example, the robot-side component 50, engages a tool, for example, engages tool-side component 61. For instance, when engaged, power can be provided to tool-side component 61, for example, from an external source. In addition, according to aspects of the invention, when robot-side component 50 of actuator 32 disengages tool-side side component 61 having tool 42, for example, when tool 42 is in a tool stand, power supply 43 can provide at least some power to tool 42, for example, in what is referred to as a “sleep state,” for instance, for a limited time, to power electrical devices on tool 42. For example, power supply 43 may power a volatile memory module or a processor performing a desired function, for example, monitoring when robot-side component 50 re-engages tool-side component 61 or monitoring when electrical power is restored to tool 42. In one aspect, when power supply 43 is a capacitor, at least initially, the capacitor may require two or more engagement/disengagement cycles or one long engagement to fully charge the capacitor. The capacitor may be sufficiently charged and provide sufficient current to energize devices on tool-side module 60 for at least 5 seconds, but typically at least 20 seconds, or even 30 seconds, for example, to provide sufficient time to power the devices of tool-side module 60 between disengagement and re-engagement with robot-side module 52.
As noted above, in one aspect, power supply 43 may comprise a “super capacitor,” for example, a super capacitor marketed under the name Aerogel by Cooper/Bussman, for example, model number KR-5R5V474-R rated at 0.47 farads (F) and 5.5 volts (V), though other “super capacitors” may be used.
Housing 72 may also include a removable cover 78 mounted to housing 72 by a plurality of fasteners 79, for example, stainless steel button head cap screws. Cover 78 may be made of a plastic, for example, a polycarbonate, such as, a transparent, abrasion-resistant polycarbonate, or its equivalent. A gasket or an O-ring seal 81, for example, a rubber O-ring, may be provided about cover 78 to substantially isolate the inside of housing 72 from the external environment. Housing 72 may also include one or more openings 82, for example, for viewing LEDs 76. Opening 82 may be provided with a cover 84 mounted over opening 82 and fastened by means of a plurality of fasteners 86, for example, alloy steel pan head thread-forming screws. Cover 84 may also be made of a plastic, for example, a polycarbonate, such as, a transparent, abrasion-resistant polycarbonate, or its equivalent. A gasket or an O-ring seal 88, for example, a rubber O-ring, may be provided about cover 84.
Subcontroller 70 may include a plurality electrical connections, for example, be connectorized, as needed. Housing 72 may include cable connectors 90, 91, 92, and 93. For example, connector 90 may be a Turck wkm 46-m cable connector and connector 91 may be a Turck wkm 55-m cable connector, or their equivalents. Connectors 90 and 91 may typically be adapted to introduce DeviceNet control and/or data signals from a robot (for example, from controller 46 and scanner 47 along bus 48) to subcontroller 70 and auxiliary power signals (for example, from controller 46) to subcontroller 70, respectively.
As shown in
Connector 92 may be a Binder 99-3729-810-04 cable connector, or its equivalent, and connector 93 may be a Turck WS 4.5T-M cable connector, or its equivalent. Connectors 92 and 93 may typically be mounted to housing 72 by means of connector receptacles 120 and 122, respectively. Receptacle 120 may be an Ethernet receptacle, for example, an M12 Ethernet female, rear-mount, 4-socket, D-coded receptacle, or its equivalent. Receptacle 122 may be a Eurofast receptacle, for example, a Eurofast female, rear-mount, 5-socket, D-coded receptacle, or its equivalent.
Connector 92 may typically be adapted to interface subcontroller 70 with a network, for example, an Ethernet network, for instance, networked with controller 46 or with external receiver 80 (see
For example, when the one or more robots used are not compatible with network communication, for example, due to the age of the robots, the one or more robots and their operation may be monitored by a PLC controller. The PLC controller (for example, as indicated by external receiver 80 in
With respect to
As shown most clearly in
Subcontroller 70 may also include one or more proximity switches 124, for example, a chrome stainless steel proximity switch provided by Balluff and having 1.5 mm detection distance. Proximity switch 124 may be provided to sense tool side module presence, for example, as a “safety” switch.
Housing 172 may also include a removable cover 178 mounted to housing 172 by a plurality of fasteners 179, for example, stainless steel button head cap screws. Cover 178 may be made of a plastic, for example, a polycarbonate, such as, a transparent, abrasion-resistant polycarbonate, or its equivalent. A gasket or an O-ring seal 181, for example, a rubber O-ring, may be provided about cover 178 to substantially isolate the inside of housing 172 from the external environment.
Subcontroller 170 may include a plurality electrical connections, for example, be connectorized, as needed. Housing 172 may include cable connectors 190, 191, and 192. For example, connector 190 may be a Turck RKF 57 5-pin, female cable connector adapted to engage a network, for example, a DeviceNet network, connector 191 may be a Turck RKFL 46, 4-pin, cable connector, and connector 192 may be a Turck FKFDL 4.4 cable connector, or their equivalents. Connector 190 may typically be adapted to introduce DeviceNet control and/or data signals from a tool (for example, from tool 42) to subcontroller 170. Connector 190 may typically be adapted to introduce auxiliary power signals (for example, from controller 46) to subcontroller 170. Connector 192 may typically be adapted to provide communication between a tool or a tool stand and subcontroller 170.
As shown in
Connector 192 may typically be adapted to interface subcontroller 170 with a network, for example, an Ethernet network, for instance, networked with controller 46 or with external receiver 80. It will be understood by those of skill in the art that the type of network and the network configuration used with subcontroller 170 may vary broadly, for example, depending upon the type of robot used, the type of application, for example, the type of manufacturing, the wiring, and the network hardware and software, among other things. Accordingly, it will be understood that the type and attributes of connector 192 may also vary.
Subcontroller 170 may also include a plurality of spring pin assemblies 206 adapted to provide robot side to tool side signal exchange, for example, between tool-side module 170 and robot-side module 70, for example by interfacing with spring-pin assembly 106 shown in
According to aspects of the invention, tool-side module 170 may include one or more power supplies or energy storage devices 143, for example, the power source 43 described above, for instance, a “super capacitor,” as described above. Power supply 143 may provide at least some power to module 170, to at least temporarily power one or more devices in module 170, for example, when module tool-side component 61, 161 is disengaged from robot-side component 50, 150 of tool changer 32.
Returning to
According to aspects of the invention, various operating parameters and/or diagnostic parameters of the tool-side component 52 of actuator or tool changer 32, may be detected, stored, and/or transmitted to receiver 80 by aspects of the invention, for example, under the control of subcontroller 60 or 70. For example, operating parameters may include input status, output status, and/or power status of actuator 32 and/or tool 42. In addition, counters may be provided for couplings, uncouplings, or coupling/uncoupling cycles, for example, for the lifetime of an actuator 32 or the lifetime for a tool 42, or for a limited time limit, for example, defined by an operator. The operating parameters may include maintenance monitoring or cycle times, for example, couple-to-couple time, uncouple to uncouple timed, couple to uncouple time, uncouple to couple time, including maximum cycles times for these events. The output format on receiver 80 may take various forms, including tabular data, histograms, and time trends, for example, to diagnose potential problems or the need for maintenance, replacement, or repair.
According to aspects of the invention, receiver 80 may be a data acquisition device, a computer, or a server, for example, for transmitting operating parameters that can be viewed on an Internet web page, for example, adjacent system 30 or remote from system 30, for instance, remotely via the Internet. In one aspect, the system 30 may provide diagnostic data extraction (for example, time and date stamped) that can be viewed graphically on a web page or in .xml format to provide a time stamped log of the status of one or more parameters.
Aspects of the present invention provide tool changers, and systems and methods for controlling the operation of robotic tool changers that overcome the disadvantages of existing tool changes, systems, and methods. For example, aspects of the invention may be advantageous for high-speed robotic connections and disconnections, and for providing tool and tool changer performance information gathering. Aspects of the invention may also enhance the capability to monitor, collect, and report certain operating parameters of tool changers and tools. As will be appreciated by those skilled in the art, features, characteristics, and/or advantages of the various aspects described herein, may be applied and/or extended to any embodiment (for example, applied and/or extended to any portion thereof).
Although several aspects of the present invention have been depicted and described in detail herein, it will be apparent to those skilled in the relevant art that various modifications, additions, substitutions, and the like can be made without departing from the spirit of the invention and these are therefore considered to be within the scope of the invention as defined in the following claims.
This application claims priority from pending U.S. Provisional Patent Application 61/146,214, filed on Jan. 21, 2009, the disclosure of which is included by reference herein in its entirety.
| Number | Date | Country | |
|---|---|---|---|
| 61146214 | Jan 2009 | US |
