Wire numbers not working with custom built symbol

Wire numbers not working with custom built symbol

Zerb
Advocate Advocate
979 Views
4 Replies
Message 1 of 5

Wire numbers not working with custom built symbol

Zerb
Advocate
Advocate

So i created a custom symbol using the symbol builder and when i try and add any sort of wire numbers to any of the wires that are attached to the symbol using Wire Numbers--Automatic Wire Numbers, then picking the individual wires that I want to number, it does not work.  Now if i shorten the wire away from the symbol, then add the wire number as described above it works just as it should;  then I just stretch the wire and land it back on the symbol.  Am i missing something here?  Attached a picture for clarity.  Thanks! 

0 Likes
980 Views
4 Replies
Replies (4)
Message 2 of 5

Zerb
Advocate
Advocate

So it seems after some reading on here and testing I have the situation fixed.  All of the custom symbols i built i didnt use the proper naming conventions for ACADE apparently.  I was just using say 440-D22R2, for the name of this particular symbol in question.  Once I used the suggested naming convention HDV...etc, now everything seems to work as it should.  Which leads me to another issue perhaps someone can help with.  

 

Wire numbers seem to sometimes work properly and sometimes not.  If I number a wire that say starts on 100 and travels down across the drawing then back up and ends on line 100 as well.  I number the wire and it give me 1000, which is how I have my wiring convention setup, 1000, 1001, 1002, etc.  Then when I add a switch on that same wire, which travels down to say line 103, it will split the wire and then give me the number on the other side of the switch as sometimes 1001 or sometimes 1030. 

0 Likes
Message 3 of 5

Anonymous
Not applicable

In your project properties down at the bottom there is a setting for "Tag / Wire Number / Wire Sequence Sort Order".

You can change the behavior.

Sounds like you have vertical ladders, and the default for those is "Left to Right, Moving Down".

 

If you have a wire that starts on rung 100, moves down and around and what not, but eventually winds up back on rung 100, it will wire number that last segment that is starting/ending on rung 100 with the next available rung number for run 100. Since the wire started on rung 100, the 1000 number is already used, so it will get 1001.

 

Even if you have components breaking the wiring on different rung, as long as any of those wire segments do not get up to run 100, they will number for the nearest rung they start/end on.

 

Even if you renumber them by hand (but don't "fix" those wire numbers).. if you use any autowire renumber tool (scoot, move component, retag renumber, etc...) it will renumber to the "Left to Right, moving down".

 

ACADE can't tell what you wanted... it just sees two wires on rung 100, and numbers them accordingly.

0 Likes
Message 4 of 5

Icemanau
Mentor
Mentor

It's all down to how ACADE looks at the spacing between rungs/wires for the numbering function.

 

For example, at the halfway point between rungs, ACADE sets the rung number from 100 to 101.

If the wire coming down crosses over that point, any new wire starting after a component will be numbered using the 101 number and not the 100 number.

 

Regards Brad

>

Brad Coleman, Electrical Draftsman
Did you find this post helpful? Feel free to Like this post.
Did your question get successfully answered? Then click on the ACCEPT SOLUTION button.

EESignature

0 Likes
Message 5 of 5

JeffatPrimex
Collaborator
Collaborator

Sounds like your symbol may have the same X?TERMn attribute all wire connection points must have a unique number if the same X?TERMn exists then the next wire will not get numbered because ACE has already numbered X?TERMn

 

Best regards,
Jeff

0 Likes