Wire sequence across drawings not working

[jcrispino3]

I have a DC + and - rail that I link across multiple pages. When I go to review the wire sequence, as well as annotate the wiring diagram, I'm getting a disconnect between the wire section that goes between the two pages. I feel like it might have something to do with my source/destination blocks (when I right-click on them I get "No LINE "wire" tied to this Source/Destination marker", even though a wire type is connected to the block). Any help???

[dougmcalexander · Accepted solution]

Is the wire type layer listed in the Create/Edit Wire Type list?  Also, beware if you don’t draft with snap enabled. Some people don’t snap to the grid. This could possibly lead to a no connection, even though the wire might appear connected. There is something called the wire trap distance that can be adversely affected by the scale factor set in the Drawing Properties. But the first thing I would suspect is a wire type layer that isn’t in the Create/Edit Wire Type list. 

[jcrispino3]

No, it is on a wire listed under the "Create/Edit Wire Type" table. I always draft with snap, but I wouldn't suspect it being an issue of the source/destination symbol not being connected to the wire. The command places the symbol directly at the end of the wire. Unless I'm missing something (an attribute) in my source/destination symbol?

[rhesusminus · Accepted solution]

Do you get the same results if you use the default source/destination arrows that come with AcadE?

[jcrispino3]

It did work using the default source/destination arrows and it did lead me to find out what the issue was...

First I thought it was the fact that I didn't have the XREF attribute in my block. But that wasn't the case.

It ended up being that my XnTERM## attributes weren't set at 0,0 although appearing to be at 0,0. I have my XnTERM## attributes rotated 45 degrees to make them easier to find. They were all middle-right justified. I was setting the left "blue square" at 0,0 not realizing that the attribute was justified MR and not actually set at 0,0. Changing everything to L justified fixed everthing!!!

So @dougmcalexander gets a W for knowing the issue and @rhesusminus for pointing me towards finding the issue!!!