Stats

  • Locked Locked
  • Replies 1
  • Subscribers 164
  • Views 6566
  • 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

Importing OrCAD Capture 16.6 into Capture 16.2 using EDF Importation

ctocci

Hi,

Thought I had a solution, but NO!  Friend has OrCAD 16.6 Capture and has a fairly hierachial schematic.  So I had him export to an EDF format which worked fine.  However, when I got it, I could import the EDF Capture file, but lost all of the reference designation information.  I DID get ref des info, but it appears to have have started at number "1" on each page and there are 45 pages!!  Needless to say, this causes a severe problem if I am to synchronize the 16.6 Allegro using 16.2 Allegro for corrections.  Right now, due to the schematic have all kinds of DRC errors with duplicate references, etc.  I am stuck.

Any ideas out there?  Or is this a "bridge to far" going between OrCAD 16.6 to OrCAD 16.2 via the EDF translator?

Chris

  • oldmouldy
    Yes, "EDIF Interchange" is not going to work for hierarchical designs but there is absolutely no need to do this since Capture has File>Save As where you can change the "Files of Type" to 16.2 DSN format, which will remove the post-16.2 elements, and then use File>Open>Design in 16.2 with the created DSN file. You may have issues related to Net Groups in the 16.6 design since 16.2 didn't have these and no equivalent.
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.