Schneider Control Expert
Last updated
Last updated
DeviceLink can provide change detection with notification and backups of your STU and DTX files for devices configured over TCP/IP for the Supported Versions of Schneider Control Expert (Classic) editor. See more information about Topology Manager at the following link: Schneider Control Expert Topology Manager
Password protected or encrypted project are not supported at this time for DeviceLink backup
Below are the Agent system requirements to configure a Copia Agent for the backup of Schneider Control Expert projects:
You will need a licensed copy of Schneider Control Expert (see supported versions) that is capable of backing up a Project from the Device(s). In addition, any additional vendor software must be licensed and installed on PC running the Copia Agent. (i.e. EDS files, Add-on's etc.).
Since Schneider Control Expert can only have a single version installed on an Agent, if you have version skew in your location, you may need additional Agents to maintain compatibility with all devices.
The Agent should be tested to confirm that it can backup the PLC(s) using the vendor software without error.
Schneider Control Expert should not be running or "in-use" on the Agent during backup operations.
To configure a new project for Schneider Control Expert, you will need to already have a repository created with the Schneider Control Expert .stu file. In addition, projects should have already been downloaded into the PLC with the Upload Information. This allows the project data to be transferred from the PLC to Copia Agent. This option is under Control Expert >>Tools >>Project Settings>>PLC embedded data>>Upload information, as seen below.
DeviceLink for Schneider Control Expert will also backup the .dtx file (along with the .stu) from the PLC, but it is not required for initial setup and configuration.
Click the Add a Project button in the Projects tab.
The Add a new project configuration dialog will appear which allows you to fully configure the project, devices and job for the project.
Any items highlighted with an asterisk are required.
This is a multi-step process with each section explained in detail. At any time, you can edit the prior section of this workflow.
Projects can be edited after creation. Devices and Jobs can also be edited or created directly, using the Devices or Jobs tab. The steps for creation are similar to the steps provided below for those sections.
To get started, we will first select the Project Type from the list provided, and then select an Agent. If you have not already created an Agent, you can create and assign an Agent at a later time. See more about this in the Agents section of the documentation.
When complete, press Save and Continue.
You will now select the Project Path, which is the location (Repo/Branch) that the project is, or will be stored.
As seen, you can edit the previous steps at any time.
You will only be allowed to select the appropriate filetype or folder that is allowed for the Project Type. In some cases, a project is required to perform a backup, in other cases, the backup can create the initial backup into an empty project folder.
Once selected, press Save and Continue to proceed.
The project details allows you to update the Project name, and description if desired.
The Device Setup section is for defining the device information (PLC, comm path, etc.) that is in your project. If you have pre-created devices, you can add existing devices, otherwise you can Add a Device as seen.
Fill in all required field, and any fields that are applicable. Press Save Device when complete.
Creating Jobs is similar for all vendor types, and is described in the Creating Jobs section. It is recommended to review that section while completing a job configuration, and press Save to save the job. You can create more than one job for a device if desired.
Once complete, press Submit Project Setup to create the Project, Device(s) and Job(s).
Don't forget to enable/disable the Watch button, based on your preferences for project Notifications.
