openAES() function in 3.11+sp1

[bhavna]

I have been using openAES() function since version 3.0. The same script worked in winCCOA 3.9 also. But now in 3.11 + SP1 the script is not working. I am unable to open the alarm screen with my defined configuration.Do I need to make new configurations or do I need to run some ctrl script?

There is only one line in the script openAES("GEN","mainModule"); where GEN is the configuration defined by me and mainModule is the name of the module.
When the script is executed, it opens the module, but the Alarm Screen(AEScreen) does not show up.


Regards,

Bhavna

[fmulder]

I'm pretty sure that the datapoints have changed that are used by the AES screen. Did you copy the datapoints from your old project ? There are some internal datapoint types called _AES_..... Also, check the messages in the LogViewer.

I'd advise you to make an AES screen configuration from scratch and try again. First make a simple one for testing. Then make a screenshot from your 3.9 configuration and re-type this in 3.11+SP1

Good luck

Frenk

[bhavna]

I am attaching the log file. I am not even able to make any new configuration. https://www.winccoa.com/fileadmin/image ... error.docx

[fmulder]

I would guess that you have imported an old (3.9) Ascii file. This would mean that you have properlymessed up the datapoint types for the _AES datapoints.
I'd advise you the following:

* Create a new 3.11 project and first ensure that you can configure the AES screen
* When this works
* Go to your non working project and delete all the internal datapoints called _AES_...
* Now export and import from your newly created 3.11 project

THis should fix it !

good luck

[bhavna]

You were right. I made a fresh copy of my project and everything worked properly. Thank you.

[WolfgangS]

Hello Frenk,
after upgrading a 3.9-project into 3.13-version no alarms or events are shown in AES; the screen is just empty.

I opened the 3.9-project with the 3.13-project administrator as an "old" project.
Then I worked out your advices without any success.
What is missing? What to do?

Regards.
Berthold

[fmulder]

It is likely that the -aes datapoints in 3.13 are different.

- make a new 3.13 project
- export the aes datapoints
- import into your upgraded project (first delete any existing aes datapoints)
- please make backup before you begin

This should help

Good luck

[leoknipp]

Hello,

did you make an upgrade to WinCC OA 3.13 using the project administration?
Or have you created a new project with 3.13 and imported afterwards a file exported from the project used with PVSS-version 3.9?

If you have imported an ASCII-file for a project with an old version where all standard datapointtypes and datapoints were included you've modified the (new) standard datapointtypes and datapoints necessary for 3.13. This might lead to problems afterwards if some dp-elements or their values are missing.

Best Regards
Leopold Knipp
Senior Support Specialist

[WolfgangS]

Hello,

@Frenk: I've allready done this with no success. Same issue as before.

@Leopold: I make the Upgrade using the project administration.

any other idea?

regards

Berthold

[leoknipp]

Hello,

have you installed a patch for WinCC OA 3.13?
Was this patch installed before or after you made the upgrade?
If the patch was installed after the upgrade there are maybe some additional steps necessary. Which steps are needed is described in the readme-files which are part of the WinCC OA patches.

Do you get errors in the PVSS_II.log-file when opening the AEScreen?

Best Regards
Leopold Knipp
Senior Support Specialist