Community Tip - Visit the PTCooler (the community lounge) to get to know your fellow community members and check out some of Dale's Friday Humor posts! X
I'm having an issue.
On shielded cables that have pairs, somehow the conductors route, but not the overall cable diameter. Any ideas?
I have attached by datatable, membermap and XML file.
Solved! Go to Solution.
Ray,
I believe by looking at your membermap and your descriped problem you have created an overbraid. Cable is looking for you to put a sheathing over everything. Instead of defining the cable shape in Creo Schematics as 4 twisted pairs and a shield just do 8 single wires and a shield then add decorations to show the groups. Your memebermap should only be 1 level with the "physical name1" lisiting something like PAIR1_WIRE1, PAIR1_WIRE2, PAIR2, WIRE1, ect.
Thanks,
jef
Usually when you route conductors, the cable splits at the last location before the connector and the conductors route to their respective ports.
Or do you mean the complete cable doesn't route at all and only the conductors are routed over the full length of the cable?
The complete cable doesn't route. Only the conductors route the full length. The overall cable "c4" does not route.
Here is the video. Maybe this will determine what the issue is.
Ray,
I believe by looking at your membermap and your descriped problem you have created an overbraid. Cable is looking for you to put a sheathing over everything. Instead of defining the cable shape in Creo Schematics as 4 twisted pairs and a shield just do 8 single wires and a shield then add decorations to show the groups. Your memebermap should only be 1 level with the "physical name1" lisiting something like PAIR1_WIRE1, PAIR1_WIRE2, PAIR2, WIRE1, ect.
Thanks,
jef
I think you nailed it. Now I have to go back and fix "all" my shielded pair member maps and cable shapes. About 15 of them.
Yep, it was confirmed with using an Multilevel cable, that Creo Parametric "does not" read the cable diameter and minimum bend radius ! It is a known issue that the thickness and min_bend_radius is not brought over. The recommendations is to use assign_min_bend and assign_thickness on the <name>-B1* item in the model tree.
Wow, I'm surprised PTC can't fix this. Another reason not to use multilevel cables.