Before Next Index

2. Questions about resource files

1. I want to change the first characters of references that are automatically added.



The start characters of automatically added references are determined by the function type of the component cell.
The start characters for each function type are defined in

$ZDSROOT/etc/CompKind (function type definition file)

To change the first letter of the reference to be automatically added, edit the setting of reference header of "ComponentKind3".

The contents you will have edited in this file are not reflected in the references of the symbols that have already been inputted.
Regenerate a reference to reflect in the references of the symbols that have already been inputted.

sNetNameHeader : SIGN # netName Header
bNetNameHeader : B # busName Header
#
# default reference header
#
dBlockRefheader : X # block
dSymbolRefheader : IC # component
###############################################################################
# function table
###############################################################################
ComponentKind 3 {
#
# System functions
#
# Function No. Display strings reference header
0 "DEFAULT LOGIC" IC
1 "JUMPER" J
12 "POWER BOX" IC
13 "VOLTAGE PROBE" PROBE
14 "NODESET" NODESET
15 "ANALYSIS" ANALYSIS
31 "RESISTOR -R" R
32 "CAPACITOR -C" C
33 "INDUCTOR -L" L




2. I want to add or change property items in which symbols and pins can be defined.


Property items are defined in the property definitions file named "$ZDSROOT/etc/jpn/PropSpec."
This file contains system-reserved properties and user-defined properties. It is only the user-defined properties that can added or changed as desired by the user. Edit this part of the file. Add or edit UserComponents in PropSpec Editor.

The section names of user definition properties begin with the characters User.

PropSpec editor can be used under versions subsequent to Rev.6.0.
If you want to use System Designer under a version previous to Rev.5.0, edit the following user definition part of PropSpec using vi editor and other text editor such as word pad.

PropSpec
# ZUKEN CR5000 systems. Resource declaration.
# Resource version:2.100
# Japanese coding:sjis
#############################################################
#Schooling Rev5.0
#############################################################
#
# CR-5000 Design Station Property Specification File
#
# Defined above are the system-reserved properties.
#
#############################################################
# User-defined properties
#############################################################

UserComponent{
# Properties to be attached to components
# Example
# (_price int "Price" ON CIRC -1)
( PCMAC1 text "PWS PCMACRO NO 1" ON CIRC -1)
( PCMAC2 text "PWS PCMACRO NO 2" ON CIRC -1)
( PCMAC3 text "PWS PCMACRO NO 3" ON CIRC -1)
( PCMAC4 text "PWS PCMACRO NO 4" ON CIRC -1)
( PCMAC5 text "PWS PCMACRO NO 5" ON CIRC -1)
( Maker text "Manufacturer" ON CIRC -1)
( Partskind text "Partskind" ON CIRC -1)
}

UserNet {
# Properties attached to nets
}




3. I want to change the system-reserved properties.



The system-reserved properties are important information provided for use by System Designer in various tools and programs. They are also used when exchanging data with PWS, Board Designer, and other software.

Accordingly, with a few exceptions, the reserved properties for the system cannot be changed.

As exceptions, the property display strings and the viewer color numbers can be changed. (The display strings are those in the third field that are enclosed with quotation marks. The viewer color numbers are the numerals in the last field.) Note that user-defined properties are available. The user can add these or change them freely as desired.



PropSpec
##################################################################
#
# CR-5000 Design Station Property Specification File
#
# Copyright (c) 1991,1992 ZUKEN Incorporated, Japan
# ZUKEN Incorporated, R&D Division,Yokohama,Japan.
#
# $Header: PropSpec,v 1.29 95/04/13 17:26:43 inaishi Exp $
#
###############################################################

###############################################################
# System-reserved properties
###############################################################
# One record consists of the following items:
|
$Sheet {
( author text "Circuit creator" ON -1)
( date text "Date created" ON -1)
( comment text "Comment" ON -1)
( defaultPower text "Default power supply" ON -1)
( defaultGround text "Default ground" ON -1)
( partName text "Part name" ON -1)
( $RefTable "UserCircSheet")
}
|



4. I want to know which resource files are referenced when placing parts in the schematic. I also want to know what these files are used for.



When searching the input part library for parts, the properties of the parts registered in the LCDB (parts info library for schematic design) and the search conditions stored in $ZDSROOT/info/srchprts.rsc (part placement tool resource file) are referenced.

Furthermore, settings in the Parts Rule Based Search dialog box that is brought up when selecting a part from the searched parts by a Parts Rule Based Search are loaded from $ZDSROOT/info/pruledb.rsc (Parts Search Rule file).
The pruledb.rsc can be divided into files that are referenced for each schematic. In this case, they are set in rcpath of pruledb.rsc to refer (resource path file).

1. Set properties for parts in the LCDB.

All properties must be set in PropSpec.

Using under Rev.5.0 or earlier open PropSpec with a text editor and confirm.

PropSpec
#
UserComponent{
# Properties attached to components
# Example
# (_price int "Price" ON CIRC -1)
( PCMAC1 text "PWS PCMACRO NO 1" ON CIRC -1)
( PCMAC2 text "PWS PCMACRO NO 2" ON CIRC -1)
( PCMAC3 text "PWS PCMACRO NO 3" ON CIRC -1)
( PCMAC4 text "PWS PCMACRO NO 4" ON CIRC -1)
( PCMAC5 text "PWS PCMACRO NO 5" ON CIRC -1)
( Maker text "Manufacturer" ON CIRC -1)
( search-code text "Partskind" ON CIRC -1)

2. Write the property that serves as the search key, FirstSearchKey, in srchprts.rsc. (In the example below, the property "search-code" is used as the keyword when searching for parts.)

###################################################################
## Defined below are the simplified search resources for component placement tools.
## All search methods during part placement are defined here.
## ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
##
FirstSearchKey : ( serch-code 12 12 1 "IC" "CAPACITOR" "CONNECTOR" "RESISTOR" "other" )

#FirstSearchKey : ( partName 12 12 1 "uPD*" "ECU-*" "ER*" "*")
#
# Specify a property name that serves as the first search key in the component library
# of the symbol search panel. This property name must be
# one of the properties registered in &LanLCDB.
# The key is defined in the same way as for [case B] in MemoLayout.
#


SecondarySearchKeys {

-There is no specific limit to the number of items set in FirstSearchKey (e.g., IC, CAPACITOR, CONNECTOR, etc. in the above example).
-You can further define search keys under SecondarySearchKeys. In this way, you can combine search conditions with FirstSearchKey so that parts can be searched in stages.

3. Enter the settings in pruledb.rsc needed to select parts using the Parts Rule Based Search dialog box.
(Define the contents displayed in this dialog box for each function type.)
pruledb.rsc
-1
( "partName" )
( "*" )
0
( "partName" "area" "Maker" )
( "*" "*" "*" )
31

( "partName" "value" "tolerance" "Maker" )
( "*" "*" ""5%" "*" )
( "*" "*" ""10%" "*" )
( "*" "*" "" "*" )
32
( "partName" "value" "tolerance" "Maker" )
( "*" "*" ""5%" "*" )
#
# For symbols that do not have any of the function types defined here,
# a default value of -1 is used.
# Never delete the items written here.
# ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
# If default values cannot be found, operation will be unstable.

	
CR-5000 System Designer Operation Guide -MASTER-
Chapter2. Resource Files that should be costomized 2-6 "srchprts.rsc" , 2-7 "pruledb.rsc"

When all preparations above are done, you are ready to place parts in schematics.

Shown below is the procedure for placing parts in schematics.

Specify the search keyword.

Set "IC" for the part property
"Partskind" then execute the search.

Choose one of the searched parts and specify a symbol.




5. I want to restore data from log files.


All work you have done in the Sheet Editor is recorded in the files $HOME/cr5000/ds/log/lgaXXXX or lgbXXXX.
If a session has terminated abnormally, you can restore data by reexecuting this log file.

1. Copy the log file (e.g., lga10659) to a macro file (any file name is OK provided that the extension is ".mac"; for example, tmp.mac).

2. Using the Sheet Editor, open the schematic sheet you were editing when a session terminated abnormally.
(If terminated abnormally, the schematic sheet being edited is saved in the name "XXX.sht." This version is opened when you open the schematic next time.)

3. Choose [Utilities] - [Macro File] - [Edit Macro] from the menu bar.

4. Edit the macro file. Delete unnecessary contents.

#
# This command log file was written by ZUken
#
( open sheetname:"/users/lesson2/es10.cir/001.
( select sform:-159600,556400 to:737100,-6500
( cut )
:
:
( save update)
( move action:36500,27000 action:38500,27500
( select sfrom:-3288,46306 to:92338,8905 )
:
( undo )
( zoom all )
( zoom action:76680,36120 action:86280,23880
( select action:80133,28984 )
( move action:80000,29000 ccancel )
( select none )
( select focus:"sNetSeg" action:81008,29030 )
( cut

  • Since the contents, from the beginning to the last line saved, are reflected in the schematic sheet, delete them from the macro file.
    (By searching for the character string "save" you can find the last line where the save command was executed.))

  • The command that caused the session to terminate abnormally may have been written at the end of the log file. Delete this part.

5. Execute the macro file you edited to restore data.
Click [Save/Execute] in the Edit/Execute Macro dialog box.
An operation log is executed for the schematic sheet that is open.



6. I wish to edit the function type definition file (CompKind).


In the function type definition file (CompKind), a total of 256 types of set up are available, for system settings 0 to 100 and user settings 101 to 255. Changes of this file are subject to the following limitations:

Before Next Index