As mention in the GUI and common-workflows section, you may select Data to be used on the Software component Interface as queued or non-queued Data Send Point (Explicit Write) or Data Receive Point (Explicit Read), or as Data Read Access (Implicit Read) or Data Write Access (Explicit Write), or as CalPrm Access.
This results in corresponding definitions in the XML and generated code. See the following examples.
Each of these five Data Exchange Behavior options may be implemented as one of two Statemate MicroC Access Modes: "Buffered" or "Direct Using Get/Set API's". This is configured with a corresponding set of Design-Attributes on the Internal-Behavior (Default behavior in braces):
● Implicit Write Access Mode (Direct Using Get/Set API's)Each of these Design-Attributes may be set with the following 3 values:
● By Design Attribute - When "By Design Attribute" is selected, SAG will refer the Design-Attribute "Double Buffered" in the following way:In case of using Explicit Read/Write, you may want to assign the return value of the RTE API assign to a variable. This can be achieved by using a Design-Attribute "RTE Status Variable Name" available for Data-Item, Condition and Event. A non-empty value of this Design-Attribute specifies the name of a variable that will be assigned with the return value of the Explicit Read/Write RTE API's. Its default value is empty string. It is the user's responsibility to define such variable (Data-Item) in the model , with the correct settings, e.g.: Exact Type = Std_ReturnType.