Mail Archives: geda-user/2015/10/04/22:30:45.1
--047d7b5d9c073a16c20521524ac0
Content-Type: text/plain; charset=UTF-8
On Sun, Oct 4, 2015 at 4:09 PM, John Griessen <john AT ecosensory DOT com> wrote:
> On 10/04/2015 06:55 PM, John Griessen wrote:
>
>> One way to do a workflow for an autorouter would be to export an outline
>> of the area to route up to, including some metal layer pieces with
>> netnames
>> to connect to, and all components
>>
>
>
> On second thought, that is probably too much for an external tool to do.
> So the external tool doesn't need to know footprints, just export the
> pins with netnames attached and let the router go,
> then import all except pins. That's all the same result when the router
> never
> moves footprints.
>
> A router that works inside the layout program could do more. Imagine tell
> it
> a gravity direction, have some parts placed and routed, or just marked as
> "hand routed", and power busses placed, then let the router pour circuitry
> into the shape defined by the board outline, and already placed circuitry.
>
It might not have to be inside pcb to do this, it would just need to be
able to read the file format. Keep-outs of this sort are pretty straight
forward with the topo-router I think. Being in pcb or having some render
capability might be nice if you want to cheat and make the cost function a
little bit interactive. But generally its not an interactive algorithm,
nothing like push-shove at all.
--047d7b5d9c073a16c20521524ac0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quo=
te">On Sun, Oct 4, 2015 at 4:09 PM, John Griessen <span dir=3D"ltr"><<a =
href=3D"mailto:john AT ecosensory DOT com" target=3D"_blank">john AT ecosensory DOT com</=
a>></span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0=
0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=3D"">On =
10/04/2015 06:55 PM, John Griessen wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
One way to do a workflow for an autorouter would be to export an outline<br=
>
of the area to route up to, including some metal layer pieces with netnames=
<br>
to connect to, and all components<br>
</blockquote>
<br>
<br></span>
On second thought, that is probably too much for an external tool to do.<br=
>
So the external tool doesn't need to know footprints, just export the<b=
r>
pins with netnames attached and let the router go,<br>
then import all except pins.=C2=A0 That's all the same result when the =
router never<br>
moves footprints.<br>
<br>
A router that works inside the layout program could do more.=C2=A0 Imagine =
tell it<br>
a gravity direction, have some parts placed and routed, or just marked as<b=
r>
"hand routed", and power busses placed, then let the=C2=A0 router=
pour circuitry<br>
into the shape defined by the board outline, and already placed circuitry.<=
br></blockquote><div><br></div><div style=3D"">It might not have to be insi=
de pcb to do this, it would just need to be able to read the file format. K=
eep-outs of this sort are pretty straight forward with the topo-router I th=
ink.=C2=A0 Being in pcb or having some render capability might be nice if y=
ou want to cheat and make the cost function a little bit interactive.=C2=A0=
But generally its not an interactive algorithm, nothing like push-shove at=
all.</div><div>=C2=A0</div></div></div></div>
--047d7b5d9c073a16c20521524ac0--
- Raw text -