David,
I found one interesting aspect to your query. I tried to check that
I could make vias all one specified size as you stated was desired or have
them show up in a DRC check. I tried to do it using the Routing Via style
size DRC.
Guess what, it doesn't work, contrary to the details stating that it
works for either online or manual DRC checks. I set a single via size within
the DRC scope and routed a segment of trace including two vias. Then I
changed one via to values outside the scope of the rule for both the via pad
size and the hole size. Nothing happened, ran the manual DRC nothing
happened. Obviously the routing via style DRC is broken.
Has anybody else ever seen this or reported it to Protel?
On your other queries, I don't think there is anyway to handle the rest of
them, definitely not the multiple selected component stepping, stub removal
I've not seen anything.
Redundant via removal, this is reported as a error in the Drill file
generation, I believe it shows in the DRR report. Removing them is a manual
process but the report outlines the coordinates of the locations at least.
Brad Velander,
Lead PCB Designer,
Norsat International Inc.,
#300 - 4401 Still Creek Dr.,
Burnaby, B.C., V5C 6G9.
Tel. (604) 292-9089 direct
Fax (604) 292-9010
website www.norsat.com
> -----Original Message-----
> From: David Cary [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, June 21, 2001 11:32 AM
> To: Protel EDA Forum
> Subject: [PEDA] enhancements:
>
> Dear PEDA users,
>
> Here's some stuff on my wish list. (Please tell me if Protel
> already does any of
> this stuff).
>
> ---
> Make vias identical.
> Normally I want every via to be identical hole size,
> identical annular ring,
> etc. (but different x,y locations and nets, of course).
> Can I set up a design rule to warn me about accidentally
> modified vias ?
> (If I wanted something different, I could work around that
> design rule by
> converting it into a pad).
>
> ----
> If I have 1 component selected, I can Jump to it (have it
> fill the screen) by
> hitting ``View | Selected Objects'' (or hitting the button
> that does the same
> thing).
>
> If I have several violations, I can Jump to them one at a
> time by selecting
> (under the ``Browse'' left side panel) ``Browse PCB | Browse
> | Violations'' and
> then, for each violation, select it under ``Violations'' and
> hit the ``Jump''
> button.
>
> Is there a way to jump to each selected component one at a
> time ? I'm imagining
> another option under ``Browse PCB | Browse | Selected'' to
> list all the selected
> stuff, and then I could (one at a time) pick one from a list
> and hit ``Jump''.
>
> ----
> Automatic Stub Removal:
> Sometimes I wish there were a way to select and delete
> ``unused stubs''. Say I
> move a component to the opposite side of the board. That
> usually leaves a lot of
> tracks that run to where the pads used to be. I don't need
> them any more.
> (Sometimes those stubs get deleted by Automatic Loop Removal
> when I re-route
> something nearby, but I can't seem to repeat that when I want to).
>
> --
> Automatic unused via removal:
> Somehow I end up with a lot of vias that don't ``do
> anything''. They might be
> connected to copper on the top layer, but they do not connect
> to any of the
> power planes or to any copper on any other layer. I want to
> select them and
> delete them.
>
> --
> Redundant via removal:
> The autorouter likes to pile several identical vias at the
> same x,y location. It
> looks OK on the screen, but some board houses complain about
> ``multiple drill
> hits''. I don't see any reason not to automatically delete
> identical vias when
> they're at the same x,y location.
>
> --
> David Cary
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* To post a message: mailto:[EMAIL PROTECTED]
*
* To leave this list visit:
* http://www.techservinc.com/protelusers/subscrib.html
* - or email -
* mailto:[EMAIL PROTECTED]?body=leave%20proteledaforum
*
* Contact the list manager:
* mailto:[EMAIL PROTECTED]
*
* Browse or Search previous postings:
* http://www.mail-archive.com/[email protected]
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
