Versions Compared

Old Version 4

changes.mady.by.user Sylvain Ménard

Saved on

compared with

New Version Current

changes.mady.by.user Sylvain Ménard

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Table of Contents
maxLevel3

Library

rtlab/Communication/Asynchronous

Block

The OpAsyncGenCtrl block allows a user to configure the setting of the asynchronous executable.

...

Mask

...

Description

The OpGenAsyncCtrl block is used to define the setting of the asynchronous executable created by the user. All asynchronous Send and Receive block using the same Controller ID refer to this block. This controller allows some generic field to transmit parameters to the executable launched by the Controller. Refer to the section RT-LAB Asynchronous process of chapter RT-LAB Connectivity of the User Guide for more details.

Parameters

Controller ID

Specifies the controller ID that will be associated with each OpAsyncSend and OpAsyncRecv blocks.

Parameter page

Display

Displays the Float/String parameters page by page.

Float parameter 1 .. 12

Any value entered in this field is available in the asynchronous application by calling the OpalGetAsyncCtrlParameters function. These twelve values are placed in the FloatParam array in the Opal_GenAsyncParam_Ctrl structure.

EX:
Opal_GenAsyncParam_Ctrl Param;
OpalGetAsyncCtrlParameters(&Param,sizeof(Opal_GenAsyncParam_Ctrl));
printf("The 1st floating point parameter is %f\n",Param.FloatParam[0]);

String parameter 1 .. 12

Any character entered in this field is available in the asynchronous application by calling the OpalGetAsyncCtrlParameters function. These twelve strings are placed in the StringParam array in the Opal_GenAsyncParam_Ctrl structure.

EX:
Opal_GenAsyncParam_Ctrl Param;
OpalGetAsyncCtrlParameters(&Param,sizeof(Opal_GenAsyncParam_Ctrl));
printf("The first string parameter is %s\n",Param.StringParam[0]);

Name of executable

Name of executable program developed by the programmer to handle communications between Send and Recv block. Note: the controller must be able to find the executable. The program must be in the simulation's directory or in the system's path.

Inputs

This block has no inputs.

Outputs

This block has no outputs.

Characteristics and Limitations

...

Direct Feedthrough

N/A

Discrete sample time

No

XHP support

Yes (Partial XHP only)

Work offline

No