[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: gEDA-user: New User Questions.
Hi Ales,
El miÃ, 07-12-2005 a las 20:49 -0500, Ales Hvezda escribiÃ:
> >I have tried to read the howtos available and browse the web based
> >digests of this mailing list. However I still cannot see what I am
> >failing to do in getting these errors. Attached is the circuit and the
> >errors reported from the following command line entry.
> >
> >gnetlist -g drc2 circuit_1.sch -o results.txt
>
> You are using the drc2 backend on a spice netlist. This will
> mostly work, but there will be errors like the ones you got.
>
> I'm considering removing that "Remember to check that your
> schematic has no errors..." gnetlist output message because it is not
> helping but rather confusing people.
>
The backend drc2 should also be able to check spice netlists. The only
problem is that the pintype attribute should be defined in the symbols.
As an example, I can get the given schematic free of errors if add the
pintype attribute to the resistor-1.sym symbol. The attached diff is:
--- resistor-1.sym 2005-12-09 00:44:23.190889841 +0100
+++ resistor-1.sym 2005-12-09 00:45:50.639429341 +0100
@@ -13,6 +13,8 @@
pinnumber=2
T 800 150 5 8 0 0 0 0 1
pinseq=2
+T 800 150 5 8 0 0 0 0 1
+pintype=pas
}
P 0 100 152 100 1 0 0
{
@@ -20,7 +22,10 @@
pinnumber=1
T 100 150 5 8 0 0 0 0 1
pinseq=1
+T 100 150 5 8 0 0 0 0 1
+pintype=pas
}
+T 100 150 5 8 0 0 0 0 1
L 201 200 150 100 3 0 0 0 -1 -1
T 200 300 8 10 1 1 0 0 1
refdes=R?
I think that the user should always have a verification tool (the drc2
backend in this case) to search for possible errors and validate the
schematic, no matter what kind of netlist he will be using. In order to
do this painfree, some symbol work is needed (adding the pintype
attribute). I think it's worth to do it.
gsymcheck reports a warning if the pintype attribute is not set in the
symbol... why not look at the warnings and set that attribute when doing
the symbol?
Regards,
Carlos