Bundle Operations

These actions restructure how conductors are grouped and routed across bundles. They appear in various context menus (bundles, pins, branch points) and are collected here for a unified reference.

Redirect Bundle Endpoint

Move one end of a bundle to a different node.

A new connector X1 is added to the design, and the bundle BP1–P5 is redirected from BP1 to X1. Because "Delete remaining" is selected, the 3 conductors on bundle P1–BP1 that previously continued through to P5 are removed — reducing the conductor count on P1–BP1 by 3 and clearing their pin connections on P1.

Available from the Bundles context menu via Topology → Redirect.... Changes the source or target node of a bundle. The submenu is split into "Change source" and "Change target" sections, each listing eligible nodes.

When a conductor's path spans multiple bundles, redirecting one bundle can leave dangling segments on the remaining bundles. A sub-submenu offers three options depending on the topology:

Option	Behavior
Maintain connectivity	Extend the conductor's path through an existing bridge bundle between the old and new endpoints, preserving the original start and end nodes. Only appears when a bridge bundle exists.
Delete remaining	Remove the dangling segments entirely. The conductor is isolated to only the redirected bundle — any portions that sat on other bundles in the original path are discarded.
Keep as new conductors	Preserve the dangling segments as separate new conductors. The original conductors are isolated to the redirected bundle, and the orphaned segments become independent conductors that keep the original gauge, color, and material properties.

Automatic handling: If the redirect creates a loop back to the conductor's own start or end node, redundant bundles are trimmed automatically.

Insert Branch Point

Split a bundle in two by inserting a junction at its midpoint.

A new branch point is inserted along bundle BP1–P5. All conductors continue through to their previous endpoints.

Available from the Bundles context menu via Topology → Insert Branch Point. Splits a bundle at its midpoint, creating a new branch point. The original bundle becomes two bundles, and all conductors pass through the new branch point automatically. This is the starting point for splitting bundles — once a branch point exists, you can configure routing rules to direct conductors down different legs.

Join Bundles

Remove a branch point by merging its connected bundles back together.

The inverse of Insert Branch Point (and Consolidate Bundles). Removes a branch point by joining its connected bundles. Available in two places:

Branch Points → Join Bundles

Removes the branch point and merges its bundles. Works with any number of connected bundles:

2 bundles: Merges them into a single bundle. Conductors from both are preserved. Any splices at the branch point are removed as part of the operation.
3+ bundles: Groups conductors by their entry/exit bundle pair and creates one merged bundle per group. For example, a trunk BP with 4 fan-outs + 1 trunk becomes 4 direct bundles. Only available when no splices exist at the branch point and every conductor passes straight through (enters one bundle, exits another).

Right-clicking BP2 shows the Join Bundles option. The 4 bundles extending from the branch point are merged into direct connections — BP2 is removed and all conductors are preserved with their original pin assignments.

Bundles → Topology → Join with...

Available from the Bundles context menu via Topology → Join with.... Joins this bundle with an adjacent bundle through a shared branch point. A submenu lists available bundles. If the branch point has no remaining connections after the join, it is removed automatically.

Bundle BP2–P2 is selected and joined with bundle BP2–BP1 via the shared branch point BP2. BP2 is removed and the two bundles merge into a single direct bundle BP1–P2.

Reversing a Consolidate Bundles: After merging parallel bundles, each trunk branch point can be removed with Join Bundles. Two joins (one per BP) fully restores the original direct connections.

Consolidate Bundles

Combine parallel bundles into a shared trunk with fan-out legs.

Available from the Bundles context menu via Topology → Consolidate Bundles, and from the Multi-Selection context menu. Select 2 or more bundles and merge them into a trunk structure. Two topologies are supported:

Hub-spoke (bundles share a common node)

A branch point is inserted between the hub and the spokes. The original bundles are replaced with a trunk bundle from the hub to the branch point, plus fan-out bundles from the branch point to each spoke. Conductor routing through the hub is preserved.

Bundles BP2–P2, BP2–P3, and BP2–P4 are selected and merged. A new branch point BP3 is inserted, creating a shared trunk BP2–BP3 with fan-out bundles BP3–P2, BP3–P3, and BP3–P4.

Parallel independent (no shared nodes)

Two branch points are inserted — one on each side — with a trunk bundle between them. Each original bundle is replaced with a source fan-out, the shared trunk, and a target fan-out. Source vs. target sides are determined automatically by geometric position.

Bundles X3–X4, X5–X6, X7–X8, and X9–X10 — which share no common endpoint — are selected and merged. Two new branch points are created as fan-outs, with a shared trunk bundle running between them.

Mixed selections (some bundles share a node, others don't) are not supported — all selected bundles must match one of the two cases above.

Merge into Selected Path

Absorb a stray bundle into an existing trunk. New stub bundles to the trunk's ends are created automatically.

The trunk bundle BP3–BP2 is selected along with both end branch points. Right-clicking the stray FR24–FR23 bundle and choosing Merge into selected path creates two new stub bundles (FR24–BP3 and BP2–FR23), reroutes the conductor through the trunk, and removes the original direct bundle.

Available from the Bundles context menu via Topology → Merge into selected path. Unlike Consolidate Bundles, the trunk is picked explicitly through selection.

The interaction

The first plan-mode operation that uses selection-as-operands, right-click-as-subject: pick the trunk on the canvas, then right-click the bundle you want absorbed.

Click the trunk bundle. Shift-click each link if it's a multi-segment chain.
Shift-click each end branch point. You only select the ends — interior branch points in a multi-segment trunk are walked automatically.
Right-click the stray bundle → Topology → Merge into selected path. The caption shows "via BP3 ↔ BP2" when the selection is valid, or a hint about what's missing when it isn't.
Hover to preview: stray bundle dims and dashes, trunk highlights, terminal branch points glow, dashed ghost lines show the stub bundles to be created.
Click to commit.

The menu item stays visible while you build the selection, disabled with a caption like "Also shift-click both terminal branch points" until the trunk + ends are complete.

What happens on commit

Each stray endpoint pairs with whichever trunk terminal is geographically closer on the active page.
A new bundle is created from each stray endpoint to its paired terminal — reused if one already exists between those nodes.
Conductors on the stray bundle get rewritten to [stubA, …trunk, stubB], oriented per conductor's start/end direction.
Wire groups on the stray bundle are removed; the stray bundle itself is deleted.
If the stray bundle has no conductors, the topology change still happens — stubs are created, stray is removed, just no rerouting step.
If a stray endpoint already is a trunk terminal, no stub is created on that side.

Disabled or refused

The item is disabled when the trunk selection isn't a single connected chain of branch-point-only nodes, or when the right-clicked bundle is itself part of the trunk.

The command refuses with a warning toast when a conductor on the stray bundle has a multi-link path (use Reroute Conductors instead), belongs to a cable (cables move as a unit), or is locked by an assembly reference.

Undo is one step — restores the stray bundle, conductor paths, and wire groups; removes any created stubs.

Wire groups on the new route are a separate step. The merge only changes routing; use Wire Groups tools to twist or braid the absorbed wire with the trunk's existing conductors.

Merge Branch Points

Collapse multiple branch points into a single junction.

Available from the Multi-Selection context menu when 2 or more branch points are selected. Select the branch points you want to consolidate, right-click, and choose Merge Branch Points.

The branch point with the most external connections (bundles to non-selected nodes) is kept as the survivor. All other selected branch points are absorbed into it:

Bundles from removed branch points are redirected to the survivor.
Splices are moved to the survivor.
Branch point parts (boots, grommets, etc.) are consolidated onto the survivor.
Any bundles that connected two selected branch points are removed.

The selected branch points do not need to be directly connected by a bundle — any set of branch points can be merged. Hover the menu item to preview the result: removed branch points and bundles fade out, and dashed ghost lines show the new bundle paths to the survivor.

The entire operation is a single undo step — Ctrl+Z restores all original branch points, bundles, and routing.

Four branch points (BP1–BP4) are selected and merged into one. The survivor retains all external bundles, splices, and parts. A single undo restores the original topology.

Move Branch Point to Bundle

Reposition a branch point onto a different bundle.

Available from the Branch Points context menu via Topology → Move to Bundle.... Detaches a branch point from its current position and places it onto a different bundle, splitting that bundle in two.

The submenu lists all eligible target bundles on the current page. Hover a target to preview the result.

What happens:

The target bundle is split at the branch point — creating two new bundles (one on each side of the BP).
Conductors on the target bundle are rerouted through the branch point.
The branch point's old bundles that overlap with the target bundle's endpoints are absorbed (merged into the new split bundles).
Non-overlapping old bundles follow the branch point to its new position.
Wire groups and cable assignments migrate to the appropriate new bundles.
The branch point is positioned at the midpoint of the target bundle's endpoints.

Requirements: The branch point must have at least one connected bundle. Bundles locked by an assembly cannot be moved.

Convert Node Type

Change a node between branch point, component, and flying lead types.

Available from the Topology submenu in the context menu for branch points, components, and flying leads.

Conversion	Effect
Branch Point → Component	Promotes the branch point to a full component with pins. Conductors that passed through the branch point become pin connections on the new component.
Component → Branch Point	Demotes the component to a branch point junction. Pins are removed and conductor endpoints are converted to pass-through routing.
Flying Lead → Component	Promotes the flying lead to a full component. A category submenu lets you choose the new component type.

These conversions preserve all connected bundles and conductors. The entire operation is a single undo step.

Reroute Conductors

Change which physical path a conductor takes between its endpoints.

A new bundle is added between P5 and P6. The context menu on bundle BP1–P5 is used to reroute conductors via the new path through P5–P6. The conductor count on BP1–P5 is reduced by 3 as those conductors now travel through BP1–P6–P5 instead.

When multiple routes exist between a conductor's start and end nodes (through different branch points and bundles), you can switch which path the conductor follows. Available from two views:

View	How to Access
Layout	Right-click a bundle → Topology → Reroute Conductors.... A submenu groups conductors by endpoint pair, with each group showing available alternative routes. Select a route to move all conductors in the group. Only appears when at least one conductor on the bundle has an alternative path.
Schematic	Right-click a conductor → Reroute via.... A submenu lists all valid paths between the conductor's endpoints, labeled by the nodes along each route. The current path is indicated with a checkmark.

Routes are displayed as the sequence of nodes along the path (e.g., Conn1 → BP1 → Conn2). Shorter routes are listed first. When rerouting from a bundle in Layout view, all conductors sharing the same endpoint pair are rerouted together in a single operation.

The same reroute operation accessed through the Properties panel for bundle BP1–P5. Conductors are rerouted via the alternative path through P5–P6, reducing the conductor count on BP1–P5 by 3.

Tip: If you don't see the Reroute option, only one path exists between the conductor's endpoints. Use Insert Branch Point and add bundles to create alternative routes first.

Deletion Cascades

What gets automatically cleaned up when you delete something.

When you delete a node, bundle, or conductor, associated data is automatically cleaned up:

You Delete	What Gets Cascaded
Component or Branch Point	All connected bundles are removed, which cascades further to their conductors, wire groups, cable assignments, and splices.
Bundle	All conductors on the bundle are removed. Wire groups and cable assignments scoped to the bundle are deleted. Splices referencing removed conductors are updated, and any splice that drops below two conductors is automatically deleted.
Conductor	References in wire groups and cable assignments are cleaned up. Splices that drop below two conductors are automatically deleted.

All delete operations are undoable — Ctrl+Z restores the deleted items and all cascaded data.