| Author |
 Topic  |
|
|
AndyB
United Kingdom
208 Posts |
 Posted - 31 Aug 2010 : 09:26:36
|
V14
I have a dangling track error but cannot find it.
connectivity checks say's
Checked 17 of 17 nets.
0 split nets found.
0 single pin nets found.
Fully connected nets (17)
and
Optimised nets. |
Edited by - AndyB on 31 Aug 2010 09:57:21 |
|
|
shadders
United Kingdom
224 Posts |
Posted - 31 Aug 2010 : 12:16:36
|
Hi,
I have had to remove a net to find the Dangling Track since it is possibly small and short due to the track placed on top being made thicker to allow more copper to be placed.
Even using ALT and left button mouse click does not rotate through all possible selections and misses the dangling track.
Regards,
Richard. |
 |
|
|
AndyB
United Kingdom
208 Posts |
Posted - 31 Aug 2010 : 13:53:09
|
Had tried to unroute part net but crashed when design check was made.
Yes I had to unroute the net completely.
Thanks Shadders.
|
|
|
|
DavidM
United Kingdom
458 Posts |
Posted - 01 Sep 2010 : 10:53:13
|
If you run Design Rule Check and tick the box for 'Dangling Tracks', it should put an error marker on each dangling track it finds.
Then you can use the Goto bar, set the type to Error, and get a list of the errors. Double-clicking on any of them will take you to that error position on the design.
Or you could ignore the bar altogether and use the Next Error command (default shortcut T) to step through the errors, but I find using Goto is easier because you can pick and choose exactly which errors you need to hunt down.
Once you are over the error, you should be able to click to select the first item there, then use Select Next (default shortcut N) to cycle through selecting all the items at that location. I agree that finding these dangling bits can be hard sometimes, but this procedure generally works.
|
|
|
|
Peter Johnson
United Kingdom
498 Posts |
Posted - 03 Sep 2010 : 10:57:29
|
The classic 'invisible' dangling track is when you've been a littlec enthusiastic double clicking to end a track, and it's left a ridiculously small extra stub on the pad, often hidden by the wanted track, or even the pad itself.
If you can find it (and this can involve temporarily unrouting other track segments on the pad, then using 'undo') and highlight it, just right click and use 'Net', 'Unroute Track Segments' to remove it. It's safer than delete as you can't accidentally remove the wrong connection. The worst you'll do is unroute it! |
|
|
|
AndyB
United Kingdom
208 Posts |
Posted - 03 Sep 2010 : 13:47:04
|
Thanks for noting the DRC option. Will use this.
If Easy-pc manages to find the dangling tracks and has the facility tp point them out, could we not have an option for Easy-pc to list and delete them individually. |
|
|
|
davekelly
United Kingdom
28 Posts |
Posted - 07 Sep 2010 : 14:37:57
|
V14.
I am getting incredibly frustrated with these dangling tracks!
If a track goes through the middle of a pad, then why does it indicate it is dangling?
I have several where I have many pads in a straight line, all on the same net. Drawing a track from the first pad to the last through the others is clearly connected, yet I get dangling track errors. I have to keep unrouting, then drawing pad to pad. |
|
|
|
AndyB
United Kingdom
208 Posts |
Posted - 08 Sep 2010 : 13:47:15
|
| Dave, if you have a straight row unroute then autoroute the net. Its a quick clean up. |
|
|
|
edrees
United Kingdom
779 Posts |
Posted - 09 Sep 2010 : 09:46:22
|
Dave, Andy's suggestion only works if you have a netlist already created. If you are designing a pcb "on the fly" then you will have to click the track on each component node to make the net. Otherwise if you try selecting and dragging the track connecting point A to point E, (which is one track segment) all points B, C and D willl become disconnected.
I feel that this is how it should work, although back in the (not-so-good) days of sticky black tape, your method works. |
Edited by - edrees on 09 Sep 2010 13:25:34 |
|
|
|
Peter Johnson
United Kingdom
498 Posts |
Posted - 27 Sep 2010 : 15:10:47
|
quote:
Originally posted by davekelly
V14.
I am getting incredibly frustrated with these dangling tracks!
If a track goes through the middle of a pad, then why does it indicate it is dangling?
I have several where I have many pads in a straight line, all on the same net. Drawing a track from the first pad to the last through the others is clearly connected, yet I get dangling track errors. I have to keep unrouting, then drawing pad to pad.
Are you sure it's a dangling track error? I'd expect a T-P (track to pad) error where the track crosses an intermediate pad to which it's not connected. Dangling track should mean only one end of the track is connected to a recognised termination (pad, via, junction, etc.) |
|
|
| |
Topic |
|
Dangling Tracks