ince a network connection typically slows down the configuration process. The remote site configuration of the I/O devices 12 has significant advantages since the configuration can be performed by control software engineers at their own location and then electronically sent to the industrial site. The user can also do the configuration of the first I/O device 12 and of the other I/O devices on-line at the industrial site.
In step 96 in FIG. 3, the user connects the master computer 10 or 10′ to the network in order to send the created device objects to the proper devices that are on the network. In this way, the software on the network I/O devices are updated with the newly created device objects. The newly created I/O device objects then operate in accordance with the attributes and operations of the newly created device objects. Control ends with step 98.
FIG. 4 shows a GUI wherein the user uses a dialog window to select a new I/O device object from which other I/O device objects are to be cloned. The user highlights (as shown by reference 100) the I/O device object that is desired to be cloned. In the preferred embodiment, the GUI presents at reference numeral 102 the I/O devices in a hierarchical fashion, such as but not limited to, having at the top of the hierarchy the manufacturer's name followed by different device types. The hierarchical arrangement allows the user to more quickly locate desired I/O device objects.
FIG. 5 is a computer screen showing that a motor starter object has been selected and displays the attributes and values of the object as shown by reference numeral 110. The input and output characteristics of the object are shown by reference numeral 112.
FIG. 6 is a computer screen that is used to configure the attributes (i.e., parameters) for a first device object. Once the user has completed the configuration, the user saves the configuration. To add another device object to the configuration that is identical to the first I/O device object, the user selects the first I/O device object and executes an object copy command. This command gets the address for the new device from the user and configures all of the parameters automatically from the selected first device object as can be seen in FIG. 7.
The present invention also uses an object oriented model to automatically discover the target control platforms based Windows NT/2000 or WindowsCE systems and Input/Output devices. Further, in the case of Input/Output Devices, the object model once discovered, specifies and configures the devices. This model will be used to automatically clone the Input/Output devices and set their attributes and properties.
The present invention uses the Microsoft, Novell, and Vendor Specific protocols to automatically discover the target systems and devices. Once the target system is identified, the object model is used to set the attributes and properties of the control application running in the target system.
Referring now to FIG. 8, a screen capture of a GUI that identifies the Windows NT/2000 target systems is shown. In FIG. 9, a screen capture of a GUI for identifying the Windows CE based target systems is shown. Once the target systems are discovered, they can be selected and their attributes and properties can be changed. Some of the attributes are control application name, modified date, build date, and other similar or otherwise known attributes. This auto discovery is also useful for supporting remote operator/monitor screens.
Referring now to FIG. 10, a screen capture shows a GUI for auto discovery for I/O devices. Once the I/O devices have been auto-discovered, the object model enables to clone the devices. The present invention provides a very powerful mechanism to discover the target systems, I/O devices, and clone the devices where industrial automation systems, networks, and devices are configured off-line.
The present invention being thus described, it will be obvious that the same may be varied in many ways. Such variations are not to be regarded as a departure from the spirit and scope of the inventi