All pins that are not connected to a net (whether with a No Connect symbol, or otherwise) appear in the PSTXNET.DAT file, as nets with the name “NC.” Therefore, you should avoid the net alias “NC” in your design. The NC property discussed in the first option, above, appears in the PSTCHIP.DAT file in the NC_PINS line rather than being added to the NC net in PSTXNET.DAT/PSTXPRT.DAT. Therefore, all pins connected to the NC net are unconnected on the PC board.
How properties are netlisted from Capture to PCB Editor
Not all properties in the configuration file show up as properties in PCB Editor. Some of these
properties are used in generating portions of the netlist PST*.DAT files.
In PCB Editor, component properties (package properties in Capture) take precedence over
function properties (part properties in Capture). So in the netlist, a package property value is used if
both a part and package have values for the same property. Capture always uses the occurrence
values in the netlist.
Package (component) properties, which are found in the PSTCHIP.DAT and PSTXPRT.DAT netlist
files, can be viewed in PCB Editor using the Show Element command on a component. For
example, PCB Editor has defined VALUE as a Component Definition property so it appears under
this heading in the Show Element dialog box. Other properties such as CLASS or JEDEC_TYPE
are also listed.
Part (function) properties are found in the PSTXNET.DAT file and can appear as Component
Definition properties if they are predefined in PCB Editor and if you list them in the
[ComponentDefinitionProps] section of the configuration file. Function properties are listed in the
[functionprops] section of the configuration file.
Net properties appear in the PSTXNET.DAT/PSTXPRT.DAT file under the NET_NAME section.
For a design, you can have multiple configuration files. However, the configuration file to be used
while generating PCB Editor netlist needs to be specified in the Setup dialog box launched from the
PCB Editor tab of the Create Netlist dialog box.
This line begins the PSTCHIP.DAT file by declaring the file type. A PSTCHIP.DAT file always starts with the FILE_TYPE=LIBRARY_PARTS statement.
Primitive
A primitive is the description of the physical part.
Part Name
Concatenation of Source Package, PCB Footprint and other properties found in the [ComponentDefinitionProps] section of the configuration file used for netlisting.
Pin
Starts the pin section
Name
Pin name. There is a section for every pin name.
Number,Number…
The pin number for that pin name. if you have a multi-section part, then the pin numbers contaning that pin name are separated by commas
INPUT_LOAD
The netlister assigns this property to an input pin. The input local current is measured in milliamperes. If there is an output load on an output pin you get an OUTPUT_LOAD property.
OUTPUT_TYPE
Netlister assigns this property to define an output pin as open collector, open-emitter, or tri-state (3 state). This data is used to make sure all outputs on a net have the same output type. The OUTPUT_TYPE property also specifies the logic function created by tying the outputs together.
Type
Value of the output pin type when open collector, open emitter, 3 state
PinGroup
This is taken from the PinGroup column in the part editor package property spreadsheet. To see the spreadsheet, from the Package menu choose View, then from the Properties menu choose Edit. This property only shows up in PSTCHIP.DAT if you have a positive value for PinGroup meaning that pin is swappable with the other input pins for that section in the multi-section part
Power：Number; Ground:Numbers
This POWER_PINS line defines the default power and ground requirements for the physical part. Power or ground pins that need to be connected together on the board will share the same name. This syntax for this line is: name of your power pins (VCC for example):the numbers of the power pins; the name of the ground pins:the numbers of the ground pins
NC_PINS
Describes the pins not connected to the logic, but which are present in the physical package. Currently the netlister gets this value from an NC property added to the part and this property has a value of the pins you want to be no connects; these values are separated by commas. You can also cause this line to be generated if you put a no-connect symbol on a pin in the schematic. This property doesn’t show up if you don’t have any NC pins in your design.
Package(Component Definition Property)
Any property found in the property editor on a part that is specified as a property to use in the [ComponentDefinitionProps] section of the configuration file. Properties are separated by commas. The last property is followed by a semicolon. There can by any number of properties.PART_NAME, JEDEC_TYPE, and VALUE are always given in this section regardless of what is in the configuration file.
occurrence_value
The occurrence value of the property is given between the single quotation marks.
PSTCHIP样例
The PSTCHIP.DAT file contains one or more primitives, organized into a pin section and a body section.
Marks the beginning of a net entry. The net name entry always ends with a semicolon after the net property list.
‘Name’
Name of the net or the value of the Name property. If you have a net alias, it is used as the name. This is the flat net name, so if a child schematic has a different name or alias than the same net on the root, the name or alias on the root is the one that gets used.
Canonical Path
The first canonical path uniquely identifies each net in your schematics. It contains your design name, schematic folders, name, and other identifiers.
NODE_NAME
Marks the beginning of a node entry. The node name entry always ends with a semicolon after the node property list.
Reference
The reference of the physical part.
Number
The pin number on the part attached to the net.
Canonical Path
The second canonical path uniquely identifies each part the net is attached to in your schematic pages. It contains your design name, schematic folders, ID, and other identifiers.
Type
Pin type of the pin attached to the net: input (I), output (O), bidirectional (IO), and so on.
Net Property
Any property found in the property editor that is specified as a property to use in the configuration file, [netprops] section. Properties are separated by commas. The last property in the list is followed by a semicolon. There can by any number of properties. An example would be ECL=‘TRUE’;
occurrence_value
The occurrence value of the property is given between the single quotation marks.
### PSTXNET文件格式
FILE_TYPE=EXPANDEDNETLIST;
NET_NAME
'Name'
'Canonical Path';
NODE_NAME Reference Number
'Canonical Path':
'Type':;
Net Property='occurrence_value',
...
;
END.
The PSTXPRT.DAT file (the expanded part list) lists each reference designator and the sections assigned to it. The PSTXPRT.DAT file is ordered by reference designator and section number.
PSTXPRT.DAT文件元素
PSTXPRT.DAT section
Description
DIRECTIVES
Marks the beginning of the directives section. Directives always end with a semicolon.
PST_VERSION
Version of PCB Editor interface.
ROOT_DRAWING
Root schematic folder of design in Capture.
POST_TIME
Date and time of netlist.
SOURCE_TOOL
Tool used is Capture Writer or Design Entry HDL Writer.
END_DIRECTIVES
Marks the end of the Directives section.
Part Reference
The reference designator name of the physical part.
ComponentInstanceProperty
Properties and values of any component instance (package) properties found on the part and listed in the configuration file under the [ComponentInstanceProperty] section.
PART NAME
Concatenation of Source Package, PCB Footprint, and other properties found in the [ComponentDefinitionProps] section of the configuration file used for netlisting.
SECTION_NUMBER #
Marks the beginning of a physical section number. Each section of the package used gets its own section number. Single section parts have only one section number.
Canonical path
The canonical path uniquely identifies each part in your schematic pages. It contains your design name, schematicfolders, part ID, source part, implementation type, and other identifiers.
Physical path
The physical path uniquely identifies each part in a design. The physical path contains the design name, schematic folder, page number, part ID, source part, implementation type, and other identifiers specific to the selected part in the design.
Part (function) property
Any property found in the property editor that is specified as a property to use in the configuration file, [functionprops] section.Properties are separated by commas. The last property in the list is followed by a semicolon. There can by any number of properties.
occurrence_value
The occurrence value of the property is given between the single quotation marks.
PRIM_FILE
Location of the where package properties are listed. This is the PSTCHIP.DAT file which is closely linked to the PSTXPRT.DAT file.
designator
The designator is now stored so that we know if designators are numeric or alphabetic.
PSTXPRT.DAT文件格式
FILE_TYPE = EXPANDEDPARTLIST;
DIRECTIVES
PST_VERSION='PST_HDL_CENTRIC_VERSION_0';
ROOT_DRAWING = 'Root schematic folder of design' ;
POST_TIME = 'Date and Time of Netlist' ;
SOURCE_TOOL='Capture_Writer';
END_DIRECTIVES ;
PART_NAME
Part Reference ’PART NAME’;
ComponentInstanceProperty='occurence_value';
.
.
SECTION_NUMBER #
'Canonical path',
'Physical path',
Part(function) property='occurrence_value',
.
.
.
PRIM_FILE='.\pstchip.dat',
SECTION='designator';
END.
