wire to/from report mistake

[Shocker1322]

When I run the to/from wire list, there are two wires that always come up I want to get rid of. These wires are in the layer WIRES. I have removed the wires on the drawing (coincidentally they have the same name) and have replaced the devices the wires used to run to. I have even deleted the layer WIRES from being recognized as a valid wire layer. However these wires are still being reported in the to/from list. Is there a reason why this could be happening, or a way to purge all memory of former wires and rebuild the to/from list? I cannot find any reference of these wires or devices anywhere on the drawing. I even turned off every layer except WIRES and there was nothing using that layer. Any ideas would be appreciated, thanks.

[Anonymous]

One way to troubleshoot this is to run your wire from/to report for just the
drawing where these phantom WIRES are showing up. In the report dialog
select "Change Report Format" and add in the WIREHDL1 and WIREHDL2 fields
into the report.

Now find your phantom wire entry in the report. You should see a column with
"h=xxxx" entry where "xxxx" is some hexidecimal number. This gives the
AutoCAD object "handle" tag for the wire.

At your command line, type this:

(entget (handent "xxxx")) [Enter] where the xxxx=the entry from the report
without the "h=" prefix.

Example, report column shows "h=5C3D". Type in the above command like this:

(entget (handent "5c3d")) [Enter]

Your command line will now display something looking like this:

Command: (entget (handent "5c3d"))
((-1 . ) (0 . "LINE") (330 . )
(5
. "5C3D") (100 . "AcDbEntity") (67 . 0) (410 . "Model") (8 . "WIRES") (6 .
"Continuous") (100 . "AcDbLine") (10 3.93747 50.7643 0.0) (11 3.83747
50.8643
0.0) (210 0.0 0.0 1.0))

The "10" and "11" entries give the end point coordinates of the phantom
wire. You should be able to use these coordinates to locate the line entity
that is causing you some problems.

Nate.

Example
wrote in message news:4893683@discussion.autodesk.com...
When I run the to/from wire list, there are two wires that always come up I
want to get rid of. These wires are in the layer WIRES. I have removed the
wires on the drawing (coincidentally they have the same name) and have
replaced the devices the wires used to run to. I have even deleted the
layer WIRES from being recognized as a valid wire layer. However these
wires are still being reported in the to/from list. Is there a reason why
this could be happening, or a way to purge all memory of former wires and
rebuild the to/from list? I cannot find any reference of these wires or
devices anywhere on the drawing. I even turned off every layer except WIRES
and there was nothing using that layer. Any ideas would be appreciated,
thanks.

[Shocker1322]

I tried what you suggested. When I ran the to/from list I got the following h values: h=510 ; h=13C. I ran the following commands, and got the following outputs.

Command: (entget (handent "13C"))
Error: bad argument type: lentityp nil
Command: (entget (handent "510"))
Error: bad argument type: lentityp nil

When I do run it on some of the other h values I had, those seemed to work fine.

Command: (entget (handent "2D6B1"))
((-1 . ) (0 . "LINE") (330 . ) (5
. "2D6B1") (100 . "AcDbEntity") (67 . 0) (410 . "Model") (8 . "1069_#16") (100
. "AcDbLine") (10 844.602 -429.4 0.0) (11 858.295 -429.4 0.0) (210 0.0 0.0 1.0))

So I guess this is a bigger problem than first expected. Thanks for helping so far.

[Anonymous]

Try running the AcadE Audit utility (under the Schematic Report toolbar
flyout) against your project. If that fails to resolve the problem, you can
zip and send me your project set. Send to nate.holt@autodesk.com.
thanks,
Nate.

wrote in message news:4893893@discussion.autodesk.com...
I tried what you suggested. When I ran the to/from list I got the following
h values: h=510 ; h=13C. I ran the following commands, and got the
following outputs.

Command: (entget (handent "13C"))
Error: bad argument type: lentityp nil
Command: (entget (handent "510"))
Error: bad argument type: lentityp nil

When I do run it on some of the other h values I had, those seemed to work
fine.

Command: (entget (handent "2D6B1"))
((-1 . ) (0 . "LINE") (330 . )
(5
. "2D6B1") (100 . "AcDbEntity") (67 . 0) (410 . "Model") (8 . "1069_#16")
(100
. "AcDbLine") (10 844.602 -429.4 0.0) (11 858.295 -429.4 0.0) (210 0.0 0.0
1.0))

So I guess this is a bigger problem than first expected. Thanks for helping
so far.

[Shocker1322]

I was able to get rid of the two wires that were bothering me by deleting the drawing from the project, then adding the drawing back in. However this caused a catastrophic error in which all wires seem to have a double. One wire is the correct one, and changes with wire. The other seems to be a phantom wire that displays the same symptoms as the original problem. It cannot be deleted and cannot be changed. I have attached a small part of a much larger circuit that displays these problems. The terminal points are devices I customized, so the problem may be there.

[Shocker1322]

I believe I have isolated the error. This error occurs in the project database. Whenever I remove a drawing, then add it back in, I get a duplicate error. Removing and re-adding a second time adds 3 wires. And again adds 4. I created a new project, and added back in all the drawings. This seem to have fixed the problem. I am fairly sure the program should not act like this. Hope this helps to get it fixed.

[Anonymous]

Shocker1322

You are correct, the program should not be acting in this fashion. Have you
downloaded and installed SP1 (Service Pack 1) for AutoCAD Electrical 2006?

--
=======================
Jared (Autodesk, Inc)
=======================
wrote in message news:4894455@discussion.autodesk.com...
I believe I have isolated the error. This error occurs in the project
database. Whenever I remove a drawing, then add it back in, I get a
duplicate error. Removing and re-adding a second time adds 3 wires. And
again adds 4. I created a new project, and added back in all the drawings.
This seem to have fixed the problem. I am fairly sure the program should
not act like this. Hope this helps to get it fixed.

[Shocker1322]

I am only running ACE 2005 right now. We plan to upgrade to 2006 this month, so hopefully this problem will go away with the new edition. Thanks for all the support.