Stats

  • Locked Locked
  • Replies 6
  • Subscribers 125
  • Views 1876
  • 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

Adding a cap in Ultrasim requires an additional probe statement - any workaround?

ckteng

Hello, I'm adding some caps to nodes in one of my subcircuits by adding a statement with a hierarchical path like this:

C1 Xtop.Xnext.node1 VSS 1e-15

Before adding the cap, I can browse the simulation results using SimVision and see the voltage at node1.

The simulation file includes a probe statement

.probe v(Xtop.*)

After adding the cap the probe seems ineffective and I can't see node1 in my sim results.

If I add a probe statement for node1 specifically I can see it in my results.

.probe v(Xtop.Xnext.node)

I don't want to have to add a probe statement for every node I add a cap to.

Does anyone know why I can't just add the cap and continue to see results?

Thanks!

Parents

  • Marc,

    I just tried the netlist above with the same version as you, and it seems to work for me. So I suspect there must be some subtlety my simple example is missing. Perhaps you could check my netlist too - I just did:

    ultrasim -raw forumultra.raw forumultra.spi

    (the netlist was in forumultra.spi)

    I used: Version 13.1.1.049  64bit 04/15/2014 04:15 (usimamd64-46)(exactly what you used).

    Regards,

    Andrew.

Reply

  • Marc,

    I just tried the netlist above with the same version as you, and it seems to work for me. So I suspect there must be some subtlety my simple example is missing. Perhaps you could check my netlist too - I just did:

    ultrasim -raw forumultra.raw forumultra.spi

    (the netlist was in forumultra.spi)

    I used: Version 13.1.1.049  64bit 04/15/2014 04:15 (usimamd64-46)(exactly what you used).

    Regards,

    Andrew.

Children
No Data

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.