> Well, I am human! Therefore, when something try to NOT LET ME do
> things, I tend to struggle :) It works when I turn the DRC off, but
> it looks messy, and then I loose the isolation check and the comfort
> of the isolation zones delimited. That's why I would like to keep the
> DRC on...

You can't have DRC without a netlist, because the netlist is what tells 
PCBNew what can and can't be connected.   You can create a netlist 
manually (it's a text file), but the quickest, easiest, most reliable 
way to generate a netlist is with a schematic editor.   I create a 
schematic even for very simple boards because it allows me to leave DRC 
on, ensuring my board is neat and correct first time.   If the schematic 
is purely being used as a means of generating a netlist and I don't have 
the exact component in the library, I save time by improvising with 
something similar (because PCBNew only cares about footprints and 
connectivity, not electrical properties).

I used to use ISIS, and churned out one scrap board after another. 
Since using Kicad (with DRC on) that no longer happens.   Kicad is a far 
better tool for producing boards, but only if you don't force it to 
behave like obsolete software.

Regards,

Robert.

>
> I don't see how I could make a netlist without drawing a schematic
> first?
>
> Axel
>
>
> --- In [email protected], Cat C<catalin_c...@...>  wrote:
>>
>>
>> Did you turn DRC off?
>>
>> That's the purpose of DRC, to NOT LET YOU do things that are not in
>> the netlist (among other things).
>>
>> If you don't want to make a schematic, make a netlist.
>>
>>
>>
>> Cat
>>
>>> To: [email protected] From: mad...@... Date: Fri, 20
>>> Aug 2010 23:40:39 +0000 Subject: [kicad-users] Re: Type Err(4)
>>> trace near pad issue in Kicad
>>>
>>> Well, I made a simple schematic with EEschema, passed the
>>> electrical check without trouble, made the netlist, did the CVpcb
>>> thing, and routed in PCBnew. All is fine, so my Kicad build seems
>>> to be working.
>>>
>>> I tried to add another module in the pcb. Fine. I tried to
>>> connect the new module with a trace... Type Err(4)! It doesn't
>>> agree to connect the trace to the new component.
>>>
>>> I still don't understand why I cannot route manually without a
>>> schematic or a netlist when the faq says I could?
>>>
>>> Axel
>>
>
>
>
>
> ------------------------------------
>
> Please read the Kicad FAQ in the group files section before posting
> your question. Please post your bug reports here. They will be picked
> up by the creator of Kicad. Please visit http://www.kicadlib.org for
> details of how to contribute your symbols/modules to the kicad
> library. For building Kicad from source and other development
> questions visit the kicad-devel group at
> http://groups.yahoo.com/group/kicad-develYahoo! Groups Links
>
>
>
>
>
> No virus found in this incoming message. Checked by AVG -
> www.avg.com Version: 9.0.851 / Virus Database: 271.1.1/3083 - Release
> Date: 08/20/10 07:35:00
>
No virus found in this outgoing message.
Checked by AVG - www.avg.com 
Version: 9.0.851 / Virus Database: 271.1.1/3083 - Release Date: 08/20/10 
07:35:00

Reply via email to