<New features - Cover>
<Top of Section>
<Back>
<Next>
System Designer Rev.7.0 Latest information
Chapter 4. Improvements in utility functions
Net List Function Improvements
- It is now possible to control errors and warnings output when there are no parts in LCDB (or when no LCDB is present) when outputting "Board Designer Net List And Design Rule (ndf/ruf)" from the Net List Processor.
Component Browser
- Auto Parts and Search Parts List functions have been added to the Component Browser.
Multiple search parts also appear in the component property and use of Auto Parts is enabled.
This function makes it possible to check how many parts there are in each component and select desired parts from them.
Circuit Reference Allocator (Function for setting re-used references)
- When the "Circuit Reference Allocator" is used for circuits for which "Set Re-used Reference" has been set, the selected property can be assigned to a reference to support divert design.
Sheet Reference Generator
- -Overall sheet report
- Reports the use of references for all sheets in a System Designer Circuit Directory.
- -Gate handling
- Reference generation can now process gates.
Multiple parts in a sheet that share the same gate have been assigned as the same part and allocated the same reference according to the number of LCDB gates.
Improvements in Rule Checker function
- The Rule Checker function has been improved to make it easier to use.
- Check item settings have been grouped by check objectives.
- LCDB and ERC related check functions have been improved.
- Setting items and output image are now clearly identified.
- The relationship between Output net list and other tools has been improved.
- Resource files that specifies the checks required by each stage of operation have been provided.
- It is now possible to perform checks by Design Variation for schematics with destinations set.
- Check items have been added.
DCF Back Annotation
- From Rev. 7.0, the Back Annotation used between the System Designer and Board Designer now comes in the (.dcf) file format and not as a (.bif) file.
- (.dcf) files has a simpler format than (.bif) files and since they contain only the changes that have been made, there is no need to extract the changes after performing back annotation.
The simple format of the (.dcf) files makes it possible to easily handle back annotation from other systems such as Hot-Stage.
- *For the sake of backward compatibility, the new version can also handle (.bif) file back annotations used in Rev. 6.0 and earlier versions
 |
<New features - Cover>
<Top of Section>
<Back>
<Next>