Each issue appears as a row in the table and includes the following fields:
| ID | Known Issue | |||||
|---|---|---|---|---|---|---|
| 601381 Return | Sample Clock on PXIe-7902R 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.
| |||||
| 600897 Return | Installation error occurs when upgrading NI Linux Real-Time Support for NI mmWave devices. When upgrading the support from NI mmWave 15.0 to NI mmWave 15.1, the target will enter a bad and unrecoverable state. The only way to recover from this state is to reformat the RT target. Workaround: To upgrade NI mmWave support on a Linux Real-Time Target that already has NI mmWave 15.0 installed, complete the following steps:
| |||||
| 583667 Return | NI mmWave incorrectly reports coerced value for out-of-bounds frequencies when using external LO. When using an external LO, the NI mmWave driver will coerce out-of-bounds frequency values specified by the user to be within the normal operating range of the hardware. The external source is not affected, but the value used for internal calculations and reported to the user will not accurately reflect the value of this source. Workaround: Using an external source outside the frequency ranges typically supported by NI mmWave hardware is not a valid configuration and will result in unexpected system behavior. Tune any external LO source to be within the range specified on the front panel terminal to which it is connected, and supply accurate frequency values for this source to the driver during configuration.
| |||||
| 582873 Return | PXIe-3620 session invalid after aborting session. The PXIe-3620 hardware may enter an unknown state if the session is forcibly closed by aborting a VI, ending the process, or any other method that terminates device communication without calling Close Session VI. Workaround: Always end the PXIe-3620 session by calling mmWave Close Session VI. To recover after this failure, power down the system completely and reboot.
| |||||
| 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 or PXIe-7902R hardware 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 a 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.
| |||||
| 580686 Return | MAX exposes unsupported features for PXIe-7902R. The settings page in MAX provides the following three configurable options that are not actually supported on the PXIe-7902R: Firmware Autoload Setting, Update Firmware, and Erase Firmware. Workaround: These options are not supported. Do not try to perform these actions.
|
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.