Re: gEDA-user: RFC: Towards a better symbol/package pin-mapping strategy
Steven Michalske writes:
> pick a small set of some chips you care about. lets say a large
> family of the AVR series.
>
> To the symbol:
> Add a virtual pin attribute
> Add the pin map file attribute.
> pinmap=ATmega16.fpm
> device=ATmega16
> footprint=TQFP44_10
> {
And then offer a GUI to select from the list of footprints within
gschem.
Stephan
___
geda-user mailing list
geda-user@moria.seul.org
http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: Changing grids in pcb
Yes, we can certainly re-use old actions with new parameters, if it makes sense, or a single new action with multiple parameter options. We can use the words "next" and "previus" or "up" and "down" instead of numeric values, too. ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: Changing grids in pcb
On Jun 29, 2009, at 6:28 PM, DJ Delorie wrote:
>
>> Wouldn't you just use set grid with the -+ for increment and process
>> units?
>
> No. If you had a list of grid settings you used, then +- means
> stepping through the list, not arithmetic changes. Consider my grid
> choices:
>
>{ "0.1 mil" checked=gridsize,10 SetUnits(mil) SetValue(Grid,10)}
>{ "1 mil" checked=gridsize,100 SetUnits(mil) SetValue(Grid,
> 100) an={"G1" "g1"}}
>{ "5 mil" checked=gridsize,500 SetUnits(mil) SetValue(Grid,
> 500) an={"G2" "g2"}}
>{ "6.25 mil" checked=gridsize,625 SetUnits(mil) SetValue(Grid,
> 625) an={"G3" "g3"}}
>{ "10 mil" checked=gridsize,1000 SetUnits(mil) SetValue(Grid,
> 1000) an={"G4" "g4"}}
>{ "12.5 mil" checked=gridsize,1250 SetUnits(mil) SetValue(Grid,
> 1250) an={"G5" "g5"}}
>{ "25 mil" checked=gridsize,2500 SetUnits(mil) SetValue(Grid,
> 2500) an={"G6" "g6"}}
>{" 50 mil" checked=gridsize,5000 SetUnits(mil) SetValue(Grid,
> 5000) an={"G7" "g7"}}
>{"100 mil" checked=gridsize,1 SetUnits(mil) SetValue(Grid,
> 1) an={"G8" "g8"}}
>
> There's no math that will get you through that list reliably.
>
> Plus, the other problem is changing the mapped actions according to
> the inch/mm setting.
>
I Must have not been clear, I did not mean to do math to set grid
sizes, but only to add one action that uses our standard +/- value,
unit notation,
as described at the beginning of Appendix F
not to have three new actions.
But i think i see where your coming from, up is the next larger and
down is the next smaller grid size in the list, I had read up/down as
increment/decrement
>
> ___
> geda-user mailing list
> geda-user@moria.seul.org
> http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
___
geda-user mailing list
geda-user@moria.seul.org
http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: Changing grids in pcb
> Wouldn't you just use set grid with the -+ for increment and process
> units?
No. If you had a list of grid settings you used, then +- means
stepping through the list, not arithmetic changes. Consider my grid
choices:
{ "0.1 mil" checked=gridsize,10 SetUnits(mil) SetValue(Grid,10)}
{ "1 mil" checked=gridsize,100 SetUnits(mil) SetValue(Grid,100) an={"G1"
"g1"}}
{ "5 mil" checked=gridsize,500 SetUnits(mil) SetValue(Grid,500) an={"G2"
"g2"}}
{ "6.25 mil" checked=gridsize,625 SetUnits(mil) SetValue(Grid,625)
an={"G3" "g3"}}
{ "10 mil" checked=gridsize,1000 SetUnits(mil) SetValue(Grid,1000)
an={"G4" "g4"}}
{ "12.5 mil" checked=gridsize,1250 SetUnits(mil) SetValue(Grid,1250)
an={"G5" "g5"}}
{ "25 mil" checked=gridsize,2500 SetUnits(mil) SetValue(Grid,2500)
an={"G6" "g6"}}
{" 50 mil" checked=gridsize,5000 SetUnits(mil) SetValue(Grid,5000)
an={"G7" "g7"}}
{"100 mil" checked=gridsize,1 SetUnits(mil) SetValue(Grid,1)
an={"G8" "g8"}}
There's no math that will get you through that list reliably.
Plus, the other problem is changing the mapped actions according to
the inch/mm setting.
___
geda-user mailing list
geda-user@moria.seul.org
http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: Changing grids in pcb
On Jun 29, 2009, at 6:01 PM, DJ Delorie wrote: > >> a) The same grid accels, for metric and for imperial units. >> >> b) A configurable list of grid values rather than a fixed increment. >> >> c) Grid and display units should be set independently. That is, it >> should >> be possible to work with an imperial grid while display units are >> metric. >> >> Any comments? >> Would it be hard to implement this? > > Sounds like fun. You'd need a way to custom-generate the menu, as the > [g]pcb-menu.res currently hard-codes them. Also new actions that do > up/down/set grid. > > Wouldn't you just use set grid with the -+ for increment and process units? :setGrid( -.05 mm ) :setGrid( 1 mm ) :setGrid( 10 mil ) > > ___ > geda-user mailing list > geda-user@moria.seul.org > http://www.seul.org/cgi-bin/mailman/listinfo/geda-user ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: Changing grids in pcb
> a) The same grid accels, for metric and for imperial units. > > b) A configurable list of grid values rather than a fixed increment. > > c) Grid and display units should be set independently. That is, it should > be possible to work with an imperial grid while display units are metric. > > Any comments? > Would it be hard to implement this? Sounds like fun. You'd need a way to custom-generate the menu, as the [g]pcb-menu.res currently hard-codes them. Also new actions that do up/down/set grid. ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
gEDA-user: Changing grids in pcb
Hi. I am not quite happy with the way different grid sizes are chosen in pcb. It comes down to two issues: 1) key accels depend on the current metric/imperial setting. Why is this so? With metric units I have to add the CTRL key to the accels for imperial. To decrement a metric grid amounts to a three finger trick: [CTRL-SHIFT-g]. This is a pain for such an often used feature. 2) The decrement/increment is fixed along the whole range of possible sizes. However, sensible grid sizes are more like 0.1 mm, 0.25mm, 0.5mm, 1mm, 2.5mm, 5mm, 10mm. This way, it takes much less effort to change from 0.25mm to 5mm. By the way, the GTK-GUI contains a field to set the grid increment that doesn't work. Grid increment is 0.05mm, no matter what. There is this minor twitch: If the setting is metric on start-up, the grid increments by imperial amounts. Yet, they are reported in metric units. Suggestions: a) The same grid accels, for metric and for imperial units. b) A configurable list of grid values rather than a fixed increment. c) Grid and display units should be set independently. That is, it should be possible to work with an imperial grid while display units are metric. Any comments? Would it be hard to implement this? ---<(kaimartin>)--- -- Kai-Martin Knaak Öffentlicher PGP-Schlüssel: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x6C0B9F53 ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: Change PCB keystrokes
Okay. Although, I am a complete newbie; I hardly use my terminal on my mac :| Could you sort of walk me through the steps of deleting local configuration files? Afterwards would I reinstall geda-bundle? Thanks On Jun 29, 2009, at 5:19 PM, Stefan Salewski wrote: > On Mon, 2009-06-29 at 16:48 +0200, Irena Hwang wrote: > >> completely awry. I would greatly appreciate any input at all on >> fixing this problem. >> > > Can talk about Linux only: > I a program does not work properly it may be a solution to delete the > local configuration files -- > > ste...@amd64-x2 ~ $ cd > ste...@amd64-x2 ~ $ ls -la > > drwxr-xr-x 3 stefan stefan 4096 May 24 23:20 .pcb > > ste...@amd64-x2 ~ $ rm -r .pcb > > > > > > ___ > geda-user mailing list > geda-user@moria.seul.org > http://www.seul.org/cgi-bin/mailman/listinfo/geda-user ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: funny gnetlist warning
On Jun 29, 2009, at 11:01 AM, Kai-Martin Knaak wrote: > On Fri, 26 Jun 2009 15:32:05 +0200, Duncan Drennan wrote: > >>> CONN1: need new file element for footprint PLUGCON_383_2PIN >>> (value=RIA_connect) >>> Warning: argument passing may have been confused by >>> a comma in a component value: >> >> Have you tried taking the underscore out of the value? > > No. And I don't wish to, too. > Due to the gnetlists infamous misinterpretation of hyphens as m4 > code I > already restricted my library to upper case letters, numbers and > underscore. Footprint names would be a lot less human readable if > underscores were also excluded. NeverFightTheTool ;-) > > IMHO the netter way to deal with the sirtuation would be a more robust > parsing of names, rather than spam stdout with warnings. > > ---<(kaimartin)>--- > -- > Kai-Martin Knaak > Öffentlicher PGP-Schlüssel: > http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x6C0B9F53 > > > > ___ > geda-user mailing list > geda-user@moria.seul.org > http://www.seul.org/cgi-bin/mailman/listinfo/geda-user John Doty Noqsi Aerospace, Ltd. http://www.noqsi.com/ j...@noqsi.com ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: cylindrical SMT power resistor pad design: how to do a semi-circular cutout
On Jun 28, 2009, at 7:55 PM, Kai-Martin Knaak wrote: > inkscape > --> draw with real semicircle circle > --> save as eps (uncheck "make bounding box around page") That's how I did my footprint example :-P but saved as PNG for email. ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: funny gnetlist warning
On Fri, 26 Jun 2009 15:32:05 +0200, Duncan Drennan wrote: >> CONN1: need new file element for footprint PLUGCON_383_2PIN >> (value=RIA_connect) >> Warning: argument passing may have been confused by >> a comma in a component value: > > Have you tried taking the underscore out of the value? No. And I don't wish to, too. Due to the gnetlists infamous misinterpretation of hyphens as m4 code I already restricted my library to upper case letters, numbers and underscore. Footprint names would be a lot less human readable if underscores were also excluded. IMHO the netter way to deal with the sirtuation would be a more robust parsing of names, rather than spam stdout with warnings. ---<(kaimartin)>--- -- Kai-Martin Knaak Öffentlicher PGP-Schlüssel: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x6C0B9F53 ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: RFC: Towards a better symbol/package pin-mapping strategy (was: Re: slotting and power pins)
Hi Michael, On Mon, 2009-06-29 at 06:23 +, Michael Sokolov wrote: > Bert Timmerman wrote: > > > got cvs co working > > Simply typing make barfs the following: > > [snipped] > > > Your OS is too modern. Install something that is at least 25 years > obsolete and try again. > > > Seriously though, Ineiev has already told me that ultra-modern versions > of gcc refuse to compile uEDA as distributed by me. So you need to > apply some local patches of your own to port it to your modern OS. > > uEDA is developed on/under/for 4.3BSD-Quasijarus, my own version of UNIX > that very faithfully maintains the traditions of UNIX Version 7 and > Berkeley VAX UNIX. The C compiler maintains strict compatibility with > the K&R C standard aka C78. > > uEDA does however compile OK under Slackware 10.2 and RHEL 4. Lots of > warnings, but no fatal errors, so I just ignore them. > > MS > > > ___ > geda-user mailing list > geda-user@moria.seul.org > http://www.seul.org/cgi-bin/mailman/listinfo/geda-user I'm still running FC5 (which is declared dead for over 2 years now, EOLT June 2007) on my devel box, have some old i486/i586 boxes on RH6.1 in the garage, so porting to RH6.1 maybe something funny for after the holidays. I hope to install FC11 on a new box soon, as my gtk version is too old to compile gEDA and pcb ;-( Kind regards, Bert Timmerman. ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: RFC: Towards a better symbol/package pin-mapping strategy
Dan McMahill wrote: > > for things like transistors and IC's, I have already implemented exactly > this for my own use. I have an ASCII file that associates a complete > vendor part number (including package code) with a symbol template, a > footprint, and a mapping from symbol pin to footprint pin. > > Then I have an awk script that reads in the database and produces a set > of "heavy" symbols that have the correct pinout to match the footprint > that goes with them. So on my schematic, I see the correct pin number. > If I want to change from a part in a 16 pin DIP to a 20 pin PLCC, I > pick the new part number with correct package code to instantiate. > Oooh. Care to post them? Maybe create a gedasymbols page for yourself, and put it there? b.g. -- Bill Gatliff b...@billgatliff.com ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: Change PCB keystrokes
On Mon, 2009-06-29 at 16:48 +0200, Irena Hwang wrote: >completely awry. I would greatly appreciate any input at all on >fixing this problem. > Can talk about Linux only: I a program does not work properly it may be a solution to delete the local configuration files -- ste...@amd64-x2 ~ $ cd ste...@amd64-x2 ~ $ ls -la drwxr-xr-x 3 stefan stefan 4096 May 24 23:20 .pcb ste...@amd64-x2 ~ $ rm -r .pcb ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: RFC: Towards a better symbol/package pin-mapping strategy
On Sun, Jun 28, 2009 at 9:46 PM, Dan McMahill <[1]...@mcmahill.net> wrote: For transistors and IC's, I have no problems with the "enumerate them all" approach I've taken. This is what I been doing too. All semiconductors are enumerated. Since all of the graphics are done by scripts there is a single copy of the graphics data. The script adds the appropriate attributes and pin numbering. (* jcl *) -- You can't create open hardware with closed EDA tools. [2]http://www.luciani.org References 1. mailto:d...@mcmahill.net 2. http://www.luciani.org/ ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
gEDA-user: Change PCB keystrokes
Hi, Is there a way to access and edit the PCB keystrokes? Since I realized the keystrokes are not functioning, I have tried uninstalling gEDA and fink and reinstalling both (I am using mac os x, is there an easy way to uninstall the gEDA-bundle without completely uninstalling fink?), however PCB is still not working and the keystrokes are still completely awry. I would greatly appreciate any input at all on fixing this problem. Thanks for your time, -Irena ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
gEDA-user: PCB keystrokes no longer functioning
Hi, Last week I installed gEDA-bundle using fink (also updated to XQuartz 2.1.6) and PCB and all its keystrokes worked just fine. The last time I used PCB was on Friday. However, upon opening PCB today (three days later) the keystrokes don't seem to be functioning correctly: space does nothing at all instead of entering select mode, the slash zooms in and out instead of toggling between _/ and \_ modes, and esc does not enter panning mode and when drawing lines (actually esc now toggles between line modes). What is causing this abrupt problem, and what can I do to fix it? Thanks, -Irena ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
