Tips & Tricks

27

TEST UNIVERSE

Tips & Tricks

OMICRON Test Universe

Manual Version: TipsTricks.AE.6 - Year 2010 © OMICRON electronics. All rights reserved. This manual is a publication of OMICRON electronics GmbH. All rights including translation reserved. Reproduction of any kind, e.g., photocopying, microfilming, optical character recognition and/or storage in electronic data processing systems, requires the explicit consent of OMICRON electronics. Reprinting, wholly or in part, is not permitted. The product incomputeration, specifications, and technical data embodied in this manual represent the technical status at the time of writing and are subject to change without prior notice. We have done our best to ensure that the incomputeration given in this manual is useful, accurate and entirely reliable. However, OMICRON electronics does not assume responsibility for any inaccuracies which may be present. The user is responsible for every application that makes use of an OMICRON product. OMICRON electronics translates this manual from the source language English into a number of other languages. Any translation of this manual is done for local requirements, and in the event of a dispute between the English and a non-English version, the English version of this manual shall govern.

2

Table of Contents

Table of Contents 1

General Remarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5

2

First Steps with OMICRON Test Universe . . . . . . . . . . . . . . . . . . . . . . . . . . .5 2.1 Start Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5 2.2 Basic "Front Panel" Testing: QuickCMC . . . . . . . . . . . . . . . . . . . . . . . . . .8 2.3 Generating Test Steps with State Sequencer and Ramping . . . . . . . . . . .9 2.4 Combining Test Modules in an OCC Document . . . . . . . . . . . . . . . . . . . .9 2.5 Advanced Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10

3

How to Simulate Circuit Breaker Contacts . . . . . . . . . . . . . . . . . . . . . . . . .10

4

How to Monitor all Binary Input States . . . . . . . . . . . . . . . . . . . . . . . . . . . .10

5

How to Manually Set Binary Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11

6

How to Predefine Typical Channel Assignments for COMTRADE Playback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11

7

How to Test Transient Ground Fault Relays . . . . . . . . . . . . . . . . . . . . . . . .12

8

How to Get, Use and Modify a Relay-Specific PTL Template . . . . . . . . . .12

9

How to Test Differential Relays with Delta Interposing Transformers . . .12

10

How to Generate a Double Line-to-Ground Fault . . . . . . . . . . . . . . . . . . . .13

11

Test Assessment Fails - Things to Check . . . . . . . . . . . . . . . . . . . . . . . . . .13 11.1 Binary Inputs Operating Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13

12

How to Check if a Binary Input State has Temporarily Changed ("Glitch Detection") . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13

13

How to Prevent CMC Switch-Off at High Output Currents due to Overheating . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14

14

How to Duplicate or Rearrange OCC Entries . . . . . . . . . . . . . . . . . . . . . . .14

3


15

How to Reuse Custom Parameters in Multiple Test Modules with Differing Test Object Needs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15

16

How to Change the CMGPS Setup for External Use. . . . . . . . . . . . . . . . . .16

17

How to Get Access to a Net-1 Test Set . . . . . . . . . . . . . . . . . . . . . . . . . . . .16

18

How to Import Relay Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18

19

How to Test Distance Relays with Constant Source Impedance Simulation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19

20

How to Handle Test Report Settings (Forms) . . . . . . . . . . . . . . . . . . . . . . .21

21

Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23

4

Tips & Tricks

1 General Remarks This collection of tips and tricks is intended to address Test Universe novices as well as experienced users. •

Section 2 guides beginners through the first steps with Test Universe .

•

More experienced users will find useful hints in the other sections of this collection.

This way, "Tips & Tricks" supplements the Help (functional description of the Test Universe software) and the manuals (application examples using the individual test modules). The bookmarks in the left pane of your PDF reader provide an overview of the available topics.

2 First Steps with OMICRON Test Universe Test Universe (TU) is the software suite for setup, execution and administration of secondary system testing (e.g., relay testing) by means of one or several test sets such as CMC 256 that generate the test signals and analyze the reaction of the device under test. These hints are intended for users not yet familiar with the general concept of Test Universe. Please also have a look at the Tutorials (see entry on Start Page, via installation from DVD) that give a live demonstration of some aspects of Test Universe.

2.1 Start Page The OMICRON Start Page is the central navigation interface when launching Test Universe. Its tools cover all aspects from simple test shots to complex and/or automated test sequences as well as the maintenance of test setups and results. The Test Modules section allows the individual launching of modules for diverse test purposes, from generic ("virtual front panel") QuickCMC over general (Ramping, State Sequencer) and dedicated (Overcurrent) to network simulation.

5


CB Configuration controls the parameters of a process that may run in parallel to ongoing tests. It simulates the behavior of a circuit breaker (timing of position contacts 52a and 52b as resulting from Open or Close commands) using binary inputs and outputs of the connected CMC. The Control Center section allows the bundling of individual modules (as those listed in the Test Modules section) to form complex test sequences. Besides arranging modules as needed in a so-called Control Center Document (*.occ file) from New Test Document you may directly use predefined test arrangements defined for specific relay types using Open Protection Library. These OCCs are open to further alterations as needed. This library is updated on a regular basis, announced on the Web site and in the OMICRON News window (see above). The Test Administration section gives access to TestBase, a powerful test administration software that can be ordered for free via the OMICRON Web site Customer Area. Separate help for this tool is available from its user interface. The Test Tools section contains further test-related applications that are to be used in a stand-alone fashion as opposed to the modules under Test Modules that can be included in Control Center documents. AuxDC allows setting the voltage of the AuxDC output of adequately equipped devices (e.g. CMC 256). In the Setup section you find all means to set up your working environment. With the Test Set Association component you associate and configure your OMICRON CMC test set(s) via Ethernet. Using the Ethernet interface, you can put as many CMC test sets as you wish on the network and control them by even geographically remote computers (clients). System Settings provides the means for system-wide default settings. The License Manager combines the functionality of a license browser, a merge tool and a license file editor. It searches for OMICRON license files stored on the computer's hard disk(s) and displays their contents. It merges license information from different files into the master license file Omicron.lic. It furthermore allows to add license keys manually. And Language Selection lets you change default language for the Test Universe user interface. The Support section offers access to the Help (describing the handling of the software tools), the manuals (describing typical applications with examples), OMICRON Assist for troubleshooting support, and more. The Custom section might contain pre-configured entries for certain customers, and is open for your own add-ons of external programs that you would like to launch from this location. If interested please click the User-specific Tools link to learn how this can be done.

6

Tips & Tricks

The header area contains links to OMICRON Web sites. Furthermore, if your computer has access to the Internet and when an update to your current TU software version is available, a related link will be shown underneath the version indication allowing you to directly look up the related information on the Web site. But now some first steps for actual testing:

7


2.2 Basic "Front Panel" Testing: QuickCMC Launch QuickCMC, the first entry under Test Modules. The module starts in Direct Set mode, i.e., you can directly define the currents and voltages per output. In other set modes you may define the quantities, e.g., as fault impedance. Via the V I E W menu (or the related toolbar icons) you may display an additional Vector view (allowing the representation of the electrical quantities in various ways, e.g., symmetrical components, power, …) and/or an Impedance view (e.g., for simple tests of distance relays). For the overall TU philosophy it is essential to note that two setups should be edited according to your needs: The Test Object parameters (from the P A R A M E T E R S pull-down menu or via toolbar icon, see the ToolTip showing when pointing at an icon) describing the device under test (DUT) (e.g., the tripping zones of a distance relay which will show up in the Impedance view), and the test equipment itself (P A R A M E T E R S | H A R D W A R E C O N F I G U R A T I O N or the related toolbar icon) where you, for example, can combine the 6 currents of a CMC 256 in various ways from generating 6 individual currents to generating just one current but with a much higher magnitude and/or compliance voltage. Here you also set the definition and routing of binary input and output signals (these are, for example, shown in the Binary Inputs/Trigger section of the QuickCMC Test view). So, whenever you use a module (QuickCMC or any other one), check the Test Object and hardware settings prior to executing tests with the module. Test Object - Hardware Configuration - Test Module OMICRON’s Ohm’s law ;-) You will later see that this approach shows its full power when combining tests in a Control Center document where you may do these definitions just once for common usage in all modules. For all details regarding the user interface and functions of QuickCMC please make use of the Help function which also provides a link to a PDF manual containing a detailed working example. Take your time to explore all QuickCMC features: right-click the Test view’s Analog outputs elements for default value setting; explore the abs/rel and time/cycle display options; select the "Trigger" signal that should detect the successful reaction of the DUT; mark "Switch off" under "On Trigger" if signal output shall automatically stop at this trigger; use F8 to generate healthy voltage prior to fault output; start (and possibly stop) the actual fault output with F5. If you would like to add the test data to a test report, click F10 (check the Report view for results). Saving the test module saves all settings (including hardware and test object) plus all stored test results in one test file that can later be reopened to view or be re-used for another test with similar settings. Even step ramping and pulse ramping can be achieved with QuickCMC (see the aforementioned documentation for details).

8

Tips & Tricks

2.3 Generating Test Steps with State Sequencer and Ramping Once you are familiar with QuickCMC and the OHM concept you may want to try out State Sequencer. To put it simple, State Sequencer links a sequence of QuickCMC-like shots (states) and tracks the reaction of the DUT. The transition trigger from one step to the next can be individually set up, e.g., a fixed time delay, a binary input signal (see the Trigger tab in Detail view). This module is ideally suited for time measurements. For more details see its Help, also including a link to the PDF manual with a dedicated application example. Ramping and Pulse Ramping modules are best suited for threshold determination. For more details see its Help, also including a link to the PDF manual with dedicated application example.

2.4 Combining Test Modules in an OCC Document Once you are familiar with the various test modules you may want to combine several of them to a test sequence. This is done using the Control Center features. On the Start Page, select New Test Document. The newly created OCC document already contains a Test Object (TO) and a Hardware Configuration (HWC) block to remind you that it is good practice to define these settings in advance. Please open each and set them as needed for the test. You may now insert test modules as needed via the pull-down menu I N S E R T | T E S T M O D U L E . . . or the module icon bar (make it visible by clicking V I E W | T E S T M O D U L E S T O O L B A R ). Note that all modules inherit settings from the preceding TO and HWC. You may insert additional TO and/or HWC further down the sequence, if required; they will apply to succeeding test modules. If you deal with many modules in one document you may hierarchically structure them using I N S E R T | G R O U P . You may execute any module in the OCC (use the OCC as collection of individual tests) or typically execute all contained modules in sequence for a combined test. The right side shows the report section for each test module, so the OCC file contains all test reports together with the test settings. You may add text, graphics (e.g., your company logo) etc. in the report area; even Microsoft Excel spreadsheets etc. for added information. Please see the Help for details.

9


2.5 Advanced Features One great advantage using a central TO in an OCC is that all modules can access relay parameters from the TO by linking to them instead of using fixed value settings (e.g., a ramping limit can be dynamically derived from a relay parameter). This drastically reduces the maintenance effort when re-using an OCC for relays with different settings. Look for "LinkToXRIO" in the Help index for details of this great feature. The OCCs in the Protection Testing Library make extensive use of this approach. It might be quite interesting to load a PTL template (Open Protection Testing Library in the Control Center section of the Start Page) as a working example and have a look at the Test Object entries and at the links in the test modules to get an impression of the strength of this approach. For specialist applications with sophisticated scripting please have a look at the Automation and CM Engine chapters in the Help.

3 How to Simulate Circuit Breaker Contacts Launch CB Configuration from the Start Page to set up the behavior of the simulated contacts 52a and 52b, i.e., to simulate the timing of closed-position and opened-position contacts of a circuit breaker (via binary CMC outputs) reacting to Trip and Close commands (received via binary CMC inputs). By default, Binary Input 1 is CB Trip and Binary Input 3 is CB Close, while Binary Output 1 is CB 52a and Binary Output 2 is CB 52b (open the HWC from CB Configuration for these settings). Transmit the prepared setting and simulation initiation via the "Send CB Parameters to CMC" toolbar icon. CB Configuration can now be closed. No other test module or OCC needs to be open, the CMC does the CB simulation all by itself until a Stop is transmitted (by clicking the above mentioned "Send CB Parameters..." toolbar icon) from the newly launched CB Configuration, or when the CMC is turned off.

4 How to Monitor all Binary Input States Use the test tools Binary I/O Monitor from the Start Page.

10

Tips & Tricks

5 How to Manually Set Binary Outputs While you can activate binary outputs in QuickCMC, these are only activated as long as the analog outputs are activated (i.e., F8 Prefault or F5 Outputs ON/ OFF). If you want the contacts to keep their state while continuing with other test tasks, launch State Sequencer. It contains one default state, which is all we need for this task. Set all voltages and currents to zero (right-click on the value, select 'Zero' and then 'Equal magnitudes'). Select T E S T | L A T C H I N G B I N A R Y O U T P U T S . Go to Detail view, Binary Out tab. Set the contact states as needed. To transfer this state set, either click the "Start/continue test" toolbar icon or click and release the "Static output" toolbar icon. You may now close the module (possibly save it for later re-use) and work with another test module or test document. The binary output states will stay as selected until a test module redefines the states or the unit is switched off. The same latching can of course be achieved in an automated fashion by including such a single-state sequence in an OCC test document.

6 How to Predefine Typical Channel Assignments for COMTRADE Playback •

Launch Advanced Transplay

•

Set up the Hardware Configuration

•

Save this "empty" Advanced Transplay file (*.tra)

•

Load this template file before importing a COMTRADE file. This gives you the predefined assignment. Save under a new name.

•

Set up and save as many different template files as needed for your typical setups.

11


7 How to Test Transient Ground Fault Relays From the Start Page section Network Simulation… launch the test module Transient Ground Fault, and start the related Help. Note: This test module is intended for isolated or compensated grid operation, only. These transient ground fault relays typically signal the fault direction without the need to instantly trip, and rely on the transient phenomena at fault incidence for their operation, thus this dedicated module is required for these cases.

8 How to Get, Use and Modify a Relay-Specific PTL Template New versions are frequently added to be downloaded from the Customer Area of our Web site www.omicron.at. Each template is accompanied by a detailed description about its proper handling. Since these templates are "normal" OCC files, they can be modified as needed by staff experienced with TO editing, LinkToXRIO etc., e.g., to adapt test steps to your company testing philosophy. Adding new test steps might be done best in a new subgroup in the OCC to differentiate these entries from the parts delivered (and documented) by OMICRON. Save the resulting OCC under a different name to be used as a new template.

9 How to Test Differential Relays with Delta Interposing Transformers The interposing transformer can be seen as a part of the protection system and therefore it is recommended to test it together with the relay. The CMC current generators are internally Y-connected to the neutral. So, for testing Differential relays using an interposing transformer and therefore having delta circuits on their input side, it is recommended to test the relay as a complete system together with the corresponding interposing transformer. In general the interposing transformers use YD vector group, hence the question of how to connect CMC is as well answered. That means, if you connect on the Y side of the interposing you will have a starpoint available to connect the CMC neutral to. The interposing transformer automatically takes care of the zero sequence current elimination which is considered by the test module. Just activate the "interposing transformer" option in the Advanced Differential Test Object.

12

Tips & Tricks

10 How to Generate a Double Line-to-Ground Fault For this type of fault, several boundary conditions need to be defined for a proper simulation. This is why two dedicated Test Cases (grid models) are available within the NetSim test module for full modeling flexibility.

11 Test Assessment Fails - Things to Check 11.1 Binary Inputs Operating Mode Check if the connections to the binary inputs (e.g., the start and trip signals) carry voltage or are driven by contacts, only. Make sure that in the Hardware Configuration of the OCC (or of the stand-alone test module) the binary inputs are set accordingly. In the Protection Testing Library templates a Pause module at the beginning of the template reminds the user to adapt this setting prior to the test.

12 How to Check if a Binary Input State has Temporarily Changed ("Glitch Detection") Launch the Binary I/O Monitor in parallel to your test module (e.g. QuickCMC) or Control Center document. It will display all binary inputs and outputs, taking the signal names from the currently active test module. Select the "Indicate state change" option. Any signal change will now be captured and indicated with a double-arrow mark. Reset the marks by clicking Indicate state change twice.

13


13 How to Prevent CMC Switch-Off at High Output Currents due to Overheating In the Hardware Configuration you find a "Compliance Voltage" slider (click the "Details" button on the General tab). If the DUT including the connecting leads show a very low burden (e.g., modern digital relays), the driving voltage for the current paths of the CMC causes high power loss inside the CMC leading to high heat dissipation. This may cause the CMC to switch off due to overheating if generating high currents for a long time. In this case you may move the "Compliance Voltage" slider towards low burden/continuous duty cycle. This reduces the driving voltage and thus the power loss and heating inside the CMC. In case the compliance voltage level becomes too low (i.e., the output currents will be distorted), the Overload indicators in the test module will turn red for affected the current signals, giving you a feedback for acceptable compliance voltage settings. Note: Due to its different amplifier technology, this slider is not required if a CMC 356 test set is connected.

14 How to Duplicate or Rearrange OCC Entries You can move or duplicate test modules in the left navigation area by drag-and-drop. Click the module once to select it (possibly add a consecutive range of adjoining modules by shift-clicking the test module at the other end of the range), then click again and hold to drag the selected test module(s) to the target location. If you do not want to move but duplicate, just hold the key while dragging and dropping (a plus sign will indicate the duplication). Alternatively, you can use the (right-click) context menu options to cut/copy items and paste them to another location. This works for test modules as well as for TO or HWC.

14

Tips & Tricks

15 How to Reuse Custom Parameters in Multiple Test Modules with Differing Test Object Needs Do not include multiple Test Objects in the OCC but include multiple RIO blocks for the test modules in one common Test Object. From each test module select the RIO block (activate) that is to control this module. In this way all custom parameters defined in the TO are available to all modules although they have individual RIO settings (e.g., differing impedance zone setups). Using several Test Objects would result in duplication of the custom parameters - duplication of user settings should be avoided due to awkward setting changes and maintenance issues.

15


16 How to Change the CMGPS Setup for External Use If you would like to prepare CMGPS as synchronized clock pulse source for externally triggered devices, e.g., changing the pulse sequence from the default of 1 pulse per minute, you can open State Sequencer from the Start Page. Open the Hardware Configuration, select the IRIG-B & GPS tab and select "Trigger via CMGPS". Click O K . Now open the Time Trigger Configuration dialog box (from the P A R A M E T E R S pull-down menu click T I M E T R I G G E R C O N F I G U R A T I O N … or the satellite toolbar icon). Modify the GPS settings as needed and click the "Save to Device…" button to write them back to the CMGPS device. It will remember these settings after disconnection and is ready to be used as stand-alone device, generating the pulses as set up, e.g., via the Pulse out 2 connectors.

17 How to Get Access to a Net-1 Test Set Test sets with the Net-1 option communicate with the computer via Ethernet. This communication has to be properly set up, including the traffic through firewalls in their path.

Firewall configuration The Windows firewall included with Win XP Service Pack 2 and higher is automatically configured during the installation of Test Universe if in the Setup dialog box this option was selected accordingly. If this was not done, it is possible to set the automatic configuration at a later stage by selecting the "Allow OMICRON software to configure …" option under F I L E | P R E F E R E N C E S in the Test Set Association and Configuration tool. For any other protection software, the service OMFind.exe must be allowed for out- and inbound UDP traffic on port 4987. In addition, the CMEngAL.exe must be permitted to use a DCOM connection (bi-Directional COMmunication). For more details please see the file Requirements.txt in the root folder of the Test Universe installation DVD or the Support booklet (click Manuals on the Test Universe Start Page).

16

Tips & Tricks

Troubleshooting •

The CMC does not appear within the Test Set Association and Configuration tool. 1. Check if the CMC is turned on. 2. Check the Ethernet connection. 3. Click the "Search" button in the Test Set Association and Configuration tool. 4. Close all security programs such as the firewall and anti virus software that may block the communication. 5. If the CMC still does not appear, and it is connected through a network, connect it directly to the computer. 6. Click the "Search" button once again. 7. Press the black Association button on the rear side of the CMC test set to reset the IP settings. 8. Click the "Search" button once again. 9. Power off the CMC test set. 10.Reset the CMC test set to factory default status by pressing the "!" and the "Association" buttons on the rear side of the CMC test set while powering it on. 11.Keep those two buttons pressed until you hear the relay clicking of the hardware check.

•

The CMC appears in the Test Set Association and Configuration tool but cannot be used 1. Check the "Status" column of the Test Set Association and Configuration tool and perform the measure mentioned there. 2. Check if the IP settings of the CMC test set match the settings of the computer by clicking the "IP Configuration" button. 3. Try to work with a static IP address. 4. Check the status mentioned within a module. 5. Create a communication log file.

17


Communication log file 1. Connect the CMC test set to the mains and the computer, and power it up. 2. Start the Test Universe Start Page; close running test modules. 3. On the Start Page click Support | Calibration & Diagnosis… | Logfile to open the CM Engine Log Viewer. 4. Open the test module and proceed as usual until the error occurs. 5. Save the logfile with F I L E | S A V E or F I L E | S A V E A S . . . 6. Send the file to the OMICRON Technical Support.

18 How to Import Relay Settings The most comfortable way to make the actual relay settings known to Test Universe test modules is to import the settings from a file, e.g., a data file generated by the relay settings program. For selected tools, such as Siemens Digsi or AREVA MiCOM S1, or for generic data import via XML data structure, so-called Import Filters can be used to copy the settings from the settings file to the Test Object of the test module or of the OCC test document. The Customer Area at the OMICRON Web site www.omicron.at provides the most recent selection of import filters for download. It is important to remember that these filters copy relay settings to a predefined parameter structure in the Custom XRIO section of the Test Object. Therefore, you first have to create this relay-specific parameter structure, e.g., by loading the XRIO converter into the Test Object or opening a PTL template that contains this converter. With these parameter definitions in place the Import relay settings... pull-down menu command is enabled, allowing the selection of the import filter to fill the predefined parameters with relay settings. Test modules referencing these Test Object entries (e.g., via LinkToXRIO) automatically adapt to the relay settings.

18

Tips & Tricks

19 How to Test Distance Relays with Constant Source Impedance Simulation In the Advanced Distance teste, select "Constant Source Impedance" as Test Model on the Settings tab to activate kind of a network simulation that properly calculates all phase voltages and currents that result from the fault type and fault impedance data for a specified infeed (source) impedance, with the source being upstream of the assumed VTs and CTs (in backwards direction) and the fault being downstream of the VTs and CTs. This is especially helpful for testing relays that rely on voltages of the non-faulted phases for close-up faults. A common test is to find the zone boundaries in all 4 quadrants. The important thing to notice is that with this arrangement the fault is always in forward direction; so the lower left half of the R-X plane does not mean "fault in backward direction". Due to polarization (offset) effects, using the non-faulted voltages, the resulting relay zones reach a little into (lower-left) quadrant 3 giving better forward direction assessment margin. To test the behavior with inversed feeding direction (with faults to be simulated in backward direction), resulting in changed four-quadrant zone boundaries typically excluding the origin, the best way is to insert a second Advanced Distance module into the OCC test document (rename it to, for example, "Backward Direction") and to reverse the current output polarity for this module, e.g., by changing the "CT starpoint" setting in the RIO Distance block of the associated Test Object. To do so, add a second RIO Distance block to the OCC Test Object (you can copy/paste the first block, thus preserving all other settings), change the CT starpoint setting in this second block, and then open the Test Object from each Advanced Distance module and set the related Distance block as "Active Function" (right-click the block to open the context menu). This way, each test module gets its Distance settings from a different block in the same Test Object. The advantage of inserting a second Distance block into one Test Object as opposed to inserting a second individual Test Object is that all user-specific settings (e.g., relay settings in an XRIO converter section) can easily be changed and maintained since they only exist once: all related RIO Distance parameters in both RIO blocks refer to the same Custom parameter, if you choose to.

19


Hence, the test report will contain the results of two Advanced Distance modules; one showing the 4-quadrant characteristic for forward fault direction, and the other one for backward fault direction. NOTE: For proper automatic assessment, separately define those "polarized" zone characteristics for forward and backward direction (in the related RIO block) that differ from the "standard" (non-polarized) characteristic. If you want to test the standard characteristic, do not use the "Constant Source Impedance" model.

20

Tips & Tricks

20 How to Handle Test Report Settings (Forms) Click the Report command on the Parameters pull-down menu of any test module to specify the details shown in the module’s test report. By default, the Report Settings dialog box provides two predefined test report templates: "Short Form" and "Long Form". In case these two predefined report templates do not match your needs, click the Define… button. In the Define Report Forms dialog box you can now either customize the settings and then store them to redefine the "Short Form" or the "Long Form", or you can click the Add… button to save the changed settings to a new report template with a name of your choice. Up to this point these changes apply to the currently open test module file only. They will be stored along with the file but will not be available to other newly created or opened files.



If you want to keep the redefined form (either with the default name "Short Form" or "Long Form", or with the new name you gave it), click the Set as Default button. From now on you can assign this customized report template form to all module reports. Important to understand in this context: If you assign a report template from the Report Form list, only the position of this template within the Report Form list is stored to the test report file, not the actual contents (as opposed to the definition described above). The effect is: •

If you open this test report file on another computer (let’s call it computer "B") that has a different definition at this particular list position than the source computer (computer "A") - for example a "Short Form" that has previously been redefined and stored with different in comparison to computer "A" -, you will get a test report created according to the settings of the form definition of computer "B", i.e., most likely different from the source system on computer "A".

•

If you open this test report file on a computer "B" that does not provide this position in the Report Form list (example: the test module file was assigned a user-added report template form Form3 on the 3rd position in the Report Form list of source computer "A", but the Report Form list of computer "B" only contains the first 2 default forms), you will get a test report created according to the first form definition in the of Report Form list of computer "B" (e.g., "Short Form") - again different in comparison to computer "A".

21


There are two ways to ensure that the representation of the test report on a different computer "B" is identical to the one on the source computer "A": 1. If you need it for one or a few specific test reports only: Click the Report command on the Parameters pull-down to open the Report Settings dialog box. Click the Define… button. Toggle any of the white check boxes of your choice back and forth. This is interpreted as a "modified" selection, and even though no real change was performed that way, it is now treated as a local variant. If you now save the test module file, it will carry the test report definition along with it. 2. If you want to use the same default report template definitions on the source and on the target computer without having to touch the test module file, you need to copy the template definition file(s) from the source computer "A" to the target computer "B". There is a template definition file for each test module, e.g., a file named OMADist.TPVRep for Advanced Distance. The files are located at the Documents and Settings folder, e.g., C:\Documents and Settings\username\Application Data\Omicron\Test Universe\Report Settings\OMADist.TPVRep Search for *.TPVRep to get a list of all template definition files. Note that these files only exist for those modules whose default report form definitions were changed (or extended) by the user. Copy these files to the respective path on the target computer(s), and all test reports relating to these forms will have the same look on all target systems without making the settings local as in solution 1. And, eventually, if you want to make a default report template form from a local setting received with a test module file: Click the Report command on the Parameters pull-down to open the Report Settings dialog box. Click the Define… button. Click the Add… button, change the template’s name if you want to, and then click the Set as Default button. This way is identical to the way to create or modify a form on your own.

22

Tips & Tricks

21 Glossary DUT HWC OCC OHM

Device under test (e.g. relay)

PTL

Protection Testing Library

TO

Test Object

Hardware Configuration OMICRON Control Center document "OMICRON’s Ohm’s law": the suggested setup sequence for Test Object - Hardware Configuration - Test Module

23


24

Tips & Tricks

Recommend Documents