
                          TABLE OF CONTENTS

 1.  Purpose of the FreeStyleRoute.
 2.  Requirements to the equipment.
 3.  Installation on hard disk.
 4.  Package operating.
 4.1.  Data files.
 4.2.  Starting the program.
 4.3.  Management.
 4.3.1.  Main menu.
 4.3.2.  Script.
 5.  How to organize operation process to provide effective routing.
 5.1.  Preparing input data.
 5.2.  Definition of the design style.
 5.2.1.  Strategy import.
 5.2.2.  Layers assignment.
 5.2.3.  Contact pads description.
 5.2.4.    Bars description.
 5.2.5.    Specific pads types.
 5.2.6.  Description of the circuits routing rules.
 5.2.7.  Description of the components installation rules.
 5.3.  SpeedWay. Fast routing.
 5.3.1.  Improvement of routing quality.
 5.3.2.  Choosing the best variant.
 5.4.  FreeStyle. Layout correction.
 5.5.  Organization of interaction with external procedures.
 5.6.  Saving results.
 5.7.  Correcting automatic design results.
 6.  Tecnical characteristics and restrictions.
 7.  Information about the developers.


                      FreeStyleRoute 1.6 for DOS

                             User's guide

 1. Purpose.

     The program package  FreeStyleRoute (hereinafter named FSR) is
 a combination  of the high-performance  grid-less  router of printed
 circuit boards SpeedWay and the corrector FreeStyle. Routing quality
 of  and  elements  placement  density  are comparable or superior to
 high-quality manual routing. Resultant tracks are smooth and have no
 sharp- curves.  Algorithms used allow to insert any number of tracks
 between the outputs of an element.  FSR is compatible with the ACCEL
 Technologies P-CAD EDA at PDF-files level.


 2. Requirements to the equipment:

  - IBM PC or compatible computer
  - Math coprocessor
  - Hard disk
  - No less than 2M memory available
  - Videoadapter VGA or compatible
  - Manipulator "Mouse", compatible with Microsoft Mouse
  - MS-DOS  ver.  3.30  or  upward  or  any  other  operating  system
    supporting DOS sessions

     The package showed its  efficiency  during  workbenches  on  the
 following platforms:

     MS-DOS ver.  5-7
     OS/2 v3, DOS session
     Windows 95, 98, 2000, DOS session
     Windows NT v.4.0, DOS session

  Memory volume on hard disk:
  Executed files located in BIN directory - 3.8 Mb.
  Total                                   - 4.5 Mb.


 3. Installing FreeStyleRoute on hard disk.

    The package is delivered as a self-extracting archive. To install
 it:
     1. Create an empty directory with an arbitrary name.
     2. Copy contents of the distribution disk to the directory.
     3. Start self-extracting file FSRSETUP.EXE.

     After the unpack is completed the following catalog structure is
 formed in the working directory:

     FSR (working directory)
      
      BIN
      DOC
      EXAMPLES
              <Proj1>
              <Proj2>
             ...
              <Projn>

     BIN directory contains executed FSR files.
     DOC directory contains documents.
     EXAMPLES directory  contains  examples  of  FSR  operation   in
 separate subdirectories.

     The executive module is named FSR.EXE,  the other executed files
 must not be started directly.
     Location and  names  of  subdirectories   are   not   important.
 Independent  directories  must be created for each task.  FSR.EXE is
 called from working directories.  To make a call you have to enter a
 complete  path  to the BIN directory in the DOS command line or in a
 specially created command file.  You do not need to specify anything
 in the PATH environment variable.  An example of the FSR.BAT command
 file is included in the package.

     It is recommended to create a directory for temporary  files.  A
 path  to  the directory is entered in the TEMP environment variable.
 (Example:  SET TEMP=E:\TEMP).  Usually this directory locates on the
 electronic  disk - in this case performance speed increases.  If the
 TEMP variable is missing, temporary files are created in the working
 directory.  If the TEMP variable specifies a non-existent directory,
 correct work of the programs is not guaranteed.


 4.  Package operation.
 4.1. Data files.

    FreeStyleRoute recognizes and outputs data,saved in PDIF format
 (PCAD Data Interchange Format). These files have .PDF-expansion.

     Besides of a .PDF-file,  the file FSROUTE.STL must be available,
 since it describes the contact  pads  configuration,  the  width  of
 tracks  and  the  size  of  backlashes  between them.  Every working
 catalog must have just one such file.
     The file  FSROUTE.STL  is  created  and  edited  by the built-in
 editor at the command "SCRIPT/DEFINE DESIGN STYLE"

     Names of data files in the internal FSR format are * .FSB.

 4.2. Starting the program.

      You can start the  program  by  simply  calling  fsr  and  then
 selecting the input PDF file in the menu "PROJECT", or by specifying
 the input file as a parameter while making a call:

 fsr  <PDF_input_file>.

 4.3. Operation management. Panels. The Main menu.

      The main  menu  locates  on the left.  It helps open additional
 panels with executive submenus.  We will describe here only the main
 menu  and  the  menu "SCRIPT".  The built-in context- sensitive help
 will provide you with prompts for any menu during operation process.

 4.3.1. Main menu.

  EXIT      - terminate work session and exit system
  PROJECT   - open/save project
  SCRIPT    - base panel where PB  routing  process  is  managed from
  INTERFACE - panel for calling external systems and programs
  SETTINGS  - seting system parameters
  HELP      - about the program
  ABOUT     - about the developers

 4.3.2. Operation script.

       The panel "SCENARIO" is used to manage base design cycle. This
 cycle  includes  a number of procedures,  called interatively untill
 the developer is satisfied with the result acheived.


      DEFINE DESIGN STYLE

      RE-ROUTE ANEW                  | SpeedWay
      IMPROVE ROUTING QUALITY        | (router)
      CHOOSE THE BEST VARIANT        |
      CREATE INTERMEDIATE PDF-FILE   V

      CORRECT TRACKS    FORM         |  FreeStyle
      ADJUST ELEMENTS DISPOSITION    | (correcter)
      CREATE PDF-FILE IN FSR STYLE   V


 5. Organizing operation process to provide effective routing.

  To provide effective operation the developer shall:
    - Prepare correct input data;
    - Define parameters specifying design style;
    - Understand the purpose of actions executed by the system during
      the routing process,  interfere in automatic program  operation
      process  and  implement  manual  correction  of  the  operation
      process results if necessary;
    - Organize interaction with the EDA used.

     Now we  will  consider how to ensure the fulfilment of the above
 requirements.

 5.1. Preparing input data.

      The input  data  are  prepared  before  the  routing process is
 started by means of an external EDA.  Circuits  must  be  specified,
 components placed etc. You have to make sure that each component and
 the board itself has a border marked by a closed  contour.  Prepared
 routing data should be converted into the PDF format.

      ATTENTION! While  creating  .PDF-file  with the utility PDIFOUT
 the option "Include Pin Name in Subcomponent Section" must  be  off,
 i.e.  you  can  not  enter  alphanumeric  names  of  contacts in the
 component circuits description section.

 5.2. Definition of the design style.

      Design style description is stored  in  the  file  FSROUTE.STL.
 Every  working  catalog  should  contain just one such file.  Design
 style means availability of certain agreements  made  to  adopt  the
 FreeStyleRoute system to an external EDA.  It describes data which
 were not defined or were not completely defined  in  the  PDIF-file:
 contact  pads  form,  tracks  width  and  backlashes size,  elements
 movement pitch value etc.  Some of these data can be  found  in  the
 file  containing  the routing strategy description,  others are new.
 The file FSROUTE.STL is created and edited by the built-in editor at
 the command "SCRIPT/DEFINE DESIGN STYLE".

 Actions sequencing:

   - Select  the  menu  item  "SCRIPT  /  DEFINE DESIGN STYLE".  If a
     CTL-file was previously created for routing in the system P-CAD,
     import data from it through the menu item "STRATEGY IMPORT";
   - Assign layers and barriers in the item "LAYERS ASSIGNMENT";
   - Specify  routing  layers  and  their  diposition  on  the  board
     (upper/lower) in the item "ROUTING LAYERS";
   - Define contact pads in the item " CONTACT PADS DESCRIPTION";
   - Define circuits classes and parameters  in  the  item  "CIRCUITS
     CLASSES";
   - Define components classes and parameters in the item "COMPONENTS
     CLASSES".


 5.2.1. Strategy import.

        If you have  a  ready  P-CAD  (system)  file  describing  the
 routing  strategy (.CTL),  you can import information on the contact
 pads form,  routing  layers  quantity  and  circuits  routing  rules
 therefrom  by selecting the item "STRATEGY IMPORT",  but as FSR uses
 more parameters, you will have to define some of them manually.


 5.2.2. Layers assignment.

        FreeStyleRoute's  layers concept  is different from P-CAD's
 one.  FSR deals  with  physical  planes:  metallization  planes  for
 circuits  routing  and  one or two planes for components placing (on
 two sides of the board).
        The section  "LAYERS ASSIGNMENT" defines the display of logic
 layers on the plane.  FSR does not make any  assumptions  concerning
 layers names,  no names are reserved. The names can have length from
 1 up to 6, empty names are forbidden.
        FreeStyleRoute  has ability  to shift (move) elements after
 the routing is completed - it keeps circuits integrity and  observes
 required backlashes. Real outlines (contours) of the components must
 be described to avoid their "overlapping".  If a layer specified  by
 the  base layer describing the outlines is used in a library element
 description,  this layer is applied.  Otherwise alternate layers are
 applied.


 5.2.3. Contact pads description.

        Contact pads can be represented by  two  geometrical  models:
 circle  and  "sausage".  The latter is used to represent rectangular
 and square contact pads,  including bars.  "Sausage" is a wide  line
 (rectangle)  with semicircular "caps" on its ends.  Slope and length
 of the line are specified by the parameter "STRETCH", the line being
 able to be oriented not only horizontally or vertically, but also at
 an arbitrary angle.  Contact pads rotate together  with  components.
 Each  contact  pad  type should undoubtedly define a pin or a planar
 contact.  A   component   can   have   pin   and   planar   contacts
 simultaneously.


 5.2.4. Bars description.

        Not-round contact pads are described by means of  "sausages",
 special  attention  should  be  paid to the square pads orientation:
 "sausages" should be stretched across the chip contacts  line  -  in
 this case "caps" will less hinder the tracks. Bar orientation should
 be correctly specified by  the  parameter  "STRETCH"  and,  besides,
 sometimes it is required to specify the shifting of the bar symmetry
 center toward the  corresponding  pin's  center.  This  shifting  is
 specified by the parameter "CENTRE".


 5.2.5. Contact pads specific types.

        When contact pad's form is described in the routing  strategy
 file, FreeStyleRoute uses this description.  But sometimes instead
 of  describing  contact  pad's  form,  barriers   are   entered   in
 appropriate  places  in  the  library  element description or in the
 section  "ANNOTATE  of  a  .PDF-  file.  FSR  does  not   use   this
 information.  In this case make sure that you know the exact form of
 a contact pad of this type and describe it yourself in  the  section
 "CONTACTS TYPES", paying particular attention to the orientation.
        If it is impossible to choose the correct  orientation,  this
 type  of  contact  pad  being  used  in  inconsistent ways by one or
 several components,  the unique issue is to change  selectively  the
 contacts type of a component or library element,  i.e. correction of
 the initial job with an external editor is required.


 5.2.6. Description of tracks,  backlashes, vias and tracks branching
        points.

      Tracks and backlashes are described in  the  section  "CIRCUITS
 CLASSES".  Common  parameters for all circuits are minimum allowable
 backlash between track edge and board edge and branchings  and  vias
 setup grid pitch. Designer has to divide circuits into classes, each
 class has its own routing parameters, namely:
   - width
   - minimum allowable backlash
   - nominal backlash
   - types of automatically set vias (all vias are through)

      During routing process the system will try to observe  assigned
 tracks  width  and  nominal backlashes between tracks.  If it is not
 possible to observe nominal backlash, the system will reduce it down
 to   the  minimum,  creating  thus  "bottlenecks".  Bottlenecks  are
 indicated during routing process  and  can  be  then  liquidated  by
 moving components.

      A special  grid  is  specified  to setup vias.  Another grid is
 specified  for  tracks  branching  points.  Notice  that  the   same
 parameter  is  used to fix sharp bends points of approximated tracks
 in draft mode.  These grids are generally used to facilitate  manual
 correction  of  the printed layout in external graphic editor and to
 provide compatibility with technological equipment  used.
      FreeStyleRoute does not require grids, big values of the grid
 pitch only complicate the operation of the FreeStyle  corrector,  do
 not specify grids that are larger than you need.


 5.2.7. Description of the rules of components fixing.

        FreeStyle corrector has  ability  to  shift  (move)  elements
 within  certain  limits  keeping  circuits  integrity  and observing
 required backlashes.  Therefore moving rules should be specified and
 real  outlines  (contours)  of the components should be described in
 the initial job. As well as circuits, components can be divided into
 classes. X- and Y-axis grid pitch is specified for each class. These
 parameters are used during automatic or manual moving of components.
        Besides, the common parameter for all components is specified
 - minimum allowable backlash between outlines of components  located
 on the same board side.


 5.3. SpeedWay. Fast routing.

      SpeedWay is called by the command "RE-ROUTE" and means  routing
 anew with loss of connections already routed.  The following actions
 can be executed:

 - Manual placement of components with instant re-routing facilitated
   by the following features:
    - Components rotation and movement with highlighting of  incident
      connections of a moved component.
    - Highlighting  of  potential  bottlenecks,  i.e.  gaps   between
      contacts,  where  the  required  quantity  of tracks can not be
      placed in one layer. Probably they can be placed in two layers.
    - Indication of tracks current length (approximately),  length of
      point-to-point connections and bottlenecks quantity
    - Selecting  two circuits at once by different colours.
 - Fixing components - valid for elements having  fixed  location  on
   the board.

      Components which are not fixed are considered mobile. It means,
 in particular,  (if the reloading between modules is  allowed)  that
 the  system  won't  limit  the  quantity of tracks between not-fixed
 components, considering that possible bottlenecks will be liquidated
 by  moving  components.
      Components fixation influences considerably the  board  layout.
 Therefore  only  the  components which do need to be fixed,  require
 fixing.

      100% circuits   routing   is  completed  in  1-2  seconds.  All
 connections will be routed,  even if it  requires  to  violate  some
 technological  restrictions.  Thus,  you  can  check the adequacy of
 constructive choice and components placement on  the  early  routing
 stage.
      At this  moment tracks length is usually much inferior to P-CAD
 results but the vias quantity can be some larger.


 5.3.1. Improvement of routing quality.

        Optimization procedure  is  used  to improve routing quality.
 Tracks  total  length  and  vias  number  are  minimized.  The  best
 assignment  of  tracks  sections  on commutation layers is chosen as
 well as their placement in respect of other tracks and contact pads.
 5-10  minutes optimization can give a very good result.  During next
 10-20 minutes routing quality improve less.
        The greatest  contribution to optimization process is made by
 the algorithm of global minimization  of  tracks  vias  number.  The
 algorithm   is  unique,  it  has  theoretically  minimum  number  of
 operations  which  allows  to  minimize  vias  number  for   current
 overlaying tracks layout precisely and in less than one second.
        The following result is usually achieved: 0.5 vias per circuit
 for  layouts  with  prevalence of components with planar outputs and
 0.06 vias per circuit for layouts with prevalence of components with
 planar outputs,  i.e.,  5 and 30 times better accordingly than P-CAD
 results.  It is  also  much  better  than  ordinary  manual  routing
 results.

        FSR automatically  selects  optimum routing variants and save
 them under the names of vvv_llll.fsb,  where vvv means  vias  number
 and llll - tracks total length in centimeters.  Optimization process
 can only be interrupted by operator, auto-stop is not provided.
        Optimization can  be  suspended  and then renewed through the
 item "IMPROVE ROUTING QUALITY". It is also possible to return to the
 stage  of  manual  placement of components (with loss of connections
 already made) without creating an intermediate .PDF-file.


 5.3.2. Choosing the best routing variant.

      The operator  is to choose the variant which he thinks the best
 from a number of automatically saved competitive variants.  With the
 command  "CREATE  INTERMEDIATE  .PDF-FILE"  the  selected variant is
 transformed in intermediate  PDF-file.for  further  correction  with
 FreeStyle corrector.


  5.4. FreeStyle. Layout correction.

      FreeStyle corrector is used to improve the layout of  a  routed
 board.  The  board  should  be  pre-routed  with the supplied router
 SpeedWay or any other router. The following actions are executed:

 - Optimization of tracks form;
 - Moving components;
 - Moving vias and tracks branching points.

      The optimum tracks form is computed automatically. Each track's
 route  has  the  shortest length,  i.e.  bends round contact pads by
 circles arcs with a required backlash and passes  from  one  arc  to
 another along straight lines segments.
      Moving tracks components, vias and branchings is used to reduce
 tracks   length,   provide   required   backlashes  (liquidation  of
 bottlenecks) and to reduce board area occupied by components. Moving
 can be done manually or automatically. During the moving process the
 optimum tracks placement is immediately re-computed.
      To execute  automatic  moving  a number of parameters should be
 specified by means of the dialogue box "PARAM / MOV".

      Moving vias and branching points is  done  automatically,  vias
 and  branchings  move  to  optimum  computed locations.  If the item
 "gradually  reduce  movement   pitch"   is   marked,   the   program
 automatically   stops  after  the  optimum  is  achieved.  20  -  30
 iterations are required depending on the grid pitch.
      To move  components it is better to use combined strategy which
 represents a combination of automatic and manual stages.  To  reduce
 board  area  it  is  recommended  to  initiate  the  "drift"  to the
 requisite direction.  Components which must not move  automatically,
 must be fixed.
      Manual moving  of  components,  vias  and  branchings  has  the
 following  peculiarity:  if  the  switch  "push"  is  not in the "-"
 position, all requirements to the backlashes size should be observed
 during  moving  process,  and  if  it  is  in the "-" position,  any
 violation is allowed, i.e. you may drag a via through any slot, e.g.
 between chip planar contacts.

      ATTENTION! At   this   stage  tracks  layout  is  not  changed,
 therefore,  e.g.,  to insert a track between other  contacts  or  in
 another  layer,  the  external  editor should be used,  for example,
 PC-CARDS (see item 5.5).
      If the editor PC-CARDS is used,  it is recommended to switch on
 the option "draft mode" while creating output .PDF-file,  and it  is
 important  to  correctly  set  branchings setup grid for the version
 4.5.


 5.5. Organization of interaction with external procedures.

      To interact   with   other   systems  and  programs  the  panel
 "INTERFACE" is provided allowing to call external programs. External
 programs are called by pressing corresponding buttons.  The operator
 can create, modify and delete buttons.
      Up to  three  successively executed commands can be assigned to
 each button.  If there are more than three commands they  should  be
 called through batch files.
 .PDF-filename without extension  can  be  entered  into  the  called
 program  as  a parameter.  It can be done with a quasi-variable with
 the name %s.  You can use up to 4 "%s" in one command line.  If  you
 need  to  use "%" symbol for another purpose,  you should repeat it:
 "%%".
      We will give an example:  a practically useful call allowing to
 use the graphic editor PC- CARDS to view and  edit  results  of  FSR
 system operation and then transfer corrected results back in FSR:

   PDIFIN   %s.pdf   tmp.pcb > nul
   PCCARDS  -r       tmp.pcb
   PDIFOUT  tmp.pcb  %s.pdf  > nul


 5.6. Saving results.

      Intermediate operation  results  are   saved   in   .FSB-files.
 Compatibility  of  internal  formats  of  different  versions is not
 guaranteed.

 ATTENTION! Do not delete initial .PDF-file until work on project  is
 completed, you will need it to create output .PDF-file.

      The final variant is recorded with the command "CREATE PDF-FILE
 IN FSR STYLE".  It is recommended to execute  the  command  "CORRECT
 TRACKS  FORM"  before  recording  the  final variant - if the option
 "draft mode" is on, you should switch it off.

 5.7. Correcting automatic design results.

      As well as any other automatic design system,  FSR has its  own
 imperfections.  Therefore  the  designer is given the possibility to
 interfere in the system operation and to "correct" its results.

 Liquidation of bottlenecks.
      If there  are  any bottlenecks during the routing process (this
 is typical for practically any board),  you should use the following
 methods to liquidate them:

   - Moving vias
   - Moving tracks branching points
   - Moving components
   - Changing track route.

      All items,  except last one,  are executed in the item "CORRECT
 ELEMENTS  PLACEMENT".  To  change  tracks  route an external graphic
 editor must be called.

      Changing tracks route. Sometimes it is possible to reduce track
 length,  to  liquidate a bottleneck or to execute some other actions
 useful from the man's point of view,  by changing a track route. You
 should  use an external editor for this purpose.  To use an external
 editor,  you should first connect  it  correctly  through  the  item
 "INTERFACE" (item 5.5).

      Thus, to  correct  track route you should execute the following
 actions:

  - Create PDF file in FSR  style,  the  option  "draft  mode"  being
    switched on. First you should set tracks branchings setup grid to
    provide their easy correction in the graphic editor that you use.
    For instance, proper values for PC-CARDS v 4.5 are 5:5 or 25:25.
  - Pass to the panel "INTERFACE" and  call  graphic  editor.  Modify
    layout.   Do  not  care  about  observing  backlashes  and  other
    auxiliary technical details. The only thing you should care about
    is not to let tracks cross.
  - Save results. Exit the editor and go back to the FSR environment.
  - Pass  to  the panel "SCRIPT" and execute the item "CORRECT TRACKS
    FORM".
  - To complete the process,  you should execute the item "CREATE PDF
    FILE IN FSR STYLE" once again,  the  option  "draft  mode"  being
    switched off.

  6. Tecnical characteristics and restrictions (approximate data).
 Ŀ
   Grid-less router SpeedWay   Geometrical corrector FreeStyle 
 Ĵ
  Components             1000  Components                 1000 
  Contacts               5000  Contacts                   5000 
  Circuits               5000  Circuits                   5000 
  Classes of circuits      20  Classes of circuits          20 
  Signal layers             2  Signal layers                32 
  Board size      0.6m x 0.6m  Board size          300m x 300m 
  Precision       0,1 microns  Precision           0,1 microns 
 

 Restrictions for the router SpeedWay:

     Vias prohibition  area  and  any  text in routing layers are not
 taken into consideration.
     Routing is always executed in two layers. Consequently, all vias
 are through.
     Polygons and internal conducting layers are not recognized.
     All previously placed tracks are ignored. Therefore, to describe
 power supply buses,  aerials,  loops or  reserve  lines  you  should
 define them as contacts.
     If automatic  change  of component coordinates is undesirable or
 impossible, the component should be announced fixed.

 Restrictions for corrector FreeStyle:

     All vias are through.
     Polygons and internal conducting layers are not recognized.
     Text in  routing  layers  should  be  enclosed  in  the  routing
 prohibition area (on corresponding layer).
     All tracks  are  considered changeable.  Therefore,  to describe
 power supply buses,  aerials,  loops or  reserve  lines  you  should
 define them as contacts.
     Tracks of different circuits must not cross in one layer.
     Placement of  components  in  several tiers (on one side) is not
 supported.
     It is  impossible to specify that several components should move
 together as one unit. For instance, a component and its fixture.


 7. Information about the developers.

 St.Petersburg, Russia.
 Team manager: Serguej Jurjevich Luzin,
               ph. (7 812) 592-18-32.
               E-mail: luzin1@.rol.ru
 Author of the method: Oleg Borisovich Polubasov.
                       E-mail: pbas@rol.ru

 Dial Ingenering: ph. (7 812) 301-90-30
                  www.Dial-Eng.spb.ru

    The work   has   begun  at  the  end  of  80's  in  NPO  "Distant
 Communications"  ("Dalnjaa  svjaz").  Team's  scientific  interests:
 discrete  optimization methods,  radioelectronic equipment technical
 design,  PLM logic synthesis.  A number of fundamentally new results
 have  been  obtained  in  these areas (models,  algorithms and their
 program realizations).

 Ŀ
  The FSR developers team 
  wish you fruitful work! 
 
