The Autosar System Signals generator extension view is used to generate system signals and system signal groups for a defined inter ECU Communication in an allocated Autosar System. For more information about the Autosar standard, visit the Autosar home page.

Prerequisites

• The complete Autosar Meta model for describing allocated Autosar Systems
• An existing, approved Architectural Signal List
• An installation of the SystemWeaver Explorer client (swExplorer), version R34 or later
• The SWExtension.SystemSignalsGenerator extension is located in the Client's swExplorerExtensions directory
• An SW Architect has configured and activated the view via Configure the explorer

The view is accessible via menu options on the ribbon that have been configured by an Architect, and are available when an AUTOSAR System item is selected. Below is one example of a configured option. 

Example Menu Option

They are also available via the View drop-down at the bottom of the list by ribbon group name. 

Getting Acquainted with the View

With an allocated AUTOSAR system selected, the top section of the view will present a grid of approved architectural signals together with the system signals which based on them and will be generated. Some filtering options are also available to make working with long signal lists easier. Any faulty mappings will be displayed in the bottom section of the view.

The following information is displayed in the list.

Arch Signal name

The name of the architectural signal.

Element

The path from ECU down to each primitive data type.

System Signal Name

The name of the system signal that will be generated. It consists of the Arch system signal name combined with the primitive data type, and a system-generated number. 

Status

This column indicates the status of each system signal, and this determines how the given signal is handled when the 

system signal generation operation is executed in the view. 

New	Indicates that a new signal will be created in the System signals list
Included	Indicates that the signal is already generated and included in the System signals list
No data type	Indicates that no data type exists in the Sender receiver interface
Delete	Indicates that Arch system signal does not exist in the Arch system signal list
Included new version	Indicates that the Arch system signal has been updated, but the mapping or group mapping has not. The versions are not in sync.

Filtering Options

Some useful Filter options are available at the top of the view if you are interesting in only viewing a subset of architectural  signals. Multiple selections are ORed together. Filtering is useful especially with long lists.

Faulty Mappings 

Faulty mappings are mappings that do not have a system signal. When you use the view to generate system signals as described below, the listed faulty mappings will be removed. 

Generating System Signals

In order to use the view to generate system signals, the view checks for the existence of the following: 

• The Autosar system must be in 'Work' status
• An Arch system signal list exists in the structure and it is in 'Work' status
• The interfaces have datatypes
• The records and arrays are not empty. Any empty ones are ignored.

To generate system signals, click the Generate System Signals button at the bottom right corner of the view. 

The table below describes how listed signals are handled based on their Status. 

Example Result

Note: If no Arch system signal list is found in the selected AUTOSAR system, a pop-up will indicate this.  An Arch system signal list can be created using the Architectural System Signals extension view.  If no System signals list is found, you will also be notified:

What's Next?

The generated system signals can now be imported into a Networking tool.