Skip to main content
apapadopoulos-2
apapadopoulos-210-Marble
10-Marble
April 22, 2026
Question

Creo Cabling Repeat Region

  • April 22, 2026
  • 2 replies
  • 54 views

Greetings,

 

Looking for ideas on how to report sum length of cable spool based on custom length per spool segment used in cable harness.

example:

spool A - length=L1, custom_length (driven from relation) =CL1, spool used N1 times in harness.

total length of spool A =?

the problem i have is that I can’t make any relation as there is no way to use rep.qty for cable spools in a harness.

summation function is also not very flexable. I would prefer if it was function then I could create a relation with If (example: if spool a name==A sum).

Is there another simpler way to solve it? 

Practically best solution I found is to generate the table  > export to CSV > make simple excel relation.

2 replies

L
Lars_F14-Alexandrite
14-Alexandrite
April 28, 2026

You can sum the results of length‑related relations by using Repeat Region Summation.

If you have a relation that modifies the length per spool, one approach is to separate each spool into its own filtered table and then apply the summation to the relation‑based length values. The idea is illustrated in the image below. In this example, each table uses a simple relation of the form:

len_with_extra = harn_run_len + 5

and the total spool length is obtained by summing len_with_extra within that table.

That said, in many cases you can simply rely on harn.spool.len to get the total length of wire required for a spool.
For cable harnesses, any additional length needed inside the connector (for example, from the entry port to the crimp or terminal) should normally be handled using the connector parameter Internal_len (INT_LENGTH). This parameter adds the specified length to the wire beyond the entry‑port coordinate system, where the routed wire would otherwise terminate. As a result, harn.run.len and harn.spool.len already include this internal connector length, and extra relations should only be used for additional slack such as service loops or manufacturing allowances.

 

 

Br,

Lars

    apapadopoulos-2
    apapadopoulos-210-MarbleAuthor
    10-Marble
    April 28, 2026

    Hello and thank you for reply. splitting tables is something I considered but its is not practical or generical. Its easier to export to CSV and do it in excel. But “harn.run.len and harn.spool.len already include this internal connector length” is something that that I didn’t consider. It might simplify or give another way to determine overlength. thank you for the tips.

    I'm the self-inflicted mind detonator, yeah I'm the one infected, twisted animator.
    L
    Lars_F14-Alexandrite
    14-Alexandrite
    April 28, 2026

    Hello,

    You can sum the results of length‑related relations by using Repeat Region Summation. It may not be flexible but it does sum all values in one column.

    If you have a relation that modifies the length per spool, one approach is to separate each spool into its own filtered table and then apply the summation to the relation‑based length values. The idea is illustrated in the image below. In this example, each table uses a simple relation of the form:

    len_with_extra = harn_run_len + 5

    and the total spool length is obtained by summing len_with_extra within that table.

    That said, in many cases you can simply rely on harn.spool.len to get the total length of wire required for a spool.
    For cable harnesses, any additional length needed inside the connector (for example, from the entry port to the crimp or terminal) should normally be handled using the connector parameter Internal_len (INT_LENGTH). This parameter adds the specified length to the wire beyond the entry‑port coordinate system, where the routed wire would otherwise terminate.

    As a result, harn.run.len and harn.spool.len already include this internal connector length, and extra relations should only be used for additional slack such as service loops or manufacturing allowances.

     

    Br, Lars

     

    Terms & ConditionsAccessibility statement