[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: gEDA-user: Migration form eagle to gEDA
Hi Abhijit,
I looked at your site. Your tutorial document is pretty good.
Regards,
Chetan Bhargava
On Mon, Jul 25, 2011 at 11:48 AM, Abhijit Kshirsagar
<abhijit86k@xxxxxxxxx> wrote:
> Recently I wrote a small script to automate some of the things needed
> to be done after the gEDA tools are installed:
> such as setting up per-user symbols and footprint directories; and
> adding these to the gafrc and gschemrc files, etc...
> The script (Setup_gEDA.sh) is well commented and can be downloaded from
> here:
> [1]http://sites.google.com/site/abhijit86k/linux/geda
> Its really quite basic, but i hope it helps someone...
> Thanks and Regards,
> ~Abhijit
>
> On Mon, Jul 25, 2011 at 22:41, Colin D Bennett <[2]colin@xxxxxxxxxxx>
> wrote:
>
> On Sun, 24 Jul 2011 19:17:39 -0700
> "[3]bsalinux@xxxxxxxxx" <[4]bsalinux@xxxxxxxxx> wrote:
> > I guess that his question might have been asked before but is there
> > any howto or tutorial to migrate from Eagle to gEDA?
> > I tried Google searches but no meaningful information has been found.
>
> Do you mean migration of particular designs (schematic/layout),
> importing them to gEDA?
> Or do you mean migrating as a user?
> I have never used Eagle, so I can't be of any specific assistance in
> that regard. Â However, I can say that while there are tutorial on
> gschem/PCB and the general gEDA workflow, there is a need for a
> good,
> complete tutorial for new users.
> Because gEDA is designed to support a wide variety of uses and
> workflow
> methods, I feel it is not immediately clear to new users how to
> proceed.
> Let me share my basic process for designing a circuit and PCB so you
> can get a feel for how the tools might be used:
> 0.) Set up a revision control system.
> Â Â Something modern like git or Bazaar is best.
> Â Â Commit frequently, and write descriptive commit messages!
> Â Â (I find this useful as a journal or log to come back to myself
> about
> Â Â what I've done on the design, not to mention saving yourself
> from
> Â Â screwups...)
> 1.) Draw schematic with gschem, placing symbols and drawing net
> Â Â connections.
> Â Â Various steps required as part of drawing the basic schematic:
> Â Â - Import any special symbols not in the default library from
> Â Â Â [5]gedasymbols.org
> Â Â - If you can't find the symbol you need, draw custom symbol
> Â Â Â in gschem, save as .sym file.
> Â Â - Run a schematic design rule check (DRC) with âgnetlistâ;
> Â Â Â fix any DRC errors.
> 2.) Assign footprints to all components in the schematic.
> Â Â You can do this in gschem or using gattrib (table view).
> Â Â - Import any special footprints from [6]gedasymbols.org
> Â Â - If you can't find an appropriate footprint, create one in the
> Â Â Â âpcbâ tool. (Takes some practice, but after a while it
> becomes
> Â Â Â straightforward.)
> Â Â - Make sure the footprints you are using are correct for the
> Â Â Â parts you are going to use.
> Â Â - Check footprints to make sure that pin assignments from
> Â Â Â schematic symbol to PCB footprint is correct!! Watch out for
> Â Â Â LEDs, diodes, polarized capacitors, etc. that may have pins
> Â Â Â identified only as â1â and â2â. Â (I often use my own custom
> Â Â Â symbols/footprints with more descriptive, logical pin
> identifiers
> Â Â Â like âPâ and âNâ on diodes for P-type and N-type terminals.)
> 3.) Lay out the board.
> Â Â - Import schematic into pcb.
> Â Â - Set âpreferencesâ for the design such as minimum copper
> Â Â Â clearance, board dimensions, layer stackup, etc.
> Â Â - Set up the grid as you prefer.
> Â Â - Place components.
> Â Â - Route tracks with lines. Â (You can use autorouter, but that
> is a
> Â Â Â personal preference... I have always done manual routing.)
> Â Â - Draw board outline on the âoutlineâ layer.
> Â Â - Add ground flood if desired.
> 4.) Verify design.
> Â Â - Run DRC in the pcb program; fix any problems such as âcopper
> areas
> Â Â Â too closeâ, etc.
> Â Â - Print out the PCB layout at 1:1 scale on paper and actually
> place
> Â Â Â the parts on it. Â This is a sanity check to make sure
> footprints
> Â Â Â are correct and spacing around certain parts are sufficient
> Â Â Â (e.g., need enough spacing around some connectors, switches,
> Â Â Â jumpers, sockets, heat sinks, etc.).
> I'm no wizard, just a novice, but I've done a few dozen designs and
> am
> feeling very comfortable in gEDA myself so hopefully this is
> helpful.
> One thing that I've found is that it is worthwhile to âerror-proofâ
> yourself through your process. Â Some of the common errors I've made
> are
> related to incorrect pin assignments or footprint assignments, so I
> take special care to validate those.
> Regards,
> Colin
>
> _______________________________________________
> geda-user mailing list
> [7]geda-user@xxxxxxxxxxxxxx
> [8]http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
>
> References
>
> 1. http://sites.google.com/site/abhijit86k/linux/geda
> 2. mailto:colin@xxxxxxxxxxx
> 3. mailto:bsalinux@xxxxxxxxx
> 4. mailto:bsalinux@xxxxxxxxx
> 5. http://gedasymbols.org/
> 6. http://gedasymbols.org/
> 7. mailto:geda-user@xxxxxxxxxxxxxx
> 8. http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
>
>
>
> _______________________________________________
> geda-user mailing list
> geda-user@xxxxxxxxxxxxxx
> http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
>
>
--
NOTICE: This email is a one to one communication and not for receiving
any offers or a mass relay of emails. Please refrain from subscribing
this email address to any of the mailing lists. All / any mass emails
to this address will be considered as SPAM and will be reported to FTC
and other authorities. Thanks.
_______________________________________________
geda-user mailing list
geda-user@xxxxxxxxxxxxxx
http://www.seul.org/cgi-bin/mailman/listinfo/geda-user