This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

DS280MB810: Request for model update for performance and IBIS compliance

Part Number: DS280MB810


Tool/software:

Hi,

I've been working with the provided IBIS-AMI model for this device in Hyperlynx for the past few weeks and have noticed some issues with the model:

- I had to (with the help of a Siemens rep) make modifications to the .ami file in order for the repeater functionality to work. This is because the model is quite old and supports repeaters using a standard that was proposed to the IBIS council at the time but ultimately not adopted in favor of a different standard. This problem cost me a *lot* of time in troubleshooting

- Performance: Simulations using the model take 3 to 4 order of magnitude more time than identical simulations using different repeater models. This makes sweeping parameters and optimization go from a 2 day job to a 2 week job, with most of it spent waiting for sweeps to run.

- Occasional erratic results: In some configurations the model would radically misbehave and return results that are clearly physically impossible or unreasonable, with no common thread between offending configurations.

It is clear to me that this model is old and needs a touchup, at bare minimum for compliance with the actual IBIS standard.

  • Hi Jonathan,

    I haven't seen this reported before but will communicate your findings to our team. Thank you for bringing this to our attention.

    Typically we simulate with Keysight ADS, not Hyperlynx. Are you able to simulate with ADS and if so do you see the same issues?

    Best,

    Shane

  • Hi Shane,


    I do not have the necessary licenses to simulate with ADS so I can't comment on whether the issues present themselves there. However from what I understand, the non-compliant repeater standard that the model follows is because at the time the model was made the repeater keywords did not exist in the IBIS standard but rather were supported in an ad-hoc way by Keysight ADS only.

    Supporting the IBIS standard required adding the [Repeater Pin] Keyword and the Repeater_Type AMI parameter, was well as adding AMI_Version to the AMI file. In addition, the Redriver model itself is of format BIRD158/194, which means it uses S-params rather than I-V and V-t curves which is the normal IBIS way. Converting one to the other however is not difficult once you know you need to do it.

    I hope that helps!

  • Thank you Jonathan, the context certainly helps.

    Unfortunately we don't have the ability to modify this file right now, but I have made our team aware of this. 

    Best,

    Shane