Oliver,
I have concerns about greying out the part and being able to see any change
when printed in B&W. This may be why Altium used a big "x", and why the
tools I regularly use also allow an "x" or removing the DNI (I'm most
familiar with this acronym) part.
Another thing to consider is the abil
Oliver,
On 11/26/2018 4:03 AM, Oliver Walters wrote:
> I'd like some direction from a project leader on how I should progress,
> rather than wasting my efforts:
>
> 1. Adding "DNP" option to schematic components.
>
> This can be achieved now, without breaking the .sch file format. It
> allows co
Hi Oliver,
>
>
> I think we need to fit this in with the existing PCBNew Attributes stuff
> (“attr” in the file format). We currently have through-hole, SMD and
> virtual (the later being similar to DNF/DNP), but a lot of folks have found
> that too limiting for various reasons. I suspect this me
Just a reminder, we already have a properties token for key/value pairs.
Key/value pairs are provided for use by third party tools and are not
used internally. All internal functionality must be implement as valid
file tokens. Also keep in mind that one of the goals of kicad file
formats is to b
su 25. marrask. 2018 klo 20.25 Jeff Young (j...@rokeby.ie) kirjoitti:
>
>
> I think we need to fit this in with the existing PCBNew Attributes stuff
> (“attr” in the file format). We currently have through-hole, SMD and
> virtual (the later being similar to DNF/DNP)
>
I have always found "virtua
Along these lines, we should probably figure out what attributes/properties
KiCad should store as rigidly-defined fields/data members rather than a
more flexible (key/value) system.
>From what I can tell, some of the commercial EDA software I have used
treats almost everything as an "attribute" in
Hi Oliver,
I think we need to fit this in with the existing PCBNew Attributes stuff
(“attr” in the file format). We currently have through-hole, SMD and virtual
(the later being similar to DNF/DNP), but a lot of folks have found that too
limiting for various reasons. I suspect this means we n
I've often seen "NC" used to mean "no connect" which usually is the "X"
symbol you put on pins to prevent ERC warnings.
DNP is also the one I've seen the most. I actually have heard from a
(US-based) assembly vendor that DNP is the most common, DNI is next after
that, and all other options are way
>In the files I have used "DNF" or "fitted" - what should the accepted
nomenclature be here? I've seen DNF / DNP / NC and other examples used. I'd
like to get some clarity on what I should use going forward.
By far I've always seen DNP in mass usage. "Do not populate". I've seen
"NC" less often f
Frank,
That's a good idea,I hadn't thought of that. I'll add it to my working
document.
Cheers,
On Sun, 25 Nov 2018, 20:00 Hi Oliver
>
> This looks very nice! A plot option to disable DNF components in paste
> layer would be nice
>
>
> 25. nov. 2018 05.38 skrev Oliver Walters :
>
> A feature I
Hi OliverThis looks very nice! A plot option to disable DNF components in paste layer would be nice 25. nov. 2018 05.38 skrev Oliver Walters :A feature I feel has been missing from KiCad is the ability to mark parts as "DNF" (Do Not Fit) so they are excluded from assembly files (BoM / PnP / etc).Ma
su 25. marrask. 2018 klo 6.38 Oliver Walters (oliver.henry.walt...@gmail.com)
kirjoitti:
>
>
>- (Eventually) ability to switch between assembly variants in PCBNEW
>
>
We regularly need several independent variants in the same board. For
example two different regulators for different kinds of
12 matches
Mail list logo
