kicad-developers team mailing list archive

[André S. <list.dev.kicad@xxxxxxxxxxxx>]

The approach with "power" components sounds like a really good way to handle this (I think that should be put into the documentation as a tip). I always felt power flags a hack, thanks for the confirmation. ;)
In a design there are not so many places where you provide power and there are not so many components you can put in the power path. 
Also using dedicated symbols reminds you that these components must be chosen with special care. 

  André 

On February 7, 2016 4:40:51 AM GMT+01:00, Jeff Barlow <jeff@xxxxxxxxxx> wrote:
>I agree with Andrew's approach. Power flags are just a hack to suppress
>
>a valid error message. If there's a power flag on a net ERC will still 
>be happy even after you accidentally delete the component that actually
>
>supplies the power.
>
>On 02/06/2016 06:14 PM, Andrew Zonenberg wrote:
>> It still works if you adopt the approach fully. I make separate
>> components "POWER_INDUCTOR" etc that have one terminal a power input
>> and the other a power output.
>>
>> On 06/02/16 09:55, André S. wrote:
>>> >This may work when the output is directly connected to the net. But
>>> >if you have some output/input filter behind it this will not work
>>> >as expected, you still need the power flag then.
>>> >
>>> >André
>
>-- 
>Later,
>Jeff
>
>_______________________________________________
>Mailing list: https://launchpad.net/~kicad-developers
>Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx
>Unsubscribe : https://launchpad.net/~kicad-developers
>More help   : https://help.launchpad.net/ListHelp