CapitalKnowledge

Wiring

Automatic

Change of Multicore Type During Wiring Synthesis

Multicore types are usually defined in the associated, logical designs. However, you can use a ‘Set multicore type’ constraint to specify that wiring synthesis changes the type of a multicore, removes a multicore completely (leaving the wires that would otherwise be innercores as part of no multicore), or removes shielding defined against a multicore (provided this does not invalidate logical connectivity).

Caution

You cannot use this constraint with combined logical multicores. It works with functional-source multicores only.

In addition, you cannot change a multicore in a way that violates logical connectivity. For example, you cannot remove a shield from a mutlicore if the shield maps to a device pin that connects to the functional source of the shield.

See Overview of Rules and Constraints for high-level information about working with rules and constraints.

The constraint can be applied to a design or a harness. You can apply it to a full multicore or a subset of a multicore by applying it to the appropriate harnesses. For example, shielding may be removed from a portion of a multicore that runs through a small harness but be retained across the rest of the multicore in other harnesses.

Caution

If the constraint changes a non-shielded multicore to a shielded type, the shield is not added automatically.

A design rule check ‘Multicore that breaks multicore type rule’ is available to run that identifies multicores that violate any applicable ‘Set multicore type’ constraints (rules). See “Design Rule Checks” in the Capital Design Tools - Common Functions User Guide for general information about running design rule checks.

Scenario Example
To change a multicore type: CopyRetain multicore and set multicore type to coax where multicore matches Name = MC33.*In this example, the multicore type is changed to coax for any multicores with a name attribute that starts MC33.
To remove a multicore: CopyRemove multicore and set multicore type to none where multicore matches Name = MC2In this example, wiring synthesis removes a multicore with a name attribute that matches MC2. Any innercores are retained as wires (no longer in a multicore).
To remove shielding from a multicore: CopyRemove shield and set multicore type to oval where multicore matches Name = MC34.*In this example, wiring synthesis removes shielding and changes the multicore type to oval for any multicores with a name attribute that start MC34.
To restrict the multicore type so that it matches the associated, logical design: Note If a multicore type needs to be restricted for a certain harness, you can set the multicore type as existing so that the type is protected. ‘Existing’ takes the multicore type from the associated, logical design. CopyRetain multicore and set multicore type to existing where multicore matches Name = MC4.In this example, a multicore with a name matching MC4 is retained and has the multicore type taken from the associated, logical design. This will override any change that has been made manually to the multicore type for MC4 in Capital Systems Integrator.

Parent Topic:

Wiring

Capital Systems Integrator User Guide, 2512.2606

Unpublished work. © 2026 Siemens

Source: https://docs.sw.siemens.com/en-US/doc/861057055/202511026.capital_si_user/id2aadaf87-81fd-42d4-af4b-1e20e31d18e0 · retrieved 2026-07-18