Shall we update the distributed sym files so they pass gsymcheck ?
Should gsymcheck really complain about a missing numslots=0
and report error for a net=GND:2 attribute?
***
When doing pcb import schematic, I get the message:
Remember to check that your schematic has no errors using the drc2
Running gnetlist -g drc2 on a schematic I get:
Checking non-numbered parts...
Checking duplicated references...
Checking nets with only one connection...
Checking pins without the 'pintype' attribute...
Checking type of pins connected to a net...
WARNING: Pin(s) with pintype 'output': U2:9
Hello,
In my current design I wanted ton create footprint (for touch key) that would
have normal pin and some copper tracks connected to this pin. Is it possible?
Tracks automatically became pads in footprint so then I have DRC errors. In
general is it possible to create footprint that will
On Fri, Sep 24, 2010 at 4:02 PM, Armin Faltl armin.fa...@aon.at wrote:
Dreaming about mechanical cad features in pcb and how one best works
to mechanical constrains on a pcb, knowing the latest and greates pcb
use OpenGL and transparency anyway,
http://code.google.com/p/toped/ is an IC Layout
Hello, everybody!
This is my first post at this mailing-list, so I would like to introduce myself
very short. The main part of this mail starts after the double-line.
My name is Felix and I am studying electrical engineering in Germany. I am
sorry for my bad English, I hope, you will
On Sep 26, 2010, at 2:31 AM, Karl Hammar wrote:
The U3 is the lm7805-1.sym from gschem and it does not contain any
pintype attribute.
It is easy enought to correct:
$ diff `locate lm7805-1.sym`
1c1
v 20080127 1
---
v 20031231 1
19,20d18
T 300 600 5 10 0 0 0 0 1
Bob Paddock wrote:
http://code.google.com/p/toped/ is an IC Layout Editor that puts the
transparency to good use, as an example.
Alas there are no screen shots in the project to show how it would
apply to PCB.
There are screen shots two in Chitlesh's page on fedora.org:
michalwd1979 wrote:
In my current design I wanted ton create footprint (for touch key)
that would have normal pin and some copper tracks connected to this
pin. Is it possible? Tracks automatically became pads in footprint
so then I have DRC errors.
Give all connected pads the same pin number
Felix Ruoff wrote:
My name is Felix and I am studying electrical engineering in Germany.
I am sorry for my bad English, I hope, you will understand me
No problem. You are not the only German on the list.
In fact, we may well be the second largest user group :-)
The following patch changes
Karl Hammar wrote:
Shall we update the distributed sym files so they pass gsymcheck ?
Yes, please.
I gave up on gsymcheck because it caused more work due to false alarms
than it saved by pointing to real errors.
Should a missing numslots=0 really be a warning?
It is annoying to include it
There are screen shots two in Chitlesh's page on fedora.org:
http://chitlesh.fedorapeople.org/FEL/gallery.html
Thank you.
What does the tope GUI differently to Peter Cliftons semi forked
version of pcb?
I've not run Peter's version so can't really comment. I'm all to
slowly poking at a
Karl Hammar wrote:
Running gnetlist -g drc2 on a schematic I get:
(...)
Why does it warn about
output -- input/output
Don't know. IMHO, this combination should be fine.
input/output -- pwr
input and output are meant to refer to signals. The DRC assumes that
signals should never
Thank you, kaimartin, for your reply!
IMHO, it would be better to put the patch file in a regular attachment
rather than copy paste it to the main body of the mail. Mail servers do
quite a bit of space, tab and new line munging on the main body and
render the patch unusable. By contrast, they
Sorry, i forgot the attachement :-(.
Here it is.
Felix
Am 26.09.2010 21:38, schrieb Felix Ruoff:
Thank you, kaimartin, for your reply!
IMHO, it would be better to put the patch file in a regular attachment
rather than copy paste it to the main body of the mail. Mail servers do
quite a bit
Bob Paddock wrote:
Someone, some place, in the future will want to support something
that none of us have ever heard of today.
If there is a easy, well documented, Plug-In system, then they can
implement what they need without having to figure out the internals
of PCB.
The downside is that
Not being part of the distribution
A well documented plug in should become part of the distribution.
Undocumented code of any kind, should not.
___
geda-user mailing list
geda-user@moria.seul.org
http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Bob Paddock wrote:
What is the benefit of plug-ins for this kind of infrastructure?
IMHO, support of different image formats should be part of the
main distribution.
Someone, some place, in the future will want to support something that
none of us have ever heard of today.
If there is a
17 matches
Mail list logo
