Stats

  • Locked Locked
  • Replies 2
  • Subscribers 64
  • Views 8114
  • Members are here 0
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

vsource will not accept expressions in its parameters

NewScreenName

Hi all,

I am trying to generate a signal as a sum of sinusoids whose frequencies are linear combinations of four parameters (f1, f2, f3, f4). In the first picture you can see how I set it up.

However at the time of running the simulation, the error shown in the second picture appears. So it looks to me like the issue is that vsource will not accept expressions as frequencies and amplitudes? Is there any way to have it working this way without me having to manually calculate and insert the new set of frequencies everytime I change one of the f1,f2,f3,f4 parameters?

Thank you very much

Best regards

Parents

  • This is because of a quirk with the Spectre language - expressions inside vectors have to be surrounded by parentheses. In the Virtuoso version I'm using (IC6.1.8 ISR27) the frequencies do get netlisted with parentheses around the expressions, but the amplitudes don't - so change to: (0.5*Ain/Ntones) . Check the netlist - if the frequency expressions are not in the version you're using (I wonder if they are not, because the errors you get are slightly different), try adding parentheses around each of the frequency expressions.

    I think we need to fix the netlisting of this component to put parentheses around the amplitude expressions automatically.

    Andrew 

Reply

  • This is because of a quirk with the Spectre language - expressions inside vectors have to be surrounded by parentheses. In the Virtuoso version I'm using (IC6.1.8 ISR27) the frequencies do get netlisted with parentheses around the expressions, but the amplitudes don't - so change to: (0.5*Ain/Ntones) . Check the netlist - if the frequency expressions are not in the version you're using (I wonder if they are not, because the errors you get are slightly different), try adding parentheses around each of the frequency expressions.

    I think we need to fix the netlisting of this component to put parentheses around the amplitude expressions automatically.

    Andrew 

Children

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. 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. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.