Importing Data Files Using Genesys

Genesys can import the following file types:

• DXF File
• Excellon (Gerber) Drill List
• GDSII File
• Genesys Netlist
• Gerber File
• Load Pull Data File
• S-Data File
• SPICE File
• XML File
• 6.0 Model Library
• Old Genesys S-Data File

To import a file

1. Click File on the Genesys menu and select a file type from the Import menu.
2. Follow the instructions in the windows that appear.

CITI file Import

Overview

CITIfile is a standardized data format that is used for exchanging data between different computers and instruments. CITIfile stands for Common Instrumentation Transfer and Interchange file format.

This standard is a group effort between instrument and computer-aided design program designers. As much as possible, CITIfile meets current needs for data transfer, and it is designed to be expandable so it can meet future needs.

CITIfile defines how the data inside an ASCII package is formatted. Since it is not tied to any particular disk or transfer format, it can be used with any operating system, such as DOS or UNIX, with any disk format, such as DOS or HFS, or with any transfer mechanism, such as by disk, LAN, or GPIB.

By careful implementation of the standard, instruments and software packages using CITIfile are able to load and work with data created on another instrument or computer. It is possible, for example, for a network analyzer to directly load and display data measured on a scalar analyzer, or for a software package running on a computer to read data measured on the network analyzer.

Data Formats

There are two main types of data formats: binary and ASCII. CITIfile uses the ASCII text format. Although this format requires more space than binary format, ASCII data is a transportable, standard type of format which is supported by all operating systems. In addition, the ASCII format is accepted by most text editors. This allows files to be created, examined, and edited easily, making CITIfile easier to test and debug.

File and Operating System Formats

CITIfile is a data storage convention designed to be independent of the operating system, and therefore may be implemented by any file system. However, transfer between file systems may sometimes be necessary. You can use any software that has the ability to transfer ASCII files between systems to transfer CITIfile data.

The descriptions and examples shown here demonstrate how CITIfile may be used to store and transfer both measurement information and data. The use of a single, common format allows data to be easily moved between instruments and computers.

CITIfile Definitions

This section defines: package , header , data array , and keyword .

Package

A typical CITIfile package is divided into two parts:

• The header is made up of keywords and setup information.
• The data usually consists of one or more arrays of data.

The following example shows the basic structure of a CITIfile package:
Unable to render embedded object: File (cktsim-05-1-10.gif) not found.
When stored in a file there may be more than one CITIfile package. With the Agilent 8510 network analyzer, for example, storing a memory all will save all eight of the memories held in the instrument. This results in a single file that contains eight CITIfile packages .

Header

The header section contains information about the data that will follow. It may also include information about the setup of the instrument that measured the data. The CITIfile header shown in the first example has the minimum of information necessary; no instrument setup information was included.

Data Array

An array is numeric data that is arranged with one data element per line. A CITIfile package may contain more than one array of data. Arrays of data start after the BEGIN keyword, and the END keyword follows the last data element in an array.

A CITIfile package does not necessarily need to include data arrays. For instance, CITIfile could be used to store the current state of an instrument. In that case the keywords VAR , BEGIN , and END would not be required.

When accessing arrays via the DAC (DataAccessComponent), the simulator requires array elements to be listed completely and in order.

Example: S[1,1], S[1,2], S[2,1], S[2,2]

Keywords

Keywords are always the first word on a new line. They are always one continuous word without embedded spaces. A listing of all the keywords used in version A.01.00 of CITIfile is shown in CITIfile Keyword Reference.

To import CITI File in Genesys:

1. Open File > Import > CITI File..
   
2. Select CITI File for Import in the Open file dialog:
   
3. If the CITI file has arrays (variable, which names have indexes in square braces[]), it opens the dialog, defining output format of the array data.
   
   Select Yes to convert array data in arrays, or No- otherwise:
4. The imported file creates dataset with name = the file name in the Genesys workspace tree.
   We imported "proj.cti" CITI file, which created same named dataset:
   
5. If the workspace tree has dataset with name of the imported CITI file, then this dialog is opened to rename the output dataset:
   

For example, if CITI file has array data S[i,j]

  Saving its array data as Arrays will creates swept relative to independent variable  freq  vector PORTZ and matrix S:

otherwise the array data will be saved as scalar varaiables PORTZ_i and S_i_j:

CITIfile Examples

The following are examples of CITIfile packages.

Display Memory File

This example shows an Agilent 8510 display memory file. The file contains no frequency information. Some instruments do not keep frequency information for display memory data, so this information is not included in the CITIfile package.

Note that instrument-specific information (#NA = network analyzer information) is also stored in this file.

CITIFILE A.01.00
#NA VERSION HP8510B.05.00
NAME MEMORY
#NA REGISTER 1
VAR FREQ MAG 5
DATA S RI
BEGIN
-1.31189E-3,-1.47980E-3
-3.67867E-3,-0.67782E-3
-3.43990E-3,0.58746E-3
-2.70664E-4,-9.76175E-4
0.65892E-4,-9.61571E-4
END

Agilent 8510 Data File

This example shows an 8510 data file, a package created from the data register of an Agilent 8510 network analyzer. In this case, 10 points of real and imaginary data was stored, and frequency information was recorded in a segment list table.

CITIFILE A.01.00
#NA VERSION 8510B.05.00
NAME DATA
#NA REGISTER 1
VAR FREQ MAG 10
DATA S[1,1] RI
SEG_LIST_BEGIN
SEG 1000000000 4000000000 10
SEG_LIST_END
BEGIN
0.86303E-1,-8.98651E-1
8.97491E-1,3.06915E-1
-4.96887E-1,7.87323E-1
-5.65338E-1,-7.05291E-1
8.94287E-1,-4.25537E-1
1.77551E-1,8.96606E-1
-9.35028E-1,-1.10504E-1
3.69079E-1,-9.13787E-1
7.80120E-1,5.37841E-1
-7.78350E-1,5.72082E-1
END

Agilent 8510 3-Term Frequency List Cal Set File

This example shows an 8510 3-term frequency list cal set file. It shows how CITIfile may be used to store instrument setup information. In the case of an 8510 cal set, a limited instrument state is needed to return the instrument to the same state that it was in when the calibration was done.

Three arrays of error correction data are defined by using three DATA statements. Some instruments require these arrays be in the proper order, from E[1] to E[3] . In general, CITIfile implementations should strive to handle data arrays that are arranged in any order.

CITIFILE A.01.00
#NA VERSION 8510B.05.00
NAME CAL_SET
#NA REGISTER 1
VAR FREQ MAG 4
DATA E[1] RI
DATA E[2] RI
DATA E[3] RI
#NA SWEEP_TIME 9.999987E-2
#NA POWER1 1.0E1
#NA POWER2 1.0E1
#NA PARAMS 2
#NA CAL_TYPE 3
#NA POWER_SLOPE 0.0E0
#NA SLOPE_MODE 0
#NA TRIM_SWEEP 0
#NA SWEEP_MODE 4
#NA LOWPASS_FLAG -1
#NA FREQ_INFO 1
#NA SPAN 1000000000 3000000000 4
#NA DUPLICATES 0
#NA ARB_SEG 1000000000 1000000000 1
#NA ARB_SEG 2000000000 3000000000 3
VAR_LIST_BEGIN
1000000000
2000000000
2500000000
3000000000
VAR_LIST_END
BEGIN
1.12134E-3,1.73103E-3
4.23145E-3,-5.36775E-3
-0.56815E-3,5.32650E-3
-1.85942E-3,-4.07981E-3
END
BEGIN
2.03895E-2,-0.82674E-2
-4.21371E-2,-0.24871E-2
0.21038E-2,-3.06778E-2
1.20315E-2,5.99861E-2
END
BEGIN
4.45404E-1,4.31518E-1
8.34777E-1,-1.33056E-1
-7.09137E-1,5.58410E-1
4.84252E-1,-8.07098E-1
END

When an instrument's frequency list mode is used, as it was in this example, a list of frequencies is stored in the file after the VAR_LIST_BEGIN statement. The unsorted frequency list segments used by this instrument to create the VAR_LIST_BEGIN data are defined in the #NA ARB_SEG statements.

2-Port S-Parameter Data File

This example shows how a CITIfile can store 2-port S-parameter data. The independent variable name FREQ has two values located in the VAR_LIST_BEGIN section. The four DATA name definitions indicate there are four data arrays in the CITIfile package located in the BEGIN...END sections. The data must be in the correct order to ensure values are assigned to the intended ports. The order in this example results in data assigned to the ports as shown in the table that follows:

CITIFILE A.01.00
NAME BAF1
VAR FREQ MAG 2
DATA S[1,1] MAGANGLE
DATA S[1,2] MAGANGLE
DATA S[2,1] MAGANGLE
DATA S[2,2] MAGANGLE
VAR_LIST_BEGIN
1E9
2E9
VAR_LIST_END
BEGIN
0.1, 2
0.2, 3
END
BEGIN
0.3, 4
0.4, 5
END
BEGIN
0.5, 6
0.6, 7
END
BEGIN
0.7, 8
0.8, 9
END

CITIfile Keyword Reference

The following table lists keywords, definitions, and examples.

CITIfile Keywords and Definitions

CITIfile Guidelines

The following general guidelines aid in making CITIfiles universally transportable:

Line Length. The length of a line within a CITIfile package should not exceed 80 characters. This allows instruments which may have limited RAM to define a reasonable input buffer length.

Keywords. Keywords are always at the beginning of a new line. The end of a line is as defined by the file system or transfer mechanism being used.

Unrecognized Keywords. When reading a CITIfile, unrecognized keywords should be ignored. There are two reasons for this:

• Ignoring unknown keywords allows new keywords to be added, without affecting an older program or instrument that might not use the new keywords. The older instrument or program can still use the rest of the data in the CITIfile as it did before. Ignoring unknown keywords allows "backwards compatibility" to be maintained.
• Keywords intended for other instruments or devices can be added to the same file without affecting the reading of the data.

Adding New Devices. Individual users are allowed to create their own device keywords through the # (user-defined device) mechanism. (Refer to the table immediately above for more information.) Individual users should not add keywords to CITIfiles without using the # notation, as this could make their files incompatible with current or future CITIfile implementations.

File Names. Some instruments or programs identify a particular type of file by characters that are added before or after the file name. Creating a file with a particular prefix or ending is not a problem. However in general an instrument or program should not require any such characters when reading a file. This allows any file, no matter what the filename, to be read into the instrument or computer. Requiring special filename prefixes and endings makes the exchange of data between different instruments and computers much more difficult.

A CITIfile package is as described in the main CITIfile documentation: the CITIFILE keyword, followed by a header section, usually followed by one or more arrays of data.

Note There are some specific problems with the current version in reading and/or writing this data format. On the Agilent EEsof web site, refer to the Release Notes in Product Documentation, and to Technical Support for more information and workarounds (http://www.agilent.com/find/eesof).

Exporting Files Using Genesys

Genesys can export the following file types:

• ASCII Drill List
• Export Schematics to ADS
• Bill of Materials
• Bitmap (Active Window)
• Bitmap (Entire Screen)
• DXF File
• Excellon (Gerber) Drill List
• GDSII File
• Gerber File
• HPGL File
• IFF Schematic File
• Part Placement List
• S-Parameters
• SPICE File
• Touchstone File
• XML File

To export a file

1. Open the workspace tree object to make the it the active window or click the window of the object to be exported if it hasn't been selected.
2. Click File on the Genesys menu and select a file type from the Export menu.
3. Follow the instructions in the windows that appear.

Additional Export Information

S-Parameters are exported in the Touchstone format.

Touchstone circuit files are similar to Genesys netlists and are generally a one-to-one translation.

Layout Designs

There are several tools available to you to help with the export/conversion of Layout Designs.

AutoCAD DXF/DWG Translator

The DXF/DWG translator enables you to convert Genesys designs into AutoCAD's DXF/DWG file format, as well as convert DXF/DWG files into Genesys designs. DXF is a very simple file format that can be read by most CAD programs that support DXF. The DXF/DWG translator is bidirectional and provides support for hierarchical and all layer separation.

DWG is a binary format, therefore the files take less time to load and save. Genesys supports importing and exporting to/from AutoCAD. AutoCAD versions 12 to 2007 are supported for import. AutoCad versions 2000, 2004 and 2007 are supported for export. Carefully consider how you want to use DXF/DWG output - including layer numbering, use of holes, and polygon shapes - before beginning your layout Layout. Setting up the proper layout rules in Genesys can save a lot of time in generating acceptable DXF/DWG output. For specific considerations or limitations, consult your AutoCAD documentation.

Note: Password protected DWG files are not supported.

Genesys includes an editor that can display the DXF/DWG Layout. Using the editor, you can compare the DXF/DWG files to the original Genesys layout Layout to verify that the Layout was exported correctly. Similarly, DXF/DWG files can be previewed prior to import into Genesys:

• to edit a large Layout down to a smaller Layout prior to importing it into Genesys. This edited Layout can be saved and then imported in Genesys.
• or after import, to verify that the DXF/DWG Layout data and the Genesys-imported Layout appear similar.

For details, see Using the Pre-Production Editor.

Importing DXF/DWG Files to Genesys

The Import DXF/DWG Options dialog enables you to specify units, and layers to control the import of DXF/DWG format files. A DXF/DWG file must be selected in the main export dialog for the Import DXF/DWG Options dialog to open.

To import AutoCAD DXF/DWG files:

1. In the layout window containing your design, choose File > Import > DXF File...
   
2. Enter path to imported DXF(DWG) file in the opened "Import DXF" dialog window manually, from Open File dialog, pushing "Browse" button:
   
3. If the path point to existing file, it enables "Preview" button, pushing on which opens the importing file in Preproduction Editor
   
4. Push button OK to continue DXF/DWG import. It Opens Import DXF Options dialog, Layers tab.The Layers tab displays a list all the layers in DXF/DWG file. Layers can be selectively imported to Genesys using the import column. By default all layers are imported. Map importing file layers to Genesys layers, choosing them from Layout Layer combo boxes, or to viahole layers, checking Via?  checboxes, and choosing metal layers from Via From and Via To combos:
   
5. Set layout arc and linear items resolutions, or use default:
   
6. Push OK button to import the AutoCAD file.

Exporting an Genesys Design to DXF/DWG Files

The Export DXF/DWG Options dialog box enables you to set file format, Autocad version, path geometry, and hole format.
To export AutoCAD DXF/DWG files:

1. In the layout window containing your design, choose File > Export > DXF File...
   
2. It opens Export DXF Options dialog. Select exported layers in the Layers tab (default - all layers are selected)
   
3. Select exporting DXF Options: output File Format DXF(Text) or DWG(Binary), AutoCAD version, format of Holes, and format pf  Paths.
   
4. At the Layout Options tab define exporting  Layout objects (components, EM-ports, drill holes). To convert all layout objects to resolved polygons (excepting layers with text), set checkbox Convert all shapes into resolved polygons.
   
5. Close the dialog by OK button opens Export DXF (or Export DWG) file opening dialog. Enter full path to output file manually, or using Browse button. Select box View File after export to view output file after export.
   
6. Push OK button. After export it opens Preproduction editor, displaying results of the export:
   
   Genesys Error/Messages window displays results of the export:
   

Export Layout Options

We can show up Layout options settings, defining exporting  Layout objects (components, EM-ports, drill holes). # Converting to resolved polygons (Export ports = Yes):

1. All layout objects are converted to polygons, which are resolved to polygon unions for all layers, not having text objects.
   
2. Exporting without converting to "resolved polygons" (Export ports = Yes):
   All layout objects are mapped to output "as is", without converting to polygons.
   
3. Converting to resolved polygons (Exports ports = No):
   All layout objects are converted to polygons, which are resolved to polygon unions for all layers, not having text objects. No EM ports are exported.
   

Options

Note Some systems may not be able to tolerate complex polygons with cutlines. For these systems, select Holes as polygons. This option is deselected as the default.

Gerber Translator

The Gerber Artwork Translator can translate artwork directly from circuit layouts created with Genesys Layout editor into Gerber format. It exports Genesys layouts into ASCII files that control Gerber photoplotting equipment.

Genesys includes an editor that can display the Gerber/Drill design. Using the editor, you can compare the Gerber/Drill files to the original Genesys layout design to verify that the design was exported correctly.

For details, see Using the Pre-Production Editor.

Gerber Command Format

The Gerber format is a numerical control language developed to generate photo artwork. The output of this translator is an ASCII file that contains the following Gerber commands:

G01 = linear interpolation
G54 = aperture select
D01 = shutter open
D02 = shutter close
D03 = flash
M02 = end of program
X and Y = coordinates
* = end of block

Coordinates are absolute, with implied decimal point and optional leading zero suppression. However, the literal string values may be modified in the message file. For example, G01 may be changed to AB. A sample listing of the Gerber file commands, with interpretation to the right, might look like this:

This example would produce the following figure.

The output file (Gerber command file) is the Gerber Drawing File (.gbr).

Exporting Gerber Files

Genesys Gerber export tool can generate Gerber files in RS274X and MDA format for raster photo plotters.

The Gerber export tool creates one output file for each different layer used in the layout design. For example, if the design contains two layers, TOP METAL and TOP SILK, two Gerber files will be generated:

• TOP_METAL.gbr
• TOP_SILK.gbr

All exported viaholes with identical metal layers are exported in 2 files: Gerber layer .gbr, and drill file .drl. For example, if the design has viaholes between TOP METAL layer and BOTTOM COVER, and between TOP COVER and TOP METAL layer, export of  the viaholes creates 4 files:

• TOP_METAL_BOT_COVER.gbr
• TOP_METAL_BOT_COVER.drl
• TOP_COVER_TOP_METAL.gbr
• TOP_COVER_TOP_METAL.drl

To export Gerber files:

1. In the layout window containing your design, choose File > Export > Gerber File...
   
2. The Export dialog box appears. Select export layers, and their polarity (default is positive)
   
3. Set Gerber export options at the tab "Gerber Options" that apply.
   For available options, see Gerber File Options.
   
4. In Genesys 2008.07, drill file export is accomplished simultaneously as part of the Gerber export. The procedure for generating the drill file is similar to generating the Gerber file.To create Gerber drill file, select exporting drill layers. You may edit actual drill tool diameter for each drill hole.
   Note. All drill holes from the same the viahole layer are selected together.
   Drill files are configured from the Drill tab in the Export Gerber Options dialog.Select the check box to designate the layer for which you want to generate the drill file. When a layer is selected, all the tools on that layer are automatically selected. By default, no drill file will be generated during Gerber export.
   The drill file options Number format, Output unit, and Zero suppression are same as options set for Gerber export in Options tab of Export Gerber Options dialog. However, note that the zero suppression in Drill is actually a zero inclusion.
   Tool Dia. (Diameter) is an editable field. By default the Tool Diameter value equals the Drawing Diameter value.
   
5. The exporting layout objects and output objects format may be specified at the "Layout options" tab. It may include component footprints, EM-ports, and drill holes.
   All Genesys layout objects may be converted to "resolved" polygons by selecting "Convert all shapes into resolved polygons". In this mode you may specify layout geometry resolution parameters for arcs and linear layout object items.
   
6. Click OK to save your settings or Cancel to retain the default settings.
   It closes "Export GBR Options" dialog and opens "Export GBR" dialog, setting output Gerber file(s) location.
   
   As a default all output Gerber files will be exported in a single folder - one file per layer(.gbr) and per drill layer(.drl).
   If it's exported to a single file - all Layout layers and drill holes will be saved in one output Gerber file.
7. Click OK to export the Genesys layout design to a Gerber file, or click Options to update export options.
   A Status window appears detailing the export information.
   
8. If checkbox "View File after Export" is set, after the export it opens "Preproduction editor":
    

Importing Gerber Files

1. In the layout window where you woud like to import Gerber design, choose File > Import > Gerber File...
   
2. In the opened "Import GBR" dialog window select import File or Folder. Folder is default for Gerber Import:
   
3. Enter the imported  File or Folder path, or push button "Browse" to open File or Folder entering dialog:
   
4. After entering correct File (or Folder) path, it may be previewed by pushing button "Preview",
   
   opening Preproduction Editor
   
5. Push button OK of the Import GBR dialog. It opens "Import GBR Options" dialog.
   Map imported Gerber files layers to Genesys Layout window layers, selecting it from pull down combo boxes:
    
   and to Genesys Layout viaholes layers, selecting checkbox "Via?", and selecting the viahole metal layers form pull down Genesys metal layers (including metal covers) combo boxes:
   
6. Set Gerber import options, or use default from imported Gerber/Drill files:
   
7. Set layout resolution options at "Layout Options" tab for importing arcs and linear layout object items:
   
8. Push OK button for importing, or Cancel to cancel the operation.

Gerber File Options

File format

• Select RS274X for an enhanced version of Gerber RS274D format that supports embedded apertures and G36/G37 polygons.
• Select MDA if your photoplot shop uses a FIRE 9000 plotter. It embeds apertures and supports POEX/POIN polygons for fill on the fly.

Hole format

In Genesys, when a hole is created in a geometrical figure (like polygon), a cutline is introduced. This is a false edge connecting the outer boundary of the polygon with the inner boundary. This polygon is actually a single re-entrant polygon. When you select Holes as cutlines this re-entrant polygon is translated to Gerber as-is. The default is Holes as cutlines.

Holes as Cutlines

Select Holes as polygons or Preserve holes to remove the false edge from the polygon.

Holes as polygons

When Holes as polygons is selected, holes are exported as filled elements. Therefore the polygon will appear to have no holes.

Preserve holes

When Preserve holes is selected, the resultant polygon in Gerber contains a dark area and empty area. This option is not available for exporting Gerber files in RS274X format.

Unit

Available units are inch or mm. Inch is the default.

Number format

The number of integers placed before and after the decimal point. If chosen incorrectly, Gerber data resolution can be poor. The default is 2.4. If the unit is set to mm then you can set the number format to 3.3.

A warning message is displayed in the Status window to notify the user that to preserve the precision in the Gerber data, number format has to be selected carefully. If the Gerber data is not generated correctly for the selected number format then a suitable error message is displayed in the Status window.

Zero suppression

Available settings are Leading and None. Select Leading (the default) to remove all leading zeros in the coordinate data, making the Gerber file smaller.

Line width for polylines

Polylines in Genesys have zero width, but you can use this option to provide a width to be used for drawing this polyline in the Gerber file.

If the polylines and arcs (both zero width entities) are not required to be exported, then set the width to zero.

Generate single file

When this check box is selected, a single file is generated for all the selected layers in the Layer tab. Specify the file name with extension .gbr. This file will be created in the destination directory selected in the Export dialog box.

Gerber Layer Options

All the layers used in the design are displayed in a table in the Layers tab of the Export Gerber Options dialog. By default, all the layers will be displayed with positive polarity and all layers will be exported. You can avoid exporting a specific layer by de-selecting the check box in the Export column for that layer.

Limitations and Considerations

• No intermediate mask file is generated.
• The new Gerber export tool is targeted for the raster photoplotters to generate RS274X and MDA file format.
• No aperture filling is supported for polygons.
• No separate aperture file is required for RS274X and MDA files.
• You must set the appropriate number format in the Export Gerber Options dialog so that the precision in Gerber data is more than the precision in layout design.
• The Gerber translator can generate a single Gerber file for all layers. However, the Gerber Viewer cannot process a Gerber file in which multiple layers are defined in a single file.
  It imports only the first layer defined in the file.
• Exporting MDA files using "Generate single file" option will export all the figures in the same layer. It is advisable not to use "Generate single file" option for MDA format. 
• If a layer does not have any via (circles) then it will not be displayed in the Drill table and no drill file will be generated for that layer.
• One drill file will be generated for each layer.
• Drill files will be created in the Destination directory selected in the Export dialog.
• Drill file name is the same as layer name with extension .drl. For example, drill file for the layer cond will be cond.drl.
• If Tool Diameter is set to 0.0, the Tool Diameter will be equal to the Drawing Diameter in the output drill file.

Using the Pre-Production Editor

Genesys includes an editor that can display DXF/DWG and Gerber/Drill designs. Using the editor, you can compare the DXF/DWG and Gerber/Drill files to the original Genesys layout design to verify that the design was exported correctly. Similarly, DXF/DWG and Gerber/Drill files can be previewed prior to import into Genesys:

• to edit a large design down to a smaller design prior to importing it into Genesys. This edited design can be saved and then imported in Genesys.
• or after import, to verify that the DXF/DWG and Gerber/Drill design data and the Genesys-imported design appear similar.

File Menu

The File menu contains common Open, Save, Save As, and Close functions and lists the four most recent files viewed in the editor.

Note When files are saved as Gerber/Drill files using the Pre-Production editor, the layer name is used as the file name.

Edit Menu

The Edit menu contains common and specialized editing commands.

Note Union, Intersection, Union Minus Intersection, Crop, and Chop do not work for open ended figures with zero width (for example arc and polylines).

View Menu

The view menu contains commands that allow you to alter the view of the current design.

View All	Your design is scaled and repositioned to fit within the viewing area.
The Zoom Commands	The Zoom commands enable you to enlarge or shrink the area being viewed. You can zoom in and zoom out using mouse wheel. The enlarged or condensed figure is moved towards the center of the window. Zoom To Area > click a point and then with the mouse button pressed move the mouse to the bottom right of the area and release the mouse button to define a new view. Zoom to Point to zoom in on a specified point in the window. Click to specify a point and the current view is magnified by a factor of two, moving the point you specify to the center of the window. Zoom In By 2 to zoom in by a factor of 2. Zoom Out By 2 to zoom out by a factor of 2.
Measure	The Measure dialog allows you to measure lengths. Absolute X, Y displays the absolute coordinates of the point of mouse click. Delta X, Y gives the relative X and Y coordinates from previous mouse click. Angle gives the angle with respect to a line horizontal to the X axis. Cumulative distance gives the total length from starting point to current point. Click Clear to reset the values for Absolute X,Y, Delta X, Y, Angle and Cumulative distance. Click Cancel to dismiss the measure dialog box.
Undo/Redo Stack	Unable to render embedded object: File (editor4.gif) not found. Shows last performed actions. You have an option to undo or redo the last operations performed.
Layer Table	The layer Table displays the layer information. It enables you to switch on/off layers from display. It also enables you to view layer number, layer name and layer color. Click Select All to view all the layers and Deselect All to switch off all the layers. All the layers are displayed by default.
Status	The status window displays messages about the status of the current design, as well as warning and error messages.

Window Menu

This menu contains the following common Window commands:

Viewing Files in the Pre-Production Editor During Export

To view a DXF/DWG or Gerber/Drill file during export from Genesys:

1. Select DXF/DWG or Gerber/Drill from File type drop-down list in Export dialog.
2. Select the View file after export checkbox and click OK.
   This will display the exported DXF/DWG or Gerber/Drill file. A status window shows if the export is complete or failed and the design is displayed in the Pre-Production Editor.

Viewing Files in the Pre-Production Editor During Import

To view a DXF/DWG or Gerber/Drill file during import to Genesys:

1. Select DXF/DWG or Gerber/Drill from File type drop-down list in Import dialog.
2. Click Preview to view the file in the Pre-Production Editor.

Editing Files in the Pre-Production Editor

Using the Pre-Production Editor you can cut, copy, paste and modify designs. From the Modify menu, you can perform editing functions like union, intersection, union minus intersection, crop, and chop.

To edit using the Pre-Production Editor:

1. Open a design in the Pre-Production Editor as described above.
2. Click Edit > Edit Enable.
   • To cut a figure, select the figure and then click Edit > Cut.
   • To copy a figure, select the figure and then click Edit > Copy.
3. To crop or chop a figure:
   • Select the figure.
     
   • Click Crop or Chop.
   • Mark the area to crop/chop using mouse.
     
   • Release the mouse to crop/chop the selected area.
     
4. Click Delete to delete selected item.
5. Click Undo to revoke last Edit command.

Using Files From Earlier Genesys Versions

Genesys lets you load files created using all versions of Genesys prior to the current version. Once you save the files using the current version of Genesys, the files will not load in versions prior to GENESYS2005 (forward compatibility, and not backward compatibility).

GENESYS2005 and beyond are backward compatible as long as you disable Compact Data Format (Tools / Options).

Old Support:

Genesys imports files created using SUPERSTAR version 4 or later and any version of Genesys. You cannot import the following features from versions of SUPERSTAR created prior to version 4:

• Post Processing - Genesys now has better post processing capability that is not compatible with the old technique. For information on the new post processing procedures, see the Simulation manual and the Using Equations chapter of the User's Guide . Also, see the Genesys example file Model Extract.wsx.
• 3D Graphs - Parameter sweeps are now different, so you must recreate 3D graphs after importing them.
• EMPOWER Simulation Data - EMPOWER calculated data is now stored inside the workspace file, instead of separate files. You must recalculate the data after importing. Also, you might want to set up any decomposition examples again, because Genesys version 7 and later provides better ways to set up these files. For more information, see the EMPOWER manual.
• Multiple Impedances - Files with multiple WINDOW blocks reusing the same network to simulate different terminations use only the first set of terminations. Impedances are now stored in the ports and are tunable. If you still need multiple impedances:
  1. Load your schematic.
  2. Create other schematics using NET blocks so your schematic can use the terminations you want.

• Microstrip Radial Stubs (MRS) - There is a new radial stub model with only one port that was introduced in Genesys version 7. Replace any radial stubs with a microstrip tee and the new stub. For more information, see the Element Catalog .

Using the ADS Link

Genesys provides a link to Advanced Design System (ADS). You can export schematics from Genesys directly to an open ADS session by selecting File > Export > Export Schematics to ADS. Genesys displays a dialog box showing all instances of ADS with open projects.

You first select the instance that you want (if there is more than one running), then you select which design/s to export to ADS. When you click OK, the selected schematics are transferred to ADS. See ADS RF Architect and Synthesis documentation (in the Transfer/IO section of the ADS documentation) for more information on using the link in ADS.

The link transfers schematics only from Genesys to ADS. It does not transfer schematics from ADS to Genesys. Only schematics and linear simulations will be transferred. Layouts, plots and datasets are not transferred. Not all schematics will transfer exactly, see ADS documentation for substrate/model mapping information.

Installation Requirements

• An installed version of Genesys 2006.10 or newer
• An installed Windows version of ADS 2006A or newer

Licensing

• If Genesys was purchased as an ADS add-on, choose ADS style licensing in Genesys.
• On multi-CPU systems which use network licenses, it is important to always:
  1. Stop the ADS simulator before launching Genesys.
  2. Exit Genesys before starting a simulation in ADS.

Accessing ADS Documentation

Documentation is available on the web at:
http://edocs.soco.agilent.com/display/doc/Home,
or can be accessed by clicking a help button in ADS.