MagicDraw SysML/Cameo: For export of more complex physical interaction and flow cases to Modelica or Simulink/Simscape/Stateflow load the SysPhS ModelLibrary using SysPhSLibrary.mdzip as a shared project.

Icon class
icon_class
far fa-sticky-note
icon_class_computed
far fa-sticky-note
Note kind
TIP
Specification keywords
SysML-1.6
SysPhS-1.1
SysPhS Keywords
SysPhS ModelLibrary
Keywords
Click on the image to view it full size
As of 2021-01-12 the four samples for export to Modelica and Simulink all use the additional SysPhS ModelLibrary, expanded in the attached image.

For example, in the SignalProcessor sample the Mixer and TwoPinSignalComponent both have part properties typed by the ReadSignalInElement and ReadSignalOutElement from the SysPhSLibrary.

Compare with:
MagicDraw SysML/Cameo: You do not always need to load the entire SysPhS ModelLibrary for simpler black box exports to Modelica or Simulink/Simscape/Stateflow (sometimes the sysphs_profile within the MD Customization for SysML is enough)
To use SysPhS in the [util:mdsysml)] or Magic Cyber-Systems Engineer ® (Cameo Systems Modeler®) load SysPhSLibrary.mdzip as a shared project (if working in local mode) under: 
/modelLibraries/SysPhSLibrary.mdzip
Relates to
SysPhS zone (SysML Extension for Physical Interaction and Signal Flow Simulation)
Related notes
[TIP] MagicDraw SysML/Cameo: You do not always need to load the entire SysPhS ModelLibrary for simpler black box exports to Modelica or Simulink/Simscape/Stateflow (sometimes the sysphs_profile within the MD Customization for SysML is enough)
Related notes (backlinks)
Related snippets (extracts)
Visit also
Visit also (backlinks)
External links
No Magic Docs: Exporting to External Simulation Models