Etap 12.6

[surgeArrester]

Thanks for the --------. Greatly and highly appreciated.

I have been using this ETAP v12.6 doing some transient stability studies. I have noticed that when we load the saved project it sometimes display "INCORRECT PARAMETER". But still the project is loaded and still you can do the analyses.

Sometimes, upon invoking the calculation, it displays "error something2x EXIT CODE 9".. but if we save the project and reload again, it works OK.

Also, the invoking the calculation it says "Memory full".. restarting ETAP resolves this scenario and the analysis is ok.

Has anyone tried this? What do you think is the cause?.. Thanks...

[cadguy]

Thanks for the --------. Greatly and highly appreciated.

I have been using this ETAP v12.6 doing some transient stability studies. I have noticed that when we load the saved project it sometimes display "INCORRECT PARAMETER". But still the project is loaded and still you can do the analyses.

Sometimes, upon invoking the calculation, it displays "error something2x EXIT CODE 9".. but if we save the project and reload again, it works OK.

Also, the invoking the calculation it says "Memory full".. restarting ETAP resolves this scenario and the analysis is ok.

Has anyone tried this? What do you think is the cause?.. Thanks...

I studied the med in detail. I can summarize it as follows :

What a proper med does ? Provide the correct data to the security check routine which it is asking for. Or bypass the routine and assign the correct value to the operand and tell it to move ahead.

What this med does ? Pass through every check, return fail results in each case thereby consuming lots of time and memory. Finally redirect to run routine without flushing memory.

What may be result ? Long operation time, Momery Full, Buffer overrun, System hang up, Erroneous result.

About INCORRECT PARAMETER !

The file you saved with this med went to demo mode. Any file you save with this with transient stability or any other module which is not truely supported will go to demo mode and show that INCORRECT PARAMETER message on opening.

[surgeArrester]

I studied the med in detail. I can summarize it as follows :

What a proper med does ? Provide the correct data to the security check routine which it is asking for. Or bypass the routine and assign the correct value to the operand and tell it to move ahead.

What this med does ? Pass through every check, return fail results in each case thereby consuming lots of time and memory. Finally redirect to run routine without flushing memory.

What may be result ? Long operation time, Momery Full, Buffer overrun, System hang up, Erroneous result.

About INCORRECT PARAMETER !

The file you saved with this med went to demo mode. Any file you save with this with transient stability or any other module which is not truely supported will go to demo mode and show that INCORRECT PARAMETER message on opening.

.
That explains it. It does show on opening etap files with "incorrect parameter" display. And shows it hangs up upon calculation in transient stability.