Revision history [back]

I don't have experience with v32 and v33 on the same system, but I do have v30 and v32. We ran into an issue where, because they take different version of python, you have to explicitly set up the environment between the two. You may also run into this issue because v32 and v33 also run different python environments.

To set up the environment, we run this bat file before import psspy:

SET PATH=C:\PROGRA~1\PTI\PSSE30\PSSBIN;C:\PROGRA~1\PTI\PSSE30\PSSLIB;%PATH% 
c: 
cd c:\ 
actv <LICENSE KEY> PYTHON.EXE actv <LICENSE KEY> PYTHONW.EXE

Best of luck.

I don't have experience with v32 and v33 on the same system, but I do have v30 and v32. We ran into an issue where, because they take different version of python, you have to explicitly set up the environment between the two. You may also run into this issue because v32 and v33 also run different python environments.

To set up the environment, we run this bat file before import psspy:

SET PATH=C:\PROGRA~1\PTI\PSSE30\PSSBIN;C:\PROGRA~1\PTI\PSSE30\PSSLIB;%PATH% 
c: 
cd c:\ 
actv <LICENSE KEY> PYTHON.EXE  actv <LICENSE KEY> PYTHONW.EXE

Best of luck.

I don't have experience with v32 and v33 on the same system, but I do have v30 and v32. We ran into an issue where, because they take different version of python, you have to explicitly set up the environment between the two. You may also run into this issue because v32 and v33 also run different python environments.

To set up the environment, we run this bat file before import psspy:

SET PATH=C:\PROGRA~1\PTI\PSSE30\PSSBIN;C:\PROGRA~1\PTI\PSSE30\PSSLIB;%PATH% 
c: 
cd c:\ 
actv <LICENSE KEY> PYTHON.EXE 
actv <LICENSE KEY> PYTHONW.EXE

Best of luck.