Mail Archives: geda-user/2021/07/07/10:43:02
Stephen C. Menas:
...
> The substitute offered by Fedora (Kicad, I
> think) was not to my liking and there seemed to be no tools to port all
> my gschem schematic and symbol files to the Kicad platform. When I found
> that gschem support was revived, I was overjoyed.
...
pcb-rnd (http://repo.hu/projects/pcb-rnd/) can convert pcb files to
kicad.
I have a geda symbol -> kicad porting tool at:
http://aspodata.se/git/openhw/bin/sym2kicad.pl
> Finally, an offer. I have written a C program which I call "geda_parts".
> It reads a .sch file and creates an almost publishable parts list. For
> example: "geda_parts xxyy.sch R" would produce a file "xxyy_R.parts"
> which lists all the resistors in numerical order. This file is also useful
> for finding duplicated reference designators and holes in the reference
> designator sequence. It currently works for most of the common part types
> (resistors, capacitors, transistors, ICs, inductors, etc,). I have yet to
> make some modifications to handle multislot ICs and will probably do some
> more cleaning up but, if there is any interest, I can post the source
> once it is stable.
I have made a somewhat different choise. I don't really care about the
order R1 R2 ..., I'm more interested in: this roll of chip resistors
with value (e.g.) 33k, where do they go, then I take next roll, ...
So I'm more interested in sorting per: device, footprint, value, and
lastly, the refdes is just where theese go to. Also, I want the value
sorted so that 1p goes before 1n, which comes before 1u, 1m, 1, 1k, 1M
etc., just in the way my component rolls are sorted.
Do you have example output of your program so one can see if it does
what one wants?
///
I have:
http://aspodata.se/git/openhw/bin/GnetBom2.pl
it uses lepton-netlist or gnetlist (at your choise) and prettifies the
output. I.e., the netlister gives me:
$ head top.sch.list
refdes:device:footprint:value:qty
_M1:Connector:smarc_spec82x50.fp:MM70-314-310B1-2:1
_cQ1:TransistorNPN:sot23_to236.fp:BC817-40:1
_cR0,_cR1:Resistor:yageo_YC248r.fp:YC248 22:2
_cR2:Resistor:ipc7351b_1608Ar.fp:1M:1
_cR3,_p12Rt1,_p18Rt2:Resistor:ipc7351b_1608Ar.fp:100k:3
_cX1:Connector:Hirose_FH41-28S-0.5SH(05)_b.fp:FH41-28S-0.5SH(05):1
_cpU1,_dpU1:PowerDistSwitch:sot23_5.fp:TPS2051B:2
_dR1:Resistor:ipc7351b_1608Br.fp:10k:1
_dX1:Connector:amphenol_GSD0901xSEUr_1010.fp:GSD090012SEU:1
from which it then produces two versions which are easier on the eyes:
$ head top.sch.list1
device footprint value refdes
Capacitor ipc7351b_1608Ar.fp 10n _p18Cb1
Capacitor ipc7351b_1608Ar.fp 100n _dmC2
Capacitor ipc7351b_1608Ar.fp 100n _epC2
Capacitor ipc7351b_1608Ar.fp 100n _epC3
Capacitor ipc7351b_1608Ar.fp 100n _epC4
Capacitor ipc7351b_2012Ar.fp 330p _paC2
$ head top.sch.list2
device footprint value refdes
Capacitor ipc7351b_1608Ar.fp 10n 1 _p18Cb1
Capacitor ipc7351b_1608Ar.fp 100n 4 _dmC2 _epC2 _epC3 _epC4
Capacitor ipc7351b_2012Ar.fp 330p 1 _paC2
Capacitor ipc7351b_2012Ar.fp 1n 3 _elC1 _elC2 _elC3
Capacitor ipc7351b_2012Ar.fp 10n 1 _p2C2
Capacitor ipc7351b_2012Ar.fp 100n 3 _p12C2 _p3C2 _p5C2
Capacitor ipc7351b_2012Ar.fp 1u 7 _epC1 _p12C1 _p2C1 _p2C3 _p3C1 _p5C1 _paC1
Capacitor ipc7351b_3216Ar.fp 1n 1 _epC5
$
Regards,
/Karl Hammar
- Raw text -