MxDSRC

For detailed information on 802.11 tests, refer to the 80211_TSS_TP_Test_Specification. The section numbers below refer to this specification.

1.Power on the hardware and wait 30 minutes for the temperature to stabilize.

2.Calibrate the NI System.  

3.Determine the cable path losses.

4.Select the Test Configuration (hardware) for the test you are running, for example: TC4. See the tables in section 6.2. The configuration diagrams are also provided below.

5.In MxVDev, open the DSRCPhysicalLayerTestAutomation.mxp project.

6.Open MxTransIt.

7.Ensure the UDP Configuration properties on the two UDP (Generic Transform) Transforms are set correctly. For details, see: Setting the IP Addresses and Ports.

Click to expand.

8.Copy the Resource Names from the NI Measurement & Automation Explorer (NI Max) to the property on the corresponding Transforms listed here:

NI MAX. Click to expand.

9.Ensure that the Configuration Files Folder Path property for the DSRC Physical Layer Test Manager Transform is set to the Configuration Files subfolder of the project folder as shown below. This is the location of the TDMS configuration files.
 

Click to expand.

10.In the Properties box of the SUT Interface Transform, enter the TCI version as shown here:

11.In MxVDev, open the Project Settings and select the tags for Channel and DataRate that you wish to test.

oRxPowerStepSize is the step size as described in TP-80211-RXT-PHY-BV-05 of the document WAVE802.11-TSS&TP. Enable this tag when you need to use the values of step size defined in the Constants & Calibrations menu. When unchecked, a default step size of 2 will be used.

oMaxRxPower is the maximum power level described in TP-80211-RXT-PHY-BV-05 in the document WAVE802.11-TSS&TP. Along with MinRxPower, it defines the range of power levels over which TP-80211-RXT-PHY-BV-05 is tested. Use only when Debugging. The default value is -30 dBm.

oMinRxPower is the minimum power level described in TP-80211-RXT-PHY-BV-05 in the document WAVE802.11-TSS&TP. Along with MaxRxPower, it defines the range of power levels over which TP-80211-RXT-PHY-BV-05 is tested. Use only when Debugging. The default value is determined based on the Receive Sensitivity Table defined in WAVE802.11-TSS&TP.

12.Parameters provided with the IUT by the test requestor, for example MaxTransmitPower, can be entered in the Constants and Calibrations window. To access, select View->Constants from the MxVDev main menu.

13.In the MxVDev Project Explorer, select the Scenario for the test you wish to run. The Scenario names correspond to the Test Purpose Ids in section 6.2. Double-click on the Scenario name to open it.

14.When the hardware is warmed up, click the run button () to run the test.

For Regression Testing, use the following Regression scripts provided with the project:

•For TP-80211-RXT-PHY-BV-01, use RXT BV 01.mxreg

•For TP-80211-RXT-PHY-BV-02 and 03, use RXT BV 02 to 03.mxreg.

•For TP-80211-RXT-PHY-BV-04, use RXT BV 04.mxreg

•For TP-80211-RXT-PHY-BV-04, use RXT BV 05.mxreg

•For TP-80211-TXT-PHY-BV-01 to TP-80211-TXT-PHY-BV-06, use TXT BV 01 to 06.mxreg.

•For TP-80211-TXT-PHY-BV-07, use TXT BV 07.mxreg.

•For TP-80211-TXT-MAC-BV-01 and TP-80211-RXT-MAC-BV-01, use MAC.mxreg

802.11 Test Configurations

Click to expand. Test Configuration 1 (TC1) SA = Signal Analyzer Click to expand. TXT Test Setup Test Configuration 2 (TC2) Test Configuration 3 (TC3) Click to expand. Test Configurations 2 and 3 have been implemented in the MxDSRC as shown below. RXT Test Setup 1 For the following Data rates, the test setup is as shown above. •20MHz Channel: 6Mbps, 9Mbps, 12Mbps •10MHz Channel: 3Mbps, 4.5Mbps, 6Mbps, 9Mbps RXT Test Setup 2 For the following Data rates, the test setup is as shown above. •20MHz Channel: 18Mbps, 24Mbps, 36Mbps, 48Mbps, 54Mbps •10MHz Channel: 12Mbps, 18Mbps, 24Mbps, 27Mbps Test Configuration 4 (TC4) The VST is not required for TC4. If used, the configuration is the same as TC3.

For detailed information on 1609.2 tests, refer to the CVNGSE_WAVENS_TSS_TP_Test_Specification. The section numbers below refer to this specification.

1.Ensure the system is configured with the proper Security Credentials. See Configuring Security Credentials.

2.Select the Test Configuration (hardware) for the test you are running, for example: TC1. See the tables in section 6.2. The configuration diagrams are also provided below.

3.Power on the hardware.

4.Wait 5 minutes for the GPS signal (real or simulated).

Note: The date and time of a simulated GPS must fall within the valid dates of the Security Certificate.

5.In MxVDev, open the DSRC_1609Dot2and3.mxp project.

6.Open MxTransIt.

7.Ensure the UDP Configuration properties on the two UDP (Generic Transform) Transforms are set correctly. For details, see: Setting the IP Addresses and Ports.

Click to expand.

8.In the Properties box of the SUT Interface Transform, enter the TCI version as shown here:

9.In MxSuite, open the Project Settings and select the tags for Channel, DataRate, and TransmitPower that you wish to test:

10.In the MxVDev Project Explorer, select the Scenario for the test you wish to run. The Scenario names correspond to the Test Purpose Ids in section 6.2. Double-click on the Scenario name to open it.

11.Click the run button () to run the test.

To run a Regression Test, use the Regression script, RegressionPHYRX.mxreg.

1609.2 Test Configuration 1 (TC1)

For detailed information on 1609.3 tests, refer to the CVNGSE_WAVENS_TSS_TP_Test_Specification. The section numbers below refer to this specification.

1.Ensure the system is configured with the proper Security Credentials. See Configuring Security Credentials.

2.Select the Test Configuration (hardware) for the test you are running, for example: TC2. See the tables in section 6.2. The configuration diagrams are also provided below.

3.Power on the hardware.

4.Wait 5 minutes for the GPS signal (real or simulated).

Note: The date and time of a simulated GPS must fall within the valid dates of the Security Certificate.

5.In MxVDev, open the DSRC_1609Dot2and3.mxp project.

6.Open MxTransIt.

7.Ensure the UDP Configuration properties on the two UDP (Generic Transform) Transforms are set correctly. For details, see: Setting the IP Addresses and Ports.

Click to expand.

8.In the Properties box of the SUT Interface Transform, enter the TCI version as shown here:

9.In MxSuite, open the Project Settings and select the tags for Channel, DataRate, and TransmitPower that you wish to test:

10.In the MxVDev Project Explorer, select the Scenario for the test you wish to run. The Scenario names correspond to the Test Purpose Ids in section 6.2. Double-click on the Scenario name to open it.

11.Click the run button () to run the test.

To run a Regression Test, use the Regression script, RegressionPHYRX.mxreg.

1609.3 Test Configuration 1 (TC1)

1609.3 Test Configuration 2 (TC2)

For detailed information on 1609.4 tests, refer to the CVNGSE_WAVENS_TSS_TP_Test_Specification. The section numbers below refer to this specification.

1.Ensure the system is configured with the proper Security Credentials. See Configuring Security Credentials.

2.Select the Test Configuration (hardware) for the test you are running, for example: TC1. See the tables in section 6.2. The configuration diagrams are also provided below.

3.Power on the hardware.

4.Wait 5 minutes for the GPS signal (real or simulated).

Note: The date and time of a simulated GPS must fall within the valid dates of the Security Certificate.

5.In MxVDev, open the DSRC_1609Dot4.mxp project.Power on the hardware and wait 30 minutes for the temperature to stabilize.

6.Open MxTransIt.

7.Ensure the UDP Configuration properties on the two UDP (Generic Transform) Transforms are set correctly. For details, see: Setting the IP Addresses and Ports.

Click to expand.

8.In the Properties box of the SUT Interface Transform, enter the TCI version as shown here:

9.In MxSuite, open the Project Settings and select the tags for Channel, DataRate, and TransmitPower that you wish to test:

10.In the MxVDev Project Explorer, select the Scenario for the test you wish to run. The Scenario names correspond to the Test Purpose Ids in section 6.2. Double-click on the Scenario name to open it.

11.Click the run button () to run the test.

To run a Regression Test, use the Regression script, RegressionPHYRX.mxreg.

1609.4 Test Configuration 1 (TC1)

For detailed information on SAE J2945/1 tests, refer to the J2945_1_TSS_TP_Test_Specification. The section numbers below refer to this specification.

1.Power on the hardware and wait 30 minutes for the temperature to stabilize.

2.Calibrate the NI System.  

3.Determine the cable path losses.

4.Select the Test Configuration (hardware) for the test you are running, for example: TC1. See the tables in section 6.2. The configuration diagrams are also provided below.

5.In MxVDev, open the DSRCPhysicalLayerTestAutomation.mxp project.

6.Open MxTransIt.

7.Ensure the UDP Configuration properties on the two UDP (Generic Transform) Transforms are set correctly. For details, see: Setting the IP Addresses and Ports.

Click to expand.

8.In the Properties box of the SUT Interface Transform, enter the TCI version as shown here:

9.Copy the Resource Names from the NI Measurement & Automation Explorer (NI Max) to the property on the corresponding Transforms listed here:

NI MAX. Click to expand.

9.In MxSuite, open the Project Settings and select the tags for Channel, DataRate, and TransmitPower that you wish to test:

10.In the MxVDev Project Explorer, select the Scenario for the test you wish to run. The Scenario names correspond to the Test Purpose Ids in section 6.2. Double-click on the Scenario name to open it.

11.When the hardware is warmed up, click the run button () to run the test.

To run a Regression Test, use the Regression script, RegressionPHYRX.mxreg.

J2945/1 Test Configuration 1 (TC1)

J2945/1 Test Configuration 2 (TC2)

J2945/1 Test Configuration 3 (TC3)

J2945/1 Test Configuration 4 (TC4)

•DSRC modem

•Programmable RF Attenuator

•Fixed RF Attenuator

•Screened box

•GPS or GPS simulator

•PC

•Vector Signal Transceiver - Not required for protocol testing

•MxSuite

•NI Wireless LAN Measurement Suite

•Test Control Interface (TCI) is required for your SUT or IUT - See: https://github.com/certificationoperatingcouncil

1.Copy the OnBoardSecurity state and config directories to the c:\ProgramData\SecurityInnovation\Aerolink  directory (if this directory does not exist, create it), so you have the following directory structure inside c:\ProgramData:
 

2.Click on the Windows start button, right-click on Computer, and select Properties.

3.Click on Advanced system settings.

4.Click on the Environment Variables button.

5.Under User Variables click the New button.

6.In the variable name add  : AEROLINK_CONFIG_DIR   and in the variable value add C:\ProgramData\SecurityInnovation\Aerolink\config.
 

7.Click OK.

8.Click on New again.

9.In the variable name add: AEROLINK_STATE_DIR  and in the variable value add C:\ProgramData\SecurityInnovation\Aerolink\state
 

10.Click OK.

11.Copy aerolink.dll to the c:\windows directory.

12.Reboot.

The procedures detailed in this document are in addition to factory calibration. All specifications and procedures assume that the components of the system are calibrated in accordance to National Instruments recommendations.

Before any path loss calculations can be performed the VST must be calibrated.

Calibrating the NI PXIe-5644R

Temperature drift and other environmental changes can lead to performance degradation for several NI 5644R specifications. Self-calibration adjusts the NI 5644R for variations in the module environment using an onboard high-precision calibration tone. Perform self-calibration to compensate and optimize the performance of the NI 5644R for a given ambient temperature and operating environment.

To ensure the system meets the stated specifications, it must be calibrated and operated in an environment where the temperature does not vary beyond 25 ± 5 °C (30 minutes of warm up after turning on the system is recommended).

The self-calibration is performed using the installed self-calibration executable located at Start>>All Programs>>National Instruments>> Vector Signal Transceivers>>VST Self Calibrate.

The NI 5644R stores the new calibration data in its nonvolatile memory if the self-calibration is performed successfully.

For more information, see: http://zone.ni.com/reference/en-XX/help/373680C-01/vstdevices/selfcalibration5644/

Path Losses are the total losses in a path which includes cable loss, attenuation used, insertion loss and connector loss.

There are four path losses to be considered:

1.VST RF OUT to SUT

2.Test Device to SUT

3.Test Device to VST RF IN

4.SUT to VST RF IN

Determination of Path Losses

Path losses are calculated outside of the MxSuite environment using WLAN Suite from NI, which includes WLAN Generator, WLAN Analyzer, and NI Switch Soft Panel. WLAN Suite requires tdms configuration files to be loaded. The settings for the WLAN Analysis tool can be loaded from the AnalyzerBaseline.tdms file and those for the WLAN Generator tool can be loaded from Generator_400Octets_Ch172.tdms located in <Project Folder>\Configuration Files. Using these tdms files avoids the need to manually configure the tools. To avoid errors while loading AnalyzerBaseline.tdms, uncheck the ‘Load Waveform’ option in the load configuration file dialog box. In the event that the ‘Device Identifier is not valid’ error is thrown, select the appropriate device from the drop-down list in Resource Name parameter.

The procedure followed to calculate losses is detailed below. The losses for each path should be determined for every channel (172, 174 etc). The losses determined in each path should then be entered in the file PathLossCalibration.csv located at <ProjectFolder>\Configuration Files. Enter the values from the VST Analyzer window into the appropriate columns. DO NOT change the format of the file as this might prevent the calibration values from being loaded. The Transform and the harness are provided with the DSRCPhysicalLayerTestAutomation.mxp project. Note that all the losses are negative numbers and should be entered as such. Select True or False for the SUT connected using FAKRA property.

Click to expand.

RF Path 1: VST RF OUT to SUT

The RF flow from VST RF Out to SUT is shown in bold lines on Figure 1. This configuration is used in the following tests (See 80211_TSS_TP_Test_Specification V1.1.0.pdf): •TP-80211-RXT-PHY-BV-01 Minimum Input Sensitivity •TP-80211-RXT-PHY-BV-02 Adjacent Channel Rejection •TP-80211-RXT-PHY-BV-03 Non-Adjacent Channel Rejection •TP-80211-RXT-PHY-BV-04 Receiver Maximum Input Level •TP-80211-RXT-PHY-BV-05 Received Channel Power Indicator Measurement For this configuration, VST RF OUT is fed through a fixed attenuator (-10dB / -8dB) and an RF Combiner to the SUT. To remove the losses in this path before the test begins, the SUT cable is connected directly to the RF IN port of the VST. The total loss in the path is calculated as the difference in observed power on the analyzer (RF IN) to the transmitted power from generator (RF OUT). When the supplied tdms files are used, the output power is set to 0 dBm and therefore the power measured on the analyzer can be entered directly into the Transform properties. For RF Path1, connect comB to sumAB and comA to sumAB on the NI Switch Soft Panel. Click to expand.

RF Path 2: Test Device to SUT

RF Path 3: Test Device to VST RF IN

RF Path 4: SUT to VST RF IN

Calibrating the Test Device

This configuration is used in the following tests (See 80211_TSS_TP_Test_Specification V1.1.0.pdf ):

•TXT-80211-RXT-PHY-BV-02 Adjacent Channel Rejection

•TXT-80211-RXT-PHY-BV-03 Non-Adjacent Channel Rejection

In these tests, a DSRC Test Device is used to generate DSRC RF traffic on the specified channel. The output of the DSRC Test Device is not calibrated and therefore its output must be adjusted at the outset of these tests. The calibration of the Test Device is done through the Calibrate Modem.mxs Scenario. This scenario is executed as part of the regression file RXT BV 02 to 03.mxreg.

The accuracies of the Vector Signal Transceiver, Programmable RF attenuator, and Combiner are included in the test system while calculating losses in the respective path.

NI PXIe-5644R

•Frequency Settling Time: Settling Time Maximum Time (ms) Low Loop Bandwidth Medium Loop Bandwidth High Loop Bandwidth ≤ 1 x 10-6 of final frequency 1.1 0.95 0.38 ≤ 0.1 x 10-6 of final frequency 1.2 1.05 0.4 •Internal Frequency Reference Initial Adjustment Accuracy………………………………………………………………………………………. ±200 * 10-9 Temperature Stability……………………………………………………………………………………………. ±1 * 10-6 max Aging………………………………………………………………………………………………………… ±1 * 10-6 per year, max Accuracy………………………………………………………………………………………………………….………... ±2.2 * 10-6 •Spectral Purity: For Center Frequency 4 GHz to 6GHz Phase Noise, 20kHz Offset (Single Sideband), Low Loop BW………………………………... -93 dBc/Hz Phase Noise, 20kHz Offset (Single Sideband), Medium Loop BW…………………………. -93 dBc/Hz Phase Noise, 20kHz Offset (Single Sideband), High Loop BW………………………………... -97 dBc/Hz RF Input •Absolute Amplitude Accuracy (dB): For center frequency 4 GHz to 6GHz 15 °C to 35 °C 0 °C to 55 °C Self-Calibration Temperature ± 1 °C Self-Calibration Temperature ± 5 °C Self-Calibration Temperature ± 1 °C Self-Calibration Temperature ± 5 °C - ± 0.90 - ± 0.95 - ± 0.75 - ± 0.80 ± 0.30, typical ± 0.55 ± 0.33 ± 0.55 •Frequency Settling Time: 0.95 ms to settle to ≤1x10-6 of final frequency 1.05 ms to settle to ≤0.1x10-6 of final frequency •Average Noise Density (dBm/Hz): For center frequency 4 GHz to 6GHz Reference level Average Noise Level (dBm/Hz) -50 dBm -156 -10 dBm -144 •Input Return Loss (VSWR): Center frequency 5 GHz to 6 GHz………………………………… -11 dB (1.78:1) •Error Vector Magnitude: 20MHz bandwidth 64-QAM, 375MHz-6GHz...................... -40 dB •Third Order Input Intercept Point: Center frequency 1.5 GHz to 6 GHz   and -20 dBm Reference level………………………………………………………………………………… 1 dBm •Second Order Input Intercept Point: Center frequency 4 GHz to 6 GHz   and -2 dBm Reference level…………………………………………………………………………………… 52 dBm RF Output •Output Power Level Accuracy (dB): Center frequency 4 GHz to 6 GHz 15 °C to 35 °C 0 °C to 55 °C Self-Calibration Temperature ± 1 °C Self-Calibration Temperature ± 5 °C Self-Calibration Temperature ± 1 °C Self-Calibration Temperature ± 5 °C - ± 1.00 - ± 1.15 - ± 0.80 - ± 0.90 ± 0.28, typical ± 0.40 ± 0.38 ± 0.60 •Frequency Settling Time: 0.95 ms to settle to ≤1x10-6 of final frequency 1.05 ms to settle to ≤0.1x10-6 of final frequency •Output Noise Density (dBm/Hz): Center frequency 3.5 GHz to 6 GHz Power Setting Average Output Noise Level (dBm/Hz) -30 dBm -165 0 dBm -147 10 dBm -136 •Output Return Loss (VSWR): 5 GHz to 6 GHz………………………………………………………… -11 dB (1.78:1) •Error Vector Magnitude: 20MHz bandwidth 64-QAM, 375MHz-6GHz....................... -40 dB •Third order intermodulation distortion: 5 GHz to 6 GHz, 0 dBm tones, Baseband DAC -2 dBFS………………................................ -44 dBc 5 GHz to 6 GHz, 0 dBm tones, Baseband DAC -6 dBFS………………................................ -45 dBc 5 GHz to 6 GHz, -6 dBm tones, Baseband DAC -2 dBFS………………............................... -50 dBc 5 GHz to 6 GHz, -6 dBm tones, Baseband DAC -6 dBFS………………............................... -54 dBc 200 MHz to 6 GHz, -36 dBm tones, Baseband DAC -2 dBFS………………........................ -54 dBc 200 MHz to 6 GHz, -36 dBm tones, Baseband DAC -6 dBFS………………........................ -58 dBc

NI PXIe-5695

NI PXIe-2790

Test Case Uncertainty

All IP addresses must be in the same subnet. IP addresses have this format:

192.168.xx.yyy

xx must be the same for all addresses in your system. yyy must be unique for each device.

There are two UDP (Generic Transform) Transforms in the test harness. For both Transforms, select the Ethernet interface from the drop down list in the Select Ethernet Interface property. Once selected, the local IP address is populated automatically.

Enter the values below in the properties of the UDP Transform connected to each device.

Modem

DUT

Setting Up the Modem Proxy

1.Create a folder named Danlaw in the C:\Users\Public\ directory if it is not already present.

2.Create a text file: TestSystemIPv4AddressAndPort.txt

3.In this text file, add the following two lines:

Test_System_IPv4Address=192.168.xxx.yyy

Test_System_ListeningPort=51000

Where 192.168.xxx.yyy is the IPv4 address of the test system.

This file is used by the test system to instruct the modem proxy where to forward DSRC packets received over the air.