11/10/2022 0 Comments Diptrace library right angle headerI often find that I want to have a library that's split up into sections. I think Gerard asked for a more capable library hierarchy capability than I'm looking for right now, and his idea would probably work for me too.but I'd be reasonably happy with something simpler: Other typical candidate I would see fit nicely into such hierarchy are high luminosity LEDs. Alternatively if new components are created i can easily add them to the "Myapp component" for my next batch of product. If my componenet provider runs out of stock of the component I usually buy, I can easily switch to the next in the list and not have to check every time i get into the problem. This would be a manuallly created list of specific components that all use the same generic component ant that from the designer perspective would fit the need of a specific application. Then, i would appreciate one more layer of components where I could define a list of componenet that would be more or less equivalent from "my application" perspective, something like "MyApp SO8 Power FET N". Then for every power fet I am interested in (e.g., based on max VDS, RDS, or any other parameter), i could define every specific power fet by there name and any specific parameter associated to it. I could define an "SO8 Power FET N" as a generic component. I would be interesting to define a Generic component and then make reference to that generic component rather than redefine how it looks like in schematic and what pin goes where. Many componenets use the same pinout and pattern.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |