MaxRoute Translator
The MaxRoute Translator is an application that allows to convert layout project (database) to a form that is acceptable to
MaxRoute Autorouter and MaxRoute Autoplacer. It outputs all the information necessary to reconstruct the system layout project (database) in
MASSTECK. This module may also be used to import routed traces from MaxRoute Autorouter as well as results of MaxEDS Autoplacer.
Starting Maxroute Translator
From the Layout Editor, select the menu
Auto | Autoroute | Maxroute.
The Maxroute Translator window is as shown below.
- Translate EDWinXP Project to Maxroute ASCII File
This option allows to translate the currently loaded project (database) to
MASSTECK ASCII file (files with .MIN extension) that are acceptable to
MaxRoute Autorouter and MaxRoute Autoplacer. This file includes pad code assignments, packages, copper areas and layout texts which will be treated as keep-out areas.
Operation
Enable this option from the MaxRoute Translator window. Use the to select the path for the
MaxRoute ASCII file. Select the path and directory of the file. By default, the name of the project (database) is displayed. Click
Execute to execute and implement the translation.
- Import Results from MaxRoute Autorouter
This option allows to import the results of MaxRoute Autorouter back to the system. All traces in the current project (database) will be replaced by imported results (routed traces) from MaxRoute Autorouter which are stored as
MASSTECK ASCII files with the .MIN extension. The file to be imported should correspond with the currently loaded project (database).
Operation
Enable this option from the MaxRoute Translator window. Use the to select the path for the MaxRoute ASCII file (*.min) from which results are to be imported. Select the path and directory for the file. By default, the name of the project (database) is displayed. Click EXECUTE to execute and implement the operation.
Note: If the components have been relocated manually or automatically (using MaxEDS placer) in MASSTECK, the placer results are reflected in the project. Partially routed and unrouted traces are not recognized by the system.
- Import Results from MaxRoute Autoplacer
This option allows to import the results of MaxRoute Autoplacer back to the system. All components in the current project (database) will be relocated according to imported results from
MaxEDS placer and stored as MASSTECK ASCII files with
.MIN extension. The file to be imported should correspond with the currently loaded project (database).
Operation
Enable this option from MaxRoute Translator window. . Use the to select the path for the MaxRoute ASCII file (*.min) from which results are to be imported. Select the path and direcotry for the file. By default, the name of the project (database) is displayed. Click Execute to Execute and implement the operation.
SetUp Option
This menu allows to set the various options for translating project (database) to
MaxRoute ASCII file based on which routing is carried out by the
MaxRoute Autorouter.
Click the to invoke the Setup menu is as follows:
On clicking this option, Trace Widths, Vias & Grids dialog box pops up in which the width of power and signal traces as well as various other prerouting options may be defined.
Layers
Opens the Routing Layers dialog box that allows setting different layers for routing. The minimal clearances from track to pad, track to track, pad to pad, via to via, via to pad, track to via may also be specified.
On selecting this option, Routing Layers dialog box pops up in which the various layers may be set for routing. By default,
COMPONENT LAYER and SOLDER LAYER are enabled.
Layer Map
Opens the conversion setup dialog box that allows to map each layer of the system database to a layer of
MASSTECK.
On selecting this option, a Conversion Setup dialog box pops up.
The default mapping setup is displayed which may then be changed if required. The system allows 32 layers while
MASSTECK allows only 30. By default, the first 15 layers are mapped to the first 15 layers in
MASSTECK and the last 15 layers to the last 15 layers in MASSTECK. This implies that the layers M & N in the system database remain unused. If these layers are to be used, they have to be mapped by first clicking on an appropriate layer in the layer list and then on the required layer in the system. The default mapping setup is also changed in the same manner.