saving lbr files locally

[eric_engineer]

So this is annoying. I can't seem to save a .lbr file correctly anymore. I know I have done it in the past but this time the only way I could figure out to do it was to go to view on web and export it there.  But! It stripped out the urn for the step file, so I got the library but lost the model.

Where's the old way to export like save to my computer when you have a lib open?  And if that's gone how do I figure out the urn of my step.  I guess I'll have to manually edit it.

[jorge_garcia]

Hi @eric_engineer ,

Could you elaborate a little? Local libraries have never been able to store 3D assets without involving at least one managed library. Any particular reason you aren't just sticking to Fusion's cloud storage?

I'm going to run this by the team but I vaguely recall hearing that Fusion wouldn't work with local libs anymore. I'll get back to you.

Best Regards,

[eric_engineer]

Sure, you used to be able to save a copy of the lbr locally. You're right, it did not have the 3D file in it, but the urn that pointed to the 3d file stored in the cloud was there (not stripped) . That meant I could use that library as a template to quickly generate parts programmatically. Now I can't see a way to save the library locally anymore, that seems to be gone? And if you export it from the web the export strips the urn. I know it's still there because I spent a day getting around this by writing a library dump.upl that included the fully library with the urn.

We use these templates to get around having to painfully manually create each new resistor (or other parts) with all the parametric part data. So, we have scripts to take a digikey part number and automatically make a fully importable library for us that we suck into our resistor.lbr. With the 3D data stripped it means an extra step of opening the part, manually placing the model and saving which all takes time.

-Eric

[lauri_barnhart]

Hi @eric_engineer,

I wanted to check in and see if you still needed assistance, or if you found a solution to your question already? Let us know if you need further assistance by providing an update or if you have found a solution, please share it with the community so other members who may have the same question could learn from your experience.

All the best,

Lauri | Community Manager

[jorge_garcia]

Hi @eric_engineer ,

Thank you for explaining the use case. I guess what I'm struggling to grasp is why you can't run those scripts and ULPs within Fusion itself? Why export to a local library?

Really interested in knowing, we are actively developing the Python API for Fusion at which point even more options will materialize.

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

Best Regards,

[C.Nicks]

You may try making a copy from the cache file.

Open the library you want to export, then run the show_path.ulp to show the location. Navigate to that folder and the lbr will be there. Note that Fusion generates a unique path each time the files are opened.