Stats

  • Locked Locked
  • Replies 4
  • Subscribers 125
  • Views 1515
  • 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

fallTime function - Documentation error ?

The Setlaz

Hi,

 

I just noticed when I used the fallTime function as described in the OCEAN documentation 6.1.5 - January 2012, it actually returns me the value of the riseTime.

The example in the documentation is pretty clear though :

------------------

fallTime( v( "/net8" ) 9 nil 1 nil 10 90 )

Computes the fall time for the waveform representing the voltage of "/net8" from 9 to 1.

-----------------

 

It seems to actually compute the rise time on my waveform. If I want the falltime, either I have to swap '9 nil 1' to '1 nil 9' or swap '10 90' to '90 10'

 

Is that "normal" ?

 

Thanks a lot,

Damien

Parents

  • Damien,

    It was broken in ISR8 - something changed which meant that the order of the arguments was different from what it said (if you specify the high value then the low value, then it should be 10 90 as the first threshold is 10 percent of the way between the high and the low, and the second threshold is 90 percent between the high and the low). 

    It was fixed in ISR12 (may have been ISR11, but I see an integration notice for ISR12 too). This was as a result of CCR 972729. There's another related CCR because we weren't really happy about the fact that riseTime and fallTime would actually detect the opposite if the arguments were specified the other way around - they are essentially doing the same thing at the end of the day. I believe it's more clearly documented from ISR12 onwards (I didn't check just now as I'm on vacation today and only taking a brief look).

    In the affected versions, you could use the attached code. Use:

    load("fixedFallTime.ile" "992136_v3")

    (the file is password encrypted, and the second argument is the password). Only use this in IC615 ISR8-ISR11, after which it is unnecessary.

    Regards,

    Andrew

    fixedFallTime.ile
Reply

  • Damien,

    It was broken in ISR8 - something changed which meant that the order of the arguments was different from what it said (if you specify the high value then the low value, then it should be 10 90 as the first threshold is 10 percent of the way between the high and the low, and the second threshold is 90 percent between the high and the low). 

    It was fixed in ISR12 (may have been ISR11, but I see an integration notice for ISR12 too). This was as a result of CCR 972729. There's another related CCR because we weren't really happy about the fact that riseTime and fallTime would actually detect the opposite if the arguments were specified the other way around - they are essentially doing the same thing at the end of the day. I believe it's more clearly documented from ISR12 onwards (I didn't check just now as I'm on vacation today and only taking a brief look).

    In the affected versions, you could use the attached code. Use:

    load("fixedFallTime.ile" "992136_v3")

    (the file is password encrypted, and the second argument is the password). Only use this in IC615 ISR8-ISR11, after which it is unnecessary.

    Regards,

    Andrew

    fixedFallTime.ile
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.