NI LTE Toolkit 2.0 Known Issues

Updated Sep 9, 2025

Overview

This document contains the NI LTE Toolkit 2.0 known issues that were discovered before and since the release of NI LTE Toolkit 2.0. 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.

Glossary of Terms

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 NI-RFSG in which the issue was reported. If you discover the issue appears in an earlier version of NI-RFSG 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 by Severity

246803	—	Auto detection of resource blocks does not work when you set the number of PUSCH resource blocks to 1
276101	—	Incorrect I/Q gain imbalance and quadrature skew measurements returned for asymmetric frequency domain allocations
317040	—	SRS EVM measurement does not work for special subframes
325982	—	The PUCCH EVM deteriorates for some cell IDs
327603	—	OBW measurement displays inconsistent results for PUCCH and sparsely-filled PUSCH
329207	—	The toolkit does not apply trigger delay for ACP and SEM measurements
329842	—	ModAcc measurements return incorrect results for uplink PUSCH and PUCCH occupied in certain subframes when the Measurement Mode is set to Specific Slot
333815	—	The toolkit displays an error when you increase the value of n_DMRS and enable auto detection for PUSCH TDD

Known Issue

246803

Auto detection of resource blocks does not work when you set the number of PUSCH resource blocks to 1.

The toolkit cannot auto detect single resource blocks for all bandwdths.

Workaround: Set the Auto RB Detection Enabled property to False if you set the number of resource blocks to 1.

Reported Version: 2.0

Resolved Version: N/A

Added: 02/08/2012

276101

Incorrect I/Q gain imbalance and quadrature skew measurements returned for asymmetric frequency domain allocations

The I/Q gain imbalance and quadrature skew impairments are estimated in the frequency domain. The algorithm assumes that the RB allocation is symmetric about the DC sub-carrier. If the RB allocation is not symmetric, the algorithm returns incorrect values.

Workaround: None

Reported Version: 1.0

Resolved Version: N/A

Added: 02/10/2011

317040

SRS EVM measurement does not work for special subframes

The NI LTE 2.0 Toolkit does not support EVM measurements in the UpPTS field of the special subframe.

Workaround: Do not analyze special subframes.

Reported Version: 2.0

Resolved Version: N/A

Added: 02/08/2012

325982

The PUCCH EVM deteriorates for some cell IDs

The PUCCH EVM deteriorates for cell IDs 175 and 375.

Workaround: None

Reported Version: 2.0

Resolved Version: N/A

Added: 02/08/2012

327603

OBW measurement displays inconsistent results for PUCCH and sparsely-filled PUSCH

The OBW measurement displays inconsistent results for fully-filled PUCCH and Low RB PUSCH.

Workaround: OBW measurement is not supported for PUCCH and sparsely-filled PUSCH.

Reported Version: 2.0

Resolved Version: N/A

Added: 02/08/2012

329207

The toolkit does not apply trigger delay for ACP and SEM measurements

The toolkit does not apply trigger delay for 15 MHz and 20 MHz ACP and SEM measurements.

Workaround: None

Reported Version: 2.0

Resolved Version: N/A

Added: 02/08/2012

329842

ModAcc measurements return incorrect results for uplink PUSCH and PUCCH occupied in certain subframes when the Measurement Mode is set to Specific Slot

ModAcc measurements return incorrect results for uplink PUSCH and PUCCH when the Measurement Mode is set to Specific Slot.

Workaround: None

Reported Version: 2.0

Resolved Version: N/A

Added: 02/08/2012

333815

The toolkit displays an error when you increase the value of n_DMRS and enable auto detection for PUSCH TDD

The toolkit displays the "Unable to Synchronize" error message when you increase the value of n_DMRS and enable auto detection for PUSCH TDD.

Workaround: None

Reported Version: 2.0

Resolved Version: N/A

Added: 02/08/2012

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