Overview
After the installation of Control Expert is completed, projects and settings can be recovered by restoring in the following recommended order:
Only if the previous installed version is less than Unity Pro 4.0:
Custom libraries
Private ASI catalog
For all versions, including versions less than Unity Pro 4.0:
DFBs and DDTs in the Type Library Manager
Archived Application *.STA and/or Application Exchange Files *.XEF (Control Expert Classic)
Restoring Custom Libraries
To restore custom libraries, import them using the
tool.The procedure is explained below:
Step |
Action |
---|---|
1 |
Close Control Expert if it is open. |
2 |
Start . |
3 |
In the dialog:
|
4 |
Click . |
5 |
The following message may appear: The installation has succeeded but there are warnings. Details are in file: <C:\WINNT\logunit\install.log> Disregard this message. Click . |
6 |
Repeat steps 3 to 5 for each custom family that needs to be restored. |
7 |
Launch Control Expert: . |
8 |
Check that all the families have been successfully installed: . |
For more information, refer to Types Library Manager.
Restoring Manually DFBs, DDTs, and FFBs in the Type Library Manager
It is possible to restore the custom libraries manually even if they have not been saved.
This operation is useful in the following cases:
You forgot to save custom libraries in an installable form before updating,
You have been using custom FFBs defined with EFB Toolkit.
The directory of the custom libraries depends on Unity Pro version installed and the operating system. Generally, they are saved automatically during the installation process in the following directory:
Unity Pro 4.0 or later:
Windows 7 or 10 (32 bits or 64 bits):
C:\ProgramData\Schneider Electric\Unity Pro\CustomLibset\Vx.y
Windows XP:
C:\Program Files\Schneider Electric\Application Data\Schneider Electric\Unity Pro\CustomLibset\Vx.y
Unity Pro 3.1 or earlier:
C:\Program Files\Schneider Electric\Application Data\Schneider Electric\Unity Pro\CustomLibset\OldCustomdbxx.yy
The following table shows how to proceed when replacing Unity Pro 3.1 or earlier:
Step |
Action |
---|---|
1 |
Copy the content of the old custom library from the following directory (example):
|
2 |
Paste the content of the old custom library into the newer Control Expert custom library directory:
|
3 |
Repeat step 1 and 2 for all versions Vx.y where the custom library is needed. |
Restoring Private ASI Catalog
If the private ASI catalog files were previously saved, they must be restored to their original location.
Restoring Archived Application File (*.STA)
This restoration consists of importing the *.STA files previously stored. The *.STA files are used when the PLC cannot be stopped. To restore *.STA files follow the procedure below for each project:
Step |
Action |
---|---|
1 |
Launch Control Expert: . |
2 |
Open the *.STA file from menu.The file type selected must be Unity Pro Archived Application File (*.STA). |
3 |
Click . |
4 |
Save the project as an *.STU file. |
Restoring Application Exchange File (*.XEF)
This restoration consists of importing the *.XEF files previously stored. Importing from an XEF format involves to re-generate the project. To restore *.XEF files follow the procedure below for each project:
Step |
Action |
---|---|
1 |
Launch Control Expert: . |
2 |
Open the *.XEF file from menu.The file type selected must be Unity Pro Application Exchange File (*.XEF). |
3 |
Click . |
4 |
Save the project as an *.STU file. |