Stats

  • Locked Locked
  • Replies 12
  • Subscribers 168
  • Views 26604
  • Members are here 0
More Content
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Allegro Extra pins and Missing Pins

salasidis

I am new to Allegro, and have a problem with PCB Footprints for certain components.

 

For example,

 

A) one component mounts on a Dip16 footprint, but only has 4 pins (pin 1,8,9,16).

 

B) A diode uses a SOT-23 package with 3 pins, but only 2 pins are required.

 

How does one force Allegro to ignore missing pins in the schematic that are not required (example A).

 

I have "fixed" this by defining in my Orcad CIS part schematic invisible zero length pins that are not required (ie define the other 12 pins in example A, or create a new diode symbol with an extra unused pin.

 

Is there a better way?

 

 

(netrev.lst output below

 

ERROR(SPMHNI-196): Symbol 'SOT65P210X110-3N' for device 'DIODE TS_SOT65P210X110-3N_DISCR' has extra pin '3'.

#2   WARNING(SPMHNI-192): Device/Symbol check warning detected.

ERROR(SPMHNI-196): Symbol 'DIP16' for device 'CPC1945G_DIP16_DISCRETE_CPC1945' has extra pin '2'.

ERROR(SPMHNI-196): Symbol 'DIP16' for device 'CPC1945G_DIP16_DISCRETE_CPC1945' has extra pin '3'.

ERROR(SPMHNI-196): Symbol 'DIP16' for device 'CPC1945G_DIP16_DISCRETE_CPC1945' has extra pin '4'.

ERROR(SPMHNI-196): Symbol 'DIP16' for device 'CPC1945G_DIP16_DISCRETE_CPC1945' has extra pin '5'.

ERROR(SPMHNI-196): Symbol 'DIP16' for device 'CPC1945G_DIP16_DISCRETE_CPC1945' has extra pin '6'.

ERROR(SPMHNI-196): Symbol 'DIP16' for device 'CPC1945G_DIP16_DISCRETE_CPC1945' has extra pin '7'.

ERROR(SPMHNI-196): Symbol 'DIP16' for device 'CPC1945G_DIP16_DISCRETE_CPC1945' has extra pin '9'.

ERROR(SPMHNI-196): Symbol 'DIP16' for device 'CPC1945G_DIP16_DISCRETE_CPC1945' has extra pin '11'.

ERROR(SPMHNI-196): Symbol 'DIP16' for device 'CPC1945G_DIP16_DISCRETE_CPC1945' has extra pin '12'.

ERROR(SPMHNI-196): Symbol 'DIP16' for device 'CPC1945G_DIP16_DISCRETE_CPC1945' has extra pin '13'.

ERROR(SPMHNI-196): Symbol 'DIP16' for device 'CPC1945G_DIP16_DISCRETE_CPC1945' has extra pin '14'.

ERROR(SPMHNI-196): Symbol 'DIP16' for device 'CPC1945G_DIP16_DISCRETE_CPC1945' has extra pin '15'.

Parents
  • salasidis

    Thanks, but could you please tell me where to set the NC propery. I looked within Allegro 'Display' 'Property' but could not find an NC entry.

     

    I would think creating a new footprint with the NC= for the pins not used would be easiest

     

    I tried adding an NC property within the part properties of Capture, but this has not worked, I still get the same netrev.lst message (I tried it for the Dip16 part)

     

    Addendum: I managed to get the DIP16 to work with an NC parameter added to teh capture side (not sure why it did not work the first time).

     However if I try making a new footprint with a DIP16 layout but only 4 pins defined (1,8,10,16) to match the capture, I still get the error message about the missing pins. Do the PCB Footprint pins have to be in a linear order (ie no skipped numbers)

Reply
  • salasidis

    Thanks, but could you please tell me where to set the NC propery. I looked within Allegro 'Display' 'Property' but could not find an NC entry.

     

    I would think creating a new footprint with the NC= for the pins not used would be easiest

     

    I tried adding an NC property within the part properties of Capture, but this has not worked, I still get the same netrev.lst message (I tried it for the Dip16 part)

     

    Addendum: I managed to get the DIP16 to work with an NC parameter added to teh capture side (not sure why it did not work the first time).

     However if I try making a new footprint with a DIP16 layout but only 4 pins defined (1,8,10,16) to match the capture, I still get the error message about the missing pins. Do the PCB Footprint pins have to be in a linear order (ie no skipped numbers)

Children
No Data
Cadence Guidelines

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.