Each issue appears as a row in the table and includes the following fields:
The following items are known issues in WTM 1.2 and/or the WTS Software.
| ID | Known Issue | |||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 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.
| |||||||||||||||||||||||
| 613666 | In TestStand, the WTM steps may compute incorrect parameter values in some scenarios. The following list includes the incorrect generated parameter values:
| |||||||||||||||||||||||
| 613641 | In WTM, the WTM Plugin Manager might halt indefinitely. The LabVIEW adapter opened by TestStand does not close, which may cause the WTM Plugin Manager to halt. Workaround: Close TestStand, the TestStand Sequence Editor, the WTM Plugin Manager, and any other references to LabVIEW. Reopen the WTM Plugin Manager.
| |||||||||||||||||||||||
| 617415 | The WTM Manifest Editor cannot open the Plugin Package Manifests of the type DUT created by the WTM Plugin Manager. The Plugin Package Manifest of the type DUT created by the WTM Plugin Manager cannot be read by the WTM Manifest Editor due to a change in the representation of the DUT manifest information. Workaround: Use the WTM Plugin Manager to modify the type DUT manifest information within the Plugin Package Manifest. NI recommends using the WTM Plugin Manager for any further modifications to manifest information.
| |||||||||||||||||||||||
| 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
| |||||||||||||||||||||||
| 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.
| |||||||||||||||||||||||
| 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.
| |||||||||||||||||||||||
| 582487 | The WTM Loopback DUT Manifest needs to be recreated after upgrading to a new version of WTM. The WTM Loopback DUT Manifest changes over each version of the software to account for new capabilities and new technologies that are added. Therefore, the WTM Loopback DUT Manifest needs to be recreated if you upgrade to a new version of WTM. When using an old WTM Loopback DUT Manifest, the returned error may be confusing since the number of elements might be different between the two loopback DUT versions. Workaround: Recreate the System Configuration Manifest.
| |||||||||||||||||||||||
| 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.
| |||||||||||||||||||||||
| 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
| |||||||||||||||||||||||
| 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.
| |||||||||||||||||||||||
| 617000 | In the WTS Instrument Software GUI, some parameter values do not update correctly after calling the *RST command. Some parameter values in the RF General Settings instrument personality do not always update correctly when the you call the *RST command. The following subsystems may not return to their default state when the instrument is reset.
| |||||||||||||||||||||||
| 612548 | In WTS Software, setting a non-existent port for WLAN SG results in a non-intuitive error. The following non-intuitive error results if a non-existent port is set for WLAN SG: -300,"SCPI Cmd (Def):SOURCE:RFSG:WLAN:STATE, Personality Index:1; DeviceErrorCode: 5000 DeviceErrorMessage: niRFInstr SG.lvlib:niRFInstr SG Create and Download.vi:760002 Internal Error: The hardware has a thread lock. This lock timeout after 60 seconds. This means someone keep this lock and didn't return." Workaround: Ensure all the ports are configured correctly.
| |||||||||||||||||||||||
| 614764 | In WTS Software, the total memory consumption grows over time. The WTS Software memory grows over time. For the first few hours of use, the memory rate is large but decreases over time. The memory consumption is large due to the following reasons:
| |||||||||||||||||||||||
| 617402 | The connection session updates are not visible on the WTS Instrument Software GUI. If a connection session is added through the command SYSTem:INSTrument:COUNt, by default that connection session is not updated on the WTS Instrument Software GUI. Workaround: To enable the WTS Instrument Software GUI updates, you must change a parameter in the connection session file. Complete the following steps to enable the WTS Instrument Software GUI updates:
| |||||||||||||||||||||||
| 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.
| |||||||||||||||||||||||
| 611452 | In WTS Software, the Trigger Line Manager does not work correctly for WLAN MIMO measurements with logical port names on non-WTS hardware systems. On a non-WTS hardware system, specifically those with an 18-slot chassis, the trigger requires connections that are not done automatically for non-physical ports. For this reason, MIMO measurements do not work when using non-physical ports (virtual ports). Workaround: Use the physical port names but do not use logical ports names.
| |||||||||||||||||||||||
| 581014 | In WTS Software, the LTE origin offset results may be higher than expected. The instrument may have better origin offset than expected because the instrument has its own LO signal located at the center frequency. Workaround: N/A
| |||||||||||||||||||||||
| 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.
| |||||||||||||||||||||||
| 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.
| |||||||||||||||||||||||
| 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
| |||||||||||||||||||||||
| 623403 | In WTS Software, the ZigBee waveforms have the wrong scaling. The ZigBee waveforms in WTS Software contain the wrong headroom parameter, which causes the wrong scaling and the output power to be higher than expected. Workaround: N/A
|
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.