Libraries are making my head spin

[robert_pellegrino]

I am very confused about how parts libraries work.  I just want to create a simple component using the files from Mouser.  One of the facets that is tripping me up is the difference between local libraries on disk, vs the Fusion Team libraries.  I get lost in the maze of which library am I editing, and where does it live, and what needs updating or uploading, or...

Why do I have 2 versions of libraries, only one of which can be edited?  Can someone suggest a straightforward workflow where I just open 1 file, edit a footprint, then save it?  I don't care if I have to eliminate local libraries. or eliminate Fusion Team libraries, or whatever.  I just want this seemingly simple task to be simplified.

[jorge_garcia]

Hi @robert_pellegrino,

If I recall correctly, mouser provides parts in a format for the Samacsys tool they've partnered with. This is currently not available for Fusion which is creating much of the confusion is since you have to use a local EAGLE library and then link that to a Fusion Team library and keep track between the two.

The best recommendation I can give is to not use the files from Mouser and use one of the supported part services for Fusion either UltraLibrarian or SnapMagic (Formerly SnapEDA). They do the same thing as the Samacsys tool and are integrated into Fusion. You can get them from these two links

https://apps.autodesk.com/FUSION/en/Detail/Index?id=5446990520022318629

https://apps.autodesk.com/FUSION/en/Detail/Index?id=8116232332146395670

Let me know if there's anything else I can do for you.

Best Regards,

[robert_pellegrino]

Neither of those tools has the parts that I need, nor would they match the simplicity of the Mouser->samacsys->schematic workflow.  What would be required to make this work the way it did in Eagle?

[jorge_garcia]

Hi Robert,

The way you worded that gives me the impression that you didn't try either tool, but that's beside the point. 

To get this to work the way it did in EAGLE would require Samacsys to make a new plugin to properly support Fusion. The impetus is truly on them to do it, the tools are all there. You could try working around it by having the Samacsys tool generate a local EAGLE library and then constantly uploading it to Fusion, but that's so messy I hesitate to recommend it.

My original recommendation still stands. There is also always the option to create the part yourself. Then there is no concern about the accuracy of a part or it's provenance.

Let me know if there's anything else I can do for you.

Best Regards,