Archived: LabVIEW Communications System Design Suite 4.0 Known Issues
Updated Mar 17, 2020
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.
This document contains the LabVIEW Communications System Design Suite 4.0 known issues that were discovered before and since the release of LabVIEW Communications System Design Suite 4.0. Not every issue known to NI will appear on this list; it is intended to only show the severe and more common issues that can be encountered.
Note: As of the release of LabVIEW Communications System Design Suite 3.0, most FPGA functionality is now contained in the LabVIEW NXG FPGA Module which is included in the LabVIEW Communications System Design Suite. For FPGA Known Issues in LabVIEW Communications System Design Suite 4.0, refer to LabVIEW NXG 4.0 FPGA Module Known Issues.
Error 0x80004005 can occur when trying to configure the Ethernet settings on a LabVIEW Communications Real-Time Target when no Ethernet connection is present
When trying to change the Ethernet port settings on a LabVIEW Communications Real-Time Target, error 0x80004005 will occur if no connection is active on the port.
Workaround: Connect the Ethernet port you are trying to configure to an active network connection. For example, connect the port to a switch.
Dropping a large number of unplaced FPGA devices in SystemDesigner can cause a hang
Attempting to drop a large number of FPGA (USRP RIO or FlexRIO) devices in SystemDesigner, such as using the Unplaced Live Hardware>>All menu, can fail or cause a hang.
Workaround: Drop the FPGA hardware items one by one.
When debugging a LabVIEW Communications Real-Time Target, the dialog indicating a target reboot will not disappear if the application name has a space.
If trying to debug an application which has spaces in the name on a LabVIEW Communications Real-Time Target, the dialog indicating that the target is rebooting after deployment will not clear.
Workaround: Remove any spaces from the name of the application document.