PlantStruxure PES[V4.3]: Why Advanced Settings (Citect INI) changes for Supervision Project in PES is not Deployed to Supervision Server during Supervision Executable Deployment
Goals and Symptoms
In PES whenever user make any changes to Advanced Settings for Supervision Project in PES, these changes are not deployed to Supervision Server at Supervision Executable deployment. User has to manually make those changes in all Supervision Server and Client machine after any changes.
Facts and Changes
In this article we will explain various configuration that can lead to automatic deployment of changes made in Advanced Settings. The resolution mentioned in this document is for PES V4.3.
Causes and Fixes
As you might already know that Citect INI is being used to do the advanced configuration related to Citect application function and Runtime. This configuration is PC specific as each machine having its own local copy of Citect INI file and if you are running with multiclient environment, it allows you to configure different behavior in each machine. In case you want same configuration in each machine you need to replicate the Citect INI file throughout the machines that are running with Vijeo Citect.
The Advanced Setting command for Supervision Project allows you to modify parameters of the citect.ini file by using the Computer Setup Editor tool of Vijeo Citect by launching Computer Setup Editor window in PES VM. This citect.ini file is then copied to the %SoCoDeploy%\Users\<Project identifer> folder when you deploy the Supervision Participant project. Deployment of supervision Project is using the Backup and Restore Concept of Vijeo Citect which means that whenever you restore (in citect) or Deploy (from PES) the Citect INI file that was saved during Backup of Project will be restored into the Project Folder Path (Default Vijeo Citect Vx.yy\Users\<Project identifer>).
But by default when Vijeo Citect starts up, it takes the value from Citect INI located in the path "....Vijeo Citect 7.50\Config" (or %SoCoDeploy%\Config in PES Terms) but the deployed INI from PES is located in Project Path "..Vijeo Citect Vx.yy\Users\<Project identifer>". This is the reason you cannot see the changes that you made in Advanced Settings in PES to the Citect INI.
There are few methods to overcome this:
1. Change in Vijeo Citect configuration to look for the Citect INI file located in Project folder than the default Config folder.
To specify an alternative INI file path for Vijeo Citect :
a.Click the icon that you use to start Citect Explorer and/or Runtime. (Use Runtime in case you are launching Runtime separately from Explorer i.e. From Desktop Icon)
b.Right-click to display the shortcut menu and select Properties.
c.Click the Shortcut tab.
d.Add the name of the INI file to the command line property of the appropriate icon using the -i option. For example, to start Vijeo Citect v 7.50 using the initialization file Citect.ini from Project Folder, enter the following line:
C:\Program files\Schneider Electric\Vijeo Citect\Vijeo Citect 7.50\bin\citect32.exe -i C:\Program files\Schneider Electric\Vijeo Citect\Vijeo Citect 7.50\Users\<Project identifer>\Citect.INI
This will force Vijeo Citect to use Citect INI file located in Project Folder. And then after all the changes in Advanced Setting are automatically applied with Project Deployment.
Note: This configuration need to changed in Each Vijeo Citect Server and Client Machines. If you change the Project Name or Executable Name, this configuration need to modify or else Citect will still be configured to use the old path and can return error if path is not valid or file not available.
2. User can manually copy Citect INI file from Project Folder (C:\Program files\Schneider Electric\Vijeo Citect\Vijeo Citect 7.50\Users\<Project identifer>\Citect.INI) and paste it in Config folder of Vijeo Citect (C:\Program files\Schneider Electric\Vijeo Citect\Vijeo Citect 7.50\Users\Config\Citect.INI) every time after user make changes in Advanced Settings and deployment.
3. You can create a Cicode to add parameter in Citect INI using PrameterPut cicode function and then you can call this cicode function as Client startup function.
4. Instead of Modifying in Citect INI, you can also add specific parameter in Project by adding parameter in Citect Project Editor-->System--> Parameter. Note that this will not make any new entry in the Citect INI but this new changes will be applicable when Project is in Run Mode.
You can use any of the method above as per your suitability.