createComponentAsSubsystem - Class: arxml.importer
Package: arxml
Create AUTOSAR atomic software component
as Simulink atomic subsystem
Syntax
[susbsysH, success]
= importerObj.createComponentAsSubsystem(ComponentName)
[susbsysH, success]
= importerObj.createComponentAsSubsystem(ComponentName, Property1, Value1, Property2, Value2,
...)
Description
[susbsysH, success]
= importerObj.createComponentAsSubsystem(ComponentName)
creates a Simulink subsystem corresponding to the AUTOSAR atomic
software component 'COMPONENT' described in the
XML file imported by the arxml.importer object importerObj.
You can also specify optional property/value pairs when creating
this Simulink subsystem:
[susbsysH, success]
= importerObj.createComponentAsSubsystem(ComponentName, Property1, Value1, Property2, Value2,
...)
You can perform AUTOSAR configuration and code generation on
atomic subsystems or function call subsystems. These subsystems must
be convertible to model reference blocks by using the method:
Simulink.SubSystem.convertToModelReference
Note
The AUTOSAR target automatically checks that the subsystem meets
this requirement when you perform a subsystem build. |
You do not have to convert your subsystem to a model reference
block; it is optional. If you convert your subsystem to a referenced
model, you can configure AUTOSAR options within the referenced model.
You can export functions for a single function-call
subsystem. First configure your function-call subsystem AUTOSAR options
(e.g., using the GUI from the Configuration Parameters dialog or by
calling autosar_gui_launch(subsystemName)).
Then right-click the subsystem and select Real-Time
Workshop > Export Functions.
Inputs
| ComponentName | Absolute short name path of the atomic software component
. |
| PropertyN, ValueN | Optional property/value pairs. You can specify values for the
following properties:- CreateSimulinkObject
Boolean value, true or false (default is true). If true, the
function creates the Simulink.AliasType and Simulink.NumericType corresponding
to the AUTOSAR data types in the XML file. - NameConflictAction
'overwrite' (default) or 'makenameunique' or 'error' .
Use this property to determine the action to take if a Simulink model
with the same name as the component already exists. - AutoSave
Boolean value, true or false (default is false). If true, the
function automatically saves the generated Simulink model.
|
Outputs
| susbsysH | Subsystem handle. |
| success | True if the function is successful. Otherwise, it is false. |
Examples
importer_obj.createComponentAsSubsystem('/package/autosar_component2')See Also
Importing an AUTOSAR Software Component in the Real-Time Workshop Embedded Coder documentation
 | createComponentAsModel (arxml.importer) | | createOperationAsConfigurableSubsystems (arxml.importer) |  |
Learn more about Simulink through this collection of videos, articles, technical literature and the Getting Started with Simulink Guide.
Get this Simulink Kit
Store 
