Stats

  • State Not Answered
  • Replies 8
  • Subscribers 44
  • Views 7506
  • Members are here 0
More Content

Linking database parts in a design originally created in an older version of Capture is very slow

mbmsv

A while ago I asked a question about a problem with linking database parts in Capture CIS 17.4. 

I have now definitively concluded that the problem is specific to the design I am working on. This design is based on a Xilinx reference design and the problem is present even in the unmodified reference design. I tried a different but similar Xilinx reference design and linking database parts in it is at least three times faster. It is still slow but it proves that the problem is with the design. One obvious difference between the two reference designs is that they were created with different OrCAD versions. I believe the one I used originally was created with OrCAD 16.6, and another one it seems with 17.2. So, why linking database parts works so slow in a design that was created in 16.6? I tried exporting the design to XML and EDIF formats and importing it back in a hope that that would clean it somehow but that didn't help. Any ideas would be highly appreciated. As it stands now, being productive when working with this design is basically impossible.

Thanks

  • 0

    The DSN file structure has not changed in forever.   

    17.4/22.1 should be universally faster as a rewrite to a 64-bit app compared to 16.6 that I have to keep running.   

    16, 17, 22 have separate Capture.INI files/file history so I have easier access to my OLB files to build new parts.

  • 0 in reply to Robert Finley

    OK, perhaps the version has nothing to do with it. It was just a guess. What else could be the cause of the issue? The design must be corrupted in some mysterious way. If someone is willing to test it, here is a link to the reference design in question: https://www.xilinx.com/member/forms/download/design-license.html?cid=bb488d1f-e81d-4316-b56d-49670e050702&filename=zcu111-schematic-source-rdf0464.zip (an account is required to download it). After opening the design go to a decoupling page, select 10 identical capacitors and try linking them to a database part. How long did it take? How long should it take?

  • 0 in reply to mbmsv

    Thanks for the link to the design.

    CIS can capture large designs.  An old Gateway laptop repair manual can attest to that.

    Ultimately, even with faster computers, there are efficient ways and less efficient ways to search and update large data sets.   

    The lazy side of me would note that CIS supports adding the CIS part number property manually to multiple instances on the schematic. Select multiple symbols, "Edit Properties", select the CIS PN property row of fields allowing you to update one CIS Part number then propagate across selected instances.  Save.  Trigger Part Manager Update to force part properties to match CIS.   

    Another option might be to open your dsn, select it under design resources.  Select >Tools >Export Properties.  Chang the *.EXP extension to *.txt.  You can open it using microsoft Excel.   The idea is make edits in excel then Orcad has >Import Properties.  But, I haven't tried that yet.

    Adding a new CIS capacitor instance then copying it might be fast.  But, re-placing them in layout if the refdes changed sounds painful

  • 0 in reply to Robert Finley

    The problem is that I have another issue that was caused by me experimenting with the capacitor symbol and making extra properties visible, and then experimenting with different font sizes and positions for them. It turned out that the schematics part of Capture doesn't agree with the symbol editor and if you try to use a different font size in the symbol it will be messed up in the schematics later. If you edit the property position in the symbol and update the symbol you end up with the property being displayed in both old and new positions. Strangely enough, everything seems to work when you place the component first time but then if you go back and change something in the symbol it all gets messed up and the only way to clean it is to re-link the database parts while having the checkbox for replacing the part 's schematic graphical representation and visible property locations checked. I don't think the methods you are proposing would help with that. Note also, that the linking time doesn't depend on this checkbox. 

  • 0 in reply to mbmsv

    Ok.  I was operating on the assumption you needed to link a schematic to your CIS database to export a BOM.

    Wondering if you have multiple library capacitor symbols in the design causing slowdowns.  

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.