Home Support Documentation Bugs

Archived: LabVIEW Communications System Design Suite 2.1 Bug Fixes

Updated Mar 10, 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.

Overview

The following items are a subset of known issues fixed between LabVIEW Communications System Design Suite 2.0 and 2.1. If you have a CAR ID, you can search this list to validate that the issue has been fixed. This is not an exhaustive list of all bugs fixed in this release and does not capture bugs that were fixed in LabVIEW NXG.

ID

Fixed Issue
576267When a GCDL document exists under two FPGA targets and is added to a VI under a PC target, the icon will display incorrectly.
587454Adding a large number of files to the project from the Navigation Pane can cause the application to hang or become unresponsive for a time.
587522Changing the build spec from "Bitfile" to "None" during compilation will cause the compilation to fail. In LabVIEW Communications 2.1 the work flow has changed and the old work flow is no longer possible.
589526Creating local FIFOs near the maximum allowable sizes may cause compilations to fail with the message "There is a problem with one or more of the VIs associated with the compile".
595935If a design includes an array of complex double floating-point data types, and the "Profile Fixed Point Data" option is enabled for the VI, then running the VI in simulation may cause the application to hang and become unresponsive.

 

Back to top

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