The Package Matching tab allows you to create links between part numbers and packages which can then be sent to the Fuji machine once the machine program is generated.
Option | Description |
Component Selection | Displays a part number and its associated information from the CAD data. Use the arrow buttons to navigate through all of the CAD items. The Confirm button confirms the assignment identified between the CAD item displayed in the Component Part No field and the candidate package highlighted in the list of Candidate Packages (lower-right area of the dialog) after you select the Assign button. |
Package Comparison Viewer | The Package Comparison Viewer area of the dialog shows two images:
Both images use the same units of measure and scaling and are centered in the viewer to give you a visual indication of the quality of the match between the CAD represented pad landing and the selected package. Select the small button just above the images to rotate the foreground image in the Package Comparison Viewer counter-clockwise by 90 degrees. |
Package Comparison Parameters | The Package Comparison Parameters area of the dialog displays the details of the item displayed in the Component Part No field and the candidate package selected in the list of Candidate Packages side by side. |
Candidate Search Criteria | The Candidate Search Criteria area of the dialog contains the search criteria you enter to provide a ranked list of possible package definitions. Use the Search button at the bottom of the dialog to search the machine’s package library for suitable packages. The search criteria include the following properties:
|
Candidate Packages | The Candidate Packages area (lower-right corner of the dialog) displays the search results with the most highly ranked result shown first. The Assign button assigns the candidate package selected in the Candidate Packages list to the part number displayed in Component Part No. This mapping must be confirmed by selecting the Confirm button for the Part/Package assignment to be recorded / saved for automatic mapping in the future. The List All button displays the entire Candidate Packages list to show all values (that is, not just those returned when you use the Search button). |
How the Lead Count value is determined
...
For each package definition (<Part> tag within the *.FDX file), the import routine determines the Lead Count as indicated in the Interpretation for LeadCount Determination column in the table below.
ShapeType Value (Hex) | Represents | LeadNum Values Present in XML | Interpretation for Lead Count Determination |
00: | Unknown | No LeadNum value or equivalent | 0 (zero) |
01: | ”Melf Chip” | No LeadNum value or equivalent | 2 |
02: | ”Sp.Chip” | No LeadNum value or equivalent | 2 |
03: | ”Mini-Tr/SOT” | NS | N + S |
04: | ”SOP” | NE | (N + E) x 2 |
05: | ”QFP” | NE | (N + E) x 2 |
06: | ”PLCC” | NE | (N + E) x 2 |
07: | ”Std.Chip” | No LeadNum value or equivalent | 2 |
08: | ”2Ends” | No LeadNum value or equivalent | 2 |
09: | ”P-Tr” | NS | N + S |
0A: | ”Cylinder” | No LeadNum value or equivalent | 2 |
0B: | ”Bare.Chip” | No LeadNum value or equivalent | 0 (zero) |
0C: | ”Special” | Specific LeadNum values. | See note below. |
0D: | ”BGA” | No LeadNum value | Use the BgaAmount value |
0E: | ”Odd.Chip” | No LeadNum value or equivalent | 2 |
0F: | ”SOJ” | E | E x 2 |
10: | ”Con-E” | E | E x 2 |
11: | ”Con-NSEW” | NESW | N + E + S + W |
12: | ”OffLead” | NESW | N + E + S + W |
13: | ”AsMark” | No LeadNum value or equivalent | 0 (zero) |
14: | ”Sp.Quad” | NESW | N + E + S + W |
15: | ”Gravity” | No LeadNum value or equivalent | 0 (zero) |
16: | ”Ignore” | No LeadNum value or equivalent | 0 (zero) |
17: | ”FlipChip” | NESW | ((N + S)/2) x ((E + W)/2) |
18: | ”Sp.Con” | E | E |
19: | ”BGA” | No LeadNum value | Use the BgaAmount value |
1D: | ”Special, Smart_Recognition” | No LeadNum value | 0 (zero) |
Determining the Lead Count for ShapeType Special
...
When you select the Search button in the dialog, a score (a percentage value) is calculated for each package definition in the locally cached package library. The scoring is implemented as shown in the following table:
Lead Count | 250 |
Package Class | 150 |
Name | If exact match, short circuits the ranking; otherwise 0 - 50 based on number of characters that match and percentage of the search string matched from the first character to the first mismatched character. |
Pitch | Within tolerance, 50. This tolerance is independent of the dimensional tolerance. |
Dimensions | Maximum 100. |
In addition, when the package search is performed, each package entry is dimensionally compared to the item displayed in Component Part Noas follows.
The bounding rectangle of the item displayed in Component Part No is calculated and the long and short dimensions are determined (these are referred to as boundingX and boundingY respectively).
If a tolerance (absolute not a percentage) value is defined in the Search criteria the specified Tolerance is used; otherwise the Tolerance value is set to the candidate package’s Tolerance value (if one is defined).
The Minimum score is calculated like this:
...
The same calculation is made twice, once for the length of a package (using the bounding rectangle length and the BodyX values), and once for the width of a package (using the bounding rectangle width and the BodyY values). This calculation is made as shown below:
...
After the Length Score is calculated for both the length and the width values of the package, the two values are combined to give the overall dimension Score:
Dimension Score = Length Score [Length] + Length Score [Width]
-------------------------------------------------------------
...