advertisement
ETAS Interfaces
A sender-receiver interface can be used to communicate data (using data element prototypes within the <DATA-ELEMENTS>
element) or modes (see section 6.2,
Mode
, on page 67 for more details).
Tip
In AUTOSAR R3.1.5 or lower , a sender-receiver interface can contain zero or more data elements and/or zero or more mode groups. However, it is good practice to separate interfaces used for data transfer and interfaces used for mode management.
In AUTOSAR R4.0.* , a sender-receiver interface must contain either data elements or a single mode group. If a sender-receiver interface contains both kinds of elements, an error is issued during code generation.
6.1.1
Data Element Prototypes
Each sender-receiver interface can specify zero or more data elements that constitute the
AUTOSAR signals communicated over the interface. Each data item defines a prototype of a specific type and can be a primitive data type, a RECORD or an ARRAY type. See chapter 4,
Data Types
, on page 33 for details of defining data types.
To create a data element in ASCET:
In the component manager, double-click on SRInterface .
The "Sender Receiver Interface Editor for: SRInterface" editor opens.
Use the Signed Discrete Variable button to create an sdisc variable.
The "Properties for Scalar Element: sdisc" dialog window opens.
Name the signed discrete variable Speed .
Figure 17 : Data element Speed for the sender-receiver interface SRInterface
To create an implementation of a data element:
In the "Sender Receiver Interface Editor for: SRInterface" editor, go to the Implementation tab.
In the Implementation tab, double-click the Speed element.
The "Implementation for: Speed" window opens.
In the "Master" field, activate Implementation .
In the "Implementation" field, select sint16 .
Right-click in the "Min" and "Max" fields and select Default
Value from the context menu.
Close the "Implementation for: sdisc" window with OK .
ASCET V6.3 AUTOSAR User’s Guide 64
ETAS Interfaces
The Implementation tab of the "Sender Receiver Interface
Editor for: SRInterface" editor shall look like the figure below.
Figure 18 : Implementation Impl of the sender-receiver interface SRInterface with data element Speed
An implementation of a sender-receiver interface in ASCET corresponds to a sender-receiver interface in AUTOSAR. The sender-receiver interface in configuration language is generated by ASCET in the file Swc_interfaces.arxml
.
In
AUTOSAR R3.1.5 or lower
, the declaration of data elements within a sender-receiver interface definition has the following structure:
Listing 27: ARXML code - declaration of data elements within sender-receiver interface
(AUTOSAR R3.1.2)
ASCET V6.3 AUTOSAR User’s Guide 65
ETAS Interfaces
In
AUTOSAR R4.0.*
, the declaration of data elements within a sender-receiver interface definition has the following structure:
Listing 28: ARXML code - declaration of data elements within sender-receiver interface
(AUTOSAR R4.0.2)
A data element is defined using the <DATA-ELEMENT-PROTOTYPE> 1 / <VARIABLE-DATA-
PROTOTYPE> 2 element, and all elements must be defined within an encapsulating <DATA-
ELEMENTS> element.
Each <DATA-ELEMENT-PROTOTYPE> / <VARIABLE-DATA-PROTOTYPE> element must specify:
the <SHORT-NAME> that you will use to refer to the item
the <SW-DATA-DEF-PROPS> data properties, among them
the <SW-CALIBRATION-ACESS>
a <TYPE-TREF> reference to the type of the data item
AUTOSAR R3.1.5 or lower only: whether the data reception <IS-QUEUED> or not
<IS-QUEUED>false</IS-QUEUED> – means that a newly received value overwrites the previous value of the datum. If a value is sent multiple times before it is received then the receiver can only access the last transmitted value.
1 AUTOSAR R3.1.5 or lower
2 AUTOSAR R4.0.*
ASCET V6.3 AUTOSAR User’s Guide 66
advertisement
Related manuals
advertisement
Table of contents
- 13 Introduction
- 13 Safety Advice
- 13 Correct Use
- 13 Labeling of Safety Instructions
- 13 Demands on the Technical State of the Product
- 14 System Information
- 14 User Information
- 14 User Profile
- 14 Document Structure
- 15 How to use this Manual
- 16 Related Documents
- 16 Definitions and Abbreviations
- 18 AUTOSAR Overview
- 18 AUTOSAR Basic Approach
- 19 What is an AUTOSAR Authoring Tool?
- 20 What is a Runtime Environment?
- 21 What is a Behavior Modeling Tool?
- 22 Developing Software Components in ASCET
- 22 Configuring ASCET
- 22 Configuring the Creation of AUTOSAR Components
- 22 Code Generation Settings for AUTOSAR
- 25 Settings for the AUTOSAR XML Output
- 26 Code Generation
- 28 Approaches for Creating Software Components
- 28 Top-Down Approach
- 30 Bottom-Up Approach
- 30 Working with the RTE Generator
- 31 Contract Phase
- 31 RTE Phase
- 33 Data Types (AUTOSAR R3.1.5 or Lower)
- 33 BSW Types
- 33 Primitive Data Types
- 36 Primitive Data Types With Semantics
- 39 Complex Types
- 39 Record Types
- 43 Array Types
- 45 Data Types (AUTOSAR R4.0.*)
- 45 Application Data Types
- 45 Implementation Data Types
- 45 Type Mappings
- 46 Platform Types
- 47 Base Types
- 47 Examples
- 47 Primitive Data Type
- 50 Enumeration Type (Primitive Data Type with Semantics)
- 52 Record Type (Complex Types)
- 58 Array Type (Complex Types)
- 62 Interfaces
- 62 Sender-Receiver
- 64 Data Element Prototypes
- 67 Mode Switch
- 71 Client-Server
- 72 Operations
- 79 Calibration
- 80 Calibration Parameters
- 84 NVData (AUTOSAR R4.0.* only)
- 85 Variable Data Prototypes
- 87 Software Component Types
- 88 Ports
- 88 Provided Ports
- 93 Required Ports
- 101 Internal Behavior
- 102 Events
- 103 Timing Events
- 104 Operation-Invoked Events
- 106 Mode-Switch Events
- 108 Runnable Entities
- 110 Responding to Timing Events
- 111 Sending to a Port
- 111 Explicit Communication
- 113 Implicit Communication
- 115 Receiving from a Port
- 116 Explicit Data Read Access
- 118 Implicit Data Read Access
- 120 Responding to a Server Request on a Port
- 122 Concurrent Invocation of Servers
- 124 Making a Client Request on a Port
- 126 Interrunnable Variables
- 126 Scalar Interrunnable Variables
- 128 Complex Interrunnable Variables (AUTOSAR R4.0.* only)
- 129 Read and Write Access
- 132 Exclusive Areas
- 132 New Since ASCET V
- 132 Configuration
- 134 Usage
- 136 Modes
- 136 Defining Modes
- 137 Mode Communication
- 138 Using Modes
- 139 Software Component Initialization and Finalization
- 139 Triggering a Runnable Entity on a Mode-Switch
- 141 Disabling Modes
- 144 Implementing Software Components
- 144 Basic Concepts
- 144 Namespace
- 144 Runnable Naming Convention
- 144 API Naming Convention
- 145 API Parameter Passing Mechanisms
- 145 Application Source Code
- 145 Application Header Files
- 146 Entry Point Signature for Runnable Entities
- 147 Sender-Receiver Communication
- 148 Sending to a Port
- 151 Receiving from a Port
- 154 Client-Server Communication
- 155 Implementing a Server Operation
- 156 Making a Client Request on a Port
- 157 Accessing Calibration Parameters
- 161 Accessing ASCET Messages
- 165 Concurrency Control with Exclusive Areas
- 166 Sequences of a Runnable Assigned to an Exclusive Area
- 168 ETAS Contact Addresses
- 169 software
- 172 : Enable creation of AUTOSAR components
- 173 : Project settings for AUTOSAR projects