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-RFmx Demod 1.0 and 1.1 known issues that were discovered before and since the release of NI-RFmx Demod 1.0 and 1.1. 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).
RMS EVM is higher than expected when sync bits are found in OQPSK signal.
When a synchronization pattern is found in OQPSK signal, the RMS EVM and RMS Offset EVM are high.
The reference waveform created using the demodulated bits after finding the synchronization pattern has transients in the begin of the waveform. This causes the symbols in the beginning of the waveform to have higher EVM.
Applying equalization in OQPSK does not improve Mean RMS EVM and Mean Peak EVM, even though Mean RMS Offset EVM and Mean Peak Offset EVM improve.
Equalization on OQPSK signals does not improve Mean RMS EVM and Mean Peak EVM.
Equalization on OQPSK signal is performed after the offset between the I and Q channels are removed. This method improves Mean RMS Offset EVM and Mean Peak Offset EVM, but does not improve Mean RMS EVM and Mean Peak EVM
Save RFmx VIs when prompted.
If you are not using NI RFSA 14.0, save the RFmx VIs when prompted.
Reported Version: 1.1
Resolved Version: N/A
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.
You probably noticed we have a new look, but our focus remains on you. We've expanded our offerings to better serve you so that you can take on the complex challenges facing humanity today, tomorrow, and for the next 100 years. It's time. Let's Engineer Ambitiously.