Welcome to Scribd. Sign in or start your free trial to enjoy unlimited e-books, audiobooks & documents.Find out more
Download
Standard view
Full view
of .
Look up keyword
Like this
30Activity
0 of .
Results for:
No results containing your search query
P. 1
Proteus Isis Application Note (English)

Proteus Isis Application Note (English)

Ratings: (0)|Views: 2,485|Likes:
Published by Carlos Navarro M.
ISIS APPLICATION NOTE (English)
ISIS APPLICATION NOTE (English)

More info:

Published by: Carlos Navarro M. on Oct 20, 2009
Copyright:Attribution Non-commercial

Availability:

Read on Scribd mobile: iPhone, iPad and Android.
download as PDF, TXT or read online from Scribd
See more
See less

01/25/2013

pdf

text

original

 
ISIS APPLICATION NOTE
ISIS SDF Netlist 3.0 Technical Information1. Introduction
SDF is Labcenter's native netlist format. It was designed with the following requirements in mind:
q
The netlist file should contain all the textual information stored in the schematic. This includes not just part name and connectivity but also part properties, net properties and pin types. It is thuspossible to do all manner of database type processing on your designs by means of analysingSDF files.
q
The format should be compact. Some netlist formats are mind bogglingly verbose - the EDIFformat as defined by an international standards committee) has failed to catch on because evensimple designs can result in files of over 1Mb!
q
The format should be easy to parse. In fact, SDF files can be read with BASIC programs so youdon't have to be a C wizard to make use of SDF.The rest of this document describes the SDF file format - if you don't understand what follows it is unlikelythat you have sufficient programming experience to work with SDF files.
2. Basic File Structure
An SDF file is divided into several sections or 'blocks', as follows:
q
A header block.
q
A
PROPERTIES
block.
q
A
MAPPINGS
block.
q
A
MODELDEFS
block.
q
Zero or more
SCRIPT
blocks.
q
A
PARTLIST
block.
q
A
NETLIST
block.
2.1 Block Structure
Each section or block is identified by a single line which begins with the block name immediatelypreceded by an asterisk ('*') character.The header and
SCRIPT
blocks are subtlety different to the others - the header because it is simply just afile header at the top of the netlist, and the
SCRIPT
block as it is simply a direct dump of similarly-namedtext script objects in ISIS. The structure and format of these blocks is discussed fully in a subsequentsection.For the remaining blocks, the block name is followed by a comma (',') character and an integer count ofthe number of
additional 
 
lines in the block
 
that follow it. Each block is line oriented (i.e. one item orrecord per line) and comma separated. Fields likely to contain commas are enclosed in double quotes;no field may contain the double quote character.
3. The HEADER Block
The header block is simply a block of text that appears at the top of the SDF file and gives details of thedesign from which the netlist was extracted An example header block is shown below:
ISIS SCHEMATIC DESCRIPTION FORMAT 3.0=====================================Design: C:\PROTEUS\SAMPLES\SOMEFILE.DSNDoc. no.: <NONE>Revision: <NONE> Author: <NONE>Created: 10-Jun-94 Modified: 12-Jun-94
 
The first line identifies that the file contains an SDF version 3.0 netlist; the remaining lines containinformation extracted from the
Design Properties 
dialogue form in ISIS. Each field starts exactly 10characters in from the left.MDF model files created for use with the LISA simulators have a slightly different header.
LISA MODEL DESCRIPTION FORMAT 3.0
In other respects they are identical to normal SDF files.
4. The PROPERTIES Block
The
PROPERTIES
block contains global design properties assigned through
*DEFINE
scripts in the ISISdesign and possibly through other mechanisms (e.g. for netlists generated for use with either of the LISAsimulators, simulation control properties assigned of the
Edit...Graph 
dialogue forms are placed in the
PROPERTIES
block). There is only one
PROPERTIES
block in an SDF 3.0 netlist file.For example, an ISIS design containing the text script:
*DEFINEBETA=100 MIN_STEPS=100
results in a netlist containing the following
PROPERTIES
block:
*PROPERTIES,2BETA=100 MIN_STEPS=100
The first line indicates that this is a
PROPERTIES
block and contains two records. Each record is thenspecified on its own line in the form:
<pname>=<pvalue>
where:
<pname>
is the name of the property being assigned.
<pvalue>
is the value being assigned to it.
Note that the names of properties being assigned and the values they are assigned is dependent on theend use of the netlist.
5. The MAPPINGS Block
For a normal SDF 3.0 netlist, the
MAPPINGS
block is always empty (that is, the record count in the
*MAPPINGS
line is always zero). For MDF linkable netlists (i.e. model files) generated for use with theLabcenter LISA simulators, the
MAPPINGS
block contains the
MAP
 
ON
mappings from a
MAP
 
ON
script inthe ISIS design.The
MAPPINGS
block is used by the Labcenter LISA simulators to conditionally define a set of sheetproperties depending on the value of another (second) sheet property. At present, the netlist generator inISIS only generates a
MAPPINGS
block from a
MAP
 
ON
script where this second property is the
VALUE
property (this is usually the value of the component being modelled) and hence this parameter is
not 
explicitly present in the netlist.For example, an ISIS design containing the text script:
*MAP ON VALUE7407 : TDLHDQ=6n, TDHLDQ=20n, OCOPS=Q7417 : TDLHDQ=6n, TDHLDQ=20n, OCOPS=Q74HC07 : TDLHDQ=7n, TDHLDQ=7n, OCOPS=Q
results in a
model 
netlist containing the following
MAPPINGS
block:
*MAPPINGS,37407 : TDLHDQ=6n, TDHLDQ=20n, OCOPS=Q7417 : TDLHDQ=6n, TDHLDQ=20n, OCOPS=Q74HC07 : TDLHDQ=7n, TDHLDQ=7n, OCOPS=Q
 
The first line indicates this is a
MAPPINGS
block and is followed by three records. Each record is then ofthe form:
<value> : <pname=pvalue>, ..., <pname=pvalue>
where:
<value>
is the text to be matched against the sheet
VALUE
property.
<pname>
is the name of a property to be assigned if a match occurs.
<pvalue>
is the value to be assigned to the named property if a match occurs.
Thus, in the above example, if value of the sheet
VALUE
property is 74HC17, then the sheet properties
TDLHDQ
and
TDHLDQ
are assigned the value 7n and the property
OCOPS
is assigned the value
Q
.For more information in
MAP
 
ON
scripts, consult section 6.4.7 in the ISIS manual and the DSIM ModellingTutorial (section 2.5.4 in particular) in the LISA manual.
6. The MODELDEFS Block
For a normal SDF 3.0 netlist, the
MODELDEFS
block is always empty (that is, the record count in the
*MODELDEFS
line is always zero). For MDF linkable netlists (i.e. model files) generated for use with theLabcenter LISA simulators, the
MODELDEFS
block contains the model definititions from the
MODELS
script(s) in the ISIS design.The
MODELDEFS
block is used by the LISA simulators (currently only the analogue simulator) to allowseveral property assignments to be grouped under a single name. A component can then assign all theproperties in a
MODELDEFS
record by assigning the
MODELDEFS
record name to its
MODEL
property.For example, an ISIS design containing the text script:
*MODELS741_NPN : BETAF=80,ISAT=1E-14,RB=100,VAF=50,TAUF=0.3E-9,TAUR=6E-9741_PNP : BETAF=10,ISAT=1E-14,RB=20, VAF=50,TAUF=1E-9, TAUR=20E-9
results in a netlist containing the
MODELDEFS
block:
*MODELDEFS,2741_NPN : BETAF=80,ISAT=1E-14,RB=100,VAF=50,TAUF=0.3E-9,TAUR=6E-9741_PNP : BETAF=10,ISAT=1E-14,RB=20, VAF=50,TAUF=1E-9, TAUR=20E-9
The first line indicates this is a
MODELDEFS
block and is followed by two records. Each record is then ofthe form:
<name> : <pname=pvalue>, ..., <pname=pvalue>
where:
<name>
is the name of the record.
<pname>
is the name of a property to be assigned.
<pvalue>
is the value to be assigned to the named property.Thus, in the above example, if a component in the netlist contains the property assignment:
 MODEL=741_NPN
this is the same as it containing the multiple assignments:
BETAF=80,ISAT=1E-14,RB=100,VAF=50,TAUF=0.3E-9,TAUR=6E-9
For more information in
MODELS
scripts, consult section 6.4.8 in the ISIS manual.
7. The SCRIPT Blocks
An SDF 3.0 netlist may contain zero or more
SCRIPT
blocks. Each
SCRIPT
block is a direct export froman a script in the ISIS design, the first line of which begins
*SCRIPT
and in which the last line begins
*ENDSCRIPT
. All characters after the leading
*SCRIPT
and up to and including the characters on theline beginning
*ENDSCRIPT
are placed in the netlist.

Activity (30)

You've already reviewed this. Edit your review.
1 hundred reads
1 thousand reads
Jordy Wallace liked this
mancst liked this
Vista liked this
Vista liked this
Stanislaw Szylin liked this
Hai Pham liked this
Ali Shaheen liked this
orb1t_ua liked this

You're Reading a Free Preview

Download
scribd
/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->