status of links between cape and relay vendor setting software

Status of Links Between CAPE and Relay Vendor Setting Software

Prepared for

CAPE Users Group

June 24-25, 2014

Electrocon International, Inc. Ann Arbor, Michigan

This document is the sole property of Electrocon International, Inc. and is provided to the CAPE Users Group for its own use only. It may not be supplied to any third party, or copied or reproduced in any form, without the express written permission of Electrocon International, Inc. All copies and reproductions shall be the property of Electrocon International, Inc. and must bear this ownership statement in its entirety.

Links to Relay Vendor Setting Software 2014 Users Group Meeting

Links Between CAPE and Relay Vendor Setting Software For most CAPE users, the CAPE database has become an important repository for relay settings. At a minimum, these relay settings are important for record keeping purposes, but their value is increased when they are used more effectively. Using the relay settings for analysis within CAPE has proven to be one obvious way to increase their value. Increasingly, another way has been to transmit them electronically to and from the relays themselves, or at least to the relay vendor's software. While direct communication with relays is impractical, transferring settings via the vendor's software has proven quite practical; that is, provided the manufacturer is motivated to cooperate. Since we reported our first such link in June of 1998, much progress has been made. Your positive feedback to your suppliers will ensure continued cooperation in the future. Below is a list of relay vendor software that we are aware of. Many have been linked to already, and some are active works-in-progress. Our first goal is to allow reading setting data from these software packages into CAPE. Then, if possible, we want CAPE to write data out to these packages. ABB CAP 540 The CAP 540 software supports REx 5xx relays. Transferring settings from CAP 540 to CAPE is supported through the ABB Parameter Setting Tool (PST). You can invoke PST by right clicking on a relay in CAP 540, and choosing Parameter Setting from the pop-up menu. See the PST entry below for more information.

1


PCM 600 ABBs newest setting software is called PCM 600. This software is used to communicate with the REx670 series relays. Prior to PCM version 2.2, there was no way to extract settings into any format that is usable by CAPE. As of version 2.2, the possibility to export to XRIO format was added. To create an XRIO file from within the PCM software, select a REx670 device, then select Tools | Parameter Setting. Next, select File | Export Parameters, specify a filename, and then click Save. To import these settings into CAPE, view the desired relay in CAPE DBE, click the Settings I/O button, then Import from ABB PCM 600 v2.x XRIO file, and finally choose the file created from PCM.

Please be aware that the parameter identifiers in the XRIO file are not identical to the tap names used in CAPE. Because of this, alternative tap names (parameter I/O names) are needed in CAPE to allow translation of XRIO file identifiers and CAPE tap names. If your CAPE relay library information does not include these identifiers, then the settings transfer will not work well. To correct this problem, you can re-import the REx670 styles

2


from a new copy of our cape_starter database (our master relay library). At this time, the RED670, REL670 and RET670 models are supported. PST (Parameter Setting Tool) Transferring settings from PST to CAPE is supported via a PST print file. To create this file from within PST, choose File | Print, and then turn on the Print to file option at the bottom of the print dialog. Specify a text file name, and click OK. To import these settings into CAPE, view the desired relay in CAPE DBE, click the Settings I/O button, then Import from ABB Parameter Setting Tool text print file, and finally choose the file created from PST.

3


RELTools - RELWise The RELWise software is for REL512 relays only. Transferring settings from RELWise to CAPE is supported via a text print file. To create this file from within RELWise, choose File | Print, and then turn on the Print to a File option in the middle-left of the print dialog.

Click Print, and then specify a text file name. To import these settings into CAPE, view the desired relay in CAPE DBE, click the Settings I/O button, then Import from ABB REL512 text file. Choose the file created from RELWise. If the file was created with more than 1 settings group, you will need to select the group that you would like to import. Text files created by RELWise versions 2 and 3 are now supported. RELWise cannot import settings from these text files, so exporting setting from CAPE to this text file format is not supported.

4


WinRCP The WinRCP software can export a text settings file. To create this file, view the settings in WinRCP, then click the save icon and name the text file.

To import these settings into CAPE, view the desired relay in CAPE DBE, click the Settings I/O button, then Import from ABB WinRCP text file. Choose the file created from WinRCP. This has been verified to work (at least partially) for the MDAR, REL301/302, REL350, and REL352 relay models. Alstom (Areva) MiCOM version 2.x The MiCOM software is divided into 3 parts: S&R-Courier; S&R-103; and S&R-Modbus. Each of these modules supports a different set of relays and uses a different settings file format. At this time, there is no support in CAPE for working with S&R Modbus files. MiCOM version 2.x S&R Courier The native file format for the S&R Courier software is a binary *.set file. Preliminary support for importing settings from this file format is included in CAPE. To use this feature, view an Alstom relay in the DBE, click the Settings I/O button, and then select the item Import from Areva/Alstom settings file (*.set). You will see a warning message indicating that the import feature is still under development, and you will be

5


asked if you want to continue. Clicking Yes leads to a file selection dialog where you can choose the desired *.set file. After selecting the file, you will be prompted with a list of all the setting groups found in the file. Some or all of these can be selected for import. In general, CAPE styles contain only group 1 settings, so any settings at address 5000 or higher (groups 2, 3 and 4) should not be selected for import. Success or failure messages will be written to the DBE log file during the import process. Please keep in mind that this import function is preliminary. Not all of the information in the file can be imported. Valid *.set files can be produced from the MiCOM S&R Courier setting software only. Files produced by the MiCOM S1 S&R Modbus software also use the *.set file extension, but are NOT in the same format, and CAPE cannot import them. MiCOM version 2.x S&R 103 Transferring settings from S&R-103 to CAPE is supported via text print files. To facilitate this transfer, some CAPE relay styles have been enhanced to include the relay tap address in the CAPE tap description field. This provides a way for the DBE to link the settings in the text file to settings in CAPE. To create a text file from S&R-103, view the relay, choose File | Print File, and then give the text file a name. To import these settings into CAPE, view the desired relay in CAPE DBE, click the Settings I/O button, Import from Areva/Alstom S&R-103 text export file, then choose the file created from S&R-103. Next you will see a screen allowing selection of the settings group to import. CAPE styles typically contain the global and setting group 1 settings, so these options should be set. If you have modified the relay style to contain group 2, 3 or 4 settings, you can import them also. Please note that if you choose to import groups that do not exist in the CAPE style, the DBE log file will contain failure messages for these additional parameter sets. This transfer has been verified to work for the P130C, P132, P433, P435, and P437 relay models.

6


MiCOM S1 Studio version 3.x MiCOM S1 Studio 3.0 was released in March 2008. This software package encompasses the 3 previous packages (S&R Courier, Modbus and 103), and also provides an additional option for settings export. By right-clicking on a settings record in the Studio Explorer you can choose Export to CAPE Format. This is a comma-separated text file format, specifically created to facilitate settings transfer with CAPE. As of S1 Studio version 3.0, these files can be created for settings transfer to CAPE. We expect that future versions of S1 studio will allow importing settings from this file format, thus providing a path for settings transfer from CAPE to MiCOM. To import these settings into CAPE, view the desired relay in CAPE DBE, click the Settings I/O button, Import from Areva MiCOM S1 Studio settings file, and then choose the file created from S1 Studio. The next screen allows some control over the log messages that will appear during the settings import. After specifying the log options, the next screen allows selection of the settings group to import. Depending on the type of relay that you are importing (COURIER or S&R-103), the options will be slightly different, but both are similar in that you can choose to import one or more of the global and groups 1 through 4. CAPE styles typically contain the global and setting group 1 settings, so these are the obvious ones to import. For COURIER type relays, you have the option of importing group 2, 3 or 4 settings and putting them in CAPE as group 1 settings. This is useful because CAPE always uses the group 1 settings for simulation, so translating group 2, 3 or 4 settings to group 1 allows you to perform CAPE simulations using group 2, 3 or 4 settings. If you have modified the relay style to contain group 2, 3 or 4 settings in addition to group 1, you can import all settings without address translation (the first choice in the list). Please note that if you choose to import groups that do not exist in the CAPE style, the DBE log file will contain failure messages for these additional parameter sets. These failure messages will reference tap addresses 5xxx and 6xxx for group 2, 7xxx and 8xxx for group 3, and 9xxx, Axxx for group 4. Important point to remember: CAPE relay styles are typically created with setting values specified in SECONDARY quantities. One of the relay setting parameters in S1 studio controls if the displayed quantities are in PRIMARY or SECONDARY (usually address 092E). This MUST BE set to SECONDARY before exporting the settings to a text file. Otherwise, primary values will be exported, which are not correct for use in CAPE.

7


For S&R-103 type relays, you have the option of importing one or more groups. Typically, you should select Global and Setting Group 1. The settings transfer from S1 Studio files has been verified to work with: P123; P343; P433; P435; P441; P442; P443; P444; P445; P543; P544; P545; P546; P547; P633; PD532; PD551; PD571. MiCOM S1 Agile version 1.x MiCOM S1 Agile was released in September 2012, and is the successor to S1 Studio. From a relay settings management perspective, this software is essentially identical to the previous S1 Studio. The exported setting files are in the same format. Please refer to the previous section describing S1 Studio, as all the material also applies to S1 Agile. WinEPAC32 V6G WinEPAC is somewhat old (2001) software for managing EPAC relay settings. The native file format for this software is a text *.cnf file. These *.cnf files contain French setting-name references, numeric setting values, and integer index numbers to refer to discrete text tap values. To import these settings into CAPE, view the desired EPAC relay in CAPE DBE, click the Settings I/O button, then Import from EPAC settings file. When prompted, select the *.cnf settings file. The import handles most, but not all settings in the file. Exporting settings from CAPE to a *.cnf file is not supported. Basler Electric BESTCOMS There is BESTCOMS software to support several of the newer Basler relays including the BE1-851, BE1-951, BE1-IPS100, BE1-CDS220 and others.

8


These software packages can export settings to a text file. For the BE1-851 and BE1-951, the BESTCOMS software supports exporting to either a *.TNP or a *.txt format. It also supports importing from the *.TNP format. To facilitate bi-directional settings transfer, CAPE supports the *.TNP format and not the *.txt format. To import these settings into CAPE, view the desired relay in CAPE DBE, click the Settings I/O button, and then Import from BESTCOMS *.TNP file. For the BE1-IPS100 and BE1-CDS220, the BESTCOMS software supports only exporting to a text (*.txt) file. To import these settings into CAPE, view the desired relay in CAPE DBE, click the Settings I/O button, and then Import from BESTCOMS text export file. Beckwith At this time, there is no official support for transferring settings to/from any Beckwith relay software. There is development work in progress to support the transfer of settings between CAPE and IPScom M-3425 series relay files. This development work involves using a Beckwith-created utility to transfer settings between the native binary *.dat file, and an XML text setting file. CAPE can then transfer settings with the XML file. ERLPhase (formerly NxtPhase) Offliner Settings transfer from Offliner to CAPE for BPRO (*.bps or *.b1s), FPRO (*.fps), LPRO (*.lps) and TPRO (*.tps) text files is supported. Transfer of settings from CAPE to Offliner is not supported at this time. The *.bps, *.b1s, *.fps, *.lps or *.tps files are the native file format for the Offliner software, so no special steps are required to create a file for CAPE import. To import settings into CAPE, view the desired relay in CAPE DBE, click the Settings I/O button, and then Import from ERLPhase settings file. Not all settings are correctly transferred at this time. Taps that can be set to one of a list of different text values are not always handled correctly. The text setting file often contains a number 0...n, indicating the index of the selection, but CAPE contains the actual text values. Translating between these two setting representations is problematic. The link between a CAPE tap name and a tap name in the text file is established by using the Tap Description value from the CAPE relay library. You may need to re-import the NxtPhase relay models into your CAPE library to get these updated tap descriptions.

9


General Electric EnerVista (ALPS/LPS relays) Settings transfer from EnerVista to CAPE is supported via the text report file output from the ALPS Set software. The export is located in the File | Save Settings Report As menu. Select ALL CATEGORIES, and then give your text file a name.

To import these settings into CAPE, view the desired relay in CAPE DBE, click the Settings I/O button, and then Import from ALPS/LPS text export file. EnerVista (UR series relays) Settings transfer from EnerVista to CAPE is supported via the CSV text file export from EnerVista. EnerVista does not support importing these CSV files, so a CAPE-to-EnerVista transfer is not possible. To export a CSV file, right-click on the settings file in the Offline Window tree view in EnerVista, and then select Export Settings File.

On the print/export options form, choose group 1 only, and Include All Features. The resulting CSV file can be imported into CAPE.

10


To import these settings into CAPE, view the desired relay in CAPE DBE, click the Settings I/O button, and then Import from EnerVista CSV text export file. You will be prompted with a list of functions found in the CSV file. By un-checking some functions, you can limit the scope of the settings import. Typically, function names that include the text GROUP 1 are desired. Others may also be useful. At this time, CAPE supports the following GE UR series relays: B30; B90; D30; D60; D90, F35, F60; L90; T35; and T60. Note: With each version of the EnerVista software it is not uncommon to have some tap names change slightly. These small differences in tap names will prevent the setting values from being correctly transferred to CAPE. Until General Electric starts using a fixed, unique name for each setting parameter in the exported CSV file, there is nothing we can do to prevent these problems. Nanjing Nari-Relays Electric Co. (NARI) RCS-PC The RCS-PC software allows communicating with, and managing settings for various NARI relays. At this time, CAPE supports only the RCS-941 relay. Settings transfer from NARI text settings files to CAPE is supported. Transfer of settings from CAPE to a NARI file is not supported at this time. To create a text file suitable for transferring settings you must:

View the desired settings in RCS-PC Select the Execute | Setting menu On the settings screen, click save, then name the file.

To import settings into CAPE, view the desired relay in CAPE DBE, click the Settings I/O button, and then Import from NARI RCS-PC settings file (*.set). Schneider SFT2841 At this time, relays supported by SFT2841 are not yet modeled in CAPE, so settings transfer between CAPE and SFT2841 is not supported. However, SFT2841 does use a text file to store settings, so settings transfer should be possible in the future. Once CAPE models have been created, then more work can be done to support settings transfer.

11


Schweitzer SEL-5010 The SEL-5010 program stores settings in an MS Access database. Settings can be easily transferred between these MS Access files and CAPE. To invoke the settings transfer, view the desired relay in CAPE Database Editor, then click the Settings I/O button. On the Import or Export Settings? popup, select either Import from SEL-5010 mdb file or Export to SEL-5010 mdb file. To successfully transfer settings with a SEL-5010 mdb file, CAPE must be able to find the SEL-5010 system database (SEL5010.mdw). If this file cannot be found automatically, you will be prompted for it. Usually, this file is located in the SEL-5010 installation directory. Once the system database has been found, CAPE will next try to find the master SEL-5010 settings database. If CAPE is able to determine where your master SEL-5010 database is located, it will connect to it automatically. Otherwise, you will need to choose the database manually. You can choose either your master 5010 database, or any single-relay export database created from SEL-5010. After selecting the database, you will see the search form for picking the desired relay, scheme and group(s). In the case of a master SEL-5010 database, there will be many relays to choose from. A single-relay export database will contain only one relay.

Choose the desired scheme from the 5010 database, and then select one or more groups to import. Click the Import button to transfer settings into CAPE. Please note that a CAPE

12


relay model typically does not contain groups 2-6, or port settings beyond P1. See Appendix A for details on how to store these additional settings in your CAPE database. *Note: In CAPE, text-type settings can be at most 100 characters in length. Some SEL taps, notably logic settings, can contain values that are longer than 100 characters. If you need to support a text setting longer than 100 characters in CAPE, you must create a second tap with a name of .2 (.3, .4, etc). When transferring settings to/from SEL-5010, CAPE will look for these extended taps, and treat them as one long setting. This comment also applies to SEL-5030 I/O. AcSELerator (SEL-5030) RDB Files The AcSELerator program stores its relay setting data in a *.rdb file. This file is in a structured storage format which CAPE can read or update directly. To transfer settings between a SEL-5030 RDB file and CAPE, view the desired relay in the CAPE Database Editor, and then click the Settings I/O button. On the Import or Export Settings? popup, select one of the choices Import from SEL-5030 RDB file or Export to SEL-5030 RDB file. Either choice will lead to a similar series of popup forms allowing some degree of control over the settings transfer, and resulting in settings being either transferred from the RDB into CAPE (import), or from CAPE into the RDB (export). The first screen (not shown) allows selection of the desired *.RDB file. The second screen (shown at right) allows selecting the desired relay from a list of all relays contained in the RDB. The third screen (shown at right) allows selecting the setting files (setting groups) that you would like to transfer from within the selected relay. The final screen (shown below) allows changing some options associated with the settings transfer.

After clicking OK on the Setting I/O Options form, the settings transfer will begin. The mechanics of this transfer is essentially identical to the transfer of settings between CAPE and AcSELerator text files, which is described in the next section.

13


AcSELerator (SEL-5030) Text Files The SEL-5030 program can import and export settings in plain text files. SEL-5030 will export settings in several text files, one for each group. Using these files, settings can be easily transferred between 5030 and CAPE. To export settings from SEL-5030, view the desired relay and then click the Export button. Select all groups that you would like to export. One text file will be created for each group that you select. Please note that a CAPE relay model for a Schweitzer relay typically contains only 1 copy of each setting group. See Appendix A for details on how to store these additional settings in your CAPE database. To invoke the settings transfer in CAPE, view the desired relay in the CAPE Database Editor, then click the Settings I/O button. On the Import or Export Settings? popup, select one of the choices Import from SEL-5030 text file, Export to SEL-5030 text file, Import directory of SEL-5030 text files, or Export directory of SEL-5030 text files. Either of the first two choices will lead to a file selection dialog where you can choose one of the files created by 5030. With these options, only a single file can be selected at a time so transferring all the settings will take several passes. To process many files at once, use the third or fourth choice, and select the directory containing the text files. After selecting the directory, you will be prompted with a list of all files in the directory. Each file represents one group of settings. As noted above, a CAPE model typically contains only one of each setting. Multiple groups are not represented in one relay style. For this reason, you will want to select only one file from each group (A1-A10, L1-L6, S1-S6). In some CAPE models, an exception is made for PORT settings (P1-P3, PF). These are sometimes all represented in a single style. If, during the file selection step above, you were to inadvertently select two files from the same group (S1 and S2 for example), you would see a message during the import indicating that a tap has already been imported. If you see this message, No to All is almost certainly the correct answer. This will prevent the S2 settings from overwriting the S1 settings.

14


After selecting the files to import (or export), the next popup provides some additional data transfer options. The Transfer tap comments allows control over the transfer of user comments that may exist in the SEL-5030 files for each tap. Sometimes the CAPE model for a relay is not a perfect match for the actual relay. There may be a few settings in the actual relay that CAPE does not contain, or perhaps the CAPE model that you are using includes some taps that do not exist in the actual relay that you ordered. Depending on the situation, you may or may not want to see log messages about taps that do not exist in both CAPE and the relay vendor file. The two options Report source taps not found in CAPE and Report CAPE taps not found in source allow suppressing log messages about this type of mismatch. The final option available controls if you want to see log messages about ALL taps, whether their setting changed or not, or if you would prefer to see messages only for taps that changed. When exporting settings from CAPE to SEL-5030, you must first create the text settings files by exporting settings from SEL-5030. Then, choose the export option from CAPE and select the pre-existing text file(s). CAPE DBE will modify the selected file, changing the tap values to those stored in CAPE. After updating the text files, you can import them into SEL-5030. Siemens DIGSI 4.3 thru 4.7 DIGSI 4.3 thru 4.7 can store settings for various versions of Siemens relays. Settings for many of these devices can be transferred from DIGSI to CAPE via ASCII text files. For devices identified as SIPROTEC 3, settings can be exported to an ASCII file (*.asc). Using this file format, settings can be transferred from DIGSI to CAPE. Transfer of settings from CAPE to DIGSI is not supported since DIGSI provides no way of importing settings from the *.asc files. To export a *.asc file from DIGSI, view the device in offline mode. Select the Offline item in the left-hand tree view, then right-click on the Parameter item in the right-hand window. Choose ASCII Export, then name your file. For devices identified as SIPROTEC, settings can be exported to an ASCII file (*.elc). Using this file format, settings can be transferred from DIGSI to CAPE. Transfer of settings from CAPE to DIGSI is not supported since DIGSI provides no way of importing settings from the *.elc files. To export a *.elc file from DIGSI, view the device in offline mode. Next, choose File | Export | Configuration and Protection parameters. Specify a name for the *.elc file. To import either *.asc or *.elc files into CAPE, view the corresponding relay in the CAPE Database Editor, then click the Settings I/O button. On the Import or Export Settings? popup, select Import from DIGSI 4 text file. Next, choose the *.asc or *.elc file name.

15


Note: When importing from a *.elc file which contains multiple setting groups, you must choose ONE group to import. CAPE relay styles typically contain settings for only one group. DIGSI 4.6, 4.7 Both DIGSI 4.6 and 4.7 support importing and exporting settings in XML format. This format is superior to either the *.asc or *.elc text format as it supports more settings. To export a *.xml file from DIGSI, view the device in offline mode. Next, choose File | Export | System Interface (XML). Specify a name for the *.xml file. To import a *.xml file into DIGSI, right-click on a relay in the DIGSI Manager and selecting Import Device change the file type to XML, then select the XML settings file. To import the *.xml settings file into CAPE, view the corresponding relay in the CAPE Database Editor, then click the Settings I/O button. On the Import or Export Settings? popup, select Import from DIGSI 4 XML file. Next, choose the *.xml file name. Settings can also be transferred from CAPE to DIGSI using XML files. For best results, create the XML file first by exporting settings from DIGSI. Then, in CAPE DBE, view the corresponding relay and click the Settings I/O button. On the Import or Export Settings? popup, select Export to DIGSI 4 XML file, and choose the file created by DIGSI. DIGSI 4.8 DIGSI 4.8 can both import and export settings in a text XML format. This is similar to the XML I/O feature of DIGSI 4.6 and 4.7, but the file format is a little different, and it now covers ALL settings. Previously, some settings were not included in the XML file. CAPE supports transferring settings both from DIGSI to CAPE, and CAPE to DIGSI using these XML files. When transferring settings from CAPE to DIGSI, the XML file must already exist, so you must first export a file from DIGSI, then export settings from CAPE to the same file. To invoke the XML import/export function in DIGSI, right-click on a device, then choose either Export device or Import device.

16


When specifying the file name for export, be sure to set the file type to DIGSI 4 transfer file (*.xml). To import the *.xml settings file into CAPE, view the corresponding relay in the CAPE Database Editor, then click the Settings I/O button. On the Import or Export Settings? popup, select Import from DIGSI 4 XML file and then choose the *.xml file name. Settings can also be transferred from CAPE to DIGSI using XML files. This is a 3-step process. 1. Create the XML file by exporting settings from DIGSI as described above. This creates

a file with the correct structure. 2. Export settings from DBE to the XML file. This is done by viewing the corresponding

relay in DBE, clicking the Settings I/O button, choosing Export to DIGSI 4 XML file, then choosing the XML file created by DIGSI.

3. Import the settings into DIGSI. This is accomplished by right-clicking on the device in DIGSI, choosing Import device, and then selecting the XML file.

Sometimes, the setting values in CAPE are not identical to the setting values in the DIGSI XML file. To accommodate this possibility, the settings import/export between CAPE and a DIGSI 4 XML file uses a conversion template. This template serves as a cross-reference between setting values in CAPE, and setting values in the XML file. This is most often necessary when working with non-English XML files. CAPE relay models are almost always created in English, so setting values in any language other than English will require conversion. When the XML file is selected for settings transfer is in DIGSI 4 XML format, you will be prompted to select a conversion template. If a conversion template for the selected relay model already exists, it will appear in the list along with the choices to create a new template, or not to use a template. If your XML file is in English, then you probably do not need to create or use a conversion template. If your XML file is not in English, then you should definitely use a conversion template. If a suitable conversion template exists, select it. Otherwise select Create new conversion template and you will be prompted for name for your new template. The default name is the name of the model in the DIGSI XML file. If any setting can not be transferred due to a mismatch in valid values, you will be prompted with a list of valid values, and you must provide a translation. Each time you answer a prompt like this, the conversion template is updated to "remember" your answer. In this way, the

17


conversion is improved so that next time you import or export a settings file it will already know how to translate many of the settings. Please note that the settings translation is stored on a per-tap basis, so you may have to provide the same translation multiple times. The conversion templates are stored in the file \xml\Settings_Converters\.xml. VAMP VAMPSET The VAMPSET software supports many models of VAMP relays. At this time, CAPE supports the VAMP 40, VAMP 135 and VAMP 140 models. The native file format for this software is a text *.vf2 file. To import these settings into CAPE, view the desired VAMP relay in CAPE DBE, click the Settings I/O button, and then Import from VAMP VF2 file. When prompted, select the *.vf2 settings file. The import handles most, but not all settings in the file. Exporting settings from CAPE to a *.vf2 file is not supported. ZIV ZivercomPlus At this time, relays supported by ZivercomPlus are not yet modeled in CAPE, so settings transfer between CAPE and ZivercomPlus is not supported. However, ZivercomPlus does use XML files to store settings, so settings transfer should be possible in the near future. Once CAPE models have been created, then more work can be done to support settings transfer.

18


Appendix A: Working with Relays that Contain Multiple Setting Groups Many modern digital relays allow storing multiple groups of settings. While only one group can be active at any given time, you can easily change the active group, thereby changing many setting values all at once. When we create relay models in CAPE to simulate a device, we typically include only one copy of each tap setting. This is sufficient for coordination studies, and is all that is needed for most users. Should the need arise, it is possible to store more than one group of settings in CAPE by using the alternative setting groups feature. This feature allows storing a complete duplicate copy of the relay settings. To create an alternative settings group, click the Copy button in the Group Displayed region of the Protective Device Data screen.

Give your new group a name, indicating that these are S2 settings. To allow importing or exporting settings to/from your new group, set the Group Displayed to your new group name.

Now, the Setting I/O function will transfer settings between the relay vendor files and this alternative settings group. If you would like to perform coordination studies in CAPE using one of these alternative setting groups, simply set the Active Group to the alternative group that you would like to work with. There is no limit on the number of setting groups a relay may have. Further, any relay in CAPE may have alternative setting groups, including ancient electromechanical relays. Therefore, you could use this feature to hold future or historical settings, not merely the alternative groups the physical device may support.

19

Status of Links BetweenCAPE and Relay Vendor Setting SoftwareThis document is the sole property of Electrocon International, Inc. and is provided to the CAPE Users Group for its own use only. It may not be supplied to any third party, or copied or reproduced in any form, without the express written permission...Links Between CAPE and Relay Vendor Setting SoftwareABBCAP 540RELTools - RELWiseAlstom (Areva)MiCOM version 2.xMiCOM version 2.x S&R CourierMiCOM version 2.x S&R 103OfflinerSFT2841SEL-5010DIGSI 4.6, 4.7DIGSI 4.8ZivercomPlus

status of links between cape and relay vendor setting software

Documents