This content provides support for older products and technology, so you may notice outdated links or obsolete information about operating systems or other relevant products.
This document contains the NI LTE Toolkit 1.0 known issues that were discovered before and since the release of NI LTE Toolkit 1.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.
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).
Incorrect conversion for cyclic shift indexes when 3GPP cyclic shift is disabled in NI LTE Generation Toolkit 1.0
When the 3GPP Cyclic Shift Enabled property is set to False, the toolkit uses the PUSCH Cyclic Shift Index 0 and PUSCH Cyclic Shift Index 1 properties. However, the toolkit does not convert the cyclic shift indexes to alpha_cs as defined in section 18.104.22.168 of the 3GPP TS 36.211 v 8.6.0 specifications.
Workaround: Set the 3GPP Cyclic Shift Enabled property to True.
Cannot set the NILTESG_DL_PHICH_PAYLOAD_USER_DEFINED_DATA attribute in the NI LTE Generation Toolkit for CVI/C
If you set the NILTESG_DL_PHICH_PAYLOAD_USER_DEFINED_DATA 2D array attribute to a valid value, the toolkit incorrectly resets this attribute value to an empty array.
Affected Functions: niLTESG_Set2DArrayAttributeI32, niLTESG_SetDLPHICHPayloadUserDefinedData
The PHICH duration in the MIB is always set to Normal when the PBCH payload type is set to Auto Configure
When the PBCH payload type is set to Auto Configure, the master information block (MIB) configuration follows section 6.2.2 of the 3GPP TS 36.331 v8.6.0 specifications. However, when the PHICH duration is set to Extended, the bits representing the PHICH duration correspond to Normal PHICH duration.
Workaround: Set the PBCH payload type to User Defined Bits and then configure the MIB.
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.
Incorrect display of some parameter values in the NI LTE 1.0 Analysis Interactive Example
For some settings, the interactive example displays the default parameter values and not the actual values used for the measurement. For example, in the Channel Power configuration page, if you set the Span Type parameter to Standard, the interactive example automatically chooses the Span and Measurement BW parameter values according to the settings specified in the 3GPP TS 36.521 v8.6.0 specifications. However, the interactive example does not display these updated parameter values and shows only the default values.
This is only a display issue; the measurements reported are accurate.
The following table lists the parameters that do not display the actual values used for measurement.
Parameters displaying incorrect value
Adjacent Channel Power
Frequency List Type = Standard
Ref. Channel Bandwidth
Span Type = Standard
RBW Filter Type
Span Type = Standard
Reported Version: 1.0
Resolved Version: 1.0.1
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.