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

3 次查看（过去 30 天）
Vishnu
Vishnu 2024-7-23
编辑： akshatsood 2024-8-13
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

请先登录，再回答此问题。

回答（1 个）

akshatsood
akshatsood 2024-8-13
编辑：akshatsood 2024-8-13
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.

类别

在 Help Center 和 File Exchange 中查找有关 Simulink Coder 的更多信息

标签

产品


版本

R2019a

Community Treasure Hunt

Find the treasures in MATLAB Central and discover how the community can help you!

Start Hunting!

Translated by