rtheda

  Read Module : Incases Theda

File | File Import | Incases Theda Read

Router

Database Class: NET

System: Computervision Theda

Hardware Platform: SUN

Version: 2 to 3.1

Operating Systems: UNIX

RSI Call Out: THED

Input File Format:.TL

Command Sequence to Generate file(s): board save TL

Make sure, that all SCOPES are saved.

Output File Format:.TL

Command Sequence to Load file(s): Normal file load

General Comments:

Board outline is PSEUDO REAL.

LIBRARY definition needed.

TL SYNTAX from Version 2 to 3.1 supported.

Input Comments:

1.PARTS that contain mirrored and or rotated symbols in Theda are 	not supported.

2.VOID AREAS without parents are supported.

   	3.COMPACT output TL-SYNTAX is not supported by RSI-Reader.

   	4.MOUNTING HOLES and other free standing pads are not supported.

   	5.CHAMFERED Arcs (Radius Value in Polylines) are not supported.

   	6.DIMENSION scope is not supported.

   	7.COMPONENTs without Reference Designator names are not

 	translated.

   	8.PHISICAL KEEPOUTS section is not currently supported.

LAYER DEPENDENT PADSTACK DEFINITION :

Theda allows the definition of different Padstack Graphics, dependent on which Layer the pad ends up being placed. This is not supported.

LAYDBASE allows in the Setup file to normalize a Padgraphic, which will change the Layername. This, however may duplicate Graphic elements.

Output Comments:

NAMED COPPER AREAS crashes Theda during file load, therefore all copper areas are translated as unnamed.

Incases Theda (TL) Reader

Theda allows the same definition names for Shapes, Padstacks and Packages.

CAMCAD will add a prefix to these names, so that no duplicated name occurs:

TL section	Added Prefix

Shapes	SHAPE_

Padstack	PADSTACK_

Incases Theda Reader

File Used for Import: TL file

How to Produce file:

System Supported:

There is currently no import setup (*.IN) file used with the Incases Theda reader.

Incases Theda (TL) Reader

There are no special considerations for importing Theda (TL) files into CAMCAD for HP3070. Please refer to the general CAMCAD help file for help on this subject.


rallegro

  Read Module : Allegro File

File | File Import | Allegro File

Cadence Allegro files have the default extension .brd. These binary files must be first "extracted" into ASCII files, before loading into CAMCAD. The extract is a program in the Allegro System and must be executed using the CAMCAD "valext.txt" file. The CAMCAD Allegro reader is user definable and adapts automatically to add-ons and changes in the extract file. However, the beginning records of the extract file must stay identically. The user can change the attribute section of the extract file.

"valout.txt" example as supplied with CAMCAD:

#

# VALID ALLEGRO OUTPUT SCRIPT FOR ROUTER SOLUTIONS SOFTWARE

#

# This Script creates 4 files : BRD.TXT PAD.TXT SYM.TXT RTE.TXT

#

# This is the new modified version May 92. (Router Solutions Inc.)

# This is the new modified version APR 94. (Router Solutions Inc.)

#	Component values, partnumber and type was added.

#

# This is the new modified version MAY 94. (Router Solutions Inc.)

#               Pin Rotation was added. This only work from

#               Allegro version 6.

#

# This is the new modified version JUN 94. (Router Solutions Inc.)

#               Test point was added.

#

# This is the new modified version DEC 96 (Router Solutions Inc.)

#	User properties added.

# Board section was never used. Exchange it for Layer information

#BOARD

#	BOARD_NAME

#	BOARD_UNITS

#	BOARD_EXTENTS_X1

#	BOARD_EXTENTS_Y1

#	BOARD_EXTENTS_X2

#	BOARD_EXTENTS_Y2

#	BOARD_LAYERS

#END

LAYER

LAYER_SORT

LAYER_SUBCLASS

LAYER_ARTWORK

LAYER_USE

LAYER_CONDUCTOR

LAYER_DIELECTRIC_CONSTANT

LAYER_ELECTRICAL_CONDUCTIVITY

LAYER_MATERIAL

LAYER_SHIELD_LAYER

LAYER_THERMAL_CONDUCTIVITY

LAYER_THICKNESS

END

PAD_DEF

END

GEOMETRY

# GENERATES PLACEMENT, SYMBOL, AND ETCH INFORMATION

  SYM_TYPE

  SYM_NAME

  REFDES

  SYM_X

  SYM_Y

  SYM_ROTATE

  SYM_MIRROR

  NET_NAME

  CLASS

  SUBCLASS

  RECORD_TAG

  GRAPHIC_DATA_NAME

  GRAPHIC_DATA_NUMBER

  GRAPHIC_DATA_1

  GRAPHIC_DATA_2

  GRAPHIC_DATA_3

  GRAPHIC_DATA_4

  GRAPHIC_DATA_5

  GRAPHIC_DATA_6

  GRAPHIC_DATA_7

  GRAPHIC_DATA_8

  GRAPHIC_DATA_9

  GRAPHIC_DATA_10

  COMP_DEVICE_TYPE

  COMP_PACKAGE

  COMP_PART_NUMBER

  COMP_VALUE

# User Attributes are added here

  BARCODE

  BOARD_FIDUCIAL

  BOARD_TOOLING

  BREAKAWAY

  CUTOUT

  PANEL_FIDUCIAL

  PANEL_TOOLING

  ROBBER_BAR

  CLIP_DRAWING

END

COMPOSITE_PAD

# GENERATES VIA AND NETLIST INFORMATION

# from here on down, these are user attributes and are optional

  NET_NAME

  PIN_NUMBER_SORT

  CLASS

  REFDES

  SYM_TYPE

  SYM_NAME

  SYM_X

  SYM_Y

  SYM_ROTATE

  SYM_MIRROR

  PIN_NAME

  PIN_NUMBER

  PIN_X

  PIN_Y

  PAD_STACK_NAME

  VIA_X

  VIA_Y

# for Version 6

  PIN_ROTATION

  TEST_POINT

  NET_PROBE_NUMBER

END

# End of VALOUT.SCR

================= end of example

Allegros extract program will return an error message, if you try to extract non-existant attributes.

How to run extract:

extract

<enter brd file name>	: your_file_name

<enter .txt extract script> : valout.txt //  will need 4 files, hit return on the fifth.

<enter filename> : brd.txt

<enter filename> : pad.txt

<enter filename> : sym.txt

<enter filename> : rte.txt

<enter filename> : <return>	// no file name

Now the program will execute. Check extract.log for error messages.

The loading of the Allegro files can be in any order, or in simultanious selection.

.MIRRORLAYER in ALLEGRO.IN

In the extracted files, all components are exploded. This means every instance of a 1206 Resistor (R1,R2,R3) has its own library definition. CAMCAD rebuilds a library from the exploded data. Therefore the first instance of a shape becomes the master, from which all other instances are derived. To rebuild the mirrored shapes correctly, CAMCAD looks into the .MIRRORLAYER in the ALLEGRO.IN to "unmirror" layers.

File load sequence:

The 4 script files can be loaded in any sequence, however to correctly update BOARD_FIDUCIAL and PANEL_FIDUCIAL, it is important that the .s file (3rd file from extract) is loaded before the .r (4th file from extract). Only this guaranties that the FIDUCIAL of the pins are updated correctly with the symbol inserts.

SMD pad recognition:

A pad is flagged to be SMD if no drill diameter is set.

SMD component recognition:

SMD componenets are recognized like in CCMout. See SMD rule flag

in ALLEGRO.IN.

PADFORM SHAPE (complex outline) is read in as a Rectangle with X and Y size as defined in the extract file.

· Allegro EDA PCB Reader

Cadence Allegro files have the default extension .brd. These binary files must be first "extracted" into ASCII files, before loading into CAMCAD. The extract is a program in the Allegro System and must be executed using the CAMCAD "valext.txt" file. The CAMCAD Allegro reader is user definable and adapts automatically to add-ons and changes in the extract file. However, the beginning records of the extract file must stay identically. The user can change the attribute section of the extract file.

"valout.txt" example as supplied with CAMCAD:

#

# VALID ALLEGRO OUTPUT SCRIPT FOR ROUTER SOLUTIONS SOFTWARE

#

# This Script creates 4 files : BRD.TXT PAD.TXT SYM.TXT RTE.TXT

#

# This is the new modified version May 92. (Router Solutions Inc.)

# This is the new modified version APR 94. (Router Solutions Inc.)

#	Component values, partnumber and type was added.

#

# This is the new modified version MAY 94. (Router Solutions Inc.)

#               Pin Rotation was added. This only work from

#               Allegro version 6

· Allegro PCB Reader

File Used for Import: Allegro Extract (brd.txt, pad.txt, sym.txt, and rte.txt)

How to Produce File: To execute the Allegro extract utility, perform the following steps:

From the UNIX command prompt...

>extract <return>

You will be prompted for:

Layout name (*.brd): path/filename <return>

Extract command file (*.txt): path/valout <return>

Extract output filename (*.txt): path/brd <return>

Additional output filename (<return> if none) (*.txt): path/pad <return>

Additional output filename (<return> if none) (*.txt): path/sym <return>

Additional output filename (<return> if none) (*.txt): path/rte <return>

Additional output filename (<return> if none) (*.txt): <return>

(Please refer to the "Extract Supplement" below if you receive errors during the extraction.)

This creates the following files that are used as input for CAMCAD.

brd.txt

pad.txt

sym.txt

rte.txt

The "valext.txt" script is supplied by RSI through the CAMCAD installation. The output files must be in the described sequence.

CAUTION: If there is text on the manufacturing layer PROBE_BOTTOM the Allegro extract program may go into an endless loop. The effect will be for the SYM file to continually grow until all disk space is exhausted.

Systems Supported: Cadence Allegro v: 6.0 through current (the Allegro Extract utility is only provided by Cadence with installs of Allegro on Unix platforms.)

Extract Supplement:

Allegro may crash during the extract. This is because some user-defined attributes, which are specified to be extracted in the valext.txt script, may not exist in the binary database. Please check the extract.log file produced by the extract utility for a listing of the non-existing attributes that must be commented out of the valext.txt extract script prior to running. Such an error would appear in the extract.log file as follows:

# User Attributes are added here

BARCODE

Field 'BARCODE' is unknown.

This means that in the valext.txt after the line "# User Attributes are added here" there is a line with "BARCODE" as an attribute to be extracted that does not exist in the database being extracted. This "BARCODE" line in the valext.txt extract script must be commented out using the pound symbol (# BARCODE). Subsequently, any attributes not in the valext.txt that are desired to be extracted may each be entered on a new line following the line reading "# User Attributes are added here". For further information regarding the Allegro Extract utility and the use of extract scripts please refer to the Allegro documentation.

Allegro Extract Reader setup for Intermediate 3D-Layout Writer (*.ccs)

The Allegro Extract input is configured using an import setup file called ALLEGRO.IN in the CAMCAD directory. This file uses several commands to setup certain information for importing the database correctly for proper 3D-Layout Extraction. The information in the setup file includes, but is not limited to, the following list of commands, their function and usage.

ALLEGRO.IN - Import setup for Cadence Allegro Extract file reader. All lines must start with a ";" for a comment line and a "." for a command.

.BOARDOUTLINE	"BOARD GEOMETRY"     "BD_OUTLINE"

This command is used to define the Allegro "Class" and "Sub-Class" from which to extract the board outline of the PCB. This is a crucial information for the Intermediate 3D-Layout Writer (*.ccs).

.COMPOUTLINE           "PACKAGE GEOMETRY"      "ASSEMBLY_TOP"

This command is used to define the Allegro "Class" and "Sub-Class" from which CAMCAD should extract the component outline to be used for extruding the component. This is a crucial information for the Intermediate 3D-Layout Writer (*.ccs).

· Allegro PCB Reader

File Used for Import: Allegro Extract (brd.txt, pad.txt, sym.txt, and rte.txt)

How to Produce File: To execute the Allegro extract utility, perform the following steps:

From the UNIX command prompt...

>extract <return>

You will be prompted for:

Layout name (*.brd): path/filename <return>

Extract command file (*.txt): path/valout <return>

Extract output filename (*.txt): path/brd <return>

Additional output filename (<return> if none) (*.txt): path/pad <return>

Additional output filename (<return> if none) (*.txt): path/sym <return>

Additional output filename (<return> if none) (*.txt): path/rte <return>

Additional output filename (<return> if none) (*.txt): <return>

(Please refer to the "Extract Supplement" below if you receive errors during the extraction.)

This creates the following files that are used as input for CAMCAD.

brd.txt

pad.txt

sym.txt

rte.txt

The "valext.txt" script is supplied by RSI through the CAMCAD installation. The output files must be in the described sequence.

CAUTION: If there is text on the manufacturing layer PROBE_BOTTOM the Allegro extract program may go into an endless loop. The effect will be for the SYM file to continually grow until all disk space is exhausted.

Systems Supported: Cadence Allegro v: 6.0 through current (the Allegro Extract utility is only provided by Cadence with installs of Allegro on Unix platforms.)

Extract Supplement:

Allegro may crash during the extract. This is because some user-defined attributes, which are specified to be extracted in the valext.txt script, may not exist in the binary database. Please check the extract.log file produced by the extract utility for a listing of the non-existing attributes that must be commented out of the valext.txt extract script prior to running. Such an error would appear in the extract.log file as follows:

# User Attributes are added here

BARCODE

Field 'BARCODE' is unknown.

This means that in the valext.txt after the line "# User Attributes are added here" there is a line with "BARCODE" as an attribute to be extracted that does not exist in the database being extracted. This "BARCODE" line in the valext.txt extract script must be commented out using the pound symbol (# BARCODE). Subsequently, any attributes not in the valext.txt that are desired to be extracted may each be entered on a new line following the line reading "# User Attributes are added here". For further information regarding the Allegro Extract utility and the use of extract scripts please refer to the Allegro documentation.

Allegro Extract Reader setup for Intermediate 3D-Layout Writer (*.ccs)

The Allegro Extract input is configured using an import setup file called ALLEGRO.IN in the CAMCAD directory. This file uses several commands to setup certain information for importing the database correctly for proper 3D-Layout Extraction. The information in the setup file includes, but is not limited to, the following list of commands, their function and usage.

ALLEGRO.IN - Import setup for Cadence Allegro Extract file reader. All lines must start with a ";" for a comment line and a "." for a command.

.BOARDOUTLINE	"BOARD GEOMETRY"     "BD_OUTLINE"

This command is used to define the Allegro "Class" and "Sub-Class" from which to extract the board outline of the PCB. This is a crucial information for the Intermediate 3D-Layout Writer (*.ccs).

.COMPOUTLINE           "PACKAGE GEOMETRY"      "ASSEMBLY_TOP"

This command is used to define the Allegro "Class" and "Sub-Class" from which CAMCAD should extract the component outline to be used for extruding the component. This is a crucial information for the Intermediate 3D-Layout Writer (*.ccs).

Allegro PCB Reader

Attributes in the Allegro extracts are not associated to any particular entity type. The user must assign attributes to an entity type (e.g. component) in the ALLEGRO.IN file. A list of any how attributes were mapped and any unused attributes is entered into the ALLEGRO.LOG file after the input file is processed.

There are no additional special considerations for importing Allegro files into CAMCAD for HP3070. Please refer to the general CAMCAD help file for help on this subject.


rvisula_cadstar

  Read Module : Visula & Cadstar-NT File

File | File Import | Visula & Cadstar-NT File

Router Solutions Incorporated

LAYDBASE - Input/Output Formats

1) General Description

2)	What files we need

2a)	How to create the files we need

3)	How to import your file

3a)	Input control file *.IN

3b)	The Log file

4)	Database class

Board Outline class

Component class

5)	Troubleshooting & Faqs

RSI Call Out: CADF

Database Class: Net

System: Cadstar for Windows, Visula

Hardware Platform: HP, SUN, Win

Version:

Operating Systems: UNIX

Input File Format: .paf file

Output File Format: PAF file

Command Sequence to Load file(s):

The PAF file in read or written in Visula -> File -> Neutral Database -> Read/Write

Cadstar is not dependant on technologies, though the translator requires a technology file. It is suggested that the standard TT6 technology file be used.

On the other hand, the Visula system is dependent on Technologies. Only defined technologies are allowed (TT2, TT4, TT6), other technologies received from customers are specific to that customer. You can not add layers to a technology.

General Comments:

None at this time.

Input Comments:

Tested version is CADIF 4.0

Padforms are derived from the PADASSIGN section. (not from the padstack section). Therefore PADFORMS are the same, regardless of the placement side of the shape.

A Cadstar defined "island" within a boundry area is not supported.

All Pins are converted to the original defined pin numbers (not the optional pin names).

Only 90° pad rotation is allowed.

Round Padform is translated as Round.

Anulus Padform is translated as Round.

Square Padform is translated as Square.

Diamond Padform is translated as Round.

Octagon Padform is translated as Square.

Finger Padform is translated as Oblong.

Oblong Padform is translated as Rectangle.

Bullet Padform is translated as Oblong.

Copper padform is translated as Round padform.

Dimension entities are ignored.

ZONE placed components are not supported.

Circles and polygons with voids are converted to polygons.

Taper lineends and pads are ignored.

Copper areas are not completely supported.

Copper voids are not completely supported.

Closed polylines containing arcs will not be filled.

Output Comments:

Supported Visula version 3.5 and 4.

Cadstar for Windows Version 2.0

Pin Names are converted to Pin Numbers

After loading into Cadstar there may be some non-optimized "ratsnests". Simply run the Cadstar Reconnect function.

Cadstar v 2.1 may still show missing connections even though all traces are routed (hopefully this will be fixed in a future release of Cadstar).

Copper (Electrical layers) as part of a shape (packAlt) are not translated. (Visula seems not to allow SYMDATA on electrical layers).

INPUT means RSI can READ the database and

OUTPUT means RSI can WRITE the database.

Visula & Cadstar-NT PCB Reader

Files Used for Import: CADIF

How to Produce files: File | Export - CADIF

System Supported: CADIF files from Redac Visula and CadStar for Windows.

CadStar/Visula CADIF Reader setup for Intermediate 3D-Layout Writer (*.ccs)

The CADIF input is configured using an import setup file called CADIF.IN in the CAMCAD directory. This file uses several commands to setup certain information for importing the database correctly for proper 3D-Layout Extraction. The information in the setup file includes, but is not limited to, the following list of commands, their function and usage.

CADIF.IN - Import setup for CadStar/Visula reader. All lines must start with a ";" for a comment line and a "." for a command line.

.BOARDOUTLINE	"BOARD"

This command is used to define the CadStar/Visula layer from which to extract the board outline of the PCB. This is a crucial information for the Intermediate 3D-Layout Writer (*.ccs).

.COMPOUTLINE      "L241"

This command is used to define the CadStar/Visula layer from which CAMCAD should extract the component outline to be used when extruding the component. This is a crucial information for the Intermediate 3D-Layout Writer (*.ccs).

Visula & CADstar-NT PCB (CADIF) Reader

The mirror layers for CADIF files must be set either in the CADIF.IN file or manually in the CAMCAD Layer dialog. If the mirror layer is not set properly, pads on the back side of the PCB will still be shown on the component side of the PCB.


rveribest

  Read Module : VeriBest EIF File

File | File Import | VeriBest EIF File

Router Solutions Incorporated

LAYDBASE - Input/Output Formats

1) General Description

2)	What files we need

2a)	How to create the files we need

3)	How to import your file

3a)	Input control file *.IN

3b)	The Log file

4)	Database class

Board Outline class

Component class

5)	Troubleshooting & Faqs

RSI Call Out: EIF

Database Class: NET

System: Veribest EIF Files

Hardware Platform(s): Sun

Version(s): 1.0, VB14

Operating Systems(s): UNIX

Update yourself!!

Get the latest EIF.SYM translator setup file modified

06/27/97 to make use of all your VeriBest layers.

Included are modified versions of VeriBest's EIF into

VBPCB level mapping files (EIF_LEVX.TXT and VBPCB.LVL).

Input File Format:

EIF Files Intergraph/Veribest supports EIF output for the following products:

     Daisy Boardmaster 4.5 +

     AT Designer 12.4

     Cadnetix any Version F

     PCB Engineer has to be upgraded to AT Designer

Command Sequence to Generate file(s):

The following seven (7) files are created on EIF output from Veribest. 	1.filename_cor.txt - Rename to filename.cor

          Correspondence file.

   	2.filename_cel.txt - Rename to filename.cel

          Cell definition file

   	3.filename_clr.txt - Rename to filename.clr

          Clearance file

   	4.filename_des.txt - Rename to filename.des

          Design file

   	5.filename_pad.txt - Rename to filename.pad

          Pad geometry file

   	6.filename_pin.txt - Rename to filename.stk

          Padstack (Pin) file

   	7.filename_tec.txt - Rename to filename.tec

          Technology file, layer stacking

A Keyin netlist must also be extracted from Veribest.

The Keyin-netlist to be renamed to filename.net

If you have any questions on which files should receive which extention please refer to the correspondence file (open with ascii viewer).

Output File Format:Listed below.

Command Sequence to Load file(s):

The following files are generated by EIFOUT

   	1.*.cel -- Cell definition file

   	2.*.clr -- Clearance file

   	3.*.cor -- Correlation file

   	4.*.des -- Design file

   	5.*.net -- Keyin Netlist

   	6.*.pad -- Pad geometry file

   	7.*.pkg -- Package file

   	8.*.stk -- Padstack (Pin) file

   	9.*.tec -- Technology file, layer stacking

Veribest EIF import procedure.

First create an empty design directory.

     C:\>md design1

     C:\>cd design1

Copy the created EIF files into this empty design directory.

     C:\design1>copy rsi\xxxeif\filename.*

     C:\design1>copy rsi\xxxeif\eifo_cor.txt

Copy all files from the veribest\vbpcb\libelect\pcbseed directory into the design directory.

     C:\design1>copy veribest\vbpcb\libelect\pcbseed\*.*

21 files should be copied over.

Run Veribest PCB from the Windows "Start" menu.

     Start | Programs | Veribest PCB | Veribest PCB

When the "Open a Design File" file selection dialog box opens, navigate to your design directory and select the file "design.vdb" and click on the "OPEN" button.

Veribest PCB and MicroStation will open and load the design.vbd file.

Now the EIF load may be performed. This is found under:

     File | Import | EIF

When the "EIF import" dialog opens select all option boxes (do not modify Radio Button selections) then click the "OK" button.

This will load the EIF files located in the directory from which the design.vbd was loaded.

A timed dialog box should appear followed by a message "EIF imported successfully". Click "OK".

At this point the padstacks must be processed. From the menu bar select:

     Route | Pads Processor

When dialog box appears click "OK".

The EIF load procedure is now complete. The file may now be saved out under its proper name.

     File | Save As

If a File | Save is performed the design will be saved out as design.vbd in your design directory.

General Comments:

Board outline is REAL.

LOCAL COMPONENT driven.

The EIF files are compatible with both INTERGRAPH AT-DESIGNER and VeriBest-PCB system.

All files are in ASCII and fully portable between hardware platforms.

Input Comments:

The (.USECORFILE y) command in the EIF.TEC file will load all files for translation automatically. The EIFO_COR.TXT must be renamed to file_name.COR and this .COR file specified as the input.

Spaces in layer names are eliminated. e.g. "COMP NAME" --> COMPNAME

Local component definition in design file under part placement is not supported. The shape is taken from the cell library definition.

PART_DEF, VIA_DEF, AND CELL_DEF - Local part definition in design file is not supported --> Violates the library concept.

Mounting Holes are not supported (MH in CEL file and DES file are not translated).

Layernames in EIF files can contain whitespace (blanks). These spaces are removed while reading the files into the LAYDBASE system. Therefore the Layer "Trace Layer 1" will be changed to "TraceLayer1". This is important for the correct setup in the STP files.

Pin Stack definitions must contain all the pin graphic information. pad Entries under a Shape are converted as graphic elements and they are not associated with Pins. Pins, which are CROSS_HAIR shapes will get the graphic of the PAD entry which is on the same placement

coordinate. Pads, which fall on Pin coordinates of pins, which are not CROSS_HAIR shapes will be ignored.

Pad Shapes - ROUND_HOLLOW will be converted to ROUND FILLED.

SQUARE_HOLLOW will be converted to SQUARE FILLED.

Pin and Pad assign: They are as Pins and Pads in the EIF cell files. The default and good definition should be that the pin defines the correct PADSTACK (defined in STK file). However there are two more ways that a PAD definition can influence the pin PADSTACK

definition:

   	1.. PADOVERWRITEPIN y will always overwrite the pinstack with 	multiple PAD forms on multiple layers. The PAD center MUST be 	identical for all pad forms.

   	2.In EIF.TEC you can use the command .PADOVERWRITE padform . This 	will only overwrite a PIN form (i.e. Crosshair) which is set with 	.PADOVERWRITE ... Multiple PADOVERWRITEs are allowed. The pin is 	only overwritten if the placement coordinate is equal between pad 	and pin.

 Planes :

PLANE_OUTL SOLID is translated as a solid plane.

PLANE_OUTL HOLE are voids.

Planes are not parents of voids.

SMD Pins are defined with graphic on TOP_PAD and BTM_PAD. Only the graphic for TOP_PAD is translated for SMD pads. SMD pads are Pads, which have no drill size.

Non centered PADS geometries are not supported. Non centered pad geometries are padstacks, which have a XOFF and YOFF not equal 0.0.

ELLIPSE as graphic entity is not supported.

Cells defined as EGDE CONNECTORS do not reflect the mirrror of this connector, and therefore all pins are converted to the TOP layers, even that the pins should be on the BOTTOM layer. VERIBEST needs to fix the mirror flag in EIF-Des file. The current workaround is to

redefine the EDGE CONNECTOR before generating the EIF files to a SMD component.

Output Comments:

Veribest EIF scanner drops parts which are placed at angles other than 0, 90, 180, and 270 degrees.

Veribest supports only one offset axis in pad definitions.

The user must set plane connections within the Veribest environment.

     SETUP|JOB PERAMETER

     ROUTE|PLANES|PLANE PROCESSOR

INPUT means RSI can READ the database and

OUTPUT means RSI can WRITE the database.

VeriBest PCB Reader

The EIF output processor generates multiple EIF files. The easiest way to import is to use the Correspondance file, but also single loading of files is allowed. CAMCAD needs the

following files as minumum:

PAD

PADSTACK

CELL_LIB

DESIGN

NETLIST

Typcial Correspondance file example:

.FILETYPE CORRESPONDENCE

.VERSION "VB14.00"

.CREATOR "Intergraph"

.PAD "eifo_pad.txt"

.PADSTACK "eifo_pin.txt"

.CELL_LIB "eifo_cel.txt"

.CLEARANCE "eifo_clr.txt"

.TECHNOLOGY "eifo_tec.txt"

.DESIGN "eifo_des.txt"

.PDB_ASCII "asciipdb.txt"

.NETLIST "netlist.kyn"

VeriBest PCB Reader

File Used for Import: Massteck Interchange format

How to Produce file: Export | Massteck interchange

System Supported: Massteck - MAX EDA Revisions 6 and 7

There is currently no import setup (*.IN) file used with the OrCAD for Windows reader.


rpfw

  Read Module : Protel For Windows File

File | File Import | Protel For Windows

GENERAL DESCRIPTION

IMPORT SPECIFICATIONS

SYSTEM:	PROTEL for Windows

VERSION:	2.7

IMPORT FORMAT:	.PCB (ASCII)

CREATING THE IMPORT FILE

In the PROTEL for Windows environment perform the following

steps:

1) FILE MENU | SAVE AS

2) Select the TEXT Option

3) Name the File

4) Select OK

IMPORTING INTO CAMCAD

Show the Import Dialog box

ITEMS CONTROLLED BY PROTEL.IN

UNDERSTANDING THE PROTEL.LOG FILE

general

unique

DATABASE CLASSIFICATIONS

DATABASE CLASS:	Net

BOARD OUTLINE CLASS:	PSEUDO or REAL

COMPONENT CLASS:	LIBRARY or EXPLODED

Need popup windows for PSEUDO, REAL, LIBRARY and EXPLODED

LOCAL PADSTACK DEFINITIONS

	IMPORT FILE	CAMCAD
BLIND VIAS SUPPORTED	YES	NO
BURIED VIAS SUPPORTED	YES	NO
COMPLEX PAD SPECIFICATIONS	YES	NO
SOLDERMASK INFORMATION
TROUBLESHOOTING and FREQUENTLY ASKED QUESTIONS

Protel For Windows PCB Reader

File Used for Import: Massteck Interchange format

How to Produce file: Export | Massteck interchange

System Supported: Massteck - MAX EDA Revisions 6 and 7

There is currently no import setup (*.IN) file used with the Protel for Windows reader.


rpcad

  Read Module : PCAD File

File | File Import | PCAD File

Router Solutions Incorporated

LAYDBASE - Input/Output Formats

RSI Call Out: PDIF

Database Class:

System: PCAD

Hardware Platform: PC

Version: 2 thru 8

Operating Systems: DOS

Input File Format: .PDF

Command Sequence to Generate file(s):

PDIFOUT -I pcb_file where pcb_file is the PCAD .PCB file (Binary Database)

Also on PDIF export from the PCad user interface, under PDIF OUT Option, make sure that " List Pin Names in Component " is selected (yes), default value is NO. Failure to do this will result in

the pin sequence to be used in the target database rather than the desired pin numbers.

Output File Format: .PDF

Command Sequence to Load file(s):

PDIFIN -I pdf_file where: pdf_file is the RSI generated .PDF file.

This creates a PCAD .PCB file which can be loaded into PCAD using the standard file load.

General Comments:

Board outline is PSEUDO.

LIBRARY definition, but Pad forms can be locally defined.

DIMENSION entities are not supported in RSI Input and Output software.

PDIF translators work on the library definition, the same as PCCARDS if ROTATE PADSTACKS is switched on in the PCB Editor Configuration.

Input Comments:

PDIF file has no drill information.

PDIF Version 7 is fully (including Aperture Table) supported.

PCAD allows for the local redefinition of pad stacks. This is not supported by laydbase, only the master definition is translated.

FLASH Rotation in Padstack definitions is not supported.

SHAPE types for FLASHES are translated to Round except RECTANGLE are translated to Rectangle.

LOCAL Padstack overwrite (IPT command) is not supported.

P-CAD allows duplicate pin names(e.g. two pin 6's). This is not allowed in LAYDBASE or other CAD systems. To resolve this problem modify the .PINNAMENUMBER command in the PDIF.TEC file to be set to "y".

Output Comments:

The padstack definitions for PDIF output are generic. The user can modify or even link their own padstacks to fit their application.

Drill information is not included in the padstack inside the PDIF file. Please check the SSF file for more info.

For further information regarding Padstack and Drill information please view this technical document.

Be sure to switch on Padstack rotation before loading an RSI generated PDIF file.

PDIFIN version 5 can not read PDIF files larger than 1 mb.

Thermals are not converted automatically into PCAD the user must add thermal via the PCAD command "Query Netpin" - Shows you all pintype connected to a net, and "Query Netvia" to convert all viatypes used in a net.

Void areas without parents are not supported.

Built in APERTURE TABLE for PDIF Version 7 output not supported.

RSI Translators create specific output for different version of PDIF. This feature is controlled in the PDIF.SYM file by the ".VERSION" command. The options are;

.VERSION 4 D - this is for PDIF version 4 or PCAD version 4 and 5 	- MIL based units.

.VERSION 6 D - this is for PDIF version 6 or PCAD version 6, 7 	and 8 - SUB MIL based units

The "D" creates a PDIF file which is compatible to DOS naming limitations. This may be replaced with a "U" which will create a PDIF file with UNIX naming limitations. CAUTION - a DOS file can always be loaded into UNIX but a UNIX file may not be compatible with DOS.

INPUT means RSI can READ the database and

OUTPUT means RSI can WRITE the database.

 PCAD PCB Reader

Files Used for Import: PCAD PDIF

How to Produce files: PDIF write

System Supported: PDIF v: 2.0 through current.

PCAD PDIF Reader setup for Intermediate 3D-Layout Writer (*.ccs)

The PCAD PCB input is configured using an import setup file called PDIF.IN in the CAMCAD directory. This file uses several commands to setup certain information for importing the database correctly for proper 3D-Layout Extraction. The information in the setup file includes, but is not limited to, the following list of commands, their function and usage.

PDIF.IN - Import setup for PCAD PCB reader. All lines must start with a ";" for a comment line and a "." for a command line.

.BOARDOUTLINE	"BRDOUT"

This command is used to define the PCAD layer from which to extract the board outline of the PCB. This is a crucial information for the Intermediate 3D-Layout Writer (*.ccs).

.COMPOUTLINE      "SLKTOP"

This command is used to define the PCAD layer from which CAMCAD should extract the component outline to be used when extruding the component. This is a crucial information for the Intermediate 3D-Layout Writer (*.ccs).

PCAD PCB Reader

There are no special considerations for importing PCAD PCB files into CAMCAD for HP3070. Please refer to the general CAMCAD help file for help on this subject.


rorcad

  Read Module : PADS File

File | File Import | PADS File

Router Solutions Incorporated

LAYDBASE - Input/Output Formats

1) General Description

2)	What files we need

2a)	How to create the files we need

3)	How to import your file

3a)	Input control file *.IN

3b)	The Log file

4)	Database class

Board Outline class

Component class

5)	Troubleshooting & Faqs

PADS PCB-2000 and PADS Perform--See Section 1

PADS Power PCB--See Section 2

_________________________________________________________________

Section 1 PADS PCB-2000 and PADS Perform

RSI Call Out: PAD6

Database Class: PIN

System:  PADS Perform

Hardware Platform(s): PC / Sun / HP

Version(s):

Operating Systems(s): DOS - Windows / UNIX

Input File Format:.ASC

Command Sequence to Generate file(s):

1.From the In/Out menu select ASCII Out

2.Select Output Formats Basic Units

3.Select Sections to Output All

4.Fill in the the Output Filename field and select the OK button

Output File Format:

Command Sequence to Load file(s):

1.From the In/Out menu select ASCII In

2.Enter the name of the RSI generated .ASC file and hit enter

Recommended PADS Layering Scheme

1 Component Side

2-20 Other Electrical Layers - Solder Side is always the highest 	number.

21 Soldermask Top

 	22 Solder Paste Bottom

 	23 Solder Paste Top

24 Drill

25 Plane Clearance

26 Silkscreen Top

27 Assembly Top

 	28 Soldermask Bottom

 	29 Silkscreen Bottom

 	30 Assembly Bottom

General Comments:

For more information see PAD2 page.

Board outline is REAL.

For input to PADS POWER PCB, you must set the .UNIT command in 	PADS.SYM to MIL, otherwise the PADS POWER PCB makes errors in the 	PARTDECAL section.

Input Comments:

If mitres have been set then when performing the Pads ASCII out the "Convert MITRES to ROUTE SEGMENTS" check box must be selected for the mitres to appear in the ASCII file.

Mitres are 90° corners that are chamfered to 45° at 1/2 the grid distance.

If mitres are present and "Convert MITRES to ROUTE SEGMENTS" was not selected on ASCII out, then the RSI translator will generate an error and will exit. This can be overridden by changing the PADS.TEC file command .EXITMITREERROR to "n".

Part values are interpreted as follows:

R1 RC07,4.7K,10% = Shapename RC07

Value 4.7K

Tolerance 10%

Pads can rename pin names of Library components (DECAL) by type.

Example: 7400 DIP14

     Pin 1 -> AA1

     Pin 2 -> AA2

and

     7402 DIP14

     Pin1 -> BB1

     Pin2 -> BB2

This is a modification of the library. The RSI database converts these situations as follows:

One library shape will be created 7400_DIP14 with Pins AA1, AA2 	and another shape will be created 7402_DIP14 with pins BB1 and 	BB2.

Parts can be assigned as testprobes in .TEC file with .TESTPROBE xx (prefix of Decal name)

Output Comments:

Multiple via definitions are supported for loading data into PADS.

When complex copper areas are loaded into PADS a display error may occur during PADS ASCII IN.

Complex Pads are not supported.

To input unused vias the .UNUSEDVIA command in the .SYM file must be set to "y".

Different via sizes per net are not supported.

While loading files into PADS PCB (WORK), major limitations in the amount of information, no room for entities and other restrictions, may prevent the file being read into PADS. The only solution is to reduce the complexity of the input file (eliminating of layers). Laydbase Pads Writer software will not check for these limits, only for the syntax.

Necked Line Width might not be converted correctly due to a reported error in LAYDBASE.

Text elements per decal are limted to 5000 total characters. The exceeding text is not written out (so that the design loads into PADS).

All data and comments in this document are solely RSI's

interpretation or implementation of the applicable database.

INPUT means RSI can READ the database and

OUTPUT means RSI can WRITE the database.

____________________________________________________________________

Section 2 PADS Power PCB

RSI Call Out: PPWR

Database Class: Net based (different than PADS PERFORM)

System: PADS POWERPCB

Hardware Platform: PC, SUN, HP

Version: 1.5, 1.6, 2.0

Operating Systems: DOS, WINDOWS, UNIX

Input File Format:

Command Sequence to Generate file(s): From the In/Out menu select ASCII Out Select Output Formats Basic Units Select Sections to Output All Fill in the the Output Filename field and select the OK button

Output File Format:

Command Sequence to Load file(s):

From the In/Out menu select ASCII In Enter the name of the RSI generated .ASC file and hit enter.

PADS PowerPCB Version less than 1.5 may show load errors. Please update your PowerPCB to version 1.5 or better.

General Comments:

Board outline is REAL.

For input to PADS POWER PCB, you must set the .UNIT command in PADS.SYM to MIL, otherwise the PADS POWER PCB makes errors in the PARTDECAL section.

Input Comments:

The ASCII file needs to CONVERT MITRES to ROUTE SEGMENTS done.

Partvalues are interpreted as follows:

R1 RC07,4.7K,10% = Shapename RC07

Value 4.7K

Tolerance 10%

Pads can rename pin names of Library components (DECAL) by type.

Example: 7400 DIP14

Pin 1 -> AA1

Pin 2 -> AA2

and

7402 DIP14

Pin1 -> BB1

Pin2 -> BB2

This is a modification of the library. The RSI database converts these situations as follows:

One library shape will be created 7400_DIP14 with Pins AA1, AA2 and another shape will be

created

7402_DIP14 with pins BB1 and BB2.

The ASCII file needs to CONVERT MITRES to ROUTE SEGMENTS done.

Part can be assign as testprobes in .TEC file with .TESTPROBE xx (prefix of Decal name)

Output Comments:

Single Pin Nets are dropped when loading into Pads POWER.

Multiple via defintions are supported for loading data into PADS.

When complex copper areas are loaded into PADS a display error may occur during PADS ASCII IN.

Complex Pads are not supported.

Different via sizes per net are not supported.

Necked Line Width might not be converted correctly due to a reported error in LAYDBASE.

All electrical and netlist copper is converted to "Pourout" or "Voidout". The user has to flood in Pads.

Rats Nets update is not done global, but has to be done net by net. Pads Power PCB now treats nets as a collection of vias and segments. This now allows the interface software to "dump" all segments and vias into a net without worrying about "missing lines". PADS POWER will

automatically reconnect these segments.

If you now load a translated design into PowerPCb, you will first see all nets with rats nets, just go to routing menu, click a segment or via and again. PowerPCb will automatically recalculate the connection.

INPUT means RSI can READ the database and

OUTPUT means RSI can WRITE the database.

PADS PCB Reader

Component shapes and types in PADS.

PADS has a section DECAL and PARTTYPE.

DECAL is the physical, graphic description of a shape (i.e. DIP14).

PARTTYPE is a defintion of components which used one or more decals (alternates). The PARTTYPE is what places the component. A PARTTYPE also can change pinnames of a DECAL.

CAMCAD does the following:

DECAL : All DECALS are converted to Geometries.

PARTTYPES : are attached as a ATT_TYPE to a component.

If a PARTTYPE has alphapins, a new GEOMETRY (DECAL) gets created called TYPE_DECAL and the component gets this Geometry attached.

The CAMCAD Typelist must have a unique identification between component and its defintion. PADS can change a PARTTYPE with alternate Decals.

Layernames:

Pads has layer numbers and layer classes. CAMCAD assigns the following names to these classes:

PADS Layer numbers used in DECAL section are called DECAL_nr

PADS PCB Reader

Files Used for Import: PADS ASC

How to Produce files: IN/OUT | Export ASC (Perform), File | Export (Power)

System Supported: PADS Perform and PADS Power PCB through v 2.0

PADS .ASC Reader setup for Intermediate 3D-Layout Writer (*.ccs)

The Pads input is configured using an import setup file called PADS.IN in the CAMCAD directory. It may be necessary to modify this file to properly configure it for the Intermediate 3D-Layout Writer (*.ccs).

PADS.IN - Import setup for Pads Perform/Power reader.

The Board outline layer is always on the internally handled "board" layer. This is hard-coded in CAMCAD and can not be changed.

.COMPOUTLINE    "DECAL_0"

This command is used to define the layer from which CAMCAD should extract the component outline to be used when extruding the component. This is a crucial information for the Intermediate 3D-Layout Writer (*.ccs). If no outline is found on the specified layer CAMCAD will search for and use the outlines from all the other DECAL_* layers.

For explanations of the other commands in this file please refer to the CAMCAD standard help file for further documentation and usage.


rorcad

  Read Module : OrCAD File

File | File Import | OrCAD File

Router Solutions Incorporated

LAYDBASE - Input/Output Formats

1) General Description

2)	What files we need

2a)	How to create the files we need

3)	How to import your file

3a)	Input control file *.IN

3b)	The Log file

4)	Database class

Board Outline class

Component class

5)	Troubleshooting & Faqs

RSI Call Out: MASS

Database Class: NET

System: 	ORCAD LAYOUT PLUS

Massteck - MAX EDA

Hardware Platform: PC

Version: Revisions 6 and 7

Operating Systems: DOS

Input File Format:.MIN

Command Sequence to Generate file(s):EXPORT MASSTECK ASCII

To generate the proper .MIN file, under options, "all of the above" should be selected, which is the default setting.

Output File Format: .MIN

Command Sequence to Load file(s):IMPORT MASSTECK ASCII

General Comments:

Board outline is PSEUDO.

Input Comments:

Component value text is not supported as component value, but as text.

For mirrored components to work correctly the .MIN file must match the symbol name and the mirror name ("-M") and the UID (as suggested in the Orcad design process manual).

Orcad defines separate symbols for mirrored and non-mirrored components. If the mirrored component does not have the same UID as the non mirrored component then the translator will place the "mirrored" symbol from the TOP (not mirrored, because it was the mirrored definition).

Double PINNAMES : ORCAD LAYOUT PLUS allows same pinnames for different pin numbers. This is not allowed in RSI-LAYDBASE, and will be dropped.

ORCAD LAYOUT PLUS allows different technology by layer, this is not supported. The TECHNOLOGY is taken from the first electrical layer.

Only 90° pad rotation is supported.

Dimension Objects are not translated.

Output Comments:

Drill sizes will be written for drills with sizes greater than 0.00 inches for which DRD or DRL is the nick-name.

CIRCLES and ARCS are not currently supported.

VOID areas are not supported.

RING CONNECTIONS, which are part of an electrical net, are automatically optimized during the read process into MASSTECK. These ring connections will be lost.

There is a known error in the OrCad .MIN file reader in that it may periodicaly drop some routed traces.

Complex plane areas may cause the Orcad Min to Max converter to lock up. It is suggested not to convert these plane areas , rather to recreate them in Orcad.

OrCAD PCB Reader

File Used for Import: Massteck Interchange format

How to Produce file: Export | Massteck interchange

System Supported: Massteck - MAX EDA Revisions 6 and 7

There is currently no import setup (*.IN) file used with the OrCAD for Windows reader.


rpfw_creatingimportfile

  Read Module : Protel For Windows File

Creating the Import File

GENERAL

In the PROTEL for Windows environment perform the following

steps:

1) FILE MENU | SAVE AS

2) Select the TEXT Option

3) Name the File

4) Select OK


rpfw_ImportingintoCAMCAD

  Read Module : Protel For Windows File

Importing into CAMCAD


rpfw_ItemsControlledbyPROTEL.IN

  Read Module : Protel For Windows File

Items Controlled by PROTEL.IN


rpfw_UnderstandingthePROTEL.LOGfile

  Read Module : Protel For Windows File

Understanding the PROTEL.LOG file


rpfw_DatabaseClassifications

  Read Module : Protel For Windows

Database Classifications

DATABASE CLASS:	Net

BOARD OUTLINE CLASS:

COMPONENT CLASS:


rscicards_ImportSpecifications

  Read Module : Scicards/Harris-EDA

Import Specifications


rscicards_theImportFile

  Read Module : Scicards/Harris-EDA

Module Name: Scicards/Encore (CII) Layout Read

The Import File

The first step in using CAMCAD to view Scicards/Harris-EDA Encore files is to generate the CAD file used for import.  Whenever possible, verify that you are saving the maximum amount of data in generating the file.

Systems Supported: Scicards/Harris-EDA

Version: 2-8

Files Used for Import: .DAT (CII)

How to Produce files: Select from the menu commands:

Export | Readable | All Options On


rscicards_ImportingintoCAMCAD

  Read Module : Scicards/Harris-EDA

Importing into CAMCAD


rscicards_ItemsControlledBycii.IN

  Read Module : Scicards/Harris-EDA

Items Controlled by Cii.IN


rscicards_UnderstandingtheCii.LOGfile

  Read Module : Scicards/Harris-EDA

Understanding the Cii.LOG file


rscicards_DatabaseClassifications

  Read Module : Scicards/Harris-EDA

Database Classifications

Database Class:

Board Outline Class:

Component Class:


rtheda_CreatingtheImportFile

  Read Module : Incases Theda

Creating the Import File

Input File Format:.TL

Command Sequence to Generate file(s): board save TL

Make sure, that all SCOPES are saved.


rtheda_ImportingintoCAMCAD

  Read Module : Incases Theda

Importing into CAMCAD


rtheda_ItemsControlledbyTHEDA.IN

  Read Module : Incases Theda

Items Controlled by THEDA.IN


rtheda_UnderstandingtheTHEDA.LOGfile

  Read Module : Incases Theda

Understanding the THEDA.LOG file


rtheda_DatabaseClassifications

  Read Module : Incases Theda

Database Classifications

Database Class: Net

Board Outline Class: Pseudo

Component Class: Library


rmentorneu_theImportFile

  Read Module : Mentor Neutral File

Module Name: Mentor Neutral File Read

The Import File

The first step in using CAMCAD to view Mentor Neutral files is to generate the CAD file used for import.  Whenever possible, verify that you are saving the maximum amount of data in generating the file.

Systems Supported: Mentor Boardstation

Version: 8.x

Hardware Platform: SUN, HP

Operating Systems: UNIX

Files Used for Import: .NEU (ASCII)

How to Produce files: Load the CAD data into Mentor and select:

File | Create | Neutral File

This will create the ASCII file.  Be sure to include all of the data types.  Give the file a .NEU extension.

Note:  When creating a neutral file in Mentor the user has multiple options for what data to include. Selecting anything less than all options will result in missing data which is either imperative or at least useful in CAMCAD.


rmentorneu_ImportingintoCAMCAD

  Read Module : Mentor Neutral File

Importing into CAMCAD

The required module is Mentor Neutral File read.  There are no special considerations in importing .neu files.  For general file import information, refer to the CAMCAD Help Reference page Working With Files.

From the CAMCAD menu commands, choose

File | Import | Mentor Neutral File Read

Next, browse to the proper location and select the file. After the file is read in, a .log file will be produced to record import information.  Click the button "Place at Origin and Fit Page to Image" to place the file into the CAMCAD project window.


rmentorneu_ItemsControlledbyneutral.IN

  Read Module : Mentor Neutral File

Items Controlled by NEUTRAL.IN file

The Mentor Neutral File input is configured using an import setup file called NEUTRAL.IN in the CAMCAD directory. This file uses several commands to setup certain information for importing databases correctly. You are encouraged to open this file in a text editor and adjust the settings to properly import your CAD data.

The information in neutral.in includes, but is not limited to, the following list of commands, their function and usage.

NEUTRAL.IN - Import setup for Mentor Neutral File reader: All lines must start with a ";" for a comment line and a "." for a command line. NOTE: Attribute names in CAMCAD are case sensitive.

.BOARDOUTLINE   "BOARD_OUTLINE"

This command is used to define the Mentor layer from which to extract the board outline of the PCB.

.COMPOUTLINE   "COMPONENT_PLACEMENT_OUTLINE"

This command is used to define the Mentor layer from which CAMCAD should extract the component outline to be used when extruding or translating the component.

.HEIGHTATTR   comp_height   MM

This command is used to define the Mentor attribute that contains the height (Z-size) value. A Z-size unit descriptor follows the Mentor attribute name. The descriptor MM specifies that the  "value" of the height attribute is in Millimeters, IN is for Inches, MI is for Mils, and TN is for Internal Database Units.

CAMCAD for HP3070 Users:

The Neutral file has a section called "Board Added Part Information". This section contains the placement information for all Mentor GENERIC components. Unfortunately the description of these geometries are not defined anywhere in the Neutral file.  The parts placed in this section are always non-electrical and are usually unnecessary for the HP3070 output. However, in some cases items such as tooling holes and fiducials may be found in this section.

To provide a method of importing data in this section into CAMCAD, the NEUTRAL.IN file has three (3) special commands:

.FIDUCIALATTR   geometry_name

When a geometry of the name geomerty_name is found, a FIDUCIAL component is inserted at the XY coordinate specified by the B_ADDP statement. Since there is no description of a FIDUCIAL in the Neutral file a geometry with a single .020 diameter pad is inserted on FIDUCIAL1 layer for the top side or on FIDUCIAL2 layer for the bottom side.

.TOOLINGATTR   geometry_name

When a geometry of the name geomerty_name is found, a TOOLING HOLE is inserted at the XY coordinate specified by the B_ADDP statement. Since there is no description of a TOOLING HOLE in the Neutral file a 0.150 diameter drill is inserted into the database.

.GENERICATTR   geometry_name

When a geometry of the name geomerty_name is found, a GENERIC COMPONENTis inserted at the XY coordinate specified by the B_ADDP statement. Since there is no description of a GENERIC COMPONENT in the Neutral file a geometry containing a 0.100 diameter circle is inserted into the database.

.UNNAMEDNET [STRING]

Definition: When nets are encountered with the [STRING] as a prefix, the net will be renamed to "$$__REFDES.PIN" of some component pin on the net.

If the pin is unconnected, the net name will be as follows:

"NC__REFDES.PIN"


rmentorneu_Understandingtheneutral.LOGfile

  Read Module : Mentor Neutral File

Understanding the NEUTRAL.LOG file

When a file is imported into CAMCAD, a .LOG file is produced which records import information.

Unplaced Components Log Message:

It is posible for a neutral file to be created from a design which is not yet completed. This is most notable when there are components listed in the neutral file which never get physically placed on the PCB. This is not allowed in CAMCAD. Any unplaced components found in the input file will be placed at 0,0 and the following message will be added to the NEUTRAL.LOG file.

Unplaced Component [name] at line_number

Where:

name = then unplaced component reference designator

line_number = the line in the neutral file where the unplaced component was found


rmentorneu_DatabaseClassifications

  Read Module : Mentor Neutral File

Database Classifications

Database Class: Pin

Board Outline Class: Real

Component Class: Library


rmentor4_theImportFile

  Read Module : Mentor 4 File

Module Name: Mentor Board Station V8 Read

The Import File

The first step in using CAMCAD to view full Mentor Board Station files is to generate the CAD files used for import.  Whenever possible, verify that you are saving the maximum amount of data in generating the files.

Systems Supported: Mentor Boardstation, Fablink

Version: 8.2, 8.4

Hardware Platform: SUN, HP

Operating Systems: UNIX

Files Used for Import: ascii_geometries, comps.comps_*, nets.nets_*, traces.traces_*

1.  ascii_geometries: Definitions for all library elements in the design including board outline, panel definition, layer stack-up

2.  comps.comps_*: Component file, which is called in the Mentor system comps.comp.$x. This file has the component placement information, as well as reference designator, part number, and package..

3.  nets.nets_*:  Netlist file, which is called in the Mentor system nets.net.

4.  traces.traces_*:  Trace or Wire file, which is called traces.trace. This file has all the via, routing and filled area information.

How to Produce files: Only the ascii_geometries file needs to be saved in a special way, the other three files are in the standard Mentor format.

In Mentor Librarian select:

LOAD | PART FILE

File | SAVE | GEOMETRY ASCII > To Single File

Note:  Be sure to select the proper options to save all parts into a single ASCII file with a .PRT extension.

The standard Mentor names for the other files needed are as follows

comps.comps_*

traces.traces_*

nets.nets_*

Where * represents the highest number found for the file name specified.


rmentor4_ImportingintoCAMCAD

  Read Module : Mentor 4 File

Importing into CAMCAD

The required module is Mentor Board Station V8 Read. For general file import information, refer to the CAMCAD Help Reference page Working With Files.

When loading the Mentor files into CAMCAD, the Geometry ASCII file must be loaded first (like on the Mentor system). There after, once this file is loaded, all other files can be loaded in any order or combined.

From the CAMCAD menu commands, choose

File | Import | Mentor Board Station V8 Read

Next, browse to the proper location and select the .prt file. After the file is read in, a .log file will be produced to record import information.  Click the button "Place at Origin and Fit Page to Image" to place the file into the CAMCAD project window.

Repeat this procedure for the other three Mentor data files.

NOTE: RefDes  When RefDes is not placed BL (bottom left) a slight relocation of the RefDes may occur. The "right reading" command is not supported. Only one instance of the "^$ref" per component is supported (on components with multiple instances the first instance will be used).


rmentor4_ItemsControlledbyMENTOR.IN

  Read Module : Mentor 4 File

Items Controlled by MENTOR.IN

The Mentor 4 File input is configured using an import setup file called MENTOR4.IN in the CAMCAD directory. This file uses several commands to setup certain information for importing the database correctly.

The information in the setup file includes, but is not limited to, the following list of commands, their function and usage.

MENTOR4.IN - Import setup for Mentor 4 File reader. All lines must start with a ";" for a comment line and a "." for a command line.

.BOARDOUTLINE   "BOARD_OUTLINE"

This command is used to define the Mentor layer from which to extract the board outline of the PCB. This is a crucial information for the Intermediate 3D-Layout Writer (*.ccs) and the HP3070 Writer (*.brd, *.bxy).

.COMPOUTLINE   "COMPONENT_PLACEMENT_OUTLINE"

This command is used to define the Mentor layer from which CAMCAD should extract the component outline to be used when extruding or translating the component. This is a crucial information for the Intermediate 3D-Layout Writer (*.ccs) and the HP3070 Writer (*.brd, *.bxy).

.HEIGHTATTR   comp_height   MM

This command is used to define the Mentor attribute that contains the height (z-coordinate) value. The Mentor attribute name is followed by a measurement unit descriptor. The descriptor MM specifies that the  "value" of the height attribute is in Millimeters, IN is for Inches, MI is for Mils, and TN is for Internal Database Units. Be advised that attribute names in CAMCAD are case sensitive.


rmentor4_UnderstandingtheMENTOR.LOGfile

  Read Module : Mentor 4 File

Understanding the MENTOR.LOG file

The Mentor.LOG file will record specifics about the file import.  If an item, entity, attribute, or layer is influenced by a setting in the Mentor.IN file, it is recorded in the .LOG file.  To better understand any Mentro.LOG file entries, find and understand the relevant section in the .IN file.

There are no extra considerations for the Mentor.LOG file.


rmentor4_DatabaseClassifications

  Read Module : Mentor 4 File

Database Classifications

Database Class: Pin

Board Outline Class: Real

Component Class: Library


rallegro_CreatingtheImportFile

  Read Module : Allegro File

Creating the Import File

Cadence Allegro files have the default extension .brd. These binary files must be first "extracted" into ASCII files, before loading into CAMCAD. The extract is a program in the Allegro System and must be executed using the CAMCAD "valext.txt" file. The CAMCAD Allegro reader is user definable and adapts automatically to add-ons and changes in the extract file. However, the beginning records of the extract file must stay identically. The user can change the attribute section of the extract file.

"valout.txt" example as supplied with CAMCAD:

#

# VALID ALLEGRO OUTPUT SCRIPT FOR ROUTER SOLUTIONS SOFTWARE

#

# This Script creates 4 files : BRD.TXT PAD.TXT SYM.TXT RTE.TXT

#

# This is the new modified version May 92. (Router Solutions Inc.)

# This is the new modified version APR 94. (Router Solutions Inc.)

#	Component values, partnumber and type was added.

#

# This is the new modified version MAY 94. (Router Solutions Inc.)

#               Pin Rotation was added. This only work from

#               Allegro version 6.

#

# This is the new modified version JUN 94. (Router Solutions Inc.)

#               Test point was added.

#

# This is the new modified version DEC 96 (Router Solutions Inc.)

#	User properties added.

# Board section was never used. Exchange it for Layer information

#BOARD

#	BOARD_NAME

#	BOARD_UNITS

#	BOARD_EXTENTS_X1

#	BOARD_EXTENTS_Y1

#	BOARD_EXTENTS_X2

#	BOARD_EXTENTS_Y2

#	BOARD_LAYERS

#END


rallegro_ImportingintoCAMCAD

  Read Module : Allegro File

Importing into CAMCAD


rallegro_ItemsControlledbyAllegro.IN

  Read Module : Allegro File

Items Controlled by ALLEGRO.IN


rallegro_UnderstandingtheAllegro.LOGfile

  Read Module : Allegro File

Understanding the ALLEGRO.LOG file


rallegro_DatabaseClassifications

  Read Module : Allegro File

Database Classifications

Database Class:

Board Outline Class:

Component Class: Local


rpads_GeneralDescription

  Read Module : PADS File

General Description


rpads_CreatingtheImportFile

  Read Module : PADS File

Creating the Import File

For Pads Perform: From the menu commands, choose

     IN/OUT | Export ASC

For Pads Power: From the menu commands, choose

     File | Export

In either case, the file extension should be .asc.


rpads_ImportingintoCAMCAD

  Read Module : PADS File

Importing into CAMCAD


rpads_ItemsControlledbypads.IN

  Read Module : PADS File

Items Controlled by PADS.IN

The Pads input is configured using an import setup file called PADS.IN in the CAMCAD directory. It may be necessary to modify this file to properly import your CAD file.

PADS.IN - Import setup for Pads Perform/Power reader.

The Board outline layer is always on the internally handled "board" layer. This is hard-coded in CAMCAD and can not be changed.

.COMPOUTLINE  "DECAL_0"

This command is used to define the layer from which CAMCAD should extract the component outline to be used when extruding or translating the component. This is a crucial information for the Intermediate 3D-Layout Writer (*.ccs) and the HP3070 Writer (*.brd, *.bxy). If no outline is found on the specified layer CAMCAD will search for and use the outlines from all the other DECAL_* layers.

.LOGICDEVICETYPE  [Logictype] [Devicetype]

This command will assign a device type to the matching logic type.  For example, .LOGICDEVICETYPE CAP CAPICATOR.

.FIDUCIALATTR

.SMDATTR

.NON_ELECTRICAL_PINS [OPTION]

Pins which have no copper on any layer are optionally ignored, made into fiducials, or kept normal.

.UNNAMEDNET [STRING]

Definition: When nets are encountered with the [STRING] as a prefix, the net will be renamed to "$$__REFDES.PIN" of some component pin on the net.

If the pin is unconnected, the net name will be as follows:

"NC__REFDES.PIN"


rpads_Understandingthepads.LOGfile

  Read Module : PADS File

Understanding the PADS.LOG file


rpads_DatabaseClassifications

  Read Module : PADS File

Database Classifications

Section 1 PADS PCB-2000 and PADS Perform

RSI Call Out: PAD6

Database Class: PIN

____________________________________________________________________

Section 2 PADS Power PCB

RSI Call Out: PPWR

Database Class: Net based (different than PADS PERFORM)


raccel_theImportFile

  Read Module : Accel File

Module Name: Accel EDA (.pcb) Layout Read

The Import File

The first step in using CAMCAD to view Accel .pcb files is to generate the CAD files used for import.  Whenever possible, verify that you are saving the maximum amount of data in generating the .pcb file.

Systems Supported: Accel EDA and Tango PRO

Version: 12, 13

Hardware Platform:  PC

Operating Systems: DOS

File Used for Import: .PCB (ASCII)

How to Produce File: Load CAD data into Accel.  Then, perform a standard file save in ASCII format.

In order to assure net assigns as copper, run:

utils|Reconnect Nets

from the Menu Bar before saving the file.

Tango Pro PCB Lite limitations are not conformed to. Only the limitations, as known, of Accel EDA and Tango Pro full versions are adhered to.


raccel_ImportingintoCAMCAD

  Read Module : Accel File

Importing into CAMCAD

The required module is Accel EDA (.pcb) Layout read.  There are no special considerations in importing .pcb files.  For general file import information, refer to the CAMCAD Help Reference page Working With Files.

From the CAMCAD menu commands, choose

File | Import | Accel EDA (.pcb) Layout Read

Next, browse to the proper location and select the file. After the file is read in, a .log file will be produced to record import information.  Click the button "Place at Origin and Fit Page to Image" to place the file into the CAMCAD project window.


raccel_ItemsControlledbyAccel.IN

  Read Module : Accel File

Items Controlled by ACCEL.IN

The Accel EDA input is configured using an import setup file called ACCEL.IN in the CAMCAD directory. This file uses several commands to setup certain information for importing the database correctly. The information in the setup file includes, but is not limited to, the following list of commands, their function and usage.

ACCEL.IN - Import setup for Accel EDA/Tango Pro reader. All lines must start with a ";" for a comment line and a "." for a command.

.BOARDOUTLINE	 "BOARD"

This command is used to define the layer from which to extract the board outline of the PCB.

.COMPOUTLINE   "TOP SILK"

This command is used to define the layer from which CAMCAD should extract the component outline to be used when extruding or translating the component.

Note: Multiple layers may be defined as the "component outline".  For example:

.COMPONENTOUTLINE    "TOP SILK"

.COMPONENTOUTLINE    "BOT SILK"

.HEIGHTATTR     ComponentHeight

This command is used to define the height of a component. Any attribute can be assigned. This is a crucial information for the Intermediate 3D-Layout Writer (*.ccs). All heights from Accel EDA are assumed to be in Accel units.


raccel_UnderstandingtheACCEL.LOGfile

  Read Module : Accel File

Understanding the ACCEL.LOG file

The Accel.LOG file will record specifics about the file import.  If an item, entity, attribute, or layer is influenced by a setting in the Accel.IN file, it is recorded in the .LOG file.  To better understand any Accel.LOG file entries, find and understand the relevant section in the .IN file.

There are no extra considerations for the Accel.LOG file.


raccel_DatabaseClassification

  Read Module : Accel File

Database Classifications

Database Class: Net

Board Outline Class: Pseudo

Component Class: Local Component


rpcad_theImportFile

  Read Module : PCAD File

Module Name: PCAD PDIF Layout Read

The Import File

The first step in using CAMCAD to view PCAD files is to generate the CAD file used for import.  Whenever possible, verify that you are saving the maximum amount of data in generating the file.

Systems Supported: PCAD

Version: 2-8

Hardware Platform: PC

Operating Systems: DOS

Files Used for Import: .PDF (ASCII)

How to Produce files: Select PDIF OUT in the PCAD user interface.  Alternatively, at the DOS command line run: PDIFOUT -l file .pcb


rpcad_ImportingintoCAMCAD

  Read Module : PCAD File

Importing into CAMCAD


rpcad_ItemsControlledbyPCAD.IN

  Read Module : PCAD File

Items Controlled by PCAD.IN

The PCAD PCB input is configured using an import setup file called PDIF.IN in the CAMCAD directory. This file uses several commands to setup certain information for importing the database correctly for proper 3D-Layout Extraction. The information in the setup file includes, but is not limited to, the following list of commands, their function and usage.

PDIF.IN - Import setup for PCAD PCB reader. All lines must start with a ";" for a comment line and a "." for a command line.

.BOARDOUTLINE	"BRDOUT"

This command is used to define the PCAD layer from which to extract the board outline of the PCB. This is a crucial information for the Intermediate 3D-Layout Writer (*.ccs).

.COMPOUTLINE      "SLKTOP"

This command is used to define the PCAD layer from which CAMCAD should extract the component outline to be used when extruding the component. This is a crucial information for the Intermediate 3D-Layout Writer (*.ccs).


rpcad_UnderstandingthePCAD.LOGfile

  Read Module : PCAD File

Understanding the PCAD.LOG file


rpcad_DatabaseClassifications

  Read Module : PCAD File

Database Classifications

Database Class:

Board outline Class: PSEUDO

Component Class: Library


rveribest_GeneralDescription

  Read Module : VeriBest EIF File

General Description

Import Specifications

System: Veribest EIF Files

Hardware Platform(s): Sun

Version(s): 1.0, VB14

Operating Systems(s): UNIX

Input File Format:

EIF Files Intergraph/Veribest supports EIF output for the following products:

     Daisy Boardmaster 4.5 +

     AT Designer 12.4

     Cadnetix any Version F

     PCB Engineer has to be upgraded to AT Designer


rveribest_CreatingtheImportFile

  Read Module : VeriBest EIF File

Creating the Import File

Veribest EIF import procedure.

First create an empty design directory.

     C:\>md design1

     C:\>cd design1

Copy the created EIF files into this empty design directory.

     C:\design1>copy rsi\xxxeif\filename.*

     C:\design1>copy rsi\xxxeif\eifo_cor.txt

Copy all files from the veribest\vbpcb\libelect\pcbseed directory into the design directory.

     C:\design1>copy veribest\vbpcb\libelect\pcbseed\*.*

21 files should be copied over.

Run Veribest PCB from the Windows "Start" menu.

     Start | Programs | Veribest PCB | Veribest PCB

When the "Open a Design File" file selection dialog box opens, navigate to your design directory and select the file "design.vdb" and click on the "OPEN" button.

Veribest PCB and MicroStation will open and load the design.vbd file.

Now the EIF load may be performed. This is found under:

     File | Import | EIF

When the "EIF import" dialog opens select all option boxes (do not modify Radio Button selections) then click the "OK" button.

This will load the EIF files located in the directory from which the design.vbd was loaded.

A timed dialog box should appear followed by a message "EIF imported successfully". Click "OK".

At this point the padstacks must be processed. From the menu bar select:

     Route | Pads Processor

When dialog box appears click "OK".

The EIF load procedure is now complete. The file may now be saved out under its proper name.

     File | Save As

If a File | Save is performed the design will be saved out as design.vbd in your design directory.


rveribest_ImportingintoCAMCAD

  Read Module : VeriBest EIF File

Importing into CAMCAD

 After the series of files are created with the VB2RSI.exe program, the files are ready for import into CAMCAD.  Only one file, the correlation file, needs to be imported into CAMCAD.  This file calls all of the other files in their proper order so that they are all imported correctly into CAMCAD.

Choose File | Import | Veribest, and browse to select the correlation file.

The file import process is incremental; if you need to import any extra files after the correlation file is imported (such as a netlist file) you can choose File | Import | Veribest again, and import the extra file.


rveribest_ItemsControlledbyVeribest.IN

  Read Module : VeriBest EIF File

Items Controlled by VERIBEST.IN


rveribest_UnderstandingtheVeribest.LOGfile

  Read Module : VeriBest EIF File

Understanding the VERIBEST.LOG file


rveribest_DatabaseClassifications

  Read Module : VeriBest EIF File

Database Classifications

Database Class: Net

Board outline Class: Real

Component Class: Library

Local component definition in design file under part placement is not supported. The shape is taken from the cell library definition.

PART_DEF, VIA_DEF, AND CELL_DEF - Local part definition in design file is not supported --> Violates the library concept.


rvisula_cadstar_theImportFile

  Read Module : Visula & Cadstar-NT File

Module Name: Zuken/Redac (.paf) Layout Read

The Import File

The first step in using CAMCAD to view Zuken-Redac Visula and CADSTAR for Windows files is to generate the CAD file used for import.  Whenever possible, verify that you are saving the maximum amount of data in generating the file.

Systems Supported: Zuken-Redac Visula and CADSTAR for Windows

Version: 4.0

Hardware Platform: HP, SUN, Win

Operating Systems: UNIX, Win

Files Used for Import: .PAF (ASCII)

How to Produce files: Select from the menu:

File | Neutral Database | Write


rvisula_cadstar_ImportingintoCAMCAD

  Read Module : Visula & Cadstar-NT File

Importing into CAMCAD


rvisula_cadstarItemsControlledbycct.IN

  Read Module : Visula & Cadstar-NT File

Items Controlled by Cct.IN

The CADIF input is configured using an import setup file called CADIF.IN in the CAMCAD directory. This file uses several commands to setup certain information for importing the database correctly for proper 3D-Layout Extraction. The information in the setup file includes, but is not limited to, the following list of commands, their function and usage.

CADIF.IN - Import setup for CadStar/Visula reader. All lines must start with a ";" for a comment line and a "." for a command line.

.BOARDOUTLINE	"BOARD"

This command is used to define the CadStar/Visula layer from which to extract the board outline of the PCB. This is a crucial information for the Intermediate 3D-Layout Writer (*.ccs).

.COMPOUTLINE      "L241"

This command is used to define the CadStar/Visula layer from which CAMCAD should extract the component outline to be used when extruding the component. This is a crucial information for the Intermediate 3D-Layout Writer (*.ccs).


rvisula_cadstar_UnderstandingtheCct.LOGfile

  Read Module : Visula & Cadstar-NT File

Understanding the Cct.LOG file


rvisula_cadstar_DatabaseClassifications

  Read Module : Visula & Cadstar-NT File

Database Classifications

Database Class: Net

Board Outline Class:

Component Class:


rallegro_LocalPadstackDefinitions

  Read Module : Allegro File

Local Padstack Definitions


rorcad_CreatingtheImportFile2

  Read Module : OrCAD File

Creating the Import File

Input File Format:.MIN

Command Sequence to Generate file(s):EXPORT MASSTECK ASCII

To generate the proper .MIN file, under options, "all of the above" should be selected, which is the default setting.


rorcad_ImportingintoCAMCAD2

  Read Module : OrCAD File

Importing into CAMCAD


rorcad_ItemsControlledbyORCAD.IN2

  Read Module : OrCAD File

Items Controlled by ORCAD.IN


rorcad_UnderstandingtheORCAD.LOGfile2

  Read Module : OrCAD File

Understanding the ORCAD.LOG file


rorcad_DatabaseClassifications2

  Read Module : OrCAD File

Database Classifications

Database Class: Net

Board outline Class: Pseudo

Component Class:


databaseclass_pin
Database Class: Pin

Connections must be made in a pin-to-pin manner.  "T" connections

are created by doubling back ono an existing section of a trace to give

the visual appearance of a "T" connection.  This class usually has very

stringent rules that must be followed for trace routing and via placement.


boardoutlineclass_pseudo
Board Outline Class: Pseudo

Board outlines in this CAD format are comprised of standard line elements.

The CAD format does not allow for a real board outline entity.


boardoutlineclass_real
Board Outline Class: Real

Board outlines in this CAD format are true board outline entities.  CAMCAD

supports true board outlines.


componentclass_library
Component Class: Library

Library driven CAD systems have a component library section within the CAD

data which defines all components.


componentclass_localcomponent
Component Class: Local Component

Local component CAD systems are systems where the shape of a component

can be changed locally (only for that one instance). Also called  Exploded Component Class.


databaseclass_net
Database Class: Net

Connections are allowed to be made in any order and "T" connections

are also allowed.  Although rules must be followed for trace routing and

via placement they are usually very loose, thus allowing the designer

much more freedom in the routing process.