I'm trying to implement a multi-instance SW-C with a non-periodic triggered runnable in Simulink and I'm having trouble importing the .arxml file. The arxml files are created in DaVinci Developer 4.4 and exported for Autosar Version 4.0.3.
At first I tried to create a Server/Client interface for the output value and create a server runnable for the 'Get' Operation that I created. Sadly Matlab refused to import the arxml file and greeted me with the following error:
Unable to model the periodic runnables of component '/ComponentTypes/NtcSnsrCs' as AtomicSubsystem because the component contains
serverrunnables: 'TQlfr_Get'. Explicitly specify the ModelPeriodicRunnablesAs parameter with value FunctionCallSubsystem.
For more information, see the arxml import and createComponentAsModel documentation.
I followed the recommendation in the error message and changed the parameter to "FunctionCallSubsystem" and received the following error message:
Unable to model the runnables of component '/ComponentTypes/NtcSnsrCs' as FunctionCallSubsystem because the component supports
multiple instantiation. Either try specifying the ModelPeriodicRunnablesAs parameter with value AtomicSubsystem, or set attribute
supportsMultipleInstantiation of the component '/ComponentTypes/NtcSnsrCs' SwcInternalBehavior to false. For more information,
see the arxml import and createComponentAsModel documentation.
Are server/client interfaces on SW-Cs with multiple instantiation supported by embedded coder/simulink? If yes: How can I import the .arxml?
After running into this road block, I tried to model the interface as a sender/receiver interface. I created a normal runnable and assigned the trigger "On Data Reception". When importing with 'ModelPeriodicRunnablesAs' 'FunctionCallSubsystem' I got the same error as with the Server/Client interface. The following error was displayed after changing the parameter to 'AtomicSubsystem':
Unable to model the periodic runnables of component '/ComponentTypes/NtcSnsr' as AtomicSubsystem because the component does not contain any
runnables triggered by a TimingEvent. Explicitly specify the ModelPeriodicRunnablesAs parameter with value FunctionCallSubsystem. For more
information, see the arxml import and createComponentAsModel documentation.
Is it possible to import a SW-C which supports multiple instatiation and contains a non-periodic runnable? If yes: How ?
Are these error messages limitations of embedded coder or only of the import process? Can I create this functionality in Simulink and export an .arxml-file from there?
PS:Matlab R2017b was used (I can't select that version from the drop down).