Hello,
I think that every user of EAGLE needs the BOM functionnality. We may have differents need, but the aim is the same : generate a BOM file. So I suggest we discuss about making a unique powerfull ULP that will fit every need.
As far as I am concerned, I use the bom-am.ulp and I like the way it works. It uses a file text (called the database) to assign references (farnell ordre codes for my part) to components. A component is a couple (device, value).
So, for example, if I add a 330 ohm resistor in a package 0603, and if it already exists in the database, the bom-am will already know the farnell order code, and I will not have to look for it again.
I do not like the "attributes", because they are not saved in the database, so we have to set them each time we add a new component.
My suggestion is to mix the bom-am and the Design Link to get new functionnalities :
- choosing the order code : when using the bom-am, we can assign references to a component, and we could use Design Link instead of searching on a web browser.
- generating the BOM file : as the database knows the order code of each component, we could use Design Link to get more information about the components (for example : manufacturer, manufacturer part number tolerance, ratings, temperature, ROHS, prices, availability, etc) so as to export them (according to the user choices) in a file (csv, html, etc).
- ordering on Farnell : according to some options, all (or part of) the BOM could be added to the order list.
Do you think about other interesting functionnalities ?
Jerome
