Why don't all my Simulink data dictionary entries have a defined APPLICATIO​N-VALUE-SP​ECIFICATIO​N short-label field in my ARXML file when using AUTOSAR code generation?

My model uses autosar.tlc as target. To observe the code generation issue please generate the code with AUTOSAR toolbox.

In our AUTOSAR dictionary settings we have 'ImplementationDataType' option as "NotAllowed" under the AUTOSAR dictionary, so that we can generate an application data type for each AUTOSAR data type.

However, in the generated ARXML file many signals defined in my Simulink data dictionary do not have a corresponding "APPLICATION-SPECIFIC-VALUE" defined correctly for instance.

For example, if I have a bus signal "exSig" with minimum and maximum values 0 to 20 is defined. I expect that an  APPLICATION-VALUE-SPECIFICATION short-label field of "DefaultInitValue_Float_0to20" exists.

However, the generated ARXML, does not contain this short-label field, which causes an SWC integration issue and is preventing me from completing my work.

Answer 1

[MathWorks Support Team]

When using the AUTOSAR target system, the generated code only defines properties for signals that are used in the corresponding Simulink model and not external dictionaries/sources. This seems to be an optimization to not generate superfluous code, and to allow for componentized modules.

A simple workaround would be to define an "In Bus Element" or "Out Bus Element" for the desired respective inport/outport signals , this should generate the necessary short-label fields. No additional blocks would need to be added, however, this should specify that your model would like to define this signal and its properties.