Patent Grant
9584585
Not applicable
The present invention relates to control devices and, more particularly, to drives employed to control operating characteristics of motors.
Drives are control devices that are employed to control, monitor and/or otherwise interact with a variety of operational characteristics and parameters of motors such as, for example, motor speed, motor torque, motor power usage, etc. A wide variety of drives are available for use in conjunction with a wide variety of types of motors, including both alternating current (AC) motors such as synchronous motors and induction motors, and also direct current (DC) motors. Drives can also be used to control, monitor, or otherwise interact with a variety of other electromechanical machines such as generators and motor/generator hybrids (or even other types of machines and/or processes).
The control provided by drives includes the direct control over the power flow to the controlled motors or machines. Many drives are pulse width modulated (PWM) drives that rapidly turn on and off the flow of current (and the voltages) applied to the motors being controlled. In some circumstances, power that is effectively AC (including, for example, three-phase AC) can be provided to a motor simply by switching on and off DC sources with respect to the motor in an appropriate time-varying manner. Often, such PWM drives include a circuit board. with a controller (e.g., a computer, microprocessor or programmable logic device (PLD)) and an array of controllable power switching devices such as power transistors that are switched on and off by the control device.
Drives can be used to control motors of a variety of different power levels. A medium voltage AC drive, for example, generally is understood to be a drive used to control an AC motor requiring input voltages within the range of about 2400 to 7200 Volts AC. Exemplary medium voltage AC drives include, for example, the Allen-Bradley PowerFlex 7000 family of drives manufactured by Rockwell Automation, Inc. of Milwaukee, Wis., the beneficial assignee of the present application. In contrast, a low voltage AC drive typically would he used to control an AC motor requiring input voltages at lower levels (e.g., 480 Volts AC), while a high voltage AC drive would be used to control an AC motor requiring input voltages at higher levels (e.g., 10,000 Volts AC). Drives can likewise be configured for operation with other types of motors and other machines that are intended to operate at a variety of different power levels or require a variety of different power characteristics.
It is usually only possible for human beings (or other entities, e.g., computers) to interact with conventional drives in limited manners and/or within restricted environments. For example, in industrial environments, it is often only possible for human beings (e.g., technicians or other personnel who are operating or monitoring a manufacturing process) to control and/or monitor the operation of drives in an indirect manner by way of signals communicated via intermediate devices. Various different types of intermediate devices are possible. For example, the speed of a drive can be controlled by a speed potentiometer connected to an analog input of the drive and manually adjusted by the operator, while starting and stopping of the drive can be controlled through the use of hardwired pushbuttons for Start and Stop. Also, in some circumstances, specialized control terminals with specialized graphical user interfaces (GUIs) allow operators to access drives to which those control terminals are in communication.
Nevertheless, to the extent that drives are accessible by human beings (or other entities) by way of such intermediate devices, the manner of access is often constrained by the requirements of those intermediate devices. For example, in circumstances where access to drives is made possible by way of specialized control terminals with specialized GUIs, interaction via such control terminals/GUIs often requires the installation and use of special proprietary hardware and/or software at the locations of the operating personnel, for example, a PanelView 550 Monochrome Terminal available from Rockwell Automation equipped with appropriate firmware. Also, to the extent that such control terminals/GUIs require software (particularly firmware), such software often is only appropriate for use with a given terminal/GUI and is not transferable to other terminals/GUIs. This is the case even where a control terminal is capable of receiving information from a drive via a standardized type of connection such as an Ethernet connection.
Additionally, even where specialized control terminals/GUIs are employed in conjunction with drives to facilitate the accessing of the drives, such access is usually limited in terms of the rapidity with which desired information can be obtained from the drives and/or the rapidity with which commands or other information can be provided to the drives. The coupling of such control terminals/GUIs to drives typically involves the use of one or more intermediary hardware coupling components connected in between the terminals/GUIs and the drives. Also, the communication of signals between the control terminals/GUIs and the drives typically requires the addition and removal of protocol information in relation to the signals. Both the interposition of intermediary components and the addition/removal of protocol information slow down the rate at which information can be communicated between the control terminals/GUIs and the drives.
Further, because special proprietary hardware and/or software is typically required to allow persons to interact with drives by way of such control terminals/GUIs, and because such hardware and/or software is separate from (albeit directly or indirectly coupled to) the hardware and/or software implemented on the drives themselves, changes to aspects or features of the drives often necessitate changes in the hardware and/or software allowing accessing of the drives. If appropriate changes to the accessing hardware/software are not made, compatibility problems can result. Yet configuring/upgrading of the hardware and/or software (e.g., firmware) on a control terminal separate and/or remote from a drive often is burdensome and costly, as it typically requires a technician to visit the control terminal and install software onto and/or otherwise modify or reconfigure the control terminal. While configuring/upgrading of a drive typically necessitates configuring/upgrading of the control terminal, typically the configuring/upgrading of the two devices cannot be performed in a coordinated manner, e.g., simply by performing a single action or process or with a single package.
In addition to providing access to motor drives in the aforementioned manners, it is also known (particularly in industrial environments) to provide access to motor drives via programmable logic controllers (PLCs) that are in communication with the drives. In recent years, PLC devices having both PLCs and accompanying web servers (e.g., “web-enabled PLCs”) have been developed allowing users to access, via the Internet, both the PLCs as well as devices coupled to the PLCs such as motor drives. However, the access to motor drives afforded by such web-enabled PLCs is disadvantageous for several reasons. First, while configuring/upgrading of a drive typically necessitates configuring/upgrading of software or other information on the web-enabled PLC, such configuring/upgrading of both devices typically cannot be performed in a coordinated manner, e.g., simply by performing a single action or process or with a single package.
Further, communication of any data between the drives and the web servers (and thus between drives and users on the Internet) is restricted by the processing/transmission efficiency of the PLCs themselves, which are situated between the web servers and the drives. Communication between the web servers and the drives also is restricted insofar as typically the signals sent to and received from the drives by the PLCs are communicated by way of any one of a number of proprietary intermediary devices including, for example, backplanes associated with the PLCs and various signal processing devices. The operation of such intermediary devices typically restricts the types of information that can be communicated, and considerably slows down the speed with which information can be communicated between the drives and PLCs, thus limiting the volume of information that can be transmitted effectively in a given time period. In some cases, communication adapters or converters are often coupled in between the PLCs and the drives, further restricting the types of information that can be communicated and reducing the speed of communication. For at least these reasons, web-enabled PLCs do not resolve the aforementioned problems associated with providing access to drives.
Although additional systems also exist that include web servers in association with other devices (e.g., other than PLCs), it is unclear whether such additional systems might be capable of providing improved access to drives. As in the case of web-enabled PLCs, a number of such systems employ web servers that are in communication with other devices by way of backplanes, backplane drivers and/or other intermediary devices. Consequently, communications between the web servers and other devices are typically delayed or restricted in various manners, such that any information to he communicated to and from those other devices by way of the web servers also tends to be delayed or restricted in various manners. Thus, as in the case of many of the other above-described systems, it would appear that it still would be difficult to configure or upgrade both a drive and associated web server in a coordinated, efficient manner.
Given the ubiquity of drives for controlling motors, other electromechanical machines and other machines in many environments including (but not limited to) industrial environments, and given the above-described limitations associated with controlling, monitoring and otherwise interacting with such drives as they are conventionally implemented, it would be desirable if an improved drive/drive system could be developed that would overcome one or more of these limitations. For example, it would be desirable if an improved drive system could be developed that in at least some embodiments provided enhanced access in terms of communication with other systems or entities (and/or operators or other personnel). More particularly, it would be desirable if an improved drive system in at least some such embodiments allowed for enhanced communication of commands and other information to and/or from the drive system, such that the speed of communicating information/commands to and from the drive system was not as significantly reduced due to the presence of intermediary hardware components and/or the addition/removal of communication protocol information as in conventional systems such as those discussed above.
Also for example, it would be desirable if an improved drive system could be developed that in at least some embodiments was accessible without the need for installing significant specially-designed or proprietary hardware (e.g., a specialized control terminal) or software at the location of the person or entity desiring access. Indeed, it would be further desirable if such an improved drive system could be developed that allowed access at multiple locations without the installation of different specially-configured hardware and/or software at those various locations. Additionally, it would be desirable if such an improved drive system could be developed that in at least some embodiments eliminated or reduced the possibility of incompatibilities arising between the drives and the access terminals/devices despite the upgrading or other modification of the drives, and alleviated sonic of the costs associated with configuring, upgrading or other modification of the drives.
The present inventor has recognized that some or all of the above-described disadvantages associated with conventional drives can be alleviated by an improved drive system that includes a server (and appropriate software). In at least some embodiments, the server and drive are directly integrated with one another, either by placing the processing units of the server and drive in direct communication with one another, or by utilizing a single processing unit to govern both the server functionality and the drive functionality (so as to provide complete/full integration). By integrating the server and drive in such manners, there are no (or virtually no) delays or restrictions in communicating information antler commands between the server and drive, and large amounts of data can rapidly be transmitted between the server and the drive. Thus, the speed of access to the drive by way of external terminals in communication with the server is enhanced due to the server being fully integrated with the drive.
In at least some embodiments, by virtue of the server, such a directly integrated drive system can communicate with one or more user-accessible terminals located either proximate the drive system or remotely therefrom, via an internet or intranet-type connection/network (and, in at least some such embodiments, via the World Wide Web). Assuming that the server includes appropriate software and other information (e.g., including HTML code/applets), the software/information for generating a graphical user interface (GUI) on the terminals appropriate for enabling user access of the drive can he largely if not entirely stored within the server and then made available to the user-accessible terminals. With such a system, direct user access of the drive becomes possible without the use of specialized, proprietary software or hardware at the location(s) of the users, since conventional browser-equipped computers or other similar terminals will suffice as the user-accessible terminals.
Further, in at least some embodiments, compatibility issues between the drive and the user-accessible terminals that might otherwise arise due to updates or other modifications to the drive can be largely or entirely eliminated. That is, when updates or other modifications to the drive are made, all that is needed in terms of appropriately updating the manner of operation of the user-accessible terminals is the appropriate updating of the software/information at the server. Also, in at least some embodiments, to facilitate implementation of the improved drive system into industrial automation systems employing industrial control protocols and proprietary interfaces, the server is configured to communicate with the outside (including the provision of real time data) by way of Ethernet/IP protocols. Further, in at least some embodiments, the server has a FTP capability that further facilitates the transfer of large amounts of information. Additionally, in at least some embodiments, executable files can be transferred.
In at least some embodiments, the present invention relates to a drive system that includes a first module that operates as a server, where the first module is at least one of directly integrated with a second module that operates as a drive and fully integrated to include the drive.
Further, in at least some embodiments, the present invention relates to a drive system including a server, and a first drive, where the server and the drive are in communication with one another, and where the server is capable of communicating at least one web page onto an internet-type communications medium for receipt by an additional terminal. The server is further capable of communicating at least one executable program onto the internet-type communications medium.
Additionally, in at least some embodiments, the present invention relates to a method of communicating with a drive. The method includes providing a server that is at least one of directly integrated and fully integrated with the drive, sending a web page from the server onto an internet-type communications medium for receipt by a terminal, and receiving a communication arriving from the terminal at the server off of the internet-type communications medium.
Further, in at least sonic embodiments, the present invention relates to an add-on component for implementation in relation to a drive. The add-on component includes a module configured to be coupled to a port of the drive, where the module includes a server. When the module is coupled to the port, the server is directly integrated with the drive.
Additionally, in at least some embodiments, the present invention relates to a computer-readable medium embodying instructions for a processor to perform a method of communicating with a drive. The method includes sending a web page from the server onto an internet-type communications medium for receipt by a terminal, providing at least one of an executable program and information following a FTP protocol from the server onto the interact-type communications medium for receipt by the terminal, and receiving a communication arriving from the terminal at the server off of the internet-type communications medium.
Referring to
The motor 4 in the present embodiment is a medium voltage three-phase AC synchronous motor (requiring voltages within the range of about 2400 to 7200 Volts AC). In alternate embodiments, the motor 4 could also be a high or low voltage AC motor or another type of motor, for example, an induction motor (of any voltage level), a DC motor, or a linear motor. Further, the motor 4 is also intended to be representative of other types of electromechanical machines such as generators or generator/motor hybrids, or even combinations of multiple motors and/or other machines, or processes. Indeed, the motor 4 is intended to be representative generally of any device(s) or process(es) that is/are capable of being controlled by the drive system 2, the other drive systems discussed below, or any other type of motor drive or similar system (e.g., a drive for another electromechanical machine).
To control the operation of the motor 4, the improved drive system 2 includes a drive module 8 that, as illustrated, includes a control unit (or “drive control”) such as a central processing unit (CPU) 10. In the present embodiment, the drive system 2 is a pulse width modulated (PWM) drive system; in which the CPU 10 controls the operation of the motor 4 (at least in part) by rapidly switching on and off the currents/voltages applied to the motor. More particularly, the CPU 10 of the drive module 8 as shown governs the operation of the motor 4 by providing control signals to multiple power switching devices 12, which can be power transistors, for example. By appropriately turning on and off the power switching devices 12, effectively alternating current (AC) power can be provided to the motor 4, such that the motor can be driven as an AC motor.
In some embodiments of the present invention, the drive module 8 is a full-fledged drive system or drive that is capable of independent operation on its own (e.g., independently of the other portions of the drive system 2), for example, a PowerFlex 7000 MV AC drive available from Rockwell Automation, the beneficial assignee of the present application. In other embodiments, the drive meddle 8 can be something less than a complete drive system/drive that i capable of operating independently. Indeed, although the drive module 8 of
Although the drive module 8 of
Further as shown in
The server module 14 stores a variety of information. In particular, the server module 14 stores a website with one or more web pages 22, which can be in the form of HTML (hypertext markup language) code as weld as include applets (e.g., JAVA applets). Often, the web pages contain text as well as possibly graphical images and/or hypertext links to other web pages, which can be stored internally within the server module 14 and/or at external sites. Additionally, in at least some embodiments, the server module 14 stores executable programs 23. Such executable programs can include executable binaries, for example, .NET or Microsoft Foundation Class (MFC) based programs, which can utilize the .NET framework and/or the .NET Compact Framework available from Microsoft Corporation of Redmond Wash. Also, the server module 14 is capable of storing and processing other information 21 including, for example, data regarding performance of the server module, the drive module 8, the overall drive system 2, the motor 4, or other data. In at least some embodiments, as discussed in further detail below, the server module 14 is configured to allow for communication of such data via the file transfer protocol (FTP).
The web pages 22, executable programs 23 (or components of such programs), and/or other information 21 stored and/or processed at the server module 14 can be provided via the Internet 18 to one or more terminals or web clients, which are shown in
By virtue of their respective browser programs, the terminals 24, 26 can communicate with the server module 14 via the Internet 18 (and the additional communication link 20) and access the website so as to download the web pages (including applets) 22, as well as the executable programs 23 and other information 21. Further, in some embodiments, other programs or tools on the terminals 24, 26 also can be employed in addition to (or instead of) browser programs to download information such as the information 21, e.g., programs allowing for information to be transferred to the terminals via FTP. As discussed further with respect to
More specifically, to access the website hosted by the server module 14, a user at one of the terminals 24,26 types a Uniform Resource Locator (URL) address, which in turn causes a connection to be established between the terminal and the server module 14 and causes the retrieval of one or more files (possibly in the form of web pages) 22 from the server module. In the present embodiment, the browser program employed by the terminals 24,26 includes a Java virtual machine (VM) in order to execute Java applets and classes. Embedded within the HTML code of a web page typically are one or more references to one or more Java classes. The browser requests such a Java class from the server module 14 and executes the returned code, so as to transform the generic browser-equipped terminal 24 or 26 into a terminal that is appropriate for use m interacting with the drive system 2. As various interface objects (for example, tabs, buttons, fields as discussed below with reference to
In the embodiment of
While
Also, the particular physical devices and protocols utilized for communications between the terminal(s) and the drive system 2 corresponding to the seven layers of the OSI model can vary depending upon the embodiment. In the present embodiment, to provide real-time data from the drive system 2/server module 14, one or more of the Java classes provided to the terminals 24, 26 are able to make requests to the server module 14 using the Ethernet/IP (Ethernet/industrial protocol) adaptation of CIP (as is used by DeviceNet or ControlNet). This includes the stack layers of Ethernet (Physical and Datalink), IP, TCP, and CIP Encapsulation. Two additional protocols are also employed, which are embedded within the CIP layer, PCCC and DPI. It is information in the DPI protocol that the drive system 2 ultimately understands and will respond to for the purposes of delivering real time data.
Notwithstanding the above description, in alternate embodiments a variety of other physical devices and protocols can be employed corresponding to the different layers of the OSI model. For example, in some embodiments, the communication link 20 could (instead of having an Ethernet-type physical layer) have a physical layer that is CAN-based, or otherwise different from an Ethernet-type physical layer. In still additional embodiments, one or more serial connections (e.g., RS232-based connections or connections employing 20-COMM-E modules available from Rockwell Automation) can also be utilized as the communication link 20 (and/or in place of the Internet 18 as shown in
Also for example, with respect to the network layer, while the interact protocol (IP) is typically utilized, other protocols could also be employed (e.g., IPX). Additionally for example, with respect to the transport layer, typically the TCP protocol is utilized but, in some alternate embodiments, other protocols such as the UDP protocol or the DPI/ScanPort protocol could also be used. Further for example, with respect to the application layer, any of HTTP, FTP, Telenet, SNMP, NFS or a variety of other protocols can be used instead of CIP or Ethernet/IP. In at least some embodiments, in terms of firmware, the interact protocol stacks are required to provide standard message passing via an Ethernet connection. Ideally, these are available as a library so that resources are not required for coding and testing. Through the use of a library, firmware efforts are directed at providing application support unique to the drive (as well as any unique protocols, e.g., protocols unique to the automation industry where the drives are being used in an automation environment).
In at least some embodiments, the server module 14 also facilitates the efficient transferal of files between the drive module 8 and the terminals 24, 26, typically using FTP. In this manner, the terminals 24, 26 are able to obtain various information concerning operation of the drive module 8 and/or the motor 4 including, for example, reports, configuration data, diagnostics data, and instructional data from the drive module. Also, typically by way of FTP, it is possible for new firmware components or configuration data to be loaded into the drive system 2 by way of FTP. Further, the terminals 24, 26 are able to gain real time access to various operational, diagnostics or other data regarding the drive module 8 and/or the motor 4 using the Ethernet/IP (Ethernet/industrial protocol).
In view of the above discussion, in at least some embodiments, the server 14 can be understood as including more than one server, or multiple “sub-servers”. For example, the server 14 can include a first sub-server dial is a web server or HTTP server, a second sub-server that is a FTP server, and a third sub-server that is an Ethernet/IP server. Other versions of the server 14 can include any one or more of these (and/or other) server capabilities. Again for example, in some embodiments, the server 14 would only include the FTP server capability but not the Ethernet/IP capability or web/HTTP capability. In further embodiments, the server 14 can include other sub-server(s) having other server capabilities in addition to, or instead of, server capabilities relating specifically to the aforementioned server capabilities relating to the communication of web/HTTP, FTP, and Ethernet/IP-type data.
By employing a server or similar device on the improved drive system 2 as shown in
Turning to
In the present embodiment employing the Ethernet communication link 20, the RS232 port 42 is a redundant communications port that is not utilized. However, in alternate embodiments, it can be used in addition to or instead of the Ethernet port 41 to achieve communications between the server module 14 and external devices such as clients/terminals as discussed above. In particular, the RS232 port 42 can he utilized to achieve point-to-point serial connections with terminals where an Ethernet network is not available or required. In such embodiments, the protocols associated with the upper levels of the OSI model would still be used, but the protocols/structures associated with the lower levels (e.g., physical layer, data link layer, network layer and transport layer) would be different and appropriate for the RS232 connection. Although
The CPU 40 is additionally coupled to a plurality of memory devices including a random access memory (RAM) device 43, a flash memory device 44, and a dual port random access memory (DPRAM) 46. The CPU 40 is coupled to each of the memory devices 43-46 by way of one or more additional internal communication links or internal buses 47. In contrast to the other memory devices 43-45, the DPRAM 46 in particular is capable of being in communication not only with the communication links 47 but also with the internal communication link(s) 16 discussed above with respect to
In terms of the physical structure of the server module 14, in at least some embodiments the server module is formed by way of a plug-in card such as a Personal Computer Memory Card International Association (PCMCIA) card (which can be an approximately 3.5 inch by 2 inch card) that plugs into a port existing on the drive module 8. Plugging-in of the card into the port allows for coupling of the DPRAM 46 to the communication link(s) 16 of the drive module 8. Use of such a card allows the drive system 2 to implemented in a modular manner. Consequently, Internet connectivity can be viewed as an option but not a necessity (e.g., the server can be added to a drive at a later date). Also, the use of such a card allows the drive system to be more easily adapted to newer or different server platforms in the future if required. Such adaptability could be advantageous in a variety of scenarios including, for example, where a choice of third party CPU core has become obsolete, where storage memory or processing power requirements change or increase, etc.
In other embodiments, the server module 14 need not be implemented on a plug-in card, but rather can take on a more conventional physical structure such as a circuit board mounted within a housing for the drive system 2, e.g., the same housing in which is housed the drive module 8. Also, in some embodiments, the server module 14 and drive module 8 could be implemented on the same microchip. In all (or at least most) embodiments, regardless of whether the server module 14 is implemented in the form of a modular card or otherwise, the server module 14 should be coupled in very close proximity to the CPU 10 of the drive module 8 (e.g., a few inches, for example, less than four inches) to avoid engendering speed and noise issues.
The improved drive system 2 of
Notwithstanding the different functional responsibilities of the drive module 8 and the server module 14 of the drive system 2, in the present embodiment the to modules are directly integrated with one another (that is, the two modules are in intimate association or embedded with one another) since the respective CPUs 10, 40 of the two module 8, 14 are directly coupled to one another by way of the DPRAM 46 (and the communication link(s) 16, 47). The DPRAM 46, unlike many other possible intermediary devices, allows for nearly seamless, perfectly transparent communications between the CPUs 10, 40, almost as if the CPUs 10, 40 shared the same memory bus. More particularly, the DPRAM 46 does not add or remove, or necessitate the addition or removal of, any protocol information (including, for example, checksum information) with respect to any of the signals provided on the communication links 16, 47. Nor does the DPRAM restrict the communication of information in any manner. As a consequence, data can be passed back and forth between the CPUs 10, 40 in an effectively delay-free, uninterrupted, and unrestricted Manner, and very large amounts of data can be efficiently passed back and forth between the CPUs, in a real time manner if necessary. Further as a result; the CPUs 10, 40, and the drive module 8 and server module 14 of which those CPUs form a part, can be viewed as operating as almost a single module.
Because of the direct integration of the drive module 8 and server module 14 via the DPRAM 46, communications are facilitated not only between those two modules but also between the drive system 2 and the external terminals 24, 26 that are coupled to the drive system by way of the Internet 18. In particular, because data at the drive module 8 can be immediately and efficiently communicated from the drive module to the server module 14, such data (or derivative data as generated by the server module based thereupon) can be more rapidly and efficiently communicated to the terminals 24, 26. Likewise, commands and other data transmitted from the terminals 24, 26 to the server module (and other derivative commands and data generated by the server module based thereupon) can be more rapidly and efficiently transmitted to the drive module 8. Messages communicated from the terminals 24, 26 are directed toward the directly integrated server module and drive module, rather than toward some other location remote or only loosely connected with the drive module.
Although the improved drive system 2 of
While
The embodiment of
While
Through the use of such directly-integrated designs, communication between the various (e.g., server and drive) modules can occur without significant delays or interruptions that might otherwise occur due to the use of such intermediary devices or the addition/removal of protocol information. Consequently, the server is able to operate in nearly constant, uninterrupted, and instantaneous communication with the drive control (or drive module), such that large amounts of monitored information regarding performance of the drive control (or the entire drive system) can be rapidly and continuously provided to the server, and such that commands and other information provided by the server to the drive control (or drive module) are supplied in a rapid, continuous meaner as well. Further, while delays may still occur between the server and any terminals that are in communication with the server by way of the Internet or other communication linkages, communication delays or interruptions arising from the manner of communication between the server and the drive control (or drive module) controller are largely (if not entirely) eliminated.
Although the above-described embodiments of the present invention are embodiments in which a drive module and server module (or multiple such modules) are directly integrated or (in the embodiment of
In such embodiment, the Ethernet connection and associated protocols are used to communicate onto the communication link 20 and thereby with the terminals 24, 26 via the Internet 18, while the other hardware medium/protocol(s) are used to communicate with the drive module 55 by way of a communication link 58, which also may be tightly controlled or proprietary. From the perspective of the drive module 55, the adapter 56 is external, although physically the adapter could be situated along with the drive module within a shared housing or enclosure.
One example of an adapter 56 with respect to which the server 57 could he integrated is the above-mentioned 20-COMM-E module available from Rockwell Automation. This module is capable of converting an Ethernet signal into a physical CAN (Controller Area Network) signal, and vice-versa. The protocol used on the CAN side is the DPI (Drive Peripheral Interface) protocol, also available from Rockwell Automation, while the protocol used on the Ethernet side can be (as described above) the Ethernet/IP protocol built on top of the standard TCP/IP protocols used for transporting messages over the Ethernet link.
The 20-COMM-E module particularly suited for operation as the adapter 56 in conjunction with the Internet 18 on several counts. First, a 20-COMM-E module includes multiple HTML pages that can be used to gather information about the 20-COMM-E module (e.g., about the adapter 56) and to configure its operation (albeit not the configuration of any associated drive module). The 20-COMM-E module also has the capability of sending email messages (if appropriately configured) when a fault occurs in the associated drive module 55. However, while a 20-COMM-E module can serve as the adapter 56 between the Ethernet communication link 20 and the CAN-DPI communication link 58, the module has several limitations in this regard. First, information being passed over the CAN-DPI communication link 58 to the drive module 55 from the adapter 56 is limited to that defined by the DPI Protocol. Also, while the adapter 56 is capable of providing real-time control feedback and drive configuration data via a physical Ethernet connection, the adapter is not capable of serving web pages from the drive or providing FTP services for the files in the drive.
Another example of the adapter 56 other than a 20-COMM-E module would simply he a dedicated server that, instead of being directly or fully integrated with the drive module (as in the case of
Referring to
Although
Turning to
More specifically, the forms/dialogs/pages shown in
Referring in particular
As noted above, the present exemplary
Referring to
Given a particular user-specified Access level and Filter level, the web page 80 then allows the display of certain corresponding amounts of information and also allows for (or restricts) the entry of certain types of requests/commands from the user. In the present example, given a Basic Access level and a Read/Write Filter level, a variety of information is displayed in a left field 87 of the web page 80. The information displayed in the left field 87 includes, as shown, a list of selectable parameter groups such as “Feedback”, “Feature Select”, “Motor Ratings” and several others (the particular parameter groups shown need not always be present, nor are exhaustive of all possible parameters; for example, in some alternate embodiments, the information displayed in the left field 87 could also include additional parameter groups such as “Control Masks”, “Owners”, “Logic I/O” and “Adapter I/O”). Upon receiving a user selection of one of these parameter groups, a second list of specified parameters corresponding to the selected parameter group appears in a right field. 88. In the example shown, the Motor Ratings parameter group was selected in the left field 87 and, consequently, a variety of specifiable motor parameters (e.g., “Motor Poles”, “Rated Motor Amps”, etc.) are shown in the right field 88, gene of the specifiable motor parameters is selected, then a further pop-up form 89 appears in which the user is presented with an opportunity to modify or specify a motor parameter. In the example shown, the “Rated Motor Amps” motor parameter has been selected from the right field 88, and consequently the pop-up form 89 provides d 90 in which the user could enter a new value for rated motor Amps.
Turning to
With respect to
This method of assigning a parameter to a port (including all of the selection operations) in the context of the Analog tab 94 is also employed in the context of the PLC tab 95. Further, the method of selecting a parameter for viewing or modification in the context of Parameters tab 93 is similar to that discussed with respect to the Display web page 80. In all cases, the Access 81 and Filter 82 properties limit the displayed information.
Turning to
Once communication is established, first and second windows 122 and 126 are provided. In the first window 122, folders (or other memory locations) associated with the terminal (e.g., memory locations within the computer forming one the terminals 24, 26) are displayed while, in the second window 126, files that reside at the server module (or at some other portion of the drive system 2 such as the drive module 8) are displayed.
Once the first and second windows 122, 126 are displayed, the user can then cause the contents of a file listed in the second window 126 to be copied into a selected folder/memory location within the terminal simply by dragging and dropping the icon associated with that file (e.g., an icon 120 as shown) onto an appropriate folder icon (e.g., an icon 125) within the first window 122. Such a file transfer capability facilitates direct access to reports within the drive module and updating of firmware components. In at least some embodiments, a similar procedure could be followed also in terms of copying executable programs (or components of such programs) such as the executable programs 23 discussed above from the drive system 2 to one of the terminals 24, 26.
Also, it should be noted that, while embodiments of the present invention make it possible to communicate with a drive from a terminal using standard web browser program technology and tools such as Internet Explorer™ and File Explorer, various embodiments of the present invention also make it possible to facilitate industrial control protocols. For example, the server module 14 in at least some embodiments has a capability involving the Ethernet/IP protocol that allows for connection of the drive system 2 to existing proprietary software packages and tools (e.g., Drive Tools™ or Drive Explorer™ available from Rockwell Automation). Further in at least some embodiments, the server module 14 can be coupled to one or mere programmable logic controllers (PLCs) via PLC connections.
The present invention is intended to encompass a variety of different drive systems that are equipped with a communications system that allows for communications with one or more outside terminals in a manner that does not require significant special configuration or tailoring of those outside terminals for interaction with the particular drive system. Such a control system facilitates a variety of interactions with drives and their associated motor(s) (or other controlled machine(s)) that would otherwise be difficult or not possible. For example, such a control system makes it possible for a user to remotely control a drive system and/or an associated motor or other controlled machine(s), potentially from numerous locations (e.g., from numerous terminals around the world). Such control can include not only starting, stopping, or modifying the operation of a motor (e.g., increasing or decreasing its speed or torque) via the drive system, but also include providing configuration instructions to the drive system, such as instructions regarding what motor parameter should be monitored or modified (and or how to perform such monitoring/modification). In at least some embodiments, the present inventive system makes it possible to perform drive firmware configurations or upgrades via the established connection.
Further, such a user can also remotely monitor the drive system and/or associated motor or other machine(s), to allow for “remote diagnostics”, “troubleshooting” and other operations. Numerous parameters can be monitored, which can relate to, for example (in the case of a motor), operating variables, drive configuration, motor ratings, motor and drive faults and/or related safe modes of operation, and coordination of one motor with another motor. Because such monitoring and control capabilities become available by virtue of the present invention, it also becomes possible for users to remotely control a given drive system or motor (or other controlled machine(s)) in relation to other drive systems or controlled machines, and to achieve coordinated control of multiple drive systems and/or controlled machines. Such monitoring and control capabilities are useful in a variety of industrial, commercial, residential, transportation-related and other environments.
The drive system control and/or monitoring capabilities afforded by various embodiments of the present invention can serve a variety of purposes. For example, in a development environment, a user may desire to program the drive system. Not only can embodiments of the present invention allow for such programming, but also at least some embodiments of the present invention allow a user to rapidly download new code for debugging, provide the user with access to extended trending, event logs and customized reporting (e.g., histograms), and allow a user to connect to multiple drives from the same development platform (e.g., from the same terminal/personal computer). Indeed, at least some embodiments of the present invention are particularly beneficial insofar as they allow any terminal/personal computer/workstation to access any drive that is connected to the network (such that point-to-point connections are not required), allow downloads to the drive to be performed at higher transfer rates than would otherwise be possible, and allow a user to accomplish tasks using familiar browser program technology and other familiar software programs (e.g., programs involving “drag and drop” features). The FTP server functionality described above with respect to
Embodiments of the present invention employing the browser-equipped terminals allow a user to both monitor the drive system and motor (or other machine) coupled thereto, as well as to perform diagnostics and order self-diagnostic tests/routines to be performed. Additionally, the browser-equipped terminals allow a user to control the setting up of each of the drive system and the motor (or other machine) coupled thereto, even possibly when the drive system and/or motor (or other machine) are first being manufactured. That is, embodiments of the present invention can be useful in setting up/configuring/testing the drive system and the motor (or other machine) coupled thereto, both in a “test bay” circumstance when the systems are first being manufactured, as well as in a “customer support” or “product support” circumstance after the system is already being operated in the field.
Further, due to the direct or full integration of the drive/drive module and server/server Module in at least some embodiments of the present invention, the introduction or upgrading of software, firmware or other aspects of both the drive and server can be performed in a coordinated manner, as a result of one action or procedure such as the introduction of a single software package. That is, in such embodiments, it is not necessary to conduct multiple, independent procedures to configure or upgrade the drive and server independently, but rather each of the drive and server (and, more particularly, each of their CPUs or other control devices, or their shared CPU or control device) can be configured or upgraded together in a single operation.
In a “test bay” circumstance, a ‘payload’ (e.g., firmware, language module, Drive Identity Module (DIM) data, XIOLogix program) for a particular job can be sent to a drive system such as the drive system 2 from a central server. The contents of the payload, which would typically be configured by technical personnel, allow each job to be customized without a need for manual loading in the test bay. For example, a particular job may require a different version of firmware from the standard version being shipped with other drives, due to functionality or compatibility with other systems. Only certain jobs receive a language module, which also differ depending on the country of destination. The DIM data which is already unique for each job can be downloaded directly to the drive and burnt into the DIM. Each of these operations relating to configuring the drive system with a payload, which conventionally might be done in a sequence of manual steps, can be automated using a single step. Different payloads can be automatically communicated to different drive systems simply by selecting a job number/item and downloading the respective payload to the respective drive. Further, incorporation of a payload into a given drive can also be followed with a set of predefined test bay parameters based on the motor setup required for the test bay dynes, again removing any manual entry requirements.
As for a “customer support” or “product support” circumstance, web-based embodiments of the present invention arc particularly advantageous insofar as a web based terminal not only ensures continual compatibility with new drive firmware (as the terminal firmware is part of the drive firmware), but allows remote connections to the drive using the same interface as if at the drive itself. A hardwired, distance limited connection no longer need be employed between the drive to the terminal, and individual proprietary software (with possible compatibility issues) running on a personal computer is not required. In addition, more then one terminal can be used. As a result, customers can easily place one or more terminals in a control room or remote site in addition to at the drive locally. When product support is required, customers or service personnel can each use the same familiar interface from their respective offices, even though the drive system is located at a remote site. Further, the FTP capability discussed with respect to
Although many of the above-described embodiments involve the use of a “server” that is capable of sending web pages onto an internet-type communications medium, or capable of sending web pages in addition to other types of information (e.g., information following the FTP protocol or executable programs) onto an internet-type communications medium, the present invention is also intended to encompass other embodiments in which other types of communications media are employed. For example, in some embodiments, other types of media for communication in relation to other types of networks, (e.g., Token Ring networks, Firewire networks, USB-type networks, etc.,) can be utilized, where the servers are directly or fully integrated or otherwise associated with drives. Also, at least some embodiments of the present invention are envisioned in which the server only provides non-web page information such as information in accordance with the FTP protocol and/or executable programs. Thus, the present invention is not limited to embodiments that employ only a web server as a server.
Further, in the above discussion, a “drive system” or “drive” is understood to be a device that interacts with motors and/or other controlled devices that lack intelligence. For example, while a drive system will typically control the actual currents and/or voltages that arc applied to the motor so as to govern the operational behavior of the motor (e.g., its frequency of operation), a drive system will not typically communicate in other manners with the motor (e.g., for configuring the motor or for data transmission). Nevertheless, the present invention is also intended to encompass alternate embodiments in which drive systems (or similar systems) are in communication with motors and/or other controlled devices that have some intelligence, e.g., devices that have a central processing unit, microprocessor, programmable logic device or other logic devices/components. In such embodiments, the communication between the drive systems and the controlled devices need not be limited to power signals, but also could include various other analog or digital communications signals, including possibly both high power and low power signals. In at least some such embodiments, it is possible on an external device such as one of the terminals 24, 26 to communicate with a motor (or other controlled device) directly or indirectly via the drive system, so as to configure, send commands to, receive data from, and/or otherwise communicate with the motor (or other controlled device).
Additionally, since drive systems in such embodiments are capable of communicating with motors and/or other controlled devices in various manners not limited merely to controlling the currents/voltages/power applied to the motors/controlled devices, the drive systems are capable of receiving, storing and/or processing the information received from the motors/controlled devices and also providing that information on to terminals such as the terminals 24, 26. Indeed, while conventional drive systems often operate “open loop” in relation to the motors or other devices being controlled, such that little if any feedback is received by the drive systems from the controlled devices, the present invention is intended to encompass “closed loop” arrangements in which the drive systems receive a variety of types of feedback from the motors, controlled devices or associated devices. Such feedback could range from minimal feedback, such as that provided by a tachometer associated with a motor, to a range of other signals that could potentially provide a variety of information to the drive system relating to performance, faults, configuration, and other characteristics of the motor or other controlled device.
It is specifically intended that the present invention not be limited to the embodiments and illustrations contained herein, but include modified forms of those embodiments including portions of the embodiments and combinations of elements of different embodiments as come within the scope of the following claims.
This application is a divisional of U.S. patent application Ser. No. 11/329,625, filed on Jan. 11, 2006, which is a non-provisional application of U.S. Provisional Application No. 60/709,654, filed on Aug. 19, 2005, the full disclosures of which are each incorporated herein by reference.
| Number | Name | Date | Kind |
|---|---|---|---|
| 5142824 | Le Compagnon et al. | Sep 1992 | A |
| 6164900 | Labell et al. | Dec 2000 | A |
| 6587884 | Papadopoulos et al. | Jul 2003 | B1 |
| 6640140 | Lindner et al. | Oct 2003 | B1 |
| 6757568 | Birzer et al. | Jun 2004 | B2 |
| 6801920 | Wischinski | Oct 2004 | B1 |
| 6819960 | McKelvey | Nov 2004 | B1 |
| 6915330 | Hardy et al. | Jul 2005 | B2 |
| 7103642 | Chen | Sep 2006 | B1 |
| 7134118 | McNutt | Nov 2006 | B1 |
| 7233830 | Callaghan | Jun 2007 | B1 |
| 7299099 | Divelbiss et al. | Nov 2007 | B1 |
| 7440809 | Lehman | Oct 2008 | B2 |
| 7530113 | Braun | May 2009 | B2 |
| 20020082720 | Birzer et al. | Jun 2002 | A1 |
| 20020083847 | Schmitz et al. | Jul 2002 | A1 |
| 20020129565 | Silberman et al. | Sep 2002 | A1 |
| 20020156837 | Batke et al. | Oct 2002 | A1 |
| 20030051074 | Edwards | Mar 2003 | A1 |
| 20030067419 | Lambert | Apr 2003 | A1 |
| 20030084112 | Curray et al. | May 2003 | A1 |
| 20030109951 | Hsiung | Jun 2003 | A1 |
| 20040007404 | Schmitz et al. | Jan 2004 | A1 |
| 20040267395 | Discenzo et al. | Dec 2004 | A1 |
| 20050021676 | Chambers | Jan 2005 | A1 |
| 20050065913 | Lillie et al. | Mar 2005 | A1 |
| 20060015195 | Lehman et al. | Jan 2006 | A1 |
| 20060224250 | Callaghan | Oct 2006 | A1 |
| 20070043457 | Davis | Feb 2007 | A1 |
| 20090119437 | Hilscher | May 2009 | A1 |
| Entry |
|---|
| Ethernet Adapter Module, ACS 5000, ABB Switzerland Ltd., pp. 1-16, See p. 14; 2005. |
| PF7000 GEN-32 Medium voltage Support Technical Services Update Modem Configuration on the PF7000 Drive, Issued by Rob Bickford, Apr. 2, 2003. |
| PowerFlex EtherNet/IP Adapter 20-COMM-E product information web page on archive.org dated Jun. 13, 2004, by Rockwell Automation. |
| Number | Date | Country | |
|---|---|---|---|
| 20140091737 A1 | Apr 2014 | US |
| Number | Date | Country | |
|---|---|---|---|
| 60709654 | Aug 2005 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 11329625 | Jan 2006 | US |
| Child | 14043106 | US |
