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 have a "noConn" (from basic lib) connected directly to an Instance terminal.
There is no wire in between the two objects, meaning that it won't take a "label" for changing the net name.
How can I rename that (internal) signal name in this case?
You can't, as far as I know. I think you simply have to drag the noConn a little so that you have a short wire between them, and then you can add a label.
In reply to Andrew Beckett:
I think this is the first time that I hear from you that something is impossible... ;-)
Well, don't you think there should be a way? still, you have a net in your design that you just can't change its name, this isn't seem logical.
Idea for enhancement?
In reply to izucker:
There's always a first time!
The challenge is, how would you attach a label to the thing that needs to be named when there is nothing physical to attach to? Possibly you could attach the label to the noConn component, but this would be a bit of a special case. What about the situation where you have two series connected resistors which have overlapping pins - how would you name the net then? You can't attach a label to an instance, because it wouldn't know which pin you wanted it to belong to.
To some extent, there have to be some semantics associated with how the physical drawing is converted into logical connectivity, and so some rules/limitations apply.
So if you can think of a good/usable way of naming the net, I can propose it - I just can't think of a way it would be done...
How about changing the name with some Skill code directly on the internal data structure?
I couldn't find a way here either...
You can do that, but it will get lost as soon as you do a "check" on the schematic again, so it's probably of limited value. That said, we have had some thoughts on having the connectivity being more persistent (only an idea, so I don't want to give details here).
How would you change the net name in this case with Skill? I couldn't realize how to do that.
And if the net name was changed and its not the default "net*" anymore, why would the "check" operation will "touch" and change it?
Assuming the net on the "noConn" net was called "net5", this will do it:
cv=geGetEditCellView()old=dbFindNetByName(cv "net5")new=dbMakeNet(cv "myNet")dbMergeNet(new old)dbSetConnCurrent(cv)dbSave(cv)
However, as soon as you do a "check", it will get reset. This is because the physical interconnect drives the connectivity, not the other way around - and any net not set by the schematic checker will get recreated. This is to help ensure that inconsistencies don't appear when connectivity is changed in the schematic - you could have ended up with two things which are still connected to the same net despite there being no physical connection any more (because the wire was deleted), and it would have to somehow know the intent of the user.
Of course, it's conceivable that we could have it that the connectivity in the database is more persistent, but right now it doesn't work that way.