The ProgramManagerType provides the FunctionalUnit’s program manager. It is formally defined in Table 56.
Table 56 – ProgramManagerType Definition
Attribute |
Value |
||||
BrowseName |
ProgramManagerType |
||||
IsAbstract |
False |
||||
References |
Node Class |
BrowseName |
DataType |
TypeDefinition |
Other |
Subtype of the TopologyElementType Type defined in OPC 10000-100 |
|||||
0:HasComponent |
Object |
ActiveProgram |
|
ActiveProgramType |
M |
0:HasComponent |
Object |
ProgramTemplateSet |
|
ProgramTemplateSetType |
M |
0:HasComponent |
Object |
ResultSet |
|
ResultSetType |
M |
0:HasComponent |
Method |
Download |
|
|
O |
0:HasComponent |
Method |
Remove |
|
|
O |
0:HasComponent |
Method |
Upload |
|
|
O |
Conformance Units |
|||||
LADS ProgramManagerType |
|||||
|
ActiveProgram represents the ongoing operational state of a FunctionalUnit on a Device, providing user-friendly, sequential insight into the progress and context of the currently running program.
ProgramTemplateSet holds the template set associated with the ProgramManager.
ResultSet contains the results of program runs. It includes information about where and by whom the run was initiated, the template used along with any additional parameters, the samples included, contextual information to link the results with the associated samples, and where the results are provided.
Note: The Properties argument of the ProgramTemplateManager’s Upload and Download Method is intended to provide vendor-specific information and/or to extend the opaque ByteString with transparent metadata. This enables legacy devices to continue using proprietary program formats while also being able to transport transparent metadata for the LADS server itself or possible device drivers.
Note: Results must be created between the start (calling Start/StartProgram method or a manual start) and the end of a Program. So, the result must be complete before the ActiveProgram state machine transitions to the Complete state.