| www.delorie.com/archives/browse.cgi | search |
| X-Authentication-Warning: | delorie.com: mail set sender to geda-user-bounces using -f |
| X-Recipient: | geda-user AT delorie DOT com |
| DKIM-Signature: | v=1; a=rsa-sha256; c=relaxed/relaxed; |
| d=gmail.com; s=20120113; | |
| h=mime-version:in-reply-to:references:date:message-id:subject:from:to | |
| :content-type; | |
| bh=XBqMXytDiJx41V6hTrHgcPwHGwfZWtWnHO+J/uX/4mo=; | |
| b=vJZmGa8eq0DPM6ADlOUFfqOjNB2LWhJ65X3BjYTUk25wwYK5wroObfdqDeLnIta5hm | |
| QZ/u3uCA5AAb7HXIGjbofkYNxfcFII0w50EtcbDlBE8Naw5v7ZeI0T/OeKYemBt7Be/D | |
| xTx0OQPLntfRBJQ83fMapm4o/qyPrj4tpMx/o+rN9I0gtc50wObaBrYMTok/VpXpwLR1 | |
| U8kq9LgX0s14pTree2wQPWT2/xBa2wdTiO59JZ0qG1Vj2SgGJPZixdLutv+oIaVVkqnN | |
| L1h9zH2l7A+dX84irAPIKUukKekvBgPjCFVnqxZ/IyJBGZUozReVHoKBbmH2dwiJsdow | |
| iWEw== | |
| MIME-Version: | 1.0 |
| X-Received: | by 10.180.126.37 with SMTP id mv5mr6320057wib.2.1415039482431; |
| Mon, 03 Nov 2014 10:31:22 -0800 (PST) | |
| In-Reply-To: | <CAOFvGD5BGdfUKO+WhRjTZNGqYCEO2dNVCtKp4N2ZRNQ7Z2uLxQ@mail.gmail.com> |
| References: | <CAOFvGD5BGdfUKO+WhRjTZNGqYCEO2dNVCtKp4N2ZRNQ7Z2uLxQ AT mail DOT gmail DOT com> |
| Date: | Mon, 3 Nov 2014 10:31:22 -0800 |
| Message-ID: | <CAOP4iL3QzntprWs34R2hp6qeJmm6iuzA8caYKfFpo=7cXNFt6A@mail.gmail.com> |
| Subject: | Re: [geda-user] Eagle's XML Format -> gEDA Schematic/PCB? |
| From: | Ouabache Designworks <z3qmtr45 AT gmail DOT com> |
| To: | geda-user AT delorie DOT com |
| Reply-To: | geda-user AT delorie DOT com |
| Errors-To: | nobody AT delorie DOT com |
| X-Mailing-List: | geda-user AT delorie DOT com |
| X-Unsubscribes-To: | listserv AT delorie DOT com |
--e89a8f839d7db18feb0506f88d51 Content-Type: text/plain; charset=UTF-8 So I randomly picked one part from the pdf and found that it is contained in two separate sections in the xml file: <symbol name="TC4424AVPA"> <pin name="VDD" x="-17.78" y="7.62" length="middle" direction="pwr"/> <pin name="IN_A" x="-17.78" y="2.54" length="middle" direction="in"/> <pin name="IN_B" x="-17.78" y="0" length="middle" direction="in"/> <pin name="NC_2" x="-17.78" y="-5.08" length="middle" direction="nc"/> <pin name="NC" x="-17.78" y="-7.62" length="middle" direction="nc"/> <pin name="GND" x="-17.78" y="-12.7" length="middle" direction="pas"/> <pin name="OUT_A" x="17.78" y="7.62" length="middle" direction="out" rot="R180"/> <pin name="OUT_B" x="17.78" y="5.08" length="middle" direction="out" rot="R180"/> <wire x1="-12.7" y1="12.7" x2="-12.7" y2="-17.78" width="0.1524" layer="94"/> <wire x1="-12.7" y1="-17.78" x2="12.7" y2="-17.78" width="0.1524" layer="94"/> <wire x1="12.7" y1="-17.78" x2="12.7" y2="12.7" width="0.1524" layer="94"/> <wire x1="12.7" y1="12.7" x2="-12.7" y2="12.7" width="0.1524" layer="94"/> <text x="-4.0894" y="14.8844" size="2.0828" layer="95" ratio="10" rot="SR0">>NAME</text> <text x="-5.7912" y="-22.2504" size="2.0828" layer="96" ratio="10" rot="SR0">>VALUE</text> </symbol> and <deviceset name="TC4424AVPA"> <description>Dual High-Speed Power MOSFET Drivers</description> <gates> <gate name="A" symbol="TC4424AVPA" x="0" y="0"/> </gates> <devices> <device name="" package="DIP254P762X533-8"> <connects> <connect gate="A" pin="GND" pad="3"/> <connect gate="A" pin="IN_A" pad="2"/> <connect gate="A" pin="IN_B" pad="4"/> <connect gate="A" pin="NC" pad="8"/> <connect gate="A" pin="NC_2" pad="1"/> <connect gate="A" pin="OUT_A" pad="7"/> <connect gate="A" pin="OUT_B" pad="5"/> <connect gate="A" pin="VDD" pad="6"/> </connects> <technologies> <technology name=""> <attribute name="DESCRIPTION" value="MOSFET" constant="no"/> <attribute name="MPN" value="TC4424AVPA" constant="no"/> <attribute name="OC_FARNELL" value="1332308" constant="no"/> <attribute name="OC_NEWARK" value="34M8777" constant="no"/> <attribute name="PACKAGE" value="PDIP-8" constant="no"/> <attribute name="SUPPLIER" value="Microchip" constant="no"/> </technology> </technologies> </device> </devices> </deviceset> parsing this out would be easy enough and you could regurgitate it back out into a file named something like element13/MOSFET/TC4424AVPA/PDIP-8.sym Somebody will need to come up with an algorithm for the file name and how to map everything into geda format. John Eaton On Mon, Nov 3, 2014 at 9:47 AM, Jason White < whitewaterssoftwareinfo AT gmail DOT com> wrote: > Hello, I just recently learned that newer versions of Eagle use an > entirely XML based format for their Part Libraries as well as for > schematic pages and layouts. Has anyone been able to do anything with > this (maybe have written a script or something?) to allow gEDA to be > able to use the rather large component libraries that have been > produced and is freely distributed for Eagle? > > Take [1] for an example of such a library, it contains an enormous > number [>1000] of pre-made symbols and footprints. Element14 as well > as many others freely distribute part libraries to promote their > services. > > It would be a time saver to be able to use those libraries in gEDA > designs, either to extract individual symbols and packages, or perhaps > even to have something represent the entire library file as a > directory of symbols and footprints to gEDA. > > [1] > http://www.element14.com/community/servlet/JiveServlet/download/64255-1-101093/Microchip.zip > > Thanks, > Jason White > --e89a8f839d7db18feb0506f88d51 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr"><div>So I randomly picked one part from the pdf and found = that it is contained in two separate sections in the xml file:<br><br><br>&= lt;symbol name=3D"TC4424AVPA"><br><pin name=3D"VDD&quo= t; x=3D"-17.78" y=3D"7.62" length=3D"middle" = direction=3D"pwr"/><br><pin name=3D"IN_A" x=3D&qu= ot;-17.78" y=3D"2.54" length=3D"middle" direction= =3D"in"/><br><pin name=3D"IN_B" x=3D"-17.78&= quot; y=3D"0" length=3D"middle" direction=3D"in&qu= ot;/><br><pin name=3D"NC_2" x=3D"-17.78" y=3D&quo= t;-5.08" length=3D"middle" direction=3D"nc"/><b= r><pin name=3D"NC" x=3D"-17.78" y=3D"-7.62"= ; length=3D"middle" direction=3D"nc"/><br><pin na= me=3D"GND" x=3D"-17.78" y=3D"-12.7" length=3D= "middle" direction=3D"pas"/><br><pin name=3D"= ;OUT_A" x=3D"17.78" y=3D"7.62" length=3D"midd= le" direction=3D"out" rot=3D"R180"/><br><pin= name=3D"OUT_B" x=3D"17.78" y=3D"5.08" length= =3D"middle" direction=3D"out" rot=3D"R180"/&g= t;<br><wire x1=3D"-12.7" y1=3D"12.7" x2=3D"-12.= 7" y2=3D"-17.78" width=3D"0.1524" layer=3D"94= "/><br><wire x1=3D"-12.7" y1=3D"-17.78" x2= =3D"12.7" y2=3D"-17.78" width=3D"0.1524" laye= r=3D"94"/><br><wire x1=3D"12.7" y1=3D"-17.78= " x2=3D"12.7" y2=3D"12.7" width=3D"0.1524&quo= t; layer=3D"94"/><br><wire x1=3D"12.7" y1=3D"= ;12.7" x2=3D"-12.7" y2=3D"12.7" width=3D"0.15= 24" layer=3D"94"/><br><text x=3D"-4.0894" y= =3D"14.8844" size=3D"2.0828" layer=3D"95" rat= io=3D"10" rot=3D"SR0">&gt;NAME</text><br>&= lt;text x=3D"-5.7912" y=3D"-22.2504" size=3D"2.082= 8" layer=3D"96" ratio=3D"10" rot=3D"SR0"= >&gt;VALUE</text><br></symbol><br><br></div>and<br><br><= div><br><deviceset name=3D"TC4424AVPA"><br><description&= gt;Dual High-Speed Power MOSFET Drivers</description><br><gates>= ;<br><gate name=3D"A" symbol=3D"TC4424AVPA" x=3D&quo= t;0" y=3D"0"/><br></gates><br><devices><br>&l= t;device name=3D"" package=3D"DIP254P762X533-8"><br>= <connects><br><connect gate=3D"A" pin=3D"GND" = pad=3D"3"/><br><connect gate=3D"A" pin=3D"IN= _A" pad=3D"2"/><br><connect gate=3D"A" pin= =3D"IN_B" pad=3D"4"/><br><connect gate=3D"A&= quot; pin=3D"NC" pad=3D"8"/><br><connect gate=3D&= quot;A" pin=3D"NC_2" pad=3D"1"/><br><connect= gate=3D"A" pin=3D"OUT_A" pad=3D"7"/><br>&= lt;connect gate=3D"A" pin=3D"OUT_B" pad=3D"5"= /><br><connect gate=3D"A" pin=3D"VDD" pad=3D"= ;6"/><br></connects><br><technologies><br><technolog= y name=3D""><br><attribute name=3D"DESCRIPTION" v= alue=3D"MOSFET" constant=3D"no"/><br><attribute n= ame=3D"MPN" value=3D"TC4424AVPA" constant=3D"no&qu= ot;/><br><attribute name=3D"OC_FARNELL" value=3D"13323= 08" constant=3D"no"/><br><attribute name=3D"OC_NE= WARK" value=3D"34M8777" constant=3D"no"/><br>&l= t;attribute name=3D"PACKAGE" value=3D"PDIP-8" constant= =3D"no"/><br><attribute name=3D"SUPPLIER" value= =3D"Microchip" constant=3D"no"/><br></technology&= gt;<br></technologies><br></device><br></devices><br><= /deviceset><br><br><br></div><div>parsing this out would be easy enough = and you could regurgitate it back out into a file named=C2=A0 something lik= e element13/MOSFET/TC4424AVPA/PDIP-8.sym</div><div><br></div><div>Somebody = will need to come up with an algorithm for the file name and how to map eve= rything into geda format.<br><br></div><div>John Eaton<br><br><br></div><di= v><br><br></div></div><div class=3D"gmail_extra"><br><div class=3D"gmail_qu= ote">On Mon, Nov 3, 2014 at 9:47 AM, Jason White <span dir=3D"ltr"><<a h= ref=3D"mailto:whitewaterssoftwareinfo AT gmail DOT com" target=3D"_blank">whitewat= erssoftwareinfo AT gmail DOT com</a>></span> wrote:<br><blockquote class=3D"gma= il_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-lef= t:1ex">Hello, I just recently learned that newer versions of Eagle use an<b= r> entirely XML based format for their Part Libraries as well as for<br> schematic pages and layouts. Has anyone been able to do anything with<br> this (maybe have written a script or something?) to allow gEDA to be<br> able to use the rather large component libraries that have been<br> produced and is freely distributed for Eagle?<br> <br> Take [1] for an example of such a library, it contains an enormous<br> number [>1000] of pre-made symbols and footprints. Element14 as well<br> as many others freely distribute part libraries to promote their<br> services.<br> <br> It would be a time saver to be able to use those libraries in gEDA<br> designs, either to extract individual symbols and packages, or perhaps<br> even to have something represent the entire library file as a<br> directory of symbols and footprints to gEDA.<br> <br> [1] <a href=3D"http://www.element14.com/community/servlet/JiveServlet/downl= oad/64255-1-101093/Microchip.zip" target=3D"_blank">http://www.element14.co= m/community/servlet/JiveServlet/download/64255-1-101093/Microchip.zip</a><b= r> <br> Thanks,<br> Jason White<br> </blockquote></div><br></div> --e89a8f839d7db18feb0506f88d51--
| webmaster | delorie software privacy |
| Copyright © 2019 by DJ Delorie | Updated Jul 2019 |