Automatically Updating Flatten Links

This task shows you how to get assistance when updating the flatten links of a complete harness and have some parts of the process done automatically.
Have both the 3D harness document and the flattened harness document open.
  1. Click Auto Update Flatten Link in the Update Flatten Links toolbar.

  2. In the flattened harness document, select a bundle segment.

    The bundle segment is identified in the geometry area.
  3. In the 3D harness document, select a bundle segment.

    The bundle segment is likewise identified in the geometry area.
  4. Click in the geometry area to start the comparison.

    The algorithm used is that set in the Flattening Harness Parameters.

    The entire harness is browsed automatically starting from the bundle segment selected first. The algorithm compares components two-by-two to see if they are identical, and if conditions are met, then maps the two components.
    If several solutions are possible, the algorithm informs the user and waits for user input.

    When the comparison is complete, components whose flatten links have been properly updated are highlighted in both documents.

Mapping by Topological Algorithm

Mapping conditions are different for each harness component and take into account tolerance values specified.

  • Bundle segments: must be of the same length and diameter.
  • Devices: must have the same Reference Designator or instance name.
  • Internal splices: must belong the same mapped bundle segment and have the same abscissa along the electrical curve.
  • Supports: must belong to the same mapped bundle segment and have the same abscissa along the electrical curve.
  • Protective coverings: must belong to the same mapped and covered bundle segment and have the same abscissa along the electrical curve.
  • Wires and wire groups: must have the same From/to end and be routed along the same route.

Mapping by Naming Algorithm

Mapping conditions are based on the naming of the Reference Designator if valuated. If this attribute is not valuated, then mapping is based on the Instance Name.

If attributes have the same name, then components are mapped successfully.

Special case for supports: since supports are not considered electrical components, they do not have Reference Designator attributes. The user can, however, specify a user-defined attribute, naming it Reference Designator.