Thank you for the exhaustive answer! /sza2
John Doty wrote: > No, but there are lots of ways to do this. In some designs, I have a > gain adjustment resistor. In most cases it should be left out, so it > has "value=omit". Something like "value=330, not mounted" is > perfectly legal from the gschem/gnetlist perspective. What happens > down the road depends on your back end(s). > > You are perfectly free to make up your own attributes. I have things > like "spec=25WVDC, X7R". List "spec" in your attribs file, and > "gnetlist -g bom" will pick it up. So, make up an "instructions" > attribute if you like. > > Rough edges: > > The tools complain about empty attribute strings, and make them > difficult to create. Why? An empty string is a perfectly good > attribute for some purposes. > > Unknown attributes for a symbol instance show up as "unknown" in the > BOM. Sometimes this is wanted, others not, especially in the case of > custom attributes. This is another place where the project symbol > directory approach comes to the rescue, because your project's > symbols can contain defaults for your project's custom attributes, > saving you from having to attach one to every instance. > > John Doty Noqsi Aerospace, Ltd. > http://www.noqsi.com/ > [email protected] > > > > > _______________________________________________ > geda-user mailing list > [email protected] > http://www.seul.org/cgi-bin/mailman/listinfo/geda-user > > _______________________________________________ geda-user mailing list [email protected] http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
