57. When making a command input, I want to change the default option.
Edit the Environment resource file (lanenv.rsc).
On the File manager, Double-click on the lanenv.res file to open the Environment Resource Editor.
Click on the [Command Default] icon and change the settings for each command as necessary.
Only the user like the "System Administrator", who has a write permission can change the settings for the master resource file, '$ZDSROOT/info/lanenv.rsc'.
58. The connector location for the sheet connector has gotten too long.
I want to make a carriage return.
When executing the Cross Reference, specify the [Max string length],
or make a carriage return in the "Change Attribute" Dialog.
Minimum number of characters will be the number of characters usable in case of a single connection in each output mode.
(In other words, in the mode where output is 002:A1, setting in less than 6 characters is not valid. )
59. I want to extend the end point of the bus beyond the the point where the net is connected.
Select [Place]-[Bus] and indicate [Auto-connect] in Right-click, then add an additional bus line at the end point of the existing bus.
The Bus Label will be set to that of the existing bus automatically.
Depending on the settings of [Enter Net] in the Command Default (defined in "Environment Resource" file), the operation may be different.
60. On the Circuit, I want to prohibit some of the component properties from editing.
In $ZDSROOT/etc/PropSpec, change the description of [LCDB Reference] to "CIRCUNEDIT". This will make it impossible to copy the LCDB settings at inputting component and to change the properties in the Schematic Editor.
Editing of PropSpec varies with each version.
Activate PropSpec editor from CR-5000 Design File Manager and proceed with editing on the editor.
61. I do not know how to use the short symbol.
The short symbol is used to put a Net Label as a component somewhere on the net.
To insert a short symbol, set Component type to [Short] and set ON the property [Accept Net?] of the pin connected
to the net which is output to the netlist.
62. Cannot find parts by using a wildcard "*".
1. For properties of text type:
2. For properties of float/int type:
"*" cannot be used. Instead, you can do range search.
For example, "1000<1000000" can be expressed as "1k<1M".
3. You can proceed with And/Or search within the same property.
(Example)
Since 2-byte characters are not allowed in properties reserved for the system, fonts allocated to special characters are used to display such symbols.
64. Will the display speed slow down when hatching is used frequently?
The display speed is not supposed to slow down when there is an increase amounts of hatching.
However, frequent use of hatching increases the amount of redraws, thus the display speed slows down.
65. What happens when you attempt to reference the fourth or later data by referencing a data resource having only up to third data.
Nothing is displayed on the Editor.
66. Is it possible for a figure to be chipped by restrictions on a displayed object (narrow pitch, many nodes, etc.).
There is no specific problem if a figure has about 200 nodes.
If the pitch is too narrow, it may look like paint.
67. Search Parts Num. in a Parts Rule Based Search becomes 0.
Although Search Parts Num. are supposed to be indicated according to specifications, parts that are registered in LCDB are imported using the CDB name as the key when components are placed. Since CDB names identify parts, there are no identical CDB names in LCDB. Thus the Search Parts Num. is limited to 1 when components are placed.
When placed parts are selected to display them in a "Parts Rule Based Search" dialog, entered properties and symbol file names are used as keys in searching LCDB.
The following are probable causes of the Search Parts Num. becoming 0.
*You may be searching for the wrong condition, so try changing the condition of Parts Rule Based Search.
*The part or the property that is the keyword of the rule search condition may not be registered in LCDB. Check.
*The LCDB path cannot be referenced either because it is not set using the Components Library Path of landata.rsc (Data Resource File) or is incorrectly set. Check.
68. The following message appears when a schematic sheet is opened. "Please see (log/upsmb001.log) for checking updated symbols ".
Schematic sheets store the update record of the referenced symbol files internally.
When a schematic sheet is opened, it checks the update record of the symbol file. If this information differs from information in the schematic sheet, a "upsmbXXX.log" file is generated and a message is displayed.
This message is not displayed if "Reload Symbol Figure" is performed.
It is recommended to check what symbol figures deviate from the update clock kept by the schematic sheet before reloading.
Do as shown below to check updated symbols.
1. Click [Utility] a [Open/Save Log Check] in the schematic sheet editor.
2. The content of the log file output when the sheet is opened can now be viewed in the dialog. You can locate its place in the schematic sheet by clicking the updated symbol figure in the list.
3. Click [swapSymbol] in step 2 to perform "Reload Symbol Figure" for the selected symbol figure.
Clicking [swapSymbol All] allows you to perform "Reload Symbol Figure" for all updated symbol figures.
@@
The log files are named as follows.
001.sht...upsmb001.log
002.sht...upsmb002.log
:
The files are generated not for each symbol but when a schematic sheet is opened.
(Even if symbols 002.sht are edited when only 001.sht is opened, "upsmb002.log" is not generated.)