Does variation point blocks get generated for OPERATION-INVOKED-EVENT runnables ?

I have added Variation points for a runnable like below from systemdesk

<RUNNABLE-ENTITY UUID="32a97bd4-8cc3-443b-979d-8423bf9af7c1">

<SHORT-NAME>ActvAirDamCtrlDTIStart</SHORT-NAME>

<MINIMUM-START-INTERVAL>0</MINIMUM-START-INTERVAL>

<CAN-BE-INVOKED-CONCURRENTLY>true</CAN-BE-INVOKED-CONCURRENTLY>

<SYMBOL>ActvAirDamCtrl_ActvAirDamCtrlDTIStart</SYMBOL>

<VARIATION-POINT>

<SHORT-LABEL>ActvAirDamVPnt</SHORT-LABEL>

<SW-SYSCOND BINDING-TIME="PRE-COMPILE-TIME">

<SYSC-STRING-REF DEST="SW-SYSTEMCONST">/FCAVariants/VariantManagement/BuildActvAirDam</SYSC-STRING-REF>==1</SW-SYSCOND>

</VARIATION-POINT>

</RUNNABLE-ENTITY>

But once the model is created the runnable does not contain this variation point

Answer 1

[akshatsood]

Dear @Vishnu

I understand that you have added variation points for a runnable element in SystemDesk and imported it into Simulink. However, the runnable does not contain this variation point.

As mentioned in the following documentation, "VARIANT-POINT" entries appear for AUTOSAR ports, runnables, and runnable accesses to external data:

https://www.mathworks.com/help/releases/R2019a/autosar/ug/configure-autosar-variants-in-ports-and-runnables.html

Can you try replacing "SYSC-STRING-REF" with "SYSC-REF" as detailed in the above documentation and reimporting to see if this helps? I believe there might be compatibility issues between Simulink and SystemDesk.

Please refer to the attached documentation for detailed guidance on configuring variants for AUTOSAR elements.

I hope this helps.