Schneider Unity. AUVESY GmbH. Last updated: 03 September Fichtenstrasse 38 B D Landau Germany

Transcription

1 Schneider Unity AUVESY GmbH Last updated: 03 September 2018 Fichtenstrasse 38 B D Landau Germany

2 TOC Schneider Unity 3 Support for Schneider Unity projects 5 Integrating existing Schneider Unity projects into versiondog 6 Integrating new Schneider Unity projects into versiondog 7 Creating jobs for a Unity device with versiondog 8 Restoring a Schneider Unity device 11 Executing uploads of my Unity device if Unity is not install on my versiondog server 13 Backing up different PLCs that run different Unity versions 14 Working in versiondog with STA Files instead of STU files 15 2

3 Schneider Unity Schneider Unity Pro is the common programming, debugging and operating software for the Modicon M340, M580, Premium, Momentum and Quantum PLC ranges. The documentation for Schneider Unity contains information on the interaction between Schneider Unity and versiondog. The documentation aims at providing a user with the knowledge essential for working with Schneider Unity via the versiondog UserClient. The user should have a basic knowledge of the concepts of the versiondog system and some experience in working with Schneider Unity. Network diagram Requirements - In order to work properly, the solutions presented in this tutorial require certain software (and hardware). Compatibility overview with versiondog: From versiondog version Schneider Unity firmware version

4 From versiondog version Schneider Unity firmware version If you want to create backup jobs for Schneider Unity and use more than one version of Unity you have to use versiondog UploadAgents and versiondog CompareAgents 4

5 Support for Schneider Unity projects The versiondog system provides the option to activate Schneider Unity support. All Schneider Unity editors of version 4.0 or higher are supported. If Schneider Unity support is currently not included in the functionality of your versiondog system, you can activate Schneider Unity support if required. You can check for yourself whether Schneider Unity is currently supported by your versiondog system. Proceed as follows: 1. Open the AdminClient 2. Click on the Licencing button 3. Select the Information tab. 4. Check if the entry Schneider Unity is listed in the Data Types field. If Schneider Unity is included in the data type list, it is supported by your system. If Schneider Unity is not included in the data type list, it is not supported by your system. If you wish to work with Schneider Unity but Schneider Unity is currently not supported by your versiondog system, you can activate Schneider Unity support. The following applies: If you use versiondog Standard Edition with a valid Update & Support Agreement, the activation of Schneider Unity support will be accomplished according to the provisions of the Update & Support Agreement. Please contact us for an update of your licence. If you use a version of versiondog other than Standard Edition and/or without a valid Update & Support Agreement, please contact us for information on the conditions for the activation of Schneider Unity support. 5

6 Integrating existing Schneider Unity projects into versiondog If Schneider Unity is supported by your versiondog system, you can integrate Schneider Unity projects into versiondog. It is possible to integrate all Schneider Unity products according to the Compatibility overview with versiondog. Proceed as follows to integrate an existing project into versiondog: 1. Create a Schneider Unity component in the versiondog UserClient. (For more details on how to create a component refer to: Creating a new component). 2. Browse in the Windows explorer to your Unity project file (STU) 3. Copy per drag and drop the Unity project from the original folder into the working directory of the component. To do that you need to drop the project file onto the Unity component in the project tree 4. Return to the Schneider Unity component in the versiondog UserClient and click on Create base version and check-in The Schneider Unity project now has been integrated into versiondog and can be managed within versiondog. In versiondog, it is only possible to display the project tree of a unity project if a Unity editor is installed locally. This editor must be of the same version as the one used for the creation of the project 6

7 Integrating new Schneider Unity projects into versiondog If Schneider Unity is supported by your versiondog system, you can integrate newly created Schneider Unity projects into versiondog. It is possible to integrate all Schneider Unity products according to the Compatibility overview with versiondog. Proceed as follows to integrate a new project into versiondog: 1. Create a Schneider Unity component in the versiondog UserClient. (For more details on how to create a component refer to: Creating a new component). 2. Open your Unity editor 3. Create a new project and save it in the folder of the Schneider Unity component that you just created 4. Return to the Schneider Unity component in the versiondog UserClient and click on Create base version and check-in The new Schneider Unity project now has been integrated into versiondog and can be managed within versiondog. In versiondog, it is only possible to display the project tree of a unity project if a Unity editor is installed locally. This editor must be of the same version as the one used for the creation of the project 7

8 Creating jobs for a Unity device with versiondog In versiondog, scheduled jobs can be used to control if the program that runs on a device is the same as the last version that was checked in, or if the newest version that was developed was implemented on all machines. It is also possible with versiondog to use jobs to create a backup of a device. The result (the backup) can be used for a detail comparison and also for the purposes of disaster recovery and further editing. Configuring a job for a Unity compatible device 1. Open the versiondog AdminClient and click on Jobs 2. In the tree, select your Unity component 3. In the ribbon (tab Home), click then on the button Create 4. In the column Job configuration, select the Upload type and configure the sections General and Upload and compare If you need help configuring these sections, read AdminClient Basics: 5. Jobs 5. Configure the Schneider Unity settings: a. In the drop-down menu of the Project, select the project you want to backup. This option is only relevant if you have more than one Schneider unity projects in your component b. In the drop-down menu of the Access path, select the interface/protocol used to interact with the device c. In the field Device, enter the IP-address of the or the name of the device d. Option: If you want to also back up the current values, tick the box Save data from the PLC to file. This will create a DTX file. e. Option: If you want to back up a simulator, tick the box Upload from simulator 6. Option: If you want to create a backup with the job for restore purposes, make sure that: 8

9 Before downloading your Unity project to the Schneider device, you have configured your project to download some additional data to the device. To do that you need to: a. Open your project in the Schneider Unity editor b. Click on Tools c. Click on Project Settings... d. Go to General > PLC embedded data e. Activate the options Upload information and Comments (if you need them, you can also activate Animation tables) f. Click on apply, then on OK and follow the usual manipulation to download the project onto the device 9

10 Only if you made this modification to your Schneider Unity program, before downloading the program onto your device, will your backup be complete and restorable. The Auto-lock feature of Unity cannot be detected by the compare during the backup process 10

11 Restoring a Schneider Unity device You can use the compare capabilities of versiondog to know if the program that runs on the device was modified since the last execution of a job. If the result of the job shows that the program on the device was modified, you might want to restore your device to the last checked-in version. To restore your device to an older program, you have two possibilities: Proceed as follows to restore a Schneider Unity device from a version: 1. Open your UserClient 2. Select the component of the project that you want to restore 3. Perform a Check-Out of the component 4. Open the Schneider Unity project with the corresponding editor 5. In the Schneider Unity editor, use the function that you usually use to send the project to the device Proceed as follows to restore a Schneider Unity device from a backup: If you followed all the steps to make a backup restorable (for more information, read Creating jobs for a Unity device with versiondog), you have the option to perform a restore from the backup and download that backup onto the device. The versiondog backup contains a project file and a PLC parameter file (DTX) if the job is configured as described before. 1. Open your UserClient 2. Select the component of the project that you want to restore 3. Click on the component details tab Jobs and select a job 4. In the window at the bottom, select the job results from which you want to copy a backup and click on Copy backup to directory 5. Click on Browse... and select the directory to which you want to copy the content of the backup to (the content of the chosen directory will be deleted before the copy process is star- 11

12 ted) 6. Open the Schneider Unity project copied from the backup with the corresponding editor 7. In the Schneider Unity editor, use the function that you usually use to send the project to the device See also: User Client Basics 12

13 Executing uploads of my Unity device if Unity is not install on my versiondog server To be able to execute upload and compare processes, your versiondog server needs to have access to the Unity software. One solution would be to install it on the same computer as the versiondog server. If you cannot install this software on the versiondog server, you will need to use upload & compare agents to access a computer on which the Unity software is installed. The agents need to be installed before creating the jobs. See also: versiondog Upload & Compare agents Creating jobs for a Unity device with versiondog 13

14 Backing up different PLCs that run different Unity versions To be able to execute upload and compare processes, you need to have the Unity software installed on the same computer as your versiondog server, but if you use more than one version of Schneider Unity, it is not possible to install the different versions on the same computer. Therefore, in this case, you cannot install these software on the versiondog server: you will need to use upload & compare agents to access the computers on which each version of the Unity software is installed. You need to carefully name each of your upload and compare agents to make sure that you have no problem recognising them when you select them in the drop-down menu of the job configuration. For example, you could name your agents "UploadUnity6" and "UploadUnity8" in an environment where you'd need a connection to two different computers, with a different version of the Unity editor installed on each one. See also: versiondog Upload & Compare agents Executing uploads of my Unity device if Unity is not install on my versiondog server 14

15 Working in versiondog with STA Files instead of STU files In Schneider Unity, you have the possibility to create STA files out of your STU project files. These STA archive files can bring a certain amount of compatibility between Unity versions and are smaller than the corresponding STU. Creating a component type for STA files management If you intend to work only with the STA files, we recommend creating a new component type to manage the STA files. You can base this new component type on a copy of the Schneider Unity component type. If you copied the Schneider Unity component type, you need to remove the STU files from the Compare these files field and replace it with STA. For more information on the creation of component types, read Creating a new component type. Setting versiondog to compare STA files By default, the Schneider Unity component in versiondog is configured to only take STU project files into account during the compare process and there is no component type pre-configured for STA files. If you don't want to create a new component type, you can modify the existing Schneider Unity component type to allow the comparison of STA files: I. Open your versiondog AdminClient II. In the ribbon, click on: III. In the Component types list: 1. Expand the Schneider folder 2. Expand the PLC folder lying therein 15

16 3. Select the Schneider Unity Component type 4. In the column in the middle of the screen, select the second line of the field Compare these files then: a. add STA to the column specification b. Select SchneiderUnity in the drop down menu of the comparator column c. Select Include in the drop down menu of the subdirectories column 5. Click on: From then on, not only STU files but also STA files will be compared. If you want to compare a STU with an STA file, use the free comparator of versiondog (you will need a Schneider Unity editor of the same version as the STU installed on your local machine) 16

17 Component with STA and STU files If you have configured the versiondog comparator to include also STA files in the comparison (see precedent section), then versiondog will show you a list of files that could be open when using the function Open editor. It would show you in a pop up box both files and you would have to select one of them to be opened with the Unity editor. Remember that if you modify and save an STA file with your Unity editor, it creates an STU file 17