Stats

  • State Not Answered
  • Replies 3
  • Subscribers 45
  • Views 11339
  • Members are here 0
More Content

Migrating designs from OrCAD capture 17.2 to OrCAD capture CIS 17.4.

KramYesoh

I want to migrate a number of designs from OrCAD capture 17.2 to OrCAD capture CIS 17.4.

Not too difficult. But my main aim is to replace all of the schematic components defined in local libraries with those that I’m creating in the CIS database.

My question might be a bit naïve but how do I go about doing that? I can't find anything in the user manual about it or any online tutorials or articles on the subject.

Is there a quick and efficient way to replace components, placed in the 17.2 schematic which has been loaded into 17.4 capture with CIS, with components in the CIS data base or is it a case of going through the migrated schematic component by component, deleting and replacing?

Oh what fun…….

Any help for a novice gratefully accepted.

Mark

Parents
  • 0

    It may depend on exactly what you want to do but, typically, the only requirement is Link the existing parts in the Schematic to the equivalent Parts in the CIS Database, basically adding the Part Number property from the Database. You can do this efficiently through the Part Manager, right-click on the DSN file entry in Project Manager, for instance, left-click the Value column to sort by Value, then you can left-click on the first entry for a Value and shift+left-click on the last entry for the Value and right-click>Link Database Part to open the CIS Explorer with a list of possible parts for the selected value, and select a Part and Link Database Part from there. In this way you can "bulk" link a number of Parts, rather than linking each Part individually. If you really want to replace the library paths used, not strictly necessary, you will need to open the Design Cache and start using Replace Cache on the Parts in the Design Cache but this probably isn't going to get you a great benefit for the effort expended.

Reply Children
No Data
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.