• 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. Allegro X PCB Editor
  3. Schematics and PCB don't seem properly linked

Stats

  • State Verified Answer
  • Replies 4
  • Subscribers 160
  • Views 2111
  • Members are here 0
More Content

Schematics and PCB don't seem properly linked

AL202512303326
AL202512303326 7 months ago

I got handed over a PCB project, I have the parts libraries, schematics and the PCB. The PCB and schematics seem to only semi-correspond to each other: I can cross-probe all nets that I tried, didn't try them all) and some components, but not all of them. So I tried to sync up the SCH and the PCB, and no matter what I tried, around 180 components would always disappear from the board and would have to be placed manually again. At the same time, some of the constraints (most notably, for routing diff. pairs) would stop working. The same thing happens if I try to use the Update PCB button, or if I export a netlist from the SCH and import into the PCB. I can see no logic as to which components disappear (they are not the same ones as the ones I cannot cross-probe), but it's always the same amount, and always the same ones. 

The closest I got to stuff not going whack is by fixing/locking a few components I know would disappear, and then trying to update the PCB while unticking the "ignore FIXED propery" checkmark. In this case, the update wouldn't happen, and I would get thrown a message saying "Error processing 'C101': Cannot modify element; the object or a parent has the FIXED property.", then "Run stopped because errors were detected", then the whole process, well, stopping. 

Any tips as to why this might happen? Maybe some file got missed in the handover (it was remote, I just got handed a bunch of stuff), and I should ask for it?

TRANSLATE with x
English
Arabic Hebrew Polish
Bulgarian Hindi Portuguese
Catalan Hmong Daw Romanian
Chinese Simplified Hungarian Russian
Chinese Traditional Indonesian Slovak
Czech Italian Slovenian
Danish Japanese Spanish
Dutch Klingon Swedish
English Korean Thai
Estonian Latvian Turkish
Finnish Lithuanian Ukrainian
French Malay Urdu
German Maltese Vietnamese
Greek Norwegian Welsh
Haitian Creole Persian
TRANSLATE with
COPY THE URL BELOW
Back
EMBED THE SNIPPET BELOW IN YOUR SITE
Enable collaborative features and customize widget: Bing Webmaster Portal
Back
  • Sign in to reply
  • Cancel
Parents
  • avant
    0 avant 7 months ago

    When importing the netlist, make sure the "always place changed component' box is checked.

    I noticed this starting with Allegro version 17.4

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • AL202512303326
    0 AL202512303326 7 months ago in reply to avant

    Sadly that didn't solve the problem, I still have the same components misbehaving. I also tried placing a few of them, then re-importing the netlist, and the same components disappeared again. 

    TRANSLATE with x
    English
    Arabic Hebrew Polish
    Bulgarian Hindi Portuguese
    Catalan Hmong Daw Romanian
    Chinese Simplified Hungarian Russian
    Chinese Traditional Indonesian Slovak
    Czech Italian Slovenian
    Danish Japanese Spanish
    Dutch Klingon Swedish
    English Korean Thai
    Estonian Latvian Turkish
    Finnish Lithuanian Ukrainian
    French Malay Urdu
    German Maltese Vietnamese
    Greek Norwegian Welsh
    Haitian Creole Persian
    TRANSLATE with
    COPY THE URL BELOW
    Back
    EMBED THE SNIPPET BELOW IN YOUR SITE
    Enable collaborative features and customize widget: Bing Webmaster Portal
    Back
    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • avant
    +1 avant 7 months ago in reply to AL202512303326

    One thing that may be a quick fix is to export the component placement file, import the netlist, and then import the component placement file.

    • Cancel
    • Vote Up +1 Vote Down
    • Sign in to reply
    • Reject Answer
    • Cancel
Reply
  • avant
    +1 avant 7 months ago in reply to AL202512303326

    One thing that may be a quick fix is to export the component placement file, import the netlist, and then import the component placement file.

    • Cancel
    • Vote Up +1 Vote Down
    • Sign in to reply
    • Reject Answer
    • Cancel
Children
  • AL202512303326
    0 AL202512303326 7 months ago in reply to avant

    Yep, that worked. Not sure what's causing the issue, but this workaround saved me so much headache! Thank you! 

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • 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