1、OrCAD Capture Messages Reference Guide ALGnnnn Messages The ALGnnnn messages are errors and warnings generated by the Capture netlister during netlisting and back annotation. Each of these messages may be caused by more than one type of problem, yet end up with the same result. In general, most erro
2、r and warning information may be found in the session log. You can also click in the text of the session log message and press F1 to view more details. Error A design or environment condition encountered that prevents the netlisting from proceeding. An error is always fatal and the netlisting proces
3、s is aborted. Warning An undesirable design or environment condition encountered which you should be aware but one that allows netlisting to continue. Error ALG0011 Conflicting values of (Source Package) Cell names found on and for part This situation should only occurs if you use the DEVICE propert
4、y. You can change one or more of the DEVICE properties to make the Part Name (primitive line) unique for each distinct part in the PSTCHIP.DAT file. The part name, which is the value found between single quotation marks in primitive line of the PSTCHIP.DAT file, must be unique for every different ty
5、pe of part in the design. The part name is just the value of the DEVICE property present. If there is no DEVICE property on the part, then the part name is a made by combining the values of the Source Package, PCB Footprint, Value, and other properties that may be found in the ComponentDefinitionPro
6、ps section of the configuration file. The part name string is a concatenation of these properties, with each value separated by an underscore character. For more information, see the OrCAD Capture Users Guide. Error ALG0012 Property “PCB Footprint“ missing from part : , ( , A PCB Footprint (JEDEC_TY
7、PE in PCB Editor) is required for all parts in PCB Editor. Therefore all parts without this property are listed before aborting the netlisting. You can add the PCB Footprint property by selecting the part listed, then choosing Edit Properties from the pop-up menu and placing a value, such as dip14_3
8、, on the part. ErrorALG0013 Conflicting values of following properties found on different sections of For multi-section parts, all sections must have the same values for the properties listed under ComponentInstanceProps in the configuration file. For example, ROOM is a component instance property,
9、so if you add ROOM to the combined property string when you annotate, then sections with differing ROOM properties will not be packaged together. You can separate or combine component instances in a multi-section parts just by specifying distinguishing properties in the combined property string. Che
10、ck the configuration file to identify the component instance properties currently available. For more information, see the OrCAD Capture Users Guide. Error ALG0014 Conflicting values of part name found on different sections of Type topic text here. Conflicting values: cannot netlist this part This e
11、rror displays if there is a pin number missing on one of the parts in the schematics. All pins on parts should be numbered before attempting a netlist. All parts with unnumbered pins are listed before the netlister aborts the run. View the session log for details about why the netlist aborted. You c
12、an run the library correction utility on library files, for correcting duplicate pin names, and then use these libraries in creating new designs. After correcting the libraries you will not encounter the ALG0031 error. Error ALG0032 Pin number “0“ found on : , ( , . Pin number should be greater than
13、 “0“. Cannot netlist this part PCB Editor does not support pin numbers equal to 0 (zero). Change the pin number by editing the part, then the pin. All parts with pin numbers equal to zero are listed before the netlister aborts. Look in the session log for details about which pins must be changed. Er
14、ror ALG0033 Invalid Part Property specified for , ID If you have a multi-section part, then the component definition properties for each section must be the same. For example, you cant have two different PCB Footprint or Value properties on two different sections of a NAND gate IC. Error ALG0034 Una
15、ble to open file for reading This error message occurs when the configuration file or board file specified in the Create Netlist dialog box or the Back Annotate dialog box does not exist in the path specified or is corrupted. You can go to the Setup dialog box and click on the edit button to verify
16、which problem you have. To do so, you browse to a valid configuration or board file. A default configuration file (allegro.cfg) was installed with Capture in the Capture subdirectory. If you have deleted it you can recreate it by writing a text file with the contents from the configuration file Help
17、 topic and save the file with a .CFG extension. Error ALG0035 Aborting Swap file creation.Please correct the above errors and retry There were fatal error(s) encountered during swap (.SWP) file creation. See the Capture session log for details. There is also a swap.log text file that contains the sa
18、me errors that were found in the session log at the time the last back annotation was run. Error ALG0036 Unable to read logical netlist data There was an error encountered while reading PST*.DAT files. This error is probably caused by invalid characters in the PST*.DAT files. You have probably modif
19、ied your netlist files since importing logic to PCB Editor. Remember that even things like deleting a net that doesnt have a net alias and then re-drawing it will result in a new net name since net names are auto generated. Error ALG0037 Unable to read physical netlist data This error message appear
20、s when Capture encounters an error while reading the *VIEW.DAT files. The possible causes of this error are: Invalid character in *VIEW.DAT files *VIEW.DAT files are not stored in the same location as pst*.dat files PST*.dat and *VIEW.DAT files do not correspond to the same design Illegal characters
21、 in reference designators or net Changes made to a part in Capture design after board file creation. This can happen because of running the Replace Cache or Edit part commands. One or more values of the component definition properties got changed after board file creation Some components got deleted
22、 from Capture design after board file creation Design file/root schematic/hierarchical block names got changed after board file creation Netlist files not readable because either the path to the file is long or has spelling errors. For more information, see the OrCAD Capture Users Guide. Error ALG00
23、38 Unable to create logical-physical difference data There was an error encountered while creating data for swap (.SWP) file writing. Back annotation generates new netlist files (PST*.DAT), compares them with the *VIEW.DAT board files, and then generates a swap (.SWP) file with the differences. Look
24、 for errors in swap.log netlist.log files or the in the session log, or consider reasons why one step in this back annotation process might have failed. Error ALG0039 No components to package in design Either no components are placed on the schematic or all placed components are to be excluded from
25、the netlist. For example, if all components are assigned the PSpiceOnly property, there would be no netlist. To eliminate this error, you must use components besides those with just the PSpiceOnly property when creating an PCB Editor netlist. Error ALG0040 Value of Property missing from part , ( , T
26、his error is reported when a property value needed for netlisting is NULL (the occurrence value is blank or empty but there is an instance value). To fix the problem you should edit the part and enter an occurrence value for the property. If there is an instance value, you can also delete the occurr
27、ence value which will make the instance property “shine through“ to the occurrence in the property editor because a child occurrence inherits the property of its parent instance if no property value exists on the occurrence. The yellow values are the occurrence values in the property editor. To make
28、 the instance shine through, you have to select the occurrence cell (appropriate row and column) in the property editor and then right mouse click and select delete property. Backspacing or just deleting the characters in the occurrence cell one at a time wont work. Error ALG0041 Part Reference miss
29、ing from part with value : , ( , Part Reference is a combination of reference and designator. Make sure that the designator is not a question mark (?). If it is, you need to annotate your design. You may need to check occurrence mode when annotating if your instance designators have values but your
30、occurrence designators do not. Error ALG0042 Duplicate Reference Designator : , ( , To avoid this error, run the DRC report to check for duplicate Reference Designators before creating the PCB Editor netlist. Duplicate part references are reported in the session log. Proper annotation will avoid or
31、fix this error. You can unconditionally annotate your design or manually change one of the duplicated part references. Error ALG0043 Net named “NC“ found on the design. Please rename the net. PSTXNET.DAT uses a net named nc to specify where all the unconnected or no-connect pins no-connect pins are
32、for PCB Editor. So, do not create a net with an alias of NC or all those pins connected to the net will get a NC property on them in PCB Editor and therefore wont be a net there. Error ALG0044 Conflicting values of “Power Pin Visibility“ found on different sections of : , ( , Power pins should be ei
33、ther visible or invisible for all occurrences in a reference; mixed visibility is not allowed in a reference. You can fix this problem by selecting the part, choosing Edit Part from the pop-up menu, and making the power pins visible. Error ALG0045 Multiple pin s which have different nets connected f
34、or part : , ( , A part with duplicated pins, whether the part be on the same section or in a different section of a package, cannot be connected to different nets. For example, if you have a part with two power pins named VCC and you connect one of the pins to ground and the other to VCC or VEE then
35、 you get this error. Another reason could be that the design is not annotated. Make sure the same net goes to all pins on the part having the same name. Remember that in Capture, two nets not visually connected together but with the same net alias name are connected electrically. Check all sections
36、for multi-section parts, especially if the sections are on different pages. Error ALG0046 Duplicate Pin Number found on and for part : , ( , Two pins cannot share the same pin number. To fix this problem, select the identified part, then choose Edit Part from the pop-up menu. Choose Package from the
37、 View menu, then select the desired component and change its pin numbers so they are unique. Alternatively you could change the part in the library and do a replace cache (with preserve option). Warning ALG0047 “No_Connect“ property on pin ignored for : , ( , . Connecting pin to net A pin has the Is
38、 No Connect property enabled (checked) but there is a net connected to it. Either remove the net or disable the Is No Connect property. Error ALG0048 Conflicting values of “Power Pin Visibility“ found on and for part All sections of a multi-section part must have identical Power Pin Visibility value
39、s. These values can be changed in the property editor. Error ALG0049 Pin Number specified in “NC“ property also found on Pin If a net is attached to a pin number that is also listed as value of a NC property, then you get this error. The NC property value should be made up of pin numbers separated b
40、y commas. Here are three cases: If you have a part with six pins and all of them are connected to nets and you also have an NC property with value of “6,7,8“ then you will get an error for pin 6. If the NC property has a value of “18,19,18“ then youll get an error for pin 18. If “NC“ has “3“ where 3
41、 is also the pin number on O youll get an error for pin O. Error ALG0050 Duplicate Pin Name found on : , ( , A component contains more than one pin with the same logical name. You can fix this problem by selecting the part and choosing Edit Part from the pop-up menu. Choose Package from the View men
42、u, then Properties from the Edit menu. Change the value in the Name Normal column to the desired pin name. This error occurs if you have multiple ground or power pins with the same name but different pin numbers, and you make the power pins visible on the component. The PST*.DAT file format does not
43、 currently support this condition. However, it allows duplicate pin-names for invisible Power pins. So, you need to make the power pins invisible or give each one a different name, such as GND1 and GND2 instead of just GND. To update a large number of parts, run the library correction utility on lib
44、rary files, to correct duplicate pin names. You can then use these libraries in creating new designs. After correcting the libraries you will not encounter the ALG0050 error. Error ALG0051 Pin is renamed to after substituting illegal characters on : , ( , This message is flagged when the netlister d
45、etects: duplicate pin names per package. or a pin name with an illegal character, such as (a single quotation mark). In addition to flagging the message, Capture also renames the pin. You can use Library Correction utility to rename the pin names. This utility scans through all the parts in the libr
46、ary and identifies those components that have duplicate logical pin names. However, if a component has a duplicate Power pin, then that pin is not considered as duplicate by the Library Correction utility. Error ALG0052 Net has illegal Character “!“. Please rename the net A net name cannot contain i
47、llegal characters such as ! (the bang character). You must rename the net. Note the list of illegal characters on net names in the Capture - PCB Editor flow ; ! “ * along with any other character. This implies that * is a valid pin name but a*, *a and * are invalid. Unicode character set Also, cross
48、 probing (cross highlighting and cross selection) will not work for this part if you use a or a (back slash) in the net name. For more information, see the OrCAD Capture Users Guide. Error ALG0053 All pins are power : , ( , This error occurs if all pins are power pins (effectively a zero pin compone
49、nt where no pins are found in the Pin section of the part in PSTCHIP.DAT file). PCB Editor cant handle this kind of part yet. If you encounter this error, edit the part to contain at least one non-power type pin. Error ALG0054 Conflicting number of parts per package for : , ( , All the sections of the package with the reference are not the same. It appears that there is a section packaged incorrectly with the rest of the sections, possibly something like a 74LS00 got packaged with a 74LS04 gat
