home *** CD-ROM | disk | FTP | other *** search
- PADS-LOGIC Version 2.5 ADVISORIES
-
-
- PINSTALL
-
- The PINSTALL (PADS Installation program) provided with PADS-LOGIC v2.5 can
- only be used to install PADS-LOGIC v.2.5 and PADS-PCB v4.x. Do not use the
- PINSTALL provided on other PADS product diskettes to install PADS-LOGIC v2.5.
-
- You must use the PINSTALL program provided with other PADS programs (i.e.,
- PADS-2000 v3.x, PADS-SuperRouter v4.x) for installing PADS programs other
- than PADS-LOGIC v2.5 and PADS-PCB v4.x.
-
- If you are loading other PADS programs, then you must load PADS-LOGIC v2.5
- last. Batch files for the other programs reference the old PADS-LOGIC
- executable "CAE.EXE" rather than the new ones, "LOGIC32.EXE" and
- "LOGIC16.EXE". If you do not load PADS-LOGIC v2.5 last, then you must
- modify the names of the executables yourself or re-load the software over
- again.
-
- You cannot load PADS-LOGIC 16-bit and 32-bit into the same directory. Before
- beginning the installation process, decide which option you will be
- installing. To help you select which option to install a list of
- considerations is provided in the PADS-LOGIC Reference Manual.
-
-
-
- USER LIBRARIES
-
- In order to support all of the new Library features incorporated into the
- software, you must convert any library items that you have created into the
- new Library format. The procedure on how to use the Library Conversion
- Program CONV3TO4 is explained below.
-
- If you are a new user of PADS-LOGIC and/or PADS-PCB, you will not have any
- customized library shapes, therefore you can disregard this note.
-
- If you are an existing user and have PADS-PCB Version 4.x or PADS-2000
- version 3.x already installed, and you are updating to PADS-LOGIC Version
- 2.x, pay special attention to items 8 and 9 regarding initializing existing
- libraries.
-
- Customers Converting V 1.2x PADS-LOGIC Libraries to PADS-LOGIC V 2.x format:
-
- 1) Load the Version 2.X Update.
- 2) Type: CD \PADS <CR> to change to the \PADS directory.
- 3) Type: CONV3TO4 <CR>
- 4) Select Item #4.
- 5) Select the version of the package that you are converting.
- 6) Select the type of library that you are converting.
- 7) Enter the drive letter (followed by a colon) and the path to your old
- PADS Library. (<CR> defaults to the current drive and the \PADS\LIB
- directory.)
- 8) Initialize or add to existing V4 Library? I/A. "I" should be used if
- your User Library does not exist. "A" should be entered if you are
- adding parts to an existing V 4.0 Library.
- 9) Overwrite duplicate items? (This prompt only appears if you have
- responded with the letter "A" to the question #8, and intend on
- replacing parts already existing in the V4.0 library. If you are
- only planning on adding parts to the new library, enter an "N" for
- "NO").
- 10) Confirm the selection.
-
- Keep in mind that one of the new features with the library is the ability
- to have up to 9 different libraries active at one time, not just a standard
- and a user library.
-
- To do this with your User Library, once you have finished converting the
- libraries, go to the User Library and write out the Part Type and Decal
- information that you wish to make a separate library from. Then, create
- the new Library through PLIB\INITIALIZE and feed the ASCII files back into
- the new Library using PLIB's READ.
-
- Once the Library Conversion is complete, you may also want to remove
- nonessential files located in the Library directory. Files with .DAT and
- .IDX extensions are among the old library data files which can be removed
- once the conversion process is complete.
-
-
-
-
-
- USING PADS-LOGIC 16-bit and 32-bit
- A schematic BINARY file created in PADS-LOGIC 16-bit is upward compatible
- with the 32-bit option. A schematic created with the 32-bit option must be
- transferred to the 16-bit using the ASCII OUT transfer method. Keep in mind
- the 32-bit database must stay within the limits of the 16-bit option to
- transfer properly.
-
-
- NETLIST
- When a user specifies a Reports, Netlist out, using PADS-PCB, the user
- should note that the PCB decal defined in this ASCII file identifies a
- specific decal which appears in his/her PCB database. This new version is
- enhanced to allow all the alternates to be available in Pads-Pcb providing
- the alternate decal being called out is one of the alternates presently
- defined in the part type used to bring the part in. If the decal is
- completely independent of the part type being used, then only that specific
- decal will be available in the board design.
-
-
- REPLACE PART
- Attempting to replace a part in a schematic which has less pins than the
- original part results in the prompt: "NEW PART HAS LESS PINS THAN ORIGINAL
- PART", and the part will not be replaced. This is an error checking
- function that is performing correctly. You cannot change a part with fewer
- pins because connections would be lost. Always replace with a part
- containing the same number or more pins. If not possible, the original
- part must be deleted and the new part (with fewer pins) put in and reconnected.
-
-
- DUPLICATE PIN NAMES
- Unable to have duplicate pin names in LOGIC decal! Names such as NC or N/C
- must be different, ie: NC1, NC2, etc.. This is functioning correctly and
- will not be changed. If desired, add the names as free text in the Mod Gate
- routine.
-
-
- REFERENCE DESIGNATORS
- Pure alpha reference designator names are not supported.
-
-
- BUS NAMES
- Bus names with alphanumeric characters are not supported, ie: DA1[00:13],
- only names such as DA[00:13]
-
-
- SET PLOGIC
- If you use the directory variable statement (i.e., set PLOGIC or PPCB), the
- batch files associated with PADS Software must also be modified to match
- the new directories assigned.
-
-
- MEMORY REQUIREMENTS
- Customers using the 16-bit option of Pads-Logic must have 1 Megabyte of
- expanded memory available in order to run the program. Customers who are
- using a 286 CPU MUST have the expanded memory loaded on a true expanded
- memory card. Customers with a 386 CPU can configure their expanded memory
- via an expanded memory manager.
-
- Customers using the 32-bit option of PADS-Logic do not need expanded memory
- to operate the software. Since the 32-bit option is written in 32-bit code,
- it will only operate on 80386 and 80486 computers.
-
-
- DISK SPACE
- Please be advised that on systems with low amounts of hard disk space, a
- message appears indicating your disk space is low, and the backup files
- cannot be created without clearing up more disk space. If the message goes
- unheeded, the system in some cases will attempt to try backing up the
- schematics and get caught in a never ending loop. A reboot of the system is
- the only way out of the software.
-
-
- CAE DECAL GENERATION
- Many users are modifying existing parttypes to make other parts. While
- this is a valid procedure, please be aware that if you make changes to a
- gate decal at this level (physical changes rather than text modifications),
- any other parttype that utilizes this gate decal in its configuration, will
- also assume these physical changes. The correct way to implement these
- changes is:
-
- 1) To use an existing gate decal as a base for generating another, call
- up gate "A" under the "GATE DECAL" command in the library menus,
- produce all the modifications necessary at this point, and save it
- away as gate"B". This way gate "A" is preserved in its original form
- and gate"B" has now been created.
- 2) To generate a new gate decal at the parttype stage, you simply define
- the name in the electrical section. When you complete (F9) the
- parttype, the system alerts you that your gate decal does not
- exist. At this time, select "MOD GATE" and generate your gate decal.
- Once you have finished defining the gate, select complete (F9), and
- save the part away in the normal fashion.
-
-
- OFFPAGE
- If a schematic is brought to another design station and a GROUP/CUT is
- performed which contained offpage symbols, when that cut is re-added to a
- new sheet, the offpage symbol may be added using the wrong symbol. This is
- caused by the differences between the offpage parts which can vary from
- system to system. We recommend modifying the offpage part on system two to
- match that of system one, then paste the group back in.
-
-
- REPORTS
- The REPORTS/NETLIST selection called "other" should not be used by any
- customer as a type of output netlist. It is a spare entry which PADS
- Software, Inc. will use when new output formats become available.
- Several output formats have been removed from PADS-LOGIC Version 2.X.
- These outputs have been removed to avoid confusion and will be re-instated
- as they become available. They are CADnetics, ViewLOGIC, and Mentor.
-
-
- DOS 5.0 ADVISORY
- DOS 5.0 is functioning fine on many systems here at PADS Software, Inc.
- The systems are loading all available drivers into high extended memory
- which provides a large additional amount of DOS 640K memory to our
- programs. This additional DOS memory allows for larger numbers of parts,
- as well as connections in our 16-bit programs. We have, however, run into
- several cases where certain statements when executed through the CONFIG.SYS
- file would cause the programs to lock up or act unpredictably. We advise
- stripping the CONFIG.SYS file down until you find which statements are
- causing the problem. One known statement is:
-
- DOS = HIGH, UMB
-
- We also advise stripping the AUTOEXEC.BAT down until you find which
- statements are causing the problem. Two known statements are:
-
- VERIFY ON/OFF
- MIRROR
-
- Once these statements have been explored, investigate stripping your disk
- caching programs, they may be causing problems as well.
-
-
-
-
-
- PADS-LOGIC 32-BIT OPTION ADVISORIES
-
-
- HARDWARE NOTES
- The 32-bit option of PADS-LOGIC is not compatible with 80286 or XT computers.
-
-
- TRANSFERRING FILES TO PADS-LOGIC 16-BIT
- A schematic created with the 32-bit option must be transferred to PADS-
- LOGIC 16-bit using the ASCII OUT transfer method. Keep in mind the 32-bit
- database must stay within the limits of the 16-bit option to transfer
- properly.
-
-
- ENGINEERING CHANGE ORDERS (ECO)
- The current ECO routine supports up to 12 character net names. Problems may
- occur if more than 12 character net names are used. A new ECO routine that
- corrects this problem is scheduled for the next release of PADS-LOGIC.
-
-
- NETWORK USERS
- PADS-LOGIC 32-bit option will not run if you execute the software from a
- directory other than the server's directory. Reason is, the software looks
- for the PADS directory to be at the root level rather than the client path.
- To run PADS-LOGIC 32-bit on a network, simply go to the server's directory,
- and type:
- LOGIC32 <CR>
-
- to invoke the executable. NOTE: Job files are saved to the "client's" path.
-
-
- FOR PADS-PCB USERS
- If you plan to use the PADS-LOGIC 32-bit option with PADS-PCB, take care
- not to exceed the limits of PADS-PCB. The 16-bit option of PADS-LOGIC will
- not allow you to create a schematic that exceeds the maximum design size of
- PADS-PCB.
-
-
- NET NAMES
- PADS-LOGIC 32-bit supports 47 character net names. PADS-PCB only supports
- 12 character net names. Problems may occur if you are using PADS-PCB and
- exceed the 12 character limitation. PADS-2000 v3.x does support 47 character
- net names.
-
-
- BUS NAMES
- PADS-LOGIC 32-bit supports BUS NAMES up to 44 characters.
-
-
- SIGNAL PINS
- Do not exceed more than 20 characters in the EDIT SIGPIN routine, problems
- may result.
-
-
- EDIT TEXT
- Hierarchical symbol names cannot be turned off.
-
-
- PRINTING REPORTS
- To directly print out report files to your printer, type PRN <CR>.
-
-
-
- If, after reviewing this document and consulting your PADS-LOGIC manual,
- you would like additional information, then contact our Technical Support
- Staff at (508) 486-3328 or 1-800-423-PADS.
-
- 4/92
-
- ***** END OF LOGIC.DOC FILE *****
-