NI-mmWave 18.1 and 19.0 Known Issues

Aperçu

This document contains the NI-mmWave 18.1 and 19.0 known issues that were discovered before and since the release of NI-mmWave 18.1 and 19.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-mmWave in which the issue was reported. If you discover the issue appears in an earlier version of NI-mmWave 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

713511 Multiple PXI Express chassis synchronization is not supported when using certain module revisions.
699823 LabVIEW 2018 10GbE projects require component-level IP (CLIP) rescan.
629286 Transmitter (TX) channel synchronization error occurs when initializing the baseband TX modules.
601381 Sample Clock on PXIe-7902 High-Speed Serial Instrument not enabled after reboot.
582362 Putting OS into Sleep state while NI-mmWave session is open results in error -63150, -52007.
582132 Gain ranging takes 4x (2x) longer than typical on first (second) instruction when using PXIe-1075 Chassis.


ID Known Issue
713511

Return

Multiple PXI Express chassis synchronization is not supported when using certain module revisions.

Multiple PXI Express chassis synchronization for the mmWave Transceiver System is not supported when using a revision B PXIe-3610 Waveform Generator module and a revision B PXIe-3630 Digitizer module. To determine which module revision you have, complete one of the following tasks:

  • Refer to the label on the side of your module; the part number is printed on the label. The letter in the part number identifies the revision of the module. For example, part number 140137A-01L identifies a revision A PXIe-3610.
  • Run Get Module Information from the ni3610_and_ni3630_Driver_Lib.lvlib API.
Workaround: To configure multiple chassis, you must use a revision A PXIe-3610 module and a revision A PXIe-3630 module. 
Reported Version: 18.1    Resolved Version: N/A    Added: 10/17/18
699823

Return

10GbE projects require component-level IP (CLIP) rescan in LabVIEW 2018.

When compiling the example 10GbE project in LabVIEW 2018 (32- and 64-bit), code generation will fail with the following error: "The CLIP declaration file was updated on disk since it was associated with this LabVIEW project. Rescan the CLIP declaration in the Component-Level IP page of the FPGA Target Properties dialog box. File: C:\Program Files (x86)\National Instruments\LabVIEW 2018\Targets\NI\FPGA\RIO\790XR\CLIP\v1\V7\10GbE\TenGbeClip.xml."

Workaround:

  1. Right-click on the target in the project and select Properties to open the FPGA Target Properties dialog box.
  2. Select the Component-Level IP category.
  3. Select the TenGbECLIP Open Core declaration.
  4. Click the Rescan all Files button.
  5. Close the FPGA Target Properties dialog box.
  6. Save the project.

You will not need to repeat this process after saving the project.

Reported Version: 18.0    Resolved Version: N/A    Added: 10/04/18
629286

Return

TX channel synchronization error occurs when initializing the baseband TX modules.
When initializing the baseband TX modules by calling the Open VI in the NI mmWave Reference Project, you may get the following error:

Error code: -1 Sync TX.vi<ERR> TX channel cannot be synchronized. The measured skew exceeds 1.5 samples.

This error indicates a synchronization issue between the PXIe-3610 Waveform Generator and the PXIe-7902 module.

Workaround: Ensure that both modules are placed in the same bus segment and are connected using mini-SAS HD cables that are less than or equal to 1 m. Ensure proper chassis fan settings, adequate airflow, and ambient temperatures within the specified operating range. Visit ni.com/manuals and refer to the mmWave Transceiver System Getting Started Guide or mmWave Transceiver System Specifications for environmental requirements.

If you modified the FPGA code and introduced additional delay on the in-phase/quadrature (I/Q) data path, ensure that you have compensated for this delay on the Host code.

After verifying proper hardware configuration and delay compensation in the code, try to reproduce the error by running the Multichannel Transceiver (Host) VI, found in the NI mmWave Reference Project. If the problem persists, contact National Instruments support at ni.com/support.

Reported Version: 15.3    Resolved Version: N/A    Added: 06/05/17
601381

Return
Sample Clock on PXIe-7902 High-Speed Serial Instrument not enabled after reboot.
External FPGA clocks, including the Sample Clock(s), are not maintained when the system is rebooted without being powered down. Re-downloading the relevant bitfiles will re-sync these clocks. If the force download flag is not set to TRUE, the TX Open VI and the RX Open VI will error out when attempting to open a new session because bitfiles are not downloaded automatically after a soft reset.

Workaround: Ensure the force download flag is set to TRUE (default) on Open VI.

Reported Version: 15.1    Resolved Version: N/A    Added: 09/16/16
582362

Return
Putting OS into sleep state while NI-mmWave session is open results in error -63150, -52007.
NI-mmWave does not support sleep mode. If a Windows system is put into a sleep state while an NI-mmWave session is open and actively running, the hardware will enter an invalid state. After waking the system. attempting to open a new session to the PXIe-3620 RF Upconverter and Downconverter or PXIe-7902 module will result in error -63150 (operation failed) or -52007 (operation timeout).

Workaround: Disable Windows power management modes, such as sleep, standby, and hibernate, when using this product.

To recover after this error, completely power down and reboot the system to return it to a known state.

Reported Version: 15.0    Resolved Version: N/A    Added: 09/16/16
582132

Return
Gain ranging takes 4x (2x) longer than typical on first (second) instruction when using PXIe-1075 Chassis.
When using NI-P2P to send gain ranging instructions to an NI-mmWave device in a PXIe-1075 chassis, the first instruction sent after linking the sender and recipient takes four times the configured dwell time. The second instruction takes twice the configured dwell time. Instructions after this adhere to the dwell time.

Workaround: Use the PXIe-1085 Chassis. If a PXIe-1075 chassis must be used, and settling time for the first set of instructions is critical, link and send multiple instructions prior to beginning acquisition/generation.

Reported Version: 15.0    Resolved Version: N/A    Added: 09/16/16

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