Home > Community > Forums > PCB Design > ERROR(SPMHNI-196)

Email

* Required Fields

Recipients email * (separate multiple addresses with commas)

Your name *

Your email *

Message *

Contact Us

* Required Fields
First Name *

Last Name *

Email *

Company / Institution *

Comments: *

 ERROR(SPMHNI-196) 

Last post Thu, Apr 25 2013 10:35 AM by BillZ. 1 replies.
Started by joshuad 25 Apr 2013 09:46 AM. Topic has 1 replies and 664 views
Page 1 of 1 (2 items)
Sort Posts:
  • Thu, Apr 25 2013 9:46 AM

    • joshuad
    • Not Ranked
    • Joined on Thu, Apr 25 2013
    • Posts 1
    • Points 20
    ERROR(SPMHNI-196) Reply

    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. 

    Filed under: ,
    • Post Points: 20
  • Thu, Apr 25 2013 10:35 AM

    • BillZ
    • Top 75 Contributor
    • Joined on Thu, Jul 17 2008
    • Rochester, NY
    • Posts 94
    • Points 1,245
    Re: ERROR(SPMHNI-196) Reply

    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;}
    • Post Points: 5
Page 1 of 1 (2 items)
Sort Posts:
Started by joshuad at 25 Apr 2013 09:46 AM. Topic has 1 replies.