Topic for #qi-hardware is now Copyleft hardware - http://qi-hardware.com | hardware hackers join here to discuss Ben NanoNote, atben / atusb 802.15.4 wireless, and other community driven hw projects | public logging at http://en.qi-hardware.com/irclogs
<qi-bot>
[commit] Werner Almesberger: genex: added reading of files containing supplemental descriptions (master) http://qi-hw.com/p/eda-tools/1b7ace9
<qi-bot>
[commit] Werner Almesberger: genex/genex.c: new option -d to dump the tree instead of making a PDF (master) http://qi-hw.com/p/eda-tools/904a60f
<qi-bot>
[commit] Werner Almesberger: genex/pdf.c: changed page orientation from landscape to portrait (master) http://qi-hw.com/p/eda-tools/8e8a3c5
jekhor has joined #qi-hardware
Ayla has joined #qi-hardware
jekhor has joined #qi-hardware
<wpwrak>
hmm. debugging code written while with the flu is fun. 1-2 days of coding, twice that time debugging :-(
Ayla has joined #qi-hardware
Ayla has joined #qi-hardware
rejon has joined #qi-hardware
Ayla has joined #qi-hardware
<qi-bot>
[commit] Werner Almesberger: genex: generate PDF by default; new option -P to generate Postscript (master) http://qi-hw.com/p/eda-tools/f8e10b3
<qi-bot>
[commit] Werner Almesberger: genex: changed default orientation back to landscape; option -p for portrait (master) http://qi-hw.com/p/eda-tools/0565adf
<wpwrak>
the components that begin with a ~ still cause trouble. the ~ seems to do something magic. need to find out what ...
<cladamw>
wpwrak, nice !!!
<cladamw>
"~" for pin name or Component Name / Value ?
<wpwrak>
strangely for the component name
<wpwrak>
i think ~ in a pin name means overstrike
<wpwrak>
but you shouldn't use that. it just created names you can't express in ASCII
<cladamw>
seems that a rough hierarchical structure proposed now. :-)
<wpwrak>
ah, maybe it means "invisible:
<cladamw>
"~" in KiCad is for low level active.
<cladamw>
I like that '~' but it's bad in ASCII paradise ,you can see ADV7181C, there's few "~" to stand for pins function. :-)
<wpwrak>
yes, in pins. inverted.
<wpwrak>
i would just use nNAME
<wpwrak>
that is perfect ASCII _AND_ you can use it in code for identifiers
<wpwrak>
names that contain special characters (/, #, etc.) can't be used directly in code. so you get things like #FOO in the schematics but the code calls it something like nFOO
<cladamw>
oh~ i just see "~TESTPOINT" which is you're talking
<qi-bot>
[commit] Werner Almesberger: genex/sym2xps: also accept components names beginning with ~ (master) http://qi-hw.com/p/eda-tools/7de800e
<qi-bot>
[commit] Werner Almesberger: genex/expand-pintype: preserve a tile at the beginning of a component name (master) http://qi-hw.com/p/eda-tools/3703852
<wpwrak>
regarding the hierarchy, we may have to rearrange things a few times before we have a good hierarchy
<wpwrak>
but that's now pretty easy. you just move the component around in EXPAND and the rest is automatic
<wpwrak>
we have a few things under "Vendor" that are in truth generic components, and should go there
<cladamw>
let me see EXPAND a little. :-)
<wpwrak>
also, some of the components in the generic tree should also have a name that describes them, not just a part number. e.g., FSMRA2JH
<wpwrak>
the names in EXPAND are case-insensitive. so i sometimes used upper case, sometimes lower case. not sure if this is actually a good idea. maybe i'll change it :)
<cladamw>
EXPAND is a folder or file ?
<wpwrak>
a text file
<cladamw>
not for a real part number, yeah... some of them should be a generic name
<cladamw>
wpwrak, arh... sorry. forget it. I understand now. :-)
<wpwrak>
i still need to do a few more things to make it a bit more user-friendly, though
<wpwrak>
particularly the installation. else, it can't find its scripts and gets a little confused
<cladamw>
wpwrak, so currently i don't need to appendix in EXPAND file once I create a new symbol now ? All that EXPAND file created by your genex tool, right ?
<wpwrak>
no, EXPAND is an input for genex
<wpwrak>
EXPAND tells it what hierarchy we want
<wpwrak>
so it would be good if you could add new things also to EXPAND
<wpwrak>
i should probably make a script that finds them automatically
Ayla has joined #qi-hardware
<wpwrak>
genex can also include comments. there's an example on the WM9707SCFT/V
<cladamw>
not sure if xiangfu/me will add more symbols or not, but i think just few. so genex is under eda-tools, do i need to be the member under eda-tools, should i ? don't know. :-)
<wpwrak>
to use, you don't need to be a member. if you think you'll need to edit something over there, i'll add you
<cladamw>
(comments) yes, i saw it.
<cladamw>
(member) i think no need now. :)
<cladamw>
what's the real goal for the info of "comments" from /genex/DESC ?
<cladamw>
just a rough/briefly description for component ?
<wpwrak>
i would use it to indicate the maturity of a component. e.g., "used in schematics", "used in schematics for which a layout has been made", "used in schematics from which a working device has been built'
<wpwrak>
and perhaps also list reviews
<cladamw>
how about extract those info from Properties from *.dcm ? some of them I filled up in Descriptions within its Properties. :-)
<wpwrak>
it could also contain a description of the component. e.g., the information you've put in the .dcm files. it shouldn't be hard to extract it from there
<wpwrak>
i'd just use the description from there. not add more to .dcm. .dcm isn't convenient to maintain
<cladamw>
nice, we are in the same page on *.dcm :-)
<wpwrak>
e.g., if you build a new board, you'd have to update the maturity of dozens of components. you don't want to have to edit all those .dcm files ;-)
<cladamw>
okay. so the goals for "comment" are for e.g., "used in schematics", "used in schematics for which a layout has been made", "used in schematics from which a working device has been built' <<< got it.
xiangfu has joined #qi-hardware
<wpwrak>
we should find short words for that. e.g., "DRAFT" for anything that hasn't been used yet, maybe "USED" if it has been used in schematics, not even sure if we need a separate category for layout (i gave that only as an example), and maybe "TESTED" if we have a working circuit
<cladamw>
this sort of like warehouse(parts) management to let user known which parts are 'used' and 'recommended' a bit. And easy to maintain warehouse. :-)
<wpwrak>
or maybe instead of "TESTED", the name of the circuit. that would be useful in case that circuit doesn't need all the pins
<wpwrak>
yes, and to indicate how much they can trust a component :)
<wpwrak>
in the kicad sense, i.e., "symbol"
<wpwrak>
unless we've built a device, there could be all sort of bugs. particularly in the smaller components. SOT-23 with the wrong numbers and such :)
<cladamw>
okay... in my mind. they are "USED in m1r4", "USED in avt2, atben, atusb"
<wpwrak>
some if the old ones were even TESTED in a number of projects :)
<cladamw>
we should use parts as commodity rather than added interminable components future.
<wpwrak>
lemme add a few of my experimental parts ...
<cladamw>
yeah...this info is good for users.
jekhor has joined #qi-hardware
<cladamw>
but like i said that even the tools are great, but we should not have info to let user feeling that parts can be added forever, we want those common parts as possible. well ... even parts are depends on applications though. :-)
<wpwrak>
btw, i think you need to commit bnc.lib
<cladamw>
yeah.... but since I found that symbol i built is actually a RCA symbol, so i removed bnc symbol there. :-)
<cladamw>
once someone build a board with BNC then copy it from KiCad's system lib. :-)
<cladamw>
wpwrak, i need go out now. night ~
<wpwrak>
ah, then i'll remove bnc.lib gfrom the .pro
<qi-bot>
[commit] Werner Almesberger: genex/: "genex" is now a wrapper that sets PATH, then calls genex-bin (master) http://qi-hw.com/p/eda-tools/fff142c
<qi-bot>
[commit] Werner Almesberger: genex: added install/uninstall targets and wrapper generator (master) http://qi-hw.com/p/eda-tools/54ecc10
losinggeneration has joined #qi-hardware
wolfspraul has joined #qi-hardware
<wpwrak>
projects.qi-hardware.com down ?
panda|x201 has joined #qi-hardware
<mth>
wpwrak: it won't load for me either (DNS works, timeout on HTTP)
<wpwrak>
wolfspraul: are you "playing" ? :)
<wolfspraul>
hmm
<wolfspraul>
alright :-)
qi-bot has joined #qi-hardware
<wpwrak>
thanks ! :)
<qi-bot>
[commit] Werner Almesberger: components/: added dual_trans.lib, with pre-biased Panasonic XP series BJTs (master) http://qi-hw.com/p/kicad-libs/95b8394
<qi-bot>
[commit] Werner Almesberger: components/: components from wernermisc/labsw (opto-couplers, a relay) (master) http://qi-hw.com/p/kicad-libs/d13404a
<qi-bot>
[commit] Werner Almesberger: components/: components from ben-wpan (antenna, xtal, AT86RF23x, and balun) (master) http://qi-hw.com/p/kicad-libs/b68ddec