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.
maybe my screen resoution is too large for this tool, but it annoys me everytime I plot a curve that I have to squint to see if it's mV or uV because the font is just too small. I can easily change it, I know, but it'd be great if it could be changed by default. Same goes for my ocean scripts plots.
The fonts can be changed using a .cdsenv setting. You didn't say which version you're using though...
In reply to Andrew Beckett:
I'm using IC6.1.5. What can I put in my .cdsenv to change the default font that VIVA uses when plotting waveforms (for the axis, titles, etc.)? Currently it seems to be using Helvetica (Linotype) - which doesn't print properly from my printer.
what is the syntax in order to get default Yaxis font size of 16.
In reply to yishai eilat:
envSetVal("viva.axis" "font" 'string "Default,16,-1,5,50,0,0,0,0,0")
In your ~/.cdsenv :
viva.axis font string "Default,16,-1,5,50,0,0,0,0,0"
I'm new with Cadence and I would like to do the same thing: changing axes font size.
I have created an empty file .cdsenv in my work directory and I copied the line:
viva.axis font string "Default,16,-1,5,50,0,0,0,0,0"
I started Cadence (6.1.5-64b) again from my work directory and I tried to draw a plot, but the axes font size hasn't changed.
Am I missing something?
In reply to Clidre:
The documentation on the methodology to set new defaults for ViVA is not accurate.The defaults can be placed in your .cdsinit file and must be preceeded by lading the ViVA context as detailed below.
; ViVa default fonts to Clean; Added from Wayne Ingram's note on 7/24/2013;; If customer is setting font related cdsenv variables in .cdsinit (via envSetVal API),; there's a requirement to load the 'viva' context _before_ any envSetVal call is made.; This can be achieved by the following in the .cdsinit file:loadContext(strcat(prependInstallPath("etc/context/") "viva.cxt"))callInitProc("viva")envSetVal("viva.graph" "titleFont" 'string "Clean,12,-1,5,55,0,0,0,0,0")envSetVal("viva.axis" "font" 'string "Clean,12,-1,5,50,0,0,0,0,0")
In reply to smlogan:
I'm a bit surprised by this (I found Wayne's solution and the corresponding CCR). For me it works fine without the pre-loading of the viva context, and I really don't think that should be necessary. Maybe it's been fixed (I was using IC615 ISR17 and IC616 ISR2 when testing this).
Anyway, I've asked R&D to check - because the comment on pre-loading the viva context came from them initially.
Is there any follow-up available on this topic? I could do the testing across versions myself, but if there's an answer already available then it would save me the work.
In reply to SharksFan:
No, I didn't get an answer - and to be honest, I've been a bit busy to chase it up (especially as I couldn't see the problem in the versions I was using, as I mentioned). I may well see the R&D person this week as I'm in the US, and so I'll ask him if I see him.