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.
I'm currently designing a Class-D output stage and I have come across some
minor problems with the configuration with two of my measurement, namely FFT and THD.
As I always know the frequency(s) of my input signal I wanted to configure the FFT and the
THD measurement to always fit to the period of the output signal. So I defined two variables,
one for the start of the interval and one for the stop, both are integer multiples of the period.
I included those design variables into my measurements as discribed in a different post in this
forum using the desVar() function. For THD this yields in
thd(v("/outp" ?result "tran") desVar("startint") desVar("stopint") 16384 desVar("sigfreq")
for FFT I used the same syntax.
However both measurements do not work. I checked a lot of other measurements with the
desVar() method, they all work fine.
Anyone out there with some pointers ?
You probably should use the VAR() function, not the desVar() function. desVar returns a string, and that's not what you want here... (I'm surprised it works elsewhere).
In reply to Andrew Beckett:
Thanks for the hint, however it's still not working.
What I have tried:
I use the same set of three variables
sigfreq = 256k
startint = 5u
stopint = startint+5*1/sigfreq
thd(v(.....) 5u 24.531u 36000 256000)
I replaced the frequeny setting 256k for the THD measurement with VAR("sigfreq") -> Measurement evaluates fine
If I replace the starttime with VAR("startint") the measurement already fails,
drForwardFFT: argument #2 should be a number
What can I do now ?
In reply to baenischfau:
You should report this to customer support. You shouldn't have to do this, but it may well fix it if you change your:
thd(v(...) VAR("startint") 24.531u ...)
famMap('thd v(...) VAR("startint") 24.531u ...)
I have a CCR for a similar problem with another function, but not with thd. The idea is that famMap copes with unwrapping family data - and so if for some reason the v() is a family, and the VAR("startint") is a waveform (or family) rather than a number, it can sort it out. thd could do this itself.
It's a bit of a guess, but a similar strategy has worked in other cases for me.
Thanks for your assistance on the matter. I have tried the famMap() option but I still get the same
error messages. As soon as our local contact for Cadence is back I'll ask him to bring this in to