Actions
Forum Thread Details
  • Replies 8 replies
  • Subscribers 176 subscribers
  • Views 818 views
  • Users 0 members are here
Related

Is there a better search ULP

autodeskguest

 

I've been using eagle for about 2 weeks now and am very impressed.

I have been able to create my own component (package) first time with

very little difficulty and am finding the interface very usable

(contrary to advice I was given elsewhere)

 

My biggest problem however seems to be in component selection from

the extensive libraries.

 

Whilst I'm familiar with the obvious ones (3M Amphenol microchip etc)

when I come to select say a volatge regulator but dont

have the big names available locally - how can I search the entire

libraries for say "voltage regulator" to pull up makes I may never have

heard of?

 

Some libraries are named of course and can be searched after "USE [x}"

but others are not so obvious as to their content. Doing "use *" helps

but does mean confusing the in-use list.

 

Is there a better way to do this (if I have explained clearly enough)

 

It did occur to me to export the libraries to mySQL or similar somehow

but I dont know if there are license issues involved there.

 

 

 

Parents

  • Op Sun, 23 Sep 2012 13:06:08 +0200 schreef fred <email@address.com>:

     

     

    SorryRichard - perhaps I was being too verbose.

     

    I'm looking for a way to search through all libraries for a component

    BEFORE  the the library has been "use[d]"

     

    ie. do exactly what you suggest but on all libraries that are NOT in

    use. A full text search on all libraries on the system in other words.

     

    I cant see a way to do that.

     

     

    Hello Fred,

     

    Ok. But then I have to ask: Why?

    What's the problem with having libraries in USE? It all comes down to 

    beeing able to (quickly) find the component you want. Why does it matter 

    if you have 10 or 100 libraries in use?

    After you use Eagle longer you'll probably develop your own libraries with 

    often used and tested components and searching the 'system' lib's will 

    only happen once in a while, usually as an starting point to develop your 

    own devices.

     

    So, while searching the lib's may be important now, it will become less 

    important. Up till that point I think that 'USE *' and using the search 

    within Eagle will do the job.

     

    Or am I still missing something?

     

    Richard

     

Reply

  • Op Sun, 23 Sep 2012 13:06:08 +0200 schreef fred <email@address.com>:

     

     

    SorryRichard - perhaps I was being too verbose.

     

    I'm looking for a way to search through all libraries for a component

    BEFORE  the the library has been "use[d]"

     

    ie. do exactly what you suggest but on all libraries that are NOT in

    use. A full text search on all libraries on the system in other words.

     

    I cant see a way to do that.

     

     

    Hello Fred,

     

    Ok. But then I have to ask: Why?

    What's the problem with having libraries in USE? It all comes down to 

    beeing able to (quickly) find the component you want. Why does it matter 

    if you have 10 or 100 libraries in use?

    After you use Eagle longer you'll probably develop your own libraries with 

    often used and tested components and searching the 'system' lib's will 

    only happen once in a while, usually as an starting point to develop your 

    own devices.

     

    So, while searching the lib's may be important now, it will become less 

    important. Up till that point I think that 'USE *' and using the search 

    within Eagle will do the job.

     

    Or am I still missing something?

     

    Richard

     

Children
  • in reply to autodeskguest

    For those that come across this thread.

     

    To search for a specific component

    Open up the eagle control panel right click on the library folder as shown in figure 1, an option to search will be available select it and a search box will appear at the bottom as shown in figure 2. Type in your parameters such as " voltage regulator lm* ", use of wildcards is allowed and it will display the results and allow navigation. This is handy to see if the component exists in your library and to make sure you don't duplicate your efforts by creating a new one.

     

    image

    Figure 1 right click on folder

     

    image

    Figure 2 searching for a component " voltage regulator lm* "

     

    If you do create a new library it is recommended that you edit the directories list to add in an external library and store it there so when an upgrade occurs you will  not have to copy and paste into the new version of the software,

     

    More information, libraries,scripts and instructions can be found on my github here.