[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Bug-gnucap] Fw: gnucap bug
From: |
al davis |
Subject: |
Re: [Bug-gnucap] Fw: gnucap bug |
Date: |
Fri, 7 Mar 2008 20:31:37 -0500 |
User-agent: |
KMail/1.9.9 |
On Thursday 06 March 2008, Ron Peters wrote:
> I guess that attachments don't work in this forum.
Non-text attachments are removed. "base64" attachments are
non-text, even if the file contains text. Some other types of
files that are really text may be rejected because the
mime-type is not text.
Also, HTML postings and postings with any attachments are held
for moderation.
This is necessary to keep spam off of the list.
> I want H1, H2 and H3 in XAF7 to use R1, R2 and R3 in XAM4 as
> current sensors.
>
> Here is the netlist:
I cut it down a bit...
> .subckt AM4 1 2 3 4 5 6
> R1 1 4 0
> R2 2 5 0
> R3 3 6 0
> R4 1 0 1e12
> .ends
> *Probe 1
> XAM4 31 32 33 41 42 43 AM4
>
> .subckt AF7 1 2 3 4 5 6 7 8 9
> H1 70 0 R1.XAM4 1.04186
> H2 80 0 R2.XAM4 1.04186
> H3 90 0 R3.XAM4 1.04186
> .ends
> XAF7 41 42 43 51 52 53 61 62 63 AF7
>
There is no XAM4 in .subckt AF7. The current probe must be in
the same scope. You have XAM4 in the global scope.
Then ... Current probes cannot use hierarchical names. It must
be local to the scope.
You cannot make unstructured connections by hierarchical node
names. All connections must be made through the port list.
This is by design, so its working as intended. If you want to
propose it on the developer list, you can raise the question of
whether this is the correct design.