Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

Is it possible to calculate the rise/fall time of an operational amplifier ?

+3
−0

I am planning to use the LM318 operational amplifier to generate a PWM signal and I need to know how to calculate the rise/fall time.

LM318/LM218/LM118 datasheet

-The slew rate is 70 V/µs maximum
-Slew rate can reach 150 V/µs But with a condition of "feedforward compensation will boost the slew rate to over 150 V/μs and almost double the bandwidth."

As suggested from Mr. Olin, here is my calculation:
the LM318 offers 70 V/µs and the output voltage that I need is 18 V so:
(18 V) / (70 V/µs) = 0.257143 µs = 257.143 ns.

And then I did this: (257.143/5)×4 = 205.714 ns.
Because the rise/fall time start at 10% and end at 90%.

And in case of 150 V/µs this is going to be:
(18 V) / (150 V/µs) = 0.12 µs = 120 ns (120/5)×4 = 96 ns.
Is my calculation correct?

History
Why does this post require attention from curators or moderators?
You might want to add some details to your flag.
Why should this post be closed?

2 comment threads

Please note that the "10% to 90%" criterion is valid for small-signal responses only. The slew rate i... (3 comments)
Six significant figures (0.257143) do not make any sense when there are 1-2 in the calculation (18 V ... (1 comment)

1 answer

+3
−0

Rise and falls times are limited by the maximum slew rate the opamp can produce. This is something you look up in the datasheet. Note that the slew rate might be dependent on supply voltage and possibly other factors. Or, the datasheet might just give a single minimum large-signal slew rate for the whole range of possible conditions.

Once you have the slew rate, divide the voltage that has to be traversed for whatever you consider "rise" and "fall" by the slew rate. For example, if you decide the opamp can do 3 V/µs at minimum and you want the output to change 10 V, then that will take at most:

(10 V) / (3 V/µs) = 3.3 µs

The slew rate is 70v/ųs max.

I opened the datasheet from the link you provided, and right on the second line of the first page it says that only 50 V/µs is "ensured". The only mention of 70 V/µs I can see is for a typical value, which is meaningless.

(18 V) / (70V/µs) = 0.257143 ųs = 257.143 ns

That is correct, sort of. As stated before 70 V/µs is not the spec for this opamp. The other problem is that 257.143 ns is absurd. Carrying an extra digit or two in intermediate calculations makes sense to avoid adding additional noise. But claiming to know the transition time to within a picosecond is ridiculous. Just 257 ns is already lots more accurate than you know the actual slew rate, but would be an acceptable answer with the understanding this is an intermediate value with a bit more precision than really needed.

And then i did this: (257.143/5)×4 = 205.714 ns. Because rise/fall time start at 10% and end at 90%.

Yes, you're really asking about slewing 80% of the 18 V, so the resulting time will be 80% of the time calculated for 18 V. Other than the absurd precision, this is correct for your starting assumptions.

History
Why does this post require attention from curators or moderators?
You might want to add some details to your flag.

0 comment threads

Sign up to answer this question »