FATF FABmaster ASCII Transfer Format

ASCII Transfer Format (FATF) Notice This document describes FABmaster ASCII Transfer Format (FATF) which may be used to input a neutral database from any other computer system into FABmaster and to output a neutral database from FABmaster to any other computer system. The information in this document is proprietary to FABMASTER S.A., Meylan/Grenoble, France and its use is authorised uniquely for the purpose of developing interfaces between FABmaster and another computer system. Table of Contents TOC \o "1-4" 1. FABmaster ASCII Transfer Format 3 1.1 Sample FATF File 3 1.2 Header 5 1.3 Units & Co-ordinates 5 1.4 Optional Keywords 6 1.4.1 :NOTRACE 6 1.4.2 :NOAUTOCOG 6 1.4.3 :NOAUTOROTATE 6 1.4.4 :NO_PAD_STACK_GROUP 6 1.4.5 :NOXY (with FABUPIP) 7 2. FATF File Sections 8 2.1 BOARD_DATA Section 8 2.1.1 Job 8 2.1.2 Board Contour 8 2.1.3 Work Space 9 2.1.4 Fiducials (Not Yet Implemented) 9 2.1.5 Board Thickness 9 2.2 PARTS Section 9 2.3 NETS Section 10 2.4 PAD_SYMBOLS Section 11 2.5 LAYER_NAMES Section 12 2.5.1 LAYER_TYPE 13 2.5.2 LAYER_SENSE 13 2.5.3 LAYER_NAMES 13 2.5.4 Layer Assignments 14 2.6 LAYER_SETS Section 15 2.7 PAD_STACKS Section 15 2.8 PADS Section 17 2.9 FONTS Section 17 2.10 Primitive Graphics Symbols 18 2.11 PACKAGES Section 19 2.11.1 PIN_TYPE & TST_TYPE 20 2.11.2 HEADER 20 2.11.3 LABEL Sub-section 21 2.11.4 PINS Sub-section 21 2.11.5 LAYER Sub-section 21 2.11.6 PAD Sub-section 22 2.12 TEST_POINTS Section 22 2.13 LAYERS Section 23 1.​ FABmaster ASCII Transfer Format 1.1​ Sample FATF File ;Copyright (c) FABMASTER S.A., France, 1992 :FABMASTER FATF REV 11.1; :UNITS = 1/1000 INCH; :NOAUTOROTATE :BOARD_DATA 1,"JOB" (JOB_NAME,VERSION,CREATED,MODIFIED); 2,"CONTOUR" ((X1,Y1,0),(X2,Y2,0),...,(Xn,Yn,0)); ..... 1+nc,"CONTOUR" ((X1,Y1,0),(X2,Y2,0),...,(Xn,Yn,0)); 2+nc,"WORK_SPACE" (XMIN,XMAX,YMIN,YMAX); 3+nc,"FIDUCIALS" ((X1,Y1),(X2,Y2),...,(Xn,Yn)); 4+nc,"THICKNESS",; :EOD :PARTS PART_Id,PART_NAME,DEVICE_NAME,PACKAGE_NAME,X,Y,ROTATION,T_OR_B; PART_Id,PART_NAME,DEVICE_NAME,PACKAGE_NAME,X,Y,ROTATION,T_OR_B; :EOD :NETS NET_ID,NET_NAME,POWER_OR_SIGNAL,((PART_Id,PIN_Id),..,((PART_Id,PIN_Id)); NET_ID,NET_NAME,POWER_OR_SIGNAL,((PART_Id,PIN_Id),..,((PART_Id,PIN_Id)); :EOD PAD_SYMBOL = "P_ROUND"(DIAMETER) "TRACK"(SPOT_WIDTH,(0,-dY),(0,dY)) "P_BLOCK"(-dl,-dl,dl,dl) "TRACK"(SPOT_WIDTH,(-dX,0),(dX,0)) :PAD_SYMBOLS PAD_SYMBOL_ID, PAD_SYMBOL; :EOD LAYER_TYPE = ELECTRICAL or DOCUMENTATION or DXF or BOARD_CUTOUT or MASKING or ASSEMBLY or SILKSCREEN {if undefined, default is DOCUMENTATION} LAYER_SENSE = COMMON or TOP or BOTTOM or TRANSPARENT {if undefined, default is TRANSPARENT} :LAYER_NAMES LAYER_ID,LAYER_NAME,LAYER_SENSE,FLIP_LAYER_ID,LAYER_TYPE; LAYER_ID,LAYER_NAME,LAYER_SENSE,FLIP_LAYER_ID,LAYER_TYPE; :EOD :LAYER_SETS LAYER_SET_ID,LAYER_SET_NAME,(LAYER_ID,LAYER_ID,...,LAYER_ID); LAYER_SET_ID,LAYER_SET_NAME,(LAYER_ID,LAYER_ID,...,LAYER_ID); :EOD :PAD_STACKS PAD_STACK_ID,PAD_STACK_NAME,DRILL,B_OR_P_OR_N,((LAYER_SET_ID,PAD_SYMBOL_ID)); :EOD :PADS NET_ID, PAD_STACK_ID, ((X1,Y1),(X2,Y2),...,(Xn,Yn)); NET_ID, PAD_STACK_ID, ((X1,Y1),(X2,Y2),...,(Xn,Yn)); :EOD :FONTS 1,FONT_NAME,CHAR_HEIGHT,CHAR_WIDTH,CHAR_SPACE,SPOT_WIDTH; :EOD SYMBOL = "ROUND" (DIAMETER,X,Y) "BLOCK" (Xlo,Ylo,Xhi,Yhi) "TRACK" (SPOT_WIDTH,(X1,Y1),(X2,Y2), ...,(Xn,Yn)) "LINE" (SPOT_WIDTH,(X1,Y1),(X2,Y2), ...,(Xn,Yn)) "POLYGON"((X1,Y1),(X2,Y2), ...,(Xn,Yn)) "CIRCLE" (RadiusMax,RaiusMin,Xcentre,Ycentre) "TEXT" (FONT_ID,X,Y,JUSTIFY,ROTATION,MIRROR,"STRING") PIN_TYPE,TST_TYPE = D or T or B :PACKAGES PACKAGE_ID,PACKAGE_NAME,XMIN,XMAX,YMIN,YMAX, ("LABEL"(FONT_ID,X,Y,JUSTIFY,ROTATION) ), ("PINS"(PIN_id,PIN_NAME,PIN_X,PIN_Y,PIN_TYPE),..., (PIN_id,PIN_NAME,PIN_X,PIN_Y,PIN_TYPE) ), (PIN_id,"PAD" (PAD_STACK_ID,((X1,Y1),.. ,(Xn,Yn))), PIN_id,"LAYER"(LAYER_ID,(SYMBOL,..., SYMBOL)),..., PIN_id,"LAYER"(LAYER_ID,(SYMBOL, ... SYMBOL)) ); PACKAGE_ID, (..............); :EOD :TEST_POINTS NET_ID (X,Y) TST_TYPE; or NET_ID (X,Y) TST_TYPE,PART_id,PIN_id; :EOD :LAYERS NET_ID, "LAYER" (LAYER_ID,(SYMBOL,...,SYMBOL)); NET_ID, "LAYER" (LAYER_ID,(SYMBOL,...,SYMBOL)); :EOD :EOF 1.2​ Header The header line includes a revision number, for example for FABmaster software version V8.E the revision number is 11.1. The syntax of the header line is: :FABMASTER FATF REV [] [] [;] [] Means the field is optional. A sequence of spaces and/or tabulations. Given by: [.] Examples of correct revision definition: :FABMASTER FATF REV10; :FABMASTER FATF REV 1.3; :FABMASTER FATF REV 11.0; To note: ​ If the revision definition is incorrect, a syntax error will be output to the error report and status file iperror.asc. ​ The revision number must be lower than the current revision number which is 11.1 for the FABmaster software V8.E. ​ The revision number is displayed in the error report and status file iperror.asc as :FATF - Revision Number - . ​ If the revision number is invalid, a range error will be output to iperror.asc and by default the current revision number 11.1 will be output for the revision. 1.3​ Units & Co-ordinates Prior to FABmaster software V8C units were only possible in 1/1000 inch: :UNITS = 1/1000 INCH As from FABmaster software version V8.C there are 3 possibilities: :UNITS = 1/1000 INCH :UNITS = 1/10000 INCH :UNITS = 1/100000 INCH Co-ordinates are in the range –100 inch to +100 inch. 1.4​ Optional Keywords 1.4.1​ :NOTRACE If this line is included it prevents FABmaster from connecting a signal to an unconnected node which has been chosen as a Test Point. This can be very useful when: ​ The CAD design is dense and so will save time. ​ There is a possibility of error which would be the case if a documentation object (such as an arrow) or the board outline was used as the connecting pole. 1.4.2​ :NOAUTOCOG If this keyword is included, FABmaster will not recalculate the different part centres of gravity but leave them as they were designed in the original CAD database. 1.4.3​ :NOAUTOROTATE If this is included, FABmaster will not redefine the different part rotations but will leave them as they were designed in the original CAD database However, if it is missing FABmaster will redefine the package which comes from the original CAD design so that the vector components showing the direction of the 1st pin towards the 2nd pin are: ​ Positive for the X-axis (0 < Xpin2 - Xpin1). ​ Positive or zero for the Y-axis (0 <= Ypin2 - Ypin1). To do this, FABmaster must execute a multiple rotation of 90° in relation to the CAD definition. For example this new package definition will correspond to a rotation of 0° in order to position the parts. The other rotations (90, 180, 270) will be calculated in relation to this new definition turning in a clockwise direction. 1.4.4​ :NO_PAD_STACK_GROUP Include this keyword to stop FABmaster from grouping pad stacks which have been declared as identical in the FATF file. For example: 1,"",32,P,((1,1)); 2,"",32,P,((1,1)); 3,"",4,P,((5,3)); By default FABmaster will group the first 2 pad stacks as the pad stack is the same. Include the keyword :NO_PAD_STACK_GROUP, so that all 3 padstacks are left separate. 1.4.5​ :NOXY (with FABUPIP) The keyword NOXY was added to the FATF language for FABUPIP - FABmaster User Programmable Input Processor. FABUPIP is an alternative when CAD data is unavailable although CAD input is always the preferred input. If no CAD data is available, FABUPIP can be programmed by the user to read in most forms of ASCII data files which include Part List data and simple X,Y data including Net and Pin List files: If no X,Y data is available, FABUPIP can still be used to input parts and Net List data (without X,Y information) in order to generate a tester input list. If no data at all is available, the user can type in his own Parts/Net List data in any ASCII format, can program FABUPIP to read in this data and can create a FABmaster database. In this case, FABmaster can only generate an in-circuit test program with no nail or fixture data. If FABUPIP is to generate a database without X,Y data, the keyword NOXY is needed in the header of a FATF file: :FABMASTER FATF,REV1.2; :NOXY :UNITS = 1/1000 INCH :BOARD_DATA If NOXY is included in the header, FABmaster will accept a limited database with no X,Y data. In some sections null X,Y data is required (ask for an example file if you need the exact syntax). A database which is input using the keyword NOXY has no Data Screens meaning there are no Data Screen icons in the Job Screen. Output processors which generate an input list for in-circuit test can be run although neither nail nor fixture information is available. Output processors for assembly applications (SMD and through-hole parts) cannot be run as they require a minimum of part X,Y data. 2.​ FATF File Sections 2.1​ BOARD_DATA Section :BOARD_DATA 1,"JOB" (JOB_NAME,VERSION,CREATED,MODIFIED); 2,"CONTOUR" ((X1,Y1,0),(X2,Y2,0),...,(Xn,Yn,0)); ..... 1+nc,"CONTOUR" ((X1,Y1,0),(X2,Y2,0),...,(Xn,Yn,0)); {nc = no. of contours} 2+nc,"WORK_SPACE" (XMIN,XMAX,YMIN,YMAX); {nc = no. of contours defined} 3+nc,"FIDUCIALS" ((X1,Y1),(X2,Y2),...,(Xn,Yn)); {nc = no. of contours defined} 4+nc,"THICKNESS",; {nc = no. of contours defined} :EOD Example :BOARD_DATA 1,JOB("DATA CONTROL CARD PCB1602 REV1.O DATED 17-06-1989",,1-1-87,23-11-1992); 2,CONTOUR ((3937,3937,0),(3937,7874,0),(12598,7874,0),(12598,3937,0), (3937,3937,0)); 3,WORK_SPACE (300,16050,0,11810); 4,FIDUCIALS ((2100,1900),(2100,9800),(14300,9800)); 5,THICKNESS,63; :EOD The :BOARD_DATA section contains miscellaneous information describing the Job, board contour, work space limit, known Fiducial positions and the board thickness. 2.1.1​ Job 1,"JOB" (JOB_NAME,VERSION,CREATED,MODIFIED); JOB_NAME Optional. Title describing the Job, max. 64 characters. VERSION Optional. Current revision of the Job data. CREATED Optional. Job Creation date. Parameters take the form dd‑mm‑yyyy: dd: an integer defining the Day (1..31) mm: an integer defining the Month (1..12) yyyy: an integer defining the Year MODIFIED Date the Job was last processed on FABmaster. Updated automatically. 2.1.2​ Board Contour CONTOUR is a set of X,Y co-ordinates which defines the board outline. More than one "contour" can be defined. 2,"CONTOUR" ((X1,Y1,0),(X2,Y2,0),...,(Xn,Yn,0)); (X1,Y1,0) X1..Xn and Y1..Yn are mandatory integers (Xn,Yn,0) 0 means that each corner of a "contour" is a 90° angle. In the current release of FATF only 90° angles are supported. 2.1.3​ Work Space WORK_SPACE describes the outer limits of all data. If data is found outside the limits, it may be clipped and lost. 2+nc,"WORK_SPACE" (XMIN,XMAX,YMIN,YMAX); (XMIN,XMAX,YMIN,YMAX) Mandatory integers defining X,Y min. and max. co-ordinates. 2.1.4​ Fiducials (Not Yet Implemented) FIDUCIALS will define board Fiducials (User Reference Points) which can include locating holes or camera symbols. 3+nc,"FIDUCIALS" ((X1,Y1),(X2,Y2),...,(Xn,Yn)); X1..Xn, Y1..Yn Optional integers. 2.1.5​ Board Thickness THICKNESS defines the thickness of the board. 4+nc ,"THICKNESS",; Mandatory integer. Board thickness (in MILs). 2.2​ PARTS Section :PARTS PART_ID,PART_NAME,DEVICE_NAME,PACKAGE_NAME,X,Y,ROTATION,T_OR_B; PART_ID,PART_NAME,DEVICE_NAME,PACKAGE_NAME,X,Y,ROTATION,T_OR_B; :EOD Example :PARTS 1,"U1","401061A","DIL14",9300,4550,0,T; ... 21,"D1","1N4148","DIODE1",10450,7300,2700,T; ... 42,"C1","1UF_16V","TANT1",10600,7300,900,T; ... 70, "R1","10K‑2%","RES8",10750,7300,2700,T; ... :EOD All parts must be defined in this section and numbered consecutively from 1 to n. PART_ID Mandatory integer from 1 to 8192. Sequence number referencing each part. PART_NAME Mandatory. Schematic reference designator for each part. Valid Part Names are "IC1", "U33", "J1A", "BOARD", "TARGET_1". DEVICE_NAME Recommended string. Describes the type of part. Used on FABmaster to refer to all electrical Device Attributes for the part. Valid Device Names are "74LS00", "10K", "C145678-RS-YY6-9". DEVICE_NAME can be modified in FABmaster through the Device Attribute Library or import a Device Library file in FABmaster neutral BOM format. PACKAGE_NAME Mandatory. Describes the type of physical Outline Package the part uses. PACKAGE_NAME must be in the :PACKAGES section. PACKAGE_NAME can be modified in FABmaster through the Outline Attribute Library or by importing an Outline Library file in FABmaster neutral BOM format. X,Y Mandatory in the range 0 to 32767. Gives the part body COG (Centre Of Gravity) X,Y co-ordinates. The FATf input processor automatically checks and corrects these values. If there is a Reference Point for the part (such as pin 1) the values are corrected by FATf to provide the part centre of gravity. ROTATION Mandatory integer, 1/10 degree intervals. Part rotation of the body as it is to be placed on the board. Rotation values are integer, 0 to 3600 with 1/10° units. Rotation 0 is the part as it exists in the :PACKAGES section. A 90° rotation (900 in 1/10° units) rotates the part body 90° in a clockwise direction. T_OR_B Mandatory. "T", "t" or "B", "b". Parts can be placed on the Top ("T"/"t") or the Bottom ("B"/"b") of the board. If a part is on the Top, it is displayed as defined in the :PACKAGES section. If a part is on the Bottom it is flipped during display in the Y data axis. 2.3​ NETS Section :NETS NET_ID,NET_NAME,POWER_OR_SIGNAL,((PART_ID,PIN_ID),...,((PART_ID,PIN_ID)); NET_ID,NET_NAME,POWER_OR_SIGNAL,((PART_ID,PIN_ID),...,((PART_ID,PIN_ID)); :EOD Example :NETS 1,"#1",S,((1,1),(68,1),(116,4)); ... 152,"ACCEPT14*",S,((74,1),(108,8),(117,2),(117,7),(118,2),(118,7)); ... 176,"ALARM1*",S,((108,5),(111,3),(117,4)); ... :EOD This section contains a list of all the electrical interconnections between the parts on the board. NET_ID Mandatory integer from 1 to 32767. Sequence number. All nets must be defined and numbered from 1 to n consecutively. The NET_ID will be used in other sections. NET_NAME Optional. Nets can have names - optional whereas the net number (NET_ID) is mandatory. POWER_OR_SIGNAL Mandatory. "P", "p" for "POWER"; "S", "s" for "SIGNAL". Nets are identified as Power or Signal connections. (PART_ID,PIN_ID) Mandatory. A net is a series of nodes connected electrically. Each node describes a part pin number and is made up of: ​ PART_ID: PART_ID sequence number in the :PARTS section ​ PIN_ID: pin number of the packages in the :PACKAGES section. 2.4​ PAD_SYMBOLS Section PAD_SYMBOL = "P_ROUND"(DIAMETER) "TRACK"(SPOT_WIDTH,(0,‑dY),(0,dY)) "P_BLOCK"(‑dl,‑dl,dl,dl) "TRACK"(SPOT_WIDTH,(‑dX,0),(dX,0)) :PAD_SYMBOLS PAD_SYMBOL_ID, PAD_SYMBOL; PAD_SYMBOL_ID, PAD_SYMBOL; :EOD Example :PAD_SYMBOLS 1,P_ROUND (60); 2,P_BLOCK (‑20,‑20,20,20); 3,TRACK (50,(0,‑60),(0,60)); ... :EOD This section is needed to define Pad Stacks (see :PAD_STACKS). Pad Stacks define pads which are drilled right through the board (through-hole) or only partially (buried vias). A drilled Pad Stack must define a Pad Symbol on each layer or set of layers on which a symbol is to be displayed. Pad Symbols are not needed for SMD parts with undrilled pads. In this case, the pads can be defined directly in the package on each Layer if necessary. This section contains a one-line definition for each pad shape which is used in :PAD_STACKS. Each Pad Symbol is numbered 1 to 255 consecutively by a sequence number. PAD_SYMBOL_ID Mandatory. Sequence number from 1 to 2047. Used in the :PAD_STACKS section. PAD_SYMBOL Mandatory Symbol. Pad Symbols can be: *​ Round (P_ROUND) *​ Square (P_BLOCK) *​ Oblong (TRACK) Oblong pad shapes are created via a TRACK symbol. "P_ROUND"(DIAMETER) Filled round pad (). The pad is displayed at the centre of the Pad Stack. "P_BLOCK"(-dl,-dl,dl,dl) Filled square pad (). Currently this symbol does not support rectangular pad shapes. -dl,-dl - lower left corner of the square pad with respect to the centre of the Pad Stack. dl,dl - upper right corner of the square pad with respect to the centre of the Pad Stack. "TRACK"(SPOT_WIDTH,(0,-dY),(0,dY)) Filled vertical oblong pad. To display move a filled circle with diameter SPOT_WIDTH from –dY to dY (-dY, dY offsets with respect to Pad Stack centre). "TRACK"(SPOT_WIDTH,(-dX,0),(dX,0)) Filled horizontal oblong pad. To display move a filled circle with diameter SPOT_WIDTH from –dX to dX (-dX, dX offsets with respect to Pad Stack centre). 2.5​ LAYER_NAMES Section LAYER_TYPE = ELECTRICAL or DOCUMENTATION or DXF or BOARD_CUTOUT or MASKING or ASSEMBLY or SILKSCREEN {if undefined, default is DOCUMENTATION} LAYER_SENSE = COMMON or TOP or BOTTOM or TRANSPARENT {if undefined, default is TRANSPARENT} :LAYER_NAMES LAYER_ID,LAYER_NAME,LAYER_SENSE,FLIP_LAYER_ID,LAYER_TYPE; LAYER_ID,LAYER_NAME,LAYER_SENSE,FLIP_LAYER_ID,LAYER_TYPE; :EOD Example :LAYER_NAMES 1,"DRILL PAD ",COMMON,0,ELECTRICAL; 2," TOP COPPER",TOP,3,ELECTRICAL; 3,"BOTTOMCOPPER",BOTTOM,2,ELECTRICAL; 4,"INNERCOPPER1",TRANSPARENT,0,ELECTRICAL; 5,"INNERCOPPER2",TRANSPARENT,0,ELECTRICAL; 6,"TOP OUTLINE",TOP,7,ASSEMBLY; 7,"BOT OUTLINE",BOTTOM,6,ASSEMBLY; 8,"TOP SILKSCRN",TOP,0,SILKSCREEN; 9,"DXF DXF2 ",TRANSPARENT,0,DOCUMENTATION; 10,"DXF DXF1 ",TRANSPARENT,0,DOCUMENTATION; 11,"DXF 0 ",TRANSPARENT,0,DOCUMENTATION; 12," TOP MASK ",TOP,0,SILKSCREEN; :EOD 2.5.1​ LAYER_TYPE LAYER_TYPE defines the type of layer material or the type of data contained in the layer: Layer Type Layer Data Content ELECTRICAL Part pads, vias & routing data and includes all copper layers. FABmaster uses the layers to determine the routing of interconnections. ASSEMBLY Part package Outline contours, i.e. part physical Outlines that FABmaster uses to determine the limits of a part package for insertion path calculation, test point clearance, etc. SILKSCREEN Contains information which is to be printed on the board. BOARD_CUTOUT Data relating to the board outline routing, contouring and internal cut-outs. DXF Data output from FABmaster to a DXF file, modified on AutoCAD (or EasyCAD) and then re-input into FABmaster. MASKING Contains "negative" data such as solder & epoxy masks. DOCUMENTATION (Default) Any other type of non-electrical data. 2.5.2​ LAYER_SENSE LAYER_SENSE defines how the layer must be displayed. A layer can be displayed: *​ on all the other layers: COMMON. *​ from the TOP. *​ from the BOTTOM. *​ through the board: TRANSPARENT. Layer Sense Display COMMON Layers which contain data common to all the layers, e.g. drill pads. TOP Layers visible from the top of the board only; often referred to as the component side. BOTTOM Layers visible from the bottom only; often referred to as the solder side. TRANSPARENT Can contain any data, but generally only contain the inner electrical layers of multilayer boards. Documentation and other layers are usually assigned TOP but can be designated TRANSPARENT if necessary. ! In a FATF database, all SMD parts must be stored on the TOP layers only. If an SMD is on the bottom, TOP layer data is flipped automatically during display to the BOTTOM as described below: FLIP_LAYER_ID. 2.5.3​ LAYER_NAMES LAYER_NAMES are used to define the layers used on the PCB. One line describes each layer. LAYER_ID Mandatory integer. Layers must be numbered consecutively with a LAYER_ID from 1 to n. LAYER_ID is then used to refer to the layer. LAYER_NAME Optional name to describe the layer which is truncated to 12 characters automatically after input into FABmaster. LAYER_NAME, if defined, will be displayed on FABmaster to help the user during the display set-up. LAYER_SENSE Describes the layer display. A layer can be displayed on all layers, from the top side only, from the bottom side only or transparently through the board. See LAYER_SENSE (§ 2.5.2). LAYER_TYPE Defines the type of layer material or type of data contained in the layer. See LAYER_TYPE (§ 2.5.1). FLIP_LAYER_ID Controls the flipping of SMD parts to the BOTTOM layers. 1,"TOP COPPER",TOP,2,ELECTRICAL; 2,"BOTTOM COPPER",BOTTOM,1,ELECTRICAL; An SMD part has copper data