Stats

  • Locked Locked
  • Replies 4
  • Subscribers 166
  • Views 16148
  • 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

Component Device Pin Number Mismatch; Cannot Replace

EASiA

Hi All,

I have been trying to translate a board made in Altium to OrCAD. When making the Netlist, I received the warning:

#3 WARNING(SPMHNI-184): Device library warning detected.

WARNING: U11 component device pin number mismatch; cannot replace.

The part is a simple 4 pin regulator. Both the schematic symbol and the PCB symbol have 4 pins, as far as I can tell. How can I resolve this?

Parents

  • Obviously the Altium part is 'pin labelled' different than the Orcad footprint. The Altium netlist should be editable (e.g. text file), so look up U11 in the file and see what they label the pins as (maybe like 1A. 1B, 2A, 2B?). Then map the U11 footprint accordingly.

  • in reply to CadAce2K

    Hi , I did not fully understand what you meant. I was finally able to understand that even though I made the schematic symbol have 4 pins, I did not label the number correctly for it to match the current footprint that was made. I mistook pin number mismatch to be amount and not a label of sorts. I understand now that device pin number mismatch means that the number label of the symbols and footprints have to match and not meaning the amount of pins.

Reply
  • in reply to CadAce2K

    Hi , I did not fully understand what you meant. I was finally able to understand that even though I made the schematic symbol have 4 pins, I did not label the number correctly for it to match the current footprint that was made. I mistook pin number mismatch to be amount and not a label of sorts. I understand now that device pin number mismatch means that the number label of the symbols and footprints have to match and not meaning the amount of pins.

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.