11.3 Component behavior - Real.Continuous

The following diagram shows a Block Definition Diagram (BDD) style representation of MagicDraw/Cameo SysPhSLibrary components vs the SysPhS-1.1 spec table 11.3.2.2 Continuous components:

Click on the image to view it full size

Some identified errors in the MagicDraw SysML Plugin and Magic Cyber-Systems Engineer^® (Cameo Systems Modeler^®) versions of the SysPhSLibrary:

MDSysML/Cameo 19SP3: SysPhSLibrary vs SysPhS-1.1: Continuous.Integrator is missing the 'init' PhSConstant (maps to y_start in Modelica)

MDSysML/Cameo 19SP3: SysPhSLibrary vs SysPhS-1.1: SPELLING/TYPO: VariableDelay: parameter 'maxDelay' should be 'delayMax'

The following might have more consequence:

MDSysML/Cameo 19SP3 vs SysPhS-1.1: The Continuous.TransferFunction and Discrete.TransferFunction have Ports 'u : RealVectorSignalInElement [1]' or '[*]' and 'y : RealVectorSignalInElement [1]' or '[*] instead of RealSignalInElement/RealSignalOutElement

The tool library versions seems to contradict the spec convention when compared with the table under 11.3.2.2 Continuous components:

SysPhS-1.1: 'Simulation platform data specified in the Component Ports (Input and Output), PhSConstants, and platform Parameters columns are scalar, unless marked with a V (vector) or an M (matrix). Component input ports for scalars are typed by RealSignalInElement, IntegerSignalInElement, or BooleanSignalInElement, while component output ports for scalars are typed by RealSignalOutElement, IntegerSignalOutElement, or BooleanSignalOutElement ... Component input ports for vectors are typed by specializations of RealVectorSignalInElement, while component output ports for vectors are typed by specializations of RealVectorSignalOutElement ...'

Transfer functions don't per se have to be restricted to scalar input and output, but the spec descriptions seem to only describe scalar ones.

Up next

11.3 Component behavior - Real.Discrete

Notes

[ISSUE, TOOL] MDSysML/Cameo 19SP3: SysPhSLibrary vs SysPhS-1.1: Continuous.Integrator is missing the 'init' PhSConstant (maps to y_start in Modelica)

[ISSUE] MDSysML/Cameo 19SP3 vs SysPhS-1.1: The Continuous.TransferFunction and Discrete.TransferFunction have Ports 'u : RealVectorSignalInElement [1]' or '[*]' and 'y : RealVectorSignalInElement [1]' or '[*] instead of RealSignalInElement/RealSignalOutElement

[ISSUE] MDSysML/Cameo 19SP3: SysPhSLibrary vs SysPhS-1.1: SPELLING/TYPO: VariableDelay: parameter 'maxDelay' should be 'delayMax'

Snippets (quotes/extracts)

[SysPhS-1.1] Simulation platform data specified in the Component Ports (Input and Output), PhSConstants, and platform Parameters columns are scalar, unless marked with a V (vector) or an M (matrix).

[SysPhS-1.1] Component input ports for scalars are typed by RealSignalInElement, IntegerSignalInElement, or BooleanSignalInElement, while component output ports for scalars are typed by RealSignalOutElement, IntegerSignalOutElement, or BooleanSignalOutElement ...

[SysPhS-1.1] Component input ports for vectors are typed by specializations of RealVectorSignalInElement, while component output ports for vectors are typed by specializations of RealVectorSignalOutElement ...

Visit also

SysPhS-1.1

SysPhS zone (SysML Extension for Physical Interaction and Signal Flow Simulation)

Visit also (backlinks)

Related slides (includes other tutorials)

Related slides (backlinks, includes other tutorials)

Flags