C HYPERSIM Acceptance Test Plan

Transcription

1 C HYPERSIM Acceptance Test Plan Version: 3.2

2

3 Test Result Approval The undersigned acknowledge they have reviewed the steps in this Acceptance Test and agrees with the approach it presents. Changes to this Acceptance Test will be coordinated with and approved by the undersigned or their designated representatives. Signature: Date: / /

4

5 C HYPERSIM Acceptance Test Plan Page i CONTENTS 1. INTRODUCTION OBJECTIVES INSTRUCTIONS TEST STEPS FORMALISM PREREQUISITES SYSTEM CONFIGURATION SOFTWARE VERSIONS SYSTEM TESTS C SLAVE TEST WITH EXTERNAL TOOL PMUCONNECT FILE GENERATION C MASTER/SLAVE LOOPBACK TEST BETWEEN TWO SIMULATORS C MASTER/SLAVE LOOPBACK ON THE SAME SIMULATOR...18

6 C HYPERSIM Acceptance Test Plan Page 1/19 1. INTRODUCTION 1.1. OBJECTIVES This document aims at defining the acceptance tests that are to be executed to ensure the correct functionality of the C driver on HYPERSIM under Linux and Windows. It includes both the master and the slave parts of the protocol. The features that shall be tested are: C master application C slave application PMUConnect application 1.2. INSTRUCTIONS For most test cases, multiple files are provided. Before executing each case, be sure to copy the files in the right directories. File name hyservmain.cfg C37118_MASTER_SLAVE.io C37118_SLAVE.io C37118_MASTER.io C37118_MASTER_STANDALONE_CFG.opal C37118_MASTER_LOOPBACK_CFG.opal C37118_SLAVE_STANDALONE_CFG.opal C37118_SLAVE_LOOPBACK_CFG.opal *.sch, *.sig, *.xml 6.0.x Windows *.ecf, *.sig, *.xml Directory /export/local/ssr/hyconfig/ /export/local/ssr/hyconfig/ /export/local/ssr/hyconfig/ /home/hypusr01/hyworkspace/c37118/ C:\Users\UserName\HyperWorks\design\C37118 Note: The UserName is found by typing the following command in cmd.exe : echo %username%

7 C HYPERSIM Acceptance Test Plan Page 2/ TEST STEPS FORMALISM For each test, a header provides the test ID, as well as an extended description and the preliminary setup needed to accomplish the test. Each test step is identified with a number. A set of instructions is defined, along with the expected results, where applicable. Depending on what is observed, the status must be set. A check in the check box of the status column indicates test is complete. Some comments can be added at the end of each test to provide some extra information. ID Description Setup TEST STEPS # Instructions Expected results Status Comments

8 C HYPERSIM Acceptance Test Plan Page 3/19 2. PREREQUISITES The Acceptance Test Plan lists all the tests that must be executed to validate the good functionality of the system. It is important to: Read the System Description Document provided in the delivery binder. Be familiar with HYPERSIM and other software products needed for the tests. Understand the delivered hardware SYSTEM CONFIGURATION System #1 (S01) Gr. 1 Gr. 2 Gr. 3 Gr. 4 System #2 (S02) Gr. 1 Gr. 2 Gr. 3 Gr. 4 Section A Section B Section A Section B 4 x DCDC +/-18V 833mA 2 x DCDC +/-12V 625mA 4 x DCDC +/-18V 833mA 2 x DCDC +/-12V 625mA MOTHERBOARD 1 PCI-E 2.0 x8 (in x16) 2 PCI-E 2.0 x4 (in x8) 3 PCI-E 2.0 x8 4 PCI-E 1.0 x4 (in x8) PCI 33MHz (32 bits) 5 PCI 33MHz (32 bits) 6 CPU CPU CPU X.XX GHz X GB X GB 5 6 Vout: 5V, 12V 600W Power Supply 115V to 230V Simulator Ethernet MOTHERBOARD 1 PCI-E 2.0 x8 (in x16) 2 PCI-E 2.0 x4 (in x8) 3 PCI-E 2.0 x8 4 PCI-E 1.0 x4 (in x8) PCI 33MHz (32 bits) 5 PCI 33MHz (32 bits) 6 CPU CPU CPU X.XX GHz X GB X GB 5 6 Vout: 5V, 12V 600W Power Supply 115V to 230V Simulator Ethernet Ethernet Switch Figure 1: System configuration needed to run all tests NOTE: The configuration shown is needed to perform test C37118_MS_Loop_2sim. If only one simulator is available, this test can be skipped. Here is a list of what is required to execute this test plan: HYPERSIM 5.6.x or higher: Host computer with MobaXterm installed A Netgear switch Linux target with HYPERSIM installed

9 C HYPERSIM Acceptance Test Plan Page 4/19 HYPERSIM 6.0.x Windows version: Host computer with MobaXterm installed A Netgear switch Linux target with HYPERSIM 6.0.x installed Windows Host with HYPERSIM 6.0.x installed 2.2. SOFTWARE VERSIONS The tests performed during the acceptance test have been done / are to be done with the following software versions: RTOS = Redhat opalrt-6.1 Linux version: HYPERSIM R5.8.2 Windows version: HYPERSIM R6.0.0.o270 PMU Connection Tester = 4.4.0

10 C HYPERSIM Acceptance Test Plan Page 5/19 3. SYSTEM TESTS 3.1. C SLAVE TEST WITH EXTERNAL TOOL ID C37118_Ext_Tool Description Verify that the C Slave protocol is functional with an external tool. Setup See the System Configuration section. Use simulator S01 only. Files Slave files in directory /C37_118/Model/Slave. TEST STEPS # Instructions Expected results Status 1 2 Linux version: Copy files from the /hyconfig/slave/ folder in the right directory (see Instructions section of this document) and restart the real-time server as a root user. Windows version: Copy files from the /hyconfig/slave/ folder in the right directory (see Instructions section of this document). service hy.server start Edit the C37118Slave_standalone_CFG.opal file and set the pmu_nic_name to the right Ethernet interface. Linux version: The configuration files are copied on the simulator and the real-time server has been restarted. Windows version: The configuration files are copied on the simulator. The Ethernet interface are set for the slave simulation. Failure in using correct values for this parameter prevents simulation from starting. 3 Linux version: Copy files from the /Model/Slave folder to the /home/hypusr01/hyworkspace/ C37118/ directory. Windows version: Copy files from the /Model/Slave folder to the C:\Users\UserName\HyperWorks \design\c37118_slave directory. Start HYPERSIM 6.0.x and edit the parameters of the real-time simulation. See example in the Figure 4 and Figure 5 Linux version: The model and associated files are copied on the simulator. Windows version: The model and associated files are copied on the Host and HYPERSIM is configured.

11 C HYPERSIM Acceptance Test Plan Page 6/ Linux version: Open the model C37118_SLAVE_MODEL.sch. Go to the Simulation mode and load sensor file C37118_SLAVE_SENSORS.sig. Start simulation. Windows version: Open the model C37118_SLAVE_MODEL.ecf. Go to HYPERSIM/Sensors tab and load sensor file C37118_SLAVE_SENSORS.sig. Start the simulation. Linux version: Launch HyperView and then Scopeview. Open template C37118_SLAVE_TEMPLATE.xml. Windows version: Launch Scopeview. Open template C37118_SLAVE_TEMPLATE.xml. In Windows, start the PMU Connection Tester application. In the Settings tab, under Application Settings, put the ForceIPv4 parameter to True and set PhaseAngleGraphStyle to Raw. In the Tcp tab, Put the simulator IPaddress and port number In the Protocol tab, set Device ID Code to 1, select in the drop-down list IEEE C , then click Connect. In PMU Connection Tester, click on Disconnect. Change the Port value for 7201 and the Device ID Code for 2 and reconnect. In PMU Connection Tester, click on Disconnect. The slave model runs on the simulator. ScopeView is launched and the template opened. Application started. ForceIPv4 is True. Connection is successful. Data is received. See Figure 2 to compare received data. Connection is lost. Connection is successful. Data is received. See Figure 2 to compare received data. Connection is lost. 12 Stop the slave model. Simulation has stopped. Comments For the pmu_nic_name, if it is unknown, use the command ifconfig as a root the get a list of available interfaces. It is typically between eth0 and eth5.

12 C HYPERSIM Acceptance Test Plan Page 7/19 Figure 2: Results obtained with the PMU Connection Tester

13 C HYPERSIM Acceptance Test Plan Page 8/ PMUCONNECT FILE GENERATION ID Description Setup Model PMUConnect Verify that the PMUConnect application is functional to generate the IO configuration files. See the System Configuration section. Use simulator S01 only. Slave files in directory /C37_118/Model/Slave TEST STEPS # Instructions Expected results Status 1 2 Copy the PMUConnect binary file to /export/local/ssr/hyconfig/ using the following command: The PMUConnect binary file is copied in the configuration directory. cp /export/local/ssr/hypersim/linux-rhel5-32-opalrt/hyserver/bin/pmuconnect /export/local/ssr/hyconfig/ Modify the LD_LIBRARY_PATH environment variable to add the /hyconfig/ directory. As root, use command: The LD_LIBRARY_PATH variable is modified. You can verify by typing env grep LD_LIBRARY_PATH export LD_LIBRARY_PATH=/export/local/ssr/hypersim/linux-rhel5-32- opalrt/hyserver/rt/lib/:/export/local/ssr/hypersim/linux-rhel5-32- opalrt/hyserver/rt/lib/drivers:${ld_library_path} Failure to do this step will result in the following error message while trying to run the PMUConnect: PMUConnect: error while loading shared libraries Launch the C slave model. Follow steps 1 to 4 of test C37118_Ext_Tool as a guideline. In a terminal window, make the working directory to be /hyconfig/ using command: cd /export/local/ssr/hyconfig/ Launch the PMUConnect application using the IP address of the simulator as argument: The C slave model runs on the simulator. The working directory is /hyconfig/. The PMUConnect application runs. See comments at the end of this test for an overview of the expected output../pmuconnect -ip x.x -name OpalRT-PMU1 -sensor_offset port 7200 It is possible that the application does not return to a functional command prompt after running. If the last line printed is Closing PMU connection, the user can stop the program using Ctrl+C.

14 C HYPERSIM Acceptance Test Plan Page 9/ Verify that immediately after the line: Initializing C Master, you have the line: Starting listening thread.. If instead you see the line: C37.118Master: Connection to PMU x.x failed; Use the previous configuration file, a connection problem has occurred. List the files located in the directory according to their creation/modification date using command: ls -ltr The connection could be established without any problem. The 4 files listed should have the same date and time and this date/time should match the date/time when you ran the PMUConnect application. The 4 files are: -PMU-OpalRT-PMU1.txt -PMU- OpalRT-PMU1.cfg2 If you rerun the command with the exact same arguments: -connections-pmu-opalrt-pmu1.io -C37118_master_cfg_01.opal -The C37118_master_cfg_01.opal file will be incremented instead of being overwritten. A new version will be created (C37118_master_cfg_02.opal, _03.opal, _04.opal, etc). 8 Stop the slave model. The model has stopped. Comments Step #4: If running the PMUConnect application on the same simulator as the slave model, the PMU IP-address must be set to (the localhost IP). Also modify the command in step #6 accordingly. Step #5: The expected output when running the PMUConnect application is: RTServer[hypusr01]86%./PMUConnect -ip name TEST1 - sensor_offset port 7200 Name TEST1 connectionslabel TEST1 Begin initialization Begin to register on OpalRoot

15 C HYPERSIM Acceptance Test Plan Page 10/19 Registered on OpalRoot Loading services from "/export/local/ssr/hyconfig/services" Service LogRT/LogRT not found Root initialized: :25251/resources/root Initialization done SyncExchangerManager : Exchanger C37118Master created Initializing C Master... Starting listening thread. Received CFG2 frame, processing Exporting CFG2 frame for PMU :7200 PMU timebase: (-> resolution: us) PMU number: 1 PMU 1: OpalRT-PMU1 Data format - FREQ/ROCOF format: floating point - analogs format: floating point - phasors format: 16-bit integer - phasors notation: polar phasor (2): V-PHASOR I-PHASOR analog (2): ANALOG-1 ANALOG-2 digital (2x16): DIG-1 00 DIG-1 01 DIG-1 02 DIG-1 03 DIG-1 04 DIG-1 05 DIG-1 06 DIG-1 07 DIG-1 08 DIG-1 09 DIG-1 10 DIG-1 11 DIG-1 12 DIG-1 13 DIG-1 14 DIG-1 15 DIG-2 00 DIG-2 01 DIG-2 02 DIG-2 03 DIG-2 04 DIG-2 05 DIG-2 06 DIG-2 07 DIG-2 08 DIG-2 09 DIG-2 10 DIG-2 11 DIG-2 12 DIG-2 13 DIG-2 14 DIG-2 15 Phasor conversion factors (2) * 10^-5 Volt * 10^-5 Ampere Analog conversion factors (2) - factor: 0, single point-on-wave - factor: 0, RMS Value Digital conversion factors (2)

16 C HYPERSIM Acceptance Test Plan Page 11/19 - normal state: 0x0, valid bits: 0x0 - normal state: 0x0, valid bits: 0x0 Nominal frequency: 50Hz Config change count: 0 Refresh rate: 20 frame/second - 0. ANALOG-1 at 0x80c8f30 (F32) - 1. ANALOG-1.factor at 0x80c9e7c (U32) - 2. ANALOG-2 at 0x80c8f34 (F32) - 3. ANALOG-2.factor at 0x80c9e84 (U32) - 4. ClockLocked at 0x80c8ea8 (Boolean) - 5. DIG-1 00 at 0xbfe1acf8 (PositionedBit<0>) - 6. DIG-1 01 at 0xbfe1acf8 (PositionedBit<1>) - 7. DIG-1 02 at 0xbfe1acf8 (PositionedBit<2>) - 8. DIG-1 03 at 0xbfe1acf8 (PositionedBit<3>) - 9. DIG-1 04 at 0xbfe1acf8 (PositionedBit<4>) DIG-1 05 at 0xbfe1acf8 (PositionedBit<5>) DIG-1 06 at 0xbfe1acf8 (PositionedBit<6>) DIG-1 07 at 0xbfe1acf8 (PositionedBit<7>) DIG-1 08 at 0xbfe1acf9 (PositionedBit<0>) DIG-1 09 at 0xbfe1acf9 (PositionedBit<1>) DIG-1 10 at 0xbfe1acf9 (PositionedBit<2>) DIG-1 11 at 0xbfe1acf9 (PositionedBit<3>) DIG-1 12 at 0xbfe1acf9 (PositionedBit<4>) DIG-1 13 at 0xbfe1acf9 (PositionedBit<5>) DIG-1 14 at 0xbfe1acf9 (PositionedBit<6>) DIG-1 15 at 0xbfe1acf9 (PositionedBit<7>) DIG-2 00 at 0xbfe1acf8 (PositionedBit<0>) DIG-2 01 at 0xbfe1acf8 (PositionedBit<1>) DIG-2 02 at 0xbfe1acf8 (PositionedBit<2>) DIG-2 03 at 0xbfe1acf8 (PositionedBit<3>) DIG-2 04 at 0xbfe1acf8 (PositionedBit<4>)

17 C HYPERSIM Acceptance Test Plan Page 12/ DIG-2 05 at 0xbfe1acf8 (PositionedBit<5>) DIG-2 06 at 0xbfe1acf8 (PositionedBit<6>) DIG-2 07 at 0xbfe1acf8 (PositionedBit<7>) DIG-2 08 at 0xbfe1acf9 (PositionedBit<0>) DIG-2 09 at 0xbfe1acf9 (PositionedBit<1>) DIG-2 10 at 0xbfe1acf9 (PositionedBit<2>) DIG-2 11 at 0xbfe1acf9 (PositionedBit<3>) DIG-2 12 at 0xbfe1acf9 (PositionedBit<4>) DIG-2 13 at 0xbfe1acf9 (PositionedBit<5>) DIG-2 14 at 0xbfe1acf9 (PositionedBit<6>) DIG-2 15 at 0xbfe1acf9 (PositionedBit<7>) Error at 0x80c8e2c (I32) FracSec at 0x80c8eb0 (U32) Freq at 0x80c9688 (F32) I-PHASOR.angle at 0x80c87ec (F32) I-PHASOR.factor at 0x80c8ffc (U32) I-PHASOR.magnitude at 0x80c87e8 (F32) ROCOF at 0x80c968c (F32) SOC at 0x80c8eac (U32) Stat.configChange at 0x80c9677 (Boolean) Stat.dataError at 0x80c9670 (I32) Stat.dataModified at 0x80c9678 (Boolean) Stat.dataSorting at 0x80c9675 (Boolean) Stat.inSync at 0x80c9674 (Boolean) Stat.timeQuality at 0x80c967c (I32) Stat.triggerReason at 0x80c9684 (I32) Stat.unlockedTime at 0x80c9680 (I32) Status at 0x80c8e28 (I32) Timebase at 0x80c8e78 (U32) V-PHASOR.angle at 0x80c87e4 (F32) V-PHASOR.factor at 0x80c8ff4 (U32) V-PHASOR.magnitude at 0x80c87e0 (F32) Saving Mapping points in /export/local/ssr/hyconfig/pmu-test1.txt

18 C HYPERSIM Acceptance Test Plan Page 13/19 Done Creating connections file for C Master test Adding SyncExchanger for the C37118 Master Offset The following driver configuration file (/export/local/ssr/hyconfig/c37118_master_cfg_01.opal) is used to generate (./connections-pmu-test1.opal) Closing PMU connection Exiting listening thread.

19 C HYPERSIM Acceptance Test Plan Page 14/ C MASTER/SLAVE LOOPBACK TEST BETWEEN TWO SIMULATORS ID Description C37118_MS_Loop_2sim Verify that the C protocol is functional in loopback between two distinct simulators (S01 and S02). Setup See the System Configuration section. Use simulators S01 and S02. Files TEST STEPS Use files in directory C37_118/Model/Slave and C37_118/Model/Master # Instructions Expected results Status 1 Linux version: On S02, copy files from the Slave folder in the right directories (see Instructions section of this document) and restart the realtime server as a root user. Windows version: On S02, copy files from the Slave folder in the right directories (see Instructions section of this document). service hy.server start Slave files are copied on S Launch the C slave model. Follow steps 2 to 5 of test C37118_Ext_Tool as a guideline. Linux version: On S01, copy files from the Master folder in the right directories (see Instructions section of this document) and restart the realtime server as a root user. Windows version: On S01, copy files from the Master folder in the right directories (see Instructions section of this document). service hy.server start On S01, edit the C37118Master_standalone_CFG.opal file and set the ip to the IP-address of the simulated PMU (Put the IPaddress of the Slave). The C slave model runs on simulator S02 and the template has been loaded in ScopeView. Master files are copied on S01. The IP-address is set for the master simulation. The IP-addresses set in step 2 and 4 should therefore be the same.

20 C HYPERSIM Acceptance Test Plan Page 15/ Linux version: Open the model C37118_MASTER_MODEL.sch. Go to the Simulation mode and load sensor file C37118_MASTER_SENSORS.sig. Start simulation. Windows version: Open the model C37118_MASTER_MODEL.ecf. Go to HYPERSIM/Sensors tab and load sensor file C37118_MASTER_SENSORS.sig. Start the simulation. Linux version: Launch HyperView and then Scopeview. Open template C37118_MASTER_TEMPLATE.xml. Windows version: Launch Scopeview. Open template C37118_MASTER_TEMPLATE.xml. The master model runs on S01. ScopeView is launched and the template opened. Expected results can be viewed on Figure 3. 7 Run an acquisition in both ScopeView instances. Analog_1: ± 1 sine wave, 1.5 Hz, discrete = 50 ms Analog_2: ± 2 sine wave, 1.5 Hz, discrete = 50 ms Digital_1: 1 Hz, 25% duty cycle Digital_2: 1 Hz, 75% duty cycle Freq_Dev: 50 ± 0.2 sine wave, 1 Hz, discrete = 50 ms Freq_ROC: ± 100 sine wave, 0.5 Hz, discrete = 50 ms VoltagePhasorAngle: ± pi sine wave, 1.5 Hz, discrete=50ms VoltagePhasorMagnitude: 4*** CurrentPhasorAngle: ± pi sine wave, 1.5 Hz, discrete=50ms CurrentPhasorMagnitude: 3*** *** The CurrentPhasor and the VoltagePhasor magnitudes values of 3 and 4 are expected on the master side. On the slave side, the values should be 3 and 4 respectively. The factor between the

21 C HYPERSIM Acceptance Test Plan Page 16/19 two is given by the parameter unit of the item in the pmu_phasors section of C37_118_slave_cfg_01.opal, where the equation is: Master reading = Slave value unit 10 5 In this acceptance test, the unit value is set to 100, Stop both the master and the slave models Comments Both models are stopped The results must be displayed both in the slave and in the master ScopeView acquisitions. If the results are shown only in the slave acquisition, it means the data are not properly exchanged from the slave to the master. Note also that the 50 ms discretization observed on the master side is normal and is due to the pmu_data_rate slave parameter set to 20 (cycles per seconds).

22 C HYPERSIM Acceptance Test Plan Page 17/19 Figure 3: C master model acquisition results

23 C HYPERSIM Acceptance Test Plan Page 18/ C MASTER/SLAVE LOOPBACK ON THE SAME SIMULATOR ID Description Setup Files C37118_MS_Loop_1sim Verify that the C protocol is functional in loopback on a single simulator. See the System Configuration section. Use simulator S01 only. Slave and Master files in directory /C37_118/Model/Master-Slave. TEST STEPS # Instructions Expected results Status Copy configuration files from the /hyconfig/master-slave folder in the right directory as well as the models (see Instructions section of this document). Only for Linux version: restart the real-time server as a root user. service hy.server start Linux version: Copy model from the Master- Slave folder to the /home/hypusr01/hyworkspace/ C37118_MasterSlave/ directory. Windows version: Copy files from the Master-Slave folder to the C:\Users\UserName\HyperWorks \design\c37118_masterslave directory. Start HYPERSIM 6.0.x and edit the parameters of the real-time simulation. See example in the Figure 4 and Figure 5 Linux version: Open HYPERSIM and open the model C37118_MASTER_SLAVE_MODEL.sch. Go to the Simulation mode and load sensor file C37118_MASTER_SLAVE_SENSORS.sig. Start simulation. Windows version: Open the model C37118_MASTER_SLAVE_MODEL.ecf. Go to HYPERSIM/Sensors tab and load sensor file C37118_MASTER_SLAVE_SENSORS.sig. Start the simulation. Configuration files are copied on the simulator. Model is copied in the right directory in the simulator. And HYPERSIM is configured for Windows version. The Master/Slave model runs.

24 C HYPERSIM Acceptance Test Plan Page 19/19 4 Launch HyperView and then Scopeview. Open template C37118_MASTER_SLAVE_TEMPLATE.xml. Windows version: Launch Scopeview. Open template C37118_MASTER_SLAVE_TEMPLATE.xml. 8 Run acquisition in ScopeView. ScopeView is launched and the template opened. Expected results are the same as in test C37118_MS_Loop_2sim in Figure 3. 9 Stop both master and slave models. Both models are stopped. Comments Note also that the 50 ms discretization observed on the master side is normal and is due to the pmu_data_rate slave parameter set to 20 (cycles per seconds).

25 C HYPERSIM Acceptance Test Plan Page 1/1 Figure 4: Target Configuration Figure 5: HYPERSIM Simulation Configuration

26

27 CONTACT Note: OPAL-RT Corporate Headquarters 1751 Richardson, Suite 2525 Montréal, Québec, Canada H3K 1G6 Tel.: Toll free: While every effort has been made to ensure accuracy in this publication, no responsibility can be accepted for errors or omissions. Data may change, as well as legislation, and you are strongly advised to obtain copies of the most recently issued regulations, standards, and guidelines. This publication is not intended to form the basis of a contract. Technical Services 01/05/2017 OPAL-RT TECHNOLOGIES Inc.