IBD: Header1 on an Arduino Mega2560R3 - connections

The many Connectors render this large IBD rather cluttered, the idea here in this trail is merely to show how the underlying information can be captured.

Click on the image to view it full size

Modelling and style

To reduce visual clutter no 'net' tagged values are shown on any Connectors here.

Only «pin» Ports on the ATmega2560 mpu chip that have direct connections to «pin» Ports of :Header1 or related nets are shown. In some cases on the board there are actually intermediate nets that are not shown here.

Note how intermediate «node» block instances are used to represent connection via a common «net».

On the Arduino interactive board viewer schematic (SCH) view the pin p99_GND:GND is indicated as AGND.

Advanced topic

It was claimed at the beginning of this trial that «pin» encapsulates a physical connection contract. In the case shown, that contract at the header pins must in fact be from the bottom of a female header (the metal pins sticking through PCB holes) rather than the "female" sockets on top into which prototype jumper leads plugs are inserted for a specific use of the board. To model it properly, one would also need a separate matching set of Ports just for the externally exposed sockets with a different «pin» contract (but in this trail we're only looking at the default internal wiring of the board):

Visit also (later): Webel: SysML: Electronics: DO NOT represent a jack/socket as a dumb proxy. Imagine it can introduce some signal noise or other effect (such as buzz) to test it is a physical model.

Ever had a wobbly jumper plug?

Up next

IBD: Header2 on an Arduino Mega2560R3 - connections

Notes

[CAPABILITY, FEATURE, TIP, TOOL] In MagicDraw/Cameo an assigned stereotype of a Classifier that types an instance-like element (such as a part Property) "shines through" unless it has an instance-level stereotype assigned. This is sometimes called a "secondary stereotype".

[NAMING, POLICY, STYLE]{STRONG} SysML: Webel: "Trust the Type!" - Often the name of the Type of an anonymous Property or instance-level element is completely sufficient to indicate its role - unless multiple Properties of the same Type have different roles within the same owner context!

[NAMING, POLICY, STYLE] "Trust the Port or Pin Type!" - Often the name of the Type of an anonymous Port or Pin is completely sufficient to indicate its role, unless a clear indication of its direction or unique role is required.

[ANTI-PATTERN, MODELLING, PATTERN, TIP]{STRONG} Webel: SysML: Electronics: DO NOT represent a jack/socket as a dumb proxy. Imagine it can introduce some signal noise or other effect (such as buzz) to test it is a physical model.

[CAPABILITY, FEATURE, TOOL]{INFORMATIVE} MagicDraw/Cameo supports embedding images in diagrams

Snippets (quotes/extracts)

Visit also