Main Content


Specify data type, code generation options, other attributes of signal

For run-time calibration of AUTOSAR data, R2018b and R2019a introduced graphical mapping of model elements to AUTOSAR component parameters and variables. In the Code Mappings editor, you select a Simulink® model-workspace parameter or internal signal, state, or data store. You map the selected element to an AUTOSAR component parameter or variable and modify its AUTOSAR calibration attributes. If you currently model AUTOSAR parameters or variables by using AUTOSAR parameter or signal objects in the base workspace, consider migrating to the Code Mappings editor workflow. For more information, see Map AUTOSAR Elements for Code Generation.


With this class, you can create workspace objects for mapping internal global signals to AUTOSAR memory sections. You can create an AUTOSAR4.Signal object in the base MATLAB® workspace.

This class extends the Simulink.Signal class. With signal objects, you can assign or validate the attributes of a signal or discrete state, such as its data type, numeric type, dimensions, and so on. For more information, see the Simulink.Signal reference page.


Create an AUTOSAR4.Signal object by using the AUTOSAR4.Signal function described below.


signalObj = AUTOSAR4.Signal returns an AUTOSAR4.Signal object with default property values.

Open the workspace object to view and modify its properties.

The Simulink.Signal reference page describes the signal attributes in detail. The AUTOSAR4.Signal class extends the Simulink.Signal class with the following additional selection for the Storage class attribute:

  • Global — Allows you to map internal global signals to AUTOSAR memory sections. Selecting this storage class enables the custom attribute MemorySection.

    MemorySection allows you to explicitly select AUTOSAR memory section VAR, CAL, or VOLATILE, or accept the Default.

Version History

Introduced in R2014a