6.2 -> 6.5 BOM.ulp changes

Bob...thanks for your suggestion.    I also used the old bom.ulp and it

worked fine.   Its a good stopgap measure!

Warren ..  My thought was that the information from the tsv file would be

added to attributes of the parts on the schematic.   Then you could run the

bom with attributes ULP and come up with a reasonable BOM preserving the

labor invested in the original *.tsv files.   

Perhaps I don't understand how attributes are supposed to work but my

initial impression is that they don't work that well.   As an example,  if

you have created attributes for a schematic component (say digikey part

number),  and then replace the part with a different package or change the

value,  the custom attribute (dk part number) remains at the old value.  

At least with the older method (*.tsv/bom.ulp).   Is there a good on-line

tutorial for how the attributes are supposed to be used,  how they interact

with the bom generation process, etc?

Thanks for your ideas,

Jim

--

Web access to CadSoft support forums at www.eaglecentral.ca.  Where the CadSoft EAGLE community meets.

Bob...thanks for your suggestion.    I also used the old bom.ulp and it

worked fine.   Its a good stopgap measure!

Warren ..  My thought was that the information from the tsv file would be

added to attributes of the parts on the schematic.   Then you could run the

bom with attributes ULP and come up with a reasonable BOM preserving the

labor invested in the original *.tsv files.   

Perhaps I don't understand how attributes are supposed to work but my

initial impression is that they don't work that well.   As an example,  if

you have created attributes for a schematic component (say digikey part

number),  and then replace the part with a different package or change the

value,  the custom attribute (dk part number) remains at the old value.  

At least with the older method (*.tsv/bom.ulp).   Is there a good on-line

tutorial for how the attributes are supposed to be used,  how they interact

with the bom generation process, etc?

Thanks for your ideas,

Jim

--

Web access to CadSoft support forums at www.eaglecentral.ca.  Where the CadSoft EAGLE community meets.

On 21/12/2013 12:42 a.m., James Littlefield wrote:

Bob...thanks for your suggestion.    I also used the old bom.ulp and it

worked fine.   Its a good stopgap measure!

 

Warren ..  My thought was that the information from the tsv file would be

added to attributes of the parts on the schematic.   Then you could run the

bom with attributes ULP and come up with a reasonable BOM preserving the

labor invested in the original *.tsv files.

 

Perhaps I don't understand how attributes are supposed to work but my

initial impression is that they don't work that well.   As an example,  if

you have created attributes for a schematic component (say digikey part

number),  and then replace the part with a different package or change the

value,  the custom attribute (dk part number) remains at the old value.

At least with the older method (*.tsv/bom.ulp).   Is there a good on-line

tutorial for how the attributes are supposed to be used,  how they interact

with the bom generation process, etc?

 

Thanks for your ideas,

Jim

 

 

 

Hi Jim

Reading the HELP > attribute  is a good start.

Then supplement that by reading the explanations in the manual found in

the docs folder of  your installation files.

Then practice what you read.

In essence,

1. Attributes created in the library reveal themselves in the  lib, sch

and brd.

2. Attributes created in the sch reveal themselves in the sch and brd

3. Attributes created in the brd only pertain to the board

4. Then there the global attributes for the board

5. and separately, the global attributes for the schematic

To have part numbers that automatically change when you change the

package or technology, you will need to set up the attributes in the

library by device variant.

HTH

Warren