Classifications

• • G—PHYSICS
  • G06—COMPUTING OR CALCULATING; COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F9/00—Arrangements for program control, e.g. control units
  • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
  • G06F9/46—Multiprogramming arrangements
  • G06F9/48—Program initiating; Program switching, e.g. by interrupt
  • G06F9/4806—Task transfer initiation or dispatching
  • G06F9/4843—Task transfer initiation or dispatching by program, e.g. task dispatcher, supervisor, operating system
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L67/00—Network arrangements or protocols for supporting network services or applications
  • H04L67/01—Protocols
  • H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
  • H04L9/40—Network security protocols
• • G—PHYSICS
  • G06—COMPUTING OR CALCULATING; COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F2209/00—Indexing scheme relating to G06F9/00
  • G06F2209/48—Indexing scheme relating to G06F9/48
  • G06F2209/482—Application
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
  • H04L69/30—Definitions, standards or architectural aspects of layered protocol stacks
  • H04L69/32—Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
  • H04L69/322—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions
  • H04L69/329—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions in the application layer [OSI layer 7]

Definitions

• the present disclosure generally relates to process plants, and, more particularly, to launching applications from an originating application in a process plant.
• Process plants like those used in chemical, petroleum, manufacturing or other processes, typically include one or more process controllers communicatively coupled to one or more field devices via analog, digital or combined analog/digital buses.
• the field devices which may be, for example, valves, valve positioners, switches and transmitters (e.g., temperature, pressure and flow rate sensors), are located within the process environment and perform process functions such as opening or closing valves, measuring process parameters, etc.
• Smart field devices such as the field devices conforming to a well-known fieldbus protocol (e.g. the Foundation Fieldbus protocol, the HART protocol, etc.) may also perform control calculations, alarming functions, and other control functions commonly implemented within the controller.
• the process controllers which are also typically located within the plant environment, receive signals indicative of process measurements made by the field devices and/or other information pertaining to the field devices and execute a controller application that runs, for example, different control modules which make process control decisions, generate control signals based on the received information and coordinate with the control modules or blocks being performed in the field devices, such as HART and Foundation Fieldbus field devices.
• the control modules in the controller send the control signals over the communication lines to the field devices to thereby control the operation of the process.
• Information from the field devices and the controller is usually made available over a data highway to one or more other hardware devices, such as operator workstations, personal computers, data historians, report generators, centralized databases, etc., typically placed in control rooms or other locations away from the harsher plant environment.
• These hardware devices run applications that may, for example, enable an operator to perform functions with respect to the process, such as changing settings of the process control routine, modifying the operation of the control modules within the controller or the field devices, viewing the current state of the process, simulating the operation of the process for the purpose of training personnel or testing the process control software, keeping and updating a configuration database, etc.
• control systems such as the DeltaVTM control system sold by Emerson Process Management
• a control system may include multiple applications stored within and executed by different hardware devices located at diverse places within a process plant.
• a control system may include a configuration application that resides in one or more workstations.
• the configuration application may enable users to create or change process control modules and download these process control modules via a data highway to dedicated distributed controllers.
• the configuration application may also allow a designer to create or change user interfaces which are used by a viewing application to display data to a user and to enable a user to change settings, such as set points, within the process control routine.
• control system may include a configuration database application that may be executed, for example, by the same workstation(s) which execute the configuration application, or by a different hardware device coupled to the data highway.
• the configuration database application may store the current process control routine configuration and data associated therewith in a configuration database.
• control system may include a data historian application that may be executed by a data historian device. The data historian application controls the data historian device to collect and store some or all of the data provided across the data highway.
• a control system may include controller applications that may be stored and executed on a dedicated controller and, in some cases, field devices.
• a controller application may run control modules, which have been assigned and downloaded to the controller or field device, to implement actual process control.
• a control system may include viewing applications that may be executed on one or more operator workstations.
• a viewing application may receive data, for example, from a controller application via a data highway and display this data to process plant designers, operators, or users using user interfaces.
• the user interfaces may provide any of a number of different views, such as an operator's view, an engineer's view, a technician's view, etc.
• management systems such as the AMS predictive maintenance software sold by Emerson Process Management, may interact with one or more smart field devices to read the device, block, parameter, variable, or configuration information associated with those devices.
• a management system may reside on one or more operator workstations having appropriate communication ports which allow it to interconnect to, communicate with, and reconfigure a smart device.
• Management systems may be on-line, that is, have a hard-wired or any other permanent connection with a smart device. Management systems may also be portable and be capable of being periodically connected to a smart device to reconfigure or troubleshoot problems with that smart device.
• Management systems typically perform a wide variety of functions with respect to smart devices within a system.
• management systems may be used to provide users with information (e.g., values of variables or parameters) pertaining to the state of a process and to each of the smart field devices associated with or connected to the process.
• Management systems may also be used to enable a user to monitor a process and control the process by reconfiguring smart devices within the process as necessary.
• a management system may include one or more core applications as well as add-on applications provided, for example, by individual smart device manufacturers to implement changes on, and read data from, a particular smart device.
• a core application may, for example, include a graphical user interface that provides hierarchical views of devices in a plant or process.
• a core application may also, for example, provide a base functionality for interfacing with certain devices. For instance, a core application may permit a user to configure and/or read data from HART devices at a generic level.
• An add-on application may, for example, permit a user to configure and/or read data from devices that communicate via protocol other than that (those) supported by a core application.
• an add-on application may, for example, permit a user to configure and/or read data from devices at level beyond the generic level supported by a core application.
• management systems may utilize other applications such as word processing programs, spreadsheet programs, internet browsing programs, etc.
• a management system may utilize an internet browsing program to display on-line maintenance documents made available by a device manufacturer.
• a management system may launch a first application provided by a first smart device manufacturer to configure a first smart device. Also, the management system may launch a second application provided by a second smart device manufacturer to configure a second smart device. Similarly, a management system may launch a web browser to display a web page that provides information about a particular device.
• the examples described herein are generally related to launching desired applications via an originating application in a process plant. It may be desired for an originating application to be able to launch multiple desired applications, with one or more of the desired applications having a different application programming interface. In one example, the originating application is able to launch multiple desired applications via an application launcher program, subroutine, object, etc. The originating application provides the application launcher program, subroutine, object, etc. with an indication of the desired application to be launched, and the application launcher program, subroutine, object, etc. then launches the indicated desired application.
• a convenient user interface may be used to configure the process plant application to launch multiple desired applications via the application launcher program.
• a user may be prompted to indicate at least one desired application.
• the user may be prompted to specify a name of an executable file of a desired application, and may also be prompted to specify a location (e.g., a path) of the executable file.
• the user may be prompted to indicate a component in a process plant, with which the at least one desired application is to be associated.
• the user may be prompted to specify a device type with which the desired application is to be associated.
• the at least one desired application may be associated with the at least one component. For instance, an indication of the desired application may be stored in a file associated with a specified component of the process plant.
• FIG. 1 is a block diagram of an example process plant that may utilize techniques described herein for launching a desired application
• FIG. 2 is a block diagram of an example workstation that may be included in the example process plant of Fig. 1;
• FIG. 3 is a block diagram of an example process plant application that may utilize an application launcher program
• FIG. 4 is a flow diagram of an example method for launching a desired application via an application launcher program
• Fig. 5 is a block diagram illustrating an example technique for launching a desired application via an application launcher program
• FIG. 6 is a flow diagram of an example method for configuring a process plant application for launching a desired application via an application launcher program
• Fig. 7 is an example user interface for configuring a process plant application for launching a desired application via an application launcher program
• Fig. 8 is an example user interface for configuring a process plant application for launching a desired application via an application launcher program
• Fig. 9 is an example user interface for configuring a process plant application for launching a desired application via an application launcher program
• FIG. 10 is a flow diagram of an example method for configuring a management system application for launching a desired application via an application launcher program
• Fig. 11 is an example user interface for a management system application
• Fig. 12 is a flow diagram of an example method for launching a desired application via an application launcher program.
• FIG. 13 is a block diagram illustrating an example technique for launching a desired application via an application launcher program.
• Fig. 1 is a block diagram of an example process plant 10.
• the process plant 10 includes one or more nodes 12, 14, 16, 18 and 20.
• each of the nodes 12, 14 and 16 includes a process controller 12a, 14a, 16a connected to one or more field devices 22 and 23 via input/output (I/O) devices 24 which may be, for example, Foundation Fieldbus interfaces, HART interfaces, etc.
• I/O input/output
• the controllers 12a, 14a and 16a are also coupled to one or more host or operator workstations 18a and 20a in the nodes 18 and 20 via a data highway 30 which may be, for example, an Ethernet link.
• controller nodes 12, 14, 16 and the input/output and field devices 22, 23 and 24 associated therewith are typically located down within and distributed throughout the sometimes harsh plant environment, the operator workstation nodes 18 and 20 are usually located in control rooms or other less harsh environments easily assessable by controller personnel.
• a database 32 may be connected to the data highway 30 and operate as a data historian and/or a configuration database that stores the current configuration of the process plant 10 as downloaded to and/or stored within the nodes 12, 14, 16, 18 and 20.
• Each of the controllers 12a, 14a and 16a may store and execute a controller application that implements a control strategy using a number of different, independently executed, control modules or blocks.
• the control modules may each be made up of what are commonly referred to as function blocks wherein each function block is a part or a subroutine of an overall control routine and operates in conjunction with other function blocks (via communications called links) to implement process control loops within the process plant 10.
• function blocks typically perform one of an input function (such as that associated with a transmitter, a sensor or other process parameter measurement device), a control function (such as that associated with a control routine that performs PID, fuzzy logic, etc.
• control or an output function which controls the operation of some device (such as a valve, to perform some physical function within the process plant 10).
• some device such as a valve, to perform some physical function within the process plant 10
• control modules and function blocks designed and implemented in an object oriented programming protocol
• the control modules could be designed using any desired control programming scheme including, for example, sequential function block, ladder logic, etc. and are not limited to being designed using function block or any other particular programming technique.
• the configuration of the control modules as stored within the process control nodes 12, 14 and 16 is stored in the configuration database 32 which is accessible to applications executed by the workstations 18a and 20a.
• the field devices 22 and 23 coupled to the controllers 12a, 14a and 16a may be standard 4-20 ma devices, or may be smart field devices, such as HART, Profibus, or Foundation Fieldbus field devices, which include a processor and a memory. Some of these devices, such as Foundation Fieldbus field devices (labeled with reference number 23 in Fig. 1), may store and execute modules, or sub modules, such as function blocks, associated with the control strategy implemented in the controllers 12a, 14a and 16a.
• the field devices 22, 23 may be any types of devices, such as sensors, valves, transmitters, positioners, etc! and the I/O devices 24 may be any types of I/O devices conforming to any desired communication or controller protocol such as HART, Foundation Fieldbus, Profibus, etc.
• a management application may be stored on and executed by one or more of workstations 18a and 20a.
• Fig. 2 is a block diagram of example workstation 18a (workstation 20a may comprise a same or similar device).
• the workstation 18a may include at least one processor 50, a volatile memory 54, and a non-volatile memory 58.
• the volatile memory may include, for example, a random access memory (RAM).
• the non-volatile memory may include, for example, one or more of a hard disk, a read-only memory (ROM), a compact disk ROM (CD-ROM), a digital versatile disk (DND), a FLASH memory, etc.
• the workstation 18a may also include an input/output (I/O) device 62.
• I/O input/output
• the processor 50, volatile memory 54, non-volatile memory 58, and I/O device 62 may be interconnected via an address/data bus 66.
• the workstation 18a may also include at least one display 70 and at least one input device 74.
• the input device may include, for example, one or more of a keyboard, a keypad, a mouse, etc.
• the display 70 and the input device 74 are coupled with the I/O device
• I/O device 62 is illustrated in Fig. 2 as one device, it may comprise several devices.
• a management application may be stored, for example, in whole or in part, in the non- volatile memory 58 and executed, in whole or in part, by the processor 50.
• FIG. 3 is a block diagram of an example process plant application 100.
• Fig. 3 will be described in the context of a management system application. It is to be understood, however, that the process plant application 100 may be any of various types of application employed in a process plant (e.g., a control system application, a device or equipment management application, a simulation application, etc.).
• the process plant application 100 may include one or more core applications 104, and may also include one or more add-on applications 108 and/or one or more custom applications 112.
• a core application 104 may, for example, provide a base functionality for communicating with and configuring certain types of devices (e.g., HART devices, Fieldbus devices, etc.) and/or provide a graphical user interface for displaying devices in a process plant.
• an add-on application 108 may be, for example, an application, provided by a manufacturer of a device, that permits communication and configuration resources for a device for which the core application 104 does not provide such resources.
• an add-on application 108 may be, for example, an application, provided by a manufacturer of a device, that permits communication and configuration resources for a device beyond those provided by the core application 104.
• a custom application may be, for example, an application developed by an end user that provides a level of communication and configuration resources not provided by a core application 104 or an add-on application 108.
• the process plant application 100 may also utilize one or more general purpose applications 116, such as a word processing application, a spreadsheet application, a web browsing application, etc.
• the process plant application 100 may further include an application launcher program 120.
• An application such as core application 104, can launch applications, such as add-on applications 108, custom applications 112, and general purpose applications 116, via the application launcher program 120.
• core application 104 uses application launcher program 120 to launch other applications such as add-on applications 108, custom applications 112, and general purpose applications 116.
• the core application 104 need not use apphcation launcher 120 to launch every application.
• other applications besides core application 104 may utilize the application launcher program 120 or a separate application launcher program (not illustrated) similar to application launcher program 120.
• an add-on application 108 may launch a general purpose application 116 via a separate application launcher program (not illustrated).
• Each of the add-on applications 108, the custom applications 112, and the general purpose applications 116, potentially, may have a unique API.
• the core application 104 may launch multiple applications, having multiple APIs, via potentially only a single API.
• Fig. 4 is a flow diagram illustrating an example method 150 of launching an application via an application launcher program.
• Fig. 5 is a block diagram illustrating an example operation of an originating application 180 utilizing the application launcher program 120 to launch a desired application 184. Additional examples of methods for utilizing an application launcher program will be described below.
• an originating application 180 launches the application launcher program 120.
• the originating application 180 may be, for example, a core application of a process plant application.
• the originating application 180 may provide to the application launcher program 120 an indication of the particular desired application 184 to be launched.
• the originating program 180 may provide to the application launcher program 120 an indication of startup parameters which may be used to launch the desired application 184. It will be appreciated by one of ordinary skill in the art that the indication of the desired application 184 and the indication of startup parameters may be a single indicator or multiple indicators.
• the launching of the application launcher program 120 and the providing of the indicator or indicators of the desired application 184 and the startup parameters may be performed according to an API of the application launching program 120. It will be appreciated by those of ordinary skill in the art that the API of the application launching program 120 may be designed to match a portion of the API of the originating application 180 that corresponds to program launching.
• the application launching program 120 may utilize the indicator or indicators of the desired application 184 and the startup parameters to retrieve information 188 related to launching the desired application 184 according to the API of the desired application 184.
• the information 188 may include, for example, a file name of the desired application 184, a location of the desired application 184 (e.g., a path name), startup parameters to be provided to the desired application 184 in an order and syntax according to the API of the desired application 184 (e.g., a command line), etc.
• the information 188 may be stored, for example, in a file, database, etc., such that the application launching program 120 can use the indicator or indicators of the desired application 184 and the startup parameters to retrieve the information 188.
• the indicator(s) may include, for example, a file name in which the information 188 is stored, a location within a file, a database query for retrieving the information 188 from a database, a URL, an XML document, a HTTP GET, etc.
• the application launcher program 120 utilizes the information 188 to launch the desired application according to an API of the desired application 184. If startup parameters are provided, the desired application 184 may be considered to be launched "in-context.” For example, if the desired application 184 is a web browser, the web browser may be launched displaying a particular web page.
• FIG. 6 is a flow diagram illustrating an example method 200 for configuring a process plant application in which an originating application can launch a desired application via an application launcher program.
• a user may be prompted to provide a descriptive name for a desired application.
• the descriptive name may be used, for example, in providing a graphical user interface mechanism via which a user can initiate a launch of the desired application.
• the user may be prompted to provide a file name and a location of an executable file of the desired application.
• the user may be prompted to provide startup parameters for the desired application.
• the types of startup parameters that may be provided may be determined, in part, by the API of the desired application. Additionally, the user may specify, for example, an ordering, a syntax, etc., of the startup parameters that correspond to the desired application's API.
• the user may be prompted to specify one or more components in a process plant with which the desired application should be associated. For instance, in a control system application, the user may specify one or more of a controller, a module, a device, etc., used in a process. In a management system application, the user may specify, for example, a specific device, a device type, etc.
• the desired application and the startup parameters may be associated with the one or more components (which the user was prompted to specify at block 216).
• a text file may be created that includes the file name and path of the executable file and the startup parameters to be used in launching the desired application.
• the text file may be given a unique name that can be associated with the component(s) (which the user was prompted to specify at block 216).
• the process plant application may be configured to reflect the association between the desired application (which the user was prompted to specify at block 208) and the component(s) (which the user was prompted to specify at block 216).
• an originating application of the process plant application may be configured to provide a user interface mechanism for initiating a launch of the desired application.
• the user interface mechanism may be associated with the component(s).
• a menu associated with the component(s) may be configured to include an item having the descriptive name which the user was prompted to specify at block 204.
• the menu item may be associated with the text file that includes the file name and path of the executable file and the startup parameters to be used in launching the desired application.
• Figs. 7-9 are an example user interface that may be utilized to implement blocks 204, 208, 212, and 216 of Fig. 6 for a management system application.
• Fig. 7 is an example user interface 250 that may be used for prompting a user to provide a descriptive name (block 204 of Fig. 6), a filename of an executable file for the desired application (block 208 of Fig. 6), and a location of the executable file (block 212 of Fig. 6).
• a user may type in a descriptive name for the desired application in box 254.
• a user may type in a path and executable file name.
• a user may "browse" for the path and executable file name in a manner well known to those of ordinary skill in the art by selecting button 262.
• Fig. 8 is an example user interface 250 that may be used for prompting a user to provide startup parameters for the desired application (block 212 of Fig. 6).
• the user interface includes boxes 272a — 272m and 274a — 274m for specifying parameters. Parameters can be passed to the desired application in order (e.g., "Argument 1", then “Argument 2", then “Argument 3", etc.). In this way, the user may select the order in which to pass the parameter to correspond, for example, with an API of the desired application.
• a user may type in parameters in boxes 272a — 272m. Additionally, using boxes 274a — 274m, a user may pass "Arguments" to the desired application.
• An argument may correspond, for example, to a type of information corresponding to a device.
• arguments may include AMS Username (the AMS login name of a user), OPC Block Moniker (a device's Object Linking and Embedding (OLE) for Process Control (OPC) format block moniker), Plant Server Name (the name of the server for a connected device), Device Connection State (indicates whether a device is "live", i.e., "connected” or "not connected"), AMS Block Tag (a device icon label for a device that may be displayed to the user in, for example, the AMS device connection view or the AMS plant server view), Device Block Key (a number used for database device references, commonly required for structured query language (SQL) database accesses), Database Name (the domain name server (DNS) name of the database for a device), Manufacturer ID (a number that indicates a device's manufacturer), Device Type (a number that indicates a device type or
• the user interface 270 may include buttons 276a — 276m to permit a user to select an argument from, for example, a pull-down menu such as menu 278.
• buttons 276a — 276m to permit a user to select an argument from, for example, a pull-down menu such as menu 278.
• a person may specify an appropriate syntax for passing information to the desired application. For instance, using boxes 280b — 280m, 272a — 272m, and 282a — 282m, a user may add spaces, delimiters, and/or quotation marks and create a "command line" that includes the parameters in the appropriate syntax. Box 284 may provide the user with a view of the command line as it is being created so, for example, the user can verify that the correct syntax is being used.
• Fig. 9 is an example user interface 290 that may be used for prompting a user to specify one or more devices with which the desired application should be associated (block 216 of Fig. 6).
• the user interface 290 may include a list 292 of possible devices and/or device types.
• a user may select devices and/or device types to be associated with the desired application by selecting buttons 296a and 298a. For example, by selecting button 296a, the user may select all of the devices and/or device types in list 292. Additionally, the user may highlight one or more individual devices and/or device types in list 292, and then select those one or more devices and/or device types by selecting button 298a.
• the user interface 290 may also include a list 294 of devices and/or device types that have been selected to be associated with the desired application.
• the user may use button 296b to "deselect" all of the devices and/or device types in list 294. Additionally, the user may highlight one or more individual devices and/or device types in list 294, and the select button 298b to "deselect" those devices and/or device types.
• the user interfaces 250, 270, and 290 may permit a user to associate a desired application with a device type, the user, in effect, may be able to associate the desired application with, potentially, multiple devices. Thus, the user need not associate the desired application with each device, individually. In other examples, the user may be permitted to associate desired applications with individual devices.
• associating the desired application and startup parameters with the one or more devices may include storing an indication of the association in a file, such as a configuration file.
• a file such as a configuration file.
• the management system application is implemented with a WINDOWSTM operating system available from Microsoft Corporation (e.g., WINDOWS XPTM, WINDOWS 2000TM, WINDOWS NTTM, etc.)
• indication(s) of the association may be stored, for example, in an INI file and/or a Registry file.
• the information obtained via the user interface described with reference to Figs. 7-9 may be stored in an INI file.
• Fig. 10 is a flow diagram of an example method 320 for configuring the management system application (block 224 of Fig. 6).
• information that will enable the application launcher program to launch the desired program is formatted according to the standard API of the originating program.
• the information may be formatted according to an API that is not standard for the originating program.
• a standard API of the application program launcher could be employed.
• the desired application's executable file and path may be stored in a file. Additionally, parameters assembled into a command line via, for example, a user interface such as user interface 270 (Fig. 8) may also be stored in the file.
• an originating application of the management system application is configured to include one or more user interface mechanisms for initiating a launch of the desired application. For instance, if the user specified one or more device types via user interface 290 (Fig. 9), and the process or plant includes multiple devices of that type or types, multiple user interface mechanisms corresponding to the multiple devices may be included.
• Fig. 11 is a display from an example originating application.
• the originating application provides a hierarchical view of devices in a process and/or plant.
• the display 350 includes a hierarchy portion 354 and a contents portion 358.
• the hierarchy portion 354 provides a hierarchical view of an enterprise, process, and/or plant. Plants, areas within plants, plant components, etc., may be represented, in a hierarchical manner, as folders and subfolders.
• a folder in the hierarchy portion 354 with, for example, a mouse, a user can view the contents of that folder in the contents portion 358.
• the folder "Boiler 1" has been selected in the hierarchy portion 354.
• the folder "Boiler 1 " includes six devices as can be seen in the contents portion 358.
• a user has specified, via user interfaces 250, 270, and 290 (Figs. 7-9) that a desired application with the descriptive name "Naive
• Documentation is to be associated with various device types including device type "DNC5000.”
• the device “FC-4000,” which is of the type "DNC5000” has been selected.
• the originating application has been configured to include a menu item 366 in a menu associated with devices of the type "DNC5000.”
• the menu 362 can be displayed, for example, by selecting device “FC-4000” with an activation of a left mouse button, and then activating a right mouse button.
• the originating application may be configured to provide one or more user interface mechanisms, such as a menu item, by modifying a configuration file, such as an INI file associated with the origination application, or a "registry" file.
• the originating application may be configured to launch the application launcher program upon activation of the user interface mechanism (block 328). Additionally, the originating application may be configured to launch the application launcher program with the information formatted at block 324. Continuing with the example described with reference to block 324, the originating application may be configured, when launching the application launcher program, to indicate to the application launcher program the name and location of the file created at block 324. As is well known to those of ordinary skill in the art, for applications designed for a WINDOWSTM type operating system, the originating application may be so configured by modifying a configuration file, such as an INI file associated with the origination application, or a "registry" file.
• a configuration file such as an INI file associated with the origination application, or a "registry" file.
• Fig. 12 is a flow diagram illustrating an example method 400 in a process plant application for launching a desired application. The flow of Fig. 12 will be described with reference to Figs. 11 and 13.
• a user may activate a user interface mechanism in an originating application.
• the user may, for example, select a menu item such as menu item 366.
• the originating application may determine that an application launcher program should be launched. For example, if a menu item is selected by a user, the originating application may determine, based on the selected menu item, that the application launcher program should be launched.
• the originating application 450 may examine a first file, registry, etc., or portion of a file, registry, etc., (first file 454) associated with the menu item selected at block 404.
• the first file 454 may provide the executable file name and path of the application launcher program, thus indicating that the application launcher program should be launched.
• the originating application may determine, based on the user interface mechanism activated at block 404, an indicator or indicators of a desired application to be launched and of startup parameters for the desired application. For example, if a menu item is selected by a user, the originating application may determine, based on the selected menu item, an indicator or indicators of a desired application to be launched and of startup parameters for the desired application. In one particular example, the originating application may examine a configuration file or a portion of a configuration file, a registry file, etc., associated with the menu item. This configuration file, registry file, etc., may include a file name and path of another file. This other file may include information regarding the desired application, as well as startup parameters for the desired application.
• the originating application 450 may examine the first file 454 associated with the menu item selected at block 404.
• the first file 454 may provide a file name and path of a second file 458.
• the second file may include the executable file name and path of the desired application to be launched.
• the second file may include startup parameters for the desired application in a format according to the API of the desired application.
• the startup parameters may be in a format assembled using the user interface 270 of Fig. 8.
• the originating application may launch the application launcher program according to the standard API of the originating application (or a non-standard API). Additionally, the originating application may provide, via the API of the application launcher program, the indicator(s) of the desired application to be launched and its startup parameters. In the example of Fig. 13, the originating application 450 may launch the application launcher program 462, and provide it the name and path of the second file 458.
• the application launcher program may determine the desired application to be launched, based on the indicator(s) provided at block 416.
• the application launcher program 462 may determine the desired application 466 by examining the second file 458.
• the application launcher program may determine the startup parameters for launching the desired application, based the indicator(s) provided at block 416. In the example of Fig. 13, the application launcher program 462 may determine the startup parameters by examining the second file 458.
• the application launcher program may launch the desired application according to the API of the desired application. Additionally, the application launcher program may provide startup parameters to the desired application, according to the API of the desired application. In the example of Fig.
• the application launcher program 462 may launch the desired application specified in the second file 458. Additionally, the application launcher program 462 may provide to the desired application the startup parameters provided in the second file 458.
• the startup parameters may be formatted in the second file 458 according to the API of the desired application. For instance, a user may use a user interface such as user interface 270 of Fig. 8 to assemble a "command line" that is formatted according to the API of the desired application.
• startup parameters include arguments (e.g., Device ID, Device
• the application launcher program may determine the value of those arguments, and then, for example, may include those values in the command line.
• the originating application (or some other application) may pass the values of a set of arguments (e.g., all arguments, all arguments that could possibly be used by the application launcher program, all arguments that it has been determined that the application launcher program will need, etc.) to the application launcher program upon startup.
• the originating application (or some other application) may store the values of the set of arguments in a file. Then, when the application launcher needs values of particular arguments for launching a desired application, the application launcher program may determine those values by retrieving the needed values from the set of values passed to the application launcher program, or stored in the file.
• the application launcher program may provide the values of those arguments to the desired application via the API of the desired application.
• an application launcher program may be implemented as a separate program from the originating application, or as a subroutine, object, etc., of the originating application.
• the methods described above may be implemented as software programs for execution by one or more processors. Such programs may be embodied in software stored on a tangible medium such as CD-ROM, a floppy disk, a hard drive, a digital versatile disk (DND), or a memory associated with the processor, but persons of ordinary skill in the art will readily appreciate that the entire program or parts thereof could alternatively be executed by a device other than a processor, and/or embodied in firmware and/or dedicated hardware in a well known manner.
• a tangible medium such as CD-ROM, a floppy disk, a hard drive, a digital versatile disk (DND), or a memory associated with the processor

Landscapes

• Engineering & Computer Science (AREA)
• Theoretical Computer Science (AREA)
• Software Systems (AREA)
• Computer Networks & Wireless Communication (AREA)
• Signal Processing (AREA)
• General Engineering & Computer Science (AREA)
• Physics & Mathematics (AREA)
• General Physics & Mathematics (AREA)
• Computer Security & Cryptography (AREA)
• Health & Medical Sciences (AREA)
• Computing Systems (AREA)
• General Health & Medical Sciences (AREA)
• Medical Informatics (AREA)
• Stored Programmes (AREA)

Priority Applications (4)

Applications Claiming Priority (2)

Publications (2)

Family

ID=32468818

Family Applications (1)

Country Status (6)

Cited By (19)

Families Citing this family (94)

Family Cites Families (121)

• 2002
  • 2002-12-10 US US10/315,857 patent/US7600234B2/en active Active
• 2003
  • 2003-12-08 AU AU2003294598A patent/AU2003294598A1/en not_active Abandoned
  • 2003-12-08 DE DE10393871T patent/DE10393871T5/de active Pending
  • 2003-12-08 JP JP2004559464A patent/JP2006516057A/ja active Pending
  • 2003-12-08 WO PCT/US2003/039041 patent/WO2004053601A2/en not_active Ceased
  • 2003-12-08 CN CN2003801056288A patent/CN1764877B/zh not_active Expired - Lifetime

Also Published As

Similar Documents

Legal Events