In response to a Stop method call on the server, the vision system is expected to end running operation and transition to state Ready as soon as possible while retaining as much result data as possible.
See the general remarks on Stop and Abort in 8.3.2.4 for further information on the behavior.
Signature
Stop ([in]Int32cause[in]StringcauseDescription[out]Int32error);
Table 105 – Stop Method Arguments
|
Argument |
Description |
|
cause |
Implementation-specific number denoting the reason for the Stop command. |
|
causeDescription |
Text for said reason, e.g. for logging purposes. May be empty. |
|
error |
0 – OK Values > 0 are reserved for errors defined by this and future standards. Values < 0 shall be used for application-specific errors. |
Table 106 – Stop Method AddressSpace Definition
|
Attribute |
Value |
||||
|
BrowseName |
Stop |
||||
|
References |
NodeClass |
BrowseName |
DataType |
TypeDefinition |
ModellingRule |
|
HasProperty |
Variable |
InputArguments |
Argument[] |
PropertyType |
Mandatory |
|
HasProperty |
Variable |
OutputArguments |
Argument[] |
PropertyType |
Mandatory |
The cause argument given to the method can only be interpreted by the underlying vision system It can be used, for example, for logging purposes. It is expected that a value of 0 will be considered an “unspecified reason”.