<?xml version="1.0" ?>
<MsgFile>
	<Msg>
		<Id>2000</Id>
		<Category>W</Category>
		<Desc>
			"The following COMP_INST_PROP property is being fed back.
        Property name: %s
        This property is present in compview.dat but not defined as a component instance property. 
        Add the property name to the COMP_INST_PROP directive in order for future runs of the Packager-XL to treat it correctly.
"
		</Desc>
		<ExtDesc>
			"Packager-XL requires certain properties that apply to reference designators or packages on your board to be specified as component instance properties. These properties include ROOM, REUSE_NAME, REUSE_INSTANCE, and REUSE_ID. If you do not include a component instance property in the Component Instance list in the Packager Setup - Properties tab, this warning message is displayed. Specify the property listed in the warning as a component instance property. This will ensure that all packages are assigned correct reference designators."
		</ExtDesc>
		<Output>C</Output>
	</Msg>
	<Msg>
		<Id>2004</Id>
		<Category>W</Category>
		<Desc>
			"Feedback instance has been deleted from the design.
        Feedback instance: %s
"
		</Desc>
		<ExtDesc>
			"When running Packager-XL in the Feedback mode, a warning may appear that a part has been deleted from the design. This warning is often followed with WARNING 2005. This warning may occur if you are migrating from PE 13.0 to a later release. Solution: Make sure that the design is fully in sync with PE 13.0. Next, switch to PSD 14.2. Finally, run Export Physical before running Import Physical."
		</ExtDesc>
		<Output>C</Output>
	</Msg>
	<Msg>
		<Id>2005</Id>
		<Category>W</Category>
		<Desc>
			"Instance has been added to the design.
        Design instance: %s
"
		</Desc>
		<ExtDesc>
			"When running Packager-XL in the Feedback mode, a warning may appear that a part has been added to the design. This warning is often preceded by WARNING 2004. This warning may occur if you are migrating from PE 13.0 to a later release. To address this warning, make sure that the design is fully in sync with PE 13.0. Next, switch to PSD 14.2. Finally, run Export Physical before running Import Physical."
		</ExtDesc>
		<Output>C</Output>
	</Msg>
	<Msg>
		<Id>2006</Id>
		<Category>W</Category>
		<Desc>
			"Net %s has been deleted from the design. The net might have been renamed in PCB Editor. Changed net names cannot be fed back to the schematic because net renaming from PCB Editor is not supported in Packager-XL. To avoid this, rename nets in Design Entry HDL and not in PCB Editor. Run Packager-XL in the Forward mode to transfer the net names to the board.
"
		</Desc>
		<ExtDesc>
			"This warning occurs when the schematic and board are not in sync. Before you run Packager-XL in the Feedback mode, ensure that you have first run Packager-XL in the Forward mode."
		</ExtDesc>
		<Output>C</Output>
	</Msg>
	<Msg>
		<Id>2007</Id>
		<Category>W</Category>
		<Desc>
			"Net has been added to the design.
        Net name: %s
        Physical net name: %s
        The net might have been renamed in PCB Editor. Changed net names cannot be fed back to the schematic because net renaming from PCB Editor is not supported in Packager-XL. To avoid this, rename nets in Design Entry HDL and not in PCB Editor. Run Packager-XL in the Forward mode to transfer the net names to the board.        
"
		</Desc>
		<ExtDesc>
			"When running Packager-XL in the Feedback mode, a warning may appear that a part has been added to the design. This warning is often preceded by WARNING 2006. Before you run Packager-XL in the Feedback mode, ensure that you have first run Packager-XL in the Forward mode."
		</ExtDesc>
		<Output>C</Output>
	</Msg>
	<Msg>
		<Id>2008</Id>
		<Category>I</Category>
		<Desc>
			"Net name: %s
"
		</Desc>
		<ExtDesc>
			""
		</ExtDesc>
		<Output>C</Output>
	</Msg>
	<Msg>
		<Id>2010</Id>
		<Category>I</Category>
		<Desc>
			"Feedback is changing %s from %s to %s.
        Design instance: %s
"
		</Desc>
		<ExtDesc>
			"This information displays when there is a change in the LOCATION property in PCB Editor. Packager-XL generates the above information and also displays the instance where the LOCATION property has changed."
		</ExtDesc>
		<Output>C</Output>
	</Msg>
	<Msg>
		<Id>2011</Id>
		<Category>I</Category>
		<Desc>
			"Feedback is changing SEC from %s to %s.
        Design instance: %s
"
		</Desc>
		<ExtDesc>
			"This information displays when you perform a section swap in PCB Editor causing a change in the SEC property. Packager-XL generates the above information and also displays the instance where the SEC property has changed."
		</ExtDesc>
		<Output>C</Output>
	</Msg>
	<Msg>
		<Id>2012</Id>
		<Category>I</Category>
		<Desc>
			"Feedback is changing PN from %s to %s.
        Design instance: %s
        Pin name: %s
"
		</Desc>
		<ExtDesc>
			"This information displays when you perform a pin swap in PCB Editor causing a change in the PN property. Packager-XL generates the above information and also displays the instance where the PN property has changed and the pin name that has changed."
		</ExtDesc>
		<Output>C</Output>
	</Msg>
	<Msg>
		<Id>2013</Id>
		<Category>I</Category>
		<Desc>
			"Design instance: %s
"
		</Desc>
		<ExtDesc>
			""
		</ExtDesc>
		<Output>C</Output>
	</Msg>
	<Msg>
		<Id>2014</Id>
		<Category>W</Category>
		<Desc>
			"Feedback instance: %s
"
		</Desc>
		<ExtDesc>
			""
		</ExtDesc>
		<Output>C</Output>
	</Msg>
	<Msg>
		<Id>2015</Id>
		<Category>I</Category>
		<Desc>
			"Pin name: %s
"
		</Desc>
		<ExtDesc>
			""
		</ExtDesc>
		<Output>C</Output>
	</Msg>
	<Msg>
		<Id>2016</Id>
		<Category>E</Category>
		<Desc>
			"Logical part is different between design and feedback.
        Design instance: %s
        Design logical part: %s
        Feedback logical part: %s
"
		</Desc>
		<ExtDesc>
			""
		</ExtDesc>
		<Output>C</Output>
	</Msg>
	<Msg>
		<Id>2019</Id>
		<Category>W</Category>
		<Desc>
			"Connectivity has changed between the design and feedback.
        Feedback changes to PN for the Pin %s have been ignored.
        Design instance: %s
"
		</Desc>
		<ExtDesc>
			"This warning is caused when there is a change in connectivity between the schematic and the layout. For example, it might be possible that there is a termination resistor on a net in the schematic that does not need a terminator in PCB Editor. Solution: Ensure that you place termination resistors ONLY on those nets in the schematic that are to be assigned a terminator. In Design Entry HDL, remove termination resistors from nets where they are wrongly assigned, then run Export Physical followed by Import Physical to ensure that the design goes through a front-to-back then a back-to-front flow. There may be times when the changes in connectivity are deliberate and you would like to retain those changes. You can use Design Association to feedback connectivity changes to the schematic. For more information about Design Association, see the documentation."
		</ExtDesc>
		<Output>C</Output>
	</Msg>
	<Msg>
		<Id>2023</Id>
		<Category>I</Category>
		<Desc>
			"Rejecting feedback value %s for property %s.
        Design value %s will be preserved.
        Object Name: %s
"
		</Desc>
		<ExtDesc>
			""
		</ExtDesc>
		<Output>C</Output>
	</Msg>
	<Msg>
		<Id>2025</Id>
		<Category>I</Category>
		<Desc>
			"Object Name: %s
"
		</Desc>
		<ExtDesc>
			""
		</ExtDesc>
		<Output>C</Output>
	</Msg>
	<Msg>
		<Id>2026</Id>
		<Category>E</Category>
		<Desc>
			"Feedback part %s is missing and the schematic instance cannot be updated with feedback key properties.
        Schematic instance: %s
        The part might have been added using a part table file that has been accidentally removed from the PPT directive during the feedback.
        Ensure the part added in the schematic exists and the appropriate part table files containing all the part definitions are specified in the PPT directive in the Part Table section of the Project Setup form.
"
		</Desc>
		<ExtDesc>
			"This error occurs when you have added a ppt part using a ptf file, which during the feedback phase, has been accidentally removed from the PPT directive or the ppt part added in the design is removed from the ptf file from which it was added before the properties have been fed back using Import Physical. To address this error, ensure that the ppt part added in a schematic is not altered or removed and the appropriate ptf files containing all part definitions are specified in the PPT directive in the Part Table section of the Project Setup form. The Import Physical procedure should have access to the ppt that will be used during feedback."
		</ExtDesc>
		<Output>C</Output>
	</Msg>
	<Msg>
		<Id>2028</Id>
		<Category>E</Category>
		<Desc>
			"Bad ppt name in feedback data: %s
        Ppt name must be: %s
        Schematic instance: %s
"
		</Desc>
		<ExtDesc>
			""
		</ExtDesc>
		<Output>C</Output>
	</Msg>
	<Msg>
		<Id>2030</Id>
		<Category>E</Category>
		<Desc>
			"Part %s is missing and the the schematic instance cannot be updated with feedback key properties.
        Schematic instance: %s
        The part might have been added using a part table file that has been accidentally removed from the PPT directive during the feedback.
        Ensure the part added in the schematic exists and the appropriate part table files containing all the part definitions are specified in the PPT directive in the Part Table section of the Project Setup form.
"
		</Desc>
		<ExtDesc>
			"The issue is caused by a space in a KEY property field in the part table. To resolve the issue, remove the space in the part table file and then use the part manager tool to update the parts in Design Entry HDL."
		</ExtDesc>
		<Output>C</Output>
	</Msg>
	<Msg>
		<Id>2031</Id>
		<Category>W</Category>
		<Desc>
			"Feedback is changing PACK_TYPE.
        Schematic PACK_TYPE: %s
        Feedback PACK_TYPE: %s
        Schematic instance: %s
"
		</Desc>
		<ExtDesc>
			""
		</ExtDesc>
		<Output>C</Output>
	</Msg>
	<Msg>
		<Id>2034</Id>
		<Category>W</Category>
		<Desc>
			"Multiple feedback instances match design instance.
        Feedback instance has been deleted from the design.
        Feedback instance: %s
        Design instance: %s
"
		</Desc>
		<ExtDesc>
			""
		</ExtDesc>
		<Output>C</Output>
	</Msg>
	<Msg>
		<Id>2035</Id>
		<Category>I</Category>
		<Desc>
			"Feedback is creating property %s.
"
		</Desc>
		<ExtDesc>
			""
		</ExtDesc>
		<Output>C</Output>
	</Msg>
	<Msg>
		<Id>2036</Id>
		<Category>I</Category>
		<Desc>
			"Feedback is updating property %s.
"
		</Desc>
		<ExtDesc>
			""
		</ExtDesc>
		<Output>C</Output>
	</Msg>
	<Msg>
		<Id>2037</Id>
		<Category>I</Category>
		<Desc>
			"Feedback is deleting property %s.
"
		</Desc>
		<ExtDesc>
			""
		</ExtDesc>
		<Output>C</Output>
	</Msg>
	<Msg>
		<Id>2038</Id>
		<Category>W</Category>
		<Desc>
			"Feedback change %s=%s for this %s ignored.
        Design value %s unchanged.
        Net name: %s
"
		</Desc>
		<ExtDesc>
			""
		</ExtDesc>
		<Output>C</Output>
	</Msg>
	<Msg>
		<Id>2039</Id>
		<Category>I</Category>
		<Desc>
			"Old value: %s
        New value: %s
"
		</Desc>
		<ExtDesc>
			""
		</ExtDesc>
		<Output>C</Output>
	</Msg>
	<Msg>
		<Id>2040</Id>
		<Category>I</Category>
		<Desc>
			"New value: %s
"
		</Desc>
		<ExtDesc>
			""
		</ExtDesc>
		<Output>C</Output>
	</Msg>
	<Msg>
		<Id>2042</Id>
		<Category>E</Category>
		<Desc>
			"Incorrect number of pins on feedback instance %s.
        Pins needed for part: %d. Pins on feedback instance %d.
        Phys Part Name: %s
        Feedback changes to PN for this instance have been ignored.
"
		</Desc>
		<ExtDesc>
			""
		</ExtDesc>
		<Output>C</Output>
	</Msg>
	<Msg>
		<Id>2044</Id>
		<Category>I</Category>
		<Desc>
			"HARD_LOC_SEC directive is set. Feedback is not changing %s from %s to %s.
        Design instance: %s
"
		</Desc>
		<ExtDesc>
			""
		</ExtDesc>
		<Output>C</Output>
	</Msg>
	<Msg>
		<Id>2045</Id>
		<Category>I</Category>
		<Desc>
			"HARD_LOC_SEC directive is set. Feedback is not changing SEC from %s to %s.
        Design instance: %s
"
		</Desc>
		<ExtDesc>
			""
		</ExtDesc>
		<Output>C</Output>
	</Msg>
	<Msg>
		<Id>2046</Id>
		<Category>I</Category>
		<Desc>
			"HARD_LOC_SEC directive is set. Feedback is not changing PN from %s to %s.
        Design instance: %s
        Pin name: %s
"
		</Desc>
		<ExtDesc>
			""
		</ExtDesc>
		<Output>C</Output>
	</Msg>
	<Msg>
		<Id>2047</Id>
		<Category>I</Category>
		<Desc>
			"The REUSE_NAME and REUSE_INSTANCE properties are set by front end tools only. Feedback is ignoring these properties.
"
		</Desc>
		<ExtDesc>
			""
		</ExtDesc>
		<Output>C</Output>
	</Msg>
	<Msg>
		<Id>2048</Id>
		<Category>W</Category>
		<Desc>
			"Feedback rejected for at least one %s, SEC or PN.

"
		</Desc>
		<ExtDesc>
			"This warning is caused whenever feedback from PCB Editor is rejected by Packager-XL. The warning is informational in nature and is generated only once for a design, regardless of the number of feedback rejections. The details of all rejected feedback values are generated as information messages in the pxl.log file. You may individually handle each rejected feedback."
		</ExtDesc>
		<Output>C</Output>
	</Msg>
	<Msg>
		<Id>2049</Id>
		<Category>E</Category>
		<Desc>
			"Feedback has found Illegal pin swap(s) for the instance %s.
		Pin Name: %s
"
		</Desc>
		<ExtDesc>
			""
		</ExtDesc>
		<Output>C</Output>
	</Msg>
	<Msg>
		<Id>2050</Id>
		<Category>E</Category>
		<Desc>
			"Too many tokens in line %d
        File Name: %s
        There must be %d tokens.
"
		</Desc>
		<ExtDesc>
			"This error is caused whenever any feedback file (compview.dat, pinview.dat, netview.dat, funcview.dat) has more tokens than required. Each feedback file uses an exclamation mark ( ! ) as a token to separate two properties in the same line. If you use more tokens than the one defined in the first line, this error occurs. To address this error, ensure that all lines in the feedback files have the same number of tokens. Avoid editing the feedback file because it may cause errors. Use File > Export > Logic in PCB Editor to generate the feedback files."
		</ExtDesc>
		<Output>C</Output>
	</Msg>
	<Msg>
		<Id>2052</Id>
		<Category>E</Category>
		<Desc>
			"! is not the last character on line %d
        File Name: %s
"
		</Desc>
		<ExtDesc>
			"Packager-XL expects the token ( ! ) to be the last character of each line of all feedback files. If you do not use the token ( ! ) as the last character of any line of a feedback file, such as pinview.dat, Packager-XL generates this error. To address this error, ensure that the token ( ! ) is used as the last character for each line of all feedback files."
		</ExtDesc>
		<Output>C</Output>
	</Msg>
	<Msg>
		<Id>2053</Id>
		<Category>E</Category>
		<Desc>
			"Too few tokens in line %d
        File Name: %s
        Only %d are found. %d required.
        The file might have been manually edited. Run the Import Physical command with the Generate Feedback File check box selected.
"
		</Desc>
		<ExtDesc>
			"This error is caused whenever any feedback file (compview.dat, pinview.dat, netview.dat, funcview.dat) has fewer tokens than required. Each feedback file uses the exclamation mark ( ! ) as a token that separates two properties in the same line. Ensure that all lines in the feedback files have the same number of tokens. Avoid editing the feedback file because it may cause errors. Use File > Export > Logic in PCB Editor to generate the feedback files."
		</ExtDesc>
		<Output>C</Output>
	</Msg>
	<Msg>
		<Id>2055</Id>
		<Category>W</Category>
		<Desc>
			"Unknown property type %s in file %s. Ignored
"
		</Desc>
		<ExtDesc>
			""
		</ExtDesc>
		<Output>C</Output>
	</Msg>
	<Msg>
		<Id>2056</Id>
		<Category>E</Category>
		<Desc>
			"Cannot feedback properties of type %s in %s.
"
		</Desc>
		<ExtDesc>
			"This error is generated when you are mixing releases, for example using Design Entry 13.6 and Packager 14.0. As a result, while backannotating the design, Packager-XL might corrupt the pxl.state file generating this error. This error may also occur if you have hand-edited the pxlBA.txt file. Ensure that you are not mixing releases. You may also delete the pxl.state file and re-package the design using the same Design Entry HDL version as that of PCB Editor."
		</ExtDesc>
		<Output>C</Output>
	</Msg>
	<Msg>
		<Id>2057</Id>
		<Category>I</Category>
		<Desc>
			"Ignoring feedback data for %s.
        It is specified as a NO_FEEDBACK property in the command file.
"
		</Desc>
		<ExtDesc>
			""
		</ExtDesc>
		<Output>C</Output>
	</Msg>
	<Msg>
		<Id>2059</Id>
		<Category>E</Category>
		<Desc>
			"Times property is in feedback file.
        Schematic instance: %s
        Ignoring line %d from feedback file %s
"
		</Desc>
		<ExtDesc>
			""
		</ExtDesc>
		<Output>C</Output>
	</Msg>
	<Msg>
		<Id>2061</Id>
		<Category>E</Category>
		<Desc>
			"Cannot find physical part %s
        Line Number: %d
"
		</Desc>
		<ExtDesc>
			""
		</ExtDesc>
		<Output>C</Output>
	</Msg>
	<Msg>
		<Id>2063</Id>
		<Category>E</Category>
		<Desc>
			"Package %s in %s refers to multiple physical parts.
        Line Number: %d
        Phys Part Name: %s
        Phys Part Name: %s
"
		</Desc>
		<ExtDesc>
			""
		</ExtDesc>
		<Output>C</Output>
	</Msg>
	<Msg>
		<Id>2064</Id>
		<Category>E</Category>
		<Desc>
			"Instance in pinView.dat refers to multiple packages.
        Schematic instance: %s
        Line Number: %d
        Packages: %s and %s
"
		</Desc>
		<ExtDesc>
			"This error occurs while backannotating a swap operation from Allegro PCB Editor on a design that uses resistor packs with the HAS_FIXED_SIZE property attached. Any schematic body with the HAS_FIXED_SIZE = n property is automatically assigned the SWAP_GROUP = x property in PCB Editor, where x is the logical path name to the schematic symbol in Design Entry HDL. Functions within the same swap group can be swapped with one another, but not outside the swap group. If the assigned SWAP_GROUP property is manually changed to override this limitation, the backannotation process breaks. To avoid this error, it is recommended that you use single resistor symbol versions instead of resistor packs."
		</ExtDesc>
		<Output>C</Output>
	</Msg>
	<Msg>
		<Id>2067</Id>
		<Category>E</Category>
		<Desc>
			"Pin %s is not valid for physPart %s
        File Name: %s
        Line Number: %d
"
		</Desc>
		<ExtDesc>
			""
		</ExtDesc>
		<Output>C</Output>
	</Msg>
	<Msg>
		<Id>2069</Id>
		<Category>E</Category>
		<Desc>
			"%s is required in each data line of %s Line Number: %d
		Regenerate the view files using Genfeedformat.

"
		</Desc>
		<ExtDesc>
			""
		</ExtDesc>
		<Output>C</Output>
	</Msg>
	<Msg>
		<Id>2070</Id>
		<Category>E</Category>
		<Desc>
			"%s must be specified in line %d of %s
        Cannot process pin %s on pkg %s connected to net.
        Physical net name: %s
"
		</Desc>
		<ExtDesc>
			"This error may occur if you try to change a part definition on the fly. For example, if you try to change a 9-pin part to an 11-pin part (by defining a pin count of 11 and adding a new JEDEC_TYPE in PCB Editor) and then backannotate the schematic, this error may occur. In such a scenario, you can do the following to avoid the problem: Make a local copy of the pxlBA.txt file. (This is for backup.) Add the following line after LOGICAL_PIN: FUNC_LOGICAL_PATH != '' Backannotate the schematic by creating new feedback files and generate back annotation files (run Import Physical). These steps will create a pinview.dat file without the power pins in it."
		</ExtDesc>
		<Output>C</Output>
	</Msg>
	<Msg>
		<Id>2072</Id>
		<Category>E</Category>
		<Desc>
			"Unexpected end of file for file %s
"
		</Desc>
		<ExtDesc>
			""
		</ExtDesc>
		<Output>C</Output>
	</Msg>
	<Msg>
		<Id>2073</Id>
		<Category>E</Category>
		<Desc>
			"The first line of %s has bad format. Must be:
        A!NET_NAME!REFDES!PIN_NUMBER!FUNC_LOGICAL_PATH!COMP_DEVICE_TYPE!
        and then be followed by any other user specific %s properties.
"
		</Desc>
		<ExtDesc>
			"This error occurs when you do not have the first line of the pinview.dat file in the standard format. Ensure that the first line of the pinview.dat file has the following format:
			A!NET_NAME!REFDES!PIN_NUMBER!FUNC_LOGICAL_PATH!COMP_DEVICE_TYPE!
			and that the following lines have any other user specific properties."
		</ExtDesc>
		<Output>C</Output>
	</Msg>
	<Msg>
		<Id>2074</Id>
		<Category>E</Category>
		<Desc>
			"The first line of %s has bad format.
        The line must begin with %s
        and then be followed by any other user specific %s properties.
        The file might have been manually edited. Run the Import Physical command with the Generate Feedback File check box selected.
"
		</Desc>
		<ExtDesc>
			"This error occurs when you do not begin the first line of the compview.dat file with A!REFDES! and then follow it with any other component properties that you may have defined. Ensure that the second line of all feedback lines begins with the J character."
		</ExtDesc>
		<Output>C</Output>
	</Msg>
	<Msg>
		<Id>2077</Id>
		<Category>E</Category>
		<Desc>
			"The second line of %s does not start with J. The line must begin with J
        The file might have been manually edited. Run the Import Physical command with the Generate Feedback File check box selected.
"
		</Desc>
		<ExtDesc>
			"This error occurs when you do not begin the second line of any feedback file, such as netview.dat or funcview.dat, with the J character. You may have accidentally put a carriage return and separated the first line into two lines. To address the error, ensure that the second line of all feedback lines begins with the J character."
		</ExtDesc>
		<Output>C</Output>
	</Msg>
	<Msg>
		<Id>2079</Id>
		<Category>I</Category>
		<Desc>
			"File not found %s. No feedback of %s properties.
"
		</Desc>
		<ExtDesc>
			""
		</ExtDesc>
		<Output>C</Output>
	</Msg>
	<Msg>
		<Id>2080</Id>
		<Category>E</Category>
		<Desc>
			"Feedback failed because %s file is missing. To complete feedback from PCB Editor, Packager-XL requires four feedback files: pinview.dat, netview.dat, compview.dat, and funcview.dat. Generate the feedback files from the Import Physical dialog box.
"
		</Desc>
		<ExtDesc>
			"Packager-XL requires four feedback files to complete feedback from PCB Editor. These files are pinview.dat, netview.dat, compview.dat, and funcview.dat. If the pinview.dat file is not present in the packaged view, this error appears. Ensure that the pinview.dat file is in the packaged view of the design. Generate the feedback files from the Import Physical dialog box."
		</ExtDesc>
		<Output>C</Output>
	</Msg>
	<Msg>
		<Id>2081</Id>
		<Category>E</Category>
		<Desc>
			"Error generating physical net names for design.
"
		</Desc>
		<ExtDesc>
			""
		</ExtDesc>
		<Output>C</Output>
	</Msg>
	<Msg>
		<Id>2082</Id>
		<Category>E</Category>
		<Desc>
			"Cannot find %s in feedback view.
        Name: %s
        File Name: %s
        Ignoring line: %d
"
		</Desc>
		<ExtDesc>
			"This error occurs if there are parts on the board that no longer exist in the schematic. When you backannotate the schematic from the board to the schematic, it results in this error. To address this error, backannotate data from the board to the schematic to include any changes from the board before you make any modifications to the schematic. You should then make the required changes to the schematic and forward annotate to bring the board in sync."
		</ExtDesc>
		<Output>C</Output>
	</Msg>
	<Msg>
		<Id>2084</Id>
		<Category>E</Category>
		<Desc>
			"Expected an HDL-centric %s file.
        The following non HDL-centric instance name was found on line %d:
        Name: %s
"
		</Desc>
		<ExtDesc>
			""
		</ExtDesc>
		<Output>C</Output>
	</Msg>
	<Msg>
		<Id>2086</Id>
		<Category>E</Category>
		<Desc>
			"New component with reference designator %s found on board.
        The given location value is also present in schematic design.
        This is not allowed when REUSE_REFDES directive is set to OFF.
        Rename one of the reference designators.
"
		</Desc>
		<ExtDesc>
			""
		</ExtDesc>
		<Output>C</Output>
	</Msg>
  <Msg>
    <Id>2087</Id>
    <Category>E</Category>
    <Desc>
      "Not all the Pins were swapped because some instances were not instantiated in the logic design.
        "
      </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
	<Msg>
		<Id>2103</Id>
		<Category>I</Category>
		<Desc>
			"Value: %s
"
		</Desc>
		<ExtDesc>
			""
		</ExtDesc>
		<Output>C</Output>
	</Msg>
	<Msg>
		<Id>2150</Id>
		<Category>E</Category>
		<Desc>
			"Packaging cannot be completed because packager has encountered a null object ID. The design may not have been saved correctly. Save the schematic and rerun packaging.
"
		</Desc>
		<ExtDesc>
			""
		</ExtDesc>
		<Output>C</Output>
	</Msg>
	<Msg>
		<Id>2151</Id>
		<Category>E</Category>
		<Desc>
			"Object must be a %s in call to %s.
"
		</Desc>
		<ExtDesc>
			""
		</ExtDesc>
		<Output>C</Output>
	</Msg>
	<Msg>
		<Id>2152</Id>
		<Category>W</Category>
		<Desc>
			"Feedback change %s=%s for this %s ignored.
        Design value %s unchanged.
        Design instance: %s
"
		</Desc>
		<ExtDesc>
			""
		</ExtDesc>
		<Output>C</Output>
	</Msg>
	<Msg>
		<Id>2153</Id>
		<Category>W</Category>
		<Desc>
			"Feedback change %s=%s for this %s ignored.
        Design value %s unchanged.
        Pin name: %s
        Design instance: %s
"
		</Desc>
		<ExtDesc>
			""
		</ExtDesc>
		<Output>C</Output>
	</Msg>
	<Msg>
		<Id>2154</Id>
		<Category>W</Category>
		<Desc>
			"Connectivity has changed between the design and feedback. 
		Feedback changes to pin for this instance have been ignored.
		Design instance: %s 
		The pin numbers for logical pins might have got interchanged in chips.prt. Load the part in Part Developer and correct the pin numbers for the interchanged pins. 
		Or, run Export Physical to update the board with the corrected pin numbers for the interchanged pins before bringing the board data to the schematic.
"
		</Desc>
		<ExtDesc>
			""
		</ExtDesc>
		<Output>C</Output>
	</Msg>
	<Msg>
		<Id>2155</Id>
		<Category>I</Category>
		<Desc>
			"Feedback is changing SEC from %s to %s.
        Design instance: %s
        Pin name: %s
"
		</Desc>
		<ExtDesc>
			""
		</ExtDesc>
		<Output>C</Output>
	</Msg>
	<Msg>
		<Id>2156</Id>
		<Category>I</Category>
		<Desc>
			"Feedback is updating property %s.
        Design instance: %s
        Old value: %s
        New value: %s
"
		</Desc>
		<ExtDesc>
			""
		</ExtDesc>
		<Output>C</Output>
	</Msg>
	<Msg>
		<Id>2157</Id>
		<Category>I</Category>
		<Desc>
			"Feedback is creating property %s.
        Design instance: %s
        Value: %s
"
		</Desc>
		<ExtDesc>
			""
		</ExtDesc>
		<Output>C</Output>
	</Msg>
	<Msg>
		<Id>2158</Id>
		<Category>W</Category>
		<Desc>
			"NET_SHORT property is not same on all the pins of the instance '%s'. It must be specified with same value on all the pins.
"
		</Desc>
		<ExtDesc>
			""
		</ExtDesc>
		<Output>C</Output>
	</Msg>
</MsgFile>

