CapitalKnowledge

Conductors > Shield Terminations

Daisy-chaining Shield Indicators

You can use daisy chains to indicate graphically that multiple multicore or overbraid shields have a common termination point.

When you daisy-chain indicators on multicores or overbraids one (and only one) of the multicore or overbraid indicators needs to have a shield termination, at which all the shields will terminate. You can add the shield termination before or after creating the daisy chain. See also Adding a Shield Termination. If none of the indicators on a group of daisy‑chained indicators has a shield termination, the daisy chain does not represent connectivity.

Daisy chains on diagrams are graphical objects rather than connectivity objects. See “Graphic Drawing Tools” in the Capital Design Tools - Common Functions User Guide for a description of graphical objects. Daisy chains therefore cannot have properties added to them and cannot be connected to splices.

Note

To add a daisy chain to a multicore that was promoted to be shared, a shield termination must be defined in the multicore’s shared object definition in Capital Project Manager. See “Edit Shared Multicore Dialog Box” in the Capital Project Manager User Guide to add a conductor to a shared multicore in Capital Project Manager.

If indicator hookups are not displayed for a shared multicore it indicates that the multicore’s shared object definition in Capital Project Manager does not have a shield termination defined. Once you have added a shield termination in Capital Project Manager, in Capital Logic Designer press Spare Bar and enter Refresh Shared Objects and the indicator hookups will be displayed.

You can add daisy chains manually or by using the “Connect Indicators with Daisy Chain” action.

  • Adding a Daisy Chain Manually

  • Generating Daisy Chains

Parent Topic:

Shield Terminations

Capital Logic Designer User Guide, 2512

Unpublished work. © 2025 Siemens

Source: https://docs.sw.siemens.com/en-US/doc/861057055/202410078.capital_ld_user/idb77f4378-cf17-4174-b5b7-c4c5b23ab1cc · retrieved 2026-07-18