OpenTestSystem.Otx.Extensions.Measure.Actions.ExecuteDeviceService Class Reference

Execute a service provided by a measurement device More...

Inheritance diagram for OpenTestSystem.Otx.Extensions.Measure.Actions.ExecuteDeviceService:

Classes
class	DeviceServiceArguments
	Contains a list of in- and output arguments for the to-be-executed device service's parameters. More...

Public Attributes
DeviceServiceArguments	arguments
	Maps the parameters to variables or expressions. More...
OtxLink	device
	This attribute identifies the measurement device to execute the service on. The link shall point to the corresponding DeviceSignature for that device. More...
System.Boolean	executeAsync
	A window (screen) can be modal or modeless opened. "Modal" means that the execution of the sequence will only continue after the closing of the window. "Modeless" means that the process will continue after the opening of the window. The window can be closed via the close-screen activity. More...
OtxName	service
	Identifies the service which shall be executed. The service nameshall be defined within the corresponding service declaration within the DeviceSignature. More...
System.Boolean	suppressInvalidMeasurementException
	Two or more of the implementing procedures are valid. The AmbiguousCallException was thrown because throwExceptionOnAmbiguousCall="true". More...
Public Attributes inherited from OpenTestSystem.Otx.Core.Actions.ActionRealisation
OtxLink	validFor
	Cardinality [0..1] Validity of ActionRealisation. More...

Detailed Description

Execute a service provided by a measurement device

The ExecuteDeviceService action executes a service provided by a measurement device. The action connects to physical devices from where it retrieves measurements.

Checker rules

Core.CheckerRule.Core_Chk053 - no dangling OtxLink associations
CheckerRule.Measure_Chk001 - correct target for ExecuteDeviceService and DeviceEventSource
CheckerRule.Measure_Chk002 - executed device service is declarated in device signature
CheckerRule.Measure_Chk003 - correct ExecuteDeviceService arguments
CheckerRule.Measure_Chk004 - ExecuteDeviceService input argument omission
CheckerRule.Measure_Chk005 - No Path in ExecuteDeviceService ouput arguments

Syntax

Measure.ExecuteDeviceService(OtxLink device, OtxName service, {DeviceServiceArguments[ ] arguments}, Boolean suppressInvalidMeasurementException, Boolean executeAsync);

Examples

// Signatures
package Measure.DeviceSignature DeviceSignature1
{
    Measure.DeviceServiceSignature DeviceServiceSignature1(in Integer DeviceServiceInParameter1, out String DeviceServiceOutParameter1);
}
 
// Global Declarations
 
public procedure main()
{
    // Local Declarations
 
    // Flow
    Measure.ExecuteDeviceService(DeviceSignature1, DeviceServiceSignature1, { DeviceServiceInParameter1 = 4, DeviceServiceOutParameter1}, false, false);
}

Member Data Documentation

arguments

DeviceServiceArguments OpenTestSystem.Otx.Extensions.Measure.Actions.ExecuteDeviceService.arguments

Maps the parameters to variables or expressions.

device

OtxLink OpenTestSystem.Otx.Extensions.Measure.Actions.ExecuteDeviceService.device

This attribute identifies the measurement device to execute the service on. The link shall point to the corresponding DeviceSignature for that device.

executeAsync

System.Boolean OpenTestSystem.Otx.Extensions.Measure.Actions.ExecuteDeviceService.executeAsync

A window (screen) can be modal or modeless opened. "Modal" means that the execution of the sequence will only continue after the closing of the window. "Modeless" means that the process will continue after the opening of the window. The window can be closed via the close-screen activity.

service

OtxName OpenTestSystem.Otx.Extensions.Measure.Actions.ExecuteDeviceService.service

Identifies the service which shall be executed. The service nameshall be defined within the corresponding service declaration within the DeviceSignature.

suppressInvalidMeasurementException

System.Boolean OpenTestSystem.Otx.Extensions.Measure.Actions.ExecuteDeviceService.suppressInvalidMeasurementException

Two or more of the implementing procedures are valid. The AmbiguousCallException was thrown because throwExceptionOnAmbiguousCall="true".