topic Re: Feature Request: store parts datasheets in managed libraries in EAGLE Forum

Feature Request: store parts datasheets in managed libraries

Calvin — Wed, 03 Jan 2018 06:46:02 GMT

so I am loving the new managed libraries and the start of 3d part model integration. I think the next thing that would be truly great for me would be, being able to store the data sheet in the managed library linked to the parts. This would reduce my project data management, and if we could add an option in the info section to open the datasheet it would be incredibly handy when you need to verify something about a part mid design

I think this is just a logical extension of the new library design

Thank You

Calvin

Re: Feature Request: store parts datasheets in managed libraries

C.Nicks — Wed, 03 Jan 2018 07:00:37 GMT

Hi Calvin,
I think some sort of datasheet integration would be nice to have natively, although I do not personally use the managed libraries feature.

There is a very useful ulp written by Rachael Peterson called getDatasheet.ulp which opens any file link contained within a datasheet attribute. I've made it standard practice to add the datasheet attribute and links every time I create a new library part.

If you are using managed libraries or do not want to modify the libraries, you can add the attribute from either schematic or board editors.

Once the links are in there, opening the datasheet is as simple as right-clicking and selecting view datasheet.

This has been by far one of the most used ulps in my entire workflow.

Re: Feature Request: store parts datasheets in managed libraries

Calvin — Wed, 03 Jan 2018 07:43:04 GMT

this is an interesting solution, is it opening a locally saved file or a URL

I think the biggest reason I want them stored in the managed library is to that I don't have to deal with them begin stored locally, so if I wipe out a system I do not lose them, and if they are stored as referenced urls, I either need to then host them myself or hope the vendor never changes the link 🙂

it is good to know there are ulps for this, but I want to see if we can push autodesk to consider it as a native feature

I have pushed for and seen Fusion 360 take ideas from the user base and really run with them I am hoping eagle gets the same treatment, and maybe even its own idea station

Re: Feature Request: store parts datasheets in managed libraries

rachaelATWH4 — Wed, 03 Jan 2018 11:31:44 GMT

@Anonymous wrote:

this is an interesting solution, is it opening a locally saved file or a URL

I think the biggest reason I want them stored in the managed library is to that I don't have to deal with them begin stored locally, so if I wipe out a system I do not lose them, and if they are stored as referenced urls, I either need to then host them myself or hope the vendor never changes the link 🙂

Hi Calvin,

You can store either a file reference, local network based URL or an external internet based URL in the DATASHEET attribute and my ULP will just open it up in the system default web browser browser. I personally choose to use an external URL because I want to make sure I am always looking at the latest version of the datasheet and these days the main manufacturers are pretty good with maintaining consistent links to datasheets, although that's not to say broken links won't happen, they likely will at some point. If I were inclined I would add some sort of caching proxy server into the middle of it so then my URL might be http://my.proxy.local/getdatasheet.php?url="http://url.to.desired.datasheet.pdf". I might try and implement something like that at some point as it's probably a good idea for the reasons you state.

@Anonymous wrote:

it is good to know there are ulps for this, but I want to see if we can push autodesk to consider it as a native feature

I have pushed for and seen Fusion 360 take ideas from the user base and really run with them I am hoping eagle gets the same treatment, and maybe even its own idea station

I'm not sure how this would work as a native feature. It would have to be in managed libraries but I personally don't use, and likely will not use these unless they change significantly as they don't work well with my workflow at all. In addition, to do this Autodesk would end up having to cache and maintain links to datasheets and also possibly manage checking for updates from the manufacturers. I think it's likely a bit dangerous as an out of date datasheet with wrong/misleading information could lead somebody into a faulty design and then who's fault would that be? Theirs for not checking for the latest manually? Autodesk's for not maintaining their cache and ensuring the latest version? The manufacturer for not informing people of the change? For me the only solution is to take responsibility personally to ensure that I am using the correct and latest versions of data sheet and this means controlling datasheet management locally.

I agree that an idea station for EAGLE would be useful, lots of things get lost in the noise when the only place ideas can get suggested is on a busy support forum. But to be fair to Autodesk, Jorge, Ed and several of the dev team are on here regularly and see most of the suggestions, and a number of suggestions that have been made have made it into a release.

Best Regards,

Rachael

Re: Feature Request: store parts datasheets in managed libraries

Calvin — Wed, 03 Jan 2018 15:31:47 GMT

I agree users own the final responsibility for making sure the data they are working from is current, in the case of adding data sheets to managed libraries the end users still own the person responsible to make sure there info is current. So there is really very little difference to me if this integrated in the local libraries vs the managed libraries. The naming on the managed libraries might be a little misleading, in this case I am specifically thinking of the "my managed libraries", which is really just a local library stored in the cloud.

if the companies that are actually providing managed libraries for Eagle wanted to attached data sheets in there, I don't see a reason not to let them, I just don't think it would be a requirement so that is really a question of if they wanted to opt into another aspect of their parts they wanted to manage in the eagle managed libraries.

Calvin