MATLAB: Are there unused (previously imported) elements in the “ARXML” file and how to remove them

apiarxmlautosarAUTOSAR Blocksetshortname

The generated "ARXML" file declares items (such as enumerations) that were previously imported, but are no longer used in the model, project or directory. These appear as a <SHORT-NAME> in the ARXML file.

Why are these declared and how do remove them?

Best Answer

Simulink preserves previously imported elements that were created through "updateAUTOSARProperties" for round-trip purposes as explained in the following documentation page:

https://www.mathworks.com/help/autosar/ug/round-trip-preservation-of-autosar-elements-and-uuids.html

These AUTOSAR properties that are generated in the "ARXML" file can be accessed through the "getAUTOSARProperties" API (documentation linked below).

https://www.mathworks.com/help/autosar/ref/autosar.api.getautosarproperties.html

The "delete" method of the "getAUTOSARProperties" object can be used to remove unused elements. For example, to delete an unused Implementation data type:

>> arProps = autosar.api.getAUTOSARProperties(bdroot);
>> IDTs = arProps.find([],'ImplementationDataType','PathType','FullyQualified')
>> arProps.delete(IDTs{17}) % As an example, this would delete the 17th IDTs element

Related Solutions

MATLAB: Can I update a Simulink implementation of the AUTOSAR Software Component to use datatypes I define in an updated ARXML

Using AUTOSAR datatypes defined in an ARXML file is possible if you map the specific component with the datatype. Please see the documentation link I have provided below for more information on this:

https://www.mathworks.com/help/autosar/ug/data-types.html

If you have already been working on the design of a Simulink model, but want to use datatypes that are defined in a new ARXML file:

You can use the updateAUTOSARProperties function. After using this function, you will have to map the datatypes from the ARXML to the Simulink model as in the previous example. The use of updateAUTOSARProperties does not create any new object, but it only imports their definitions into the model’s AUTOSAR Properties.
Once that is done you can create workspace variables for any types using the following APIs, depending on the data type:
createNumericType
createEnumeration
You now can see them in the workspace. Enumerations are imported as CompuMethods.
Another alternative: updateModel does create new objects. However, this may not be suitable for all cases, because it will update the whole model according to the new ARXML, so that some elements may be deleted. I would not recommend using this option for importing new data types unless updating the model is required at the same time by your workflow.
Another alternative would be to use createComponentAsModel. This function does create new objects, but they would appear in a new model. You could then copy or move these types to your model an use them there as needed (Simulink allows for this functionality).

MATLAB: How to change the generated reference to E_NOT_OK in an ARXML file

An existing generated reference (such as "NOT_OK") can be changed to a different Type by using getAUTOSARProperties() and it's object functions. The following code replaces the "NOT_OK" to "E_NOT_OK":

>> arProps = autosar.api.getAUTOSARProperties(bdroot)
>> interfaces = arProps.find([],"Operation","PathType","FullyQualified")
>> oper = arProps.get(interfaces{1},"PossibleError","PathType","FullyQualified")
>> arProps.set(oper{1},"Name","E_NOT_OK")

However, this requires the model to have been used for code generation once, otherwise there is no configured error to change. An alternative method that adds the configuration from scratch, is by adding the available errors on the 'ClientServerInterface' first, then configure the corresponding error that an operation should reference. The following code adds type definitions "E_NOT_OK" and "E_CUSTOM_MESSAGE":

>> arProps = autosar.api.getAUTOSARProperties(bdroot)
>> interfaces = arProps.find([],"ClientServerInterface")
>> add(arProps,interfaces{1},'PossibleError','E_NOT_OK')
>> set(arProps,[interfaces{1} '/E_NOT_OK'],'errorCode',1)
>> add(arProps,interfaces{1},'PossibleError','E_CUSTOM_MESSAGE')
>> set(arProps,[interfaces{1} '/E_CUSTOM_MESSAGE'],'errorCode',2)
>> possibleErrors = arProps.get(interfaces{1},"PossibleError")
>> operations = arProps.find([],"Operation","PathType","FullyQualified")
>> set(arProps,operations{1}, "PossibleError", possibleErrors)

Background on Standard Return Type:

This type is provided by AUTOSAR standard which can be used as standard API return type shared between the RTE and BSW modules. This can be used by API functions of the RTE which could indicate states and errors. "E_NOT_OK" <->0x01 is used for general error.

Best Answer

Related Solutions

MATLAB: Can I update a Simulink implementation of the AUTOSAR Software Component to use datatypes I define in an updated ARXML

MATLAB: How to change the generated reference to E_NOT_OK in an ARXML file

Related Question