mmWave OTA Validation Test Software 20.5 Bug Fixes

Overview

The following items are notable issues fixed between the release of mmWave OTA Validation Test Software 20.0 and mmWave OTA Validation Test Software 20.5, including additional patches and service packs. If you have an issue ID, you can search this list to validate that the issue has been fixed. This is not an exhaustive list of issues fixed in the current version of mmWave OTA Validation Test Software.

Bug Number

Legacy ID

Description

Details

939683

An unexpected behavior occurs when the Move Home button is selected in the mmWave OTA Test Positioner SFP

When the Move Home button is selected in the mmWave OTA Test Positioner SFP, the positioner moves to the current offset that specifies the new home then moves back to the actual home. This unexpected movement can lead to tangled cables and may cause things to fall off the positioner if not properly fixed or removed, such as the antenna or spirit level.

Workaround:

There is currently no known workaround for this issue.

Reported Version:

mmWave OTA Validation Test Software 1.0 | mmWave OTA Validation Test Software 20.0

Resolved Version:

mmWave OTA Validation Test Software 20.5

Added:

Sep 2, 2020

1112060

Cannot upgrade to new version of mmWave OTA Validation Test Software using NI Package Manager

If you try to upgrade mmWave OTA Validation Test Software 1.0 to 20.0 in NI Package Manager (NIPM), NIPM displays the following message:

"Package is not installed or is not upgradable. No operation will be performed."

Workaround:

  1. Using NIPM, uninstall mmWave OTA Validation Test Software 1.0, then install 20.0 from ni.com/downloads.
  2. Ensure NIPM 20.5 or later is installed. 

Reported Version:

mmWave OTA Validation Test Software 20.0

Resolved Version:

mmWave OTA Validation Test Software 20.5

Added:

Sep 2, 2020

1115166

The mmWave OTA Validation Test Software does not support German OS due to difference in decimal separator

The following error occurs when you run the C# example application you are using an OS language that does not support the decimal point "." as a decimal separator. 

"An error occurred before the OTA test started the measurement. Exception(s): Die Eingabezeichenfolge hat das falsche format."

The error occurs because the configuration CSV file uses "." as a decimal point, and the C# code uses the OS language to parse double.

If you change the OS number format or copy the RF System Calibration result file from another computer, the TestStand sequence and C# example sequence may report a similar error because the RF System Calibration result files use the current OS language for the decimal separator.

Workaround:

Change the OS language to one that supports the decimal point "0.1" as a separator, and not a decimal comma "0,1".

Reported Version:

mmWave OTA Validation Test Software 20.0

Resolved Version:

mmWave OTA Validation Test Software 20.5

Added:

Sep 2, 2020

1142495

Files required for single-tone measurements are missing if the mmWave OTA Example package is not installed

If you choose to not install the mmWave OTA Example package when you install the mmWave OTA Validation Test Software 20.0, the following files are not installed:

  • C:\Users\Public\Documents\National Instruments\TestStand 2019 (64-bit)\Examples\OTA Test\Configurations\CW_RFmx.tdms
  • C:\Users\Public\Documents\National Instruments\TestStand 2019 (64-bit)\Examples\OTA Test\Waveforms\CW.tdms

You cannot perform single-tone measurements if these files are missing.

Workaround:

Ensure that mmWave OTA Examples is selected in NI Package Manager when you install the software.

Reported Version:

mmWave OTA Validation Test Software 20.0

Resolved Version:

mmWave OTA Validation Test Software 20.5

Added:

Sep 30, 2020

Additional Patch Information

Installing some patches may require certain additional steps or considerations. Please refer to the following table for more information about patches for this release.

These patches currently do not have any special instructions.

Glossary of Terms

 

  • Bug ID - When an issue is reported to NI, you may be given this ID or find it on ni.com.  You may also find IDs posted by NI on the discussion forums or in KnowledgeBase articles.
  • Legacy ID – An older issue ID that refers to the same issue.  You may instead find this issue ID in older known issues documents.
  • Description - A few sentences which describe the problem. The brief description given does not necessarily describe the problem in full detail.
  • Workaround - Possible ways to work around the problem.
  • Reported Version - The earliest version in which the issue was reported.
  • Resolved Version - Version in which the issue was resolved or was no longer applicable. "N/A" indicates that the issue has not been resolved.
  • Date Added - The date the issue was added to the document (not the reported date).