This document contains the WLR Test Software known issues that were discovered before and since the release of WLR Test Software 22.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 |
|---|---|---|---|
| 1596467 |
Test Results Return Incorrect Group Names for Steps with the Same Names in a WLR Test SequenceThe WLR Test Soft Front Panel uses the TDMS file format for saving
test results. Each group in the TDMS files represents the test results for
running a step once. The group name for a step not in a loop is the exact step
name. The group name for a step in a loop is “step name_<iteration
index>”. For example, the group name for a step running in the second
iteration is “step name_1”. In a WLR test sequence, steps with the same names are considered
as iterations in a loop when the test results are returned, so the group names
for steps apart from the first step are written in the following format: “step
name_<iteration index>”.
Workaround: NI recommends that you specify a unique name for each step in a sequence and always rename a step after you add it to a test sequence.
|
Reported Version: WLR Test Software: 22.0 Resolved Version: N/A Added: Jan 29, 2022 |
|
| 1775158 |
Error -1074107494 Might Occur when WLR List Sweep or WLR Initialize Runs together with Programs that Causing High CPU Usage on the Test SystemError -1074107494: “No registered trigger lines could be found between the devices in the route”. This error might occur when the test system is performing tasks that require many CPU resources while running WLR List Sweep or WLR Initialize. The CPU resources are occupied either by the WLR test or other running programs. This error message could keep popping up if you close it and initialize a WLR session again.
Workaround: Reboot the test system. To avoid this issue, NI recommends that you do not run other programs causing high CPU usage when running the WLR test APIs or using the WLR Test Soft Front Panel.
|
Reported Version: WLR Test Software: 22.0 Resolved Version: N/A Added: Jan 29, 2022 |
|
| 1796623 |
The Actual Stress Time Can Be Larger than Specified when Running WLR Stress with High Sample Rate on Multiple SitesIf measurement mode in WLR Stress is set to Measure Multiple Times, WLR Test Software tries to perform measurements at the specified sample rate. When the site number increases, system resources allocated for each site are decreasing, so it takes more time to start the next measurement on each site. If you specify a high sample rate for WLR stress tests in multiple sites, the actual speed of sampling can be lower than specified. Because WLR Test Software is designed to ensure the sample count as expected, the actual stress time can be longer than specified. In some cases, the actual stress time can be twice the value you specified.
Workaround: Specify lower sample rate or less aperture time when running WLR Stress on multiple sites. For example, when testing 12 sites with 4-terminal DUTs or 24 sites with 2-terminal DUTs, set the aperture time to 1 PLC (at 60 Hz power line frequency) and set the sample rate lower than 29 S/s.
|
Reported Version: WLR Test Software: 22.0 Resolved Version: N/A Added: Jan 29, 2022 |
|
| 1789814 |
Error -17300 Might Occur when Running the WLR Test Soft Front Panel with Command Line InterfaceError -17300: “The TestStand enumerator <enumerator name> does not match any enumerator in the LabVIEW enum parameter <enum parameter name>”. The probability that this error occurs is about 1%. Workaround:
|
Reported Version: WLR Test Software: 22.0 Resolved Version: N/A Added: Jan 29, 2022 |
|
| 1799997 |
More Delays Occur when Running WLR List Sweep on SMUs in Different ChassisWLR List Sweep uses trigger lines on the PXIe backplane to ensure SMUs in a WLR test are synchronized. Among several chassis in the test system, trigger lines are connected by high-density trigger connectors, which requires more time for internal switches. If you run WLR List Sweep on SMUs in different chassis, the time needed for routing internal synchronization connections before WLR List Sweep starts and after WLR List Sweep ends can be almost four times longer than you run WLR List Sweep on SMUs in the same chassis.
Workaround:
|
Reported Version: WLR Test Software: 22.0 Resolved Version: N/A Added: Jan 29, 2022 |
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