Plant SCADA Anywhere clients - custom ini file and other modifications

Hi abeba 

The first question, requires a custom logon script (for the user that is logging into Access Anywhere) to copy a citect.ini to the specific path before loading Plant SCADA runtime. There are some forums that have mentioned this approach, and it might also be posted on Ericom forums or IT focused forums with detailed implentation.

The second question likely requires modification to the Anywhere web page files, which is not supported. But again you might have some luck finding others that have documented that process, or you could experiment on a test system yourself. There is also a "full screen" mode in Access Anywhere which does hide the toolbar. If you don't have any luck with those approaches, I'd recommend posting an enhancement request on the Aha ideas forum: https://citectscada.ideas.aha.io/

Kind regards

Olivier

Hi Olivier,

I was able to hide the toolbar by changing the disableToolbar parameter in config.js to true.

Regarding the ini file, the issue with copying a citect.ini to the launcher directory is that it seems to get overwritten as the Anywhere software starts up (not sure at what point in the startup this happens). I have not been able to find any other information on this approach, could you point me toward the proper channels? I am having trouble finding any Ericom forums or other IT pages with much information on Plant SCADA.

Thank you

There is a knowledgebase article about this: 000032964

softwaresupportsp.aveva.com/.../000032964

Hi Bart,

Thank you, I did see that article. I am going to try it out when I have some time to play around with it. Do you know if modifying the \config\citect.ini would affect the server runtime?

Hi Bart,

Thank you, I did see that article. I am going to try it out when I have some time to play around with it. Do you know if modifying the \config\citect.ini would affect the server runtime?

Hi abeba ,

Plant SCADA Access Anywhere doesn't support profiles of citect.ini. I suggest

• Create a common profile for display clients in your project

• Merge sections  [Animator], [Client], [LAN], [MultiMonitors], and [Page] from DisplayClient.ini into the default citect.ini on the PSAA machine, which is a one-off task. However, if any merged setting in the profile is updated, you have to manually merge the change again.

• Create a logon event in Cicode in your project to adjust some settings for different RDP users

Modifying the default citect.ini file on PSAA machine won't affect the server runtime. Actually, servers can use their own profiles (different citect.ini) at runtime. Please see [RuntimeManager]Profile for details.

Hi Jacky,

Maybe I'm misunderstanding, but the issue I see with this is that whenever PSAA is run on a remote account, it copies C:\ProgramData\AVEVA Plant SCADA 2023 R2\Config\citect.ini to the remote user's temporary files (..\AppData\Roaming\AVEVA Plant SCADA Access Anywhere\Launcher\).

This citect.ini appears to be copied from the main server project periodically. So even if you were to merge it, it would be overwritten whenever the session starts again. And if we are calling this as a logon event in Cicode, by the time it applies the new ini file, it would have already launched with the old parameters.