Method and apparatus for configuring interfaces for automated systems

• US 20060020429A1
• Filed: 06/03/2005
• Published: 01/26/2006
• Est. Priority Date: 09/30/1999
• Status: Abandoned Application

• Current Assignee: Rockwell Automation Technologies Incorporated (Allen-Bradley Co., Inc.)
• Original Assignee: Rockwell Automation Technologies Incorporated (Allen-Bradley Co., Inc.)
• Inventors: McRitchie, Keith, Obitko, Marek, Brooks, Ruven, Grooms, David
• Application Number:
  US11/145,095
• Publication Number:
  US 20060020429A1
• Time in Patent Office: Days
• US Class Current: 702/189
• CPC Class Codes: G06F 30/30 Circuit design

Abstract

An apparatus and method for configuring an interface for use with an automated system including at least a first controller that runs a first system program to control and monitor automated system components, a first project file associated with the first system program and describing at least a subset of the system components and system operation, the method comprising the steps of providing an interface template that specifies interface components and arrangement of the interface components relative to each other for presentation on a display screen, gleaning information from the first project file regarding input and output parameters to be supported by an interface and instantiating an instance of an interface using the interface template and the information gleaned from the first project file.

Claims

1. A method for configuring an interface for use with an automated system including at least a first controller that runs a first system program to control and monitor automated system components, a first project file associated with the first system program and describing at least a subset of the system components and system operation, the method comprising the steps of:

providing an interface template that specifies interface components and arrangement of the interface components relative to each other for presentation on a display screen;

gleaning information from the first project file regarding input and output parameters to be supported by an interface; and

instantiating an instance of an interface using the interface template and the information gleaned from the first project file.

2. The method of claim 1 wherein the step of providing an interface template includes specifying at least a first subset of interface inputs to be provided irrespective of the contents of the first project file, the step of instantiating an interface instance including linking each of the interface inputs in the subset to a separate selectable input component.

3. The method of claim 2 wherein the step of providing an interface template includes specifying a separate screen selectable icon for each of the first sub-set of interface components, the step of instantiating including providing an interface instance including the separate screen selectable icons as the selectable input components and linking the interface inputs to the input components.

4. The method of claim 3 wherein the step of providing an interface template includes specifying a separate label for each of the separate screen selectable icons, the step of instantiating further including scripting the labels to associated screen selectable icons.

5. The method of claim 2 wherein the step of providing an interface template includes providing software code for presenting at least first and second different view types of automated system components and specifying a separate interface input for each of the first and second different view types.

6. The method of claim 2 wherein the step of providing an interface template includes providing software code for controlling automated system operation and specifying a separate interface input for each of a plurality of different control functions.

7. The method of claim 2 wherein the step of providing an interface template includes providing software code for receiving operating parameter output values from the automated system and presenting different diagnostic message types related to operating parameter values and specifying a separate interface input for each of a plurality of different diagnostic view types.

8. The method of claim 1 wherein the project file specifies a plurality of distinct automated system control assemblies wherein the step of providing an interface template includes providing a template that specifies a subset of input components that may be associated with control assemblies, the step of gleaning including identifying control assemblies specified by the project file, the step of instantiating including associating a separate one of the control assembly input components with each gleaned project file control assembly.

9. The method of claim 8 wherein the project file includes control assembly labels and system addresses, the step of gleaning including identifying control assembly labels and associated addresses, the step of instantiating includes scripting each control assembly label to a separate one of the control assembly input components and associating the control assembly input components with corresponding system addresses.

10. The method of claim 8 wherein the first system program monitors at least a sub-set of system operating parameters and generates output values associated therewith, the step of providing an interface template including providing a template having at least a first template section that is associated with a reusable software component that actively reports output values associated with at least a subset of the operating parameters, the operating parameters displayed by the interface instance at any given time being a function of which control assembly input component is selected.

11. The method of claim 1 wherein the first system program monitors at least a sub-set of system operating parameters and generates output values associated therewith, the step of providing an interface template including providing a template having at least a first template section that is associated with a reusable software component that actively reports output values associated with at least a subset of the operating parameters.

12. The method of claim 11 wherein the reusable software components are one of Active-X components and Java Beans components.

13. The method of claim 1 wherein the project file specifies a plurality of distinct automated system control assemblies and the first system program monitors at least a sub-set of system operating parameters and generates output values associated therewith, the step of providing an interface template including providing software code for presenting at least first and second different view types of automated system components and specifying a separate view type input for each of the first and second different view types, providing software code for controlling automated system operation and specifying a separate control input for each of a plurality of different control functions, providing software code that specifies a subset of input components that may be associated with control assemblies and specifying at least a first template section that is associated with a reusable software component that actively reports output values associated with at least a subset of the operating parameters, the step of gleaning including identifying control assemblies specified by the project file and the step of instantiating including associating a separate one of the control assembly input components with each gleaned project file control assembly, wherein the operating parameters displayed by the interface instance at any given time are a function of which control assembly input is selected, which view type input is selected and which control input is selected.

14. The method of claim 13 wherein the step of providing an interface template further includes providing software code for receiving operating parameter output values from the automated system and presenting different diagnostic message types related to operating parameter values and specifying a separate interface input for each of a plurality of different diagnostic view types, wherein the diagnostic information presented at any given time are a function of which control assembly input is selected, which view type input is selected, which control input is selected and which diagnostic view type is selected.

15. The method of claim 1 wherein the at least a first controller also runs a second system program to control and monitor automated system components where a second project file is associated with the second system program, the method further including the steps of gleaning information from the second project file regarding input and output parameters to be supported by a second interface and instantiating a second interface instance using the interface template and the information gleaned from the second project file.

16. A method for configuring interfaces for use with an automated system including at least a first controller that runs system programs to control and monitor automated system components, a plurality of project files associated with the system programs and describing at least a subset of the system components and system operation, the method comprising the steps of:

providing an interface template that specifies interface components and arrangement of the interface components relative to each other for presentation on a display screen;

for each of the project files;

gleaning information from the project file regarding input and output parameters to be supported by an interface; and

instantiating an instance of an interface using the interface template and the information gleaned from the project file such that a plurality of similar yet project file specific interface instances are instantiated.

17. A method for configuring an interface template for use in specifying at least one interface for use with an automated system including a controller that runs a system program to control and monitor automated system components, the method comprising the steps of:

providing a library of possible interface components;

providing a template specifying interface;

using the template specifying interface to select interface components from the library and to spatially arrange the selected components with respect to each other to form an interface template; and

storing the interface template for subsequent use in configuring interfaces.

18. The method of claim 17 wherein the step of providing a library of possible interface components includes providing at least some dynamic components that include program code for monitoring automated system operating parameters and presenting dynamic information related thereto.

19. The method of claim 18 wherein the dynamic components are one of Active-X components and Java Beam components.

20. The method of claim 17 wherein automated system information can be arranged according to several different view types and wherein the step of providing a library of possible interface components includes providing at least some components that include program code for altering view type.

21. The method of claim 17 wherein automated system information can be arranged according to several different view types and wherein the step of providing a library of possible interface components includes providing at least some components that include program code for altering view type.

22. The method of claim 17 also for configuring instances of interfaces for use with the automated system wherein the system includes at least a first controller that runs a system program to control and monitor automated system components, a project file associated with the first system program and describing at least a subset of the system components and system operation, the method further including the steps of, gleaning information from the project file regarding input and output parameters to be supported by an interface and instantiating an instance of an interface using the interface template and the information gleaned from the project file.

23. The method of claim 17 wherein the step of providing a library includes providing code segments associated with specific functions, the method further including the step of, prior to storing, using the template specifying interface to associate functions with specific selected components.

24. An apparatus for configuring an interface for use with an automated system including at least a first controller that runs a first system program to control and monitor automated system components, a first project file associated with the first system program and describing at least a subset of the system components and system operation, the apparatus comprising:

a database including at least a first interface template that specifies interface components and arrangement of the interface components relative to each other for presentation on a display screen;

a processor linked to the database and programmed to perform the steps of;

gleaning information from the first project file regarding input and output parameters to be supported by an interface; and

instantiating an instance of an interface using the interface template and the information gleaned from the first project file.

25. An apparatus for configuring an interface template for use in specifying at least one interface for use with an automated system including a controller that runs a system program to control and monitor automated system components, the apparatus comprising:

a database including a library of possible interface components;

an interface for selecting interface components from the library and spatially arranging the selected components with respect to each other to specify interface template information;

a processor programmed to perform the steps of;

receiving the interface template specifying information;

instantiating an instance of the interface template; and

storing the interface template specifying information for subsequent use in configuring interfaces.

26. A method for providing an interface screen including reusable software components that require information from a project file to be instantiated, the method comprising the steps of:

identifying information required b the reusable software components for instantiation;

storing the required information in a database;

when a screen is accessed that includes the reusable software component, accessing the database to obtain the information needed for instantiation; and

instantiating the reusable software component.

27. The method of claim 26 wherein the reusable software components are one of Active-X controls and Java Bean controls.

28. A method for programming an HMI display device that includes HMI objects, the method comprising the steps of:

providing an HMI scripting language that includes event based constructs that are associable with HMI objects;

using the HMI scripting language to script at least a portion of an HMI program that associates at least a subset of HMI objects with event based constructs; and

using the HMI program to drive an HMI.

29. The method of claim 28 wherein the step of providing an HMI scripting language that includes event based constructs that are associable with HMI objects includes providing a language that at least one of includes tag change event constructs that cause interface activity as a consequence of a user interacting with an interface object and page change events that cause interface activity as a consequence of a user moving to a different HMI screen.