patrickrossiter's profile - activity

I found that this can be replicated in jconto's working directory by changing the machine impedance on line 164 of "playback.py" from 0.0005 to 100 (or something) and re-running the study.

Hi Perolofl, Thanks for your answer, unfortunately it doesn't seem to work when the IB machine has any current flowing through it. The high source impedance means that the internal voltage is enormous and the simulation ends up with a lot of NaNs very quickly.

Hi there, I am having an issue using PLBVFU1 when network frequency dependence is enabled.

What I am finding is that when I use PLBVFU to cause a frequency disturbance and have frequency dependence switched on, the voltage on the infinite bus varies proportionally to the frequency. For example, if I start Vinf = 1.03 and ramp the frequency from 50 Hz to 47 Hz (6% decrease), the voltage also reduces by 6%, to 0.968. When the frequency returns to nominal, the voltage returns to the original value.

I have verified this on the following two cases and the performance is the same:

1. jconto's working directory (I can't link to it here but it's under the question "Example using PLBVFU1 playback generator") - if I enable frequency dependence then the voltage in the out file is about 0.3% lower the voltage in the plb file while the frequency is low.
2. I setup a case which has only one machine connected to a bus and no other network elements. The same behaviour is shown.

I have attempted to compensate for this by increasing the voltage in the PLB file by the same amount that it decreases in the simulation. However the voltage is still distorted when the frequency is ramping.

Has anyone else come across this bug? Is there a way around it, other than what I have shown above?

Hi there, Does anyone know an easy way to change the LIB and PATH settings in the Environment Manager? I’m getting errors when linking models and I believe it is because the correct directories are not in the settings.

Thanks, Patrick

The answer to this problem was that I had the following code at the end of all of my .F files:

END SUBROUTINE
END

The second "END" did not have a matching statement and when it was removed I was able to compile all three files into a single DLL as required.

Thanks for your reply, I have just seen this and this was the cause of my issue as well. I was passing an integer for the IB argument, when the routine needed a string.

This message appears in the commercial version as well. I don't think it can be removed.

I think that the error you are seeing is unrelated to the PSS messages you are getting. LUT generally stands for lookup table. I would suggest looking at UEL models and seeing whether any machines are outside their reactive limits, or active power greater than PMAX.

I would start looking at the swing bus, and then any machines you have added to the case (or other machines in the area) which have a terminal voltage of 0.9861 pu. Did you get any suspect initial conditions?

Also worth noting that I do not have any "main"s in the .F files, and only subroutines have been used (i.e.no programs)

Hi there, I am trying to compile multiple Fortran files into a single DLL and am getting the following message when creating the DLL. The files AVR1OEL.F, AVR1UEL.F and AVR1_AVR.F all compile correctly on their own and I can create three usable DLLs, but I want to have only one DLL which contains all three models. Any ideas what is going wrong here?

     link /INCREMENTAL:NO /NOLOGO /DLL /SUBSYSTEM:WINDOWS /MACHINE:X86 /ERRORREPORT:PROMPT
@"C:\Users\Patrick\.pssenvmgr\linkfilestvxtmu.txt" /OUT:"C:\Users\Patrick\.pssenvmgr\AVR1_v34.5.dll"
/map:"C:\Users\Patrick\.pssenvmgr\AVR1_v34.5.map"

 AVR1_OEL.obj : error LNK2005: _MAIN__ already defined in AVR1_AVR.obj
 AVR1_UEL.obj : error LNK2005: _MAIN__ already defined in AVR1_AVR.obj
 C:\Users\Patrick\.pssenvmgr\AVR1_v34.5.dll : fatal error LNK1169: one or more multiply defined symbols
found

 ERROR during link(1)... Aborted

Would you be able to send me the file that you were able to successfully compile?

Hi there, Quick question - should there be a psse.lib file in my PSSE34 directory?

Thanks, Patrick

Hi there, Can you please share exactly how you were able to add PSSLIB10 to the path? Thanks, Patrick

Thanks for your help. I am using the EM. What are you including in your .F file? I am only using INCLUDE 'COMON4.INS'. I have previously had a feeling that my EM is not set up correctly but I am finding it hard to diagnose.

Yes, I have used the following line for that but it is still unresolved. EXTERNAL BADMID, DOCUHD, MDLIND

Hi there, I am writing a user written model in Fortran and want to use one of the API routines in the model (specifically, MDLIND). When I include the following code:

CALL MDLIND(I, IB, 'EXC', 'STATE', IVAL, IERR)

I am unable to compile the code because of an unresolved external symbol. However I do not know where the API routines are defined and what file to include. Can anyone help?

Hi there, I am writing a user written model in Fortran and want to use one of the API routines in the model (specifically, MDLIND). When I include the following code:

CALL MDLIND(I, IB, 'EXC', 'STATE', IVAL, IERR)

I am unable to compile the code because of an unresolved external symbol. However I do not know where the API routines are defined and what file to include. Can anyone help?

This is a great answer!

Do you have an example input file we could start with?

Hi there,

I am having some difficulty using pssaccss in PSSE v34.1.1. When trying to extract some data from a .acc file, PSSE just crashes with no explanation. Below is the code which is causing the issue. Has anyone used pssaccss successfully?

On a related note, I notice that when printing dir(pssaccss), none of the methods listed match those described in the manual. Why is this? This is why i am using acccfileinit rather than acccfileinitialize, because acccfileinitialize does not appear in pssaccss.

accfile = 'ascc - SpL16.acc'
accsize = [1] * 21
n = pssaccss.accc_file_init(accfile, accsize)

I believe this is an issue with v34.3. Use v34.2 or earlier.

I am having the same issue - were you able to find a solution?