Mail Archives: geda-help/2014/09/21/11:11:58
--047d7bdca51e09f3d7050394bf18
Content-Type: text/plain; charset=UTF-8
Hmm, the gnetlist eagle export looked so real too... shame. I would think
its not too hard to do since eagle seems to have a scripting language but
damn is thier documentation rubbish.
What tool chain do you use togenerate something PADs like? I think tht
could work for me.
On Sep 19, 2014 10:19 PM, "Bernd Walter" <ticso AT cicely7 DOT cicely DOT de> wrote:
> On Sat, Sep 20, 2014 at 03:47:13AM +0200, Peter Stuge wrote:
> > vattan wrote:
> > > send files to someone who is not using gEDA, they have Altium and
> Eagle etc.
> > > I assume Eagle would be the easiest to export to
> >
> > Interchangeability of working files is not a strong point of any EDA
> > software, also not gEDA. Noone uses it much and it's low priority.
> >
> > I'd say your only chance is to use the common export formats; like
> > gerber and png. Of course Altium or Eagle can't work with them.
> >
> > I'm afraid you are a few decades too early.
>
> Easiest would be to have that someone install gEDA, because unlike
> Eagle and Altium gEDA is completely free and not picky about the
> OS and CPU architecture.
> It is even possible to use a cheap Raspberry PI to run gEDA.
> I know that Eagle has a limited costless version and Altium recently
> annouced something similar, but still those are binaries for specific
> systems only and limited in functionality.
>
> > > Does anyone have any insight here?
> >
> > Road untraveled, noone has invested resources into making it smooth,
> > it is very bumpy. A detour will save you time in the end, unless you
> > want to invest significant resources in paving the road before you
> > can travel it.
>
> Automatic conversion might even be impossible because features can be
> different.
> For example with QFN center pad I use a non paste pad overlayed with small
> paste pads to reduce paste amount.
> This might not be possible to do this way with other software, but other
> software likely have solutions for this in another way.
> On the other hand you can't just switch component foorprints to native
> library versions, because of naming and detail size differences.
> Even if you have a tool you can't expect it to do the complete conversion
> without help.
>
> In every converion case I know the projects had been recreated.
> With board layouts it turned out to be best to have a JPEG or something
> like this in background to redraw the copper on top of it.
>
> --
> B.Walter <bernd AT bwct DOT de> http://www.bwct.de
> Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm.
>
--047d7bdca51e09f3d7050394bf18
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<p>Hmm, the gnetlist eagle export looked so real too... shame.=C2=A0 I woul=
d think its not too=C2=A0 hard to do since eagle seems to have a scripting =
language but damn is thier documentation rubbish.<br>
What tool chain do you use togenerate something=C2=A0 PADs like? I think th=
t could work for me.</p>
<div class=3D"gmail_quote">On Sep 19, 2014 10:19 PM, "Bernd Walter&quo=
t; <<a href=3D"mailto:ticso AT cicely7 DOT cicely DOT de" target=3D"_blank">ticso AT c=
icely7.cicely.de</a>> wrote:<br type=3D"attribution"><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex">On Sat, Sep 20, 2014 at 03:47:13AM +0200, Peter Stuge wrote:<=
br>
> vattan wrote:<br>
> > send files to someone who is not using gEDA, they have Altium and=
Eagle etc.<br>
> > I assume Eagle would be the easiest to export to<br>
><br>
> Interchangeability of working files is not a strong point of any EDA<b=
r>
> software, also not gEDA. Noone uses it much and it's low priority.=
<br>
><br>
> I'd say your only chance is to use the common export formats; like=
<br>
> gerber and png. Of course Altium or Eagle can't work with them.<br=
>
><br>
> I'm afraid you are a few decades too early.<br>
<br>
Easiest would be to have that someone install gEDA, because unlike<br>
Eagle and Altium gEDA is completely free and not picky about the<br>
OS and CPU architecture.<br>
It is even possible to use a cheap Raspberry PI to run gEDA.<br>
I know that Eagle has a limited costless version and Altium recently<br>
annouced something similar, but still those are binaries for specific<br>
systems only and limited in functionality.<br>
<br>
> > Does anyone have any insight here?<br>
><br>
> Road untraveled, noone has invested resources into making it smooth,<b=
r>
> it is very bumpy. A detour will save you time in the end, unless you<b=
r>
> want to invest significant resources in paving the road before you<br>
> can travel it.<br>
<br>
Automatic conversion might even be impossible because features can be<br>
different.<br>
For example with QFN center pad I use a non paste pad overlayed with small<=
br>
paste pads to reduce paste amount.<br>
This might not be possible to do this way with other software, but other<br=
>
software likely have solutions for this in another way.<br>
On the other hand you can't just switch component foorprints to native<=
br>
library versions, because of naming and detail size differences.<br>
Even if you have a tool you can't expect it to do the complete conversi=
on<br>
without help.<br>
<br>
In every converion case I know the projects had been recreated.<br>
With board layouts it turned out to be best to have a JPEG or something<br>
like this in background to redraw the copper on top of it.<br>
<br>
--<br>
B.Walter <<a href=3D"mailto:bernd AT bwct DOT de" target=3D"_blank">bernd AT bwct.=
de</a>> <a href=3D"http://www.bwct.de" target=3D"_blank">http://www.bwct=
.de</a><br>
Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm.<br>
</blockquote></div>
--047d7bdca51e09f3d7050394bf18--
- Raw text -