Le 13/10/2014 16:51, Carl Poirier a écrit :
Benoît, this is exactly what I tried to say. I wasn't talking about
symbols in Altium, but about components.
They are already associated with footprints and so on, thus making
them components.
They can be not associated and still used...
Here a view of the schematic editor, with the library panel open and a
totally empty component selected.
Here is a view of the schematic library list in the schematic library
editor. Notice all the fields:
The models linked can be a footprint, a simulation model, an ibis model
and a signal integrity model. You can add several footprints for one
component which is useful for N, M, L IPC densities and generic components.
The drawing that we are working on in the schematic library editor is
a symbol.
This is where I don't agree.
You are indeed drawing a symbol, but mostly you will also set other
proprieties making it a component. It doesn't need to have a footprint.
For example, an ATMega128rfa1 is a component, not a symbol.
In the component properties, we can only put a filter on footprints
for it, but AFAIK, that's about it.
So I'd say it still stands as a symbol.
If some more pairing is going to be done in this editor, such as a
unique footprint, a SPICE model, and so on, then we might as well call
the editor a component editor.
I totally agree with this. The name Component Editor is ambiguous in
this context and shouldn't be used here at all, never. I see a
/Component editor/ like an editing tool for both the schematic component
and the footprint in the same time, and store the resulting footprint
privately attached to the component to avoid corrupting the other
component using the same base footprint.
I think the editor should be called /Schematic Library Editor/, to
explicitly say that what you edit is for eeschema. The footprint editor
should be called /PCB Library Editor/ to keep consistancy. In fact those
are the name altium folks choosed.
But what if it's used to create only a symbol?
I will take this example: PCB Libraries can contain things that are not
footprint (fiducials, holes...). But footprints are not called PCB Features.
[off topic]
Also, Eeschema should have a method for adding logos or other stuffs (I
think it has), and these elements shouldn't be added in a schematic the
same way a component is added. You may not store these graphical items
in a schlib. You don't want the logo of you company to appears in BOM
component list, you just want it in your printings.
Also, and this is important: you may put in the schema every objects
that will become physical or logical parts of the project (the pcb, the
box, screws, cables...). Some electronic engineer even put the firmware
version in the schematic which is very smart and would have saved me a
lot of time if I knew that when I started. I even burned down a mcu
because of wrong version. Now, you want to upload some code but don't
remember what is what, well IT'S IN THE BOM, YAY :D.
This is good design practice.
Components that aren't implantable (screws, box, fiducials) are marked
NI in the BOM (not implantable) for the PCB assemblers to know it's not
their business.
[/off topic]
Furthermore, how would the symbol and component libraries be
differentiated, once some more serious associations are done? Will
they all be mixed together? I think that's also part of the problem.
I don't know what is planned about this, but I would strongly support a
2 libraries system based on what already exists, with an All-in-one
schematic library containing the abstracts schematics datas of a
component (symbol, simulation model, link to footprint) along with a
All-In-One PCB library containing the real world PCB datas (footprint,
3d model). A component like a screw for example is very easily used in
the whole project. A third library would be useful to make footprints
private and pre linked to a schematic component, but it's a pain in the
ass using and managing them (Altium daunting system). I don't recommend
it, there should be better solutions no one has found yet. The project
library is a good feature for this :)
On Mon, Oct 13, 2014 at 8:10 AM, Benoît Roehr
<benoit.roehr...@gmail.com <mailto:benoit.roehr...@gmail.com>> wrote:
In KiCAD each project can have its own library of footprints,
so this idea duplicates, that exist already.
OK thanks ! I did not know about it before :)
Le 13/10/2014 13:21, LordBlick a écrit :
In response to a message written on 13.10.2014
<tel:13.10.2014> 12:04, from Benoît Roehr:
Le 13/10/2014 11:40, LordBlick a écrit :
In response to a message written on 13.10.2014
<tel:13.10.2014> 08:01, from Benoît Roehr:
For kicad, it could be a good thing to be able to
embed a single footprint to a
component if the footprint is really special, but
it's non sens if you can
appropriately tag the footprint and put it with
the others.
There is a special field to assign footprint to
schematic element…
Yes i know, I was meaning if you need a very special
footprint just for one
component, you may not want to pollute your existing
pcblibrary with this
footprint. For example, you have just one component
packaged in a 2 rows QFN
package. You don't want this in your standard QFN lib.
So the ability to attach a single footprint directly to
the component without
creating or modifying a PCBLib can be useful.
But it is new feature and it doesn't have to be
implemented yet. Not important.
Footprint have to be well named, and all searchable in the
same place, not
hidden. ;) More important for me would be a footprint
preview in schlib editor.
In KiCAD each project can have its own library of footprints,
so this idea
duplicates, that exist already.
_______________________________________________
Mailing list: https://launchpad.net/~kicad-developers
<https://launchpad.net/%7Ekicad-developers>
Post to : kicad-developers@lists.launchpad.net
<mailto:kicad-developers@lists.launchpad.net>
Unsubscribe : https://launchpad.net/~kicad-developers
<https://launchpad.net/%7Ekicad-developers>
More help : https://help.launchpad.net/ListHelp
_______________________________________________
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help : https://help.launchpad.net/ListHelp
