Create variable interface sizes in System Composer

Question

Brad 2024-4-6

0
链接

此问题的直接链接

https://ww2.mathworks.cn/matlabcentral/answers/2103721-create-variable-interface-sizes-in-system-composer

评论： Josh Kahn 2024-4-15

I would like to use System Composer to perform design trades, but to do so I need to be able to easily change interface definitions. Perferably, I would like the ports to inherit the data types and shapes sent to them like a Simulink subsystem does. However, when I try to add a test harness to a system composer block and send it data from a MATLAB workspace, it balks at a difference in port sizes.

Can System Composer interface definitions be made to truly inherit dimensions and types like Simulink models can?

0 个评论
显示 -2更早的评论隐藏 -2更早的评论

请先登录，再进行评论。

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

Answer 1

Josh Kahn 2024-4-10

0
链接

此回答的直接链接

https://ww2.mathworks.cn/matlabcentral/answers/2103721-create-variable-interface-sizes-in-system-composer#answer_1439381

SystemComposerSubsystemReferenceExample.zip

Hi @Brad Williams,

One way is to save the architecture as a Subsystem reference architecture:

https://www.mathworks.com/help/systemcomposer/ug/decompose-and-reuse-components.html#mw_073b1bd0-46f1-4696-a513-8c1eb7d11750

The recommended workflow is to use variants to define your design choices and then choose the appropriate variant during your trade study (see Create Variants on the same page). Variant component choices can have different interface and port configurations as long as any connected interfaces and ports align.

Hope this helps!

Josh

2 个评论
显示无隐藏无

Brad 2024-4-14

Thanks for clarifying the supported functionality. I was hoping that the low-overhead approach that Simulink supports with inherited data types would flow up into System Composer. Creating System Composer variants is a good approach once the trade space has been downselected somewhat, but a little limiting / time consuming in the earliest trade studies.

Josh Kahn 2024-4-15