nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

HW Library: Function for adding several ports

medini_1062733402

Hello together,

by creating a hardware library I'd like to model the pins of a connector.by using ports.

The problem:

Actually I have to create port by port. Time intense.

I'd like to have a function that asks me for number of ports (pins) and further for the counting method (e.g., Port A, Port B, Port C, ... or Port 1, Port 2, Port 3, ...).

My requirements to that functions are:

* Possibility to enter number of Ports

* Possibility to select counting method

Best Regards

Benedikt Wilhelm

Find more posts tagged with

medini

medini legacy

Accepted answers

medini_1024169437

Hello Benedikt,

I solved the issue in the script. Please find an updated version attached.

Happy Scripting

Jan

All comments

medini_1024169437

Hello Benedikt,

glad to have you here in the forum. Well, I quickly tries to realize what you asked for, later recognizing that i did not read you post carefully. Anyway, here a script that (1) can create numerous ports and (2) asks for a message format that at last can format "Port-XX" or similar, so no "Port A" but maybe you can help improving it.

The script looks like:

// $EXPERIMENTAL$
/*
 * Copyright (c) 2019 ANSYS medini Technologies AG
 * All rights reserved.
 * 
 * The script is provided "as is" without warranty of any kind. 
 * ANSYS medini Technologies AG disclaims all warranties, either express or implied, 
 * including the warranties of merchantability and fitness for a particular purpose.
 * 
 * v2019-04-15 - initial version
 */

if (!selection || (selection.length != 1) || !(selection[0] instanceof Metamodel.sysml.SysMLPart)) {
	throw "This script must be executed on a single SysML part only";
}

load(".lib/factory.js");
load(".lib/finderEx.js");
load(".lib/ui.js");

var scope = selection[0];

// Validator
function mustBeNumeric(text) {
	if (!text) {
		return "Please enter a valid number";
	}
	var num = parseInt(text);
	console.log("{0} {1}", num, typeof num);
	if (num < 0 || isNaN(num)) {
		return "Please enter a valid number";
	}

	return null;
}

var ports = [];
var num = inputText("Number", "Number of ports (numeric value)", 10, mustBeNumeric);
if (num > 0) {
	var format = inputText("Format", "Name format", "Port-{0,number,00}");
	for (var i = 0; i < num; i++) {
		var port = Factory.createElement(scope, Metamodel.sysml.SysMLPort);
		port.name = java.text.MessageFormat.format(format, i);
		ports.push(port);
	}
}

// reveal
ports;

Also find it attached. The required libraries you can find in the separate article https://medini.freshdesk.com/support/solutions/articles/1000273630-scripting-libraries

Would be cool if you can enhance and re-post your changes. Of course you also may come back with questions.

Happy Scripting.

medini_1024169437

Sorry, the script as attachment

Jan

medini_1062733402

Hello Jan,

thank you. The script works well and is flexible for individual namings.

I've just adapted the script, that it starts from 1 and not from 0.

line 41: for (var i = 1; i <= num; i++) {

I have one optimization point:

Actually I only can execute this script in the project BOM parts, line 13-15. I'd like to execute this in the HW Part Library.

Is this related to the topic, as discussed in the last meeting, that the HW part library should be handled as a separate project and then shared to the different projects?

I created a HW Part Library within the project under System Design\HW Part Libraries\HW Part Library

medini_1024169437

Hi Benedikt,

thanks for checking out. I incorporated your numbering improvement and also added support for blocks (aka types). It was merely a limitation of the script and is not really related to the question, where exactly your blocks are modeled.

However, if you share a library with other people its still advisable to maintain that in an external project and always edit it there.

I also added a check to prevent adding ports to a "typed part".

Here is the updated script, find it also attached:

// $EXPERIMENTAL$
/*
 * Copyright (c) 2019 ANSYS medini Technologies AG
 * All rights reserved.
 * 
 * The script is provided "as is" without warranty of any kind. 
 * ANSYS medini Technologies AG disclaims all warranties, either express or implied, 
 * including the warranties of merchantability and fitness for a particular purpose.
 * 
 * v2019-04-18 - support blocks, some more validation
 * v2019-04-15 - initial version
 */

// enforce single selection
if (!selection || (selection.length != 1)) {
	throw "This script must be executed on a single element only";
}

// only parts or types
if (!(selection[0] instanceof Metamodel.sysml.SysMLPart) && !(selection[0] instanceof Metamodel.sysml.SysMLBlock)) {
	throw "This script must be executed on a SysML part or block (type) only";
}

var scope = selection[0];

// well, parts shall NEVER by typed
if (scope instanceof Metamodel.sysml.SysMLPart && scope.theType) {
	throw "This parts is typed - please create ports in the type, never the instance";
}

load(".lib/factory.js");
load(".lib/finderEx.js");
load(".lib/ui.js");


// Validator
function mustBeNumeric(text) {
	if (!text) {
		return "Please enter a valid number";
	}
	var num = parseInt(text);
	console.log("{0} {1}", num, typeof num);
	if (num < 0 || isNaN(num)) {
		return "Please enter a valid number";
	}

	return null;
}

var ports = [];
var num = inputText("Number", "Number of ports (numeric value)", 10, mustBeNumeric);
if (num > 0) {
	var format = inputText("Format", "Name format", "Port-{0,number,00}");
	for (var i = 1; i <= num; i++) {
		var port = Factory.createElement(scope, Metamodel.sysml.SysMLPort);
		port.name = java.text.MessageFormat.format(format, i);
		ports.push(port);
	}
}

// reveal
ports;

Happy Scripting

Jan

medini_1062733402

There is one additional point:

When i created ports at a component inside the HW library and then looking into the FMEDA, the component name of all ports is 'new port', but in the HW library the name is e.g. 'Pin-01'.

medini_1024169437

Hm, indeed that's an issue. Reason is that the port synchronization is done on port creation. As you maybe know, the name of the port is not kept in sync at the moment, so changing the port's name in a type is not synced back to the instance (planned to change that but not yet in 2019 Rx).

I have to think about this, maybe with some tricks I can bypass this limitation.

Jan

medini_1024169437

Hello Benedikt,

I solved the issue in the script. Please find an updated version attached.

Happy Scripting

Jan

medini_1062733402

Very good!

Thank you.

Regards

Benedikt

medini_1024169437

You are welcome, Benedikt, please mark one comment as "answer" if you have time.

Jan

medini_1024169437

Benedikt, I found an issue in the script when you create ports in parts. The creation in types (blocks) is fine but not for party that have no type. I have attached a fixed script.

If you have used the script just for types you are fine, otherwise you should use the updated script and remove the old ports.

Jan