• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. PCB Design
  3. ERROR(SPMHNI-196)

Stats

  • Locked Locked
  • Replies 1
  • Subscribers 165
  • Views 5301
  • 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

ERROR(SPMHNI-196)

joshuad
joshuad over 12 years ago

Background: I am a complete novice to PCB design with almost no knowledge in this field so please excuse my ignorance, but the task is relatively simple: make a board that changes from one type of connector to another (CHAMP-68 pin to DB37). Basically two pins from the CHAMP-68 converge into one pin on the DB37 (it's for cable testing purposes). No parts on the board, nothing. I am largely relying on experimentation and youtube videos for training.

Problem: I believe I have the schematic how it should be, with the proper parts, but when I import it into OrCAD PCB Designer Professional, I get this error:

ERROR(SPMHNI-196): Symbol 'DB_RA_P-37' for device 'CONNECTOR DB37 MALE_DB_RA_P-37_' has extra pin 'M1'.

ERROR(SPMHNI-196): Symbol 'DB_RA_P-37' for device 'CONNECTOR DB37 MALE_DB_RA_P-37_' has extra pin 'M2'. 

After some research, I realized that M1 and M2 are supposed to be mechanical pins on the DB37 (used to mount the connector to the board). After looking at the footprint for the DB37, it seems to suggest that M1 and M2 are simply pins on the footprint, however I am not adept at this so I couldn't be certain. So I'm at a loss on how to get this to work properly, as it won't let me place the parts yet. I've tried adding the NC property to the schematic with "M1, M2" with the value, I've tried adding M1 and M2 as 'no-connect' pins on the schematic itself. It seems like might be one thing that might make the error go away - if I could make M1 and M2 show up as mechanical pins, I read that might fix the error. However I'm uncertain on how to do this. It seems like there should be an easy way to convert them, and the only thing my google-fu turned up was that if you delete the text then it should convert them to mechanical pins, but I don't see any text and I can't find any (editable) properties that might suggest this change. I don't think deleting the pins off the footprint and recreating them is the best option, but if it's necessary I can certainly try - I'm simply worried I won't get the dimensions/location right.

So how do I fix this?

Thanks in advance for any help. 

  • Cancel
  • BillZ
    BillZ over 12 years ago

    Hi

    When netlisting between Capture and PCB editor the total pin count has to match. If the package symbol (footprint) has 39 connect pins, the Capture part has to have 39 pins. Mechanical pins in the package symbol do not count. When you add pins in the package symbol you can choose to add then as connect or mechanical in the Options Tab. You can convert a connect pin to a mechanical by deleting the pin number. The pin number is text so Edit>Delete set the find filter to text and select the text to delete, select another pin or Right Mouse Done.  

     

    BillZ

    EMA Design Automation

    Normal 0 false false false EN-US X-NONE X-NONE /* Style Definitions */ table.MsoNormalTable {mso-style-name:"Table Normal"; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-priority:99; mso-style-parent:""; mso-padding-alt:0in 5.4pt 0in 5.4pt; mso-para-margin-top:0in; mso-para-margin-right:0in; mso-para-margin-bottom:10.0pt; mso-para-margin-left:0in; line-height:115%; mso-pagination:widow-orphan; font-size:11.0pt; font-family:"Calibri","sans-serif"; mso-ascii-font-family:Calibri; mso-ascii-theme-font:minor-latin; mso-hansi-font-family:Calibri; mso-hansi-theme-font:minor-latin;}
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
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.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information