As edge rates increase, signal intergrity (SI) becomes more and more
important, even for the hobbyist. Unfortunately, the models provided
by semiconductor vendors typically come in only 2 forms, encrypted
HSPICE and IBIS. No open tools exist for handling either. An open
HSPICE decryption utility
On Tue, May 31, 2011 at 05:09:25AM +0200, Kai-Martin Knaak wrote:
Richard Rasker wrote:
OK, I'll start by reading up on the light vs. heavy symbol discussions.
Do I understand correctly that heavy symbols basically have certain nets
with predefined names (e.g. VCC, GND) implicitly
On 05/27/2011 11:54 AM, DJ Delorie wrote:
This is more anecdotal than anything else...
I'm a Perl fan myself.
(shudder)
Javascript!
___
geda-user mailing list
geda-user@moria.seul.org
http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
On 05/30/2011 09:35 PM, John Doty wrote:
On May 31, 2011, at 6:35 AM, John Griessen wrote:
I'd like the first definition
of what gnetlist does be, Output any data it takes in, in the same format,
with lost spatial position information allowed, but keeping all other data
intact.
I think the
Oh, yes. We like this!
Cheers,
Andy.
signality.co.uk
On 31 May 2011 07:11, Russell Dill russ.d...@asu.edu wrote:
As edge rates increase, signal intergrity (SI) becomes more and more
important, even for the hobbyist. Unfortunately, the models provided
by semiconductor vendors
The attached script not only emits a message, but substitutes
attribute_conflict for the attribute in question. Since that's not
normally a legitimate value, it should help the user to detect the
problem.
From my perspective, I don't understand why this is better. 1.7.0 warns
about
On Mon, 30 May 2011 10:49:54 +0100
Peter Clifton pc...@cam.ac.uk wrote:
On Mon, 2011-05-30 at 09:37 +0200, Gabriel Paubert wrote:
Think i know now. Polygons can't have edges that cross other
edges.
You got it.. PCB doesn't allow self intersecting polygons, so I
removed
On Tue, 31 May 2011 05:09:25 +0200
Kai-Martin Knaak k...@lilalaser.de wrote:
Richard Rasker wrote:
OK, I'll start by reading up on the light vs. heavy symbol
discussions. Do I understand correctly that heavy symbols basically
have certain nets with predefined names (e.g. VCC, GND)
Do I understand correctly that heavy symbols basically have certain nets
with predefined names (e.g. VCC, GND) implicitly included, whereas light
symbols offer the pins to connect those nets oneself?
The difference between light and heavy is specificity. A light
resistor, for example, is
so, load the design files as raw data seems to mean so that the
same input could be recreated from the internal data representation.
Well, assuming we actually record *all* the data. My point was,
whatever data we care about, we do the least amount of processing on,
unless the backend asks
Why have a core at all? One of the issues with the current gnetlist
is that it cannot be ported to a different Scheme implementation,
because the core is Guile-specific. Why not start from Scheme
functions for reading/writing .sch format?
I never said the core had to be C, but given we
From my perspective, I don't understand why this is better. 1.7.0 warns
about undefined behaviour, and defaults to backwards-compatibility
(which makes some sense IMHO). This script deliberately poisons the
netlist. In my ideal world (haha) gnetlist would generate errors on
attribute
Hmmm... what autoconf did your autoreconf use?
# Generated by GNU Autoconf 2.66 for guile 1.8.7.
___
geda-user mailing list
geda-user@moria.seul.org
http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
On Mon, 2011-05-30 at 23:34 +0200, Richard Rasker wrote:
It compiled OK after installing a bunch of dependencies, but I can't
recall at all whether dbus was enabled or not. By the looks of it, I
didn't use git, so I guess dbus is switched off. Is there a way to check
if it is enabled?
On Mon, 2011-05-30 at 22:59 +0200, Richard Rasker wrote:
Um, OK ... but somehow, my older xgsch2pcb (or perhaps just the older
PCB build) doesn't recognize the layout file edited with the newer PCB
version any more. As a result, I haven't succeeded in updating any
changes in my schematic into
Presently I use a second layer (such as a jumper layer) to draw on
jumpers for single layer FR4 PCBs, however this is cumbersome; and it
doesn't support zero ohm SMT resistors. Does PCB have any support for
adding jumper components, where the pins would essentially be shorted
(the
Python!
On 31 May 2011 11:26, Jim Lynch [1]j...@k4gvo.com wrote:
On 05/27/2011 11:54 AM, DJ Delorie wrote:
This is more anecdotal than anything else...
I'm a Perl fan myself.
(shudder)
Javascript!
___
geda-user
Does PCB have any support for adding jumper components, where the
pins would essentially be shorted (the same net) but physically
separate?
Not really.
___
geda-user mailing list
geda-user@moria.seul.org
Oh. Thanks anyway. Any hack-ish way to add this in? (Because I'd like
each jumper to have a refdes and BOM entry if possible.)
On 31 May 2011 21:44, DJ Delorie [1]d...@delorie.com wrote:
Does PCB have any support for adding jumper components, where the
pins would essentially be
Oh. Thanks anyway. Any hack-ish way to add this in? (Because I'd like each
jumper to have a refdes and BOM entry if possible.)
Put them in the schematics :-)
___
geda-user mailing list
geda-user@moria.seul.org
To my knowledge this is not the case right now. Of course the pin numbers
should not be shown on the schematics: they would use up too much schematics
real estate and are not interesting anyway (even relatively simple and cheap
FPGA devices like XC3S700A has 88 power pins in the 256 pins BGA
On Tue, 31 May 2011 21:59:04 +0100
Thomas Oldbury toldb...@gmail.com wrote:
Oh. Thanks anyway. Any hack-ish way to add this in? (Because I'd like
each jumper to have a refdes and BOM entry if possible.)
What I'd do is define a copper layer. Draw your jumpers on the that layer.
Don't send the
On Tue, May 31, 2011 at 2:09 PM, Levente Kovacs leventel...@gmail.com wrote:
On Tue, 31 May 2011 21:59:04 +0100
Thomas Oldbury toldb...@gmail.com wrote:
Oh. Thanks anyway. Any hack-ish way to add this in? (Because I'd like
each jumper to have a refdes and BOM entry if possible.)
What I'd do
Double sided boards are great, but not so great when the product is
supposed to cost only $3/each, after an MSP430, mains power supply,
heatsink, triac etc.
On 31 May 2011 22:09, Levente Kovacs [1]leventel...@gmail.com wrote:
On Tue, 31 May 2011 21:59:04 +0100
Thomas Oldbury
On Wed, Jun 1, 2011 at 6:59 AM, Thomas Oldbury toldb...@gmail.com wrote:
Oh. Thanks anyway. Any hack-ish way to add this in? (Because I'd like
each jumper to have a refdes and BOM entry if possible.)
The hack I use for solder jumpers is to make a footprint that is open
circuit, and bridge
Can you still get single sided FR2?
On May 31, 2011, at 2:26 PM, Thomas Oldbury toldb...@gmail.com wrote:
Double sided boards are great, but not so great when the product is
supposed to cost only $3/each, after an MSP430, mains power supply,
heatsink, triac etc.
On 31 May 2011
DJ Delorie wrote:
I will put together such a combined symbol and footprint lib
in my section of gedasymbols. May take about a week or so.
Excellent! Thanks!
After I skipped through what needs to be done, I have to admit that
it will take a bit longer.
Hmmm... I don't think easy
Felix Ruoff wrote:
First thing: The patch does not apply to my git repository :-(.
:-|
Do you
have an actualized version of this patch, that fit to actual git head?
No. I did not touch the subject since last year.
Second thing: In the list of HIDs (line 311-323 of your patch) is the
We'll have to be careful to make this transparent to the user.
Yes, this is the tricky part. I suspect we'd need standard names
for various fields, for example the search fields Digikey uses, and
figure out some backend rules for how various database chunks are
merged, etc.
But from the
On May 31, 2011, at 11:02 PM, Peter Brett wrote:
The attached script not only emits a message, but substitutes
attribute_conflict for the attribute in question. Since that's not
normally a legitimate value, it should help the user to detect the
problem.
From my
On 05/31/2011 04:26 PM, Thomas Oldbury wrote:
Double sided boards are great, but not so great when the product is
supposed to cost only $3/each, after an MSP430, mains power supply,
heatsink, triac etc.
You seem to have BOM'd out on that product...
On 05/31/2011 04:26 PM, Thomas Oldbury wrote:
Double sided boards are great, but not so great when the product is
supposed to cost only $3/each
What you really want is the high volume technique of using
carbon conductive ink traces and insulating layers silk screened on
and single copper
Thanks for your reply!
Am 01.06.2011 00:51, schrieb Kai-Martin Knaak:
Second thing: In the list of HIDs (line 311-323 of your patch) is the
gcode-HID missing.
The gcode HID is pretty new. First time I see it mentioned in the mailing
list is november 2009. Seems like it had not made it to the
33 matches
Mail list logo
