35 DiagnosticsType ToC Previous Next

A Client can start and stop diagnostics via methods. The single diagnosis steps are vendor specific. After each completed step, the server may generate a DiagnosisStepEndEvent (Table 163).

The event keeps the result of the diagnosis step. After completion of all diagnosis functions, the server shall send a DiagnosisEndEvent (Table 164).

Table 159 – DiagnosticsType Definition

Attribute Value        
BrowseName DiagnosticsType        
IsAbstract False        
References Node Class BrowseName DataType TypeDefinition Other
Subtype of 0:BaseObjectType defined in OPC UA Part 5          
0:HasProperty Variable Status DiagnosticsStatus Enumeration 0:PropertyType M, RO
0:HasComponent Method RunDiagnostics     M
0:HasComponent Method StopDiagnostics     M
0:GeneratesEvent ObjectType DiagnosisStepEndEventType Defined in 35.4    
0:GeneratesEvent ObjectType DiagnosisEndEventType Defined in 35.5    

35.1 Status ToC Previous Next

The status shows a client whether the diagnostic function is active or finished and if diagnosis detected at least one error.

Table 160 – DiagnosticsStatusEnumeration Definition

Name Value Description
OFF 0 Diagnostics inactive
ACTIVE_OK 1 Diagnostics active
ACTIVE_ERROR_DETECTED 2 Diagnostics active, at least one error detected
COMPLETE 3 Diagnostics completed successfully, result in variable “Result” available
COMPLETE_ERROR_DETECTED 4 Diagnostics completed detected some error

Previous Next