SMT Programming - Parts Database set-up for contract manufacturer

Doug: There�s work to do checking the parts of new jobs from new or old customers with library data already existing. Just taking the packagename as matchcode might not work depending on the machines used and the library entries needed because for example a 1206 cap. varies in hight depending on value and manufactorer.

Good luck

Wolfgang

reply »

Doug, If you are looking to reduce the size of your database you have many options. You can use the Jedec outline or Jedec name to standardize your component library. Otherwise you can set one up specific to the dimensional info you measure. If you already have your database set up around part numbers I wouldn't change it. Once you generalize, a mistake is compounded. If you change Part Data for a specific customer you have just changed it for all customers, even if you don't want to. This is not such a big deal with caps and resistor but.... That's just my opinion, I could be wrong!

reply »

Doug,

What I've done in past was calling them as 1206T.5, 1206T1.0, SOIC16, RESNET16, SOIC16T5.0, ALCAP4, ALCAP5 etc.

T means thickness but for the ALCAP case 4 means 4mm diameter. If you have the time and patience, having a board and attaching a sample of every new part builds a library where you can touch and smell the various parts in your library too. This also makes it easier to decide which part type should be modified to generated the new part's library entry.

The relationship between the part number and part type depends on the machines and the program generation software you're using. The operators need to know the right part number to setup the feeder but the machine has to know what part type corresponds to that part number.

You should also expect to get error messages related to the part size/thickness since; 1. Same part number may come in different thicknesses. 2. Wrong part number may have been setup for that feeder location. 3. Nozzle picks up the part on its side. 4. ?

Regards Erhan

reply »

Doug,

I'm a PCB Designer. I work with ACCEL software to design my PCB. I'm also the superviser and programmer of the complete SMT production line. On this line, we have two quind of PNP machines : PANASERT ( japanese ) and MULTITRONIKS ( european ). From the ACCEL program, we build a software which is split the program for these two machines. Two machines have the same logic :

Part number =>> customer number and package number =>> EX:1206T.5

The part number is used for two reason. (1) Your operator know exactly what component is in this feeder and the value of that component. (2) On my two PNP machines, I can use an IPC module which is mesuring the component value specificaly for resistor and capacitor. This module using the " part number ".

My personal opinion is : I recommand you to use the part number and the package number it will be easier for you R&D department and you production department. I know that it is more work to do all your parts with a part number but your using only a few package types.

NOTE: On you sofware program, If your using the same logic, you will generate a PNP program with the complete information in only one double clik.

If you want more info about fiducial coodinate and origin logic do not esitate to email me. It will be much easier for me by email because my first language is french and I read beter than I speak.

Thank you

Francois

reply »