Hey everyone,
I've been working on some automation and techniques related to the Cabling environment, and while exploring these areas, I came across a few questions about Creo's native capabilities.
Most examples I've seen will define cables as independent wires. You will have "NEW WIRE_SPOOL"s and "NEW WIRE"s to define an array of wires in a harness model.
However, I know its possible to define both cable spools and cable definitions through the NWF file.
| NEW CABLE_SPOOL | CABLE_SPOOL_1 | 3 |
| PARAMETER UNITS | INCH | |
| PARAMETER NUM_CONDUCTORS | 3 | |
| PARAMETER THICKNESS | 0.7 | |
| PARAMETER MIN_BEND_RADIUS | 10 | |
| PARAMETER WIRE_GAUGE | 0.0 | |
| CONDUCTOR | 1 | |
| PARAMETER UNITS | INCH | |
| PARAMETER COLOR | WHT | |
| PARAMETER THICKNESS | 0.1 | |
| PARAMETER MIN_BEND_RADIUS | 2 | |
| PARAMETER WIRE_GAUGE | 0.0 | |
| PARAMETER CONDUCTOR_NAME | 2463 | |
| PARAMETER COND_ID | 1 | |
| CONDUCTOR | 2 | |
| PARAMETER UNITS | INCH | |
| PARAMETER COLOR | BLU | |
| PARAMETER THICKNESS | 0.1 | |
| PARAMETER MIN_BEND_RADIUS | 2 | |
| PARAMETER WIRE_GAUGE | 0.0 | |
| PARAMETER CONDUCTOR_NAME | 2475 | |
| PARAMETER COND_ID | 2 | |
| CONDUCTOR 3 | ||
| PARAMETER UNITS | INCH | |
| PARAMETER COLOR | RED | |
| PARAMETER THICKNESS | 0.15 | |
| PARAMETER MIN_BEND_RADIUS | 2 | |
| PARAMETER WIRE_GAUGE | 0.0 | |
| PARAMETER CONDUCTOR_NAME | 2451 | |
| PARAMETER COND_ID | 3 |
With that spool definition defined, we can similarly define a cable using the following format:
| NEW CABLE | CABLE_1 | CABLE_1 | CABLE_SPOOL_1 | |
| CONDUCTOR | 1 | |||
| ATTACH | CONNECTOR_1 | 2 | CONNECTOR_2 | 1 |
| CONDUCTOR | 2 | |||
| ATTACH | CONNECTOR_1 | 3 | CONNECTOR_3 | 1 |
| CONDUCTOR | 3 | |||
| ATTACH | CONNECTOR_2 | 2 | CONNECTOR_3 | 2 |
This NWF format will import and parse into Creo appropriately, but when I go to actually autoroute the cables, it seems as though Creo cannot find the entry ports on the appropriate connectors (post-designation, of course), meaning it will not actually perform any autorouting. However, if I model the cable instead as several independent "NEW WIRE"s (aka, 3 NEW WIRE instead of 1 NEW CABLE), it finds the appropriate connector entry's as expected, and autoroutes just fine.
Has anyone had any experience using CABLES in NWF files instead of WIRES? I've attached an example NWF file here.
Thanks,
Sully