Difference between revisions of "Programs"
(Created page with "==Introduction== {{uacap:Programs Intro}} == Program Capabilities == __NOEDITSECTION__ {{uaCollapsible|Programs|{{uacap:Programs Base}}|}}") |
(→Introduction) |
||
| (3 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
==Introduction== | ==Introduction== | ||
| − | + | OPC UA Programs represent long-running, often complex and stateful functions in a server or underlying system. | |
| + | When comparing Methods and Programs: a Method, for example, may be used to perform a calculation or reset a counter. A Program example would be to run and control a batch process, execute a machine tool part program, or manage a domain download. Programs can represent any level of functionality within a system or process in which client control or intervention is required and progress monitoring is desired. The execution time of a Program is not bound to the lifetime of a session. | ||
| + | <br>Note – the Programs Information Model is specified in [http://www.opcfoundation.org/UA/Part10/ OPC UA Part 10]. | ||
| − | == Program Capabilities == | + | ==Program Capabilities== |
| − | + | ===Program Execution Model=== | |
| − | {{ | + | {{CapabilityUri|/Programs#Program_Execution_Model}} |
| + | '''Description''' | ||
| + | <br>Understand and support the Programs Information Model. This includes all Methods to invoke or control Program execution and the handling of transition events. | ||
| + | |||
| + | '''Usage Considerations''' | ||
| + | <br>Consistent monitoring and control of long-running activities. | ||
| + | |||
| + | {{uaConformance| | ||
| + | * Manage Programs using the ProgramType Methods | ||
| + | * Monitor the execution state by subscribing for program transition events | ||
| + | * Evaluate the result data after execution ended. | ||
| + | | | ||
| + | [http://opcfoundation.org/UA-Profile/Server/ProgramBasic '''Server Profile for Programs'''] | ||
| + | }} | ||
Latest revision as of 12:16, 4 May 2015
Introduction
OPC UA Programs represent long-running, often complex and stateful functions in a server or underlying system.
When comparing Methods and Programs: a Method, for example, may be used to perform a calculation or reset a counter. A Program example would be to run and control a batch process, execute a machine tool part program, or manage a domain download. Programs can represent any level of functionality within a system or process in which client control or intervention is required and progress monitoring is desired. The execution time of a Program is not bound to the lifetime of a session.
Note – the Programs Information Model is specified in OPC UA Part 10.
Program Capabilities
Program Execution Model
URN: https://opcfoundation.org/wiki/index.php/Programs#Program_Execution_Model
Description
Understand and support the Programs Information Model. This includes all Methods to invoke or control Program execution and the handling of transition events.
Usage Considerations
Consistent monitoring and control of long-running activities.
Conformance Testing
| Client | Server |
|
