Brian Sidebotham wrote:
> 2009/4/18 Joerg <[email protected]>:
>> Andy Eskelson wrote:
>>> Have you tried selecting part A, in the lib editor and unticking the
>>> common to units option for pins 4 and 11.
>>>
>> Yes, that's AFAIR the only way in Kicad to make parts with supplies that
>> only show on the A-unit.
>>
>>
>>> That appears to give you power pins on part A, and nothing on parts B=D
>>>
>>> A quick sctatch circuit with 4 parts gives no DRC errors when used that
>>> way.
>>>
>> Now place them in a way that U?B is somewhere near the upper left, U?A
>> somewhere in the middle, U?C below, U?D to the right and then click
>> "Annotate". That's when the connections break.
>>
>> --
>> Regards, Joerg
>>
>> http://www.analogconsultants.com/
> 
> Hi Joerg,
> 
> Unfortunately this is the current behaviour of Kicad. It is I'm sure a
> bug, although I've never issued a bug report in the bug tracker
> http://sourceforge.net/tracker/?atid=762476&group_id=145591&func=browse
> 
> It might be worth you submitting a bug report to get this behaviour fixed.
> 

Done :-)


> I think Kicad should respect the unit part of the annotation. It
> should only annotate the ? section of the reference designator.
> 
> I found this particularly broke my schematic when I had a two-part
> switch which had one LED symbol unit and one switch symbol unit. When
> I annotated for the first time a lot of symbols changed units.
> 

I tacked that on in my bug report by mentioning your input. The same 
would happen if you'd purposely select A and B for a sensitive 
symmetrical mixer and part of the desired symmetry and tracking goes out 
the window if that turns to A and C. When crosstalk gets involved it can 
become particularly ugly.


> For now, it is best to hand annotate multi-unit schematic symbols.
> 

I'll stay with Eagle for now. Kicad has the huge advantage over Eagle in 
that it allows a hierarchical design. However, besides the bug in this 
thread I also became a bit scared when I changed an alias and suddenly 
it messed up components in the schematic that came from another library. 
I think components should be embedded in a schematic (like Eagle does 
that) but this is a major SW-architectural difference. So before 
switching I'd have to figure out a way to lock in library parts per 
project somehow, without having to copy tons of components.

-- 
Regards, Joerg

http://www.analogconsultants.com/

Reply via email to