On 09/01/2011 07:50 PM, Dan Roganti wrote:
I feel really, really stupid.
This is exactly what happened. There was another 7404-1.sym file
in my symbol path, an old one that I had created years ago, and it
was shadowing the "real" one, overriding it when the sheet was
On Wed, Aug 31, 2011 at 11:26 PM, Dave McGuire
<[1]mcgu...@neurotica.com> wrote:
On 08/26/2011 01:47 PM, Kai-Martin Knaak wrote:
I still get the correct result.
A stab in the dark:
Maybe you have a copy of 7404-1.sym somewhere on your hardware that
actually
is a
On Tue, Aug 23, 2011 at 11:20 PM, John Doty <[1]j...@noqsi.com> wrote:
On Aug 23, 2011, at 8:45 PM, Dave McGuire wrote:
> In any event, I've tried all combinations, and I still get the same
behavior. This is with v1.6.2.20110115. This is repeatable here,
using symbol 7404-1 from
Dave McGuire wrote:
> Thank you for your
> assistance, and I apologize for the distraction.
No worries. You are not the first to see ghosts when looking in
the wrong direction...
---<)kaimartin(>---
--
Kai-Martin Knaak
Email: k...@familieknaak.de
http://pool.sks-keyservers.net:11371/pks/lookup
On 08/26/2011 01:47 PM, Kai-Martin Knaak wrote:
Here's the procedure:
- start gschem (v1.6.2.20110115)
- open library, select symbol "74-series logic/7404-1"
- place two instances on sheet
<..snip..>
- load file "test.sch"
- note two inverter instances replaced with entir
Dave McGuire wrote:
> Here's the procedure:
>
>- start gschem (v1.6.2.20110115)
>- open library, select symbol "74-series logic/7404-1"
>- place two instances on sheet
<..snip..>
>- load file "test.sch"
>- note two inverter instances replaced with entire-package symbols
I st
On Aug 26, 2011, at 12:28 AM, Dave McGuire wrote:
> On 08/23/2011 11:20 PM, John Doty wrote:
>>> This seems like a pretty serious issue; can anyone shed a little light on
>>> it?
>>
>> Absolutely mysterious. I've never seen behavior like this and I cannot
>> reproduce it using your procedure.
On 08/23/2011 11:20 PM, John Doty wrote:
This seems like a pretty serious issue; can anyone shed a little light on it?
Absolutely mysterious. I've never seen behavior like this and I cannot
reproduce it using your procedure.
Very odd. See the click-by-click procedure in my other respons
On 08/24/2011 09:43 AM, Kai-Martin Knaak wrote:
In any event, I've tried all combinations, and I still get the same
behavior. This is with v1.6.2.20110115. This is repeatable here, using
symbol 7404-1 from the default installed library.
Can you compile a step-by-step description of what y
Dave McGuire wrote:
>> You should promote the slot attribute for both instances.
>
>Even though slot #1 defaults to 1?
>
>In any event, I've tried all combinations, and I still get the same
> behavior. This is with v1.6.2.20110115. This is repeatable here, using
> symbol 7404-1 from
On Aug 23, 2011, at 8:45 PM, Dave McGuire wrote:
> On 08/22/2011 07:45 AM, Kovacs Levente wrote:
>>>I open up a new schematic, place two instances of 7404-1, edit the
>>> attributes of the second one, promote the "slot" attribute, edit the
>>> newly-accessible one, change it to "2", save it,
On 08/22/2011 07:45 AM, Kovacs Levente wrote:
I open up a new schematic, place two instances of 7404-1, edit the
attributes of the second one, promote the "slot" attribute, edit the
newly-accessible one, change it to "2", save it, save the sheet, exit
gschem, restart, and load the sheet.
I
Dave McGuire wrote:
>I open up a new schematic, place two instances of 7404-1, edit the
> attributes of the second one, promote the "slot" attribute, edit the
> newly-accessible one, change it to "2", save it, save the sheet,
^^^
On Fri, 19 Aug 2011 23:55:49 -0400
Dave McGuire wrote:
>I open up a new schematic, place two instances of 7404-1, edit the
> attributes of the second one, promote the "slot" attribute, edit the
> newly-accessible one, change it to "2", save it, save the sheet, exit
> gschem, restart, and l
I think I'm doing something dumb. I've never used gschem's slotting
functionality before; I've always drawn my schematics with the entire
package. But I'm trying it now, it's doing something unexpected, and
I'm sure it's just me doing something wrong.
I open up a new schematic, place t
Stefan Salewski wrote:
> On Sun, 2009-06-28 at 09:18 -0700, Dave N6NZ wrote:
>> Yes. IMHO, power pins clutter functional drawings. I like to isolate
>> functional I/O from infrastructure I/O using two different symbols so
>> that they can be placed on different sheets.
> [...]
>> I believe this
> This can only fix the special case of slotted symbols with power pins.
> However, the more general case that needs to be solved, is a component
> that is associated with several different symbols. This is the case if
> power pins are dealt with a separate symbol, or if a large component is
> divi
On Sun, 2009-06-28 at 09:18 -0700, Dave N6NZ wrote:
>
> Yes. IMHO, power pins clutter functional drawings. I like to isolate
> functional I/O from infrastructure I/O using two different symbols so
> that they can be placed on different sheets.
[...]
>
> I believe this style leads to the most
Duncan Drennan wrote:
> Currently the symbol slotting functionality struggles to handle power
> pins well (at least that is what some brief googling showed). A
> recurring theme with regards to slotting is that power pins show up on
> all the slots, e.g. dual/quad opamp which has a single set of p
On Sun, 28 Jun 2009 15:32:14 +0200, Duncan Drennan wrote:
> I had a thought which might solve both of these issues. If a special
> character was defined for slotting which indicated that the pin should
> be excluded from the schematic that character could be used in place of
> the power pin slot.
Currently the symbol slotting functionality struggles to handle power
pins well (at least that is what some brief googling showed). A
recurring theme with regards to slotting is that power pins show up on
all the slots, e.g. dual/quad opamp which has a single set of power
pins for each of the opamp
On Jan 17, 2009, at 6:16 PM, DJ Delorie wrote:
>
> The idea I had a while back was to use symbolic pin names in the
> symbols, and map symbolic pin names to physical pin numbers as part of
> the "heavyification" of the symbol. The physical pin numbers are
> added to the symbol at that point. Th
On Jan 17, 2009, at 5:44 PM, Peter Clifton wrote:
> I don't
> like the fact that libgeda's core code "understands" the slot=
> attribute
> in so many places (and does lots of kludgy in-schematic
> manipulation of
> pinnumbers).
Very good point.
John Doty Noqsi Aerospace, Ltd.
DJ Delorie wrote:
> The idea I had a while back was to use symbolic pin names in the
> symbols, and map symbolic pin names to physical pin numbers as part of
> the "heavyification" of the symbol. The physical pin numbers are
> added to the symbol at that point.
That's exactly how my uEDA handle
The idea I had a while back was to use symbolic pin names in the
symbols, and map symbolic pin names to physical pin numbers as part of
the "heavyification" of the symbol. The physical pin numbers are
added to the symbol at that point. The syntax for slots would be
expanded, to allow for multipl
On Sat, 2009-01-17 at 17:11 -0500, John Doty wrote:
> The old mechanism could be left in place. Many, including me, would
> scream if it changed. If the slot is defined by slotdef=, it's old
> style, by slotfile=, it's new style.
I'd quite like to see the current slot handling C code ripped o
The current implementation of slotting in gEDA is confusing and
inflexible.
It overloads the pinseq= attribute, which is also used to order pins
for SPICE netlisting.
It does not work when the slots are heterogeneous. This, in turn,
either requires hidden power pins or redundant power pins
On Fri, Nov 7, 2008 at 5:44 PM, Kai-Martin Knaak <[EMAIL PROTECTED]> wrote:
> On Fri, 07 Nov 2008 12:37:30 +0100, Stephan Boettcher wrote:
>
>> Why do you want power symbols?
>
> Analog circuits require dedicated capacitors at the power pins.
I agree.
In analog IC design (this is my field) things
Kai-Martin Knaak wrote:
> On Fri, 07 Nov 2008 12:37:30 +0100, Stephan Boettcher wrote:
>
>> Why do you want power symbols?
>
> Analog circuits require dedicated capacitors at the power pins.
>
Yes. I am lucky that I have a good layouter, he will place bypass caps
very strategically. But when y
On Fri, 07 Nov 2008 12:37:30 +0100, Stephan Boettcher wrote:
> Why do you want power symbols?
Analog circuits require dedicated capacitors at the power pins.
---<(kaimartin)>---
--
Kai-Martin Knaak tel: +49-511-762-2895
Universität Hannover, Inst. für Quantenopt
Bernd Jendrissek wrote:
On Wed, Nov 5, 2008 at 8:06 PM, Joerg <[EMAIL PROTECTED]> wrote:
When you place, say, a LM324 as the seventh chip it will plop down U7A.
What do you mean "place ... as the seventh chip"? Do you mean when
you place your 25th opamp symbol that happens to be realized as 1
DJ Delorie <[EMAIL PROTECTED]> writes:
> There are two options:
>
> option 1: create two gate symbols, one with power leads and one
> without. Both have the same slotting info.
>
> option 2: create one slotted gate symbol with no power info, and a
> second box symbol with just power info. This
On Nov 5, 2008, at 11:32 AM, Stefan Salewski wrote:
> One question to the professional:
> Are hidden power pins really useful today?
It depends on the design. Sometimes I do a board where all of the
74XX logic runs on 3.3V. In that case, explicit power is a
distraction, so just connect the i
On Wed, Nov 5, 2008 at 8:06 PM, Joerg <[EMAIL PROTECTED]> wrote:
> When you place, say, a LM324 as the seventh chip it will plop down U7A.
What do you mean "place ... as the seventh chip"? Do you mean when
you place your 25th opamp symbol that happens to be realized as 1/4 of
a LM324?
How does E
Peter Clifton wrote:
> On Wed, 2008-11-05 at 16:44 -0800, Joerg wrote:
>> Peter Clifton wrote:
>>> On Wed, 2008-11-05 at 09:33 -0800, Joerg wrote:
Bernd Jendrissek wrote:
> [snip]
>
>> That is tough to understand for a non-programmer like me. If this means
>> that you can add power symbols o
On Wed, 2008-11-05 at 16:44 -0800, Joerg wrote:
> Peter Clifton wrote:
> > On Wed, 2008-11-05 at 09:33 -0800, Joerg wrote:
> >> Bernd Jendrissek wrote:
> >
[snip]
> That is tough to understand for a non-programmer like me. If this means
> that you can add power symbols onto packages at the first
Peter Clifton wrote:
> On Wed, 2008-11-05 at 09:33 -0800, Joerg wrote:
>> Bernd Jendrissek wrote:
>
> [snip]
>
In
gschem you'd have to design a separate power pair for pretty much every
part that has more than one slot. Can be done but kind of messy.
>>> Not on my fork: you can hav
On Wed, 2008-11-05 at 09:33 -0800, Joerg wrote:
> Bernd Jendrissek wrote:
[snip]
> >> In
> >> gschem you'd have to design a separate power pair for pretty much every
> >> part that has more than one slot. Can be done but kind of messy.
> >
> > Not on my fork: you can have one power pair symbol t
> Ok. I'll have to try that from the command line. When using auto-number
> from within the GUI is overwrites instantations of slots which it shouldn't.
That's my point: There are several ways to number refdeses in gEDA.
The command line scripts are (arguably) more configurable and
powerful, wher
Stefan Salewski wrote:
> Am Mittwoch, den 05.11.2008, 10:06 -0800 schrieb Joerg:
>
>> Just as a suggestion, the way Eagle does this is quite ideal:
>>
>> you click
>> an invoke tab and the hidden power pins show up on the -A slot. But only
>> for the device you click after invoke, not all of the
Stuart Brorson wrote:
> Hi --
>
>>> Try using the utility "refdes_renum" on your schematic. This will number
>>> all the refdeses at once. (You need to close gschem first, and run
>>> this utility from the command line.) If you already have some
>>> refdeses numbered on your schematic, then th
Am Mittwoch, den 05.11.2008, 10:06 -0800 schrieb Joerg:
>
> Just as a suggestion, the way Eagle does this is quite ideal:
>
> you click
> an invoke tab and the hidden power pins show up on the -A slot. But only
> for the device you click after invoke, not all of them.
>
Sorry, have not follo
Hi --
>> Try using the utility "refdes_renum" on your schematic. This will number
>> all the refdeses at once. (You need to close gschem first, and run
>> this utility from the command line.) If you already have some
>> refdeses numbered on your schematic, then the default behavior of
>> refde
Stuart Brorson wrote:
>>> As long as each symbol for a physical chip has the same refdes, the
>>> netlister knows how to combine their pin numbers together.
>> Just tried it: Auto-number overwrites all this stuff. Every
>> instantiation gets a new refdes :-(
>
> Try using the utility "refdes_renum
Bernd Jendrissek wrote:
> On Wed, Nov 5, 2008 at 4:24 AM, Joerg <[EMAIL PROTECTED]> wrote:
>> Yes, I thought about that, having generic opamp blocks and scooting a
>> pair of "floating" power pins over the first instantiation of a two- or
>> four-pack. That is how it's done in Eagle if you don't wa
On Wed, Nov 5, 2008 at 4:24 AM, Joerg <[EMAIL PROTECTED]> wrote:
> Yes, I thought about that, having generic opamp blocks and scooting a
> pair of "floating" power pins over the first instantiation of a two- or
> four-pack. That is how it's done in Eagle if you don't want to create a
> new symbol (
>> As long as each symbol for a physical chip has the same refdes, the
>> netlister knows how to combine their pin numbers together.
>
> Just tried it: Auto-number overwrites all this stuff. Every
> instantiation gets a new refdes :-(
Try using the utility "refdes_renum" on your schematic. This
DJ Delorie wrote:
> There are two options:
>
> option 1: create two gate symbols, one with power leads and one
> without. Both have the same slotting info.
>
> option 2: create one slotted gate symbol with no power info, and a
> second box symbol with just power info. This lets you group all yo
DJ Delorie wrote:
> There are two options:
>
> option 1: create two gate symbols, one with power leads and one
> without. Both have the same slotting info.
>
> option 2: create one slotted gate symbol with no power info, and a
> second box symbol with just power info. This lets you group all yo
Mark Rages wrote:
> On Tue, Nov 4, 2008 at 7:42 PM, Joerg <[EMAIL PROTECTED]> wrote:
>> Sorry for asking a lot here lately but I believe others will hit this
>> snag as well and I could not find much info about it, not even via a web
>> search outside geda.seul.org:
>>
>> Often power pins must be m
There are two options:
option 1: create two gate symbols, one with power leads and one
without. Both have the same slotting info.
option 2: create one slotted gate symbol with no power info, and a
second box symbol with just power info. This lets you group all your
power connections in one pla
On Tue, Nov 4, 2008 at 7:42 PM, Joerg <[EMAIL PROTECTED]> wrote:
> Sorry for asking a lot here lately but I believe others will hit this
> snag as well and I could not find much info about it, not even via a web
> search outside geda.seul.org:
>
> Often power pins must be made visible. For example
Sorry for asking a lot here lately but I believe others will hit this
snag as well and I could not find much info about it, not even via a web
search outside geda.seul.org:
Often power pins must be made visible. For example if you have to filter
the supply for digital parts or opamps separately
El jue, 02-11-2006 a las 22:17 -0500, Ales Hvezda escribió:
> [snip]
> >None of these work for me. I'm not sure how to use the Edit/Slot...
> >function - it doesn't even seem to change the slot attribute value
> >(select component, choose Edit/Slot..., change value of slot in dialog).
> >The dialog
> That's bizarre. Can anybody else reproduce this behavior?
> On my box, I select the component, pick Edit/Slot..., type in the
> new slot number (2 for a 7474-1), hit okay, and boom, I get the pins
> to change.
Weird. I just tried it again to make sure I wasn't going crazy. Here's
what
[snip]
>None of these work for me. I'm not sure how to use the Edit/Slot...
>function - it doesn't even seem to change the slot attribute value
>(select component, choose Edit/Slot..., change value of slot in dialog).
>The dialog box changes the slot attribute value but doesn't update the
>pins.
ef" attributes, you can edit your component and use the
template from the picture.
For more than one slot, simply define one more.
Adrian
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of John Griessen
Sent: Thursday, November 02, 2006 6:32 AM
To: gEDA us
Hi John,
On Thursday 02 November 2006 15:32, John Griessen wrote:
> When creating a slotted symbol,
>
> How do you use slotdef attribute? I have not found creating a
> slotted symbol in the gschem manual
The symbol creation guide is here:
http://geda.seul.org/wiki/geda:scg
And the attributes l
> However, if you change the slot number using either Edit/Slot...
> or by double clicking on the component and using the multiple attribute
> edit dialog box, then the slot number should update correctly.
None of these work for me. I'm not sure how to use the Edit/Slot...
function - it doe
When creating a slotted symbol,
How do you use slotdef attribute? I have not found creating a slotted symbol
in the gschem manual
John G
Ales Hvezda wrote:
if you change the slot number using either Edit/Slot...
or by double clicking on the component and using the multiple attribute
edit d
>I seem to be having slotting problems with gschem. If I add a 7474
>component, for instance, and change its slot number to 2, the pin
>numbers don't update. In the gschem log I see:
>
How are you changing the slot number? If you change the slot
number by directly editing the slot= attrib
I seem to be having slotting problems with gschem. If I add a 7474
component, for instance, and change its slot number to 2, the pin
numbers don't update. In the gschem log I see:
Opened file [/home/des0prb/geda/share/gEDA/sym/74/7474-1.sym]
numslots attribute missing
Slotting not allowed for this
62 matches
Mail list logo
