This document contains the mmWave OTA Validation Test Software known issues that were discovered before and since the release of mmWave OTA Validation Test Software 20.0. Known issues are performance issues or technical bugs that NI has acknowledged exist within this version of the product.
Not every issue known to NI appears on this list; it is intended to show the most severe and common issues that you may encounter and provide workarounds when possible. Other technical issues that you may encounter could occur through normal product use or system compatibility issues. You may find more information on these issues in NI’s Product Documentation, Knowledgebase, or Community.
|
Bug Number |
Legacy ID |
Description |
Details |
|---|---|---|---|
| 939683 |
An unexpected behavior occurs when the Move Home button is selected in the mmWave OTA Test Positioner SFPWhen 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: N/A Added: N/A |
|
| 1097076 |
Error -379415 occurs when initializing an OTA sessionOn the Generator Calibration Settings section of the RF System Calibration Assistant Configurator window, if there is more than one Powers (dBm) selected for a single Frequencies (Hz), the following error occurs: "-379415 Invalid table input. The input frequency array contains a duplicate value." Workaround: Run the RF System Calibration Assistant using only one power level and one reference level.
|
Reported Version: mmWave OTA Validation Test Software 20.0 Resolved Version: N/A Added: N/A |
|
| 1097098 |
LoadLibrary failed with error 87If you connect to a system using a remote desktop and open the mmWave OTA Validation Configurator or the mmWave OTA Validation Visualizer, the following error occurs: "LoadLibrary failed with error 87: The parameter is incorrect." The error occurs because there is a Windows problem when running OpenGL hardware-accelerated programs through remote desktop (RDP) sessions. Workaround:
|
Reported Version: mmWave OTA Validation Test Software 1.0 | mmWave OTA Validation Test Software 20.0 Resolved Version: N/A Added: N/A |
|
| 1112059 |
An initialization error occurs in TestStand if you run the OTA sequence directly from TestStandIf you open the mmWave OTA Validation Configurator and run the example sequence file directly in the TestStand Sequence Editor instead of starting the sequence from the mmWave OTA Validation Configurator, TestStand returns the following error: “Cannot initialize RF session.” Workaround:
|
Reported Version: mmWave OTA Validation Test Software 20.0 Resolved Version: N/A Added: N/A |
|
| 1112060 |
Cannot upgrade to new version of mmWave OTA Validation Test Software using NI Package ManagerIf 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:
|
Reported Version: mmWave OTA Validation Test Software 20.0 Resolved Version: N/A Added: N/A |
|
| 1115166 |
The mmWave OTA Validation Test Software does not support German OS due to difference in decimal separatorThe 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: N/A Added: N/A |
|
| 1142495 |
Files required for single-tone measurements are missing if the mmWave OTA Example package is not installedIf 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:
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: N/A Added: N/A |
Issues found in this section will not be listed in future known issues documents for this product.
There are currently no issues to list.
Explore Support Content and Product Documentation
Ask the NI Community
Request Support from an Engineer
A valid service agreement may be required, and support options vary by country