Home
  • Products
  • Solutions
  • Support
  • Company
  • Products
  • Solutions
  • Support
  • Company
Community PCB Design & IC Packaging (Allegro X) PCB Design 17.4 Design Sync Fails without providing errors

Stats

  • Locked Locked
  • Replies 8
  • Subscribers 174
  • Views 7965
  • 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

17.4 Design Sync Fails without providing errors

DDPCB
DDPCB over 1 year ago

As the title suggests I am unable to perform design sync between OrCAD Capture and Allegro. When I add a layout and try to sync to it I am given ERROR(ORCAP-2426): Cannot run Design Sync because of errors. See session log for error details.

Session Log

[ORPCBFLOW] : Invoking ECO dialog.
INFO(ORNET-1176): Netlisting the design
INFO(ORNET-1178): Design Name:
C:\USERS\DDOYLE\DOCUMENTS\CADENCE\BOARDS\REMOTE POWER DEVICE\CAPTURE\REMOTE_POWER_DEVICE.DSN
Netlist Directory:
c:\users\ddoyle\documents\cadence\boards\remote power device\layout\allegro
Configuration File:
C:\Cadence\SPB_17.4\tools/capture/allegro.cfg
pstswp.exe - pst - d "C:\USERS\DDOYLE\DOCUMENTS\CADENCE\BOARDS\REMOTE POWER DEVICE\CAPTURE\REMOTE_POWER_DEVICE.DSN"- n "c:\users\ddoyle\documents\cadence\boards\remote power device\layout\allegro" - c "C:\Cadence\SPB_17.4\tools/capture/allegro.cfg" - v 3 - l 31 - s "" - j "PCB Footprint" - hpath "HPathForCollision"
Spawning... pstswp.exe - pst - d "C:\USERS\DDOYLE\DOCUMENTS\CADENCE\BOARDS\REMOTE POWER DEVICE\CAPTURE\REMOTE_POWER_DEVICE.DSN"- n "c:\users\ddoyle\documents\cadence\boards\remote power device\layout\allegro" - c "C:\Cadence\SPB_17.4\tools/capture/allegro.cfg" - v 3 - l 31 - s "" - j "PCB Footprint" - hpath "HPathForCollision"
{ Using PSTWRITER 17.4.0 d001Dec-14-2021 at 09:00:49 }

INFO(ORCAP-36080): Scanning netlist files ...

Loading... c:\users\ddoyle\documents\cadence\boards\remote power device\layout\allegro\pstchip.dat

Loading... c:\users\ddoyle\documents\cadence\boards\remote power device\layout\allegro\pstchip.dat

Loading... c:\users\ddoyle\documents\cadence\boards\remote power device\layout\allegro\pstxprt.dat

Loading... c:\users\ddoyle\documents\cadence\boards\remote power device\layout\allegro\pstxnet.dat
packaging the design view...
Exiting... pstswp.exe - pst - d "C:\USERS\DDOYLE\DOCUMENTS\CADENCE\BOARDS\REMOTE POWER DEVICE\CAPTURE\REMOTE_POWER_DEVICE.DSN"- n "c:\users\ddoyle\documents\cadence\boards\remote power device\layout\allegro" - c "C:\Cadence\SPB_17.4\tools/capture/allegro.cfg" - v 3 - l 31 - s "" - j "PCB Footprint" - hpath "HPathForCollision"
INFO(ORNET-1179): *** Done ***

This issue started to occur after I changed parts that exist on previously created PCBs. I changed the following leading up to this:

1. Added height in Allegro to many of my components using the Setup->Area->Package Height tool.

2. Changed the reference designator category in OrCAD Capture to TP for several components on board.

Any advice here would be most welcome. Thanks!

  • Cancel
  • DDPCB
    DDPCB over 1 year ago in reply to steve

    When I attempt to use the New Layout functionality OrCAD Capture crashes (hangs indefinitely until forced close). This occurs with various combinations of Input Board and Board (including your suggestion of using the one board file for both fields). This also happens if I use the default board directory or the directory for the layout of this board. Currently trying to get the most up to date hotfix but have to call the support number for assistance so I can properly log in with my company license so will be some time.

    I am currently on version 17.4-2019 P001 for reference (not sure if that would cause this).

    • Cancel
    • Up 0 Down
    • Cancel
  • steve
    steve over 1 year ago in reply to DDPCB

    That's the base release (original release) so I'm not surprised you are seeing issues. Once the latest version is installed that should resolve your issues.

    • Cancel
    • Up +1 Down
    • Cancel
  • DDPCB
    DDPCB over 1 year ago in reply to steve

    Updating to a more recent hotfix has solved the issue! Thanks Rex...I mean Steve!

    • Cancel
    • Up 0 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.

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

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