Compontent library best practice for inherited ports

Systems engineering related questions and discussions.

Moderator: Moderators

Compontent library best practice for inherited ports

Postby steven.gonzalez@caemilusa.com » Wed Dec 15, 2021 12:43 pm

Im trying create a component library that has blocks with full port already defined. My question though is how can i add a nested proxy port to an inherited full port with out adding it to parent class.

My goal is to have full port define the physical connection (ie RJ45) and then later define the type of information passing through via the proxy port (ie vlan0,vlan1,etc)
You do not have the required permissions to view the files attached to this post.
steven.gonzalez@caemilusa.com
Forum Newbie
Forum Newbie
 
Posts: 1
Posts Rating:0
Joined: Tue Dec 14, 2021 3:48 pm

Re: Compontent library best practice for inherited ports

Postby alfgarciacasado@gmail.com » Thu Dec 16, 2021 3:35 am

A full port represents a part of your block that is at the boundary. Thus a full port will be typed by a block.
If the parent full port is defined, then it needs a block that types that full port (e.g. the Physical Connector block in the image).

To do that you can do the following:
1- create the specialization RJ45 block that inherits from the Physical connector.
2- create the proxy port on that RJ45
3- create the interface block that types that proxy port (e.g. Data IF)
4- create the Child block that inherits from your Parent block.
5- go to the Specification window of the Child block > go to the Ports/Interfaces section > select p1 port and
6- click on the redefine button below and change the type of p1 to RJ45.

Then you have it.

Best Regards,

Alfonso
You do not have the required permissions to view the files attached to this post.
alfgarciacasado@gmail.com
Forum Newbie
Forum Newbie
 
Posts: 3
Posts Rating:1
Joined: Thu Dec 03, 2020 2:57 am


Return to Model Based Systems Engineering (MBSE)

Who is online

Users browsing this forum: No registered users and 0 guests