Actions
Forum Thread Details
  • State Suggested Answer
  • Replies 6 replies
  • Answers 1 answer
  • Subscribers 180 subscribers
  • Views 1535 views
  • Users 0 members are here
Related

Adding company part numbers in Eagle that I can access with ULP

rx8pilot

Hello all,

 

I have successfully written my first ULP to format data for my pick and place machine. For the most part I got the data formatted to be a direct import into the machine except for one detail - part numbers.

 

The software in the machine needs to associate every reference designator with a part number. This association tells it what package, reel, value, etc it is. In Eagle, I am not sure how to assign our internal part number to each component so that when it comes time to program the pick and place it can be one swift ULP action to get the data I need.This is also a problem when outputting general purpose BOM's

 

I have been using the same resistor for all the resistors on the PCB of the same package type. Just change the values as needed. This of course is the same for the capacitors as well. What I would like to have is our part number for all the variations of values, tolerance, type, etc.

 

Active and unique parts are seemingly a little easier because I use a specific part in general. This is not always the case though, maybe an MCU with the same package has a number of variants of memory, speed, or whatever.

 

Does anyone have any suggestions or best practices for associating part number with a part that can be output via ULP's to Pick and Place centroid files and BOM's? Hoping there is an easy solution that is hiding in plain site.

 

Thanks in advance for anyone willing to help.

Parents
  • 0

    Carlos Acosta wrote on Sun, 25 October 2015 02:05

    Does anyone have any suggestions or best practices for associating

    part

    number with a part ...

     

     

    I recently added a house part number system to my Eagle BOM generation

    tools.  I allow for two ways to associate private part numbers to parts:

     

    1: The INHOUSE attribute.  This would normally be set in the library, but

    of course can be set in the schematic for one-off uses too.  The private

    part numbers for a number of organizations can be set this way.  For

    example, the string "Acme:12345;MegaCorp:789" specifies that the private

    part number within the Acme organization is 12345, and within MegaCorp is

    789.

     

    2: The BOM generation program tries to find matching parts to the ones in a

    design in a special set of CSV files.  These CSV files have close to the

    same format as the resulting BOM spreadsheets, and are easily generated

    from such BOM spreadsheets after the private part numbers for the

    organization are filled in.  You dig out the private part numbers for the

    parts used in a design, export the data to a CSV file, and from then on the

    BOM utility automatically knows the private part numbers of those parts

    without them having to be in the INHOUSE attribute.  The data in these CSV

    files includes the organization name, so results from multiple

    organizations with different private part numbers can be thrown together.

     

    The CSV_BOM program, which does most of the heavy lifting of BOM creation

    in my system, is run in the Eagle directory for the particular board.  It

    searches up the tree of directories looking for a "housename" file.  It

    reads the first one it finds to get the name of the organization to find

    in-house part numbers for.  Since the boards for each customer are in a

    separate tree, all you have to do is create the housename file once per

    customer, then the BOM tools automatically know which organization any new

    boards belong to.

     

    This all seems to be working correctly, but I haven't updated the Eagle

    Tools release with this new facility yet.  I'm having trouble getting the

    new version of Visual Studio to make 32 bit EXEs when running on a 64 bit

    system, but that's a different issue.  I can try to make this a higher

    priority if there is interest in this.

     

    I have uploaded the eagle_attr.txt file, which documents how my BOM system

    uses various attributes.

     

    --

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

     

    Attachments:
    eagle_attr.txt.zip
Reply
  • 0

    Carlos Acosta wrote on Sun, 25 October 2015 02:05

    Does anyone have any suggestions or best practices for associating

    part

    number with a part ...

     

     

    I recently added a house part number system to my Eagle BOM generation

    tools.  I allow for two ways to associate private part numbers to parts:

     

    1: The INHOUSE attribute.  This would normally be set in the library, but

    of course can be set in the schematic for one-off uses too.  The private

    part numbers for a number of organizations can be set this way.  For

    example, the string "Acme:12345;MegaCorp:789" specifies that the private

    part number within the Acme organization is 12345, and within MegaCorp is

    789.

     

    2: The BOM generation program tries to find matching parts to the ones in a

    design in a special set of CSV files.  These CSV files have close to the

    same format as the resulting BOM spreadsheets, and are easily generated

    from such BOM spreadsheets after the private part numbers for the

    organization are filled in.  You dig out the private part numbers for the

    parts used in a design, export the data to a CSV file, and from then on the

    BOM utility automatically knows the private part numbers of those parts

    without them having to be in the INHOUSE attribute.  The data in these CSV

    files includes the organization name, so results from multiple

    organizations with different private part numbers can be thrown together.

     

    The CSV_BOM program, which does most of the heavy lifting of BOM creation

    in my system, is run in the Eagle directory for the particular board.  It

    searches up the tree of directories looking for a "housename" file.  It

    reads the first one it finds to get the name of the organization to find

    in-house part numbers for.  Since the boards for each customer are in a

    separate tree, all you have to do is create the housename file once per

    customer, then the BOM tools automatically know which organization any new

    boards belong to.

     

    This all seems to be working correctly, but I haven't updated the Eagle

    Tools release with this new facility yet.  I'm having trouble getting the

    new version of Visual Studio to make 32 bit EXEs when running on a 64 bit

    system, but that's a different issue.  I can try to make this a higher

    priority if there is interest in this.

     

    I have uploaded the eagle_attr.txt file, which documents how my BOM system

    uses various attributes.

     

    --

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

     

    Attachments:
    eagle_attr.txt.zip
Children
No Data