| ID: | 710 |
| From: | John Griessen <jo...@cibolo.com> |
| Date: | Tue, 30 May 2017 10:54:09 -0500 |
| Subject: | Re: [pcb-rnd] up next: subcircuits (a.k.a. footprint model redesign) |
| in-reply-to: | 709 from ge...@igor2.repo.hu |
| replies: | 711 from ge...@igor2.repo.hu |
On 05/30/2017 07:21 AM, gedau@igor2.repo.hu wrote: > Long term we are going to replace the whole DRC. We already have big parts of that code in production (for the advanced search). > Such drc scripts will have no problem understanding an antenne loop. > > Short term we can add a temporary "no-drc" flag to one of the objects consisting the loop. There is still some thinking of how to netlist it needed. Subcircuits can be used to repeat wanted layouts in multi channel amps for instance, and then the DRC needs to go into the subcircuit to work as intended. Whether to "go into" a subcircuit is going to be a decision of the user more than a heuristic choice by pcb-rnd. Unless you have more AI smarts planned that I imagine. Subcircuits with more generic layout in them seem to demand that internal nets are brought up to the next higher level when they involve solid connections of copper trace, and so why not DRC those as usual and update the top netlist to work with all the lower level parts up until you get to components that are a black box. Black box components are not treated as a short, and only checked that they are hooked up in correct pin order to other Black box components via the netlist. The new thing here is a subcircuit is not always a black box, but can be either that old way, or a circuit that causes some connectivity changes at the next level up from it. -- John Griessen cibolo.com Austin TX building lab gear for biologists
Reply subtree:
710 Re: [pcb-rnd] up next: subcircuits (a.k.a. footprint model redesign) from John Griessen <jo...@cibolo.com>
711 Re: [pcb-rnd] up next: subcircuits (a.k.a. footprint model from ge...@igor2.repo.hu
712 Re: [pcb-rnd] up next: subcircuits (a.k.a. footprint model redesign) from John Griessen <jo...@cibolo.com>