Bartels AutoEngineer®
Version 3.4
Release Notes

Contents

1.1

Bartels AutoEngineer Product Line

1.2

Hardware and Operating System Platforms

1.3

Documentation

1.4

Installing on PC Platforms

1.5

Installing on UNIX Platforms

1.6

Maximum Path/File Name Length

1.7

Popup Menus

1.8

Automatic Design Data Backup

1.9

Automatic Parameter Backup

1.10

Screen Display of arc-shaped Polygons

1.11

ATI Mach 64 Graphic Device Drivers

1.12

PC Temporary Directory Environment Variable

1.13

Arbitrary Attributes in BAE Entry/Educate

1.14

Libraries

2.1

General

2.2

Automatic Parameter Backup

2.3

Part Naming

2.4

Signal Routing

2.5

Group Functions

2.6

Generic Output under Windows

3.1

Abort Hotkey

4.1

General

4.2

Automatic Parameter Backup

4.3

Part Placement, Part Naming

4.4

Traces on Part Level

4.5

Group Functions

4.6

Batch Design Rule Check

5.1

General

5.2

Automatic Parameter Backup

5.3

Manual Part Placement, Part Naming

5.4

Automatic Copper Fill

6.1

General

6.2

Re-Entrant Routing

6.3

Neural Autorouter

7.1

General

7.2

Automatic Parameter Backup

7.3

Multilayer Plots

7.4

Generic Output under Windows

8.1

General

8.2

Data Management

8.3

Drilling and Milling Data

8.4

Parameters

10.1

BSETUP -- Bartels AutoEngineer Setup Utility

10.2

COPYDDB -- Copy Design Database Utility Library

10.3

INSTALL -- Bartels AutoEngineer Installation Utility

10.4

LISTDDB -- List Design Database Utility Library

10.5

RULECOMP -- Bartels Rule System Compiler

10.6

VALCONV -- VALID to Bartels Conversion

11.1

General

11.2

User Language Compiler

11.3

User Language Interpreter

11.4

Index Variable Types

11.5

System Functions

11.6

BAE User Language Programs

1

BAE Hardware and Operating System Platforms

2

BAE PC Software Install Media

3

BAE PC Disk Space Requirements

4

BAE PC Software License Files

5

BAE Graphic Device Drivers

6

BAE Symbol and Part Libraries

1 General

1.1 Bartels AutoEngineer Product Line

With Bartels AutoEngineer Version 3.4 the following software configurations are available:

• Bartels AutoEngineer Professional
• Bartels AutoEngineer HighEnd
• Bartels AutoEngineer Educate/Entry

Bartels AutoEngineer Professional is the basic BAE software configuration. BAE Professional is available for PCs with Windows or DOS operating systems. SCM and/or Layout only configurations of BAE Professional are provided to satisfy special customer needs. BAE Demo software configurations of BAE Professional (fully-featured except for data output) are also available for test and evaluation purposes.

Bartels AutoEngineer HighEnd with its advanced features and functions such as high speed kernel, cross-probing, rule-driven Neural Autorouter, etc. is available for workstations only.

Bartels AutoEngineer Educate (also known as Bartels AutoEngineer Entry) is available for PCs with Windows or DOS operating systems. BAE Educate is a low-price BAE configuration with considerably reduced functionality for educational purposes and/or semi-professional users.

The following software modules are optionally available with the workstation-based BAE systems:

• Bartels AutoEngineer IC Design
• Bartels AutoEngineer Mixed Mode Simulator

Bartels AutoEngineer IC Design (BAEICD) is a complete CAD/CAM system for the physical design of integrated circuits (gate arrays, standard cells, custom ICs and/or ASICs). BAEICD consists of a series of system components such as IC Mask Editor, IC Autoplacement, IC Autorouter, IC DRC (Design Rule Check), and GDS-II and CIF standard interfaces.

Bartels AutoEngineer Mixed Mode Simulator (BAESIM) is a compiler-driven simulator for mixed analog/digital circuits. BAESIM provides direct access to the netlist data generated with the Schematic Editor of the Bartels AutoEngineer.

1.2 Hardware and Operating System Platforms

With Bartels AutoEngineer Version 3.4 the BAE Professional and BAE Educate/Entry software versions have been ported to Windows, and the BAE HighEnd software versions have been ported to OSF/Motif. I.e., BAE Professional and BAE Educate/Entry are now available for Windows NT 4.0, Windows NT 3.51, Windows 95, Windows 3.x, and OS/2 Warp (with WIN-OS/2 support), and BAE HighEnd is now available for DEC OSF/Motif, HP-UX OSF/Motif, and Solaris. BAE Windows and BAE Motif versions may be operated with either BAE standard user interface (with side menu) or with Windows pulldown menus.

The windows versions of the BAE software are generated with the Watcom 32-bit Windows-extender, and thus may be used under Windows NT, Windows 95, Windows 3.x, or OS/2 Warp (with WIN-OS/2). With the DOS versions of the BAE software either MS-DOS, OS/2 (DOS Full Screen), or Windows (DOS Box, Enhanced Mode) operating system is required, and the software is running in Protected Mode for optimized memory access. This allows for the design of very large boards since there are no software imposed limits, i.e. the system is limited just by the available amount of memory.

The workstation-based software of the Bartels AutoEngineer is available on computer systems of Digital Equipment (DEC 3000 AXP Alpha, DECstation), Sun Microsystems (SPARCstation), and Hewlett Packard (HP 9000/700 series). The workstation operating systems supported by the Bartels AutoEngineer are DECwindows (with OSF/Motif and/or) on DEC Alpha, ULTRIX (with DECwindows) on DECstation, Solaris (with OSF/Motif and/or X11) and/or SunOS (with SunView) on SPARCstation, and HP-UX (with OSF/Motif and/or X11) on HP 9000/700.

Table 1 lists the Bartels AutoEngineer Version 3.4 hardware and operating system platforms.

Table 1: BAE Hardware and Operating System Platforms

1.3 Documentation

Both the Bartels AutoEngineer® - User Manual and the Bartels User Language - Programmer's Guide have been completely revised and converted to HTML format.

1.4 Installing on PC Platforms

Install Kit

The Bartels AutoEngineer PC software is shipped either with CD-ROM or with the floppy disks listed in table 2. The BAE software files contained on the install media are stored in compressed format.

Table 2: BAE PC Software Install Media

Disk Space Requirements

Four different directory path names can be choosen for installing the BAE programs, the BAE libraries, the BAE User Language sources, and the BAE test jobs and examples, respectively. Any of these directories not yet existing will be created automatically with user verification. When installing from CD-ROM, you may optionally copy the BAE online documentation (format HTML 3.0) to your hard disk. The CD-ROM also contains extensive digital libraries, which are not provided with the floppy install media. Make sure there is enough hard disk space available for the installation; see table 3 for the corresponding disk space requirements. Some major changes have been introduced to the User Language include files of BAE Version 3.4. It is recommended to use a new baeulc directory (or save the existing one) when performing an Update installation (see below), or otherwise there might be problems when trying to re-compile existing (customer-specific) User Language programs referring to the supplied include files.

Table 3: BAE PC Disk Space Requirements

Install Program

With the BAE install kit (CD-ROM or Floppy Disk 1) the BAE install program named install is provided. This program is the one and only tool feasable for performing a correct installation on PC platforms since the BAE PC software files are stored in compressed format on the disks of the BAE install kit. Note that the install program has been considerably changed to support BAE software installation on different operating systems.

For installing the BAE software, either the CD-ROM must be inserted to the CD-ROM drive and/or floppy disk 1 of the install kit must be inserted to the floppy drive, and the drive and directory must be set accordingly. E.g., if you intend to install the BAE software from CD-ROM drive D, then insert the BAE CD-ROM to CD-ROM drive D, and enter the following commands to the DOS prompt:

>  D:  
>  install 

Once the install program has been started, the instructions issued on the screen should be followed carefully. The dialogue of the install program strongly depends on the contents of the install media. When installing from CD-ROM, you will be asked for the BAE language version (e.g. English, German, etc.) and for the operating system host platform (DOS, Windows NT, Windows 3.x, etc.). When installing from floppy disks you must mount the correct floppy disks (to be recognized by labels) rather than to select the desired operating system platform.

The install program provides different modes for performing either new Installation or Update installations. The Update install mode is strongly recommeded when just updating from earlier BAE Versions; this will prevent the install program from overwriting special BAE system and setup files ending on .dat, .def, and .fnt (otherwise user-defined colour tables, aperture tables, fonts, layer definitions, library access path settings, and menu setups stored with these files might get lost).

After selecting the install mode, the user will be prompted for the destination directories for installing the programs, the libraries, the User Language source files, and the examples and test jobs. The user may exclude certain destination directories by deleting the corresponding path names. More experienced BAE users may, e.g., suppress the installation of the BAE example jobs, or re-install certain parts of the BAE software lateron. For security reasons the install parameter settings will be verified with user query before starting the installation process. The destination directories will be created automatically on request. The install program decompresses the BAE software files and copies them to the corresponding destination directories on the hard disk. When installing from floppy drive, the user will be prompted to insert the required floppy disks, and the installation process continues until all disks are correctly installed.

At the end of the install process the install program asks for the licensed BAE software configuration to install the correct software authorization file (see below). When installing the DOS version, the user will also be asked to select the graphic device driver to be installed (see below).

Installing the Software Security Module

The BAE PC software (except for the Demo software configuration) is protected by a hardlock key (dangle) which must be plugged onto one of the parallel ports (LPT1, LPT2, or LPT3) of your PC. Switch off your computer before mounting the hardlock key shipped with the software, or otherwise the dangle might be damaged by high voltage! If you have connected a peripheral device such as a laser printer to the hardlock key, then you must always switch on the peripheral device before switching on your computer to ensure correct hardware authorization check.

The BAE PC software provides the license files according to the available software configurations as shown in table 4. You will be asked to select the BAE software configuration (and thus the appropriate license file) when installing the BAE software. Make sure to select the BAE software configuration to be installed and/or authorized on your computer.

Table 4: BAE PC Software License Files

The license file matching the BAE software configuration authorized on your computer must be available under file name router.cfg in the BAE programs directory. I.e., to install the correct license file you may also copy the desired CFG file to router.cfg in the BAE programs directory, instead of selecting the valid BAE configuration during BAE software installation. E.g., for authorizing the Demo software configuration you have to issue the following copy command (assume BAE programs directoy c:\bae):

>  copy c:\bae\demo.cfg c:\bae\router.cfg 

Note that the BAE Demo software configuration is the one and only to run without a hardlock key, since BAE Demo software is intended for evaluation purposes only. Note also that you cannot produce any CAM or User Language output with the Demo software, and that BAE Demo software masks each processed SCM and/or Layout plan element to prevent from processing with productive software configurations afterwards. I.e. the BAE user version is not able to read Demo jobs, however we are able to convert these jobs.

Windows NT Hardlock Key Check Driver

Special driver software is required for hardlock key check when running the BAE Windows and/or DOS software under Windows NT. To install this driver software simply issue the following command from the BAE programs directory (system administrator rights are required):

> hlinst . 

Ensure that "Boot Device" is selected with the Startup option of the Hardlock hardware device to be configured from the Hardware Devices dialog of the System Control panel. Note that the system must be re-booted after successfully installing the Windows NT hardlock key check driver software.

Selecting the BAE DOS Graphic Device Driver

With the Windows versions of the BAE software there is no BAE graphic device driver installation required, since BAE Windows software runs under the graphic interface of the corresponding operating system.

The DOS versions of the BAE software are shipped with a series of graphic device drivers. With BAE Version 3.4 PC software, new graphic device drivers have been developed supporting the ATI Mach64 graphic adapter (resolutions 1024*768, 1280*1024, and 1600*1200). You are asked to select an appropriate BAE graphic device driver when installing BAE DOS software. Table 5 provides the list of graphic device drivers supplied with the DOS PC software of the Bartels AutoEngineer. Please select the graphic device driver matching the video adapter and/or graphic card installed with your computer. It is recommended to install the standard VGA driver VGA480, if you are not sure about which driver to select, since VGA480 is assumed to run on almost any PC system, and you can always select a different driver (e.g. with higher resolution) lateron (see below).

Table 5: BAE Graphic Device Drivers

The graphic driver file (DEV file) matching the video adapter and/or graphic card of your computer must be available under file name bae.dev in the BAE programs directory. I.e., to install the correct graphic driver DEV file, you may copy the desired DEV file to bae.dev in the BAE programs directory (instead of selecting the correct driver during BAE software installation). E.g., for installing the VESA driver for 600*800 resolution you have to issue the following copy command (assume BAE programs directory c:\bae):

>  copy c:\bae\vesa600.dev c:\bae\bae.dev 

Installing a Pointing Device

A Microsoft-compatible three (or at least two) button mouse (e.g. Logitech, Genius, Dexxa, etc.) with corresponding mouse driver software is required for the control of Bartels AutoEngineer. Consult the documentation shipped with your mouse for information on how to connect the mouse and how to install the mouse driver software. Alternatively a compatible trackball and/or touchpad pointing device may be used instead of a mouse.

Setting up the DOS Environment

It is recommended to add the BAE programs directory path to the PATH environment variable. Load the autoexec.bat file to your text editor and check whether autoexec.bat contains a PATH statement or not. If there is already a PATH statement defined in autoexec.bat, then just add the following program path link to the PATH statement (assume BAE programs directory c:\bae):

;c:\bae

If there is no PATH statement defined in autoexec.bat, then insert the following PATH statement (assume BAE programs directory c:\bae):

PATH=c:\bae

You can also insert the following command at the end of the autoexec.bat file to include the BAE programs directory pathname with the PATH variable:

PATH c:\bae;%path%

With the PC versions of the BAE software an environment variable called BAETMP can be defined for optionally specifying a BAE temporary directory to avoid problems with temporary file generation on network-based PC/MS-DOS systems. To specify the BAE temporary directory the following command must be added to the autoexec.bat file:

SET BAETMP=<dirpath>\

<dirpath> is the path name of the temporary directory (e.g., d:\baetmp; the backslash at the end of the path name is required).

The config.sys file must contain the following statements:

BUFFERS=<b>
FILES=<f>

The number <b> of buffers should be at least 30, and the number <f> of files should be at least 20.

On 386, 486, Pentium, and Pentium Pro computers, the BAE DOS software works in Protected Mode, i.e. there is no 640 kByte barrier. Bartels AutoEngineer uses the Phar Lap 386|DOS Extender, which supports DPMI, VCPI, EMM386, XMS/HIMEM, VDISK, and INT 15h. However in special cases (e.g. with certain third party software configurations) it might be necessary to remove conflicting memory managers. If you wish to restrict the way in which BAE uses memory it is possible to reconfigure the BAE programs; please contact us for more detailed information in case. With EMM386 installed under MS-DOS 6.x it is strongly recommended to add the NOVCPI switch (and the NOEMS switch) to the corresponding config.sys line, since otherwise the performance for starting BAE graphic program modules will dramatically slow down.

BAE Setup

With the BAE software a setup definitions file template named stdset.def is supplied, which will be installed to the BAE programs directory. This file contains the following commands for setting the BAE library access paths:

SCMDEFLIBRARY ("<libdir>\stdsym");
LAYDEFLIBRARY ("<libdir>\laylib");

where <libdir> is the path name of the BAE library directory. If the library e.g. has been installed to the directory c:\baelib then you should replace <libdir> with this path name to provide correct access to the BAE symbol libraries.

The setup definitions file can be transferred to the BAE setup file bsetup.dat with the following bsetup program call (assume stdset.def to be the name of the setup definitions file, and BAE programs directory to be the working directory):

> bsetup stdset 

The bsetup utility program is also used for defining important system parameters such as the documentary layer definitions and the menu setup. It is strongly recommended to become familiar with the features of the bsetup utility program before using BAE for the design of real layouts. See Bartels AutoEngineer User Manual - Chapter 7 for details on how to use bsetup.

User Language Programs, Menu Assignments, Key Bindings

A lot of very useful User Language programs are supplied with the BAE software software. The corresponding source files will be installed to a special baeulc directory (see above). It is strongly recommended to install and compile the User Language programs, since these programs provide a wide range of additional BAE features. The baeulc directory contains batch files for automatic compilation of all of the delivered User Language programs. Some of these programs will define implicit User Language program calls, i.e. menu assignments, key bindings, and startups. The supplied startup programs will also apply User Language system functions for performing key programming and assigning menu definitions. Please consider that pre-defined key bindings and AutoEngineer menu definitions will be changed when running the compile batch file and/or (automatically) executing the User Language startup programs. For executing the compile batch file you have to move to the baeulc directory. We recommend the CPLSLL (ComPiLe with Static Link Library) compile batch file for compiling the BAE User Language programs. The DOS command for starting this batch file is:

> cplsll 

The compilation process might last some time (according to the power of your computer). After successfully processing the compile batch file, all of the User Language programs supplied with the BAE software are available.

See Bartels User Language Programmer's Guide - Chapter 4.2 for a complete listing of the User Language programs supplied with the Bartels AutoEngineer. See Bartels User Language Programmer's Guide - Chapter 4.3 or section 11.6 of these Release Notes for more detailed information on how to compile the BAE User Language programs and on how to define menu assignments and key bindings.

Starting BAE

Note that you must reboot your computer if you made any changes to the config.sys or autoexec.bat file during installation. The Bartels AutoEngineer can then be started by typing

> bae 

to the DOS prompt. It is recommended to start BAE from the directory where the design files should be generated (this considerably simplifies job file access).

In Windows, the Bartels AutoEngineer can be started by selecting the bae.exe file using the Run function from the Program Manager Files menu. Windows-based operating systems also allow for application startup by clicking onto the icon of the corresponding program file (or by clicking onto a Windows PIF file previously generated for this application). Note that startup icons and/or PIF files also allow for the definition of the directory to be entered on default when starting the corresponding application, i.e. BAE may be configured to be started from the BAE jobs directory or from any user-specific BAE project directory. A reference of the BAE startup icon may be included with the operating system launchpad to provide an even more convenient method of starting up the Bartels AutoEngineer. Consult the documentation of your operating system for more details on how to configure applications for startup.

1.5 Installing on UNIX Platforms

Install Kit

The Bartels AutoEngineer install kit for UNIX operated workstations consists of a tape archive (install media) containing the directories bin (programs and setup files), lib (symbol and part libraries), ulc (User Language source files) and jobs (examples and test jobs).

Preparing for Update Installations

You should save the files with the extensions .dat, .def and .fnt from your BAE programs directory if you are just updating from earlier BAE versions (otherwise user-defined color tables, layer definitions, Gerber aperture tables, and fonts stored with these files might get lost). Some major changes have been introduced to the User Language include files of BAE Version 3.4. It is recommended to save the contents of the existing ulc directory when performing an Update installation, since otherwise there might be problems when trying to re-compile existing (customer-specific) User Language programs referring to the supplied include files.

Installing the BAE Software

For installing the software in a user's home directory the user has to type in

>  cd $HOME  
>  tar xv 

to the UNIX shell prompt after mounting the install media. A system-wide installation for multiple user access can be achieved by creating a BAE system directory (e.g. /usr/bae) and restoring the install media contents to this directory as in

>  mkdir /usr/bae  
>  cd /usr/bae  
>  tar xv 

Setting up the UNIX Environment

The access rights must be set properly (i.e. execute for the programs, read access to the libraries, read/write access to the job files, all rights for the system administrator, special rights for the library manager, etc.). Within the BAE programs directory the user must have read access to the files ending on .cfg (for authorization check) and read/write access to the files with extensions .dat and .fnt. When working with BAE, the user must also have write access in the current directory to enable temporary file creation.

To enable BAE program call from any directory the UNIX shell environment variable PATH must be set to the BAE programs directory; this can automatically be done on shell profile execution, i.e., through shell script .profile, .login, or .cshrc (according to UNIX derivate, respectively).

BAE Setup

With the BAE software a setup definitions file template named stdset.def is supplied, which will be installed to the BAE programs directory. This file contains the following commands for setting the BAE library access paths:

SCMDEFLIBRARY ("<libdir>/stdsym");
LAYDEFLIBRARY ("<libdir>/laylib");

where <libdir> is the path name of the BAE library directory. If the library e.g. has been installed to the directory /usr/bae/lib, then you should insert the following commands to the setup definitions file for providing correct access to the supplied BAE symbol libraries:

SCMDEFLIBRARY ("/usr/bae/lib/stdsym");
LAYDEFLIBRARY ("/usr/bae/lib/laylib");

The setup definitions file can be transferred to the BAE setup file bsetup.dat using the following bsetup program call (assume stdset.def to be the name of the setup definitions file, and BAE programs directory to be the working directory):

> bsetup stdset 

The bsetup utility program is also used for defining important system parameters such as the documentary layer definitions and the menu setup. It is strongly recommended to become familiar with the features of the bsetup utility program before using BAE for the design of real layouts. See Bartels AutoEngineer User Manual - Chapter 7 for details on how to use bsetup.

User Language Programs, Menu Assignments, Key Bindings

A lot of very useful User Language programs are supplied with the BAE software. The corresponding source files will be installed to a special ulc directory (see above). This directory also contains batch files for automatic compilation of all of the delivered User Language programs. Some of these programs will define implicit User Language program calls, i.e. menu assignment, key bindings, and startups. The supplied startup programs will also apply User Language system functions for performing key programming and assigning menu definitions. Please consider that pre-defined key bindings and AutoEngineer menu definitions will be changed when running the compile batch file and/or (automatically) executing the User Language startup programs. For executing the compile batch file you have to move to the ulc directory. We recommend the CPLSLL (ComPiLe with Static Link Library) compile batch file for compiling the BAE User Language programs. The UNIX command for starting this batch file is:

> cplsll.bat 

The compilation process might last some time (according to the power of your computer). After successfully processing the compile batch file, all of the User Language programs supplied with the BAE software are available.

See Bartels User Language Programmer's Guide - Chapter 4.2 for a complete listing of the User Language programs supplied with the Bartels AutoEngineer. See Bartels User Language Programmer's Guide - Chapter 4.3 or section 11.6 of these Release Notes for more detailed information on how to compile the BAE User Language programs and on how to define menu assignments and key bindings.

Starting BAE

The Bartels AutoEngineer can be started after login from a UNIX command shell (under X11 on HP 9000 and DEC Alpha AXP, under DECwindows on DECstation, or under SunView on SPARCstation) by typing

> bae 

to the UNIX shell prompt. To simplify design/job file access, it is recommended to start BAE from the directory where the job files should be generated.

1.6 Maximum Path/File Name Length

With BAE Version 3.4 the maximum path and/or file name length to be evaluated and/or processed by the system has been increased from 40 to 200 characters.

1.7 Popup Menus

A new button named Back has been integrated to the BAE Version 3.4 popup menus for file name selection, element name selection, etc. This button features a page-up function for scrolling back in the current popup menu item list. The Back button has also been integrated to the popup menus of the User Language programs delivered with BAE Version 3.4.

A new button named Dump has been integrated to the report display popup menus of the User Language programs delivered with BAE Version 3.4. This button supports optional output of popup menu contents to file.

1.8 Automatic Design Data Backup

A feature for optionally performing automatic design data backup has been implemented with the Schematic Editor, the Layout Editor, the Autoplacement module, and the Neural Router of BAE Version 3.4. This feature is controlled with the Autosave function from the Parameter menus. The Autosave function requires a positive integer input designating the autosave time interval in minutes. On zero or dash (-) input the automatic save facility will be deactivated. With Autosave activated, the system automatically saves the currently processed element to a backup file at the specified time intervals. The name of the backup file is automatically derived from the current job file name, and will have the extension .bak. Autosaved elements may be restored using features such as the Save Element As function from the Files menu or the copyddb utility program.

1.9 Automatic Parameter Backup

Important design and operational parameters such as autosave time interval, color table name, input and display grid, angle and grid lock, coordinate display mode, standard placement angle and mirror mode, standard text size, library access paths, plot file names, standard trace widths, Mincon function class, airline display mode, placement matrix, copper fill parameters, etc. are automatically saved with the currently processed layout and/or schematic plan or with the processed library hierarchy level (part, padstack, pad, SCM symbol, etc.). When loading an element, the corresponding parameter set is automatically loaded and/or activated as well, thus providing a convenient way of setting up a default design environment suitable for processing the selected database and/or design element.

1.10 Screen Display of arc-shaped Polygons

With BAE Version 3.2 problems occurred in special cases when displaying arc-shaped fill polygons at (very) high zoom factors. The graphic driver routines of BAE Version 3.4 have been improved to fix these problems.

1.11 ATI Mach 64 Graphic Device Drivers

With BAE Professional Version 3.4 PC/MS-DOS software new graphic device drivers for supporting ATI Mach 64 graphic cards with screen resolutions 1024*768 (mach768.dev), 1280*1024 (mach1024.dev) and 1600*1200 (mach1200.dev) are supplied.

1.12 PC Temporary Directory Environment Variable

With PC-based BAE Version 3.4 an environment variable called BAETMP has been defined for optionally specifying a BAE temporary directory to avoid problems with temporary file generation on network-based PC/MS-DOS systems. To specify the BAE temporary directory the following command must be added to the autoexec.bat file:

SET BAETMP=<dirpath>\

<dirpath> is the path name of the temporary directory (the backslash at the end of the path name is required).

Warning

Make sure that the directory specified with the BAETMP environment variable does exist and is accessible by the user (enough free disk space, proper access rights, etc.), or otherwise temporary file creation (and thus design data saving) might fail!

1.13 Arbitrary Attributes in BAE Entry/Educate

Any restrictions regarding attribute definitions have been removed from the BAE Entry/Educate PC software configuration of BAE Version 3.4. I.e., BAE Entry/Educate now allows for the definition and processing of arbitrary part attributes.

1.14 Libraries

The BAE Version 3.4 part and symbol libraries have been revised and supplemented by a series of new symbol and part definitions. Table 6 lists all libraries shipped with BAE Version 3.4.

Table 6: BAE Symbol and Part Libraries

New digital libraries with more than 3800 symbols/parts defined according to IEEE/DIN standards have been designed for BAE Version 3.4.

A lot of very useful User Language programs for library management (such as library check, automatic symbol edit, automatic generation of library documentation, etc.) are provided with BAE Version 3.4. See Bartels User Language Programmer's Guide - Chapter 4 for a complete listing of the User Language programs shipped with the BAE software.

Warning

Please take extreme care when merging information from the new libraries to your existing job files (e.g. with Update Library or copyddb). You should always ensure compatibility of pin mappings, attribute definitions, layer assignments, etc. before merging any library data. For these purposes a series of most useful User Language programs are provided with BAE Version 3.4. Nevertheless we strongly recommend to refrain from updating project-specific libraries if you are unsure about compatibility to the new libraries!

2 Schematic Editor

2.1 General

A new Autosave parameter for optionally performing automatic design data backup at selectable time intervals has been implemented with the Schematic Editor of BAE Version 3.4. For more details see section 1.8 of these Release Notes.

Special case problems regarding the screen display of arc-shaped fill polygons at (very) high zoom factors have been fixed with BAE Version 3.4.

2.2 Automatic Parameter Backup

The Schematic Editor provides an in-built feature for automatically saving important design and operational parameters with the currently processed SCM plan and/or SCM library hierarchy level. The following parameters will be stored to the current design file when activating the Save Element function:

• Autosave Time Interval
• Name of the currently loaded SCM Color Table
• Input Grid
• Display Grid
• Grid/Angle Lock
• Coordinate Display Mode
• Symbol/Label Placement Default Rotation Angle
• Symbol/Label Placement Default Mirror Mode
• Symbol/Label Placement Signal Routing On/Off Mode
• Default Bus Tap Swap Flag
• Default Text Size
• Symbol Library File Name
• Logical Library File Name
• Plot File Name

Parameter sets are stored with special names according to the currently processed SCM database hierarchy level. Parameter set name [plan] is used for SCM plan elements, [symbol] is used for SCM symbol elements, [label] is used for SCM label elements, and [marker] is used for SCM marker elements. When loading an element, the corresponding parameter set is automatically loaded as well, thus providing a convenient way of activating a default parameter set suitable for processing the selected design and/or library element type.

2.3 Part Naming

The built-in part name checking feature applied by the Add Symbol function has been considerably improved to check not only the current SCM plan element but also all other SCM plan elements of the currently processed design for part name uniqueness. If a part name explicitely specified with the Add Symbol function is already used on a different sheet, then the user must confirm to use this part name on the current sheet. Note that the corresponding part will not be deleted automatically from the other sheet (as it would be if it was on the same sheet). I.e., it is up to the user to delete this part lateron to avoid name conflicts on subsequent Packager processes.

2.4 Signal Routing

The signal router, i.e. the automatic connection re-routing feature to be activated when moving symbols and/or labels on SCM plan level has been considerably improved. I.e., the signal router is now able to create Z-shaped connections and to do a better job at the pushing/shoving of connection bunches. Also a new operational SCM parameter has been introduced which allows for the activation and/or deactivation of the signal router. Signal routing can be activated and/or deactivated with the new options Signal Router On and/or Signal Router Off provided with the Move Symbol/Label function submenu to be activated by pressing the right mouse button whilst moving a symbol or label. The selected signal routing mode will also be saved with the currently processed SCM plan (see also section 2.2 of these Release Notes).

Warning

Please note that the signal router should be considered "as-is", i.e. for the moment it is straight-forward designed with the intention to simplify work rather than to provide an academically optimum SCM autorouter solution with a long time-to-application/user period. We are aware of the fact that the signal router may produce unpredictable results (e.g., elimination of connections, insertion of new junction points) in cases where symbol movement might cause net list conflicts. It is recommended to move symbols in a step-by-step approach rather than to move long distances, and to refrain from placing symbols onto each other. You may always use the Undo function and retry in cases where you are not pleased with the result.

2.5 Group Functions

The Schematic Editor Load Group function from the Groups menu has been considerably changed. The new Load Group function first resets the currently defined group to deselect all currently group-selected elements before performing the load operation. After successfully loading a group, all loaded group elements except for the connections (difficult identification due to internal data structures) are automatically group-selected. The advantage of this feature is that loaded group elements (and only these objects) may be subject to subsequent group functions without the need to perform group selection and/or deselection.

2.6 Generic Output under Windows

A new generic print/plot output function has been implemented with the Windows versions of the BAE PC software. I.e., any print/plot output feature supported by the current Windows operating system configuration is also supported with the Schematic Editor of the BAE Windows software. The new Generic Output function from the Plot Output menu can be used to activate the Windows print/plot menu.

3 Packager & Backannotation

3.1 Abort Hotkey

A new feature for aborting Packager and/or Backannotation user queries (i.e. for suppressing annotation startup) by pressing the escape key ESC (ASCII code 27) has been integrated to the user interfaces of the Packager and Backannotation program modules of BAE Version 3.4.

4 Layout Editor

4.1 General

A new Autosave parameter for optionally performing automatic design data backup at selectable time intervals has been implemented with the Layout Editor of BAE Version 3.4. For more details see section 1.8 of these Release Notes.

With BAE Version 3.4 up to 12 menu entries of the Layout Editor signal layer menus may be freely defined with layer number and layer name. See section 10.1 of these Release Notes for more details on how to customize the signal layer menus using the bsetup utility program.

Special case problems regarding the screen display of arc-shaped fill polygons at (very) high zoom factors have been fixed with BAE Version 3.4.

4.2 Automatic Parameter Backup

The Layout Editor provides an in-built feature for automatically saving important design and operational parameters with the currently processed layout and/or part symbol. The following parameters will be stored to the current design file when activating the Save Elemen function:

• Autosave Time Interval
• Name of the currently loaded Layout Color Table
• Input Grid
• Display Grid
• Grid/Angle Lock
• Coordinate Display Mode
• Wide Line Draw Start Width
• Group Display Mode
• Part Placement Default Rotation Angle
• Part Placement Default Mirror Mode
• Default Text Size
• Part Airline Display Mode
• Standard Trace Widths
• Library File Name
• Mincon Function Type

Parameter sets are stored with special names according to the currently processed layout database hierarchy level. The layout element name is used for layout elements, parameter set name [part] is used for layout part symbol elements, [padstack] is used for layout padstack elements, and [pad] is used for layout pad elements. When loading an element, the corresponding parameter set is automatically loaded as well, thus providing a convenient way of activating a default parameter set suitable for processing the selected design and/or library element type.

4.3 Part Placement, Part Naming

With BAE Version 3.4 new popup menus for selecting part names and/or library file and element names have been integrated to the Add Part, Change Part Name and Netlist Part Name functions of the Parts menu. On layout hierarchy level a netlist part name popup menu is activated with the part name prompt. With this popup menu already placed netlist parts are displayed in brackets ([, ]), and unplaced netlist parts are displayed following to a colon (:). When selecting or specifying an unplaced netlist part name, then this part will be loaded for placement. When selecting or specifying an already placed netlist part name, then the corresponding part will only be loaded for placement, if the user confirms to replace the already placed part. Entering an empty string to the part name prompt or selecting the Unplc. button will load the next unplaced netlist part. This feature is also provided with the Place Next Part function and will work until all netlist parts are placed. When specifying a non-netlist part name (i.e., a constructive part by typing in a name not provided with the netlist part name popup), the system additionally prompts for the library element name. Popup menus are provided with the library element name query for selecting the library file and the library element name. Herewith the library file name list is derived from the layout library path defined with the BAE setup, i.e. all DDB files available in the directory of the layout library path are listed. Library elements may optionally be selected by typing both the library file name (i.e. one of the names displayed with the library file name popup), a slash (/), and the library element name to the library element name prompt (typing ? for the element name will activate a popup menu providing the list of library elements from the specified libary file). An empty string input to the library element name query causes the system to use the library element previously selected with the Add Part function (if there was already one specified).

The netlist part name selection popups are also provided with the Change Part Name and Netlist Part Name functions from the Parts menu. The library element name selection of the Add Part function is also implemented for placing pins (i.e. selecting padstacks) on layout part symbol level, and for loading pads onto layout padstack level.

4.4 Traces on Part Level

BAE Version 3.4 allows for the definition of traces and vias on layout part level (e.g. for printed inductors). The corresponding Layout Editor functions (Select Via, Add Trace, etc.), the User Language system functions for placing vias and generating traces, and the User Language programs delivered with the BAE software have been changed accordingly.

4.5 Group Functions

The Layout Editor Load Group function from the Groups menu has been considerably changed. The new Load Group function first resets the currently defined group to deselect all currently group-selected elements before performing the load operation. After successfully loading a group, all loaded group elements are automatically group-selected. The advantage of this feature is that loaded group elements (and only these objects) may be subject to subsequent group functions without the need to perform any group selection and/or deselection.

The Load Group submenu to be activated using the right mouse button whilst placing the loaded group has been extended to comply with the submenus of the Move Group and Copy Group functions. I.e., the Rotate Left, Rotate Right, Set Angle, Mirror Off and Mirror On functions have been added to the Load Group submenu.

4.6 Batch Design Rule Check

With BAE Version 3.4 the Batch-DRC function from the Utilities menu has been changed to activate the Report function (from the Utilities menu) after performing the Batch Design Rule Check. I.e., the design check result is automatically displayed without the need of explicitely activating the Report function.

5 Autoplacement

5.1 General

A new Autosave parameter for optionally performing automatic design data backup at selectable time intervals has been implemented with the Autoplacement module of BAE Version 3.4. For more details see section 1.8 of these Release Notes.

With BAE Version 3.4 up to 12 menu entries of the Autoplacement signal layer menus may be freely defined with layer number and layer name. See section 10.1 of these Release Notes for more details on how to customize the signal layer menus using the bsetup utility program.

Special case problems regarding the screen display of arc-shaped fill polygons at (very) high zoom factors have been fixed with BAE Version 3.4.

5.2 Automatic Parameter Backup

The Autoplacement module provides an in-built feature for automatically saving important design and operational parameters with the currently processed layout and/or part symbol. The following parameters will be stored to the current design file when activating the Save Element function:

• Autosave Time Interval
• Name of the currently loaded Layout Color Table
• Input Grid
• Display Grid
• Grid/Angle Lock
• Coordinate Display Mode
• Wide Line Draw Start Width
• Part Placement Default Rotation Angle
• Part Placement Default Mirror Mode
• Part Airline Display Mode
• Library File Name
• Mincon Function Type
• Placement Matrix
• Placement Matrix Enabled Flag
• Copper Fill Isolation Distance
• Copper Fill Minimum Area Structure Size
• Copper Fill Trace Cutout Mode
• Copper Fill Island Delete Mode
• Copper Fill Heat Trap Mode
• Copper Fill Heat Trap Width
• Hatching Line Spacing
• Hatching Line Width
• Hatching Mode

Parameter sets are stored with special names according to the currently processed layout database hierarchy level. The layout element name is used for layout elements and parameter set name [part] is used for layout part symbol elements. When loading an element, the corresponding parameter set is automatically loaded as well, thus providing a convenient way of activating a default parameter set suitable for processing the selected design and/or library element type.

5.3 Manual Part Placement, Part Naming

With BAE Version 3.4 new popup menus for selecting part names and/or library file and element names have been integrated to the Add Part Change Part Name and Netlist Part Name functions of the Manual Placement menu. On layout hierarchy level a netlist part name popup menu is activated with the part name prompts. With this popup menu already placed netlist parts are displayed in brackets ([, ]), unplaced netlist parts currently selected for placement using the Part Set features are displayed following to a colon (:), and unplaced parts currently not selected for placement are displayed in angle brackets (<, >). When selecting or specifying an unplaced netlist part name, then this part will be loaded for placement. When selecting or specifying an already placed netlist part name, then the corresponding part will only be loaded for placement, if the user confirms to replace the already placed part. Entering an empty string to the part name prompt or selecting the Unplc. will load the next unplaced netlist part selected for placement. This feature is also provided with the Place Next Part function and will work until all netlist parts are placed. When specifying a non-netlist part name (i.e., a constructive part by typing in a name not provided with the netlist part name popup), the system additionally prompts for the library element name. Popup menus are provided with the library element name query for selecting the library file and the library element name. Herewith the library file name list is derived from the layout library path defined with the BAE setup, i.e. all DDB files available in the directory of the layout library path are listed. Library elements may optionally be selected by typing both the library file name (i.e. one of the names displayed with the library file name popup), a slash (/), and the library element name to the library element name prompt (typing ? for the element name will activate a popup menu providing the list of library elements from the specified libary file). An empty string input to the library element name query causes the system to use the library element previously selected with the Add Part function (if there was already one specified).

The netlist part name selection popups are also provided with the Change Part Name and Netlist Part Name functions of the Parts menu. The library element name selection of the Add Part function is also implemented for placing pins (i.e. selecting padstacks) on layout part symbol level.

5.4 Automatic Copper Fill

With BAE Version 3.4 some of the internal copper fill routines have been optimized to avoid unpredictable results in a series of very exotic cases.

6 Autorouter

6.1 General

With BAE Version 3.4 up to 12 menu entries of the Neural Autorouter signal layer menus may be freely defined with layer number and layer name. See section 10.1 of these Release Notes for more details on how to customize the signal layer menus using the bsetup utility program.

The BAE Version 3.4 Autorouter module has been changed to support traces and via processing on layout part level (see also section 4.2 of these Release Notes).

Special case problems regarding the screen display of arc-shaped fill polygons at (very) high zoom factors have been fixed with BAE Version 3.4.

6.2 Re-Entrant Routing

With BAE Version 3.4 Autorouter the Load Layout function for re-loading previously stored routing results has been considerably improved. The sequence of processing unroutes of multi-point connections to be re-routed has been modified to ensure that no trace can get lost in cases where the sequence of re-constructing the connection tree differs from the pre-calculated unroutes sequence (which e.g. may happen in special cases when connecting to pre-routed fixed traces).

At the end of the routing process (i.e., when storing the routing results), the Autorouter tries to transform stepped traces into diagonal traces. With half-grid routing activated, such diagonal traces could cause problems when trying to re-load using the Load Layout function. Additional checking routines have been integrated to the Autorouter of BAE Version 3.4 to suppress transformation to diagonal traces in cases where this might cause problems on re-load. The routing process not only is better guarded by these new checking routines, but also benefits from the side-effect that certain traces left unchanged by earlier Autorouter versions now might be selected for straightening.

Warning

Please note that half-grid routing results stored with earlier BAE versions might still contain diagonal traces causing problems when trying to re-load using the Load Layout function. Only half-grid routing results stored with the Autorouter of BAE Version 3.4 (or later) are guaranteed to avoid this problem.

6.3 Neural Autorouter

With BAE Version 3.4 the Neural Autorouter module based on the well-known standard Bartels AutoEngineer module is provided. The Neural Autorouter may be optionally used instead of the standard Autorouter module. The user interface of the Neural Autorouter is quite similar to the Layout Editor and/or the Autoplacement (including color setup, undo/redo, interactive routing, User Language, etc.). Special routing functions such as single net autorouting, component routing, etc. are provided with the Neural Autorouter. The Neural Autorouter algorithms also utilize automatic placement optimization such as pin/gate swap during the autorouting process.

The Neural Autorouter module of the BAE Version 3.4 HighEnd system additionally provides most powerful autorouting technologies based on patended neural network technology. Advanced features of the BAE HighEnd Neural Autorouter are skilled analog signal routing, automatic microwave structure generation, grid-less object-orientated routing with automatic placement optimization, etc. The Neural Autorouter also provides features for routing problem recognition and/or classification and for learning and automatically applying problem-adapted routing strategies and/or rules. The Bartels Neural Autorouter with its artificial routing intelligence is supposed to set new industrial standards in autorouting technology.

Autosave

A new Autosave parameter for optionally performing automatic design data backup at selectable time intervals has been implemented with the Neural Router of BAE Version 3.4. For more details see section 1.8 of these Release Notes.

Automatic Parameter Backup

The Neural Autorouter provides an in-built feature for automatically saving important design and operational parameters with the currently processed layout and/or part symbol. The following parameters will be stored to the current design file when activating the Save Element function:

• Autosave Time Interval
• Name of the currently loaded Layout Color Table
• Input Grid
• Display Grid
• Grid/Angle Lock
• Coordinate Display Mode
• Wide Line Draw Start Width
• Part Airline Display Mode
• Library File Name
• Mincon Function Type

Parameter sets are stored with special names according to the currently processed layout database hierarchy level. The layout element name is used for layout elements, and parameter set name [part] is used for layout part symbol elements. When loading an element, the corresponding parameter set is automatically loaded as well, thus providing a convenient way of activating a default parameter set suitable for processing the selected design and/or library element type.

Gridless Routing Option

A new rule-driven gridless router has been integrated to the Neural Autorouter. Gridless routing is deactivated on default (option Gridbased Routing of the new Gridless Routing function from the Options menu). The rule-driven gridless router may be activated by selecting the Gridless Routing option from the Gridless Routing function. The gridless router performs selective gridless routing, i.e. gridless routing is only applied locally where this yields better results in terms of routability and manufacturing optimization. With gridless routing activated, there are much more options for using off-grid pin channels, which might significantly increase the routability of complex layouts. Gridless routing also generates straighter connections to off-grid placed pins, thus preventing from blocking adjacent pin channels and also performing more optimization for manufacturing.

Warning

Note that gridless routing requires more main memory and computing power due to additional data structures (gridless priority tree) to be maintained during the routing process.

Placement Optimization during Rip-Up Routing

A new feature for performing placement optimizations has been integrated to the rip-up router of the Neural Autorouter module. The new Router P/G-Swap Control menu function may be used to activate (option Router Pinswap On) or deactivate (option Router Pinswap Off) placement optimization during rip-up routing. With Router Pinswap On, the rip-up router performs pin/gate/groups swaps and/or component swaps to increase routability and to get a completely routed layout in less time. Swapping is performed selectively during rip-up routing, i.e. only those swaps are performed which may simplify the routing problem. The placement optimization is also involved in the router's backtracking process, i.e. swap operations causing a deterioration of the current routing result will be rejected again. Of course swap operations are permitted on unfixed parts only, and the admissibility of any pin/gate swap is fairly controlled by considering the corresponding logical library part definitions.

Warning

ackannotation is always required after performing layout netlist modifications such as pin/gate swaps, i.e. pin/gate swaps performed by the Neural Router will get lost when re-editing the schematic without applying Backannotation before.

7 CAM Processor

7.1 General

With BAE Version 3.4 up to 12 menu entries of the CAM Processor signal layer menus may be freely defined with layer number and layer name. See section 10.1 of these Release Notes for more details on how to customize the signal layer menus using the bsetup utility program.

The BAE Version 3.4 CAM Processor module has been changed to support traces and via processing on layout part level (see also section 4.2 of these Release Notes).

Special case problems regarding the screen display of arc-shaped fill polygons at (very) high zoom factors have been fixed with BAE Version 3.4.

7.2 Automatic Parameter Backup

The CAM Processor provides an in-built feature for automatically saving important operational and plot parameters with the currently processed layout and/or part symbol. The following parameters will be stored to the current design file when changing to the BAE main menu or to the Layout Editor (i.e., CAM parameter backup may only be suppressed when exiting BAE):

• Name of the currently loaded Layout Color Table
• Input Grid
• Display Grid
• Coordinate Display Mode
• Wide Line Draw Start Width
• Output Mode Board Outline
• Output Mode All Signal Layers
• Output Mode Plot Marker Layer
• Plot/CAM Accuracy/Symbol Tolerance
• Plot/CAM Origin Coordinate
• Plot/CAM Rotation Mode
• Plot/CAM Mirroring Mode
• Power Layer Heat Trap Minimum Distance
• Power Layer Isolation Minimum Distance
• Power Layer Heat Trap Range/Tolerance
• Power Layer Isolation Range/Tolerance
• Power Layer Border Width
• Power Layer Isolation Drawing Width
• Control Plot Output File Name/Device
• Control Plot Scaling Factor
• HP-GL Plot Pen Width/Standard Line Width
• HP-GL Plot Speed
• HP-GL Plot Filling Mode
• Gerber Output File Name/Device
• Gerber Aperture Table Name
• Gerber Format/Plotter Units
• Gerber Standard Line Width
• Gerber Fill Mode
• Gerber Arc Plotting Mode
• Drilling Data Output File Name/Device
• Drilling Tool Table Output File Name/Device
• Drilling Tool Tolerance/Accuracy
• Insertion Data Output File Name/Device

Parameter sets are stored with special names according to the currently processed layout database hierarchy level. The layout element name is used for layout elements, parameter set name [part] is used for layout part symbol elements, [padstack] is used for layout padstack elements, and [pad] is used for layout pad elements. When loading an element, the corresponding parameter set is automatically loaded as well, thus providing a convenient way of activating a default parameter set suitable for processing the selected design and/or library element type.

7.3 Multilayer Plots

A new option called Multiple Layers has been implemented with the layer selection menus of the HP-GL Output, Postscript Output, HP Laser Output, Gerber Output and Insertion Output functions of the CAM Processor. I.e., it is now possible to write the plot and/or insertion data of multiple (selectable) layers to a single output file. With the Multiple Layers option, a popup menu is provided for selecting and/or deselecting the plot and/or insertion data output layers using the left or right mouse button. Layer selections with the left mouse button also allow for layer-specific pen number selections with HP-GL output (on default pen 1 is used for HP-GL output). The Col. button is used to select all currently visible layers for output (with the pen numbers automatically set to modulo eight of the corresponding layer colors for HP-GL output).

7.4 Generic Output under Windows

A new generic print/plot output function has been implemented with the Windows versions of the BAE PC software. I.e., any print/plot output feature supported by the current Windows operating system configuration is also supported with the CAM Processor of the BAE Windows software. The new Generic Output function from the Control Plot menu may be used to activate the Windows print/plot menu.

8 CAM View

8.1 General

With BAE Version 3.4 up to 12 menu entries of the CAM View signal layer menus may be freely defined with layer number and layer name. See section 10.1 of these Release Notes for more details on how to customize the signal layer menus using the bsetup utility program.

Special case problems regarding the screen display of arc-shaped fill polygons at (very) high zoom factors have been fixed with BAE Version 3.4.

8.2 Data Management

A new function called Move Data Set for moving previously loaded drilling and/or gerber data sets has been integrated to the Files menu. The data to be moved can be selected from a popup menu where available data sets are listed according to the load sequence. Each data set entry of the popup menu displays the layer(s), the offset to origin, the mirror mode, and the file name of the input data. After selecting the desired data set the user must specify the movement vector by selecting the start and end point of the movement. Herewith the input grid corresponds with the current display grid settings. Pressing the right mouse button during data set movement will activate a submenu with functions for performing absolute and/or relative jumps.

8.3 Drilling and Milling Data

The Load Drill Data function from the Files menu for loading and/or writing drilling data now allows for the selection of either Sieb&Meier or Excellon format (instead of Sieb&Meier format only). Both input units and processing of trailing and/or leading spaces are automatically derived from the input data file. Current Gerber input parameter and/or format specifications will automatically apply for input data not providing corresponding format commands. Excellon input Inch unit specifications will be processed using the currently selected Gerber format (Gerber Format 2.5, Gerber Format 2.6, etc.).

The function for loading Excellon data features automatic milling data recognition, i.e. Excellon milling data will be automatically regognized and/or processed. With Excellon output function the output data type (i.e. either drilling data or milling data) must be specified, since each drill class may contain both milling and drilling data.

The drilling and/or milling data sets are loaded and saved with drill class specification, respectively. I.e., it is possible to load drilling and/or milling data sets with different drill classes and to generate drilling and/or milling data output with selectable drill classes. With milling data the drill class may be used to differ between plated and non-plated. Drill holes and milling puncture points not assigned to the standard (-) drill class are indicated with the corresponding drill class letter (A, B, ..., Z-).

The Sort Drill Data function from the Utilities menu performs separate sorting on each of the currently loaded drilling data sets. Overall sort on multiple drill data sets can be applied by loading all data sets, save them as single data set, clear the memory, reload the single data set, and run the Sort Drill Data function on the reloaded data set.

8.4 Parameters

The new Trail./Lead. Zeros function provided with the Parameter menu is used to specify whether Gerber coordinate specifications are to be interpreted with trailing and/or leading zeros suppressed. On default the Trailing Zeros mode for expecting trailing zeros and suppressing leading zeros is used. The Leading Zeros mode for suppressing trailing zeros and expecting leading zeros is only valid with Gerber Format 2.5 and Gerber Format 2.6, i.e. any other Gerber format specification will default to the Trailing Zeros mode.

The new Mirror Mode function provided with the Parameter menu is used for optionally mirroring the input data set(s) to be subsequently loaded. The mirror modes provided with the Mirror Mode function are Mirroring Off (default), Mirror at X-Axis, Mirror at Y-Axis and Mirror at Origin, respectively. Note that input data mirroring is always done before any input data offset specification applies.

9 Neural Rule System

A Neural Rule System has been integrated to BAE Version 3.4. This allows for the definition of rules and/or rule sets which may be assigned to individual Bartels AutoEngineer objects. I.e., it is possible to define attributes for controlling design processes such as preferences for the placement of certain part types (e.g. restrictions for part rotation and/or part mirroring), layer-specific clearances to be considered by the Autorouter, net and/or netgroup-specific routing rules (maximum and/or minimum trace length, maximum parallel routing of traces, etc.). The Rule System can also be used to apply more complex design processes for the solution of specific design problems such as special design rule checks for analogues circuitry, high-frequency technique, etc. or for setting up Autorouter passes with strategies and options adapted to certain routing problems.

Rules may be specified using a programming language similar to Prolog. The Bartels Rule Specification Language provides powerful operators for finding not only all possible, but rather optimum solutions to a given rule system query or output request. A Rule System Compiler is provided for the translation of Bartels Rule System source code. Compiled rules are either applied automatically by certain BAE system functions or may be activated using customer-defined User Language programs.

See Bartels AutoEngineer User Manual - Chapter 6 for a detailed description of the Neural Rule System integrated to the Bartels AutoEngineer. See also Bartels AutoEngineer User Manual - Chapter 7 for information on the Rule System Compiler.

10 Utilities

10.1 BSETUP -- Bartels AutoEngineer Setup Utility

LAYMENUTEXT Command

The LAYMENUTEXT command of the bsetup utility program has been changed. It is now possible to define up to 12 (previously 4) entries for the signal layer menus provided with the layout program modules Layout Editor, Autoplacement, Neural Autorouter, CAM Processor and CAM View. The formal syntax of the LAYMENUTEXT command is

LAYMENUTEXT LINE <line> ("<text>",<layer>);

where <line> is the menu line number in the range 1 to 12, <text> is the text that will appear in the layer selection menus (e.g., Solder Side, Signal Layer 2, etc.), and <layer> is the signal layer (in range 1 to 100) to be selected with this menu entry.

WINMENUMODE Command

The Windows and Motif versions of the BAE software may be operated with either the BAE standard user interface with side menus or with the windows-like user interface with pulldown menus. The WINMENUMODE command is used to activate the desired user interface. Use the following command to activate the BAE standard user interface with side menus:

WINMENUMODE (SIDEMENU);

Use the following command to activate the BAE user interface with pulldown menus for Windows and/or Motif versions of the BAE software:

WINMENUMODE (PULLDOWN);

The BAE standard user interface will be activated with the DOS and/or X11 versions of the BAE software, or if the WINMENUMODE command is omitted in the BAE setup file.

See Bartels AutoEngineer User Manual - Chapter 7 for a detailed description of the bsetup utility program.

10.2 COPYDDB -- Copy Design Database Utility Library

New options have been implemented with the copyddb utility program for copying logical library data (-llib), Gerber aperture tables (-gtab), BAE font data (-fnt), SCM color tables (-sct), PCB layout color tables (-lct), IC design color tables (-ict), and User Language libraries (-ull). Option -ul for copying User Language programs has been changed to -ulp. Option -a has been changed to support all of the above-mentioned database classes. The source and destination file names required at the copyddb call may now be specified with file name extensions to support other than .ddb extensions (however, .ddb is the default if file name extensions are omitted). The new synopsis of the copyddb command is given by:

COPYDDB srcfile dstfile {-ms|-md}
        {-a|-as|-al|-ac|-sp|-ss|-sl|-sm|
         -ll|-lp|-ls|-ld|-cl|-cc|-cp|
         -llib|-gtab|-fnt|-sct|-lct|-ict|
         -ulp|-ull} [pattern]

See Bartels AutoEngineer User Manual - Chapter 7 for a detailed description of the copyddb utility program.

10.3 INSTALL -- Bartels AutoEngineer Installation Utility

The user interface of the install utility program has been changed to support the installation of BAE PC software on different operating system platforms. The single media install command mode has been integrated to the install user interface, and thus can not be activated on program call anymore.

See Bartels AutoEngineer User Manual - Chapter 7 for a detailed description of the install utility program.

10.4 LISTDDB -- List Design Database Utility Library

The listddb utility program has been changed to list all of the BAE design and system database classes. The DDB input file name required at the listddb call may now be specified with file name extension to support other than .ddb extensions (however .ddb is the default if the file name extension is omitted).

See Bartels AutoEngineer User Manual - Chapter 7 for a detailed description of the listddb utility program.

10.5 RULECOMP -- Bartels Rule System Compiler

The new rulecomp utility program is the compiler to be used for translating Bartels Rule Specification source code. Rules and/or rule sets may be defined using a programming language similar to Prolog, however with special operators to find not only all possible, but rather the optimum solution to a given rule system query or output request. Rules may be specified for and assigned to individual items such as parts, nets, traces, etc. The Rule System also supports more complex tasks such as special design rule checks or autorouter passes with certain parameter setups according to the routing problem. The Rule System uses a neural net approach to focus the rule evaluation on the probably best path. Compiled rules are either applied automatically by certain in-built BAE system functions or may be activated with customer-defined User Language programs.

See Bartels AutoEngineer User Manual - Chapter 7 for a more detailed description of the rulecomp utility program. See also Bartels AutoEngineer User Manual - Chapter 6 for a description of the Bartels Neural Rule System integrated to the Bartels AutoEngineer.

10.6 VALCONV -- VALID to Bartels Conversion

As far as we know, the valconv utility program for converting netlists from VALID to BAE is not in use anymore. We are considering to drop this program from one of the next BAE releases. Please contact us as soon as possible, if you are still using the valconv utility program; if so, we can decide to keep the program part of the released BAE software or provide a User Language program with corresponding functionality.

11 Bartels User Language

11.1 General

This section describes general changes to the User Language specification. See Bartels User Language Programmer's Guide - Chapter 2 for a detailed description of the User Language specification.

Internal User Language Version

The internal version of BAE Version 3.4 User Language has been changed. User Language programs compiled under earlier BAE versions won't be executable in the BAE Version 3.4 User Language interpreter environment (corresponding error message User Language program version incompatible!). This means that each User Language program compiled under earlier BAE Versions must be recompiled under BAE Version 3.4 to regain compatibility.

References to renamed Data Types

With the new User Language version typedef references need not be preceded with the type keyword anymore. I.e., a declaration such as

type TYPENAME varname;

can now be written as

TYPENAME varname;

The type keyword specification is still supported for backward compatibility reasons. Note however that this feature will be skipped from the next User Language version. It is strongly recommended to remove all type keyword specifications from existing User Language sources.

Function Parameter Definition/Declaration

The User Language specification has been changed to support ANSI function parameter definition/declaration compatibility. I.e., function parameters may now be defined and declared in the function header as in

fct(double dbl,string strl[],index L_MACRO m)
{
:        /* Function code */
}

Alternate function parameter definitions/declarations according to the previous User Language specification as in

fct(dbl,strl,m)
double dbl;
string strl[];
index L_MACRO m;
{
:        /* Function code */
}

are still supported.

Storage Class static

The User Language specification has been changed to support optional static storage classes for global variable and function definitions/declarations (which is required for User Language library generation/management and User Language linking features).

Internal List Length Limit

With BAE Version 3.4 the internal list length limit used for data allocation throughout the User Language has been increased from 32,767 (7FFFh) to 1,048,578 (100000h). This definition affects the following list length limits, i.e. the maximum number of objects and/or elements processed by the User Language Compiler and/or the User Language Interpreter:

• User Language system functions
• parameters per User Language system function
• User Language index types
• variables per User Language index typ
• pseudo code commands per User Language program
• global variables per User Language program
• user functions per User Language program
• parameters per user function
• local variables per user function
• macro definitions per User Language program
• type definitions per User Language program
• structure definitions per User Language program
• structure variables per structure definition
• constant double values per program
• constant strings per program
• elements on expression stack
• expression stack base size for nested function calls
• source code files simultaneously referenced
• User Language programs simultaneously activated
• elements per array dimension of specific program object
• characters per dynamically allocated string
• BNF productions per BNF reference
• BNF actions per BNF reference
• BNF formulations per BNF reference
• BNF symbols per BNF reference

Note that any User Language is more likely to fail on (HW-dependent) memory overflow problems than on list overflow. Note also that User Language program errors such as expression stack overflow caused by endless-recursive function calls might now take much more program execution time to become obvious.

11.2 User Language Compiler

This section describes the news and changes introduced to the BAE Version 3.4 User Language Compiler. See Bartels User Language Programmer's Guide - Chapter 3 for detailed information on how to operate the User Language Compiler.

Compiler Call, Compiler Options

With BAE Version 3.4 the following new features and/or command line options have been implemented with the User Language Compiler such as:

• new option -cl for compiling/generating linkable User Language libraries; new option -cp for compiling/generating User Language programs; both -cp and -cl allow for the specification of (multiple) destination element names different from that retrieved from (single) source file name
• new options -lib and -dll for performing static and/or dynamic User Language library linkage
• features for compiling different source files with a single ULC call by specifying multiple source file names and/or using wildcards; source file name specification with other than .ulc name extension; program and/or library name extraction from source file path name; source file names to be specified anywhere on the command line using the new -S[ource] option
• new -I[nclude] option for alternate include file search path specification
• new -M[acro] option for defining macros on ULC call, thus giving more control on conditional compilation processes to ULC
• new options -dp and -dl for deleting compiled User Language programs and/or libraries (-dp to replace old -del option, i.e. -del is not valid anymore)
• new options -wcon and -wcoff for either activating or deactivating wildcard processing at the specification of source files to be compiled and programs/libraries to be deleted
• listing option -l changed for selecting different listing modes; additional information on linking provided with listing output; listing format considerably changed to provide more ANSI C-like syntax
• improved ULC error handling; warning severity level to be selected with the -w option to suppress less important warnings; new -e option for selecting Compiler error abort criteria
• improved ULC message system with log file generation; new option -log for directing log file output to different file than default log file ulc.log

The new synopsis of the User Language Compiler is given by:

ulc [-wcon|-wcoff] [[-S[ource]] srcfile...]
    [-lib libname...] [-dll libname...]
    [{-cp|-cl} [dstname...]]
    [-I[nclude] includepath...] [-D[efine] macroid...]
    [-O[0|1]] [-e[0|1]] [-w[0|1|2|3|4]] [-l[0|1|2|3|4|5]]
    [-dp prgname...] [-dl libname...] [-log logfilename]

Parser

The structure data assignment check routines have been improved to perform genuine data assignment check on different structure definitions. I.e., objects referring to different structure definitions may be assigned if these structure definitions are type assignment compatible. Recursive assignment checks are also performed to apply correct check on nested structure definitions.

Conditional file inclusion controlled by macros could have failed in special cases when entering the User Language Compiler parser pass 2. This macro redefinition problem has been fixed with BAE Version 3.4 by resetting all macro definitions after completing parser pass 1.

Optimizer

New features have been implemented with the optimizer to eliminate redundant/unreferenced structure definitions.

A new feature for recognizing and eliminating unreferenced indirect-recursive user functions has been implemented with the optimizer. The previous Compiler version could only recognize direct-recursive function calls such as

f() calls f()

whilst the new version can also recognize recursion chains such as

f() calls f1() calls ... calls fn() calls f()

11.3 User Language Interpreter

This section describes the news and changes introduced to the BAE Version 3.4 User Language Interpreter. See Bartels User Language Programmer's Guide - Chapter 3 for detailed information on how to operate the User Language Interpreter.

Dynamic Linking

The BAE Version 3.4 User Language Compiler may generate User Language programs containing dynamic link requests, i.e. requests on binding User Language library machine code to program machine code at runtime. The User Language Interpreter automatically applies dynamic linking during program load. Each dynamic link library (DLL) must be available, and the definitions (variables, functions, function parameters) provided with each DLL machine code must match its definitions at compile time (otherwise the Interpreter might try to access non-existent or wrong library objects, which would result in undefined behaviour or even system crash with design data loss). The built-in linker of the User Language Interpreter checks on dynamic link library compatibility and refuses to run the program when encountering any inconveniences (error message Incompatible index/function reference(s)!). In case of incompatible DLLs the User Language program must be recompiled.

11.4 Index Variable Types

This section mentions the news and changes on the Bartels User Language index variable types. See Bartels User Language Programmer's Guide - Appendix B for a detailed description of all index variable types.

Changed Index Variable Types

The L_LINE index type may now be used to scan traces on layout part level.

The L_UREF index type may now be used to scan vias on layout part level.

11.5 System Functions

This section mentions the news and changes on the Bartels User Language system functions. See Bartels User Language Programmer's Guide - Appendix C for a detailed description of all system functions.

New System Functions

With BAE Version 3.4 the following system functions have been integrated to the Bartels User Language:

Changed System Functions

The bae_askfilename system function specification has been changed to

int bae_askfilename(          /* Returns status */
      & string;               /* Returns file name */
      string;                 /* File name extension string */
      string;                 /* Prompt string */
      );

Where the new file name extension string parameter can be used to set a file name extension filter. On empty string input, all files are scanned/displayed. On extension specification (e.g., .ddb, .dat, .txt, ., .*, etc.), only those files matching the extension are scanned and/or displayed. The - tag works for file name exclusion. On - input all files matching BAE system or data file extensions (.ass, .con, .ddb, .def, .exe, .fre, .ulc and .usf, respectively) are faded-out from display (this feature may be used for output/plot file queries where system/library/project files must not be selected).

The bae_swconfig system function has been enhanced. A function call such as

bae_swconfig(1)

can be used to check, whether the user is currently working with BAE Demo software (function return value non-zero) or not (return value zero). A function call such as

bae_swconfig(2)

can be used to check, whether the user is currently working with BAE Entry/Educate software (function return value non-zero) or not (return value zero). A function call such as

bae_swconfig(3)

can be used to query the type of the currently active user interface (0 = BAE standard menu screen interface, 1 = BAE standard menu interface under windows, 2 = BAE pulldown menu interface under Windows, 3 = BAE standard menu interface under Motif, 4 = BAE pulldown menu interface under Motif).

An internal software cache for fast directory file name scan has been implemented with the scandirfnames system function.

Two new operators named NEXTTO and PREVTO have been implemented with the select SQL command to be executed using the sqlcmd system function. These operators may be used for selecting and/or accessing succeeding and/or preceding database entries most similar to a given pattern string.

The ged_storepath and ar_storepath system functions for storing traces have been changed to work on layout part hierarchy level as well.

The ged_storeuref and ar_storeuref system functions for placing vias have been changed to work on layout part hierarchy level as well.

Redundant System Functions

Some BAE Version 3.2 system functions are redundant since BAE Version 3.4 provides corresponding new functions which can be applied more general. The redundant system functions are still supported by BAE Version 3.4, but will be removed from one of the next BAE Versions. We strongly recommend to remove the corresponding function references from your User Language source codes as soon as possible. Functions can be replaced according to the following reference (old function call ==> new function call):

The additional integer parameter of bae_inpoint is used for optionally displaying (value 1) a rubberband graphic frame during interactive input.

11.6 BAE User Language Programs

With BAE Version 3.4 a lot of very useful User Language programs are delivered. These programs will be installed as source code files to a special directory named baeulc (see also section 1.4 of these Release Notes). Please consider that BAE Version 3.4 comes with about 140 User Language files including more than 1.8 MByte (nearly 62,000 lines) of User Language source code, thus also presenting a lot of CAE/CAD software engineering know-how. Bartels User Language Programmer's Guide - Chapter 4 lists all BAE User Language programs with short descriptions, and also provides information on how to make the programs available to the BAE software.

The User Language programs already delivered with the previous BAE version have been completely revised and extended by a series of new functions. Some of the BAE Version 3.2 User Language programs have been renamed or integrated to other programs. With BAE Version 3.4 also a series of new User Language programs are provided, such as DDB element browser, operating system shell, SCM symbol/part utilities, etc. Due to the extensive changes made to the User Language programs shipped with BAE Version 3.4, BAE Update installations are recommended to install the baeulc directory to a different path as it has been installed before. At least the old include files (extension *.ulh) should be saved when being used for customer-specific UL software engineering. Also make sure to save your own UL program sources before performing BAE Update installation, and to re-compile them after successfully installing BAE Version 3.4.

Include Files

The User Language include files already delivered with the previous BAE version have been completely revised and extended by a series of new functions. All include files have been changed to support the dynamic/static linking facilities introduced to the User Language programming system.

The following User Language include files have been implemented with BAE Version 3.4:

User Language Programs

All BAE Version 3.4 User Language programs have been revised to support the dynamic/static linking facilities introduced to the User Language programming system.

Two new buttons called Back and Dump have been implemented with the popup menus used throughout the User Language programs. The Back button provides a scroll back/page up function in the current menu entry list. The Dump button is used for writing the current popup menu contents to a selectable file. User Language programs generating reports have been changed to display these reports in a popup menu with Dump option rather than to write the report to file immediately.

The layout-specific User Language programs have been revised to support traces and/or vias on layout part level (see also section 4.2 of these Release Notes).

Key bindings and menu assignments defined with the uifsetup User Language program have been slightly changed.

The following User Language programs have been implemented with BAE Version 3.4:

The ROTATE User Language program has been replaced by the LROTATE and RROTATE User Language programs.

User Language Program Compilation

When installing the BAE software, all User Language source files will be stored to a special directory named baeulc. Some of the BAE User Language programs will define implicit User Language program calls (startups, menu assignments, key bindings). Please consider that you might loose part of previously installed startups, menu assignments, or key bindings when compiling the User Language programs after Bartels AutoEngineer update installations.

With the BAE software, the cplsll.bat and cpldll.bat compile batch files are provided in the baeulc directory. CPLSLL (ComPiLe with Static Link Library) first generates a User Language library from the BAE include files and then compiles all BAE User Language programs with required machine code from the previously generated library statically linked to the programs. CPLDLL (ComPiLe with Dynamic Link Libraries) first generates a User Language library from the BAE include file hierarchy, and then compiles all BAE User Language programs with information for dynamically linking at runtime with required machine code from the previously generated library.

Dynamic linking significantly reduces disk space requirements for storing compiled programs. Note however that dynamic linking must be done by the User Language Interpreter, thus requiring more CPU time for loading programs and increasing main memory requirements for loading redundant code from dynamic link libraries. Note also that at changes of dynamic link libraries each program referring these libraries must be recompiled for compatibility reasons. Therefore static linking (compile batch file cplsll.bat) is preferable to dynamic linking (compile batch file cpldll.bat) whenever enough disk space is available and/or CPU performance is poor. From under DOS the compile batch may be started by typing either

> cplsll 

or

> cpldll 

to the DOS prompt from the baeulc directory. From under UNIX the compile batch may be started by typing either

> cplsll.bat 

or

> cpldll.bat 

to the UNIX shell prompt from the baeulc directory. The compilation process might last some time (according to the power of your computer). After successful processing of the batch file all of the User Language programs distributed with the BAE software are available.

It is strongly recommended to install and compile the BAE User Language programs since these programs provide a wide range of additional BAE features such as menu definitions, key assignments, extended report functions, advanced edit utilities, data I/O interfaces, library management tools, etc. Bartels User Language adds incredible power and flexibility to the Bartels AutoEngineer; almost any customer-specific problem arising with the use of BAE can be solved in a minimum of time without the need of waiting on a new BAE software release. It is recommended to test the distributed User Language programs using example jobs to gain an overview on the hundreds of BAE add-on functions implemented with these programs. You will find a lot of useful functions satisfying your needs either directly or slightly modified. User Language program customization is easily possible since all programs are shipped in source code with extensive inline documentation. If you are not experienced in programming or simply haven't got the time, just contact Bartels Support in case you have some requirement on additional BAE features.

Menu Assignments and Key Bindings

With the BAE software the User Language startup program bae_st.ulh is provided. This program can be compiled to generate the interpreter-specific startup programs scm_st, ged_st, ap_st, ar_st, cam_st and ced_st (with IC Design option), respectively. These programs are automatically started when entering the corresponding User Language Interpreter environment (Schematic Editor, Layout Editor, Autoplacement, Neural Autorouter, CAM Processor or Chip Editor, respectively). Each of these programs performs an indirect call to the uifsetup User Language program. uifsetup automatically activates predefined menu assignments and key bindings for the currently active BAE program module. This kind of program system organization involves considerable advantage on software maintenance: arbitrary changes on menu assignments and key bindings require modification (and re-compilation) of uifsetup source code only. The uifdump User Language program can be used to generate an ASCII report file providing complete information on the menu assignments and key bindings of the currently active BAE program module. The uifreset User Language program may be used to reset all currently defined menu assignments and key bindings of the currently active BAE program module. uifsetup, uifdump, and uifreset may also be called from the menu of the keyprog User Language program which also provides comfortable functions for online key programming.

Bartels AutoEngineer® - Version 3.4 - Release Notes
© 1985-2024 Oliver Bartels F+E • Updated: 15 July 2011, 01:24 [UTC]