| www.delorie.com/archives/browse.cgi | search |
--089e0149d164aa52700528a96863 Content-Type: text/plain; charset=UTF-8 On 6 Jan 2016 11:50, <gedau AT igor2 DOT repo DOT hu> wrote: > > I think this is a common misunderstanding. The reason PCB doesn't support burried/blind via is like 5% file format and 95% all-internal-code-in-pcb. (The 5-95 split is an educated guess, not a fact, but I believe it's not far from reality). The 95% includes everything from find.c and DRC to export HIDs and GUI HIDs. > > If we want blind/burried vias, we'll need to find how it is to be represented in a save file eventually, but the bulk of the work won't be around that part. Indeed, although it realistically isn't actally that huge a task from the data point of view. The most obvious missing thing I can see, is a physical layer stack model. Pcb layers don't explicitly map 1-1 to physical layers - and at the very least, we need to inforce a defined ordering of layer groups, before a to-from layer group notion makes sense. (I sort of did this in the 3D branch, but it needs to be more explicit). What may be a little harder, is updating the gui and renders to give a sensible interface for creating and editing this type of design feature. Since it blocks the 3D stuff, I'm taking an interest here (regarding more explicit board construction info / layer stack description), and I have plans to address this. I will also put my hand up to do the blind / buried vias, at least the back end part, and possibly a basic gui implementation in one HID - unless anyone is desperate to beat me to it! Peter --089e0149d164aa52700528a96863 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable <p dir=3D"ltr"><br> On 6 Jan 2016 11:50, <<a href=3D"mailto:gedau AT igor2 DOT repo DOT hu">gedau AT igor2= .repo.hu</a>> wrote:<br> ></p> <p dir=3D"ltr">> I think this is a common misunderstanding. The reason P= CB doesn't support burried/blind via is like 5% file format and 95% all= -internal-code-in-pcb. (The 5-95 split is an educated guess, not a fact, bu= t I believe it's not far from reality). The 95% includes everything fro= m find.c and DRC to export HIDs and GUI HIDs.<br> ><br> > If we want blind/burried vias, we'll need to find how it is to be = represented in a save file eventually, but the bulk of the work won't b= e around that part.<br></p> <p dir=3D"ltr">Indeed, although it realistically isn't actally that hug= e a task from the data point of view. The most obvious missing thing I can = see, is a physical layer stack model. Pcb layers don't explicitly map 1= -1 to physical layers - and at the very least, we need to inforce a defined= ordering of layer groups, before a to-from layer group notion makes sense.= (I sort of did this in the 3D branch, but it needs to be more explicit).</= p> <p dir=3D"ltr">What may be a little harder, is updating the gui and renders= to give a sensible interface for creating and editing this type of design = feature.</p> <p dir=3D"ltr">Since it blocks the 3D stuff, I'm taking an interest her= e (regarding more explicit board construction info / layer stack descriptio= n), and I have plans to address this.</p> <p dir=3D"ltr">I will also put my hand up to do the blind / buried vias, at= least the back end part, and possibly a basic gui implementation in one HI= D - unless anyone is desperate to beat me to it!</p> <p dir=3D"ltr">Peter<br> </p> --089e0149d164aa52700528a96863--
| webmaster | delorie software privacy |
| Copyright © 2019 by DJ Delorie | Updated Jul 2019 |