Archived: NI WCDMA 1.1.5 Known Issues

NI does not actively maintain this document.

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.

Overview



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

Known Issues:

  • National Instruments recommends that you lock the frequency reference clock source between the device generating the WCDMA/HSPA+ signals and the NI RF signal analyzer. The ModAcc, CDA, and Constellation EVM measurements may degrade from specifications when the clocks are not locked.
  • NI recommends that you calibrate the device generating the WCDMA/HSPA+ signals before performing measurements. EVM values may degrade from specifications in the presence of I/Q impairments.
  • The ModAcc and CDA measurements can tolerate a CFO of up to +/-3000 Hz for all the modes. If the High CFO Correction option is enabled in Frame mode, the measurement can tolerate a CFO of up to 50 Khz. In case of EVMQPSK CFOs, the measurement can tolerate a CFO of up to 25 kHz.
  • The time elapsed for ModAcc and CDA measurements will be greater by ~100 ms more in Frame mode and when the “High CFO Correction” option is enabled.
  • The Constellation EVM measurement reports a bad EVM for waveforms with DC offset and a 25 kHz frequency offset.
  • The EVM floor is slighly degraded compared to version 1.0.
  • The toolkit returns bad EVMs when the Scrambling Code Type is short.
  • The toolkit returns bad EVMs for shorter measurement lengths in the Constellation EVM Measurement.
    CFOs are not multiples of 100 Hz when analyzing the first slot. When the SCH is included, CFOs are not multiples of 100 Hz when analyzing the 15th slot.
  • The toolkit returns bad EVMs for ModAcc measurement when the I/Q DC Offset value is beyond the range of +2 to -2.
  • The toolkit returns bad EVMs when the clocks are synced and with TM4 without CPICH.

 

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

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