vRestrict layer and DRC

Am 16.03.2011 00:16, schrieb Bob Johnson:

I have a 4-layer board originally routed in Eagle V4 (Linux/Pro) that passed

ERC/DRC and went to production. It was discovered later that a connector had

issues (shorts) with vias under it. I'm now correcting that in V5.11.0

(Linux/Pro). I edited the connector symbol to include a vRestrict layer and

did a Library-Update All. The connector updated correctly and the vRestrict

layer now shows up as expected. Curiously, though, when I run DRC no errors

are flagged, even though nothing on the board changed except the connector

and the vias are still there, now clearly underneath the vRestrict layer.

 

I did a newsgroup search and the only possibility I saw was an issue with

blind vias. My stackup, however, is a simple (18+916) with no blind vias

defined. Is there some other setting I might be missing, or have I just run

into an Eagle bug?

Please read manual_en.pdf; page 148 == vRestrict:

Layer 43, vRestrict, is for drawing restricted areas where the

Autorouter or the Followme router may not set vias. Manually placed

vias in such a vRestrict region are not examined by the DRC and

therefore not reported as an error.

Mit freundlichen Grüßen / Best regards

Alfred Zaffran

--

_____________________________________________________________

Alfred Zaffran              Support

CadSoft Computer GmbH       Hotline:   08635-698930

Pleidolfweg 15              FAX:       08635-698940

84568 Pleiskirchen          eMail: <alf@cadsoft.de>

                             Web:   <www.cadsoft.de>

Registergericht: Amtsgericht Traunstein HRB 5573

Geschäftsführer: Dipl.-Ing. Klaus Schmidinger, Bodo Badnowitz

_____________________________________________________________

A. Zaffran wrote:

Am 16.03.2011 00:16, schrieb Bob Johnson:

>> I have a 4-layer board originally routed in Eagle V4 (Linux/Pro) that

>> passed ERC/DRC and went to production. It was discovered later that a

>> connector had issues (shorts) with vias under it. I'm now correcting that

>> in V5.11.0 (Linux/Pro). I edited the connector symbol to include a

>> vRestrict layer and did a Library-Update All. The connector updated

>> correctly and the vRestrict layer now shows up as expected. Curiously,

>> though, when I run DRC no errors are flagged, even though nothing on the

>> board changed except the connector and the vias are still there, now

>> clearly underneath the vRestrict layer.

>>

>> I did a newsgroup search and the only possibility I saw was an issue with

>> blind vias. My stackup, however, is a simple (18+916) with no blind

>> vias defined. Is there some other setting I might be missing, or have I

>> just run into an Eagle bug?

 

Please read manual_en.pdf; page 148 == vRestrict:

 

Layer 43, vRestrict, is for drawing restricted areas where the

Autorouter or the Followme router may not set vias. Manually placed

vias in such a vRestrict region are not examined by the DRC and

therefore not reported as an error.

 

 

Mit freundlichen Grüßen / Best regards

 

Alfred Zaffran

Right you are. I was looking in the online help, where vRestrict is referred

to as 'Nogo areas for via-holes', similar to tKeepout being 'Nogo areas for

components, top side'. The latter does get a DRC warning when violated.

Maybe the former description should include '(auto-router only)'. Anyway,

thanks for clarifying the issue.

A. Zaffran wrote:

Am 16.03.2011 00:16, schrieb Bob Johnson:

>> I have a 4-layer board originally routed in Eagle V4 (Linux/Pro) that

>> passed ERC/DRC and went to production. It was discovered later that a

>> connector had issues (shorts) with vias under it. I'm now correcting that

>> in V5.11.0 (Linux/Pro). I edited the connector symbol to include a

>> vRestrict layer and did a Library-Update All. The connector updated

>> correctly and the vRestrict layer now shows up as expected. Curiously,

>> though, when I run DRC no errors are flagged, even though nothing on the

>> board changed except the connector and the vias are still there, now

>> clearly underneath the vRestrict layer.

>>

>> I did a newsgroup search and the only possibility I saw was an issue with

>> blind vias. My stackup, however, is a simple (18+916) with no blind

>> vias defined. Is there some other setting I might be missing, or have I

>> just run into an Eagle bug?

 

Please read manual_en.pdf; page 148 == vRestrict:

 

Layer 43, vRestrict, is for drawing restricted areas where the

Autorouter or the Followme router may not set vias. Manually placed

vias in such a vRestrict region are not examined by the DRC and

therefore not reported as an error.

 

 

Mit freundlichen Grüßen / Best regards

 

Alfred Zaffran

Right you are. I was looking in the online help, where vRestrict is referred

to as 'Nogo areas for via-holes', similar to tKeepout being 'Nogo areas for

components, top side'. The latter does get a DRC warning when violated.

Maybe the former description should include '(auto-router only)'. Anyway,

thanks for clarifying the issue.