6.2 -> 6.5 BOM.ulp changes

On 20/12/2013 12:09 p.m., James Littlefield wrote:

Just trying to finish up my first design done in 6.5.  When I run bom.ulp I

no longer see the option to load a database (TSV) file.   Is there a way to

use a previously created TSV file to initialize the attributes of all the

parts and then run bom_with_attributes.ulp to get the previously defines

information.

 

I'm really not wanting to have to manually re-enter all the information

from all my *.tsv files for all each legacy design.

 

Thanks

Jim

 

Hi Jim

I can't see anything 'off the shelf' as that would be difficult to build

for all users and their variations if it were library focused.

Initially, where would you add the attribute information. In your

libraries or as attributes attached to the parts within your schematic?

If they are personal libraries and you have been controlling them and

their names since v4 then you could target them. Otherwise I would merge

the TSV information into your schematic for each design until you get

the library parts matched with your supplier data correctly. In the v4

bom.ulp the match for part to manufacturer info was partname:value so

those combinations in your current design need to match for the TSV data

to match and enter the new attribute. If that is the approach you want

to take it would not take to much effort to knock up a ULP to do it.

This approach is similar to that used previously. Previously the TSV

data was merged with the result of the BOM.ulp output. The new way would

be to merge the TSV into the schematic, creating new attributes/values

and then run the current v6  BOM.ulp that reads attributes.

Warren

On 20/12/2013 12:09 p.m., James Littlefield wrote:

Just trying to finish up my first design done in 6.5.  When I run bom.ulp I

no longer see the option to load a database (TSV) file.   Is there a way to

use a previously created TSV file to initialize the attributes of all the

parts and then run bom_with_attributes.ulp to get the previously defines

information.

 

I'm really not wanting to have to manually re-enter all the information

from all my *.tsv files for all each legacy design.

 

Thanks

Jim

 

Hi Jim

I can't see anything 'off the shelf' as that would be difficult to build

for all users and their variations if it were library focused.

Initially, where would you add the attribute information. In your

libraries or as attributes attached to the parts within your schematic?

If they are personal libraries and you have been controlling them and

their names since v4 then you could target them. Otherwise I would merge

the TSV information into your schematic for each design until you get

the library parts matched with your supplier data correctly. In the v4

bom.ulp the match for part to manufacturer info was partname:value so

those combinations in your current design need to match for the TSV data

to match and enter the new attribute. If that is the approach you want

to take it would not take to much effort to knock up a ULP to do it.

This approach is similar to that used previously. Previously the TSV

data was merged with the result of the BOM.ulp output. The new way would

be to merge the TSV into the schematic, creating new attributes/values

and then run the current v6  BOM.ulp that reads attributes.

Warren