Is there a way to associate two cable cores connected to the same point?
The black and blue wires cant be associated to a cable since there already one cable core associated at that point
I'm not able to do it on my machine either. I can do it if daisy-chaining wires, no problem. The issue arises when having two wires, both with the same origin and destination. When you tell it to number the wires it doesn't see it as two wires. Both get numbered with the same equipotential and wire number. You should contact your VAR and ask them to create a bug report for you.
I am facing the same problem. I have a terminal on a component to which a control wire and a ground wire is terminated. I want the wire number on the control wire, but not on the ground wire. I can't find a way to achieve this.
Did anyone get this resolved? I don't see an answer here a few years later, but I'm having the same issue. In this case I have multiple shield terminations ganged up to the same pins. I would like to associate multiple cable cores connecting between the same terminals. One work around is to add "splice" components between each shield and the pin so that the software see's the different splice terminals. However, it would be cleaner/better for this application if SWE allowed multiple cable cores to connect to the same terminals.
I came across this problem and asked the question here:
Multiple Cable Cores to a Single Connection Point
No acceptable answer was given.
When you reach the limits of what the software is able to do, submit a enhancement request for them to add functionality. Go here, https://customerportal.solidworks.com/ , and click on enhancement request. I've had many features added into the program that it didn't initially have.
At this moment, this cannot be done in this way but maybe there are some workarounds. My question is, do you need that information (2 cable cores from the same cable) in reports? is it also used for 3D? or is it just to indicate in the scheme that there are 2 physical connections between E1 and U1?
What I have found is that the way the application presents it's intelligence when connecting wires, is desirable for reporting but not the schematic drawing. The only solution I have found that will provide the correct connection list and not 'combine' items is to keep them separate.
During my schooling it was beat into me that this was the only acceptable method for the drawing. Anything else would present confusion to the installers who were trying to figure out how the thing was wired based on the schematic...
Retrieving data ...