ExecuteDiagService

The OTX ExecuteDiagService activity is used for communication with the controller. The activity prompted the diagnosis run time system to ship at the time of execution of a diagnostic service (Request) to one or more control devices. The execution of the activity waits until the response (response) from the control unit arrives or a timeout occurs. It may request parameters (RequestParams) set and response parameters (responses) are evaluated.

Reading and writing parameters can be done in two different ways, depending on whether the parameters are known at design time or not:

• Inli­ne-Map­ping

  If the parameters are known at design time, the request and response parameters on the properties of the ExecuteDiagService activity set or be bound to variables.

  The in-line mapping can not be used if more than one response from one or more control units are expected. If so, can only be accessed on the first response.

• Dyna­mic-Respon­se

  If the parameters are unknown at design time, such as the Auslesen of FehlerspeichersThe request and response parameters of the corresponding terms can dynamically ("by hand") can be configured at run time.

  A "manual" evaluation of the parameters may also be necessary if more than one answer is expected from the control unit, as in cyclical responses or functional addressing.

The activity supports two different Abarbeitungsmodi, see Property ExecuteAsync.

• Syn­chron

  means that the activity will be continued only if the response has been received by the control unit and processed.

• Asyn­chron

  means that the process continues immediately after sending the request. Do not wait for a response. Response parameters are not set in this case. Once a response is received from the control unit will trigger an event, can react accordingly on what to see DiagServiceEventSource.