Error with switch model in PSIM / SPICE

Support Communities Non PSIM Power Electronics Questions Error with switch model in PSIM / SPICE

This topic contains 5 replies, has 4 voices, and was last updated by  Albert Dunford 2 months ago.

  • Author
    Posts
  • #24196

    Junior Romani
    Participant

    Hello guys!
    I’m working with the PSIM / SPICE module version 11.0.3. And I have some problems with the simulations.
    Firstly, the key model that I use is a MOSFET of the ST Microelectronics STW70N60DM2, as follows the link <http://www.st.com/content/st_com/en/products/power-transistors/power-mosfets/n-channel-mdmesh-gt350-v-to-700-v/mdmesh-dm2-series/stw70n60dm2.html&gt; This link provided, is the SPICE model used as well as the datasheet MOSFET, I am also attaching the simulation that I am trying to accomplish. Related to the problems encountered, when I run the simulation SPICE aborts the same, presenting the following errors.

    Expression err: if(v(d,s)>0,(if(v(g,s)<(vth0-vthx*((v(tj))-27)),0,(if((v(d,s)<(v(g,s)-(vth0-vthx*((v(tj))-27)))*(kpsat0*(((v(tj))+273)/300)**(ksat))/(kplin0*(((v(tj))+273)/300)**(klin))),(1+lambda*v(d,s))*(kplin0*(((v(tj))+273)/300)**(klin))/2*v(d,s)*(2*(v(g,s)-(vth0-vthx*((v(tj))-27)))-(kplin0*(((v(tj))+273)/300)**(klin))/(kpsat0*(((v(tj))+273)/300)**(ksat))*v(d,s)),(1+lambda*v(d,s))*(kpsat0*(((v(tj))+273)/300)**(ksat))/2*(v(g,s)-(vth0-vthx*((v(tj))-27)))**2)))),-(if(v(g,s)<(vth0-vthx*((v(tj))-27)),0,(if((v(s,d)<(v(g,s)-(vth0-vthx*((v(tj))-27)))*(kpsat0*(((v(tj))+273)/300)**(ksat))/(kplin0*(((v(tj))+273)/300)**(klin))),(1+lambda*v(s,d))*(kplin0*(((v(tj))+273)/300)**(klin))/2*v(s,d)*(2*(v(g)))

    PTLex: syntax error in expression: “pwl ( p ? numparm__00000010 _ , numparm__00000011 , numparm__00000012 , -1.0000000000e-001 , 4.3001200000e-009 , 1.0000000000e-001 , 3.9361200000e-009 , 2.0000000000e-001 , 3.8796700000e-009 , 5.0000000000e-001 , 3.5942400000e-009 , 1.0000000000e+000 , 3.1037600000e-009 , 2.0000000000e+000 , 2.4118400000e-009 , 3.0000000000e+000 , 1.9661000000e-009 , 5.0000000000e+000 , 1.4264100000e-009 , 7.0000000000e+000 , 1.0710800000e-009 , 1.0000000000e+001 , 7.9437000000e-010 …” on token: ‘numparm__00000011’.

    PTLex: syntax error in expression: “pwl ( p ? numparm__00000015 _ , numparm__00000016 , numparm__00000017 , 1.0000000000e-001 , 3.0222580000e-008 , 2.0000000000e-001 , 2.9018230000e-008 , 5.0000000000e-001 , 2.5434660000e-008 , 1.0000000000e+000 , 2.2128040000e-008 , 2.0000000000e+000 , 1.8455460000e-008 , 3.0000000000e+000 , 1.6208200000e-008 , 5.0000000000e+000 , 1.3636190000e-008 , 7.0000000000e+000 , 1.1944120000e-008 , 1.0000000000e+001 , 5.7964500000e-009 , 1.5000000000e+001 , 2.7276700000e-009 ,…” on token: ‘numparm__00000016’.

    Error on line 0 : b.xsps2.becap xsps2.intecap 0 v= pwl ( p ? numparm__00000010 _ , numparm__00000011
    parameter value out of range or the wrong type

    Error on line 0 : b.xsps2.becap2 xsps2.intecap2 0 v= pwl ( p ? numparm__00000015 _ , numparm__00000016

    doAnalyses : parameter value out of range or the wrong type
    parameter value out of range or the wrong type

    Thanks for the help!

    Attachments:
    You must be logged in to view attached files.
  • #24287

    Albert Dunford
    Participant

    did you check the syntax using the spice netlist check utility?

    There are many SPICE variants and not all have the same syntax. We are working on a new release that will address this problem.

    You can also export the netlist as a .cir and run in ltspice.

  • #27098

    Neal Xu
    Participant

    Hi…i will suggest to try the migration. Once the simulation is setup the simulation is run with the LTSPICE engine which is also new with PSIM version 11.1. You are able to automatically export a simulation to a *.cir file which is then run by LTSPICE. Once the LTSPICE engine is finished the results are loaded into PSIM’s SimView for analysis. You will be able to merge the results from LTSPICE into other simulation results.

  • #39670

    Alan Perker
    Participant

    I was also getting the same error.

  • #39671

    Alan Perker
    Participant

    I was also getting the same error.

  • #39777

    Albert Dunford
    Participant

    in the latest PSIM release you can call the LTspice engine directly with the LT button. this should avoid this problem with the model syntax.

You must be logged in to reply to this topic.