COMMAND REFERENCE

The following is a description of the command set exposed to the user that will execute routing operations on the layout. These commands can be typed in directly when routing in interactive mode or used to construct a custom routing script when working in scriptable mode. Typically, you might only use the first six of these commands for interactive mode whereas you may well need to use some of the more advanced commands when in scripting modes. Each command includes a description of usage, the command syntax and an example.

The BUS Command

This command invokes a bus routing pass only on regular array of pins with collinear connections where the pins share a common X or Y coordinate. This is particularly effective on memory arrays. In this mode, the router will not generate conflicts, so rules must allow for sufficient space. By default traces are routed orthogonally, unless the diagonal option is specified. Typically, this command should be the first issued in a routing script.

Basic Syntax:

bus [diagonal]

Example:

bus diagonal

The FANOUT Command

This command autoroutes small escape wires with a via from SMD pads. Recommended for use at the start of routing where there are more than two signal layers. Not recommended for use with two layer boards as it will block routing spaces.

Typically, this command should be issued immediately after the bus command and prior to any route commands.

Basic Syntax:

fanout <number of passes>

Example:

fanout 5

The fanout direction can be also be set so that fanout vias are added inside SMD components and/or outside. Fanout can be limited by pin type, for example pins connected to power nets only.

Full Syntax:

fanout [<passes>]

[(direction [in_out|in|out])]

[(pin_share [on|off])]

[(via_share [on|off])]

[(pin_type [active|signal|power|unused|all|single])]

[(max_len <positive_dimension>)]

[(via_grid <positive_dimension>)]

[(depth opposite <positive_integer>)]

[(share_len <positive_dimension>)]

Square brackets denote an optional element; the round brackets are part of the syntax and must be typed.

Example: depth for blind and buried vias

fanout 5 (depth opposite 2) (share_len 500)

Example: fanout on signal pins only, sharing vias

fanout 5 (pin_type signal) (via_share on)

Example: fanout using a via grid of 25th

fanout 5 (via_grid 25)

The ROUTE Command

This command tells the autorouter to perform a specified number of routing passes and is the basic command used when routing. Typically you would use this command iteratively with the clean command to achieve completion. The start pass parameter is optional; it should only be used on the second or subsequent routing phases, and it sets the initial costing of the first routing pass of that route set.

Basic Syntax:

route <number of passes> [<start pass>]

Example:

route 20 (first routing phase)

route 20 16 (subsequent routing phases)

The CLEAN Command

The clean command will basically rip-up and reroute each net with high via cost and the highest cost for making clearance and crossing violation. This command is typically used iteratively with the route command: perform some routing passes, clean, perform some more routing passes, clean again, and so on. However, when full completion is reached the clean command can be used to minimise vias.

Basic Syntax:

clean <number of passes>

Example:

clean 2

The FILTER Command

At the end of a routing session you may end up with wires/vias in conflicts (crossing or too close to each other). The filter command will remove these conflicts by unrouting the minimum number of connections that are currently in conflict

Basic Syntax:

filter <number of passes>

Example:

filter 5

The RECORNER Command

The recorner command changes 90 degree wire corners to 135 degrees. It is performed on wire corners exiting pins and vias as well as bend and slant wire configuration. This command is used after completion is reached to reduce track length. This command is typically issued last.

Basic Syntax:

recorner [diagonal]

Example:

recorner diagonal

The CHECK Command

This command can be used to run a DRC (design rules check) and visually tag the violations. This is used in particular when a rule is changed. A check is automatically invoked after every routing pass. The total number of violations is shown on the status line and visual feedback is added to the layout view to indicate conflict locations.

Basic Syntax:

check

Example:

check

The CIRCUIT Command

This command is used to schedule the routing order priorities, specific vias to be used and allowed routing layers amongst nets and net classes.

Basic Syntax:

class <class_id> | net <net_id> circuit {<circuit_descriptor>}

<circuit_descriptor> ::=

[(priority <positive_integer> |

(use_via {<padstack_id>}) |

(use_layer {<layer_name>})]

The value of priority ranges from 0 to 255, the default is 10.

The use_via rule assigns one or more via padstacks to a class or a net. If more than one padstack is defined, the autorouter will favour the smallest padstack in size.

The use_layer rule assigns the routing layers on which nets and classes must be routed. Note that the use_layer rule will override a layer unselection. Layers are named with the Proteus designators TOP, I1 to I14 and BOT.

Example: Routing a net/class to specific layers

net sig1 (circuit (use_layer TOP BOT))

class fast (circuit (use_layer I1 I2))

Example: Assigning Routing Priority

net sig1 (circuit(priority 200))

Example: Routing a defined class to specific layers and using specific vias

(class special net1 net2 net3 net4 net5

(circuit

(use_via via.VIA1__1_10.bv1_10 via.VIA3__4_5.bv4_5  via.VIA3__6_7.bv6_7)

(use_layer TOP I1 I2 I3 I4 BOT)

)

(rule

(width 0.007)

(clearance 0.007)

(clearance 0.001 (type via_via_same_net))

(clearance 0.001 (type smd_via_same_net))

)

)

The COST Command

This command sets the internally defined costs to a fixed value. By default, some of the cost values get internally modified during autorouting. It is not recommended to change cross and squeeze costing specifically.

Cost values can range from 0 to 100. A value of -1 will reset the cost value. Predefined cost description values can be used:

Cost Value

Forbidden

100

High

50

Medium

25

Low

8

Free

0

The following costs can be set:

Option Description

Cross

Crossing conflict

Squeeze

wire to wire clearance conflict

via

wire to via clearance conflict

way

cost of routing in non-preferred layer direction

off-grid

cost of routing off-grid if specified

off-center

cost of entering or exiting an SMD pad off centre.

side exit

cost to exit SMD pads on long side

layer

cost of using the layer. Qualify it with (type length) for the cost of using the layer at all, or with (type way) for the cost of routing against that layer's preferred direction.

Basic Syntax:

cost <cost-type>

cost <cost_type> cost_descriptors>|[(type[length|way])] |-1]]

Examples:

cost layer TOP forbidden

cost layer I1 high (type way)

cost via high

The DIRECTION Command

Changes preferred routing direction by layer.

Basic Syntax :

direction <layer name> [horizontal|vertical|orthogonal|off]

The GRID Command

Specifies wire and via grid spacing.

Basic Syntax:

grid [via<positive_value>[<via_id>] | wire<positive_value>[<layer_name>]

Examples:

grid wire 8.333

grid wire 5 layer 1

The LIMIT Command

The limit command sets absolute limit values to be applied to each connection. Control is provided to limit maximum allowed number of intersecting wire, number of vias per connection, number of bends, and the maximum distance of non preferred (wrong-way) routing. The range of limit for <positive_integer> is 0 through 255. You can set limit values, perform some routing passes, and return to the default system values by executing a limit command with a value of -1. If you do not supply limit values, computed default values are used by the autorouter.

Basic Syntax:

limit [cross [<positive_integer> | -1] |

via [<positive_integer> | -1] |

bend [<positive_integer> | -1] |

way [<positive_dimension> | -1]]

Examples:

limit via 2

limit way 200

limit way -1 (resets limit to default)

The LOCK Command

Prevents the router from changing or deleting locked wires. Note that the router is not allowed to connect to locked wires

Basic Syntax:

lock net <name>

The PROTECT Command

Prevents router from changing or deleting protected wiring. This option may be useful to protect pre-routed ground and power nets. Note that the router is still allowed to connect to protected wiring.

Basic Syntax:

protect all wires

The RULE Command

Rules can be set globally (PCB) or specifically to layers, net classes or nets. Note that in the general case this is handled by the design rule system so this command is only really applicable when working in scriptable execution mode.

There are two categories of rules type; clearances and wiring rules are as shown be the rule descriptor below:

Basic Syntax:

rule [pcb|layer<layer_name>|class <class_id>|

net<net_id>|]{<rule_descriptors>}

 

<rule_descriptor> ::=

[(clearance <positive_dimension>

[(type {<clearance_type>})])] |

[(junction_type [term_only | all])] |

[(limit_bends [<positive_integer | -1])] |

[(limit_crossing [<positive_integer | -1])] |

[(limit_vias [<positive_integer | -1])] |

[(limit_way [<positive_integer | -1])] |

[(max_total_vias [<positive_integer | -1])] |

[(reorder <positive_integer)] | [(tjunction [on | off])] |

[(via_at_smd [off | on [(grid [on | off])] [(fit [on | off])]] |

[(width <positive_dimension>)]

You should use the Design Rule Manager User Interface (Technology Menu) in the layout module to specify rules and then let Proteus communicate with the router to enforce them.

The SELECT Command

This command enables the autorouter to use specific layers and vias for routing. It will also allow for selecting a net for routing. Note that names are case sensitive.

Basic Syntax:

select[layer|via]{<id>}|[all[layers|vias]  |comp{<comp_name>}|[net]{<net_name>}

The SET Command

Sets a named router property. The only property Proteus itself writes is pad_wire_necking, which corresponds to the Enable autonecking? option on the autorouter dialogue form. It is the first line of every schedule Proteus generates, so you will see it at the top of any DO file the router has written for you.

Basic Syntax:

set pad_wire_necking [on|off]

Example:

set pad_wire_necking on

The STATUS_FILE Command

Asks the router to write out its completion statistics. Proteus adds this command to the end of every schedule it generates, so a generated DO file always finishes with it.

Basic Syntax:

status_file

Example:

status_file

The UNLOCK Command

Unlock existing tracks.

Basic Syntax :  

unlock net <name> | [all {layers|vias}]

The UNPROTECT Command

Unprotect existing tracks and allows the router to reconsider them.

Basic Syntax :  

unprotect all wires

The UNSELECT Command

Disallow the autorouter the usage of specific layers and vias for routing. This command can be used to reduce the number of layers from that originally specified. Note that names are case sensitive.

Basic Syntax :

unselect [layer|net|via]{<id>} | [all  {layers|vias}]

Example :

unselect layer s1 s2