I am not clear about the function of embedded files? What is their purpose? They explain it in this quote,
Continuing the discussion from Post-V8 New Features and Development News:
I fail to understand the usefulness of this.
In the screenshot you showed, you have a footprint properties window open. One easy use for embedded files would be to embed 3D models into the footprint, so that you don’t have to reference an outside folder that could vary between users. For the schematic symbols, a similar embedding process for simulation models would also make sense. Not sure if embedding datasheets would make sense (since normally I want them downloaded elsewhere too) but maybe for some people’s workflow).
Do you mean that the file, say a 3d model is saved along with the project?
Yes, saving a 3D model in the actual footprint file (which is in turn cached inside the layout file for easy sharing). You could certainly do this another way (and people already do) by being careful to collect all the project-related 3D models into the project/library folder so that the file paths are all relative, rather than absolute. The file embedding just takes that a step further.
1 Like
At the moment a lot of schematic symbols in KiCad have links to external sites for datasheets, and that is nice to have. But when I use an IC in a project, I always download the datasheets, and make them part of the project, because you never know when those external links to the 'net break. And when I archive my project, I still want it to be complete after 20 years.
I’m not sure though whether I would want to embed the datasheets into the symbols, or keep them in a separate directory as I do now. Being able to look at the datasheets without starting KiCad first also has it’s advantages.
In my company we work with a centralized repository of footprints, symbols and 3D models.
We still manage the data sheet through a link, if it breaks, I look for another route.
As for footprints, we all try to have the latest version of the repository.
KiCad has support for different kinds of preferences and workflows.
If you are working with database driven libraries (mostly companies), then embedding files into symbols or footprints does not make much sense.
If you are a hobbyist, and you want to archive a project as complete as possible, then embedding datasheets and 3D models can be an interesting option. I have not looked into this though. If it means that every (same size) footprint has it’s own embedded 3D model then it would be unmanageable.
1 Like
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.