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.
Hello, I am trying to find a way to have pairs of nets follow the rules of a "diff. pair" except I do not want them to follow the same path. I prefer them to be separated from each other and can actually have other nets between them. They do need to be an the same layer however and be equal length. I would prefer not to assign them to a specific layer, rather let Specctra pick the layer. Any Ideas?
Unfortunately if you call them a diff pair you will get the "tightly coupled" version of the diff pair (you can make them edge or broadside).
But you just want two equally matched 50 ohm lines and push your signal and its complement down each one and have them arrive at the receiver in unison? Simple, just set them up as a matched group (relative propagation delay). All the same benefits. You can add multiple nets to this group -- if they all need the same distance rule.
In reply to Khurana:
Hi Khurana, Thanks for replying. It is my understanding that if I puts the nets in the same class, I can get the = length I want, but not the layer assignment unless I specifically tell each net which layer I want it to route on otherwise the nets could end up on different layers. This limits Specctras ability to untangle. The other option I know of is to assign them as DIFFERENTIAL_PAIRs. This option makes the pairs route on the same layer and gives me the = length but one net always follows its pairs path at a set spacing gap. What I am really looking for is all the rules DIFFERENTIAL_PAIR has except I want to get rid of the Gap so that each net can take its own path but stay on the same layer. Thanks again.
In reply to redwire:
Thanks redwire. I would like to let Specctra pick the layer (not assign the pair to 1 specific layer). I have 12 routing layers with 245 "pairs". I believe the matched group will put the nets on any of the 12 layers and not consider the pair requirments of being on the same layer unless I assign each pair to a specific layer. If I am wrong, could you please explain more on this. Thanks.