|
|
|
Modeling & Simulation
Our Methods
Services We Provide
Tools, Resources &
|
Error: the Double counting of C_comp in a SimulatorThe IBIS Spec has always made it clear that driver model [Ramp] data (alternatively, V-T curve data) should include the loading effects of C_comp. The voltage-time behavior of the switching pulse emanating from the driver (IBIS Output or I/O model) should not be affected by the C_comp element appearing across the driver output. How can this be and how are errors avoided? After all, the driver should see its C_comp element as a load across the output. Computation of the launched waveform could then result in an erroneous double counting of C_comp. Why is C_comp even included in the IBIS model? Simply because a reflected pulse waveform returning to the driver from the receiver, load, or mismatch, will be loaded by the effects of C_comp. Accurate computation of multiple reflection behavior requires that the simulator include C_comp effects. One popular way to avoid this potential error in a simulator program is:
How does a user tell if their software has implemented this simulation correctly? The answer is to start with an IBIS driver model where the value of C_comp can be modified. Do two simulations. Do one simulation with the value of C_comp very low, perhaps .01pf to 0.1 pf. Do the second simulation with the value of C_comp very high, perhaps 10 pf to 100 pf. Check the output ramp rates / V-T curves at the driver in both simulations. They should not be affected by the value of C_comp. Note that driving a matched transmission line simplifies the investigation. |
|
|
|