Each issue appears as a row in the table and includes the following fields:
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:
| |||||
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."
You will not need to repeat this process after saving the project.
| |||||
629286 Return |
TX channel synchronization error occurs when initializing the baseband TX modules. 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. 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.
| |||||
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.
| |||||
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.
| |||||
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.
|
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.