The Signal-To-Service Editor supports you in mapping AUTOSAR Classic Signals to AUTOSAR Adaptive Events of Services. The mapping to Signal Groups and Signals is supported for Events and Implementation Data Type Sub-Elements of an Event.
The Signal-To-Service Editor is splitted into two areas, the Editor and the
Builder.
Open Signal-To-Service Editor | <CTRL> + <SHIFT> + <D>, <Y> |
ISignal to Service Interface
In some cases, an Adaptive Application needs to communicate with a Classic Application, but as Adaptive Applications communicate in a service-oriented manner with Service Interfaces, while Classic Applications communicate in a signal-based manner using so called ISignals, a translation between them is needed.
On a model-level, the translation entails creating an appropriate Port to either receive or send a signal-based payload. This can be done by mapping a Service Interface to one Classic signal, using a Service Instance To Signal Mapping. The direction of the port, whether it's receiving or providing, will be determined by whether the signal-based payload is incoming to the Adaptive Application or outgoing.
Open Editor
To open the Signal-To-Service Editor, expand your DaVinci Adaptive project in the DaVinci Project Explorer and double click on Open Project Dashboard. The Project Frame opens showing the Project Home. You can then open the Signal-To-Service as follows:
- Open the
Editor menu on the top right of the Project Frame and click the
Signal-To-Service Editor command.
- Alternatively, use the context menu command
Open Signal-To-Service Editor of the
Open Project Dashboard node in the DaVinci Project Explorer.
- Alternatively, on the Dashboard page of the Project Home, click
Signal-To-Service Editor in the Comfort Editors area.
- Alternatively, use the context menu command
Open in Signal-To-Service Editor of a Service Instance To Signal Mapping Set or Service Instance To Signal Mapping in the AUTOSAR Model Explorer.
The Signal-To-Service Editor opens in a new tab of the Project Frame.
Editor
The Signal-To-Service Editor provides the functionalities listed below. If not otherwise mentioned, the functionalities available in the Form mode are described. If you want to manage the properties of an element textually, switch to the
DML mode via the toolbar and refer to DaVinci Modeling Language Editor for more information.
Tree View Structure | Description of Functionalities |
---|---|
| Select a Service Instance To Signal Mapping Set in the tree view on the left side of the editor. At the top of the form page, the general properties are displayed and can be modified:
Signal-To-Service Translations Area The Signal-To-Service Translations area displays existing Mappings from three perspectives, each in an individual tab:
General Functions
|
| Select a Service Instance To Signal Mapping in the tree view on the left side of the editor. At the top of the form page, the general properties are displayed and can be modified:
Signal-To-Service Translation Area This area provides the possibility to map Signals to Events of a Service Interface either before or after selecting a Service Instance. So even though a suitable Service Instance must still be selected before generation, the mapping can already be done beforehand. You can modify the mapping as follows:
Service Usage Area In this area, the Service Instance of the Service Instance To Signal Mapping must be selected.
General Functions
|
MICROSAR Adaptive Parameters Area
This area contains MICROSAR Adaptive Parameters that are specified as Model Extensions (MEX) in the MICROSAR Adaptive BSW Package. Parameters for the selected AUTOSAR model element are displayed in the table of the MICROSAR Adaptive Parameters area on the respective pages of the Signal-To-Service Editor. Select a parameter in the table to view the editing options.

For more information on the MICROSAR Adaptive Parameters, refer to the Technical Reference in the .\Doc\TechnicalReferences folder of your MICROSAR Adaptive BSW Package.
Builder
The Builder provides the automatic creation of service events, which perfectly matches to the signal selection of the selected PDUs.
Configuration
Within the configuration area, you can define namespaces, packages and files as well as naming rules for the generated output, initially.
After the initial definition the configuration area can be minimized.
- Data Type Output: Define Namespace, Package and File.
- Interface Output: Define Namespace, Package and File.
- Mapping Output: Define Mapping Set and File.
- Element Naming: Add Prefix and/or Postfix definition, to define the naming for the created elements.
For File definition, it is possible to Copy Up Down already defined files.
Ethernet Communication Connector
Select the Ethernet Communication Connector which should be used. After the selection, all available PDUs, signals and signal groups will be shown in the overview below.
Auto-hide Signals
Use a regular expression to filter out irrelevant signals. These signals are not shown in the overview and hence not selected.
PDU/Signal Overview
Select the PDUs, signals and/or Signal groups which should be mapped.
Create Event(s)
Use the Create Event button to create events based on the selected signal(s) and signal groups. Decide if the created event(s) should be added to a new Interface or to an existing one.
- Add to new Interface
A new Interface will be created based on configuration definitions. - Add to selected Interface
The created event(s) will be stored within the selected Interface.
Service Interface Event Element Overview
Within the Service Interface Event Element Overview, you can see all interfaces and events. Here it is possible to
Delete
Only the selected interface/event will be deleted.Advanced Delete
Delete the selected service interface/event and all associated data which is not used by other event mappings.