TestStand Wireless Test Module and Wireless Test System 1.3 Known Issues

Overview

This document contains the TestStand Wireless Test Module (WTM) 1.3 and/or Wireless Test System Instrument Software (WTS Software) known issues that were discovered before and since the release of WTM 1.3. Not every issue known to NI appears on this list; it is intended to show the most severe and common issues that can be encountered.

Each issue appears as a row in the table and includes the following fields:

  • Issue ID - The number in at the top of each of the cells in the first column. When you report an issue to NI, you may be given this ID, you can also find IDs posted by NI on the discussion forums or in Knowledge Base articles.  "N/A" indicates that there is no ID assigned to the issue.
  • Issue Title (in italics) - Describes the issue in one sentence or less.
  • Problem Description - A few sentences which describe the problem in further detail. The brief description given does not necessarily describe the problem in full detail, and it is expected that you may want more information on an issue. If you would like more information on an issue, contact NI and reference the ID number given in the document.
  • Workaround - Possible ways to work around the problem. The workarounds that appear in the document are not always tested by NI and are not guaranteed to resolve the issue. If a workaround refers you to the NI KnowledgeBase, visit www.ni.com/kb/ and enter the KnowledgeBase number in the search field to locate the specific document.
  • Reported Version - The earliest version of WTM or WTS Software in which the issue was reported. If you discover the issue appears in an earlier version of WTM  or WTS Software than is reported in this field, report the discrepancy to NI to have the field updated.
  • 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).


Known Issues

The following items are known issues in WTM 1.3 and/or the WTS Software.

644173 In WTM, some error messages do not clearly state the cause of failure for test sequence execution.
647859 In WTM, an unlcear error may occur during WTM startup.
647973 In WTM, an unclear error may occur when WTM starts to execute.
647976 In WTM, a non-intutive error appears during WTM startup if ports are incorrectly configured in the hardware manifest.
647986 In WTM, a non-intuitive error appears during WTM startup if the sequence does not contain a DUT initialize step.
648451 WTM does not recover from a temporary disconnection from the WTS instrument.
648781 In the WTM Plugin Manager, the WTM plugin version number is incorrectly incremented.
649134 The WTM Plugin Manager hangs in some cases.
649292 In the WTM Plugin Manager, using the Set Public Functions compiler parameter to compile a plugin utilizing the Plugin Manager leads to issues during the compile process.
652163 In WTM, compiling password-protected plugin source code using the WTM Plugin Manager command line interface and trying to secure the compiled code with a new password in the same process does not currently work.
648370 Given that a name changed on the Bluetooth TX LE Test Step, if you created a sequence using WTM 1.0, the same sequence needs to be recreated to replace this step with the new version.
610580 In WTM, the WLAN step chain property is not aligned with the enabled or disabled antenna in the System Configuration Manifest.
613591 In WTM, the WTM Plugin Manager installs multiple plugins to TestStand if multiple manifests are found.
581719 In WTM, administrator privileges are needed for palette generation.
583132 WTM may not install correctly on some laptop computers.
527869 WTM only allows installation in the default installation path.
650999 In WTS Software, the WTS instrument may stall if not all measurements are fetched.
651648 In WTS Software, initiating the signal analyzer before the signal generator is not supported when using a custom system with an external LO.
649934 In WTS Software, an error occurs when trying to configure the Reference clock on custom systems.
650760 In WTS Software, an error may occur about invalid device identifiers at startup.
651101 WTS Software does not work with other regional settings other than English-US.
651379 In WTS Software, RFSG GPRF produces an unexpected output level in list mode.
651559 In WTS Software, the WLAN measurement does not trigger correctly.
651987 In WTS Software, the frequency calculation on LTE Band 9 is incorrect.
610154 In WTS Software, WLAN 80+80 SEM combined mask construction jumps within the linear sum region.
614461 In WTS Software, the state of the signal generator displayed on the scheduling chart may be incorrect.
616906 In WTS Software, the instrument becomes unstable if the VISA Timeout is configured to be less than the Trigger Timeout.
560856 In WTS Software, the personality does not load if it is not fully activated.
560501 In WTS Software, the instrument driver returns an incorrect instrument state.
583918 In WTS Software, the WTS scheduling chart displays the signal analyzer as active when it waits for a trigger.


ID Known Issue
644173 In WTM, some error messages do not clearly state the cause of failure for test sequence execution.

During the execution of test sequences, some error messages are misleading and do not clearly state the real cause for execution failure. Some of these cases are listed below.
  • The following error may occur if a trigger timeout happens on the WTS.
    "Unflatten From String (...) Memory or data structure corrupt"
  • The following error may occur if the WTS personality that corresponds to the executed WTM test step is not activated on the WTS.
    "To More Specific Class (...) Bad type cast. LabVIEW cannot treat the run-time value..."
Workaround: N/A

Reported Version: 1.3    Resolved Version: N/A    Added: 6/20/2017
647859 In WTM, an unlcear error may occur during WTM startup.

The following error may occur if WTM encounters an improper formed hardware manifest during startup.

"Property Node (Arg :1) Error accessing property WirelessModule.SystemConfigurationManifest.HardwareDocumentation, (System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation.
Inner Exception: System.NotImplementedException: Documentation node hasn't been implemented in this XML file!) System.NotImplementedException in niDTS TestStand.lvlib:niWTM TestStand Station UTIL Read Instrument Connections.vi->niDTS TestStand.lvlib:niDTS TestStand Station Load Configuration.vi:4290003->niDTS TestStand.lvlib:niDTS TestStand Station Load Configuration.vi.ProxyCaller LabVIEW: A .NET exception occurred in an external assembly. For information about correcting this error, copy the following exception (in bold), and search the Microsoft Developer Network (MSDN) Web site or the Web for a possible explanation."


Workaround: Do not manually alter the hardware manifest.

Reported Version: 1.3    Resolved Version: 1.4    Added: 6/20/2017
647973 In WTM, an unclear error may occur when WTM starts to execute.

The following error occurs upon WTM execution if the system manifest file is corrupted.

niDTS TestStand.lvlib:niDTS TestStand Station Index SystemDutHandles by Name and Technology.vi:1180001 Specific DUT with Name/Technology could not be found.

Complete call chain:
niDTS TestStand.lvlib:niDTS TestStand Station Index SystemDutHandles by Name and Technology.vi:1180001
niDTS TestStand.lvlib:niDTS TestStand Station Index Socket by Name and Technology,vi.vi:4400005
niDTS TestStand.lvlib:niDTS TestStand Station Index Socket by Name and Technology,vi.vi.ProxyCaller

### Additional Information:
Required DUT Name:
Required DUT Technology: Bluetooth


Workaround: Use the manifest editors and avoid manually editing the manifests.

Reported Version: 1.3    Resolved Version: 1.4    Added: 6/20/2017
647976 In WTM, a non-intutive error appears during WTM startup if ports are incorrectly configured in the hardware manifest.

The following error occurs if the ports that are configured in the hardware manifest do not exist in the instrument.

RIVI Instrument Error:
-300,"SCPI Cmd (Def):SYSTEM:RFSA:CORRECTION:CSET:SELECT, Personality Index:1; DeviceErrorCode: -200220 DeviceErrorMessage: niRFSA Initialize With Options.viDevice identifier is invalid., Device identifier is invalid."


Workaround: Use the manifest editor to create the hardware manifest, and ensure that the ports defined in the hardware manifest exist on the instrument.

Reported Version: 1.3    Resolved Version: 1.4    Added: 6/20/2017
647986 In WTM, a non-intuitive error appears during WTM startup if the sequence does not contain a DUT initialize step.

The following non-intuitive error occurs if the sequence runs without a DUT initialize step.

"niDTS TestStand.lvlib:niDTS SystemHardware.lvclass:niDTS SystemHardware Get Instrument by Name.vi
No instrument found by that name in the catalog of available initialized instruments. This could happen because the ports were not configured correctly. If using WTM, verify your Manifest to make sure all connections are populated by an instrument AND by a port associated to that instrument.

Complete call chain:
niDTS TestStand.lvlib:niDTS SystemHardware.lvclass:niDTS SystemHardware Get Instrument by Name.vi
niDTS TestStand.lvlib:niDTS TestStand Station Initialize Instrument Catalog.vi
niDTS TestStand.lvlib:niDTS TestStand Station Initialize Instrument Catalog.vi.ProxyCaller

Workaround: Ensure that the sequence that you use includes a DUT initialize step.

Reported Version: 1.3    Resolved Version: 1.4    Added: 6/20/2017
648451 WTM does not recover from a temporary disconnection from the WTS instrument.

If WTM loses connection to the WTS instrument, WTM does not recover and the sequence must be restarted. If the WTM Operator Interface Example is used, then you must stop the station and click Start Station twice for the system to recover the connection to the instrument.

Workaround: Restart the station.

Reported Version: 1.3    Resolved Version: 1.4    Added: 6/20/2017
648781 In the WTM Plugin Manager, the WTM plugin version number is incorrectly incremented.

In some cases, the plugin version number is not incremented correctly if the Plugin Manager is instantiated more than once. The Plugin Manager has a local version of the plugin database and when instantiated multiple times, the local versions may become out of sync.

Workaround: Avoid instantiating multiple versions of the Plugin Manager.

Reported Version: 1.3    Resolved Version: N/A    Added: 6/20/2017
649134 The WTM Plugin Manager hangs in some cases.

In some cases, the Plugin Manager hangs due to setting read/write permissions while compiling the source.

Workaround: Wait for the Plugin Manager to finalize.

Reported Version: 1.3    Resolved Version: 1.4    Added: 6/20/2017
649292 In the WTM Plugin Manager, using the Set Public Functions compiler parameter to compile a plugin utilizing the Plugin Manager leads to issues during the compile process.

In some cases, the compile process fails when compiling plugin source code into packages using the WTM Plugin Manager when the Set Public Functions compiler parameter is enabled for the plugin.

Workaround: Do not use the Set Public Functions compiler parameter. The parameter is set to disabled by default.

Reported Version: 1.3    Resolved Version: 1.4    Added: 6/20/2017
652163 In WTM, compiling password-protected plugin source code using the WTM Plugin Manager command line interface and trying to secure the compiled code with a new password in the same process does not currently work.

When compiling password protected Plugin source code using the WTM Plugin Manager command line interface, and trying to secure the compiled code with a new password in the same process, using the command line call WTM_PluginManager.exe -c=<plugin ID>,<current password>,<new password> (or its equivalent), the specified current password does not propagate all the way through to the WTM Plugin Manager. Therefore, removing password security from the Plugin source code before compiling it does not succeed and the compile process fails.

This issue may impact you if you have a password-protected plugin source code and want to process the plugin in an automated build process utilizing the WTM Plugin Manager command line interface. This does not affect other cases where the plugin source code is unprotected. Only the WTM Plugin Manager command line interface is affected, not the graphical interface.

Workaround: Remove the password security from the plugin source code before starting the WTM Plugin Manager compile process. Alternatively, you can compile the plugin source code using the WTM Plugin Manager graphical interface.

Reported Version: 1.3    Resolved Version: 1.4    Added: 6/20/2017
648370 In WTM, upgrading Bluetooth TX LE test steps when opening a WTM 1.0 sequence in WTM 1.3 does not work.

Given that a name changed on the Bluetooth TX LE Test Step, if you created a sequence using WTM 1.0, the same sequence needs to be recreated to replace this step with the new version.

Workaround: Replace the old step with the new step. Delete the old step from the test sequence, and modify the parameters to match the old step.

Reported Version: 1.3    Resolved Version: 1.4    Added: 6/20/2017
610580 In WTM, the WLAN step chain property is not aligned with the enabled or disabled antenna in the System Configuration Manifest.

It is possible that not all DUT antennas are actually connected to the WTS if these antennas are indicated as disabled in the System Configuration Manifest. The WLAN step chain property is not aware of the disabled antenna in the System Configuration Manifest. For example, if DUT antennas 0 and 2 are enabled, DUT antennas 1 and 3 are disabled, and the Chains test step parameter is set True, False, True, False, then antennas 0 and 2 are hooked up to the WTS and enabled in this step. Instead, WTM recognizes only the first enabled antenna.

Workaround: Manually update the WLAN step chain property if you disable any antennas in the System Configuration Manifest.

Reported Version: 1.2    Resolved Version: 1.4    Added: 11/29/2016
613591 In WTM, the WTM Plugin Manager installs multiple plugins to TestStand if multiple manifests are found.

The WTM Plugin Manager installs all the manifests found on the installed plugin. This behavior is intended. You can also create a new plugin and use the WTM Plugin Manager to create a manifest.

Workaround: N/A

Reported Version: 1.2    Resolved Version: 1.4    Added: 11/29/2016
581719 In WTM, administrator privileges are needed for palette generation.

Depending on the computer settings, the WTM Palette Generation Tool may require you have administrator privileges.

Workaround: Open TestStand as an administrator. Right-click on seqedit.exe, and select Run as administrator.

Reported Version: 1.1    Resolved Version: N/A    Added: 05/04/2016
583132 WTM may not install correctly on some laptop computers.

Sometimes the WTM installer does not run as expected on laptop computers when the laptop is running on battery power.

Workaround: Plug in the laptop to a power outlet. The installer will continue successfully.

Reported Version: 1.1    Resolved Version: 1.4    Added: 05/04/2016
527869 WTM only allows installation in the default installation path.

The WTM installer provides the option to change the installation path from the suggested location. However, if you select a non-default location, WTM no longer works as expected.

Workaround: Do not change the default WTM installation path.

Reported Version: 1.0.1    Resolved Version: N/A    Added: 11/05/2015
650999 In WTS Software, the WTS instrument may stall if not all measurements are fetched.

If two measurements are requested at the same time, one has a long processing time while the other has a short processing time. If you fetch the measurement with the short processing time and execute *RST before the measurement with the long processing time is complete, the instrument stalls.

Workaround: Fetch all measurements requested or disable the measurements that are not needed.

Reported Version: 1.3    Resolved Version: N/A    Added: 6/20/2017
651648 In WTS Software, initiating the signal analyzer before the signal generator is not supported when using a custom system with an external LO.

In a custom system with an external LO connected to the same signal analyzer (SA) and signal generator (SG) block, the instrument does not support starting the SA before the SG. The SG tries to unshare the LO for a brief moment, causing the SA timeout the acquisition.

Workaround: Start the SG first and then the SA as needed. This is most common on evaluation in loopback.

Reported Version: 1.3    Resolved Version: N/A    Added: 6/20/2017
649934 In WTS Software, an error occurs when trying to configure the Reference clock on custom systems.

In some cases, the preview setting of Reference clock is carried to the next session and prevents initiate. This happens only on custom systems after the previous instance of the SCPI Interface Module Executable is killed.

Workaround: Shutdown the controller and WTS Software gracefully, and allow the process to clean up. Restart the computer.

Reported Version: 1.3    Resolved Version: N/A    Added: 6/20/2017
650760 In WTS Software, an error may occur about invalid device identifiers at startup.

WTS Software returns an error that states "The specified trigger line is currently in use" at startup. This error occurs when the previous instance of the SCPI Interface Module Executable is killed. The previous instance reserves trigger lines and does not have enough time to return it to the trigger line pool.

Workaround: Shutdown WTS Software gracefully, and restart the instrument.

Reported Version: 1.3    Resolved Version: N/A    Added: 6/20/2017
651101 WTS Software does not work with other regional settings other than English-US.

SCPI and VISA support only using a period (.) as a decimal point and comma (,) to separate parameters and lists. WTS Software malfunctions and becomes unusable if you use any other settings.

Workaround: Ensure you are using (.) as the decimal symbol value, and (,) as the list separator value in Regional Settings»Additional Settings.

Reported Version: 1.3    Resolved Version: N/A    Added: 6/20/2017
651379 In WTS Software, RFSG GPRF produces an unexpected output level in list mode.

The wrong application of attenuation settings for listable ports in sequence mode occurs when logical port names are used.

Workaround: When using a port as a listable item in list mode, ensure you use the physical port names that are available after system restart. To check the physical port name of the user-defined logical port, query the instrument by sending the ROUTe:RF:PORT:DEFine? <LogicalPortName> command.

Reported Version: 1.3    Resolved Version: N/A    Added: 6/20/2017
651559 In WTS Software, the WLAN measurement does not trigger correctly.

The WLAN instrument personality has an issue with trigger settings if they are left at default. If you do not set anything within the TRIGger:RFSA:WLAN subgroup, then the WLAN personality does not perform measurements.

Workaround: Make a minimum of one setting in the TRIGger:RFSA:WLAN subgroup, even if the default values are suitable for your application.

Reported Version: 1.3    Resolved Version: N/A    Added: 6/20/2017
651987 In WTS Software, the frequency calculation on LTE Band 9 is incorrect.

When setting frequency by band and channel, the following error occurs upon initiate.

-300,"SCPI Cmd (Def):INITIATE:RFSA:LTE:RESULTS, Personality Index:1; DeviceErrorCode: -1074135024 DeviceErrorMessage: niRFSA Initiate.vi IVI: (Hex 0xBFFA0010) Invalid value for parameter or property. The following attribute values are in conflict with each other: Attribute: External Gain Specified Value: -0.000000 Attribute: Reference Level Specified Value: 35.000000 Maximum Value: 30.000000, IVI: (Hex 0xBFFA0010) Invalid value for parameter or property."

This is due to an internal error on frequency calculation for B9 channel to frequency. This also affects bands B11, B21, and B24.

Workaround: When using normal mode, use the frequency instead of band and channel. In sequence mode, there is no workaround. Contact your NI representative to request the latest patch update.

Reported Version: 1.3    Resolved Version: N/A    Added: 6/20/2017
610154 In WTS Software, the construction of WLAN 80+80 SEM combined mask jumps within the linear sum region.

The combined mask may appear to jump between two carriers. This does not affect the WLAN 80+80 validation results.

Workaround: N/A

Reported Version: 1.2    Resolved Version: N/A    Added: 11/29/2016
614461 In WTS Software, the state of the signal generator displayed on the scheduling chart may be incorrect.

If you start the WTS Instrument Software GUI after the signal generator is powered on, the scheduling chart displays the incorrect state of the signal generator. If you manually turn on the signal generator and leave it on for 10 to 20 seconds, then turn the signal generator off, the scheduling chart might not reflect this change.

Workaround: Start the WTS Instrument Software GUI before powering on the signal generator, or reset the signal generator by sending the *RST command. You can also reset the instrument through the WTS Instrument Software GUI in the mandatory personality. Use the scheduling chart during automated control rather than manual control.

Reported Version: 1.2    Resolved Version: N/A    Added: 11/29/2016
616906 In WTS Software, the instrument becomes unstable if the VISA Timeout is configured to be less than the Trigger Timeout..

In some cases, the unit under test (UUT) might not transmit and the instrument reports a trigger timeout. If the VISA command does not wait long enough (because the VISA Timeout is configured to be less than Trigger Timeout), the instrument waits for a trigger and any reconfiguration of the signal analyzer while the signal analyzer is waiting on a trigger can bring the instrument to an undesirable state.

Workaround: If you see a query interrupted on IO Trace, the VISA Timeout is not large enough. Ensure the VISA Timeout is always larger than any Trigger Timeout of the instrument.

Reported Version: 1.2    Resolved Version: N/A    Added: 11/29/2016
560856 In WTS Software, the personality does not load if it is not fully activated.

Within NI License Manager, a fully activated license is identified by a dark green mark next to the personality name. If the license is not fully activated, the instrument will not load the personalty.

An activation of a personality indicated by a light green mark does not mean it is fully activated and therefore it will not load. A light green mark means that the personality will activate on the next use of the product, but the product requires the license to be fully activated before using it.

Workaround: Fully activate the license of the personality where a dark green mark is displayed next to the personality name in NI License Manager.

Reported Version: 1.0    Resolved Version: N/A    Added: 05/04/2016
560501 In WTS Software, the instrument driver returns an incorrect instrument state.

The instrument driver used by the WTM test steps caches the values that are sent to the instrument. For the correct state, it is important to always send an *OFF command before sending an *ON command. This is because the signal generator may have done finite generation, which does not update the cache of the instrument driver.

Workaround: Send the *OFF state command before sending the *ON state command.

Reported Version: 1.0.1    Resolved Version: N/A    Added: 05/04/2016
583918 In WTS Software, the WTS scheduling chart displays the signal analyzer as active when it waits for a trigger.

The signal analyzer is active when waiting for a trigger, and you cannot use it for anything else during that time.

Workaround: N/A

Reported Version: 1.1    Resolved Version: N/A    Added: 05/04/2016

Contacting NI

Contact NI regarding this document or issues in the document. If you contact NI in regards to a specific issue, reference the ID number given in the document. The ID number contains the current issue ID number as well as the legacy ID number (use the current ID number when contacting NI). You can contact us through any of the normal support channels including phone, email, or the discussion forums. Visit the NI Website to contact us. Also contact us if you find a workaround for an issue that is not listed in the document.

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).