Author Topic: Library structure  (Read 3177 times)

0 Members and 1 Guest are viewing this topic.

Offline trevwhiteTopic starter

  • Frequent Contributor
  • **
  • Posts: 941
  • Country: gb
Library structure
« on: March 01, 2017, 11:47:40 pm »
I am a bit confused by the library setup in CS.

Does anyone have some good information/suggestion on the best way to start working with them? My requirement is to build up a library that I will trust and mature over time.

Trev
 

Offline IanJ

  • Supporter
  • ****
  • Posts: 1665
  • Country: scotland
  • Full time EE & Youtuber
    • IanJohnston.com
Re: Library structure
« Reply #1 on: March 02, 2017, 11:56:52 am »
Hi,

http://documentation.circuitstudio.com/display/CSTU/Component+Management+in+CircuitStudio#ComponentManagementinCircuitStudio-WorkingwithSch/PcbLibraries

Don't store your .PcbLib and .SchLib files in an individual project, store them in a generic folder somewhere that all your projects can access/reference and update accordingly. I made that mistake to start with and it's a pain to fix.

You don't need to create an Integrated library, but the guide above does show you how. I just keep it simple with the .PcbLib and .SchLib files. So easy to work with (compared to Eagle)

Ian.
Ian Johnston - Original designer of the PDVS2mini || Author of the free WinGPIB app.
Website - www.ianjohnston.com
YT Channel (electronics repairs & projects): www.youtube.com/user/IanScottJohnston, Twitter (X): https://twitter.com/IanSJohnston
 

Offline AntoshC

  • Newbie
  • Posts: 6
  • Country: us
Re: Library structure
« Reply #2 on: March 02, 2017, 06:21:02 pm »
IanJ gives good advice here.

I also break up my libraries as opposed to having one large "trusted" library.

I have a folder for my SchLib and PcbLIb files within my larger library folder. That library folder also contains manufacturer libs.

Some of my personal libs only contain a single component, but it sure is easier to find my MiniUSB part in a library named USB_Connectors than in one big library with a mix of parts.

 

Offline trevwhiteTopic starter

  • Frequent Contributor
  • **
  • Posts: 941
  • Country: gb
Re: Library structure
« Reply #3 on: March 02, 2017, 06:38:37 pm »
Thanks for the advice, this all makes sense. I need to spend a bit of time playing around with creating parts, etc to understand the best way to generate my library. I think the layout and schematic take care of themselves as long as the library is done properly.
 

Offline Harvs

  • Super Contributor
  • ***
  • Posts: 1202
  • Country: au
Re: Library structure
« Reply #4 on: March 02, 2017, 08:41:33 pm »
I do a mix of both having central libraries for generic common parts (passives, micros etc.)

Then I'll have project or customer specific libraries where there's a 90% probability that I'll never use those parts in a design not for that customer

Personally I do tend to use the integrated library projects, that way I can keep text files (TODO lists) etc all together in the project.

I think more important than how you store your components is getting a consistent approach to schematic and PCB components that take into account things like how you want to produce your assembly drawings.
 


Share me

Digg  Facebook  SlashDot  Delicious  Technorati  Twitter  Google  Yahoo
Smf