Re: gEDA-user: subcircuit definition and channelised design
Geoff Swan wrote: I am relatively new to gEDA - so I thought I would find out if this is theoretically possible (or been done before) before I start trying to write my own script... What you describe seems like the sub sheet wizard which is on the wish list of many users. Yes, this sounds useful and very much so. Seems to me, that it has not been done before -- at least not in a way that has been described in gpleda.org. Looking forward to your solution, ---)kaimartin(--- -- Kai-Martin Knaak tel: +49-511-762-2895 Universität Hannover, Inst. für Quantenoptik fax: +49-511-762-2211 Welfengarten 1, 30167 Hannover http://www.iqo.uni-hannover.de GPG key:http://pgp.mit.edu:11371/pks/lookup?search=Knaak+kmkop=get ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: General Layers questions
DJ Delorie wrote: However, I don't think we should start off with lines have paste. They don't. My current project happens to be a use case for lines with paste: I need to transport lots of current on limited space. And it needs to be very resistant to vibration (this is supposed to survive a rocket launch) So ordinary green wires soldered are considered a risk of failure. What we intend to do, is solder copper wires full length on the board. This calls for tracks with exposed copper and corresponding apertures in paste layer. Paste will allow for better control of the amount of solder than with a simple syringe dispenser. Currently tracks cannot be uncovered, let alone induce paste apertures. As a work-around I plan to convert the current path into pads just before the layout is exported to gerber. (Maybe, I should write a script...) This is of course a kludge. Upshot: Please try not to constrain possible attributes and properties of objects. There may be use cases even for seemingly weird combinations just around the corner. (Do I sound like John Doty now? :-) Allowing a GUI way to enable/disable layers anywhere in the heirarchy would be cool; you could disable just the assembly objects in your generic silk layer. +1 ---)kaimartin(--- -- Kai-Martin Knaak tel: +49-511-762-2895 Universität Hannover, Inst. für Quantenoptik fax: +49-511-762-2211 Welfengarten 1, 30167 Hannover http://www.iqo.uni-hannover.de GPG key:http://pgp.mit.edu:11371/pks/lookup?search=Knaak+kmkop=get ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: General Layers questions
On 15 March 2011 14:39, Kai-Martin Knaak [1]kn...@iqo.uni-hannover.de wrote: My current project happens to be a use case for lines with paste: I need to transport lots of current on limited space. And it needs to be very resistant to vibration (this is supposed to survive a rocket launch) So ordinary green wires soldered are considered a risk of failure. What we intend to do, is solder copper wires full length on the board. This calls for tracks with exposed copper and corresponding apertures in paste layer. Paste will allow for better control of the amount of solder than with a simple syringe dispenser. Currently tracks cannot be uncovered, let alone induce paste apertures. As a work-around I plan to convert the current path into pads just before the layout is exported to gerber. (Maybe, I should write a script...) This is of course a kludge. Agreed - I'd love to see paste being a possible property of layers, though obviously only the top and bottom layers (does it make any sense to haver inner paste?) References 1. mailto:kn...@iqo.uni-hannover.de ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: General Layers questions
Kai-Martin Knaak kn...@iqo.uni-hannover.de writes: DJ Delorie wrote: However, I don't think we should start off with lines have paste. They don't. My current project happens to be a use case for lines with paste: I need to transport lots of current on limited space. And it needs to be very resistant to vibration (this is supposed to survive a rocket launch) So ordinary green wires soldered are considered a risk of failure. What we intend to do, is solder copper wires full length on the board. This calls for tracks with exposed copper and corresponding apertures in paste layer. Paste will allow for better control of the amount of solder than with a simple syringe dispenser. Currently tracks cannot be uncovered, let alone induce paste apertures. As a work-around I plan to convert the current path into pads just before the layout is exported to gerber. (Maybe, I should write a script...) This is of course a kludge. Upshot: Please try not to constrain possible attributes and properties of objects. There may be use cases even for seemingly weird combinations just around the corner. I don't think that paste shall be attributes of lines. Lines and paste live at the same level. If you need to connect them, you'd need to go one level up, like elements are one or two levels up from lines and paste, or vias are one level up. To implement this level (lines+paste) you will not need support from the file format, it's in the GUI. You may add attributes to lines and paste objects that effect the GUI to edit them together. IMHO, the file format shall loose all special support for levels (elemets, vias), just an arbitray hierachy of grouping, with attributes that tell the GUI how to present those to the user for editing. (Do I sound like John Doty now? :-) All will be well :-) Allowing a GUI way to enable/disable layers anywhere in the heirarchy would be cool; you could disable just the assembly objects in your generic silk layer. +1 ---)kaimartin(--- -- Stephan Böttcher FAX: +49-431-85660 Extraterrestrische PhysikTel: +49-431-880-2508 I.f.Exp.u.Angew.Physik mailto:boettc...@physik.uni-kiel.de Leibnizstr. 11, 24118 Kiel, Germany ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: subcircuit definition and channelised design
Hi -Original Message- From: geda-user-boun...@moria.seul.org [mailto:geda-user-boun...@moria.seul.org] On Behalf Of Kai-Martin Knaak Sent: Tuesday, March 15, 2011 3:12 PM To: geda-u...@seul.org Subject: Re: gEDA-user: subcircuit definition and channelised design Geoff Swan wrote: I am relatively new to gEDA - so I thought I would find out if this is theoretically possible (or been done before) before I start trying to write my own script... What you describe seems like the sub sheet wizard which is on the wish list of many users. Yes, this sounds useful and very much so. Seems to me, that it has not been done before -- at least not in a way that has been described in gpleda.org. Looking forward to your solution, ---)kaimartin(--- -- Kai-Martin Knaak tel: +49-511-762-2895 Universität Hannover, Inst. für Quantenoptik fax: +49-511-762-2211 Welfengarten 1, 30167 Hannover http://www.iqo.uni-hannover.de GPG key: http://pgp.mit.edu:11371/pks/lookup?search=Knaak+kmkop=get FWIW, I have saved this shell script for generating schematic pages into symbols. To be found at: http://www.xs4all.nl/~ljh4timm/downloads/geda_sch2sym.tar.gz #!/bin/bash # gEDA - GNU Electronic Design Automation # geda_sch2sym.bsh # Copyright (C) 2007 Andrew Tan Says it all. 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: subcircuit definition and channelised design
Dnia 2011-03-15 o godzinie 21:03 Bert Timmerman napisał(a): http://www.xs4all.nl/~ljh4timm/downloads/geda_sch2sym.tar.gz #!/bin/bash # gEDA - GNU Electronic Design Automation # geda_sch2sym.bsh # Copyright (C) 2007 Andrew Tan Says it all. It is also waiting for review here: https://bugs.launchpad.net/geda/+bug/698670 -- Krzysztof Kościuszkiewicz Simplicity is the ultimate sophistication -- Leonardo da Vinci ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: subcircuit definition and channelised design
Krzysztof Kościuszkiewicz k.kosciuszkiew...@gmail.com writes: Dnia 2011-03-15 o godzinie 21:03 Bert Timmerman napisał(a): http://www.xs4all.nl/~ljh4timm/downloads/geda_sch2sym.tar.gz #!/bin/bash # gEDA - GNU Electronic Design Automation # geda_sch2sym.bsh # Copyright (C) 2007 Andrew Tan Says it all. It is also waiting for review here: https://bugs.launchpad.net/geda/+bug/698670 IMPORTANT NOTE: In order to run geda_sch2sym.bsh, users must make sure the hierarchy-traversal is disabled in the system-gnetlistrc file (usually located in the /usr/share/gEDA folder). There should be some way to disable hierarchy-traversal from the commandline, is there? Or at least a local gafrc, but even that would push it out of reach for me. -- Stephan ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: subcircuit definition and channelised design
On Mar 15, 2011, at 2:50 PM, Stephan Boettcher wrote: There should be some way to disable hierarchy-traversal from the commandline, is there? Or at least a local gafrc, but even that would push it out of reach for me. You have to put a little bit of Scheme in some gnetlistrc someplace to control it from command line, but it can be done: http://archives.seul.org/geda/user/Nov-2008/msg00489.html 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: subcircuit definition and channelised design
John Doty j...@noqsi.com writes: On Mar 15, 2011, at 2:50 PM, Stephan Boettcher wrote: There should be some way to disable hierarchy-traversal from the commandline, is there? Or at least a local gafrc, but even that would push it out of reach for me. You have to put a little bit of Scheme in some gnetlistrc someplace to control it from command line, but it can be done: http://archives.seul.org/geda/user/Nov-2008/msg00489.html I had a peek at the man page: -c string Pass the specified string to the guile interpreter. This allows you to execute arbitrary guile scripts from the command line. Be sure to surround the string with either single or double quotes to satisfy your shell. The string is execute before any init or netlist backend scheme code is loaded or executed. How about: gnetlist -c '(hierarchy-traversal disabled)' 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 -- Stephan ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: General Layers questions
On Mon, Mar 14, 2011 at 10:16:34PM +, Thomas Oldbury wrote: Reading the section on blind and buried vias had me interested. However, shouldn't vias be assigned layers (and not the other way around?) It would probably make the code simpler - clicking on a via would give immediate information about layers it belongs to, whereas having vias assigned to layers would mean a costly lookup through all layers to find the via. I have expressed myself probably in wrong way. There will be a struct called via. It will contain a hole and pointers to attached object on all affected layers. So when you click on the hole you can change parameters of all attached object at once. When you click on the attached object on some layer, you will change just that object. So moving will be possible just by moving the hole. This can be easily programed, as when clicking on hole, you will have an array or something of pointer to all object, which you want to change. On the other way, the object lives on some layer, so you can treat it as any other object. Martin Kupec ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: General Layers questions
On Tue, Mar 15, 2011 at 03:00:06PM +, Thomas Oldbury wrote: Agreed - I'd love to see paste being a possible property of layers, though obviously only the top and bottom layers (does it make any sense to haver inner paste?) My concept doesn't understand top, bottom and inner layer..it is simply layer and you can do what you want to do... Martin Kupec ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: General Layers questions
On Mon, Mar 14, 2011 at 06:11:13PM -0400, DJ Delorie wrote: 1. Line is drawn on copper layer, it has properties like, mask and paste. I think for things like mask and paste, we might have to differentiate between implicit and explicit contents. A pad which has a mask opening is an implicit object on the mask layer; the user drawing additional stuff on the mask layer would be an explicit object. However, a *footprint* that defines a mask opening in a mask layer, would have explicit content on *its* mask layer. That content would be merged with it's elements' parent's corresponding mask layer during draw/output. However, I don't think we should start off with lines have paste. They don't. Pads have paste, pads are made of lines. In the new way, we should define paste separately, so it's never an attribute of something else. However, we could include shortcuts for common objects like pins or pads, which are expanded at runtime into the corresponding layers. To all the above I will write another email. What attributes lines *do* have is keep-aways, like copper clearance in polygons. Such clearances affect other like-types in the same-layer, i.e. clearance on a copper layer clears polygons on that layer, clearance in a assembly drawing layer clears filled polys on that drawing layer, etc. Yes, keep-aways are definetly just attributes. The others are not. The tricky part of all this is defining ways of referring to a given drawing layer in a physical layer by type, class, and name. I.e. if a footprint has a generic silk layer, and our design has four different types of silk layers, to which do we map the footprint? That is why I have defined active layer. So each type of layer has an active one. When I add footprint I add its silk layer to the current active silk layer. That should work and should be simple. I suggest, for performance, we define layer classes as enumerations (copper, silk, mask, paste, outline, drawing; plus modifiers like anti-paste vs paste) but have a way to further name layers in a class-like heirarchy with wildcards. Thus, a footprint might have a layer named silk::courtyard that is a silk (enumerated) class named courtyard. The design might have a courtyard layer, or might define a catch-all drawing layer silk::* it gets mapped to. Perhaps silk::assembly::courtyard which maps to a generic silk layer, unless you have a generic assembly layer, unless you have an assembly layer just for courtyards. I have a bit different idea here. Generally all can go to common silk. But elements will be attached tags. That will be just some general purpose mark. An element would have any number of tags it needs. And there will be possibility to put all tagged elements of some type to special layer, other than the active one. Allowing a GUI way to enable/disable layers anywhere in the heirarchy would be cool; you could disable just the assembly objects in your generic silk layer. It should be simple. Just skip drawing of that part :-). I know it is a bit more complicated, but it should be possible. I've mentioned numbered vs named physical layers before, like top/inner/bottom vs 1..8 (or top,2..7,bottom) - such mappings between symbolically named layers (drawing or physical) and specific physical layers in a design is something we need to figure out. There will be implicit mapping. Each drawing layer belongs to some physical layer. And everything will have names, numbers are not needed at all. Z-order will be implicitly defined by order in memory/file. Mapping the layer heirarchy to a CAM job engine, that picks out which parts of the heirarchy become which parts of each output page/sheet/gerber/screen/whatever, is another problem. I don't see what is the problem :-(. It is needed to decide which concept to use, I have no preferences, and describe closely how it should behave. The problem is that working on copper/mask/paste layers is somewhat interconnected I think the connection should be at the sub-assembly heirarchical level. We should treat footprints as just another pcb sub-assembly, so if you move an element, it's footprint is drawn at a new location, which happens to move the lines and paste together. There is NOTHING requiring an assumption that paste and lines correspond; for example, a thermal pad often has paste that is a completely different geometry than the copper. Ok. I can define that footprint is that set of elements and it moves according to origin of the footprint. And I mean any set on any set of layers. Martin Kupec ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
gEDA-user: Measuring length of trace
I'm trying to measure the length of some traces, so I can keep them the same (for timing purposes.) I've heard of :report(netlength) but that always gives me 0.00mm. What am I doing wrong, or is there something else I should be doing? ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: Measuring length of trace
I'm trying to measure the length of some traces, so I can keep them
the same (for timing purposes.) I've heard of :report(netlength) but
that always gives me 0.00mm. What am I doing wrong, or is there
something else I should be doing?
The crosshair has to be over the net you want measured. The grid may
interfere with this.
I bind that action to the 'r' key in my ~/.pcb/pcb-menu.res (lesstif):
{Report net length Report(NetLength) a={R Keyr}}
___
geda-user mailing list
geda-user@moria.seul.org
http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: Measuring length of trace
Hmm it's not working...
I'm getting: Net length: 0.00 mils
Even when hovering over the trace. I think the problem is it is
including the pads and vias and getting confused, but I wouldn't know
enough about pcb to know for certain.
Can you see images over newsgroup? I've uploaded a screenshot here:
[1]http://i53.tinypic.com/20tgtbl.png
On 15 March 2011 22:12, DJ Delorie [2]d...@delorie.com wrote:
I'm trying to measure the length of some traces, so I can keep them
the same (for timing purposes.) I've heard of :report(netlength) but
that always gives me 0.00mm. What am I doing wrong, or is there
something else I should be doing?
The crosshair has to be over the net you want measured. The grid
may
interfere with this.
I bind that action to the 'r' key in my ~/.pcb/pcb-menu.res
(lesstif):
{Report net length Report(NetLength) a={R Keyr}}
___
geda-user mailing list
[3]geda-user@moria.seul.org
[4]http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
References
1. http://i53.tinypic.com/20tgtbl.png
2. mailto:d...@delorie.com
3. mailto:geda-user@moria.seul.org
4. 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: General Layers questions
Hi, there are two things we need to consider: footprints and layouts. I don't want to talk about footprints. Footprints will just be a set of element on differents layers which behave atomicaly. So once it is created there are no problems. The problem is with layout. There are lines,arc,polygons. All of them should have an attribute of keep-away type. That is easy. The problem is how to draw a unmasked line. I can draw a line and than the same line in negative mask layer. I can even aid the designed by a tool copy to another layer (there is at least move to layer already, maybe even that one). But one the line is drawn it is a separate element with no connection to the first line. When I move with the cooper line the mask line will not move. So, do we need/want to have some sync mechanism so having unmasked lines and lines with cooper easy to maintrain? Maybe not..I don't know. When you are drawing footprint, you can draw mask/paste layers after cooper is done, so there will be probably no problems. Martin Kupec ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: General Layers questions
On Tue, Mar 15, 2011 at 03:55:58PM -0600, John Doty wrote: On Mar 15, 2011, at 3:35 PM, Martin Kupec wrote: There will be a struct called via. It will contain a hole and pointers to attached object on all affected layers. No. A via is only one kind of composite object. The list of kinds of composite objects that might appear on a board is unbounded. There isn't even a single kind of via in real life. Having an ad hoc implementation of each such object is impractical and confusing. Well-designed software would avoid implementing such things as special kludges, but would have a general facility for describing them. Then, users could contribute to libraries of such descriptions, so we would not be so dependent on developers to spoon feed us every detail. Footprints are a particular case of this, but other kinds of composite objects (subcircuits, antennas, delay lines, buried vias, fuses, current sense resistors, printed inductors and capacitors, ...) could also be in the library if the software properly distinguished between primitive elements and composite objects. Ok. You got the point. I don't see how to do it right now, but I will think of it. We need at least hole element. And say which layers it goes through. But the rest can by just footprint. The problem I see is that the number of layers affected differs, so the footprint has to accomodate that. Martin ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: General Layers questions
One thing I'd like to see is a drill hole, because at the moment I use vias for those. It means I usually have to have a minimum plating, or DRC will warn me, but drill holes rarely need plating. On 15 March 2011 22:32, Martin Kupec [1]martin.ku...@kupson.cz wrote: On Tue, Mar 15, 2011 at 03:55:58PM -0600, John Doty wrote: On Mar 15, 2011, at 3:35 PM, Martin Kupec wrote: There will be a struct called via. It will contain a hole and pointers to attached object on all affected layers. No. A via is only one kind of composite object. The list of kinds of composite objects that might appear on a board is unbounded. There isn't even a single kind of via in real life. Having an ad hoc implementation of each such object is impractical and confusing. Well-designed software would avoid implementing such things as special kludges, but would have a general facility for describing them. Then, users could contribute to libraries of such descriptions, so we would not be so dependent on developers to spoon feed us every detail. Footprints are a particular case of this, but other kinds of composite objects (subcircuits, antennas, delay lines, buried vias, fuses, current sense resistors, printed inductors and capacitors, ...) could also be in the library if the software properly distinguished between primitive elements and composite objects. Ok. You got the point. I don't see how to do it right now, but I will think of it. We need at least hole element. And say which layers it goes through. But the rest can by just footprint. The problem I see is that the number of layers affected differs, so the footprint has to accomodate that. Martin ___ geda-user mailing list [2]geda-user@moria.seul.org [3]http://www.seul.org/cgi-bin/mailman/listinfo/geda-user References 1. mailto:martin.ku...@kupson.cz 2. mailto:geda-user@moria.seul.org 3. 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: Measuring length of trace
What version of pcb are you using? ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: General Layers questions
Our current way is that copper objects have implied mask openings. I suppose we could continue that, as well as adding some paste metrics there too. This is *in addition to* a separate paste layer for user-defined paste, or for footprint-defined custom paste, of course. ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: Measuring length of trace
About dialog shows this: This is PCB, an interactive printed circuit board editor version 20091103 Compiled on Dec 18 2009 at 22:18:40 by harry eaton On 15 March 2011 22:47, DJ Delorie [1]d...@delorie.com wrote: What version of pcb are you using? ___ geda-user mailing list [2]geda-user@moria.seul.org [3]http://www.seul.org/cgi-bin/mailman/listinfo/geda-user References 1. mailto:d...@delorie.com 2. mailto:geda-user@moria.seul.org 3. 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: General Layers questions
We already have a Hole type. Create a via, and use Ctrl-H to toggle it into a hole. Note that many fabs charge extra if you have unplated holes in your design. ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: General Layers questions
Huh. Did not know that. Thanks. I'll have to check if my fab does charge. On 15 March 2011 22:51, DJ Delorie [1]d...@delorie.com wrote: We already have a Hole type. Create a via, and use Ctrl-H to toggle it into a hole. Note that many fabs charge extra if you have unplated holes in your design. ___ geda-user mailing list [2]geda-user@moria.seul.org [3]http://www.seul.org/cgi-bin/mailman/listinfo/geda-user References 1. mailto:d...@delorie.com 2. mailto:geda-user@moria.seul.org 3. 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: Measuring length of trace
version 20091103 Could you try a newer version? There's been a 20100929 release, or you could build the git version. ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: Measuring length of trace
I'll try. Are there any bug fixes for that version relating to the net length calculator? Also, are the PCB files backwards compatible?I'm working with several people who still use the 2009 versions. On 15 March 2011 22:52, DJ Delorie [1]d...@delorie.com wrote: version 20091103 Could you try a newer version? There's been a 20100929 release, or you could build the git version. ___ geda-user mailing list [2]geda-user@moria.seul.org [3]http://www.seul.org/cgi-bin/mailman/listinfo/geda-user References 1. mailto:d...@delorie.com 2. mailto:geda-user@moria.seul.org 3. 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: General Layers questions
On Mar 15, 2011, at 4:32 PM, Martin Kupec wrote: We need at least hole element. And say which layers it goes through. But that's composition, so a hole is not elementary. But it's a simple case, so it's a good place to start designing the composition language. 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: Measuring length of trace
I'll try. Are there any bug fixes for that version relating to the net length calculator? Also, are the PCB files backwards compatible? I'm working with several people who still use the 2009 versions. The files are mostly backward compatible, as long as you don't use new features, although pcb tags them with the new version no matter what. ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: General Layers questions
Martin Kupec martin.ku...@kupson.cz writes: On Tue, Mar 15, 2011 at 03:55:58PM -0600, John Doty wrote: On Mar 15, 2011, at 3:35 PM, Martin Kupec wrote: There will be a struct called via. It will contain a hole and pointers to attached object on all affected layers. No. A via is only one kind of composite object. The list of kinds of composite objects that might appear on a board is unbounded. There isn't even a single kind of via in real life. Having an ad hoc implementation of each such object is impractical and confusing. Well-designed software would avoid implementing such things as special kludges, but would have a general facility for describing them. Then, users could contribute to libraries of such descriptions, so we would not be so dependent on developers to spoon feed us every detail. Footprints are a particular case of this, but other kinds of composite objects (subcircuits, antennas, delay lines, buried vias, fuses, current sense resistors, printed inductors and capacitors, ...) could also be in the library if the software properly distinguished between primitive elements and composite objects. Ok. You got the point. I don't see how to do it right now, but I will think of it. We need at least hole element. And say which layers it goes through. But the rest can by just footprint. The problem I see is that the number of layers affected differs, so the footprint has to accomodate that. IMHO, as holes are circles draw on just another layer. People were asking for slots. If they find a vendor to do them, they may just draw lines on that layer as well. Else, DRC shall flag non-circles. Each such hole layer shall have a spec (attribute) to which (copper) layers they electrically connect. There will be at least one such layer for each type of blind, burried, and through via. The GUI will happily stack vias according to the selected routing style into a composites and paste them on the layout, so for simple cases nothing changes from how we work now. -- Stephan ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
