fizbim
10-20-2002, 05:28 PM
How does anyone (everyone) handle different manufacturing assemblies with PADS ?
Currently, we will generate a BOM for the primary assembly (lets say 01). Then we copy this BOM to a file for each assembly (say 02,03,04). Then we modify the BOM text files manually by changing part numbers, removing parts, etc for each BOM until they're complete. This is very time consuming and prone to error.
If this sounds like I'm leading up to something - you're right !
I have developed a program that is launched from a macro call in PowerLogic. It can also be run independantly as a seperate exe if you like. This program handles the task of adding, removing, changing, and adding new part numbers to components on a PowerLogic sch. It does this by adding, removing and changing assembly "tags" on the front of attribute names. For instance, here is an attribute list for a resistor. This resistor has 3 assemblies. Assembly 01 and 02 have the same part number. Assembly 03 has a different component value for the same reference designator.
(01):Part Number 123456
(01):Part Description Resistor,1K,0603,1%
(02):Part Number 123456
(02):Part Description Resistor,1K,0603,1%
(03):Part Number 789012
(03):Part Description Resistor,2K,0603,1%
Since all attributes get carried into the PCB, when an ASC file is exported from the PCB, ALL information from the design will be included. It will be an easy task for a file parsing routine to extract a BOM for each assembly and component placement information.
Of course, you could enter these tags by hand, but once again,manual manipulation is prone to human error.
Would a program that handle manufacturing assemblies like I've described be of interest to others ?
Let me know your thoughts.
Currently, we will generate a BOM for the primary assembly (lets say 01). Then we copy this BOM to a file for each assembly (say 02,03,04). Then we modify the BOM text files manually by changing part numbers, removing parts, etc for each BOM until they're complete. This is very time consuming and prone to error.
If this sounds like I'm leading up to something - you're right !
I have developed a program that is launched from a macro call in PowerLogic. It can also be run independantly as a seperate exe if you like. This program handles the task of adding, removing, changing, and adding new part numbers to components on a PowerLogic sch. It does this by adding, removing and changing assembly "tags" on the front of attribute names. For instance, here is an attribute list for a resistor. This resistor has 3 assemblies. Assembly 01 and 02 have the same part number. Assembly 03 has a different component value for the same reference designator.
(01):Part Number 123456
(01):Part Description Resistor,1K,0603,1%
(02):Part Number 123456
(02):Part Description Resistor,1K,0603,1%
(03):Part Number 789012
(03):Part Description Resistor,2K,0603,1%
Since all attributes get carried into the PCB, when an ASC file is exported from the PCB, ALL information from the design will be included. It will be an easy task for a file parsing routine to extract a BOM for each assembly and component placement information.
Of course, you could enter these tags by hand, but once again,manual manipulation is prone to human error.
Would a program that handle manufacturing assemblies like I've described be of interest to others ?
Let me know your thoughts.