Cadence® system design and verification solutions, integrated under our System Development Suite, provide the simulation, acceleration, emulation, and management capabilities.
System Development Suite Related Products A-Z
Cadence® digital design and signoff solutions provide a fast path to design closure and better predictability, helping you meet your power, performance, and area (PPA) targets.
Full-Flow Digital Solution Related Products A-Z
Cadence® custom, analog, and RF design solutions can help you save time by automating many routine tasks, from block-level and mixed-signal simulation to routing and library characterization.
Overview Related Products A-Z
Driving efficiency and accuracy in advanced packaging, system planning, and multi-fabric interoperability, Cadence® package implementation products deliver the automation and accuracy.
Cadence® PCB design solutions enable shorter, more predictable design cycles with greater integration of component design and system-level simulation for a constraint-driven flow.
An open IP platform for you to customize your app-driven SoC design.
Comprehensive solutions and methodologies.
Helping you meet your broader business goals.
A global customer support infrastructure with around-the-clock help.
24/7 Support - Cadence Online Support
Locate the latest software updates, service request, technical documentation, solutions and more in your personalized environment.
Cadence offers various software services for download. This page describes our offerings, including the Allegro FREE Physical Viewer.
Get the most out of your investment in Cadence technologies through a wide range of training offerings.
This course combines our Allegro PCB Editor Basic Techniques, followed by Allegro PCB Editor Intermediate Techniques.
Virtuoso Analog Design Environment Verifier 16.7
Learn learn to perform requirements-driven analog verification using the Virtuoso ADE Verifier tool.
Exchange ideas, news, technical information, and best practices.
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.
It's not all about the technlogy. Here we exchange ideas on the Cadence Academic Network and other subjects of general interest.
Cadence is a leading provider of system design tools, software, IP, and services.
Our CIP schematic symbols are not showing up. Just the ones in the supplied library. Everything works fine in 16.3 but we are trying to get the upgrade done.
In reply to oldmouldy:
I am assuming that you are speaking from generic experiance with upgrading OrCAD and have not actually done the 16.6 one.We have copied the appropriate lines in the Capture.ini file.
Our Channel Partner is also being stumped by this one so far. That is why I was asking if anyone has actually done it or seen this issue. Just trying to open up another channel of knowledge.
In reply to bill f:
Yes, and no, this configuration is fundamental to CIS, CIP just rides on the back of this. Just copying the Capture.ini file might not be too great an idea since the contents do change from version to version. From my standpoint, I would delete the Capture.ini from the new 16.6 location and let Capture rebuild a default, close Capture down, then copy the [Part Library Directories] section from the previous (16.3) Capture.ini and paste those entries into the newly created Capture.ini file for 16.6.
We are running CIP-E 4.002.0015 and "this just works" with our 16.6 installation.
OK, if you are running CIP 4.3, 4.003.0002, it seems to default to the "old" INI file location within the product installation. When Capture starts, check the INI file location that gets written to the session log, for now, this is the INI file that you need to get configured for your libraries. I guess that an update to CIP will be issued to get the 16.6 INI file locations supported.
Update: Too many chefs at the pot! The user "hacked" a 16.5 shortcut to reference 16.6, as a consequence, this picked up the INI file from the installation since the shortcut had a "-i <INI file in the installation>" switch. Therefore, I don't believe that there are any issues in this regard with the CIP installations, apologies to the EMA folks for any implied failing on their part.
I had this same problem and was led to this thread from a google search. This line "this is now stored at %HOME%\cdssetup\OrCAD_Capture\16.6.0 Close Capture CIS while you make the changes to the INI file." in the quoted post was exactly what I needed. However, I was confused by the %HOME% part of that file location and still had the same problem. So, if anyone else comes across this and is confused as I was, %HOME% in my case was "C:\SPB_Data\". Then, the rest of olymouldy's post is exactly correct.
So, to sum up: (in my case) my capture.ini file was located here: "C:\SPB_Data\cdssetup\OrCAD_Capture\16.6.0"
Hope this helps anyone else who may have seen olymouldy's post but was still slightly confused.
I am not trying to dis oldmoldy but we have tried all those things and this version is just being very weird. Our Channel Partner is also stumped with this and has asked Cadence for help, but they don't seem to be responding.I like the way you only need admin access to do the first install on the computer which then installs an "all user" configure program so that the actual user does not need admin access.
However something is flakey in Cadence's programming. I removed all copies of the Capture.ini, including all backups and renamed copies from the computer and networked locations it could go to, then started it regenerated the current version with directories listed and the most recent files I had accessed. It got it from somewhere that Cadence is not telling its partners about.
Looks like I am going to have to uninstall it and install 16.5 until someone from Cadence decides to come up with an answer. The person needs that computer to be useful.
I would recommend talking to EMA. They are responsible for CIP-E. I do have 16.6 and CIP-E v4.3 working.....
In reply to steve:
The CIP-E was not the issue, just included that for completeness of the system spec.
Did finally get the problem solved in a couple minutes when we FINALLY got a CIS database person involved.All the right lines were in the CAPTURE.INI file but the order of looking at directories was the problem. It needed to be opposite from what the first technician thought. He had passed it to Cadence for an answer but they never responded. It took a call to customer service to complain about an important issue (it would have been critical if we did not have the old installation on a machine that was being replaced.) taking weeks with no action.
Capture.ini has two locations ,one is in folder :\Cadence\SPB_16.6\tools\capture\
Capture.ini the Second is in :\Cadence\SPB_Data_16.6\cdssetup\OrCAD_Capture\16.6.0\Capture.ini
Compare the two files you can find that the second capture.ini file is more detail than the first one. you can backup the first capture.ini file and then delete it.then open the capture CIS you can find in the session log that the capture CIS use the second Capture.ini automaticlly.
in order to let capture CIS know where my library is and constraint
[Part Library Directories]
in :\Cadence\SPB_Data_16.6\cdssetup\OrCAD_Capture\16.6.0\Capture.ini before [Application] line
then save the file and restart capture CIS everything works fine.
In reply to sunscocool:
Whenever Capture starts it writes the capture.ini file location to the session log, so that's import to look for.
Another method is to open the command window and write GetIniPath.
I would also consider
Whenever you need to go into Capture (CIS) configuration on a company wide basis with version independent setup, you could take a look at
There's also a pdf document in English on that page.
In reply to Ejlersen: