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.

TPS54538: PSPICE Model for TPS54538 does not compile/run in TI-PSPICE

Part Number: TPS54538
Other Parts Discussed in Thread: PSPICE-FOR-TI

the PSPICE simulation for TPS54538 (SLUM922.ZIP).  Does not run with the following error messages:

ERROR(ORPSIM-15461): Incorrect number of interface nodes for X_U1.X_U7_U724.
ERROR(ORPSIM-15461): Incorrect number of interface nodes for X_U1.X_U8_U832.
ERROR(ORPSIM-15461): Incorrect number of interface nodes for X_U1.X_U842.
ERROR(ORPSIM-15461): Incorrect number of interface nodes for X_U1.X_U839.

 

  • Hi Eric,

    We will check and come back on this.

    Regards,

    Haseen.

  • Hi Eric,

    The observed ORPSIM-15461 “Incorrect number of interface nodes” errors are due to PSpice version incompatibility, not a schematic issue.
    The TPS54538 transient PSpice model (SLUM922) was validated on Cadence PSpice 16.6 / 17.x. Newer versions (including PSpice 23.1) enforce stricter hierarchical pin checking, which causes failures in the encrypted internal subcircuits.

    Recommended action:
    Please run the model using PSpice 17.4 or earlier and let me know.

    Regards,

    Usha.

  • I am running the latest PSPICE-For-TI free version (23.1-2004-S001). I do not have a Cadence License.  Is there a PSPICE-For-TI free version of the correct version?

  • Hi Eric,

    We only have PSIPCE-For-TI, you can follow these instructions in the current version to run the simulation:

    For TI encrypted power-device transient models, nom_pspti.lib is not required and may conflict with internal behavioral subcircuits. Removing it is recommended when running PSpice 23.x.

    1. PSpice → Edit Simulation Profile

    2. Open the Configuration Files tab

    3. Select Library

    4. In the list, find and select:

        nom_pspti.lib

    5. Click Remove

    6- Click OK

    Re-run the simulation

    This prevents the library from being auto-inserted again. I have tried and it's working now!

    Best regards,

    Usha.