From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
Each issue appears as a row in the table and includes the following fields:
ID | Known Issue | |||||
---|---|---|---|---|---|---|
713742 Return | LabVIEW becomes unresponsive when saving Application Frameworks for the first time When you create and then attempt to save an Application Framework, the LabVIEW executable becomes unresponsive. Windows reports "LabVIEW NXG is not responding" and offers to either close the program or wait for the program to respond.
| |||||
657508 Return |
Top-level nodes are not executable or LabVIEW Communications System Design Suite stops while compiling.
| |||||
611119 Return | No uplink and downlink throughput is indicated despite stable synchronization. Even though synchronization is stable, no uplink and downlink throughput is indicated, even for the lowest modulation order, and the corresponding constellation plots are of poor quality. At the same time, the diagrams for time and/or frequency tracking show differing values for both antennas. Because downlink pilots track frequency offset and sample time offset during data transmission period, the tracking may not work properly in noisy situations, such as cell edge scenario, or with low transmit or receive gains. Workaround: Avoid testing in noisy environment. To ensure that tracking is working properly, stop the mobile station and re-run it. This triggers a new synchronization procedure.
|
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.